Bug#397310: Downgrade

from apache 2.0, right? you don't get it, that bug broke sam's configuration wich is RC. full stop. the fact that it's usable for you does not matter, upgrades should NOT break user's configuration. stop playing games with the BTS. -- ·O· Pierre Habouzit ··O

Bug#390823: apache2-common cannot be purged.

Package: apache2-common Version: 2.0.55-4.2 Severity: serious it should have been made an empty package, without maintainer scripts, so that it could be purged, as it's superseeded with apache2.2-common. [madcoder mad] LC_ALL=C sudo dpkg --purge apache2-common (Reading database ... 142646 fi

Bug#390818: apache2-mpm-prefork: upgrade does not work if apache2 is already stopped

Package: apache2-mpm-prefork Version: 2.2.3-1 Severity: grave Justification: renders package unusable sorry for the french locale, but I guess all is pretty clear enough. * Stopping apache 2.0 web server... grep: /etc/apache2/conf.d/[^.#]*: Aucun fichier ou répertoire de ce type [ ok ]

Bug#390817: apache2.2-common: /etc/apache2/*-available/ have .svn dirs inside

Package: apache2.2-common Version: 2.2.3-1 Severity: grave Justification: causes non-serious data loss [root mad] cd /etc/apache2/mods-available ; svn info | grep URL URL : svn+ssh://svn.debian.org/svn/pkg-apache/trunk/apache2/config-dir/mods-available says it all. I happen to version my /etc/

Bug#316321: revisiting the "reload target" issue

Le Mar 30 Mai 2006 15:52, Adam Conrad a écrit : > Pierre HABOUZIT wrote: > > Ping apache2-common maintainers ? > > > > is there any reason why that bug is rotting in a RC state for 4+ > > monthes ? > > > > I may perform an NMU soon. > > Yes

Bug#316321: revisiting the "reload target" issue

, not sending signal. failed! Ping apache2-common maintainers ? is there any reason why that bug is rotting in a RC state for 4+ monthes ? I may perform an NMU soon. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org signature.asc Description: Digital signature