From nobody Sun May 08 17:42:18 2022 X-Original-To: ports-bugs@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 122801ABF463 for ; Sun, 8 May 2022 17:42:19 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KxBT66PL6z3nc8 for ; Sun, 8 May 2022 17:42:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id BC4C928FF3 for ; Sun, 8 May 2022 17:42:18 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 248HgIwe041790 for ; Sun, 8 May 2022 17:42:18 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 248HgI2w041789 for ports-bugs@FreeBSD.org; Sun, 8 May 2022 17:42:18 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 263867] www/gitlab-ce v14.10.0 failures when pushing or pulling Date: Sun, 08 May 2022 17:42:18 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: gwright@antiope.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: mfechner@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter flagtypes.name Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Ports bug reports List-Archive: https://lists.freebsd.org/archives/freebsd-ports-bugs List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports-bugs@freebsd.org X-BeenThere: freebsd-ports-bugs@freebsd.org MIME-Version: 1.0 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1652031738; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=wEJ25uEdhpivNcIYsB13sQoYZz4w2HoIETDbiOy+dlA=; b=gN2DCGirZKfK6MoW3djl4sSqqSJcf1RM85yNMJwT1FxORe4hxV0TYm5XbZ+/nrgoJ82vq4 8qdXYRiCfFdbRVjOkZFQH9X+9R8r2Acd8Mc9Zs8/LG+ugOQ/jni33yVaUWTd+glnHTiLrc Oft9BJgVyxDoSJB0uFra95TpzlpFuKu3SCf+qX/OjawxMd8Cy8OJ4pNQrhBulZqFHHuCXP +15pETb5mBeKpoGCPFcuhbA9OHzgIi4fSVMP2BG7iqlUDzl6meuQPeEHBzr03chNfHJ6i/ fhqFUpv3HLxD/K9N01oNaJ7F+irPutXB8F6mPQDMUA7Rr259JELEGBNE2Niqdg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1652031738; a=rsa-sha256; cv=none; b=l5GfGkKxWfiNT87pvIITfZ8uRBrUFUzHQJJRcgebZAcWzQg0Tx76XI0ih42jU8hVHPVbm+ QgAEEYmsrH87/KfNlJXAKJIE85tSmQkb9/+FCiNWPzpUDCqzLFy2L7BBGRzhUpxYgX6+bT PTo/wbt9M0dr+VemrPnI8FA/UYDudK3SVrvFF4zbS5f1EeXHnT2cCeRlzezSz8eeqWz8Vq jGtNKEW5iLNyoqII/7qFcKO/K6SiTpQ6Zd/YEoLx+AfWvVYTzy9BNEEc5WTV8Emiu8cQZE LUqK314vngoPNEvBpagSPyGEDSwLWk01lcBhQCMvug+zqttfUqLzPcoZJcD2rA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263867 Bug ID: 263867 Summary: www/gitlab-ce v14.10.0 failures when pushing or pulling Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: mfechner@FreeBSD.org Reporter: gwright@antiope.com Assignee: mfechner@FreeBSD.org Flags: maintainer-feedback?(mfechner@FreeBSD.org) Hi Matthais, The recent gitlab-ce (v14.10.0) introduced an annoying bug. It shows up as failure to push/pull from a server running gitlab, and apparent corruption = of repositories on the Gitlab server. Here are the observed symptoms. When pushing, I get: (base) ~/src/vev-renormalization> git push warning: core.fsyncObjectFiles is deprecated; use core.fsync instead Enumerating objects: 5, done. Counting objects: 100% (5/5), done. Delta compression using up to 8 threads Compressing objects: 100% (3/3), done. Writing objects: 100% (3/3), 389 bytes | 389.00 KiB/s, done. Total 3 (delta 2), reused 1 (delta 0), pack-reused 0 remote: warning: core.fsyncObjectFiles is deprecated; use core.fsync instead remote: warning: core.fsyncObjectFiles is deprecated; use core.fsync instead remote: fatal: commit-graph requires overflow generation data but has none warning: core.fsyncObjectFiles is deprecated; use core.fsync instead fatal: commit-graph requires overflow generation data but has none remote: warning: core.fsyncObjectFiles is deprecated; use core.fsync instead To ssh:///software/vev-renormalization.git ! [remote rejected] master -> master (missing necessary objects) error: failed to push some refs to 'ssh:///software/vev-renormalization.git' Going to the corresponding repository on the server, I see: [git@gitlab ~/repositories/@hashed/92/2c/922c7954216ccfe7a61def609305ce1dc7c67e225f873f= 256d30d7a8ee4f404c.git]$ git fsck --full Checking object directories: 100% (256/256), done. fatal: commit-graph requires overflow generation data but has none [git@gitlab ~/repositories/@hashed/92/2c/922c7954216ccfe7a61def609305ce1dc7c67e225f873f= 256d30d7a8ee4f404c.git]$ echo $? 128 After some searching, I found this recommendation: https://docs.gitlab.com/ee/install/installation.html#git Now GitLab seems to depend on a version of git patched to work with a particular version of gitaly. In the jail in which I run gitlab, I did: > cd /tmp > git clone https://gitlab.com/gitlab-org/gitaly.git -b 14-10-stable /tmp/g= italy > cd /tmp/gitaly > gmake git GIT_PREFIX=3D/usr/local This installed the patched version of git, overwriting the binaries install= ed in /usr/local/by the git package. After I did this, the repository checked clean: 05ce1dc7c67e225f873f256d30d7a8ee4f404c.git # git fsck --full Checking object directories: 100% (256/256), done. Checking objects: 100% (107/107), done. Verifying commits in commit graph: 100% (24/24), done. Also after switching to the patched version of git, pushing from a remote worked without error. It is rather annoying that gitlab (or perhaps more specifically gitaly) can= not use the released git. Let me know if I can run more experiments. Reinstal= ling git from packages seems to reliably recreate the failed state, at least for= one of my repositories. BR, Greg --=20 You are receiving this mail because: You are the assignee for the bug.=