Bug#1002056: Supporting alternative zlib implementations

2024-10-03 Thread Konstantin Demin
One minor moment: zlib-ng doesn't seem to be fully backward compatible. E.g. Angie (nginx's fork with enhancements) is unable to perform gzip compression [1] if built against zlib-ng. It's highly likely that nginx is affected too. [1] https://t.me/angie_support/4205 пт, 4 окт. 2024 г. в 03:13, Fa

Bug#1002056: Supporting alternative zlib implementations

2024-10-03 Thread Fay Stegerman
* Sebastian Andrzej Siewior [2024-10-03 22:03]: > On 2024-09-26 01:35:45 [+0200], Fay Stegerman wrote: > > For example, ZIP files or Android APKs built on a Debian system will have a > > different compressed stream, like the test files you mention. Which will > > likely > > break Reproducible Bu

Bug#1002056: Supporting alternative zlib implementations

2024-10-03 Thread Sebastian Andrzej Siewior
On 2024-09-26 01:35:45 [+0200], Fay Stegerman wrote: > For example, ZIP files or Android APKs built on a Debian system will have a > different compressed stream, like the test files you mention. Which will > likely > break Reproducible Builds tooling like apksigcopier [1] and > reproducible-apk-t

Bug#1002056: Supporting alternative zlib implementations

2024-09-25 Thread Fay Stegerman
* Guillem Jover [2024-09-25 01:55]: > Hi! > > On Wed, 2024-09-25 at 00:39:10 +0200, Fay Stegerman wrote: > > * Guillem Jover [2024-09-24 17:45]: > > > Personally, I think fully migrating from zlib to zlib-ng would sound > > > great (even for trixie), but I guess we can take it slow if you do not

Bug#1002056: Supporting alternative zlib implementations

2024-09-25 Thread Mark Brown
On Wed, Sep 25, 2024 at 01:55:17AM +0200, Guillem Jover wrote: > The problem though is, that because the compressed stream is going to > change, that can make certain test suites fail if we perform this > switch, which I think would be the main fallout that we'd see from > this and would need manu

Bug#1002056: Supporting alternative zlib implementations

2024-09-25 Thread Mark Brown
On Tue, Sep 24, 2024 at 05:45:49PM +0200, Guillem Jover wrote: > On Tue, 2024-09-24 at 15:58:10 +0200, Mark Brown wrote: > > Obviously it's far too late to do anything with the default for trixie, > > we might want to evaluate doing something after the release but for now > > it's too late. > P

Bug#1002056: Supporting alternative zlib implementations

2024-09-24 Thread Mike Hommey
On Wed, Sep 25, 2024 at 01:55:17AM +0200, Guillem Jover wrote: > Hi! > > On Wed, 2024-09-25 at 00:39:10 +0200, Fay Stegerman wrote: > > * Guillem Jover [2024-09-24 17:45]: > > > Personally, I think fully migrating from zlib to zlib-ng would sound > > > great (even for trixie), but I guess we can

Bug#1002056: Supporting alternative zlib implementations

2024-09-24 Thread Guillem Jover
Hi! On Wed, 2024-09-25 at 00:39:10 +0200, Fay Stegerman wrote: > * Guillem Jover [2024-09-24 17:45]: > > Personally, I think fully migrating from zlib to zlib-ng would sound > > great (even for trixie), but I guess we can take it slow if you do not > > feel confident or have concerns over this. >

Bug#1002056: Supporting alternative zlib implementations

2024-09-24 Thread Fay Stegerman
* Guillem Jover [2024-09-24 17:45]: [...] > Personally, I think fully migrating from zlib to zlib-ng would sound > great (even for trixie), but I guess we can take it slow if you do not > feel confident or have concerns over this. As using an alternative zlib implementation could impact Reproduci

Bug#1002056: Supporting alternative zlib implementations

2024-09-24 Thread Guillem Jover
Hi! On Tue, 2024-09-24 at 15:58:10 +0200, Mark Brown wrote: > In the past I've pushed back on doing anything here since zlib is > essential and it seemed better to be consistent over the ecosystem than > to use a more niche implementation, and some of the early optimisation > efforts had not worke

Bug#1002056: Supporting alternative zlib implementations

2024-09-24 Thread Mark Brown
A recurrning question with the zlib package in Debian is interest in the various alternative zlib implementations that are out there. There was a long period where upstream zlib development seemed very stalled, during that period people who wanted improvements started forking their own projects.