Your message dated Tue, 26 Jun 2007 19:20:22 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#430084: upgrade with unstable releases fixed it
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)

--- Begin Message ---
Package: webalizer
Version: 2.01.10-32.1
Severity: grave
Justification: renders package unusable

Since the last upgrade, yesterday, webalizer refuse to run throwing this error 
message :
webalizer: /usr/lib/libdb-4.5.so: no version information available (required by 
webalizer)


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Shell: /bin/sh linked to /bin/bash

Versions of packages webalizer depends on:
ii  debconf [debconf-2.0]     1.5.13         Debian configuration management sy
ii  libc6                     2.5-9+b1       GNU C Library: Shared libraries
ii  libdb4.5                  4.5.20-1       Berkeley v4.5 Database Libraries [
ii  libgd2-xpm                2.0.34-1       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-2 PNG library - runtime
ii  zlib1g                    1:1.2.3-15     compression library - runtime

webalizer recommends no packages.

-- debconf information:
* webalizer/logfile: /var/log/apache/access.log
* webalizer/doc_title: Usage statistics for
  webalizer/upgrading:
* webalizer/dnscache: true
* webalizer/directory: /home/sites/www_root/stats
* webalizer/upgrade2011030:


--- End Message ---
--- Begin Message ---
[EMAIL PROTECTED] wrote:
> I've just manually upgraded webalizer and libdb4.5 to the unstable
> releases ( libdb4.5.20-4 and webalizer 2.01.10-32.1)
> and now everything seems to work fine.

=> closing the bug.

Cheers

Luk

--- End Message ---

Reply via email to