Bug#718789: apache2: upgrade wheezy - testing (2.4.6-2) wiped out all of my log files
Coin, Julian Gilbey wrote: with an appropriate warning in the Description field. This field is not meant to be used for communication with our users and as a DD you should know that well. This would also not help people migrating, as they would have no reason to reread the package description. NEWS.Debian is a proper place but in this case would be too late. debconf is a solution but i'd rather a real fix than such an annoying message. From my point of view, purging an obsolete package is perfectly legitimate and i never had any problem with this before. After reading apache2.2-common.postrm i see no easy way as it is not based on package file ownership. Fortunately only symlinks in config subdirs are removed, and not all logs (only certain patterns); thus httpd.conf is probably the most problematic lost file. I guess this is all dead for unstable but a stable upload may introduce some mechanism without recreating an apache2.2-common package. Regards. -- Marc Dequènes (Duck) pgpE7_dy49fdq.pgp Description: PGP Digital Signature
Bug#718789: apache2: upgrade wheezy - testing (2.4.6-2) wiped out all of my log files
Hi, On 26.11.2013 15:39, Marc Dequènes (Duck) wrote: thus httpd.conf is probably the most problematic lost file. note that we do not ship httpd.conf in Wheezy. If you still have it, it will remain as it is not owned by apache2.2-common anymore. See also: http://anonscm.debian.org/gitweb/?p=pkg-apache/apache2.git;a=blob;f=debian/apache2.2-common.postinst;h=a730b9eff5f06d34301c2cb23804553f2ac4c21b;hb=refs/heads/wheezy#l80 I guess this is all dead for unstable but a stable upload may introduce some mechanism without recreating an apache2.2-common package. Now that the transition is over, we could reintroduce a -common transitional package, but again, we will carefully evaluate this before, as this causes lots of side-effects. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#718789: apache2: upgrade wheezy - testing (2.4.6-2) wiped out all of my log files
Hi, Julian Gilbey wrote: I think enough people are likely to be stung by this one that providing a transition apache2.2-common package would be worth doing, I agree. with an appropriate warning in the Description field. This should be not necessary as the transitional package likely can be be built in a way that it doesn't own the files any more (and maybe a modified postrm script) and hence doesn't remove them on purge, either. Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718789: apache2: upgrade wheezy - testing (2.4.6-2) wiped out all of my log files
Package: apache2 Version: 2.4.6-2 Severity: serious Justification: causes data loss I discovered that on upgrading from wheezy to the current testing, which has just had 2.4.6-2 migrating to it, the entire contents of /var/log/apache2 were blitzed. I'm guessing that what I did was to purge apache2.2-common, not realising the effects of this. Although there is the protection in it about not purging if upgrading to 2.4, it seems that somehow the timings didn't work out correctly and the purge took place anyway. There's no simple or obvious solution to this, I guess, except to provide a transitional apache2.2-common package with apache2 which doesn't purge the log files on purge, now that this task has been taken over by a different package. The description would presumably say: This package may be purged after apache2 version 2.4.6 or higher has been installed; purging prior to this may result in the loss of historical log files. Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#718789: apache2: upgrade wheezy - testing (2.4.6-2) wiped out all of my log files
On 05.08.2013 16:26, Arno Töll wrote: It's your responsibility if you use this option or apt's equivalent. This is the same problem as #717476. Refer there too, why an apache2.2-common package is problematic. err. #711925 I mean. #717476 is a duplicate of the same issue, too. -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#718789: apache2: upgrade wheezy - testing (2.4.6-2) wiped out all of my log files
severity 718789 important thanks On 05.08.2013 15:33, Julian Gilbey wrote: Severity: serious Justification: causes data loss Yes it does, and that's expected. Read the manpage from aptitude (for example): --purge-unused [..] THIS OPTION CAN CAUSE DATA LOSS! DO NOT USE IT UNLESS YOU KNOW WHAT YOU ARE DOING! It's your responsibility if you use this option or apt's equivalent. This is the same problem as #717476. Refer there too, why an apache2.2-common package is problematic. That being said we may just provide it to make these discussions finally (but possibly open a new can'o'worms). -- with kind regards, Arno Töll IRC: daemonkeeper on Freenode/OFTC GnuPG Key-ID: 0x9D80F36D signature.asc Description: OpenPGP digital signature
Bug#718789: apache2: upgrade wheezy - testing (2.4.6-2) wiped out all of my log files
On Mon, Aug 05, 2013 at 04:26:41PM +0200, Arno Töll wrote: Yes it does, and that's expected. Read the manpage from aptitude (for example): --purge-unused [..] THIS OPTION CAN CAUSE DATA LOSS! DO NOT USE IT UNLESS YOU KNOW WHAT YOU ARE DOING! It's your responsibility if you use this option or apt's equivalent. This is the same problem as #717476. Refer there too, why an apache2.2-common package is problematic. That being said we may just provide it to make these discussions finally (but possibly open a new can'o'worms). True, but I had no idea that purging that unused legacy apache-2.2.x package would mean that my modules configuration and all of my log files would be wiped out (I had spotted the earlier problem too, but did not realise the connection until reading the other bug report you referred to); I would expect that if I were purging apache completely, but not when purging legacy packages from an old version during an upgrade. I think enough people are likely to be stung by this one that providing a transition apache2.2-common package would be worth doing, with an appropriate warning in the Description field. Thanks! Julian -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
