Date: Thu, 3 Oct 2024 08:17:18 +0300 From: Matthias Fechner <mfechner@freebsd.org> To: Brooks Davis <brooks@freebsd.org> Cc: Dave Cottlehuber <dch@skunkwerks.at>, git@freebsd.org Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Message-ID: <f668d091-4ef7-4285-a2c3-0afd4bb59881@freebsd.org> In-Reply-To: <ZvxPiTaIc0yNPZF7@spindle.one-eyed-alien.net> References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> <b10dbe8b-e1c7-4da9-8c6c-9360b2545011@app.fastmail.com> <ad3067e0-5c6d-404b-98f7-2f79387f9fcd@freebsd.org> <ZvxHsdk-8XP-4fuc@spindle.one-eyed-alien.net> <ZvxPiTaIc0yNPZF7@spindle.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body> <div class="moz-cite-prefix">Am 01.10.2024 um 22:37 schrieb Brooks Davis:<span style="white-space: pre-wrap"> </span></div> <blockquote type="cite" cite="mid:ZvxPiTaIc0yNPZF7@spindle.one-eyed-alien.net"> <pre wrap="" class="moz-quote-pre">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: <a class="moz-txt-link-freetext" href="https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/lib/gitlab/checks/lfs_check.rb?ref_type=heads">https://gitlab.com/gitlab-org/gitlab-foss/-/blob/master/lib/gitlab/checks/lfs_check.rb?ref_type=heads</a>; seems to show an lfs_check.objects_missing knob to disable the precommit check. You might also need to disable some lfs integrity checks. </pre> </blockquote> at least in gitlab it is possible to disable LFS feature per repository.<br> It can be found in the repository under:<br> <p>Settings -> General -> Visibility, project features, permissions -> Repository -> Git Large File Storage (LFS)</p> <p>After I disabled this and saved the changes I was able again to push into my gitlab and all my pipelines are working again.<br> </p> <p>So at least for gitlab I can confirm it is working, maybe other tooling will continue to have problems.</p> <p>Just reverting a commit does not change the history and the history reference these LFS objects which do not exist.<br> I can imagine that other projects, using FreeBSD ports, will maybe see a similar problem.</p> <p>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.<br> 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.</p> <p>But as that will rewrite the complete history from this point on it is maybe not an option.<br> <br> </p> <pre class="moz-signature" cols="72"> 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 </pre> </body> </html> --------------aomzzQpQ743f3UEqrEnAUGp3--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?f668d091-4ef7-4285-a2c3-0afd4bb59881>