Date: Tue, 1 Oct 2024 07:57:15 -0500 (CDT) From: Dan Mack <mack@macktronics.com> To: Dave Cottlehuber <dch@skunkwerks.at> Cc: Matthias Fechner <mfechner@freebsd.org>, git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: <58d3fa07-be0f-3223-9e74-a65932b069aa@macktronics.com> In-Reply-To: <b10dbe8b-e1c7-4da9-8c6c-9360b2545011@app.fastmail.com> References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> <b10dbe8b-e1c7-4da9-8c6c-9360b2545011@app.fastmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?58d3fa07-be0f-3223-9e74-a65932b069aa>