[pkg-bacula-devel] [pkg-bacula-commits] [SCM] Bacula, a network backup, recovery and verification program branch, migrate-to-ucf, created. debian/5.0.3-1-189-gb6d6282
luca at pca.it
Thu Jun 14 13:18:00 UTC 2012
On Thu, 07 Jun 2012 14:23:09 +0200, Alexander Golovko wrote:
> At least last commit is a subject for discuss.
> There is next trouble:
> When we upgrade package from non-ucf version to ucf-version, even
> local admin didn't change config files, they differ from new configs,
> installed by package.
> So we have two variants.
> 1. Allow ucf to ask user to resolve conflicts manually
> 2. Help ucf to detect, that old config was not changed and it can be
> replaced by new version.
> I like second variant, but it realisation (last commit) seem ugly.
> Maybe you have more accurate solution?
First note: if a solution works, I do not care if it is ugly or not.
Second note: the solution we choose will be carried over until wheezy+1.
That being said, I am not aware of any general solution to this problem
(because each package moving to ucf should have the same problem), so I
would ask on debian-devel@ (please tell me if I should do it).
Something like `dpkg-maintscript-helper migrate_to_ucf` would be the
preferable solution ;-)
However, the ucf-managed files are not dpkg's conffiles:
<mid:505428ca640a282a8996c798ebbb3151 at ankalagon.ru>
This means that we could hit again the piuparts bug we had for
Gismo / Luca
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 835 bytes
Desc: not available
More information about the pkg-bacula-devel