Your message dated Tue, 07 Jul 2026 22:35:39 +0200 with message-id <[email protected]> and subject line Re: Couldn't commit to pristine-tar - This doesn't look like a tar archive (continued) has caused the Debian Bug report #1122524, regarding Couldn't commit to pristine-tar - This doesn't look like a tar archive to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1122524: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122524 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: git-buildpackage Version: 0.9.39 Severity: important I hadn't worked on packaging since long, but now my workflow is broken in a strange way - apparently, importing a new upstream version doesn't work : $ gbp import-orig --uscan gbp:info: Launching uscan... Newest version of coq-hammer on remote site is 1.3.2+9.1, local version is 1.3.2+9.0 => Newer package available from: => https://github.com/lukaszcz/coqhammer/archive/refs/tags/v1.3.2+9.1.tar.gz Leaving ../coq-hammer_1.3.2+9.1.orig.tar.gz where it is. gbp:info: Using uscan downloaded tarball ../coq- hammer_1.3.2+9.1.orig.tar.gz What is the upstream version? [1.3.2+9.1] gbp:info: Importing '../coq-hammer_1.3.2+9.1.orig.tar.gz' to branch 'upstream'... gbp:info: Source package is coq-hammer gbp:info: Upstream version is 1.3.2+9.1 gbp:error: Import of ../coq-hammer_1.3.2+9.1.orig.tar.gz failed: Couldn't commit to 'pristine-tar' with upstream '2ea1d9814513d58f08f8401c1397109a7b7b7ae3': tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors error: excessively large binary delta for /tmp/pristine- tar.tY7F8p09zt/origtarball (Please consider filing a bug report.) pristine-tar: failed to generate delta gbp:error: Error detected, Will roll back changes. gbp:info: Rolling back branch upstream by resetting it to 86b4c9a503452325aaabc441b157f1cfeaeef3c3 gbp:info: Rolling back branch pristine-tar by resetting it to cdedd02f1c539ceaa2179e03f4bf8153d41b4de4 gbp:error: Rolled back changes after import error. and directly with the tarball: $ gbp import-orig ../coq-hammer_1.3.2+9.1.orig.tar.gz What is the upstream version? [1.3.2+9.1] gbp:info: Importing '../coq-hammer_1.3.2+9.1.orig.tar.gz' to branch 'upstream'... gbp:info: Source package is coq-hammer gbp:info: Upstream version is 1.3.2+9.1 gbp:error: Import of ../coq-hammer_1.3.2+9.1.orig.tar.gz failed: Couldn't commit to 'pristine-tar' with upstream '2ea1d9814513d58f08f8401c1397109a7b7b7ae3': tar: This does not look like a tar archive tar: Exiting with failure status due to previous errors error: excessively large binary delta for /tmp/pristine- tar.Chpg1a_qnq/origtarball (Please consider filing a bug report.) pristine-tar: failed to generate delta gbp:error: Error detected, Will roll back changes. gbp:info: Rolling back branch upstream by resetting it to 86b4c9a503452325aaabc441b157f1cfeaeef3c3 gbp:info: Rolling back branch pristine-tar by resetting it to cdedd02f1c539ceaa2179e03f4bf8153d41b4de4 gbp:error: Rolled back changes after import error. I checked: - that the file I point to is indeed a valid tarball (well, a link to a valid tarball to be precise) ; - that I get a similar failure with other packages. Cheers, J.Puydt
--- End Message ---
--- Begin Message ---Le lundi 06 juillet 2026 à 20:43 -0700, Soren Stoutner a écrit : > On Monday, July 6, 2026 2:30:50 PM Mountain Standard Time Julien > Puydt wrote: > > Le samedi 04 juillet 2026 à 21:11 +0500, Andrey Rakhmatullin a > > écrit : > > > On Sat, Jul 04, 2026 at 06:09:24PM +0200, Julien Puydt wrote: > > > > > > It doesn't happen in a chroot. > > > > > > > > > > I thought you said it does. > > > > > > > > I rechecked and it doesn't. I think I mixed up somewhere... > > > > > > Well then the problem is mot likely in /usr/local or something > > > like > > > that. > > > > Nothing in /usr/local... > > > > Is there a way to actually debug what goes sideways? > > > > I'm a bit desperate... > > My guess is that one of the binaries that creates or processes > tarballs is > corrupt on your system. You could try reinstalling anything that > looks > suspicious. You could also try looking at the list of packages > installed in > your chroot as a list of possible packages to verify that haven’t > been > corrupted. > > In this regards, dpkg -V is helpful. > > https://manpages.debian.org/trixie/dpkg/dpkg.1.en.html Oh, dear, I did just that and now the error is gone! We had checked so many thing, and somewhere some file was just corrupt and stayed so even through package upgrades... THANK YOU ALL! JP
--- End Message ---
