Re: Couldn't commit to pristine-tar - This doesn't look like a tar archive (continued)

Soren Stoutner <[email protected]> Sat, 04 Jul 2026 07:48:32 -0700

Newsgroups	gmane.linux.debian.devel.general
Organization	Debian
Message-ID	<2838068.mvXUDI8C0e@soren-desktop>

On Saturday, July 4, 2026 5:54:34 AM Mountain Standard Time Julien Puydt 
wrote:
> Le mardi 30 juin 2026 à 13:23 -0700, Soren Stoutner a écrit :
> > On Tuesday, June 30, 2026 1:45:54 AM Mountain Standard Time Aryan
> > Karamtoth
> > 
> > wrote:
> > > On 30/06/26 13:02, Julien Puydt wrote:
> > > I use this command for all of my package updates.
> > > 
> > > gbp import-orig --pristine-tar --uscan
> > 
> > This package does not contain a gbp.conf.
> > 
> > https://salsa.debian.org/ocaml-team/coq-hammer/-/tree/master/debian?
> > ref_type=heads
> > 
> > Usually when working with pristine-tar, I find it best to include a
> > gbp.conf in the debian directory that enables --pristine-tar by
> 
> > default for anyone working on the package.  Like this:
> But for the elpi package I get the problem even though there is a
> gbp.conf...

Is your problem limited to one machine?  Meaning, if you use a different 
machine to run "gbp import-orig --uscan”, does it work correctly?

-- 
Soren Stoutner
[email protected]

signature.asc (application/pgp-signature, 833 B)