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

Thanks, but that is what I want to do, and that is what fails. That's the
point of the bug report actually.

Le mar. 30 juin 2026, 10:46, Aryan Karamtoth <[email protected]>
a écrit :

>
> On 30/06/26 13:02, Julien Puydt wrote:
>
> Hi,
>
> I've been stuck with this since months and no clue how to get around,
> so any insight would be welcome: when I call gbp import-orig --uscan, a
> tarball is downloaded, but can't be committed to git, because of the
> error in the title.
>
> After some poking around, I know:
>
> - the downloaded tarball is correct ;
>
> - checking out the git tree anew doesn't solve anything ;
>
> - pristine-tar is as far as I know the culprit ;
>
> - creating a new account on the same box gives the same problem, so
> it's not a configuration issue.
>
> This is: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122524
>
>
> I use this command for all of my package updates.
>
> gbp import-orig --pristine-tar --uscan
>
> What it does is, it pulls the new upstream tarball, updates the package
> source and commits the pristine tar deltas to the pristine-tar branch.
>
> Alternatively, if you have the orig tarball you can just type pristine-tar
> commit ../tarball.tar.gz and it gets added to the pristine-tar branch.
>
> Those commands are what I normally use for handling pristine-tar branches.
>
> Not sure if this might work in your case but worth a try I guess.
>
> --
> Regards,
>
> Aryan Karamtoth,
> Debian Maintainer
>
> "Sic Parvis Magna" - Sir Francis Drake
>
> Homepage: https://spaceports.in
>
> IRC: spaciouskarter78
> Matrix: @spaciouskarter78:matrix.debian.social
>
> GPG Fingerprint: 7A7D 9308 2BD1 9BAF A83B 7E34 FE90 07B8 ED64 0421
>
>