On Tue, 29 Sep 2020 16:35:49 +0200 Andrej Shadura <andrew.shad...@collabora.co.uk> wrote: > On Fri, 19 Jul 2019 15:54:19 -0300 Andrej Shadura <andre...@debian.org> > wrote: > > Based on the discussion we’re having right now, to enable to use dgit > > push with a repo where git-lfs has previously been used, the following > > steps are needed: > > > > * file a bug against git-lfs package > > * communications *probably* need to be reviewed by someone else > > * have a list of exact hook scripts we want to disable > > * pass --no-verify when there’s a hook *precisely* matching one of those > > * have a test case in dgit to check it works with the current version of > > git-lfs in Debian > > * when all of the above is done, tell git-lfs Debian maintainers > > > > For your record, here’s a list of related upstream bugs: > > > > * https://github.com/git-lfs/git-lfs/issues/3721 > > This issue has just been addressed with my pull request adding an > environment variable GIT_LFS_SKIP_PUSH to disable LFS functionality. > Just setting it unconditionally to "true" will automagically fix the > issue for git-lfs strictly newer than 2.12.0, not improving it but not > making it worse for any previous versions. The fix is directly in the > git-lfs binary, with no change to the hook scripts; however, > pristine-lfs, which uses git-lfs, already installs a hook adding support > for this variable even if git-lfs doesn’t support it. > > I don’t think fixing the bug for older git-lfs versions is worth extra > hacky code.
git-lfs 2.13.1 (which includes the fix) is now in unstable and I hope autopkgtests will get fixed soon for it to migrate to testing in time. Could you please have a look at this again? It would be great to have this in bullseye. Thanks! -- Cheers, Andrej
