Your message dated Mon, 23 Feb 2026 09:48:13 +0000
with message-id <[email protected]>
and subject line Bug#1123081: Removed package(s) from unstable
has caused the Debian Bug report #426968,
regarding webalizer: Wishing new conf setup were like logrotate
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
426968: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=426968
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: webalizer
Version: 2.01.10-32
Severity: wishlist
I appreciate the effort put into making the default webalizer
configuration a little more 'vhost friendly'. I did this locally a while
back and it seems that I came up with a solution similar to the one in
the webalizer 2.01.10-32 package (which seems different than the
solution proposed in bug 229179.)
One point where the new package and my configuration differ is that I
left the default config in /etc.
My setup:
/etc/webalizer.conf
/etc/webalizer.d/<site>.conf
/etc/cron.daily/webalizer
(package.conf & package.d/ similar to logrotate and discover)
I did this to take advantage of the way webalizer takes it's
configuration parameters. It first reads a default config named
webalizer.conf. This is either a local default config in the working
directory or the global one in the configured etcdir. Then it reads
command line options, including configuration file directives. For any
given setting the last option wins. This way I can set all my common
default information like DNSCache in one place and have my per-site
('vhost') configurations be much shorter.
The new package (maybe since 2.01.10-30) does a similar thing, but now
the global default config is grouped in with the other configs in
/etc/webalizer. It no longer stands out as a special default file. Even
the cron.daily script seems to treat it like any other config by
loading it up (effectively parsing it twice) as it iterates the config
file directory if it happens to have a LogFile directive.
I should have suggested a wish list bug on this long ago, when I first
set it up this way. I hate to change things around on people, even if I
think my layout looks better.
Please consider updating the README.Debian to emphasise how
webalizer.conf is treated differently than any other .conf in
/etc/webalizer.
The cron.daily script could reinforce this by more clearly skipping
webalizer.conf in the loop and invoking it after the loop iff the loop
didn't process any other conf files by calling webalizer without a -c
option.
-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-k7
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages webalizer depends on:
ii debconf [debconf-2.0] 1.5.11 Debian configuration
management sy
ii libc6 2.3.6.ds1-13 GNU C Library: Shared libraries
ii libdb4.2 4.2.52+dfsg-2 Berkeley v4.2 Database
Libraries [
ii libgd2-xpm 2.0.33-5.2 GD Graphics Library version 2
ii libgeoip1 1.3.17-1.1 A non-DNS IP-to-country
resolver l
ii libpng12-0 1.2.15~beta5-1 PNG library - runtime
ii zlib1g 1:1.2.3-13 compression library - runtime
webalizer recommends no packages.
--
Jacob
--- End Message ---
--- Begin Message ---
Version: 2.23.08-3.3+rm
Dear submitter,
as the package webalizer has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1123081
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
