2008/11/9 Sam Morris <[EMAIL PROTECTED]>:
> On Sun, 2008-11-09 at 00:25 +0100, Jens Peter Secher wrote:
[...]
>
> This makes sense, but I'm _sure_ that dpkg --search told me that the
> files were owned by neko, not libapache2-mod-neko. Is it possible that
> they used to be owned by neko, but transi
On Sun, 2008-11-09 at 00:25 +0100, Jens Peter Secher wrote:
> Hi, thanks for your bug report.
>
> With respect to the two "conffiles"
>
> /etc/apache2/mods-available/neko.conf
> /etc/apache2/mods-available/neko.load
>
> they belong to the package libapache2-mod-neko, and if you simply purge
Hi, thanks for your bug report.
With respect to the two "conffiles"
/etc/apache2/mods-available/neko.conf
/etc/apache2/mods-available/neko.load
they belong to the package libapache2-mod-neko, and if you simply purge
neko with something like
aptitude purge neko
then libapache2-mod-neko wi
reassign 504627 libapache2-mod-neko
thanks
Hi Sam, *,
I can't reproduce this on my Sid box.
I installed neko and libapache2-mod-neko, it correctly
created /etc/apache2/mods-available/neko.{conf,load} and
apt-get remove --purge
correctly removed this two.
At no point, I had a /etc/apache/conf.d/mo
Package: neko
Version: 1.7.0-1
Severity: serious
After purging neko, the following files were left behind on my system:
/etc/apache/conf.d/mod_neko
/etc/apache2/mods-available/neko.conf
/etc/apache2/mods-available/neko.load
-- System Information:
Debian Release: lenny/sid
APT prefers testing
5 matches
Mail list logo