Hi,

Le mercredi 08 avril 2026 à 04:37 +0100, Nick Morrott a écrit :
> On Tue, 7 Apr 2026 at 17:53, Julien Puydt <[email protected]>
> wrote:
> 
> > 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.
> 
> Dear Julien,
> 
> Apologies for the late night drive-by response - I was searching for
> other pristine-tar info, noticed your issues, and figured I'd try to
> reproduce.
> 
> I have just tested locally (note: machine has 64GB RAM) using the
> elpi workflow from the bug report above.
> 
> I had no problems with any of the following:
> 
> *) gbp import-orig --verbose --uscan
> 
>  - this downloaded/imported latest 3.6.2 tarball and generated
> pristine-tar delta

Fails here.

> *) gbp import-orig --verbose ~/elpi-3.4.5.tar.gz

Fails here.

> - using a local download of the 3.4.5 upstream tarball, generated
> pristine-tar delta
> 
> *) pristine-tar commit ~/elpi-3.4.5.tar.gz upstream/latest

Fails here.

> - after deleting the above 3.4.5 delta from the pristine-tar branch,
> generated pristine-tar delta
> 
> So, it does work (n=1), and the tarballs, gbp and pristine-tar are
> okay.

Very interesting!

> Does your /tmp have enough free space?

"df -h /tmp" says 16G, so I guess the answer is yes.

Thanks,

JP

Reply via email to