Date: Tue, 01 Oct 2024 07:04:47 +0000 From: "Dave Cottlehuber" <dch@skunkwerks.at> To: "Matthias Fechner" <mfechner@freebsd.org> Cc: git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: <b10dbe8b-e1c7-4da9-8c6c-9360b2545011@app.fastmail.com> In-Reply-To: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b10dbe8b-e1c7-4da9-8c6c-9360b2545011>