From nobody Tue Oct 01 09:00:30 2024 X-Original-To: git@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 4XHsNN0wKcz5XXBc for ; Tue, 01 Oct 2024 09:00:36 +0000 (UTC) (envelope-from mfechner@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (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 "smtp.freebsd.org", Issuer "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XHsNN0Rt1z4lbB; Tue, 1 Oct 2024 09:00:36 +0000 (UTC) (envelope-from mfechner@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727773236; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+wXB8as6ACXb1GVAFGULZGU8uDnIPGrItFoB0kAiIKs=; b=FSaOGDEHTYx77MdQMEX+BBqGXr5ak1iq5BsBRfOOVD34xt4W0BgICbqnJ4G5+nDiN07aO1 ofc2LxZH44WqJebMWyI20pCSm7QP2UV2g/MDSmmbTFyE7guOJ7BGsAmDPSB2m/WhHCrZtY K6tpEqrEC7+dXBIt8pZK7Q3oBfJNJjm74NANmMqnxB3E+UgEV24YgjPDSrPO84Ksmq/gD0 G8/O4zKwdiOIry6zzyWkR63++JGZ+vfhK/4/+8+5EkmFegtnvTHzO2O13xS7pNAWbM+1z+ cFSePhrzmnV44QVnmbQ1bPEz1zdkww43hAgy9R6t21GT/TI3dVxLyb0zo6rMiw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727773236; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+wXB8as6ACXb1GVAFGULZGU8uDnIPGrItFoB0kAiIKs=; b=NdqqpZT05zhf3nrhsm6+38m8ZnZpQm2uNgAQAb95k0sKaGi22Hv5UfxONMYZ4Gjfwz4YrM wdIMSlLK8PYlkIsFFXvJb+4c9uPNeIVA/fTuUQaz6qttkNguhp/TyWF+VW+eknWslj94i+ HHoSmkEX3JCHOjUQOKsQ8J9Y0Bxexw88s3ThuKmQ3VKuyfuO16U/v6cFOW1CRjTq07fYme xIlmKDBZBHnCmn2zRuFdXeYNtNnmw53F24G7kjhxsexHhC+LPprFZ87/zM1uwhNAQrTKFy Lx2n7677g2rkujc1W57bOVIZUyxwuIL+sUi718tYTsW9cuV4vS32X+77yTny2w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727773236; a=rsa-sha256; cv=none; b=S7XCDTiTQF2ENnCrb/G52D2u4QLQ9IrYBs3oKofaZ9UOGIGtNJLJWjiuw5ySuy9iLugJY3 bfAUa9RKRQDyPheSNvSBdjiMJb84dKmsOAo6STSVAjPEsOTtQ/Rr/HFf0TYvuiFeUb9SyP 2tInrYD5Nz0Ny+eC7VRTKW1lFGB9CjA6vrMZ0NuPtnoZH5Ji05iE4yi9k0aEZyuHpndH95 8sJ43e2epovpVvzQvGDcZcX5xxHaED/LnNlOUV6TEygudDfz7f6k4Y4r7uW+663E/XgZQN JGmV4lMY9wkuuETWIas4BA4L+oZqU7nXahJPOt2pbibslV9XZk5/8I1taahezg== Received: from [192.168.1.151] (unknown [212.108.151.172]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: mfechner) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XHsNL5Yc5zjJg; Tue, 1 Oct 2024 09:00:34 +0000 (UTC) (envelope-from mfechner@freebsd.org) Message-ID: Date: Tue, 1 Oct 2024 12:00:30 +0300 List-Id: Discussion of git use in the FreeBSD project List-Archive: https://lists.freebsd.org/archives/freebsd-git List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-git@FreeBSD.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Impossible to push my ports directory to my CI/CD pipeline To: Dave Cottlehuber Cc: git@freebsd.org References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> Content-Language: en-US From: Matthias Fechner In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Dave, Am 01.10.2024 um 10:04 schrieb Dave Cottlehuber: > I'm curious why you use the `lfs` here, I guess its just to > show lfs-related issues, and normally you don't use it? > > Anyway on a fresh checkout, this works fine: > > git clone -vv git@gitrepo.freebsd.org:ports.git -b main ports > > trying `git lfs clone ...` reports: > > WARNING: 'git lfs clone' is deprecated and will not be updated > with new flags from 'git clone' > > but also has no issues. > > In either case, `git lfs ls-files` shows nothing. > > It's not clear to me how git "knows" about lfs, but there are > a bunch of XDG_DIR config files that may impact this, viz: > > https://git-scm.com/docs/gitattributes > >> If I now try to push to my local repo I get: >> >> git push origin >> Warning: untrusted X11 forwarding setup failed: xauth key data not generated >> Locking support detected on remote "origin". Consider enabling it with: >>   $ git config >> lfs.https://gitlab.fechner.net/mfechner/Gitlab.git/info/lfs.locksverify true >> Unable to find source for object >> 99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d (try > My current thinking is there's nothing (as yet) obviously wrong with > FreeBSD's git repos, but there's possibly something interacting with gitlab. > > Can you create a new github repo, and try pushing your ports tree to that, > to see if it sees the same issue? > > Given I can't replicate this here, perhaps there is a $SOMEWHERE}/.config/git/attributes > or similar /config file that influences git tooling? I just did a fresh clone: git clone git@gitrepo.freebsd.org:ports.git cd ports git lfs ls-files --all 6d0aef4ba9 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.aarch64/libswt-atk-gtk-4965r11.so ed324ddc16 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.aarch64/libswt-awt-gtk-4965r11.so c0155fc8e7 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.aarch64/libswt-cairo-gtk-4965r11.so a928176ec9 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.aarch64/libswt-glx-gtk-4965r11.so c89e491472 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.aarch64/libswt-gtk-4965r11.so 5dbe70b5c8 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.aarch64/libswt-pi3-gtk-4965r11.so 42fa733026 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.aarch64/libswt-webkit-gtk-4965r11.so f5417c277c - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.powerpc64/libswt-atk-gtk-4965r11.so b2e525c385 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.powerpc64/libswt-awt-gtk-4965r11.so 9ef847d4e6 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.powerpc64/libswt-cairo-gtk-4965r11.so a1ffa59143 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.powerpc64/libswt-glx-gtk-4965r11.so 99a670c083 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.powerpc64/libswt-gtk-4965r11.so e8e2d306fd - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.powerpc64/libswt-pi3-gtk-4965r11.so 1d41b04bdd - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.powerpc64/libswt-webkit-gtk-4965r11.so ca2c21bf21 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.x86_64/libswt-atk-gtk-4965r11.so f56db5e813 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.x86_64/libswt-awt-gtk-4965r11.so b5e05ef77e - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.x86_64/libswt-cairo-gtk-4965r11.so 4fc786126d - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.x86_64/libswt-glx-gtk-4965r11.so f7db6794c6 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.x86_64/libswt-gtk-4965r11.so 8813907b0f - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.x86_64/libswt-pi3-gtk-4965r11.so 5db9424884 - java/eclipse/files/addons/eclipse.platform.swt/binaries/org.eclipse.swt.gtk.freebsd.x86_64/libswt-webkit-gtk-4965r11.so so it seems that there is something in the FreeBSD repository. This can maybe get only fixed be rewrite the git history, but lets see, I'm currently not sure as no one else is seeing this... I saw also a message from another user in the all-developer mailing list that also pointed to the same problem, so it is maybe not only me having that problem. If have git-lfs installed, maybe that is required to see this problem? pkg info |grep git git-2.46.2                     Distributed source code management tool git-gui-2.46.2                 Git GUI (Graphical User Interface) components git-lfs-3.0.2_23               Git extension for versioning large files gitaly-17.4.1                  Smart reverse proxy for GitLab gitlab-agent-17.4.1            GitLab kubernetes agent gitlab-ce-17.4.1               Web GUI for managing git repositories gitlab-elasticsearch-indexer-5.2.0 Elasticsearch indexer for GitLab gitlab-pages-17.4.1            Official GitLab Pages daemon gitlab-runner-17.4.0           Official GitLab Runner written in Go gitlab-shell-14.39.0           GitLab Shell handles git commands for GitLab gitlab-workhorse-17.4.1        Smart reverse proxy for GitLab libexif-0.6.24                 Library to read digital camera file meta-data libgit2-1.7.2                  Portable, pure C implementation of the Git core rubygem-danger-gitlab-8.0.0    Code Review rubygem-et-orbi-1.2.11         Time zones for fugit and rufus-scheduler rubygem-fugit-1.11.1           Time tools for flor and the floraison project rubygem-fugit18-1.8.1          Time tools for flor and the floraison project rubygem-git-1.19.1             Ruby wrapper library around git(1) rubygem-gitaly-17.4.0          Auto-generated gRPC client for gitaly rubygem-gitlab-4.20.1          Ruby client and CLI for GitLab API rubygem-gitlab-chronic-0.10.6  Natural language date/time parser written in pure Ruby rubygem-gitlab-dangerfiles-4.8.0 Dangerfile and plugins for GitLab projects rubygem-gitlab-experiment-0.9.1 Experiment library for Gitlab rubygem-gitlab-fog-azure-rm-2.1.0 Stripped-down fork that enables Azure Blob Storage rubygem-gitlab-glfm-markdown-0.0.20 Markdown processing for GitLab Flavored Markdown rubygem-gitlab-kas-grpc-17.4.1 Auto-generated gRPC client for KAS rubygem-gitlab-labkit-0.36.1   Instrumentation for GitLab rubygem-gitlab-license-2.5.0   Generate, verify and enforce software licenses rubygem-gitlab-mail_room-0.0.24 Proxy email (gmail) from IMAP to a delivery method rubygem-gitlab-markup-1.9.0    Render any fancy GitLab markup rubygem-gitlab-net-dns-0.9.2   Pure Ruby DNS library rubygem-gitlab-sdk-0.3.0       Client side Ruby SDK for GitLab Application services rubygem-gitlab-security_report_schemas-0.1.2.min15.0.0.max15.2.0 Ruby gem for GitLab security report JSON schemas rubygem-gitlab_chronic_duration-0.12.0 Natural language parser for elapsed time rubygem-gitlab_omniauth-ldap-2.2.0 LDAP strategy for OmniAuth rubygem-omniauth-github-2.0.1  Official OmniAuth strategy for GitHub rubygem-rugged-1.7.2           Ruby bindings to the libgit2 library I'm very sure that the problem is not related to gitlab, but the source problem is in the FreeBSD ports repository. Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook