From nobody Tue Oct 01 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--