On Fri, 2009-09-11 at 20:34 -0500, Gunnar Wolf wrote: > Felipe Sateler dijo [Fri, Sep 11, 2009 at 04:51:23PM -0400]: > > tags 542661 + patch > > thanks > > > > Attached is a nmudiff that does what I said before. > > Thanks. > > I don't think this will solve the problem as a whole, although it will > for many smaller updates — The configuration file must be > auto-upgraded on several major version bumps, and I still have to find > a way to properly declare it. Please check the differentes from the > version currently shipping in Lenny (0.7.2) or even worse, in etch > (0.5.5). This patch you mention _does_ help (and I won't block an NMU > if you do it), but I don't think the bug will be closed.
I have not yet read what the {pre,post}inst code do, but I figure the
right way to go is:
1. If the file has not been modified by the admin, then replace it with
the new one without asking (the default configuration should be as
identical as possible to the old one).
2. If the file has been modified by the admin, perform the auto update
and keep the old one in backup.
If this is done, then everything is OK: users who haven't modified their
configs will continue to upgrade without asking, and users who have
modified it will continue to upgrade with asking.
What other problems do you see? Am I missing something?
>
> Right now I'm quite overworked, and am also redoing the packaging in a
> DH7 fashion¹, so I'd appreciate not having to merge in too much ;-)
> But of course, your work is much appreciated (and will be merged!)
>
> ¹
> http://git.debian.org/?p=collab-maint/cherokee.git;a=commitdiff;h=dh7;hp=master
I'll keep changes as minimal as possible, of course :).
--
Saludos,
Felipe Sateler
signature.asc
Description: This is a digitally signed message part
