Hi,

On 22/09/2025 19:14, Jochen Sprickerhof wrote:
* Sylvain Beucler <[email protected]> [2025-09-22 17:42]:
There appears to be an issue with piuparts expecting a .tar.gz and getting a .tar instead though.

0m0.0s DEBUG: Starting command: ['tar', '-C', '/tmp/tmpq55k0ax3', '- zxf', '/home/ela/.cache/sbuild/bookworm-arm64.tar']
0m0.0s DUMP:

 gzip: stdin: not in gzip format
 tar: Child returned status 1
 tar: Error is not recoverable: exiting now
0m0.0s ERROR: Command failed (status=2): ['tar', '-C', '/tmp/ tmpq55k0ax3', '-zxf', '/home/ela/.cache/sbuild/bookworm-arm64.tar']

 gzip: stdin: not in gzip format
 tar: Child returned status 1
 tar: Error is not recoverable: exiting now

Actually piuparts in bookworm is rather old and misses the feature to run in unshare mode and such. So all I could do is upload an sbuild version that requires manual configuration for piuparts, but you can do that already now.

Ah OK I misunderstood the intent of your fix.


> My recommendation is to switch to trixie or request a> piuparts backports.

I'm experimenting with ARM builds for archived/ELTS dists, using a Raspberry Pi 400.
https://lts-team.pages.debian.net/howtos/arm-debug.html

It's currently stuck on bookworm, though I expect trixie to be available at some point, hence bookworm-backports.

That's also why I suggested going for a piuparts backports in my initial post. But in this particular case I believe running piuparts outside of sbuild is the most practical approach.

Cheers!
Sylvain Beucler
Debian LTS Team

Reply via email to