Re: Impossible to push my ports directory to my CI/CD pipeline

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.

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?

A+
Dave