On Fri, 28 Feb 2025 at 11:21:01 +0100, Marc Haber wrote:
I am afraid that our efforts in making adduser easier to use in
maintainer script have mainly occurred during the trixie release, so
if you want your maintainer script to also work in backports it is
probably better to keep it the way it is.
I don't care about backports for this particular package (backporting
something as central and system'y as dbus seems like a lot of regression
risk for little reward). My concern is that if dbus is installed during
an upgrade from bookworm to trixie, its postinst needs to be guaranteed
to work correctly, even if adduser hasn't necessarily been upgraded to
its trixie version yet.
So adding a versioned Depends on a suitable adduser that has the
behaviours you're referring to would probably be fine (that would force
adduser to be upgraded before the new dbus-system-bus-common.postrm is
allowed to run, so that d-s-b-c can safely rely on features of the new
adduser), but I think leaving the dependency unversioned would not be
OK. Does bookworm's 3.134 have all the behaviours you want dbus to rely
on? Or if not, is trixie's 3.137 enough?
Thanks,
smcv
