Bug#366843: marked as done (apache postinstall script insists of (quietly) setting ServerName (to localhost))

2006-09-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 Sep 2006 11:32:46 +0200
with message-id [EMAIL PROTECTED]
and subject line apache postinstall script insists of (quietly) setting 
ServerName (to localhost)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: apache
Version: 1.3.33-6sarge1
Severity: grave

When upgrading apache (or dpkg-reconfiguring it), ServerName directive
is set to some value (defaults to `localhost').  Before upgrade the
configuration was perfectly valid, with ServerName taken from hostname
apache is running on.  After upgrades, ServerName is set to invalid
'localhost'.

Usually I keep local modifications in another file (httpd.conf.local) -
stuff like MinSpareServers, mod_proxy configs (if any) etc - it's easy
to overwrite those even if set in the default httpd.conf.  But I can't
unset ServerName which is being forcedly set in httpd.conf.

There's some words about black magic in
/usr/share/apache/postinst.common wrt setting ServerName.  I probably
can just remove the text postinst.common searches for, to avoid this
issue, but.. that required me about an hour to figure it all out!.. ;)

Why the ServerName is being set in the first place, anyway?  Setting it
quietly is bad (hence Severity set to grave - it silently brokes valid
configuration), but why to set it at all?

Thanks.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing'), (50, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.16-i686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)

Versions of packages apache depends on:
ii  apache-common 1.3.33-6sarge1 support files for all Apache webse
ii  debconf   1.4.30.13  Debian configuration management sy
ii  dpkg  1.10.28Package maintenance system for Deb
ii  libc6 2.3.2.ds1-22   GNU C Library: Shared libraries an
ii  libdb4.2  4.2.52-18  Berkeley v4.2 Database Libraries [
ii  libexpat1 1.95.8-3   XML parsing C library - runtime li
ii  libmagic1 4.12-1 File type determination library us
ii  logrotate 3.7-5  Log rotation utility
ii  mime-support  3.28-1 MIME files 'mime.types'  'mailcap
ii  perl  5.8.4-8sarge4  Larry Wall's Practical Extraction 

-- debconf information excluded

---End Message---
---BeginMessage---
Version: 1.3.34-4

also sprach Michael Tokarev [EMAIL PROTECTED] [2006.05.11.1711 +0200]:
 When upgrading apache (or dpkg-reconfiguring it), ServerName
 directive is set to some value (defaults to `localhost').  Before
 upgrade the configuration was perfectly valid, with ServerName
 taken from hostname apache is running on.  After upgrades,
 ServerName is set to invalid 'localhost'.

If a global ServerName is set in the configuration, dpkg-reconfigure
works as it should, in my tests.

If I remove the global ServerName directive and reconfigure, a new
configuration is created and debconf asks for the server name to
use, defaulting to localhost. It then adds a global ServerName
directive and delegates to ucf to ask whether it's okay to replace
the file.

If for some reason, debconf or ucf don't get to do their jobs
(e.g. noninteractive frontend), the configuration file is not
changed.

This is the intended behaviour.

 Usually I keep local modifications in another file
 (httpd.conf.local) - stuff like MinSpareServers, mod_proxy configs
 (if any) etc - it's easy to overwrite those even if set in the
 default httpd.conf.  But I can't unset ServerName which is being
 forcedly set in httpd.conf.

Do you Include the httpd.conf.local file?

If I add a .local file Included from httpd.conf, and I unset
ServerName in httpd.conf and add it to httpd.conf.local,
dpkg-reconfigure correctly reads and writes to .local instead of
httpd.conf. It *will* use ucf to prompt you whether to replace the
file, which is sort of weird (I'll file another bug about this).

However, as before, I don't see a bug.

 Why the ServerName is being set in the first place, anyway?  Setting it
 quietly is bad (hence Severity set to grave - it silently brokes valid
 configuration), but why to set it at all?

From what I understand, it's needed for redirections when no vhost
matches. apache warns you if you start it without specifying
a value, so it's probably good that Debian sets it.

I am closing this bug. If you feel this is not okay, please provide
more information (like your configuration 

Processed: forcibly merging 384340 342785

2006-09-09 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 # Automatically generated email from bts, devscripts version 2.9.21
 forcemerge 384340 342785
Bug#384340: apache: postrm fails when ucf isn't installed
Bug#342785: apache: purge fails if ucf was uninstalled
Forcibly Merged 342785 384340.


End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#342785: marked as done (apache: purge fails if ucf was uninstalled)

2006-09-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 Sep 2006 11:42:16 +0200
with message-id [EMAIL PROTECTED]
and subject line apache: postinst fails when ucf isn't installed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: apache
Version: 1.3.34-1
Severity: normal

dpkg --remove apache
dpkg --remove ucf
dpkg --purge apache

in this case, the postrm fails because it wants to invoke ucf.

Greetings
Marc

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages apache depends on:
ii  apache-common 1.3.34-1   support files for all Apache webse
ii  debconf [debconf-2.0] 1.4.62 Debian configuration management sy
ii  libc6 2.3.5-8.1  GNU C Library: Shared libraries an
ii  libdb4.3  4.3.29-1   Berkeley v4.3 Database Libraries [
ii  libexpat1 1.95.8-3   XML parsing C library - runtime li
ii  libmagic1 4.15-2 File type determination library us
ii  logrotate 3.7.1-2Log rotation utility
ii  lsb-base  3.0-12 Linux Standard Base 3.0 init scrip
ii  mime-support  3.35-1 MIME files 'mime.types'  'mailcap
ii  perl  5.8.7-8Larry Wall's Practical Extraction 

apache recommends no packages.

---End Message---
---BeginMessage---
Version: 1.3.34-4

The version in sid only calls ucf if the binary can be found
(determined with `which`). I think this bug is thus closed.

-- 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems


signature.asc
Description: Digital signature (GPG/PGP)
---End Message---


Bug#386670: leaves configuration files after purge

2006-09-09 Thread martin f krafft
Package: apache
Version: 1.3.34-4
Severity: normal
Tags: patch

I have not actually verified this, but just by looking at the code
in postrm:

if [ -x `which ucf` ]; then
ucf --purge /etc/apache/httpd.conf
ucf --purge /etc/apache/access.conf
ucf --purge /etc/apache/srm.conf
ucf --purge /etc/apache/modules.conf
else
rm -f /etc/apache/httpd.conf
rm -f /etc/apache/access.conf
rm -f /etc/apache/srm.conf
rm -f /etc/apache/modules.conf
fi

The ucf manpage says:

  Note: ucf  does  not actually  touch  the file on disk in this
  operation, so any file removals are still the responsibility of
  the calling package.

So the rm calls should be outside the if.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (750, 'unstable'), (500, 'testing'), (250, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

-- 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems


signature.asc
Description: Digital signature (GPG/PGP)


Bug#386669: confusing use of ucf

2006-09-09 Thread martin f krafft
Package: apache
Version: 1.3.34-4
Severity: normal

If I Include httpd.conf.local from httpd.conf and set ServerName in
the .local file, debconf will correctly preseed dpkg-reconfigure,
and furthermore, it also writes the change to .local, which is nice.

However, then ucf is run asking me whether to install the new
version of httpd.conf.local. I think that's mighty confusing. ucf is
intended to be used for package-provided files, not just any
configuration file, I think.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (750, 'unstable'), (500, 'testing'), (250, 'stable'), (1, 
'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/dash
Kernel: Linux 2.6.17-2-686
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)

-- 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems


signature.asc
Description: Digital signature (GPG/PGP)


Bug#381376: Status of CVE-2006-3918 #381376

2006-09-09 Thread Loïc Minier
Hi,

 I think only apache was uploaded for CVE-2006-3918, and not apache2.
 Do you intend to issue a DSA for apache2 as well?  Or isn't it affected
 by the vulnerability?

 This is fixed in apache2 = 2.0.55-4.1 in unstable.

   Thanks,
-- 
Loïc Minier [EMAIL PROTECTED]



Re: Bug#381376: Status of CVE-2006-3918 #381376

2006-09-09 Thread Stefan Fritsch
On Saturday 09 September 2006 12:35, Loïc Minier wrote:
  I think only apache was uploaded for CVE-2006-3918, and not
 apache2. Do you intend to issue a DSA for apache2 as well?  Or
 isn't it affected by the vulnerability?

  This is fixed in apache2 = 2.0.55-4.1 in unstable.

The issue is less severe for apache2 because it is much more difficult 
to exploit: apache2 will first wait for the request timeout (usually 
5 minutes) before sending the problematic error message.

Cheers,
Stefan



Processed: Re: apache: postinst fails when ucf isn't installed

2006-09-09 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]:

 reopen 384340
Bug#384340: apache: postrm fails when ucf isn't installed
'reopen' is deprecated when a bug has been closed with a version;
use 'found' or 'submitter' as appropriate instead.
Bug#342785: apache: purge fails if ucf was uninstalled
Bug reopened, originator not changed.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


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



Bug#384340: apache: postinst fails when ucf isn't installed

2006-09-09 Thread Gerfried Fuchs
reopen 384340
thanks

* martin f krafft [EMAIL PROTECTED] [2006-09-09 11:42]:
 Version: 1.3.34-4
 
 The version in sid only calls ucf if the binary can be found
 (determined with `which`). I think this bug is thus closed.

 That the version in sid is fixed is nice and useful information, but
that doesn't solve the problem in stable. As you are propably aware
bugfixes from unstable (and testing) don't flow automatically into
stable, so I really would like to see this fixed in a stable update.

 Thank in advance,
Alfie
-- 
Dessen NOC erklaerte uns aber, dass das Mailproblem nicht an ihnen liegen
koennte der ihr Router habe gar keinen Port 25. Der habe nur 16 Ports.
Also kann Mails nichts mit Port 25 zu tun haben.
 -- Ulli Horlacher in [EMAIL PROTECTED]


signature.asc
Description: Digital signature


Bug#384340: marked as done (apache: postrm fails when ucf isn't installed)

2006-09-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 Sep 2006 14:15:41 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#384340: apache: postinst fails when ucf isn't installed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: apache
Version: 1.3.33-6sarge2
Severity: serious
Justification: Policy 7.2.

Hi!

 Citing from the policy:

,-- policy section 7.2. --
| Note, however, that the `postrm' cannot rely on any non-essential
| packages to be present during the `purge' phase.
`-- policy section 7.2. --

 The postrm fails when ucf isn't present. This might e.g. happen (like
it did for me) when the package is removed, and purged on later time
after being sure the old config from apache isn't needed anymore for
transition to apache2.

 Pretty please fix that for the next point release.  I looked at least in
apache2 in etch and it doesn't seem to use ucf anymore, though it would
fail if update-rc.d isn't present, and that is in a non-essential
package, too (though pulled in through pre-depends from sysvinit, so can
be waved, IMHO).

 So long,
Alfie
-- 
SILVER SERVER  \\ \\ \
[EMAIL PROTECTED] www.sil.at
+43(1)4933256-210 -- t_sysadmin
   keep your backbone tidy

---End Message---
---BeginMessage---
Version: 1.3.34-4

also sprach Gerfried Fuchs [EMAIL PROTECTED] [2006.09.09.1332 +0200]:
 reopen 384340

yeah, uh, please read up on version tracking. The bug will be marked
as closed with version 1.3.34-4 and thus will appear open wrt sarge.

-- 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems


signature.asc
Description: Digital signature (GPG/PGP)
---End Message---


Bug#342785: marked as done (apache: purge fails if ucf was uninstalled)

2006-09-09 Thread Debian Bug Tracking System
Your message dated Sat, 9 Sep 2006 14:15:41 +0200
with message-id [EMAIL PROTECTED]
and subject line Bug#384340: apache: postinst fails when ucf isn't installed
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---BeginMessage---
Package: apache
Version: 1.3.34-1
Severity: normal

dpkg --remove apache
dpkg --remove ucf
dpkg --purge apache

in this case, the postrm fails because it wants to invoke ucf.

Greetings
Marc

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14.3-zgsrv
Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1)

Versions of packages apache depends on:
ii  apache-common 1.3.34-1   support files for all Apache webse
ii  debconf [debconf-2.0] 1.4.62 Debian configuration management sy
ii  libc6 2.3.5-8.1  GNU C Library: Shared libraries an
ii  libdb4.3  4.3.29-1   Berkeley v4.3 Database Libraries [
ii  libexpat1 1.95.8-3   XML parsing C library - runtime li
ii  libmagic1 4.15-2 File type determination library us
ii  logrotate 3.7.1-2Log rotation utility
ii  lsb-base  3.0-12 Linux Standard Base 3.0 init scrip
ii  mime-support  3.35-1 MIME files 'mime.types'  'mailcap
ii  perl  5.8.7-8Larry Wall's Practical Extraction 

apache recommends no packages.

---End Message---
---BeginMessage---
Version: 1.3.34-4

also sprach Gerfried Fuchs [EMAIL PROTECTED] [2006.09.09.1332 +0200]:
 reopen 384340

yeah, uh, please read up on version tracking. The bug will be marked
as closed with version 1.3.34-4 and thus will appear open wrt sarge.

-- 
 .''`. martin f. krafft [EMAIL PROTECTED]
: :'  :proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck http://debiansystem.info
  `-  Debian - when you have better things to do than fixing systems


signature.asc
Description: Digital signature (GPG/PGP)
---End Message---


apache_1.3.33-6sarge3_i386.changes REJECTED

2006-09-09 Thread Debian Installer

Mapping stable-security to proposed-updates.
Rejected: libapache-mod-perl_1.29.0.3-6sarge3_i386.deb: can not copy to holding 
area: file not found.


===

If you don't understand why your files were rejected, or if the
override file requires editing, reply to this email.


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



Bug#386714: apache2: default vhost configuration points to wrong directory

2006-09-09 Thread Manfred Morgner
Package: apache2
Version: 2.0.55-4.1
Severity: wishlist


The default apache2 configuration in file /etc/apache2/sites-available/default 
points to /var/www,
but should point to /var/www/apache2-default.

The effect is, that a browser, showing the default site of the newly installed 
webserver will see
the derectoy listung of /var/www instead of the default installation page, that 
gives detailed
information about what's up and what to do in lots of languages.

The confifuration entry in /etc/apache2/sites-available/default line 5 should 
be:

  DocumentRoot /var/www/apache2-default


Best regards,
Manfred Morgner.


-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-486
Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8)

Versions of packages apache2 depends on:
ii  apache2-mpm-worker2.0.55-4.1 high speed threaded model for Apac

apache2 recommends no packages.

-- no debconf information


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