On Mon, Nov 20, 2023 at 10:59:02AM +0100, =?UTF-8?Q?Preu=C3=9...@buxtehude.debian.org wrote: >... > Not sure, if we need an updated breaks statement. >...
Right now the autopkgtests block zlib migration to testing since they test zlib/unstable with texlive-binaries/testing - this is permitted by the dependencies. And this is not just a test issue: On Sun, Nov 19, 2023 at 01:54:02PM +0100, Hilmar Preuße wrote: > On 11/19/23 00:40, Adrian Bunk wrote: >... > > 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. > > I'd rather expect that the triggers run at the end of the setup process, > i.e. after all packages replaced their files. At least this was the original > ideal behind them IIRC. The idea is to avoid unnecessary duplicate commands, but more than once might be required. And when upgrading to a new stable there are several cycles where triggers run at the end (you might not notice since the package manager takes care of it). On a bookworm -> trixie upgrade the man-db trigger might run 5 or 10 times instead of 1000 packages each executing the command, but it will definitely run more than once. If one of the dependencies of texlive-binaries Pre-Depends on zlib1g, this might be sufficient to ensure that all pending triggers are running after the upgrade of zlib1g and before the upgrade ot texlive-binaries. > Hilmar cu Adrian
