Package: ucf
Severity: normal
When a configuration file managed by ucf is diverted (using dpkg-divert),
ucf attempts to modify the original path for the conffile, rather than the
diverted path.
I realize that using dpkg-divert on configuration files is not a
particularly common operation at the moment, but I think that may change
in the future (http://wiki.debian.org/ConfigPackages suggests a workaround
for this problem of diverting the ucf source file, but I think that
solution reaches too far into the ucf-managed package's internals).
I think correct behavior here is for ucf to follow diversions so that it
updates the undiverted version of the configuration file (this is what
would happen with a conffile), rather than fighting with the package or
local administrator that diverted the configuration file.
The tricky issue in implementing this feature is that the ucf interface
doesn't specify what package is running ucf as, so there isn't a good way
to achieve correct behaviour with diversions by packages.
I think the best way to do this would be to add an option -P<package name>
that causes ucf to ignore diversions by <package name>, e.g. for the case
that ucf is in the postinst script for <package name>. Most packages
would not need to specify this option (in particular, the ones that need
to do so are precisely those that divert and then replace a configuration
file with a ucf-managed version).
If a patch to follow diversions and add an option to specify the package
name used for diversion exceptions would be acceptable to you, I'd be
willing to write one.
Thanks,
-Tim Abbott
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]