Hi, Le mercredi 08 avril 2026 à 08:39 +0200, Stéphane Glondu a écrit : > > Le 07/04/2026 à 18:52, Julien Puydt a écrit : > > I was usually managing my packages in the science and ocaml team > > using > > a git-buildpackage workflow (as explained > > in https://science-team.pages.debian.net/policy/#idm307 ). > > > > This has been broken since months by: > > > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122524 > > > > on which I have had no answer. > > > > > > Am I the only one having the issue? Is there a workaround? or > > perhaps calling pristine-tar directly isn't that difficult - and > > actually works? > > I was not aware of any issue with git-buildpackage (and I routinely > use it), but I don't have exactly the same workflow: I download the > tarballs first with "uscan", then I import them with "gbp import- > orig" (which looks like the second attempt of your initial attempt). > > Some ideas: > - lack of space in /tmp
"df -h /tmp" says 16G of free space. > - some kind of odd firewall or network restriction that would corrupt > the tarball when downloaded by uscan/gbp Hmmmm... see below. > - something corrupted in your local clone; did you try with a fresh > one? Yes, I did. I just noticed that the failing packages all come from github.com ; while all others come from other places. I tried to download a .tar.gz by hand, and the import-orig fails, even though tar extracts the archive without any warning. Looks like a lead, finally - even if not a fix yet. Cheers, JP
