On Tue, 12 Dec 2023 00:18:57 +0100 Maximilian Engelhardt <m...@daemonizer.de> wrote: > On Montag, 11. Dezember 2023 08:51:36 CET Martin-Éric Racine wrote: > [...] > > > > Unless I misunderstood, this is due to a change of debhelper behavior > > since compatibility level 10. This leaves me with two possible > > solutions: > > > > 1) No dh_install option. This will restart after upgrade (default since dh > > 10). > > > > 2) Add --no-stop-on-upgrade --no-restart-after-upgrade options. This > > will explicitely disable stop and restart actions. > > > > Maximilian, which one of these two would make the most sense to you? > > > > Here, I only use the binaries via ifupdown (i.e. only dhcpcd-base), so > > I have no preference. > > > > Martin-Éric > > Hi Martin-Éric, > > I think for me both options should work. I guess for maximising uptime it > would make sense to not restart dhcpcd and if it is important enough (e.g. due > a security bug) inform the user (e.g. via NEWS) that a manual restart should > happen as soon as possible. > > Now that I think more about it, not stopping and starting automatically is > probably the better option, because if something goes wrong during the update > or the update is just stuck at a prompt it could else leave the system without > network connectivity. > Better that stopping and starting again some time later would probably be just > doing an restart once (stop and directly start again without delay) if that's > possible. > > Thanks, > Maxi
I've uploaded the fix to unstable. Since this is not the sort of urgent issue that would warrant a separate update to Bookworm, I won't upload it there for now. However, I'll definitely include it if there ever is a security issue that requires an upload to Bookworm. Martin-Éric
