go ahead and remove it. this package does not support apache2. (i might
be listed as maintainer but i didn't upload it and know nothing about
being a debian package maintainer.)
-dean
On Fri, 15 Jun 2007, Gerfried Fuchs wrote:
> Package: libapache-mod-iptos
> Severity: serious
> Version: 1.1
Package: mdadm
Version: 2.5.5-1
Severity: grave
even though i have INITRDSTART='none' in my /etc/default/mdadm and rebuilt
the initrd, it still goes and does array discovery at boot time.
this is marked grave because it can cause dataloss if drives with stale
superblocks are put together in an
Package: mdadm
Version: 2.5.5-1
Severity: grave
it's dangerous to generate an mdadm.conf and start running arrays
automatically at install time! i nearly got bit by this.
i marked this grave because there's a potential for data loss with the
current install scripts.
i had 4 disks which i had
the following patch fixes two bugs related to dccproc functioning when the
kernel doesn't support AF_INET6.
dcc_udp_bind is cloberring errno before using it... and is testing for the
wrong errno... it needs to test for EAFNOSUPPORT. i probably should have
dropped the EPFNOSUPPORT tests, but i'
here's my patch.
sorry it's large because i think that per-user umask should be optional,
so i've done most of the work to make that happen... now you have to
specify "user" as an argument to pam_umask.so... as it happens it has to
be the first argument, because arguments are processed left-to-
On Sun, 17 Jul 2005, Michael Berg wrote:
> The latest libpam-umask (0.02) encounters a SIGSEGV (Segmentation fault)
this is because of some unfortunate code that i don't even think should be
in the module... it's a result of the "per-user umask" support. it
segfaults for any user which does *n
6 matches
Mail list logo
