Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2024-04-03 Thread Sebastian Andrzej Siewior
On 2024-04-03 19:16:25 [+0200], Carsten Schoenert wrote: > I did a few more working on some of the packages I maintain and I did not > encounter similar problems with wrong hash ids like a few days back. Given > the troubled times around the liblzma versions I'm not sure the initial > issue about

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2024-04-03 Thread Carsten Schoenert
Hi Guido, Am 22.03.24 um 16:22 schrieb Carsten Schoenert: I need to check this again and in detail, because I had recently some issues as the expected hash ids were different while working with gbp import and later gbp buildpackage on some package from the kicad universe. But I think these

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2024-03-22 Thread Amin Bandali
Hi Carsten, all, On Fri Mar 22, 2024 at 11:22 AM EDT, Carsten Schoenert wrote: [...] > > Thanks a lot for the follow up. Carsten can you confirm with TB if this > > works as > > expected? > > I need to check this again and in detail, because I had recently some > issues as the expected hash ids

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2024-03-22 Thread Carsten Schoenert
Hi Guido, Am 22.03.24 um 09:35 schrieb Guido Günther: ... I got pointed here by Amin. As mentioned, pristine-tar can handle multi-block xz images so this is not an issue. Further xz-utils v5.6.0+ (currently in unstable/ testing) is using multi threaded compression by default. ahh, that would

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2024-03-22 Thread Guido Günther
Hi Sebastian, Carsten, On Fri, Mar 22, 2024 at 08:34:29AM +0100, Sebastian Andrzej Siewior wrote: > On 2019-03-08 22:10:10 [+0100], Carsten Schoenert wrote: > > Hello Guido, > Hi, > > > On Tue, Jan 30, 2018 at 07:19:48AM +0100, Carsten Schoenert wrote: > > > > We should not do more options. Multi

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2024-03-22 Thread Sebastian Andrzej Siewior
On 2019-03-08 22:10:10 [+0100], Carsten Schoenert wrote: > Hello Guido, Hi, > On Tue, Jan 30, 2018 at 07:19:48AM +0100, Carsten Schoenert wrote: > > > We should not do more options. Multi threaded should be on when: > > > > > > - not using pristine-tar > > > - iff pristine-tar can handle it

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2019-03-08 Thread Carsten Schoenert
Hello Guido, On Tue, Jan 30, 2018 at 07:19:48AM +0100, Carsten Schoenert wrote: > > We should not do more options. Multi threaded should be on when: > > > > - not using pristine-tar > > - iff pristine-tar can handle it > > > > The first one is simple but what about the second? the

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2018-01-29 Thread Carsten Schoenert
Hello Guido, On Mon, Jan 29, 2018 at 01:02:30PM +0100, Guido Günther wrote: > > If possible gbp could become a at least a option for setting up the > > number of threads the xz commend will use as long pristine-tar isn't > > working properly with all kinds xz archives? > > We should not do more

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2018-01-29 Thread Guido Günther
Hi, On Sat, Jan 27, 2018 at 10:38:12AM +0100, Carsten Schoenert wrote: > Package: git-buildpackage > Version: 0.9.6 > Severity: wishlist > > Hi, > > while doing packaging work on packages which have several hundreds or > gigabytes if source code files it takes currently a long time to import >

Bug#888572: git-buildpackage: creating xz tarballs should be done multi-threaded

2018-01-27 Thread Carsten Schoenert
Package: git-buildpackage Version: 0.9.6 Severity: wishlist Hi, while doing packaging work on packages which have several hundreds or gigabytes if source code files it takes currently a long time to import new upstream tarballs which uses xz for compression. The same amount of time is needed if