Bug#1056204: nmu: texlive-bin_2023.20230311.66589-7

[Adrian Bunk <bunk@debian.org>]

On Sat, Nov 18, 2023 at 11:51:15PM +0100, Hilmar Preuße wrote:
> Control: severity -1 important
> Control: block 1056183 by -1
> 
> On 11/18/23 20:18, Samuel Thibault wrote:
> 
> Hi Samuel,
> 
> > 
> > nmu texlive-bin_2023.20230311.66589-7 . ANY . unstable . -m "Rebuild against new zlib"
> > 
> 
> Thanks for filing the NMU bug.
> 
> > So a binnmu of the texlive-bin source package seems needed on all archs
> > to fix installing texlive-binaries.
> > 
> 
> I tested if recompiling solves the issue and it does. Hence I bump severity
> of the NMU bug the get a solution ASAP.

I don't see how a binNMU would solve the problem.

A proper fix would be either to:
1. patch the version check out of texlive-bin (preferred), or
2. ensure texlive-bin has package dependencies that match this runtime check

After a binNMU the migration of zlib to testing would still be 
blocked forever by the autopkgtest of packages like asymptote that
will continue to test with zlib/unstable and texlive-bin/testing.

And it also might affects users directly, without proper dependencies 
e.g. a bookworm -> trixie upgrade might end up with the following order
(among many other things happening during the upgrade):
1. zlib gets upgraded
2. the tex-common trigger runs
3. texlive-bin gets upgraded
If this is permitted by the dependencies, then step 2 must not fail.

> Hilmar

cu
Adrian