Bug#327139: apache-perl purge ate /etc/apache

2006-03-26 Thread Adam Conrad
Geoff Crompton wrote: > > There is also /var/lib/dpkg/info/apache-perl.list, with the line > "/etc/apache". Does dpkg use this file to remove stuff? Or is everything > to be removed expressed in the apache-perl.*rm scritpts? dpkg removes everything from .list files, *BUT*, it will never remove a

Bug#327139: apache-perl purge ate /etc/apache

2006-03-26 Thread Geoff Crompton
Adam Conrad wrote: > Geoff Crompton wrote: > >>Do you have any recommendations on how to safely purge apache-perl? I >>thought it'd be good to have it documented in this bug report, for >>future people that might stumble across this. >> >> * manually edit files in /var/lib/dpkg/info to remove refe

Bug#327139: apache-perl purge ate /etc/apache

2006-03-24 Thread Adam Conrad
Geoff Crompton wrote: > > Do you have any recommendations on how to safely purge apache-perl? I > thought it'd be good to have it documented in this bug report, for > future people that might stumble across this. > > * manually edit files in /var/lib/dpkg/info to remove references to > things be

Bug#327139: apache-perl purge ate /etc/apache

2006-03-23 Thread Geoff Crompton
Adam Conrad wrote: > Geoff Crompton wrote: > >>ii apache 1.3.33-6sarge1 versatile, high-performance HTTP server >>pc apache-perl1.3.9-13.1-1.2 Versatile, high-performance HTTP > > > There's nothing I can do to fix the potato (!) version of apache-perl at > this point. > > ... Adam

Bug#327139: apache-perl purge ate /etc/apache

2006-03-23 Thread Adam Conrad
Geoff Crompton wrote: > > ii apache 1.3.33-6sarge1 versatile, high-performance HTTP server > pc apache-perl1.3.9-13.1-1.2 Versatile, high-performance HTTP There's nothing I can do to fix the potato (!) version of apache-perl at this point. ... Adam -- To UNSUBSCRIBE, email to [EM

Bug#327139: apache-perl purge ate /etc/apache

2006-03-23 Thread Geoff Crompton
This just happened to me as well. It is currently reproducable, in that after I'd restored /etc/apache from backup, I tried it again, and it occured again. It's a clients server, so I'm not keen repeating this process though. You can see below I've done some investigating about whats going on. [EM