[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

How to tell dpkg that a conffile of a disappeared package is now a configuration file (ucf)?


in the woody-to-sarge upgrade, tetex-base has taken over a file that was
previously a conffile of the texdoctk package.  In sarge, 

tetex-base: Replaces: texdoctk
tetex-bin: Replaces/Conflicts/Provides: texdoctk

so usually texdoctk is left in state "rc".  

However, since the file has changed between texdoctk's woody version and
tetex-base's sarge version, dpkg would have asked "conffile created by
you or a script".  To prevent this, we have put the file under ucf
control, and everything is fine...

... until somebody finds that texdoctk is in state rc and he doesn't
need it, and purges the package.  dpkg will remove the "conffile of
texdoctk", not knowing that it is now a (not-dpkg-managed) configuration
file of tetex-base.

Is there a way to prevent this, or is the bottom line just that ucf
should not be used for that purpose, i.e. in all cases where the package
that takes over conffiles does not depend on the replaced package?

Regards, Frank
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer

Reply to: