On 2024-02-26 20:46:43 [+0100], Guillem Jover wrote:
> > > Ignoring stderr could be a workaround, but I'd need to do something as
> > > well for the libdpkg code and the perl code calling xz, which will get
> > > very annoying.
> > >
> > > This is also going to get in the way of migrating both xz
On Mon, 2024-02-26 at 20:10:20 +0100, Sebastian Andrzej Siewior wrote:
> On 2024-02-26 19:23:58 [+0100], Guillem Jover wrote:
> > > | 89s +xz: Reduced the number of threads from 16 to 8 to not exceed the
> > > memory usage limit of 1400 MiB
> > > | 89s +xz: Reduced the number of threads from 16 to
On 2024-02-26 19:23:58 [+0100], Guillem Jover wrote:
> Hi!
Hi Guillem,
> > | 89s +xz: Reduced the number of threads from 16 to 8 to not exceed the
> > memory usage limit of 1400 MiB
> > | 89s +xz: Reduced the number of threads from 16 to 8 to not exceed the
> > memory usage limit of 1400 MiB
> >
Hi!
On Mon, 2024-02-26 at 18:57:32 +0100, Sebastian Andrzej Siewior wrote:
> Package: dpkg
> Version: 1.22.4
> Severity: important
> xz-utils 5.6.0 has been uploaded to unstable. A changed behaviour of
> `xz' is now that mutlti threaded compress/ decompression is now enabled
> by default. This in
Package: dpkg
Version: 1.22.4
Severity: important
xz-utils 5.6.0 has been uploaded to unstable. A changed behaviour of
`xz' is now that mutlti threaded compress/ decompression is now enabled
by default. This in turn leads to warnings if the requested amount of
memory exceeds the available amount.
5 matches
Mail list logo