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 will _not_ get purged automatically, that is,
the above conffiles will stay on the machine. You should also have been
instructed to run
/etc/init.d/apache2 restart
and after doing that, your apache2 will work fine and treat Neko files
as binary blobs.
However, if you instead run
aptitude purge libapache2-mod-neko
then you will indeed get the conffiles removed.
All this is how it is expected to work on a Debian system.
With respect to the file
/etc/apache/conf.d/mod_neko
it is a configuration file Apache 1.3, and not part of
libapache2-mod-neko, so many it is a left-over from some manual install
of neko?
Can you confirm or unconfirm the above observations?
Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
