From nobody Mon Sep 30 10:09:32 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 4XHGyW203Qz5Y4hB for ; Mon, 30 Sep 2024 10:09:39 +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 4XHGyV71t4z3wYQ for ; Mon, 30 Sep 2024 10:09:38 +0000 (UTC) (envelope-from mfechner@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727690979; 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=3TWeq55rvVKS1g04sIWLdibFUKq2UxB9P/KzvtJ1Yqk=; b=MIbLv5SZpkBeWjhIK7uQg5AeIsXJdDgTxaWDeu7dKmxemdOZzSGgP8lgSCMyHADIqFZbmB 18VKuZphWpSHf5PclJkDtAixLVMFkyHD3xHgZIAhLEec/7vqnAn8/cn1NmO3DB6pd6+DGV ZlMngTrkbP5XTE+B4Ein4BJTSpvMokapYzN+QVsMMu67AAWiefXq02uqQj4OVFpBYtKQRR aE6FOUBwxdx1Rkl6Cz/xpOqWZC2ABCsT2DktEU+PqSGrcK64LSMrn39b0Q1iItD1jkAZeJ 1m/+bjg7HA5uMjc5q6zEpEpgBKb+9riAUfUwIUnshx3JtoyQ2r/IcsZiBk3D8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727690979; 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=3TWeq55rvVKS1g04sIWLdibFUKq2UxB9P/KzvtJ1Yqk=; b=Mg6D/ENYIRvjuIX4Y0sh5Ap6P2+kMpcFL9dqhmpFnwvUmdiDkmj5MkTYS/JKVMlbQNzgST jUr3XaMGTvbHwVzjCG85l1VpoxIue1wOvuFrNZOnappCdznJsBwRhsTBntj2gLje0uIirA DBpJQ2VtpS1t8D9Y6M51pyvAfRZ0TDbL7vli6tZCCyhtiTQr10L4Y6QhUGUQ9odUPqA2EK HMtVUwkUPkvCS8iVbKDfluuDnWRa/Ny8P/CFs23T9mGb7rcQTw4i1N0f1saR/EKZrsM082 4kdHHsaQLwyVd/Kwqss9MsLBpWIN6X1h+CIrFI3jhdXZTuxahSXdIxGVSxMDiA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727690979; a=rsa-sha256; cv=none; b=BJ84/Ex1QPYrzjQGTfnqf49bwyoK/f4OxpBWDdGCYNxYqZ1ZiX0H9D5nzdJQN0JWP0Xri3 IsFlERd+8mKs5zu+1mFQYWLeNYqMDze+Pj5ykzNxhOmpDaSlPtusinpR+aHbFzx8EumwBM unGCRzY0aoR+ORubER7Q8sMvwDWqHa7576COoGaTrjr5TOB25MDSo6IPewAQecxlpK0nL+ tM/1JYi74DrdpHI90HzZXdvLHF2XyEWd/ckHd0NHk/7hQnflsxkJPS8MCPWe7FoVOL8/s+ K0cCYj9hac5rREjYj0V0UXYvY3P/1Tmuz8hRcYzHQtC2glphd92XVOvqopx7ww== 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 4XHGyV2JGBzFsQ for ; Mon, 30 Sep 2024 10:09:38 +0000 (UTC) (envelope-from mfechner@freebsd.org) Message-ID: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> Date: Mon, 30 Sep 2024 13:09:32 +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 To: git@freebsd.org Content-Language: en-US From: Matthias Fechner Subject: Impossible to push my ports directory to my CI/CD pipeline Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Dear all, I already tried to address that problem on the all-developer list, but it is maybe better to put it here. I think by accident someone pushed LFS object with a commit of java/eclipse. git remote -v freebsd git@gitrepo.freebsd.org:ports.git (fetch) freebsd git@gitrepo.freebsd.org:ports.git (push) freebsd-https   https://git.freebsd.org/ports.git (fetch) freebsd-https   https://git.freebsd.org/ports.git (push) githubfreebsd   https://github.com/freebsd/freebsd-ports.git (fetch) githubfreebsd   https://github.com/freebsd/freebsd-ports.git (push) origin  git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) origin  git@gitlab.fechner.net:mfechner/Gitlab.git (push) git lfs fetch --all freebsd fetch: 22 object(s) found, done. fetch: Fetching all references... [99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d] Object does not exist on the server: [404] Object does not exist on the server [c89e491472c8af1d153e2e2801836fad0e38f428d0250ed982e16baa5effbe4f] Object does not exist on the server: [404] Object does not exist on the server [f7db6794c6c3e7a03a3987537b8a0cdb1bde2996ed7c7eec50f2e5df1e7a30c2] Object does not exist on the server: [404] Object does not exist on the server [e8e2d306fd11358a07b4ee10bfef19de3b518793568fc498cdd989170d31712b] Object does not exist on the server: [404] Object does not exist on the server [5dbe70b5c83520df09c100815bb164c8903da5eb8bffbd094aaaed54b212d73a] Object does not exist on the server: [404] Object does not exist on the server [8813907b0f7b001080a346ed2d0307a1c749b85688fdfa1d270fe59a07aa3909] Object does not exist on the server: [404] Object does not exist on the server [1d41b04bdd4115c52aac8177e1b899403a3d7d9f6d147cd864463029648a4714] Object does not exist on the server: [404] Object does not exist on the server [c0155fc8e7c4b9736d81db638fed95bc9ff297453bfd0bbd7dd5d882ebca6e89] Object does not exist on the server: [404] Object does not exist on the server [6d0aef4ba9e96d4c63baae8db9cdce7c634140a2bda7da670e698e38e0df57ce] Object does not exist on the server: [404] Object does not exist on the server [a928176ec92ad347404b2454e5f4f321aaef8ba862a60b0c28adc3bdcc619a4a] Object does not exist on the server: [404] Object does not exist on the server [42fa73302624dc511e6d8958c66c82f31b8d9155f2980343b6bcdc25345e1dcd] Object does not exist on the server: [404] Object does not exist on the server [ed324ddc16ccb8b9fab3041da394b844166b6778c39cd12708bcade05b41c0da] Object does not exist on the server: [404] Object does not exist on the server [9ef847d4e699b5dbe49ac74ee35596fdddc22c6335bc96affee19a99ecd077f5] Object does not exist on the server: [404] Object does not exist on the server [f5417c277c6ca509334010bb6999c56c3ab5d3751204c74dc00c2fa25d93dfae] Object does not exist on the server: [404] Object does not exist on the server [a1ffa591430df806983c8798113264f12ea679bce4b785d70d2868dc91cec883] Object does not exist on the server: [404] Object does not exist on the server [b2e525c38598dac6885a75e7eaffa346c8aca3dbdda73cb0275f50103ec3d245] Object does not exist on the server: [404] Object does not exist on the server [5db9424884396cf5bfc46a6b22dacbe245f43a7e1eda6aeac831905dc921802e] Object does not exist on the server: [404] Object does not exist on the server [b5e05ef77effb4048e72e38605700151fdf4eae214cfa358e9e81a48e124cb52] Object does not exist on the server: [404] Object does not exist on the server [ca2c21bf21e1fa2f53c72653ea57e76506c305bdd44c6416542ebbf2ab8b1b83] Object does not exist on the server: [404] Object does not exist on the server [4fc786126dd64f936554a12c4752787c4989453654fc5d6fd119b6e5eeafec6f] Object does not exist on the server: [404] Object does not exist on the server [f56db5e81304e441260b84d6c2805ae7050ea56760d763d2b32e6be928fa1cae] Object does not exist on the server: [404] Object does not exist on the server error: failed to fetch some objects from 'https://github.com/freebsd/freebsd-ports.git/info/lfs' I have my own testing pipeline in place to automatically test my commits against changes I did to ports. But as LFS is now in the FreeBSD repository, but the files cannot be retrieved from the FreeBSD repository I'm now locked out for my CI/CD pipeline and my automated tests. 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 running git lfs fetch --all) Uploading LFS objects:   0% (0/21), 0 B | 0 B/s, done. error: failed to push some refs to 'gitlab.fechner.net:mfechner/Gitlab.git' Does anyone have an idea how that can be fixed? 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 From nobody Tue Oct 1 07:04:47 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 4XHpqB3T4wz5XNpH for ; Tue, 01 Oct 2024 07:05:10 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from fout-a8-smtp.messagingengine.com (fout-a8-smtp.messagingengine.com [103.168.172.151]) (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 mx1.freebsd.org (Postfix) with ESMTPS id 4XHpqB0Y3zz4bBL; Tue, 1 Oct 2024 07:05:10 +0000 (UTC) (envelope-from dch@skunkwerks.at) Authentication-Results: mx1.freebsd.org; none Received: from phl-compute-02.internal (phl-compute-02.phl.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id E51D61381F46; Tue, 1 Oct 2024 03:05:08 -0400 (EDT) Received: from phl-imap-02 ([10.202.2.81]) by phl-compute-02.internal (MEProxy); Tue, 01 Oct 2024 03:05:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm3; t=1727766308; x=1727852708; bh=XXxbJQ50KmEr3xNIEVlPymi6MoAV607K +p1dvSAlYEk=; b=nLSYRH4b3Mbf2ukahQ56D9V6TR3yMv5mklYIoTpKnpId0G4+ s/h7LEMqmhCGDLoOQGszIizx5KoIJQzldqUjFo0rAdU4PC1bZY5af/9u+x6OpX7X 4QeZPWexKasR3iBNA39RkZ2M95Ix/tHtTApaMzK0vRg/4nRemD5uSDSjQPAezsdU xQr49dHK7U+2jg0DR9UMTM5dvQC1EYUwknNX06a+/Owrtk5CJ6gLgoqHo0IgNci4 KMEvrF/u7lmTtBWgbgbsadJsTvzO8/uxc+4QbV9lUnEXx5u+2CIblgIOMhqT0zfo To8iU4yVBoeZAcpNfjKkoPmeB/LcSW6StkND1g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1727766308; x= 1727852708; bh=XXxbJQ50KmEr3xNIEVlPymi6MoAV607K+p1dvSAlYEk=; b=b qtGVfwr0sieknJO7sC3JCEXcNJ3yDkq3OPHWXhkf3FahVGTA3ghtISYqE4WoLwGi jby1SSmA7WpE4+gtw+EDiEgl1dCMwVuWSDEI0s/CZCO6Rc8Tu9DTBZtyy/xqnb5L RvFs8t4P/PbaMnMzeqyQ9InfpN+yOZTOI+hr2zzw6RDkj4GwJbYefLvStuF4sV4f msj0lpROtaN18Je8xmFgt1wCtZgmuGor19KvNr2Bm1nttaFGFw6N+VyOclx1iDL7 osbTJhYxvbYN5ymFAJDKZw+LebHAM7b78pOidubf2Zke232qOwr/lms0RwvIfGUw IUtoAg5YkyzfrlCBZi5OA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdduiedgudduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefoggffhffvvefkjghfufgtgfesthhqredtredt jeenucfhrhhomhepfdffrghvvgcuvehothhtlhgvhhhusggvrhdfuceouggthhesshhkuh hnkhifvghrkhhsrdgrtheqnecuggftrfgrthhtvghrnhepveelieeljeeifedvhfefhffh geevtdejgefgtedugfeuhfdvuddvvdduhfegteeknecuffhomhgrihhnpehfrhgvvggssh gurdhorhhgpdhgihhthhhusgdrtghomhdpghhithdqshgtmhdrtghomhdpfhgvtghhnhgv rhdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpegutghhsehskhhunhhkfigvrhhkshdrrghtpdhnsggprhgtphhtthhopedvpdhmohgu vgepshhmthhpohhuthdprhgtphhtthhopehgihhtsehfrhgvvggsshgurdhorhhgpdhrtg hpthhtohepmhhfvggthhhnvghrsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: ic0e84090:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 2330BB00068; Tue, 1 Oct 2024 03:05:08 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface 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 Date: Tue, 01 Oct 2024 07:04:47 +0000 From: "Dave Cottlehuber" To: "Matthias Fechner" Cc: git@freebsd.org Message-Id: In-Reply-To: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US] X-Rspamd-Queue-Id: 4XHpqB0Y3zz4bBL X-Spamd-Bar: ---- On Mon, 30 Sep 2024, at 10:09, Matthias Fechner wrote: > Dear all, > > I already tried to address that problem on the all-developer list, but=20 > it is maybe better to put it here. > I think by accident someone pushed LFS object with a commit of java/ec= lipse. on fediverse there was speculation that this is just files that look similar to git-lfs, and gitlab gets confused by them, not actually lfs files. In all cases I've seen, its been a gitlab instance that has had issues. > git remote -v > freebsd git@gitrepo.freebsd.org:ports.git (fetch) > freebsd git@gitrepo.freebsd.org:ports.git (push) > freebsd-https=C2=A0=C2=A0 https://git.freebsd.org/ports.git (fetch) > freebsd-https=C2=A0=C2=A0 https://git.freebsd.org/ports.git (push) > githubfreebsd=C2=A0=C2=A0 https://github.com/freebsd/freebsd-ports.git= (fetch) > githubfreebsd=C2=A0=C2=A0 https://github.com/freebsd/freebsd-ports.git= (push) > origin=C2=A0 git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) > origin=C2=A0 git@gitlab.fechner.net:mfechner/Gitlab.git (push) > > git lfs fetch --all freebsd 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 gen= erated > Locking support detected on remote "origin". Consider enabling it with: > =C2=A0 $ git config=20 > lfs.https://gitlab.fechner.net/mfechner/Gitlab.git/info/lfs.locksverif= y true > Unable to find source for object=20 > 99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d (try=20 My current thinking is there's nothing (as yet) obviously wrong with FreeBSD's git repos, but there's possibly something interacting with git= lab. Can you create a new github repo, and try pushing your ports tree to tha= t, to see if it sees the same issue? Given I can't replicate this here, perhaps there is a $SOMEWHERE}/.confi= g/git/attributes or similar /config file that influences git tooling? A+ Dave From nobody Tue Oct 1 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 From nobody Tue Oct 1 12:57:15 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 4XHydZ5kSlz5XpFG for ; Tue, 01 Oct 2024 12:57:22 +0000 (UTC) (envelope-from mack@macktronics.com) Received: from mail.macktronics.com (coco.macktronics.com [209.181.253.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XHydZ3c4fz57nk; Tue, 1 Oct 2024 12:57:22 +0000 (UTC) (envelope-from mack@macktronics.com) Authentication-Results: mx1.freebsd.org; none Received: from olive.macktronics.com (olive.macktronics.com [209.181.253.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.macktronics.com (Postfix) with ESMTPS id 5EEFE1BDB; Tue, 1 Oct 2024 07:57:15 -0500 (CDT) Date: Tue, 1 Oct 2024 07:57:15 -0500 (CDT) From: Dan Mack To: Dave Cottlehuber cc: Matthias Fechner , git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline In-Reply-To: Message-ID: <58d3fa07-be0f-3223-9e74-a65932b069aa@macktronics.com> References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> 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 Content-Type: multipart/mixed; BOUNDARY="3735943886-50783150-1727787258=:65788" Content-ID: X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209, ipnet:209.181.252.0/23, country:US] X-Rspamd-Queue-Id: 4XHydZ3c4fz57nk X-Spamd-Bar: ---- This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3735943886-50783150-1727787258=:65788 Content-Type: text/plain; CHARSET=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: <8b972cc3-992c-f9ad-a944-c063816352ed@macktronics.com> On Tue, 1 Oct 2024, Dave Cottlehuber wrote: > On Mon, 30 Sep 2024, at 10:09, Matthias Fechner wrote: >> Dear all, >> >> I already tried to address that problem on the all-developer list, but >> it is maybe better to put it here. >> I think by accident someone pushed LFS object with a commit of java/eclipse. > > on fediverse there was speculation that this is just files that look > similar to git-lfs, and gitlab gets confused by them, not actually lfs > files. > > In all cases I've seen, its been a gitlab instance that has had issues. > >> git remote -v >> freebsd git@gitrepo.freebsd.org:ports.git (fetch) >> freebsd git@gitrepo.freebsd.org:ports.git (push) >> freebsd-https   https://git.freebsd.org/ports.git (fetch) >> freebsd-https   https://git.freebsd.org/ports.git (push) >> githubfreebsd   https://github.com/freebsd/freebsd-ports.git (fetch) >> githubfreebsd   https://github.com/freebsd/freebsd-ports.git (push) >> origin  git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) >> origin  git@gitlab.fechner.net:mfechner/Gitlab.git (push) >> >> git lfs fetch --all freebsd > > 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. Are the multiple gitlab's / githubs's all maintaining separate LFS namespaces or are they all using the same location(s) to store "large objects"? I have only implmented LFS on gitlab in two cases but I don't think repositories are necessarily portable with respect to where LFS objects are stored. IIRC gitlab will just keep big objects on disk on the same server by default but if you configure LFS to put stuff in S3 or somewhere else, is that inforamtion kept in the git repository or on the gitlab/github/etc repository? In other words, and I am probably wrong, I would not expect an LFS object on one gitlab server's LFS location to necessarily work 100% of the time if I got that repo from another gitlab server, as I think you would need to "migrate" the LFS objects from the source LFS location (disk, s3, etc) to the dest LFS location (disk, s3, etc). Dan --3735943886-50783150-1727787258=:65788-- From nobody Tue Oct 1 19:04:17 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 4XJ6my4q1Yz5YDn1 for ; Tue, 01 Oct 2024 19:04:18 +0000 (UTC) (envelope-from brooks@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 4XJ6my48Nlz4cCR; Tue, 1 Oct 2024 19:04:18 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727809458; 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: in-reply-to:in-reply-to:references:references; bh=3nZMarBbYO2Uh82DtDwa2lnYQGCrYhjnz2eoQhugUKc=; b=CS9Iju6Pg4rVYAF1AcBCAMFlwajpkJkGlo8jJRZzuy5JeoNdV1oTEXSNfZPm1TGbjg2mpM iB+KcCOSCVFtBQrzqaI8ZjNW0QFTrGfOlZ4n1q4LDWxNlhomyxxGgHeoVXk3lGl7igL+Tn 7ULd2ElrVJhbbI9iXXx/OhaHxsIgiSh+RuKg84Q8zhy7cvIvf+aNMMjmSiPjRMDabAYGsk wzdra+MFqD3U6mIxahNKz6aFfI8Ucv9PBTbMae7f880D43M6nZCyJsB/uFnwMZ1N4rDfsq SP0K2X3VPMFgjW3O9hIwTalGmkKH3yYtYEqOv5GUX7oleMbGFmPTgzNi6x2s7w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727809458; 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: in-reply-to:in-reply-to:references:references; bh=3nZMarBbYO2Uh82DtDwa2lnYQGCrYhjnz2eoQhugUKc=; b=QyZgwvJOOQ5HrVgaMBXRZgYvtJ6N79shyAqKBYZq9bH1QkYXVlopTJNsGsiUXiZRisu5Sf ZOhyxEERmJHVn04Z8OBhb1ujAVgt4Jlb+lpYzyLamQpf0WHvcMgC1xZ18dLCKwRuI7xXlI AL36liELBj0q3EvHQHHYKeIoE9FYt5gDi0Hc6G8U0xfmfd7hiQ6wzrE/M5AAsTeJQ6fCCf 2DpJ3YJc9iFzAOkYw8AwgCs9RjxaxOrkBd4n5IL2UsVcxF6w1+0BTeb9DHbf4+kctUPA6x 9y39Lnkt7IrTwrY4k5kR73xI5PIcZiLM/le2T5eYKDmaKzDYp5uRy1dRwaPwBQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727809458; a=rsa-sha256; cv=none; b=TBFuYwQZc4YAtI8xUUnOfu1Gc34TK3MGDPDWFPo+OnlREmfI0SfLzTCG+ModgVeoc/1ABx 6J2xElxTnzVs0nRalC6zlcCNdj1LYgBaViH2a869ldVeLr9E+W2+ZjZfushn5XVupxBzBE PVs5YhhCHE/Ix/QGPj9CYBrvteGpFRLgm2r96ZdBV+sByZDLtrcR5BxyKqm39m0GuC2J2M aeUFkNynYK9aBCwXGb+5nN3yoEIVEKhrB3AV3Bnkf5/lQhMEvhdw3XgjUZV+4AU7AmCLq0 EV+wmCzlVWEYhMBjKDz+OJG1thxK+BmUE45Obn3S2iR5O+6Qn1YjGUXsvWutHw== Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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) (Authenticated sender: brooks/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XJ6my3Tznz1BDM; Tue, 1 Oct 2024 19:04:18 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id D861A3C019B; Tue, 01 Oct 2024 19:04:17 +0000 (UTC) Date: Tue, 1 Oct 2024 19:04:17 +0000 From: Brooks Davis To: Matthias Fechner Cc: Dave Cottlehuber , git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Oct 01, 2024 at 12:00:30PM +0300, Matthias Fechner wrote: > 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 ... > > > > 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... Hmm, this is quite bizzare. It looks like running `git lfs ls-files --all` causes the repo to be lfs enabled and adds the following to the .git/config file: [lfs] repositoryformatversion = 0 That's surprising and a bit annoying. I also see those files listed and they don't exist in the current checkout. Digging further the following commit introduced lfs files: commit c94e4ced329298efb06189d1c6db26e3d6ff3eef Author: Vladimir Druzenko Date: Fri Sep 13 15:54:52 2024 +0300 java/eclipse: fix build consumer devel/subversive, commit files ignored with .gitignore <...> This commit removed them, but they are still in history so anything that checks that the full history is intact is now broken: commit 3ec21e417cd5752c96b88587a5a605567ba5cd19 Author: Norbert Grundmann Date: Fri Sep 20 03:14:47 2024 +0300 java/eclipse: Remove unnecessary *.so files <...> -- Brooks From nobody Tue Oct 1 19:37:00 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 4XJ7Vn55cYz5YGh1 for ; Tue, 01 Oct 2024 19:37:05 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XJ7Vm4z4Jz4fLW for ; Tue, 1 Oct 2024 19:37:04 +0000 (UTC) (envelope-from shawn.webb@hardenedbsd.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=hardenedbsd.org header.s=google header.b=HuApnmX4; spf=pass (mx1.freebsd.org: domain of shawn.webb@hardenedbsd.org designates 2607:f8b0:4864:20::12d as permitted sender) smtp.mailfrom=shawn.webb@hardenedbsd.org; dmarc=none Received: by mail-il1-x12d.google.com with SMTP id e9e14a558f8ab-3a1a22a7fa6so657195ab.1 for ; Tue, 01 Oct 2024 12:37:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hardenedbsd.org; s=google; t=1727811422; x=1728416222; darn=freebsd.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=/sRjBahxWAgLpCJ1DVS4DdU604k/CQC5oXBH/CQB+Qg=; b=HuApnmX49ikppklRp+S9bqhIOfGChO4w3vHLW1gBRcNZhA8TaIp3fARhAEGBdBlWAz xbsSkR95Ma2ammdO3qOo2K2j3bYnNWrwWDISc8RkSLORfQ466IlYnX90CInUmNhsQLSg +F7+p3Ga6FMbbjRyuqIa+iord6bSQPXA9PYW0DhIcAwpDHLDF1UMWLilgm8wxJCN9cKS hgF1QuS0nklPKmNydWxtrr/bBMdnDExoaEWuYcgNvuQ6zMIv9gZe+z90hhwdLyU5ltzK 8FsOC2yWtNnCVaQQGVVk61XTVwZm47JjCcItUpvCsjFFbDGEhLyVICd4lZGUbHDaQWD0 cA3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727811422; x=1728416222; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=/sRjBahxWAgLpCJ1DVS4DdU604k/CQC5oXBH/CQB+Qg=; b=hBkawTK8UK3qNsdTuzAIGoLGg3D1NUgHPlj/jGbUZsrEBpXXZzyM31JzmuElVGkxmB YkpIGRoqqHoEmiS6NpGjocfUBXmdvAv6E6TKxgkKESdAXWaevlyJ3KjiDQOi4YE6GSWb IpDeY44ALakJ0u+y/Fd1ZHQedVjkTIKFTwOkbVq3JjI+h5rFD9GypkxOvJ3xh9EKRK7o dacFMbC7ZqsIMXwa6xby7i4oM2ZCjYD+8takx4COZSSOaPiRT/tTmPF6BoignZKgVOay G02hEeBdiTM+6yXeVTwjPD5lPUpgY7mBZaH2GZxc+Jk8GN2DouQTDgJoLTFLEF/WR3qP x8vg== X-Gm-Message-State: AOJu0Yyg9w9lYbI/+VPYSFz3uiIutPtmMjrxphLAIjFE6SphreGkL8E2 Wn6uJOqrrMliQReSC10Ic5scm2b4tCm0UqFWk/N8SEpAP/h0FNEUz0Il7j8Ea8dfKAHoQGhil1+ Z X-Google-Smtp-Source: AGHT+IFt6cd4oetlEBQO0zXmZyliEaexuvyGduhK/5P/BKlQjt3gdwooQABlEb/jujJzxkFF5cZIHw== X-Received: by 2002:a05:6e02:1d9e:b0:3a1:95d9:6f36 with SMTP id e9e14a558f8ab-3a35eb792admr29206115ab.13.1727811422190; Tue, 01 Oct 2024 12:37:02 -0700 (PDT) Received: from mutt-hbsd (174-24-73-190.clsp.qwest.net. [174.24.73.190]) by smtp.gmail.com with ESMTPSA id 8926c6da1cb9f-4d9ec44bb94sm1128067173.80.2024.10.01.12.37.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 01 Oct 2024 12:37:00 -0700 (PDT) Date: Tue, 1 Oct 2024 19:37:00 +0000 From: Shawn Webb To: Matthias Fechner Cc: git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: <736exensjgsyhbytunglk6qnk3dh4fyyvdc5jktzrv3zzujbgr@db6amzcu53h2> X-Operating-System: FreeBSD mutt-hbsd 15.0-CURRENT-HBSD FreeBSD 15.0-CURRENT-HBSD X-PGP-Key: https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/blob/master/Shawn_Webb/03A4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> 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 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tuvb6m3a4xuc22d3" Content-Disposition: inline In-Reply-To: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> X-Spamd-Result: default: False [-5.10 / 15.00]; SIGNED_PGP(-2.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.999]; MID_RHS_NOT_FQDN(0.50)[]; R_DKIM_ALLOW(-0.20)[hardenedbsd.org:s=google]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.20)[multipart/signed,text/plain]; RCVD_VIA_SMTP_AUTH(0.00)[]; ARC_NA(0.00)[]; TO_DN_SOME(0.00)[]; MISSING_XM_UA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MIME_TRACE(0.00)[0:+,1:+,2:~]; DMARC_NA(0.00)[hardenedbsd.org]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_TWO(0.00)[2]; RCVD_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::12d:from]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_TLS_LAST(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[git@freebsd.org]; MLMMJ_DEST(0.00)[git@freebsd.org]; DKIM_TRACE(0.00)[hardenedbsd.org:+] X-Rspamd-Queue-Id: 4XJ7Vm4z4Jz4fLW X-Spamd-Bar: ----- --tuvb6m3a4xuc22d3 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Sep 30, 2024 at 01:09:32PM UTC, Matthias Fechner wrote: > Dear all, >=20 > I already tried to address that problem on the all-developer list, but it= is > maybe better to put it here. > I think by accident someone pushed LFS object with a commit of java/eclip= se. >=20 > git remote -v > freebsd git@gitrepo.freebsd.org:ports.git (fetch) > freebsd git@gitrepo.freebsd.org:ports.git (push) > freebsd-https=A0=A0 https://git.freebsd.org/ports.git (fetch) > freebsd-https=A0=A0 https://git.freebsd.org/ports.git (push) > githubfreebsd=A0=A0 https://github.com/freebsd/freebsd-ports.git (fetch) > githubfreebsd=A0=A0 https://github.com/freebsd/freebsd-ports.git (push) > origin=A0 git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) > origin=A0 git@gitlab.fechner.net:mfechner/Gitlab.git (push) >=20 > git lfs fetch --all freebsd > fetch: 22 object(s) found, done. > fetch: Fetching all references... > [99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d] Object > does not exist on the server: [404] Object does not exist on the server > [c89e491472c8af1d153e2e2801836fad0e38f428d0250ed982e16baa5effbe4f] Object > does not exist on the server: [404] Object does not exist on the server > [f7db6794c6c3e7a03a3987537b8a0cdb1bde2996ed7c7eec50f2e5df1e7a30c2] Object > does not exist on the server: [404] Object does not exist on the server > [e8e2d306fd11358a07b4ee10bfef19de3b518793568fc498cdd989170d31712b] Object > does not exist on the server: [404] Object does not exist on the server > [5dbe70b5c83520df09c100815bb164c8903da5eb8bffbd094aaaed54b212d73a] Object > does not exist on the server: [404] Object does not exist on the server > [8813907b0f7b001080a346ed2d0307a1c749b85688fdfa1d270fe59a07aa3909] Object > does not exist on the server: [404] Object does not exist on the server > [1d41b04bdd4115c52aac8177e1b899403a3d7d9f6d147cd864463029648a4714] Object > does not exist on the server: [404] Object does not exist on the server > [c0155fc8e7c4b9736d81db638fed95bc9ff297453bfd0bbd7dd5d882ebca6e89] Object > does not exist on the server: [404] Object does not exist on the server > [6d0aef4ba9e96d4c63baae8db9cdce7c634140a2bda7da670e698e38e0df57ce] Object > does not exist on the server: [404] Object does not exist on the server > [a928176ec92ad347404b2454e5f4f321aaef8ba862a60b0c28adc3bdcc619a4a] Object > does not exist on the server: [404] Object does not exist on the server > [42fa73302624dc511e6d8958c66c82f31b8d9155f2980343b6bcdc25345e1dcd] Object > does not exist on the server: [404] Object does not exist on the server > [ed324ddc16ccb8b9fab3041da394b844166b6778c39cd12708bcade05b41c0da] Object > does not exist on the server: [404] Object does not exist on the server > [9ef847d4e699b5dbe49ac74ee35596fdddc22c6335bc96affee19a99ecd077f5] Object > does not exist on the server: [404] Object does not exist on the server > [f5417c277c6ca509334010bb6999c56c3ab5d3751204c74dc00c2fa25d93dfae] Object > does not exist on the server: [404] Object does not exist on the server > [a1ffa591430df806983c8798113264f12ea679bce4b785d70d2868dc91cec883] Object > does not exist on the server: [404] Object does not exist on the server > [b2e525c38598dac6885a75e7eaffa346c8aca3dbdda73cb0275f50103ec3d245] Object > does not exist on the server: [404] Object does not exist on the server > [5db9424884396cf5bfc46a6b22dacbe245f43a7e1eda6aeac831905dc921802e] Object > does not exist on the server: [404] Object does not exist on the server > [b5e05ef77effb4048e72e38605700151fdf4eae214cfa358e9e81a48e124cb52] Object > does not exist on the server: [404] Object does not exist on the server > [ca2c21bf21e1fa2f53c72653ea57e76506c305bdd44c6416542ebbf2ab8b1b83] Object > does not exist on the server: [404] Object does not exist on the server > [4fc786126dd64f936554a12c4752787c4989453654fc5d6fd119b6e5eeafec6f] Object > does not exist on the server: [404] Object does not exist on the server > [f56db5e81304e441260b84d6c2805ae7050ea56760d763d2b32e6be928fa1cae] Object > does not exist on the server: [404] Object does not exist on the server > error: failed to fetch some objects from > 'https://github.com/freebsd/freebsd-ports.git/info/lfs' >=20 > I have my own testing pipeline in place to automatically test my commits > against changes I did to ports. >=20 > But as LFS is now in the FreeBSD repository, but the files cannot be > retrieved from the FreeBSD repository I'm now locked out for my CI/CD > pipeline and my automated tests. >=20 > If I now try to push to my local repo I get: >=20 > git push origin > Warning: untrusted X11 forwarding setup failed: xauth key data not genera= ted > Locking support detected on remote "origin". Consider enabling it with: > =A0 $ git config > lfs.https://gitlab.fechner.net/mfechner/Gitlab.git/info/lfs.locksverify t= rue > Unable to find source for object > 99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d (try > running git lfs fetch --all) > Uploading LFS objects:=A0=A0 0% (0/21), 0 B | 0 B/s, done. > error: failed to push some refs to 'gitlab.fechner.net:mfechner/Gitlab.gi= t' >=20 > Does anyone have an idea how that can be fixed? Hey Matthias, With commit c94e4ced329298efb06189d1c6db26e3d6ff3eef[1], FreeBSD introduced LFS objects into the ports git history. This commit was reverted with commit 3ec21e417cd5752c96b88587a5a605567ba5cd19[2]. Even though the offending commit was reverted, the git commit history still contains LFS references. This caused HardenedBSD's self-hosted GitLab to become unhappy in exactly the same way yours did. I ended up disabling LFS for the ports repo in the GitLab side. This caused GitLab to become happy again. Problem is, now everyone downstream from us (and FreeBSD, too) will need to disable LFS on their repos/forks, too. [1]: https://cgit.freebsd.org/ports/commit/?id=3Dc94e4ced329298efb06189d1c6= db26e3d6ff3eef [2]: https://cgit.freebsd.org/ports/commit/?id=3D3ec21e417cd5752c96b88587a5= a605567ba5cd19 Thanks, --=20 Shawn Webb Cofounder / Security Engineer HardenedBSD Tor-ified Signal: +1 303-901-1600 / shawn_webb_opsec.50 https://git.hardenedbsd.org/hardenedbsd/pubkeys/-/raw/master/Shawn_Webb/03A= 4CBEBB82EA5A67D9F3853FF2E67A277F8E1FA.pub.asc --tuvb6m3a4xuc22d3 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEA6TL67gupaZ9nzhT/y5nonf44foFAmb8T1UACgkQ/y5nonf4 4foUPBAAhKvZzB7YiQHkDn0uenU/JetWu1K5jzjaY+onTvH11sPm23nzPfTrBdiB A94j3iwYlHqPrLznBUeFFDISZsBJpUcfInpCcU0cSLuNZqZXwK/xWnDAZsSvK0US LJoNxOQiWEM8HnNHMresHSbH+M3UK5rFoLktYnZDPTGTYd0uDH8HURnX1ebk+ii0 VuD6f0D+lM+UV3+7wNvqzTRsqkioNnJ/ag8a0IP5fQFQNmNsvg50Wb2CfV4FPtWh rFqagng7qy0t0x40m4oXsHQRzMUvcrGYFSUWRmQT0BROmQYHDFuwU4XFHb8qU0GJ jzVD2EoumKUj2osgnVNLaTTr3Did9gpIjQHXCCoscmf9EGPPGV3L7efEHBTL5I7t X3Sa/txW3Y/0nbG4V9fpWC46Np/e1cFWpMbZrU1YbTEBrx2cs7PfjYhzCPQ2djfj npbOLSQ/LuWIStbeGwheFP0+UsPMVOtnWa16SeHKiossbEKNXxe7CaZgBgZqzSrA rTsX5I0D3QEs/8kz8zQb7IOsKUJ7MUXSl3cXZC8FPVFOa4Hnzc+C3xz8C6y5GSfq ve/zV+RXgAWEM7C4rUTqmdhr15CopdpfCiDcLVWsa4+YjXD0rcI1cgxzdr2vW19U 58vm5/Bf1388Goy62VnQ2YOiXVjljf2IQjxlc5P0AOI3V7Ss9XQ= =PLn6 -----END PGP SIGNATURE----- --tuvb6m3a4xuc22d3-- From nobody Tue Oct 1 19:37:45 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 4XJ7WZ0W8Mz5YGpx for ; Tue, 01 Oct 2024 19:37:46 +0000 (UTC) (envelope-from brooks@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 4XJ7WY75LVz4ffs; Tue, 1 Oct 2024 19:37:45 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727811466; 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: in-reply-to:in-reply-to:references:references; bh=uOVOY1q7szr1LdBnzun7R/djcEVskg92OGj95atckMM=; b=fxngKCgV+HHhVnsmuLXJxyb0rGdIje35q0PJ/PH/P75ng1MH5jgFKJrbUvDIvOLgJFWtCb Fy1ySVE7iKs6hAoBig6ApDkdLfhVq482inKOD1C44TXMSFZCGWg6cnk5huW8xPHsY8FVzY p60jEUlH6tEEtQ1l0D0IcAOK4cfdf2akrUZS5bsmgOGaFm92g3Ivq9w3gi1viKaslLfDFH A8cpF/nyVjiCcaxIzNN3wuX1aEstsLYhT7tSQRusPxM4UXVPmwGCI2fhb6DpOJ5vFujdVE eyOq+ay9tFUfd4twGr6y157I81JKh225NbuPX0SL3q6ZTcymGQgnGweAceNzsA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727811466; 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: in-reply-to:in-reply-to:references:references; bh=uOVOY1q7szr1LdBnzun7R/djcEVskg92OGj95atckMM=; b=J/P6slqto5kD5wHbya+Y04hHAsqDzS8Yg1PUpHVCmUJIrGcnfBULlM9YMQCvve2N1xq3XR ebH5f5uYea337RmWdPCkdbjsfqLXXL2IffRGbkwb0Ygd8rvG+m3vuhTFv4f8s7tKuUs8Xf cc3sKIXZorWaol2I+YAkyRnBRngGIvxomSnVjCVjTQYuTw980Qq63IT65tumKVW0Hz/A+a kPr2RqlxkzfGYJWDyXsvLsxVJ0MDb2lnwu2mIEXMW6ZjnMbITSUo13fN/p76QGRwCCYTzN MqF1AEAB/vXin/5FCctcAbGXDkpZwv8Hl+Pko/u+Y57VK3WwucIDjdwincPUOw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727811466; a=rsa-sha256; cv=none; b=lPP5CgsewfZJPMDxHg6c39Z0W00q9ns9oHeXPByNtIOP/RE38DGQudIjliCt7VxQ1FJlmQ LaeKwKvufgbCiKy1YOMqzF6sRE3WK1OVfd2e4lzVt5WtjsGWciLh55oJ1j6g40bq9Ji29V c0omXx3bcuDv4rslk4rPKIv+Ii2uGqLdqwMJG7gRfMrddusLtUgoYo9lKH72Y7XPrh7Ogt 0nCHSSCNin1Un8sEEsHS1Nk6opSHDr+dhouysljseJR3gPL4okfQE6SqoRqPl2chvjagZj ywD8TX1Po0wExlBk7bSWtN0nyPsZh88f20/bHxxRTrtG0V/yE8CDoMyaZOFl6A== Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: brooks/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XJ7WY6ZKwz1CZL; Tue, 1 Oct 2024 19:37:45 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id 9C5543C019B; Tue, 01 Oct 2024 19:37:45 +0000 (UTC) Date: Tue, 1 Oct 2024 19:37:45 +0000 From: Brooks Davis To: Matthias Fechner Cc: Dave Cottlehuber , git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Tue, Oct 01, 2024 at 07:04:17PM +0000, Brooks Davis wrote: > On Tue, Oct 01, 2024 at 12:00:30PM +0300, Matthias Fechner wrote: > > 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 > ... > > > > > > > > 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... > > Hmm, this is quite bizzare. It looks like running `git lfs ls-files --all` > causes the repo to be lfs enabled and adds the following to the > .git/config file: > > [lfs] > repositoryformatversion = 0 > > That's surprising and a bit annoying. > > I also see those files listed and they don't exist in the current > checkout. > > Digging further the following commit introduced lfs files: > > commit c94e4ced329298efb06189d1c6db26e3d6ff3eef > Author: Vladimir Druzenko > Date: Fri Sep 13 15:54:52 2024 +0300 > > java/eclipse: fix build consumer devel/subversive, commit files > ignored with .gitignore > <...> > > > This commit removed them, but they are still in history so anything that > checks that the full history is intact is now broken: > > commit 3ec21e417cd5752c96b88587a5a605567ba5cd19 > Author: Norbert Grundmann > Date: Fri Sep 20 03:14:47 2024 +0300 > > java/eclipse: Remove unnecessary *.so files > <...> I've done some searching at it looks like there are gitlab options to disable the various checks. I don't admin any gitlab instances so don't know how to translate this into something you can use, but: https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/lib/gitlab/checks/lfs_check.rb?ref_type=heads seems to show an lfs_check.objects_missing knob to disable the precommit check. You might also need to disable some lfs integrity checks. -- Brooks From nobody Wed Oct 2 15:26:13 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 4XJdtt5jz1z5Xglk for ; Wed, 02 Oct 2024 15:26:14 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4XJdtt58Bgz3wsB; Wed, 2 Oct 2024 15:26:14 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727882774; 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: in-reply-to:in-reply-to:references:references; bh=Y6I8YIlL4xtyBl6v2yekGPw0Dd9VUy+ZNUtN81Y7q0E=; b=PmNHcXggNRVcC0J3VJ91YiILCJUrI1W2xizEuop24MF6UizBfMTmbpiL+TD1/hYjr5pi3B zRopdM2raxE9VvQ+yjd/uc5aSJBCNyHTBcO6sBnB6ClhkGjvt6bXfYxVa9Kxht58Db6Xz+ CViJYYffJLsm2VDayBj5mGiak2AMPZX+m+Aom7InOpI1B7VwBXzLLniN8QoG8bf5qx3hFW NA89wbk0ipjUQLXrFdAtJSZM1WR7xWT5M1aIfrqvoIp7zkaPpM+cFceyZGjwIfM0cqZicm IBBGSryNpPij+nZy9UkHFmPYC8faQWlicEOwiJ6eE6N8ZFBicOfjDLJGhRvnbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727882774; 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: in-reply-to:in-reply-to:references:references; bh=Y6I8YIlL4xtyBl6v2yekGPw0Dd9VUy+ZNUtN81Y7q0E=; b=pD4Nl6kpRd3rVIXurlGGMchlw0HIvkKy5DDjMpt4P1CgyNy2YCc2TRZZSQ/J/VivsX52zH gl7LdMAPDrB3loxg9S7HQRrweYCBCR6ljBTUCuaXJtSi4pK9+miuh+BkNaPrMMG3vnqtKT Vv8nwZiyWUJDnnATLkzbdmoIR3eHmadxPjQ1veJ6v7/DDcB2NeeJdtRvnTW2C+9HeM/DgW Vsp/j/Zmg0A//HZdJgyXESk7L86Y/eEJSe+47HhpEzYr9C6awYdrL5eSlQb2kVVALrwLnK vwT9AsAUga2TqB2IPfYrBtPGAzCkwG9FPHpeOARM0WI+JC3H7Q39jszvjZVPPg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727882774; a=rsa-sha256; cv=none; b=aU8OyHRU17BZ0YrokVNXAmalKGLxmoPh6A/sltSGiPpZer2src0NaVPo8q4kBuDSbFp3Z0 9QmHTO8IxaP6RfCp+jWSh5fA0HDKeQUCuWOKTzbJ8vyFzWJZvmG1XRynyCXJ9JgfsLEe6B UAyt/+KSbZCtivVwQT84FBAgOGAADN5EgOqMOi0hkuPGgLsa1nWnkhcI7LFWHad6j4htMy o+czYTsnbn63SwCHkKSPG/G++xOhLRG/Ee+i9VXBrm5Ul24S1zJsfLcOZsOxf8+6B9AIM0 /PHS6gPNBgYLnR8cuadzxVU7UGdiDjOUsHcOIj0OrH6/FvhTSmLUbcY16TvvYw== Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (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) (Authenticated sender: brooks/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XJdtt4YBszNnq; Wed, 2 Oct 2024 15:26:14 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id EAB6D3C019B; Wed, 02 Oct 2024 15:26:13 +0000 (UTC) Date: Wed, 2 Oct 2024 15:26:13 +0000 From: Brooks Davis To: Shawn Webb Cc: Matthias Fechner , git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> <736exensjgsyhbytunglk6qnk3dh4fyyvdc5jktzrv3zzujbgr@db6amzcu53h2> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <736exensjgsyhbytunglk6qnk3dh4fyyvdc5jktzrv3zzujbgr@db6amzcu53h2> On Tue, Oct 01, 2024 at 07:37:00PM +0000, Shawn Webb wrote: > On Mon, Sep 30, 2024 at 01:09:32PM UTC, Matthias Fechner wrote: > > Dear all, > > > > I already tried to address that problem on the all-developer list, but it is > > maybe better to put it here. > > I think by accident someone pushed LFS object with a commit of java/eclipse. > > > > git remote -v > > freebsd git@gitrepo.freebsd.org:ports.git (fetch) > > freebsd git@gitrepo.freebsd.org:ports.git (push) > > freebsd-https?? https://git.freebsd.org/ports.git (fetch) > > freebsd-https?? https://git.freebsd.org/ports.git (push) > > githubfreebsd?? https://github.com/freebsd/freebsd-ports.git (fetch) > > githubfreebsd?? https://github.com/freebsd/freebsd-ports.git (push) > > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) > > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (push) > > > > git lfs fetch --all freebsd > > fetch: 22 object(s) found, done. > > fetch: Fetching all references... > > [99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d] Object > > does not exist on the server: [404] Object does not exist on the server > > [c89e491472c8af1d153e2e2801836fad0e38f428d0250ed982e16baa5effbe4f] Object > > does not exist on the server: [404] Object does not exist on the server > > [f7db6794c6c3e7a03a3987537b8a0cdb1bde2996ed7c7eec50f2e5df1e7a30c2] Object > > does not exist on the server: [404] Object does not exist on the server > > [e8e2d306fd11358a07b4ee10bfef19de3b518793568fc498cdd989170d31712b] Object > > does not exist on the server: [404] Object does not exist on the server > > [5dbe70b5c83520df09c100815bb164c8903da5eb8bffbd094aaaed54b212d73a] Object > > does not exist on the server: [404] Object does not exist on the server > > [8813907b0f7b001080a346ed2d0307a1c749b85688fdfa1d270fe59a07aa3909] Object > > does not exist on the server: [404] Object does not exist on the server > > [1d41b04bdd4115c52aac8177e1b899403a3d7d9f6d147cd864463029648a4714] Object > > does not exist on the server: [404] Object does not exist on the server > > [c0155fc8e7c4b9736d81db638fed95bc9ff297453bfd0bbd7dd5d882ebca6e89] Object > > does not exist on the server: [404] Object does not exist on the server > > [6d0aef4ba9e96d4c63baae8db9cdce7c634140a2bda7da670e698e38e0df57ce] Object > > does not exist on the server: [404] Object does not exist on the server > > [a928176ec92ad347404b2454e5f4f321aaef8ba862a60b0c28adc3bdcc619a4a] Object > > does not exist on the server: [404] Object does not exist on the server > > [42fa73302624dc511e6d8958c66c82f31b8d9155f2980343b6bcdc25345e1dcd] Object > > does not exist on the server: [404] Object does not exist on the server > > [ed324ddc16ccb8b9fab3041da394b844166b6778c39cd12708bcade05b41c0da] Object > > does not exist on the server: [404] Object does not exist on the server > > [9ef847d4e699b5dbe49ac74ee35596fdddc22c6335bc96affee19a99ecd077f5] Object > > does not exist on the server: [404] Object does not exist on the server > > [f5417c277c6ca509334010bb6999c56c3ab5d3751204c74dc00c2fa25d93dfae] Object > > does not exist on the server: [404] Object does not exist on the server > > [a1ffa591430df806983c8798113264f12ea679bce4b785d70d2868dc91cec883] Object > > does not exist on the server: [404] Object does not exist on the server > > [b2e525c38598dac6885a75e7eaffa346c8aca3dbdda73cb0275f50103ec3d245] Object > > does not exist on the server: [404] Object does not exist on the server > > [5db9424884396cf5bfc46a6b22dacbe245f43a7e1eda6aeac831905dc921802e] Object > > does not exist on the server: [404] Object does not exist on the server > > [b5e05ef77effb4048e72e38605700151fdf4eae214cfa358e9e81a48e124cb52] Object > > does not exist on the server: [404] Object does not exist on the server > > [ca2c21bf21e1fa2f53c72653ea57e76506c305bdd44c6416542ebbf2ab8b1b83] Object > > does not exist on the server: [404] Object does not exist on the server > > [4fc786126dd64f936554a12c4752787c4989453654fc5d6fd119b6e5eeafec6f] Object > > does not exist on the server: [404] Object does not exist on the server > > [f56db5e81304e441260b84d6c2805ae7050ea56760d763d2b32e6be928fa1cae] Object > > does not exist on the server: [404] Object does not exist on the server > > error: failed to fetch some objects from > > 'https://github.com/freebsd/freebsd-ports.git/info/lfs' > > > > I have my own testing pipeline in place to automatically test my commits > > against changes I did to ports. > > > > But as LFS is now in the FreeBSD repository, but the files cannot be > > retrieved from the FreeBSD repository I'm now locked out for my CI/CD > > pipeline and my automated tests. > > > > 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 > > running git lfs fetch --all) > > Uploading LFS objects:?? 0% (0/21), 0 B | 0 B/s, done. > > error: failed to push some refs to 'gitlab.fechner.net:mfechner/Gitlab.git' > > > > Does anyone have an idea how that can be fixed? > > Hey Matthias, > > With commit c94e4ced329298efb06189d1c6db26e3d6ff3eef[1], FreeBSD > introduced LFS objects into the ports git history. This commit was > reverted with commit 3ec21e417cd5752c96b88587a5a605567ba5cd19[2]. > > Even though the offending commit was reverted, the git commit history > still contains LFS references. This caused HardenedBSD's self-hosted > GitLab to become unhappy in exactly the same way yours did. > > I ended up disabling LFS for the ports repo in the GitLab side. This > caused GitLab to become happy again. Problem is, now everyone > downstream from us (and FreeBSD, too) will need to disable LFS on > their repos/forks, too. I'm curious if you can turn LFS back on once the broken change is past? That that ports should ever use LFS, but it seems somewhat better if GitLab configs only need to be non-default during bootstrapping. At this point there's probably nothing to be done other than workarounds as rewriting history to remove this stuff would be quite disruptive after several weeks of commits. We could really use some hooks to block both things that look like lfs metadata and submodule bits. (The latter is somewhat challenging in that we need to allow them on the vendor side to support OpenZFS.) -- Brooks From nobody Wed Oct 2 15:29:00 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 4XJdyK4YMKz5Xgdr for ; Wed, 02 Oct 2024 15:29:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pl1-x62b.google.com (mail-pl1-x62b.google.com [IPv6:2607:f8b0:4864:20::62b]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XJdyK2QQjz3wsy for ; Wed, 2 Oct 2024 15:29:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-20ba9f3824fso19126715ad.0 for ; Wed, 02 Oct 2024 08:29:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1727882952; x=1728487752; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qYoQD0VNoLO0Dphsu7TJXsuUUDCPeRwKi+c68LT9hHw=; b=Cj/nQAgQ8yN1edU4KU1s64EjORy8K+mrDvRNfSATo3+al8GsD/4Oq39RcZ3x879wSg roYZVHgarD9FxCJdxXufNjrHoeeR0sd9hUBP3LV9VF2xI0s61PPvJX/kyTd+QhJNTSTI Kyj8FTUQoYzPvsRZuDJ7T3mdre50UfeQ8YfN3RjVs8dUgaT767LYSNsXPwROPJgfJAib yTE8UOkWVJqBft0ikr8nfV4BoOkNrS2ngI8nr4UI1JuIUVTvClCpEvbqm9WlwxeqzsiM E0vQxlKI62xXetJ5ZfoKxxxVN44iVviQy4GiwK+OT8LsipDB4V+O/JqNyicdtM06csjn ID4Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727882952; x=1728487752; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qYoQD0VNoLO0Dphsu7TJXsuUUDCPeRwKi+c68LT9hHw=; b=ijAUKyLeMS+GI5VNhkbsCAbzlk5RRCKarhkn4qTGyX/Kr+WmkVO+N1R31sOM/TC0RW rGVD8gKeYlH5CozqpqUlVw4AwYv3RVHTqOGK3d3Cr8jd1u4YyUL1qUfPJM30r7jhYBNx k/H59labOP99nkgI4biR7UBcOFfaTEFcF7bn7onM2tdcD8Fo/iqjGgB2f8ZDDDHSpThs zRobCMMcrlbEx3CXaCNuHI/bfWu6nqw/0E0J0cAeHnh00ko32GGhrN3cFxX0tq0F2nnE uHIn9UHWqm1EZ8wW1quryli5K7M9Px+xCR0iOEIHKBt+zSohiYzUiVgu6qTVjy78lEXu hxAw== X-Forwarded-Encrypted: i=1; AJvYcCW4NS05hhqXWDIo4Dxe75UT0KGmsaFW91xFHJA63yYzPW8Qu3WMn5jGWIGwKQsSb7Jj9hw=@freebsd.org X-Gm-Message-State: AOJu0Yznj3w3Pg3vCYv+2sPEioRNnblWffMR8OszRzPFNHUKq6dKfnIx HgXpfjvFXhnWShZGrBgKvLm2Wa6QbPKyI0aper3KOThQAGroR26etKVubYcUY9wQG9iF6EC/pcK 1VPUCnX8h3LuyWa806SAoOhi0A/MqKx4q21fYGA== X-Google-Smtp-Source: AGHT+IF7J7UCHxdpLSjDDO6PVp4IncyMxHY+l7Vd8+J1QJ0UnckzWVmJ9Azkg0tfQLbB5hpdaCMeDS/m/+5YVTbbFZY= X-Received: by 2002:a17:90b:3444:b0:2d3:d728:6ebb with SMTP id 98e67ed59e1d1-2e18451dc60mr4658862a91.5.1727882951867; Wed, 02 Oct 2024 08:29:11 -0700 (PDT) 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 References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> <736exensjgsyhbytunglk6qnk3dh4fyyvdc5jktzrv3zzujbgr@db6amzcu53h2> In-Reply-To: From: Warner Losh Date: Wed, 2 Oct 2024 09:29:00 -0600 Message-ID: Subject: Re: Impossible to push my ports directory to my CI/CD pipeline To: Brooks Davis Cc: Shawn Webb , Matthias Fechner , git@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008f88d70623801996" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XJdyK2QQjz3wsy X-Spamd-Bar: ---- --0000000000008f88d70623801996 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 2, 2024, 9:26=E2=80=AFAM Brooks Davis wrot= e: > On Tue, Oct 01, 2024 at 07:37:00PM +0000, Shawn Webb wrote: > > On Mon, Sep 30, 2024 at 01:09:32PM UTC, Matthias Fechner wrote: > > > Dear all, > > > > > > I already tried to address that problem on the all-developer list, bu= t > it is > > > maybe better to put it here. > > > I think by accident someone pushed LFS object with a commit of > java/eclipse. > > > > > > git remote -v > > > freebsd git@gitrepo.freebsd.org:ports.git (fetch) > > > freebsd git@gitrepo.freebsd.org:ports.git (push) > > > freebsd-https?? https://git.freebsd.org/ports.git (fetch) > > > freebsd-https?? https://git.freebsd.org/ports.git (push) > > > githubfreebsd?? https://github.com/freebsd/freebsd-ports.git (fetch) > > > githubfreebsd?? https://github.com/freebsd/freebsd-ports.git (push) > > > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) > > > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (push) > > > > > > git lfs fetch --all freebsd > > > fetch: 22 object(s) found, done. > > > fetch: Fetching all references... > > > [99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [c89e491472c8af1d153e2e2801836fad0e38f428d0250ed982e16baa5effbe4f] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [f7db6794c6c3e7a03a3987537b8a0cdb1bde2996ed7c7eec50f2e5df1e7a30c2] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [e8e2d306fd11358a07b4ee10bfef19de3b518793568fc498cdd989170d31712b] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [5dbe70b5c83520df09c100815bb164c8903da5eb8bffbd094aaaed54b212d73a] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [8813907b0f7b001080a346ed2d0307a1c749b85688fdfa1d270fe59a07aa3909] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [1d41b04bdd4115c52aac8177e1b899403a3d7d9f6d147cd864463029648a4714] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [c0155fc8e7c4b9736d81db638fed95bc9ff297453bfd0bbd7dd5d882ebca6e89] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [6d0aef4ba9e96d4c63baae8db9cdce7c634140a2bda7da670e698e38e0df57ce] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [a928176ec92ad347404b2454e5f4f321aaef8ba862a60b0c28adc3bdcc619a4a] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [42fa73302624dc511e6d8958c66c82f31b8d9155f2980343b6bcdc25345e1dcd] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [ed324ddc16ccb8b9fab3041da394b844166b6778c39cd12708bcade05b41c0da] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [9ef847d4e699b5dbe49ac74ee35596fdddc22c6335bc96affee19a99ecd077f5] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [f5417c277c6ca509334010bb6999c56c3ab5d3751204c74dc00c2fa25d93dfae] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [a1ffa591430df806983c8798113264f12ea679bce4b785d70d2868dc91cec883] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [b2e525c38598dac6885a75e7eaffa346c8aca3dbdda73cb0275f50103ec3d245] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [5db9424884396cf5bfc46a6b22dacbe245f43a7e1eda6aeac831905dc921802e] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [b5e05ef77effb4048e72e38605700151fdf4eae214cfa358e9e81a48e124cb52] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [ca2c21bf21e1fa2f53c72653ea57e76506c305bdd44c6416542ebbf2ab8b1b83] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [4fc786126dd64f936554a12c4752787c4989453654fc5d6fd119b6e5eeafec6f] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > [f56db5e81304e441260b84d6c2805ae7050ea56760d763d2b32e6be928fa1cae] > Object > > > does not exist on the server: [404] Object does not exist on the serv= er > > > error: failed to fetch some objects from > > > 'https://github.com/freebsd/freebsd-ports.git/info/lfs' > > > > > > I have my own testing pipeline in place to automatically test my > commits > > > against changes I did to ports. > > > > > > But as LFS is now in the FreeBSD repository, but the files cannot be > > > retrieved from the FreeBSD repository I'm now locked out for my CI/CD > > > pipeline and my automated tests. > > > > > > 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 wit= h: > > > ? $ git config > > > lfs. > https://gitlab.fechner.net/mfechner/Gitlab.git/info/lfs.locksverify true > > > Unable to find source for object > > > 99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d (try > > > running git lfs fetch --all) > > > Uploading LFS objects:?? 0% (0/21), 0 B | 0 B/s, done. > > > error: failed to push some refs to 'gitlab.fechner.net: > mfechner/Gitlab.git' > > > > > > Does anyone have an idea how that can be fixed? > > > > Hey Matthias, > > > > With commit c94e4ced329298efb06189d1c6db26e3d6ff3eef[1], FreeBSD > > introduced LFS objects into the ports git history. This commit was > > reverted with commit 3ec21e417cd5752c96b88587a5a605567ba5cd19[2]. > > > > Even though the offending commit was reverted, the git commit history > > still contains LFS references. This caused HardenedBSD's self-hosted > > GitLab to become unhappy in exactly the same way yours did. > > > > I ended up disabling LFS for the ports repo in the GitLab side. This > > caused GitLab to become happy again. Problem is, now everyone > > downstream from us (and FreeBSD, too) will need to disable LFS on > > their repos/forks, too. > > I'm curious if you can turn LFS back on once the broken change is past? > That that ports should ever use LFS, but it seems somewhat better if > GitLab configs only need to be non-default during bootstrapping. > > At this point there's probably nothing to be done other than workarounds > as rewriting history to remove this stuff would be quite disruptive > after several weeks of commits. > > We could really use some hooks to block both things that look like lfs > metadata and submodule bits. (The latter is somewhat challenging in that > we need to allow them on the vendor side to support OpenZFS.) > I didn't think we imported the submodules of OpenZFS to the vendor branch, except to the extent that data was plain files in that import not otherwise used... Warner > > --0000000000008f88d70623801996 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, Oct 2, 2024, 9:26=E2=80=AFAM Brooks Davis <= brooks@freebsd.org> wrote:
=
On Tue, Oct 01, 2024 at 07:37:00PM +00= 00, Shawn Webb wrote:
> On Mon, Sep 30, 2024 at 01:09:32PM UTC, Matthias Fechner wrote:
> > Dear all,
> >
> > I already tried to address that problem on the all-developer list= , but it is
> > maybe better to put it here.
> > I think by accident someone pushed LFS object with a commit of ja= va/eclipse.
> >
> > git remote -v
> > freebsd git@gitrepo.freebsd.org:ports.git (fetch)
> > freebsd git@gitrepo.freebsd.org:ports.git (push)
> > freebsd-https?? https://git.freebsd.org/ports.= git (fetch)
> > freebsd-https?? https://git.freebsd.org/ports.= git (push)
> > githubfreebsd?? https://github.com/= freebsd/freebsd-ports.git (fetch)
> > githubfreebsd?? https://github.com/= freebsd/freebsd-ports.git (push)
> > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (fetch)
> > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (push)
> >
> > git lfs fetch --all freebsd
> > fetch: 22 object(s) found, done.
> > fetch: Fetching all references...
> > [99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [c89e491472c8af1d153e2e2801836fad0e38f428d0250ed982e16baa5effbe4f= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [f7db6794c6c3e7a03a3987537b8a0cdb1bde2996ed7c7eec50f2e5df1e7a30c2= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [e8e2d306fd11358a07b4ee10bfef19de3b518793568fc498cdd989170d31712b= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [5dbe70b5c83520df09c100815bb164c8903da5eb8bffbd094aaaed54b212d73a= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [8813907b0f7b001080a346ed2d0307a1c749b85688fdfa1d270fe59a07aa3909= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [1d41b04bdd4115c52aac8177e1b899403a3d7d9f6d147cd864463029648a4714= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [c0155fc8e7c4b9736d81db638fed95bc9ff297453bfd0bbd7dd5d882ebca6e89= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [6d0aef4ba9e96d4c63baae8db9cdce7c634140a2bda7da670e698e38e0df57ce= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [a928176ec92ad347404b2454e5f4f321aaef8ba862a60b0c28adc3bdcc619a4a= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [42fa73302624dc511e6d8958c66c82f31b8d9155f2980343b6bcdc25345e1dcd= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [ed324ddc16ccb8b9fab3041da394b844166b6778c39cd12708bcade05b41c0da= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [9ef847d4e699b5dbe49ac74ee35596fdddc22c6335bc96affee19a99ecd077f5= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [f5417c277c6ca509334010bb6999c56c3ab5d3751204c74dc00c2fa25d93dfae= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [a1ffa591430df806983c8798113264f12ea679bce4b785d70d2868dc91cec883= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [b2e525c38598dac6885a75e7eaffa346c8aca3dbdda73cb0275f50103ec3d245= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [5db9424884396cf5bfc46a6b22dacbe245f43a7e1eda6aeac831905dc921802e= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [b5e05ef77effb4048e72e38605700151fdf4eae214cfa358e9e81a48e124cb52= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [ca2c21bf21e1fa2f53c72653ea57e76506c305bdd44c6416542ebbf2ab8b1b83= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [4fc786126dd64f936554a12c4752787c4989453654fc5d6fd119b6e5eeafec6f= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > [f56db5e81304e441260b84d6c2805ae7050ea56760d763d2b32e6be928fa1cae= ] Object
> > does not exist on the server: [404] Object does not exist on the = server
> > error: failed to fetch some objects from
> > 'https://github.com/fr= eebsd/freebsd-ports.git/info/lfs'
> >
> > I have my own testing pipeline in place to automatically test my = commits
> > against changes I did to ports.
> >
> > But as LFS is now in the FreeBSD repository, but the files cannot= be
> > retrieved from the FreeBSD repository I'm now locked out for = my CI/CD
> > pipeline and my automated tests.
> >
> > If I now try to push to my local repo I get:
> >
> > git push origin
> > Warning: untrusted X11 forwarding setup failed: xauth key data no= t generated
> > Locking support detected on remote "origin". Consider e= nabling it with:
> > ? $ git config
> > lfs.https://= gitlab.fechner.net/mfechner/Gitlab.git/info/lfs.locksverify true
> > Unable to find source for object
> > 99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d = (try
> > running git lfs fetch --all)
> > Uploading LFS objects:?? 0% (0/21), 0 B | 0 B/s, done.
> > error: failed to push some refs to 'gitlab.fechner.net:mfechn= er/Gitlab.git'
> >
> > Does anyone have an idea how that can be fixed?
>
> Hey Matthias,
>
> With commit c94e4ced329298efb06189d1c6db26e3d6ff3eef[1], FreeBSD
> introduced LFS objects into the ports git history. This commit was
> reverted with commit 3ec21e417cd5752c96b88587a5a605567ba5cd19[2].
>
> Even though the offending commit was reverted, the git commit history<= br> > still contains LFS references. This caused HardenedBSD's self-host= ed
> GitLab to become unhappy in exactly the same way yours did.
>
> I ended up disabling LFS for the ports repo in the GitLab side. This > caused GitLab to become happy again. Problem is, now everyone
> downstream from us (and FreeBSD, too) will need to disable LFS on
> their repos/forks, too.

I'm curious if you can turn LFS back on once the broken change is past?=
That that ports should ever use LFS, but it seems somewhat better if
GitLab configs only need to be non-default during bootstrapping.

At this point there's probably nothing to be done other than workaround= s
as rewriting history to remove this stuff would be quite disruptive
after several weeks of commits.

We could really use some hooks to block both things that look like lfs
metadata and submodule bits.=C2=A0 (The latter is somewhat challenging in t= hat
we need to allow them on the vendor side to support OpenZFS.)

I didn't t= hink we imported the submodules of OpenZFS to the vendor branch, except to = the extent that data was plain files in that import not otherwise used...

Warner

--0000000000008f88d70623801996-- From nobody Wed Oct 2 15:33:09 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 4XJf2t30Pgz5Xh81 for ; Wed, 02 Oct 2024 15:33:10 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4XJf2t11q1z3xGt; Wed, 2 Oct 2024 15:33:10 +0000 (UTC) (envelope-from brooks@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727883190; 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: in-reply-to:in-reply-to:references:references; bh=bzt6AW+/FXipew3YekxYNm6Zy0jqWIllDkriWg50faE=; b=QQdImGZrjuYJgWpbc45jnlNj0E5WRFNbaaMUH8fcQD+S4jdtD7/tdkxmQDHg+nD5Y23cUH Nkth8t83Bpy/NExkzNJyicH3pHXdwda62cPHFeMXo5FhqvyGpp6nlVek5fnzf+0lSBA6ny etFjEmmC9Z0RbbAKRk3L1bc3oHn29W/82G5uTYVz59k3OcLUUeArZZ9paYBbh9LwJndZf0 lFQOi6eOX6Y4neXUko/oar1ssCCWUQTyxLNufSLqNoxTm6VB8/M6ByLqTLIegFq0CUnlrl vKmPZdRuPqG6KvV69FiM+SKqc14IELd74+44b7UlcQQQFKtWveYEBAJh9bsJog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727883190; 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: in-reply-to:in-reply-to:references:references; bh=bzt6AW+/FXipew3YekxYNm6Zy0jqWIllDkriWg50faE=; b=sLWFOBCNAJFI45nTTva8l8+K4ytS1U9sZ1N3+wXHwFwEJJBnZe6EEK7cfwaxShd765DXie mHnAja8WfkDlR3Acsly67j49lUpiE2MlL7o+p6VcOPNokmByl5Erwb6tO72ynBCdaNKc2C kQAsqQ3tZ7iLZk7HRWvG/edhxtrTVnE9QLKZxCKcCUyu/frD9/xjxRmlp1OX89bHEaOBKr G4SNi6pKYfKaV22z8tKucIWkgr0ed9+uJZej2ztIiY/UuXbUc4S+bH25Du6LVeTLZykmJ5 k3vrRV2zGELK/vGWRqDaQkJdLUl6QF7Yi2eiTYo4X1foxgzgE70DVa3NW+G88Q== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727883190; a=rsa-sha256; cv=none; b=XvMDT1PJU8nfDtWwN6JjOyZouqyTQth1v4m1DpGc5gV+KfTHVNwcvaqjNLkjYxrcQicvky j4z8DiC3LKqSNKAUHCWS0lax4H65Jpz1Gb3ys5MhXIiDBAuSvfYaTXSEOmBADwe8yqdehM Z6wIzj9GVM5rKhVKOIUjPya1VDBx2/5s7IBCpp2bQIUOXBFLdu0X98ZUYId0BPj74aru7J XpYSi/glNoqB8KfZQrMke+AEQ3tw/m9eEQDSQ1CzyF2LR5np0e7kczDB3PcBGVe38IZ6X5 +I5fvlWUVaDn3hvmMsBEQHXT9W8bopxF/Aj7kcZvi2FFCxOLvLOsVucaG48Zug== Received: from spindle.one-eyed-alien.net (spindle.one-eyed-alien.net [199.48.129.229]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: brooks/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4XJf2t072XzKbD; Wed, 2 Oct 2024 15:33:09 +0000 (UTC) (envelope-from brooks@freebsd.org) Received: by spindle.one-eyed-alien.net (Postfix, from userid 3001) id C195E3C019B; Wed, 02 Oct 2024 15:33:09 +0000 (UTC) Date: Wed, 2 Oct 2024 15:33:09 +0000 From: Brooks Davis To: Warner Losh Cc: Shawn Webb , Matthias Fechner , git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> <736exensjgsyhbytunglk6qnk3dh4fyyvdc5jktzrv3zzujbgr@db6amzcu53h2> 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 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: On Wed, Oct 02, 2024 at 09:29:00AM -0600, Warner Losh wrote: > On Wed, Oct 2, 2024, 9:26???AM Brooks Davis wrote: > > > On Tue, Oct 01, 2024 at 07:37:00PM +0000, Shawn Webb wrote: > > > On Mon, Sep 30, 2024 at 01:09:32PM UTC, Matthias Fechner wrote: > > > > Dear all, > > > > > > > > I already tried to address that problem on the all-developer list, but > > it is > > > > maybe better to put it here. > > > > I think by accident someone pushed LFS object with a commit of > > java/eclipse. > > > > > > > > git remote -v > > > > freebsd git@gitrepo.freebsd.org:ports.git (fetch) > > > > freebsd git@gitrepo.freebsd.org:ports.git (push) > > > > freebsd-https?? https://git.freebsd.org/ports.git (fetch) > > > > freebsd-https?? https://git.freebsd.org/ports.git (push) > > > > githubfreebsd?? https://github.com/freebsd/freebsd-ports.git (fetch) > > > > githubfreebsd?? https://github.com/freebsd/freebsd-ports.git (push) > > > > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) > > > > origin? git@gitlab.fechner.net:mfechner/Gitlab.git (push) > > > > > > > > git lfs fetch --all freebsd > > > > fetch: 22 object(s) found, done. > > > > fetch: Fetching all references... > > > > [99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [c89e491472c8af1d153e2e2801836fad0e38f428d0250ed982e16baa5effbe4f] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [f7db6794c6c3e7a03a3987537b8a0cdb1bde2996ed7c7eec50f2e5df1e7a30c2] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [e8e2d306fd11358a07b4ee10bfef19de3b518793568fc498cdd989170d31712b] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [5dbe70b5c83520df09c100815bb164c8903da5eb8bffbd094aaaed54b212d73a] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [8813907b0f7b001080a346ed2d0307a1c749b85688fdfa1d270fe59a07aa3909] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [1d41b04bdd4115c52aac8177e1b899403a3d7d9f6d147cd864463029648a4714] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [c0155fc8e7c4b9736d81db638fed95bc9ff297453bfd0bbd7dd5d882ebca6e89] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [6d0aef4ba9e96d4c63baae8db9cdce7c634140a2bda7da670e698e38e0df57ce] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [a928176ec92ad347404b2454e5f4f321aaef8ba862a60b0c28adc3bdcc619a4a] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [42fa73302624dc511e6d8958c66c82f31b8d9155f2980343b6bcdc25345e1dcd] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [ed324ddc16ccb8b9fab3041da394b844166b6778c39cd12708bcade05b41c0da] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [9ef847d4e699b5dbe49ac74ee35596fdddc22c6335bc96affee19a99ecd077f5] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [f5417c277c6ca509334010bb6999c56c3ab5d3751204c74dc00c2fa25d93dfae] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [a1ffa591430df806983c8798113264f12ea679bce4b785d70d2868dc91cec883] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [b2e525c38598dac6885a75e7eaffa346c8aca3dbdda73cb0275f50103ec3d245] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [5db9424884396cf5bfc46a6b22dacbe245f43a7e1eda6aeac831905dc921802e] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [b5e05ef77effb4048e72e38605700151fdf4eae214cfa358e9e81a48e124cb52] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [ca2c21bf21e1fa2f53c72653ea57e76506c305bdd44c6416542ebbf2ab8b1b83] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [4fc786126dd64f936554a12c4752787c4989453654fc5d6fd119b6e5eeafec6f] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > [f56db5e81304e441260b84d6c2805ae7050ea56760d763d2b32e6be928fa1cae] > > Object > > > > does not exist on the server: [404] Object does not exist on the server > > > > error: failed to fetch some objects from > > > > 'https://github.com/freebsd/freebsd-ports.git/info/lfs' > > > > > > > > I have my own testing pipeline in place to automatically test my > > commits > > > > against changes I did to ports. > > > > > > > > But as LFS is now in the FreeBSD repository, but the files cannot be > > > > retrieved from the FreeBSD repository I'm now locked out for my CI/CD > > > > pipeline and my automated tests. > > > > > > > > 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 > > > > running git lfs fetch --all) > > > > Uploading LFS objects:?? 0% (0/21), 0 B | 0 B/s, done. > > > > error: failed to push some refs to 'gitlab.fechner.net: > > mfechner/Gitlab.git' > > > > > > > > Does anyone have an idea how that can be fixed? > > > > > > Hey Matthias, > > > > > > With commit c94e4ced329298efb06189d1c6db26e3d6ff3eef[1], FreeBSD > > > introduced LFS objects into the ports git history. This commit was > > > reverted with commit 3ec21e417cd5752c96b88587a5a605567ba5cd19[2]. > > > > > > Even though the offending commit was reverted, the git commit history > > > still contains LFS references. This caused HardenedBSD's self-hosted > > > GitLab to become unhappy in exactly the same way yours did. > > > > > > I ended up disabling LFS for the ports repo in the GitLab side. This > > > caused GitLab to become happy again. Problem is, now everyone > > > downstream from us (and FreeBSD, too) will need to disable LFS on > > > their repos/forks, too. > > > > I'm curious if you can turn LFS back on once the broken change is past? > > That that ports should ever use LFS, but it seems somewhat better if > > GitLab configs only need to be non-default during bootstrapping. > > > > At this point there's probably nothing to be done other than workarounds > > as rewriting history to remove this stuff would be quite disruptive > > after several weeks of commits. > > > > We could really use some hooks to block both things that look like lfs > > metadata and submodule bits. (The latter is somewhat challenging in that > > we need to allow them on the vendor side to support OpenZFS.) > > > > I didn't think we imported the submodules of OpenZFS to the vendor branch, > except to the extent that data was plain files in that import not otherwise > used... There's a .gitmodules that has ended up at sys/contrib/openzfs/.gitmodules at least twice. It's fine in the vendor branch, but we should prevent .gitmodules files from being merged to main, etc. -- Brooks From nobody Thu Oct 3 05:17:18 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 4XK0Kt4Qwkz5Xhmr for ; Thu, 03 Oct 2024 05:17:22 +0000 (UTC) (envelope-from mfechner@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (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 4XK0Kt3lV0z4WGq; Thu, 3 Oct 2024 05:17:22 +0000 (UTC) (envelope-from mfechner@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727932642; 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: in-reply-to:in-reply-to:references:references; bh=b7vCxQ1YHdSYWYIptWmofp4bHW+fNnldJvj9i52Pvmc=; b=pdD1e6WMhS9XxjCT25d+mpzsuGi3tFYkzxmX13/+/T83nBQZH9kj0BNWCUILzk3uqBUHt0 m6GdBg4tqLtZQeiDO2rH6xRsV8OYrmdUx1VXPC8qdII7EZZii3yrdpr+uzlhpE/RI6og9A HjbeFLbFDzcl1iD3zmOqvq3AZid36ENVS8lWSv+ORGmWTNvQsuavOL5jyQ09b9pdW3uFSt 0sNCj320PJZQyW6lFtjkA4IPLejcvMAGAEa2XwQDaenBnIarlBH8zu0eP8ejlKDlPlHzja KAXqq3G0wjJq+2gMJYNybCC3yao+H04q1ZcA5kp9FRKGJm0On8dibtDHCl/CCQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727932642; 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: in-reply-to:in-reply-to:references:references; bh=b7vCxQ1YHdSYWYIptWmofp4bHW+fNnldJvj9i52Pvmc=; b=eImB31y9R82DACLYU7Bcn+nPd/BJ0pizWp3pVfRzjDDadI/sAskrzMulKy3eepOuBUZiGQ BCOlRwSBA6IEFSQwvSLyXe21gDwDfx9lYWbYdZfYsmXdHKz8030ioQR6Nifr0376XUpgBU +XljwP7TyVF5hESLUsmvxshHuxCSfdmqgxS2z77jdibmPhrv4a486n/S3vYonqTnCVPx7B tDPdWtKiwnw5aASUpwqOxAW5bJPYEn8sCDr3BuyVi/2rhzy9evtagPT0R5XcrSdGqKBdg6 9UEaeQm07u2uYF80dM5eQlrerT5W1IniDHbrBC2vPgaXYgZMGkaaaDt1cPOmJw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727932642; a=rsa-sha256; cv=none; b=lmzcNvL82wXVwo7Ccde74D496goEnZGP+hgnmG3b7w32xG7h5kbqmjojy7SbaQMqXFFsFA 7u4VeAy1fg60EXfeEg8PmD2nDAqaUwxQBbCbFfPGlXxgMwF+KukRmw0zUML0FY1hOOj4KP 7xY0+pKrJwLvalCStvwjNhe4fHHJVwX6E93ogFZrl9acKQIm4LaVi/kqY1FUZ1VNkRf/5M /bj6EaTVx9g4mP1tPeatcr7bcKQy4K0Taxo2MqJ7F7MslY51LooJFEEkEZOQGx2SiLkMhM tAZd5wfYwCj8LZyAOsu0Vp3Cfp3o2R8uLVhJIngjLNAcpwwiE8al4NsWkCqWQQ== 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 4XK0Ks3H6szfXw; Thu, 3 Oct 2024 05:17:21 +0000 (UTC) (envelope-from mfechner@freebsd.org) Content-Type: multipart/alternative; boundary="------------aomzzQpQ743f3UEqrEnAUGp3" Message-ID: Date: Thu, 3 Oct 2024 08:17:18 +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: Brooks Davis Cc: Dave Cottlehuber , git@freebsd.org References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> Content-Language: en-US From: Matthias Fechner In-Reply-To: This is a multi-part message in MIME format. --------------aomzzQpQ743f3UEqrEnAUGp3 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Am 01.10.2024 um 22:37 schrieb Brooks Davis: > I've done some searching at it looks like there are gitlab options to > disable the various checks. I don't admin any gitlab instances so don't > know how to translate this into something you can use, but: > > https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/lib/gitlab/checks/lfs_check.rb?ref_type=heads > > seems to show an lfs_check.objects_missing knob to disable the precommit > check. You might also need to disable some lfs integrity checks. at least in gitlab it is possible to disable LFS feature per repository. It can be found in the repository under: Settings -> General -> Visibility, project features, permissions -> Repository -> Git Large File Storage (LFS) After I disabled this and saved the changes I was able again to push into my gitlab and all my pipelines are working again. So at least for gitlab I can confirm it is working, maybe other tooling will continue to have problems. Just reverting a commit does not change the history and the history reference these LFS objects which do not exist. I can imagine that other projects, using FreeBSD ports, will maybe see a similar problem. If a rewrite of the ports repository is an option should be decided by the git team, but I think that is the only clean way to get LFS objects out of the repository. I would squash the two commits (the one that added the LFS object and the one that removed it again) into a single commit, like an interactive rebase can do this. But as that will rewrite the complete history from this point on it is maybe not an option. 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 --------------aomzzQpQ743f3UEqrEnAUGp3 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
Am 01.10.2024 um 22:37 schrieb Brooks Davis: 
I've done some searching at it looks like there are gitlab options to
disable the various checks.  I don't admin any gitlab instances so don't
know how to translate this into something you can use, but:

https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/lib/gitlab/checks/lfs_check.rb?ref_type=heads

seems to show an lfs_check.objects_missing knob to disable the precommit
check.  You might also need to disable some lfs integrity checks.
at least in gitlab it is possible to disable LFS feature per repository.
It can be found in the repository under:

Settings -> General -> Visibility, project features, permissions -> Repository -> Git Large File Storage (LFS)

After I disabled this and saved the changes I was able again to push into my gitlab and all my pipelines are working again.

So at least for gitlab I can confirm it is working, maybe other tooling will continue to have problems.

Just reverting a commit does not change the history and the history reference these LFS objects which do not exist.
I can imagine that other projects, using FreeBSD ports, will maybe see a similar problem.

If a rewrite of the ports repository is an option should be decided by the git team, but I think that is the only clean way to get LFS objects out of the repository.
I would squash the two commits (the one that added the LFS object and the one that removed it again) into a single commit, like an interactive rebase can do this.

But as that will rewrite the complete history from this point on it is maybe not an option.

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
--------------aomzzQpQ743f3UEqrEnAUGp3-- From nobody Thu Oct 3 05:20:13 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 4XK0PF3fHyz5Xj4m for ; Thu, 03 Oct 2024 05:20:17 +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 4XK0PF2zQLz4WYW; Thu, 3 Oct 2024 05:20:17 +0000 (UTC) (envelope-from mfechner@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727932817; 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=1TQ7M0AWb4gsWFomYFWkCWwiL1vTJ5QlIpJ7bOjfIno=; b=k6kDQVxRWU949JzEqOHdBfDukJ5mXLZMxGKmqmh1laDkvixHiPahfh/WKJPkh/tdV8Bnnq xVxnx4cG+7DEJEkoGAfKHC4/zrx/gHgVrRV4IRoNWJkEukEUDdDJZ3Nglawq8EIXrr71o5 7pG1vv5osXC5E0iEtCNX5skg4kCZoUj1D5t4TL03Sm8ygYfFm+yYEX/CYvSRNB7e/LIVDW 7tMEx0deABFnZGRYHMPsWDTZSyOqT0W4aNvE+jx1FqUIrQ8zVMj3I1v/ESuBU5dZm/iH5z 62BQb3fxL9xGMQeRwXD5fxRxkO+NN7EWbjDWcYYppaWCa6j5ygPMNXvDKCFy9g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1727932817; 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=1TQ7M0AWb4gsWFomYFWkCWwiL1vTJ5QlIpJ7bOjfIno=; b=TVhzJlyoDhGqY9taPQS29MnPKfP/AKYvQm90BM6CHXYkMsbaGM5zDeBJFGg5YJH3JeOJ5x HwyxP/eAvNIIt6MHlWl8bIvWSdrdH3SoutY151Zswt215yWteGloitBE866qKmdnmUYnCW 4L9V4MxGqlcb8vGrjgxY0yWd0N9G/L5CDtbjjhKm86h4IhDj+jcttmTcTTaT9U2xJducZP PgLntqMHx5O4yOKZ8kCn5Duu7WTZx+wDMNGX4BAFEIoPZTzA7IJ4Yw4rZObxfBtRNdEzKK dR+k4z6lqODUolQ9wilyMcPkfzVsEvFak5B2Y665mDOuvRM6/9TAMocKqOTIBQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1727932817; a=rsa-sha256; cv=none; b=GDbf2AGHSlNn2LqABXGgUV5aecWZFqHLtmNfYytbH5IW8vZG7k/gHkI2L4QF6fLG1yMo5u r76Nvqph2FLpDxdLsKSHmgCo4SCkEF8WtCrVW4CTOJRbzS3bPS/lesuovcOqO76gUX+sIx nZPdNOS7HZswqMeN7Z0FkDzHoUV8LCn+cgJNYeJMMbRcM//Gh4dFml7+zvN0blREgU4dM3 MN8vKwe9o0m/nzc6F8QmUpQ4/OUy6TeJZ3f6Tr9nLoPp+nc0OAiijMe7gf6yPbMHpUykvV TB2/fSghuTubRnZhqZGL9EU1+VqOFf7PlT+53yx6gk6o4g+ORls9X3THNU2Mvg== 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 4XK0PD44zGzdgT; Thu, 3 Oct 2024 05:20:16 +0000 (UTC) (envelope-from mfechner@freebsd.org) Message-ID: <7aacacb5-f76f-466d-9aeb-acf27f0e4905@freebsd.org> Date: Thu, 3 Oct 2024 08:20:13 +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: Shawn Webb Cc: git@freebsd.org References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> <736exensjgsyhbytunglk6qnk3dh4fyyvdc5jktzrv3zzujbgr@db6amzcu53h2> Content-Language: en-US From: Matthias Fechner In-Reply-To: <736exensjgsyhbytunglk6qnk3dh4fyyvdc5jktzrv3zzujbgr@db6amzcu53h2> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Dear Shawn, Am 01.10.2024 um 22:37 schrieb Shawn Webb: > With commit c94e4ced329298efb06189d1c6db26e3d6ff3eef[1], FreeBSD > introduced LFS objects into the ports git history. This commit was > reverted with commit 3ec21e417cd5752c96b88587a5a605567ba5cd19[2]. > > Even though the offending commit was reverted, the git commit history > still contains LFS references. This caused HardenedBSD's self-hosted > GitLab to become unhappy in exactly the same way yours did. yes I found that option in Gitlab too and can confirm it fixed it. Please see also my other email that exactly explain where to find that option. 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 From nobody Thu Oct 3 08:24:48 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 4XK4VP6Yskz5Xx6H for ; Thu, 03 Oct 2024 08:25:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "WR4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4XK4VP3h73z41hB for ; Thu, 3 Oct 2024 08:25:01 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Authentication-Results: mx1.freebsd.org; none Received: by mail-pj1-x1034.google.com with SMTP id 98e67ed59e1d1-2e1bfa9ddb3so317107a91.0 for ; Thu, 03 Oct 2024 01:25:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20230601.gappssmtp.com; s=20230601; t=1727943900; x=1728548700; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mfBT997F8Nr+o5OLUNGENJK0tS/iHQrfjNR29UVuUTo=; b=ze3QYhzxXBX7qk23+OuaFZALIhnGxiMAJHF6T5kbxN1VT+UE69NgVG7kT8jfvXOhWM UfOh2S+R0ja2N7bwT9/qpZwC6zZqWfgYC0eYg1VayvfQ7QHkrTF+skeGILCGRS76/HHN xfXT2QBBAY3swrPwUbiPQDY+ENMp+QLFl+XUQn9CigvSaLXroAoEgd49SO5KA27pew94 mh11UWDMLb4e0Tsqy301XCan8Zl5ZamSaHPgFd2NkTsB1ChM9lg0Y1K+6mDsWxI9HCHd Nm7cwagilz2DmMcQdvV3LGq45fPWuV33BxzxT2ZudIJLz1DIiK2ESCAnfPW0V++Ka1do UrNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727943900; x=1728548700; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mfBT997F8Nr+o5OLUNGENJK0tS/iHQrfjNR29UVuUTo=; b=hAg3KsiTynOyySI/BVnQ/kQBCsbblL/Ylz4v/mKPLH92UR7kjHAvIb/7ZLDE2/KAln EomQ/N1k4S2+jwZMRh3xbpkt7yM6yAVGFiyFWmGOa35aXOeyGQHSWGNEDHlVrOJKNXeC c1bu8MHhZ4ZsUQ7kWBvYJM+X+85ZJMTUp1VXTKzAw9Jx01hB56YzIWyPbVreRnCzz4Ul g2m94gbvONb7PVGAxK6Nxk59JmuQy9zrWXy1RW/p/izu3z4CTS/x83eSpRzp7rdZ0TaP bf2rm5YQV39bve5+4tFx4Du1Qge5xIalVrZE842Vb7N8FCxQZ+PyrurZoFaF/g8aSuxB 4dew== X-Forwarded-Encrypted: i=1; AJvYcCVeHhGHDQezP5Sc0jPWh9csuomVOEO1sXWSZTJPVrfz3MdDMjVkjgbT+pymOUJo0N664EI=@freebsd.org X-Gm-Message-State: AOJu0Yzm98yeCIF3rg2UstfemD+4TzMxa6+CIrJO7HhAcKPtwx4zGPD1 adOfJji696ttA/i+mrk4oB4pBtZT2Fo+VQVEm7Fb0DKKcWhVeNU/0klxDod7UqAy8HW4XzZA1Lm QWok1NDHfGu8lQrX2+KLy5FWNeZd+zXAFKA5KJw== X-Google-Smtp-Source: AGHT+IGDNfozpx3qzcwHWyxp+PN+E8bZAf7RXD/QfFMVy1BQqTGrzRmjI2GwJh2hsSlViGUysx50TL9lNqIEaiQGnv0= X-Received: by 2002:a17:90b:164f:b0:2e0:927a:6928 with SMTP id 98e67ed59e1d1-2e1846c5140mr7803170a91.24.1727943899824; Thu, 03 Oct 2024 01:24:59 -0700 (PDT) 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 References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> In-Reply-To: From: Warner Losh Date: Thu, 3 Oct 2024 02:24:48 -0600 Message-ID: Subject: Re: Impossible to push my ports directory to my CI/CD pipeline To: Matthias Fechner Cc: Brooks Davis , Dave Cottlehuber , git@freebsd.org Content-Type: multipart/alternative; boundary="000000000000575df306238e4a9f" X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] X-Rspamd-Queue-Id: 4XK4VP3h73z41hB X-Spamd-Bar: ---- --000000000000575df306238e4a9f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Wed, Oct 2, 2024 at 11:17=E2=80=AFPM Matthias Fechner wrote: > If a rewrite of the ports repository is an option should be decided by th= e > git team, but I think that is the only clean way to get LFS objects out o= f > the repository > A rewrite of the history is impossible. It's a complete non-starter. The resulting problems would be orders of magnitude worse than this relatively minor inconvenience. Warner --000000000000575df306238e4a9f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Wed, Oct 2, 2024 at 11:17=E2=80=AF= PM Matthias Fechner <mfechner@fr= eebsd.org> wrote:
=20 =20 =20
If a rewrite of the ports repository is an option should be decided by the git team, but I think that is the only clean way to get LFS objects out of the repository
A rewrite of the history is impossible. It's a complete no= n-starter. The resulting problems would be orders of magnitude worse than t= his relatively minor inconvenience.

Warner=C2=A0
--000000000000575df306238e4a9f--