Bug#1065751: Incomplete fix for xz -T1

2024-03-10 Thread Jia Tan
Hello! I took a look at the patch and attached a small patch fix for it. I hope this helps! Jia Tan From 0f03dce25f174725e80dcd78bfa6ddd640b3714a Mon Sep 17 00:00:00 2001 From: Jia Tan Date: Sun, 10 Mar 2024 22:16:20 +0800 Subject: [PATCH] pristine-xz: Fix -T1 fallback if threads not specified.

Bug#1065751: Incomplete fix for xz -T1

2024-03-09 Thread Jeremy BĂ­cha
This issue also affects being able to use git-buildpackage to generate pristine-tar tarballs for tarballs that were already committed before the recent changes to pristine-tar. For instance I experienced it today with `gbp buildpackage` with gtk4 but the original tarball was committed in January.

Bug#1065751: Incomplete fix for xz -T1

2024-03-09 Thread Andrey Rakhmatullin
On Sun, Mar 10, 2024 at 12:34:00AM +0500, Andrey Rahmatullin wrote: > It looks like #1063252 was not enough to support tar.xz files created by new > xz-utils. I've created a tarball, committed it into my gbp repo, checked it > out > and xz -lvv doesn't show the cu flags for it (and so it's not ide

Bug#1065751: Incomplete fix for xz -T1

2024-03-09 Thread Andrey Rahmatullin
Package: pristine-tar Version: 1.50+nmu1 Severity: serious X-Debbugs-Cc: Sebastian Andrzej Siewior It looks like #1063252 was not enough to support tar.xz files created by new xz-utils. I've created a tarball, committed it into my gbp repo, checked it out and xz -lvv doesn't show the cu flags for