Hi Daniel, > > The system is configured NOT to install Recommends, i.e. it has > > APT::Install-Recommends "false"; > I'm afraid by setting this option you are simply opting into running into > this kind of breakage and are expected to fix it yourself.
Skipping Recommended at *install* time is "you've been warned", but I am not aware of anywhere in the policy where it says not installing Recommended packages *later on* is not supported: in bookworm, there was only ifupdown-ng, which did the right thing, but when -compat was split off, it became necessary to install Recommended as well in order to keep the network working. I do believe this transition from "you need package X in order to do Y" to "you need package X and Z in order to do Y" is worth a mention, even if X now Recommends: Z. > Since ifupdown-ng was a new optional package in bookworm *and* a > non-standard configuration is required to hit this problem I don't think > enough people are likely affected to warrent a release note entry. It's a very cheap thing to do, even if only one other person ever hits it. No code change at all. It does not seem possible to send a patch using salsa without creating an account, so here's one - not a patch format, but since it only adds lines anywhere you like, you should be able to just copy-paste. I hope my rst is correct - it's not something I've used previously: .. _ifupdown-ng: ifupdown-ng needs ifupdown-ng-compat to bring up network ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If a Bookworm system is using ifupdown-ng to bring up its network, it is necessary on upgrade to Trixie to also install the Recommended package ifupdown-ng-compat. Failing to do so will leave the network unconfigured after boot, because ifupdown-ng no longer provides the ifup and ifdown utilities, those having been moved to ifupdown-ng-compat. See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1115926 for details. > > P.S. After installing ifupdown-ng-compat, the networking.service was left > > in a disabled state - I have no opinion of whether that's better or worse > Looks like the service was just being installed subtly wrong. 0.12.1-8 > should fix it. Is that going to be fixed in Trixie, too? Cheers, Juha
