Bug#678674: initscripts: upgrade to Wheezy leaves obsolete configs

Dmitry Bogatov KAction at debian.org
Sat Dec 29 18:34:36 GMT 2018

control: retitle -1 Provide a way to transfer config files between packages
control: reassign -1 dpkg
control: severity -1 wishlist

[2012-06-24 15:23] Martin-Éric Racine <martin-eric.racine at iki.fi>
> 2012/6/23 Petter Reinholdtsen <pere at hungry.com>:
> > [Roger Leigh]
> >> If you do have any ideas about how this can be safely handled, we
> >> would of course be very happy to hear them.
> >
> > What about changing them in the bootlogd package, and check if the md5sum
> > of the scripts are the ones from the old initscripts package or the new
> > bootlogd package?  It would make it possible to detect if ti is the old
> > ones from initscripts or the new ones from bootlogd.
> >
> > Are you sure they are listed as obsolete by dpkg when both initscripts
> > and bootlogd are installed?  I doubt it, but have not tested it.
> I don't have bootlogd installed.
> However, I'm starting to feel that we need a proper
> dpkg-maintscript-helper method to deal with config files that change
> package ownership, especially in cases when the new package that
> adopts some config files won't necessarily be pulled in as a Depends
> or Recommends of the old package.
> I'd really welcome the feedback of dpkg maintainers on how this could
> be best handled.

I am sorry, that this bug was not addressed properly. It timed out on
sysvinit, reassigning to dpkg.

More information about the Debian-init-diversity mailing list