Bug#659148: apache2: Incorrect debhelper build dependency

[Allard Hoeve]

Package: apache2
Version: Incorrect debhelper build depends
Severity: minor


Dear Arno,


You've changed the build dependency to debhelper to (=8) in 2.2.22-1, but this
build dependency is too weak:

While trying to rebuild the package on squeeze, the package does not compile,
because debhelper 8.0.0 does not call override_dh_install-arch. Using 8.9.13
from bpo does. I tested the build on squeeze using 8.9.13 and it builds fine.


Please adjust the versioned depends to 8.9.13 or higher for us backporters. (I
haven't tested lower, but 8.9.13 is freely available for squeeze from bpo, so
one could say that's fine).



Thanks

Allard Hoeve



-- System Information:
Debian Release: 6.0.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash



-- 
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120208173318.4182.52845.reportbug@allard

Bug#501403: (no subject)

[Allard Hoeve]

Subject: apache2: Apache reload fails with failed nscd assertion
Package: apache2
Version: 2.2.8-4byte2etch0
Severity: normal



Dear Maintainers,

We run clusters of about 15 webservers that are reloaded for new configs about
twenty times per day. This results in the following error about once
per day per cluster:

apache2: nscd_helper.c:133: __nscd_unmap: Assertion mapped-counter == 0' 
failed.
/usr/sbin/apache2ctl: line 83: 30212 Aborted $HTTPD ${APACHE_ARGUMENTS} -k $ARGV
invoke-rc.d: initscript apache2, action reload failed.
Kon Apache niet herstarten: Bad file descriptor

I'm not sure what information to include in the bugreport. If you'd like more 
information about the setup, I'd be happy to provide it.

Regards,

Allard Hoeve

PS: Am running a backported version of the Apache webserver from
testing on etch.


-- Package-specific info:
List of enabled modules from 'apache2 -M':
  accounting actions alias auth_basic authn_file authz_default
  authz_groupfile authz_host authz_user autoindex cgi dir* env
  expires headers include mime negotiation php5* rewrite setenvif
  status suexec userdir*
  (A * means that the .conf file for that module is not enabled in
   /etc/apache2/mods-enabled/)

-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (600, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.25.4-fwsh-byte
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)

Versions of packages apache2 depends on:
ii  apache2-mpm-prefork2.2.8-4byte2etch0 Traditional model for Apache HTTPD

apache2 recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#485922: apr: -fstack-protector results in FTBFS on etch

[Allard Hoeve]

Package: apr
Version: 1.2.12-3
Severity: wishlist


Dear Maintainer,

The new stack-protector options prevent this package from being
backported to etch.

Please make the -fstack-protector clase in debian/rules optional for releases 
later than etch (for example using lsb_release -c -s) or even nicer, optional 
for releases of GCC that provide the stack-protector feature.

Otherwise, please conflict with earlier verions of GCC (for example the
one in etch, etc).

Thanks!

Regards,

Allard


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (600, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.7-fwsh-byte
Locale: LANG=en_US.UTF8, LC_CTYPE=en_US.UTF8 (charmap=UTF-8) (ignored: LC_ALL 
set to en_US.UTF8)



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#282042: apache-common/logs incorrectly complains about logging to pipes

[Allard Hoeve]

Package: apache-common
Version: 1.3.33-2.1
Severity: wishlist
Tags: patch

Dear Maintainers,

In our apache setup, we log to a program. This program transports messages to a 
logserver, which than processes the 
logentries. This is working fine.

While upgrading apache, the postinst scripts prompt me with a message that 
apache has switched to logrotate and logfiles
should be situated in /var/log and nowhere else. While this could potentially 
be a very useful message, all my logfiles are
in /var/log/, except for my pipe ofcourse. While investigating the situation, I 
wrote up this quick patch to make
postinst.common not croak when encountering pipes. This should confuse fewer 
users.

Please apply.

Regards,

Allard


-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8.1-byte
Locale: LANG=C, LC_CTYPE=C

Versions of packages apache-common depends on:
ii  apache-utils   1.3.33-2.1Utility programs for webservers
ii  debconf1.4.30.10 Debian configuration management sy
ii  elinks [www-browser]   0.9.1+0.9.2pre4-1 Character mode WWW/FTP browser
ii  libc6  2.3.2.ds1-18  GNU C Library: Shared libraries an
ii  libdb4.2   4.2.52-17 Berkeley v4.2 Database Libraries [
ii  libexpat1  1.95.8-1  XML parsing C library - runtime li
ii  lynx [www-browser] 2.8.5-2   Text-mode WWW Browser
ii  mime-support   3.28-1MIME files 'mime.types'  'mailcap
ii  perl   5.8.4-3   Larry Wall's Practical Extraction 
ii  sed4.1.2-1   The GNU sed stream editor
ii  ucf1.13  Update Configuration File: preserv

-- debconf information:
  apache-common/confignotes:
  apache-common/old-logrotate-exists:
* apache-common/logs:
  apache-shared/debconf-modules: mod_userdir, mod_status, mod_ssl, 
mod_setenvif, mod_rewrite, mod_negotiation, mod_mime_magic, mod_mime, 
mod_log_config, mod_include, mod_env, mod_dir, mod_cgi, mod_autoindex, 
mod_auth, mod_alias, mod_actions, mod_access, mod_php4
  apache-shared/restart: false
Index: listlogfiles
===
--- listlogfiles(revision 102)
+++ listlogfiles(working copy)
@@ -42,7 +42,7 @@
 # take away surrounding ' and 
 $file =~ s/[\\']//g;
  
-if ($file !~ m|^/var/log/| ) {
+if ($file !~ m!^(?:/var/log/|\|)! ) {
 #  $errorcondition++; # uncomment this if you prefer count of errors
   $errorcondition = 1;
   print Wrong log file definition in $conf: $_ if $printerrorfile;

Bug#235976: apache: Apache overwrites local configuration

[Allard Hoeve]

Package: apache
Version: 1.3.29.0.1-5
Severity: important

Hello All,

Whenever apache gets installed, reinstalled, upgraded or reconfigured, it 
overwrites my configuration in /etc/apache.

Perhaps my setup is a bit exotic, so I will explain the situation:

I have several Apache servers that have mostly identical configurations. To 
reduce redundancy, we placed the configuration
files on an NFS share. The local directory /etc/apache/ now contains a 
local.conf that contains any configuration directives
that should remain local and a symlink from /etc/shared/apache/httpd.conf to 
/etc/apache/httpd.conf. The shared
configuration file includes the local.conf file and all is well.

That is, all is well until the apache postinst scripts get called.

Through some magic, the symlink in /etc/apache gets removed and replaced by a 
new httpd.conf plaintext file that contains
the exact content as my /etc/shared/apache/httpd.conf. Needless to say: this is 
bad news for me. Changes made in the central
httpd.conf are no longer propagated to all servers.


One example of code, possibly responsible for removing the symbolic link, is 
from postinst.common:

if [ ! `grep ^PidFile /var/run/$pkg.pid /etc/$pkg/httpd.conf` ] ; then
cat /etc/$pkg/httpd.conf |  perl -pe \
s,^PidFile.*,PidFile /var/run/$pkg.pid,;  
/etc/$pkg/httpd.conf.dpkg-inst.$$
mv /etc/$pkg/httpd.conf.dpkg-inst.$$ /etc/$pkg/httpd.conf
fi


This raises two questions:

a) Should the apache postinst scripts overwrite a configuration file
   with a new file with identical content?
b) Should the apache postinst scripts remove a symlink and replace it
   with a plaintext file?


I think that according to section 10.7.3 of the Debian Policy Manual, a) could 
be argued for but b) can not.

I'm looking forward to hearing your thoughts about this.



Sincerely,

Allard Hoeve



-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.25
Locale: LANG=C, LC_CTYPE=C

Versions of packages apache depends on:
ii  apache-common 1.3.29.0.1-5 Support files for all Apache webse
ii  debconf   1.4.11   Debian configuration management sy
ii  dpkg  1.10.18  Package maintenance system for Deb
ii  libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii  libdb4.2  4.2.52-8 Berkeley v4.2 Database Libraries [
ii  libexpat1 1.95.6-6 XML parsing C library - runtime li
ii  libmagic1 4.07-2   File type determination library us
ii  libpam0g  0.76-15  Pluggable Authentication Modules l
ii  logrotate 3.6.5-2  Log rotation utility
ii  mime-support  3.25-1   MIME files 'mime.types'  'mailcap
ii  perl [perl5]  5.8.3-2  Larry Wall's Practical Extraction