Re: Solutions for the Apache upgrade hell
On 2014-07-16 13:46:12 +0200, Guillem Jover wrote:
> On Wed, 2014-07-16 at 11:41:25 +0200, Vincent Lefevre wrote:
> > On 2014-07-13 13:17:24 +0200, Arno Töll wrote:
> > > Unfortunately it turns out, that /a lot/ of people use "aptitude
> > > --purge-unused safe-upgrade", or the apt equivalent "apt-get
> > > dist-upgrade --purge" which causes dpkg to purge the user's
> > > configuration, in particular enabled modules, during the upgrade
> > > because apache2.2-common disappears in that step. [...]
> > Is there any reason why apt-get/aptitude removes the config files
> > just after the package is removed, and not at the end of the upgrade
> > process? IMHO, doing the later is safer and would solve this problem
> > with Apache.
> It just calls dpkg with --purge.
But what I meant is that it could do 2 passes: one without --purge,
and a second one with --purge on the removed packages. Or...
> Something that would also fix this issue (among other upgrade
> problems) is using dpkg “transactions”:
Vincent Lefèvre <email@example.com> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)