Your message dated Sun, 15 Jun 2008 18:00:13 +0200 (CEST)
with message-id <[EMAIL PROTECTED]>
and subject line package has been removed
has caused the Debian Bug report #475589,
regarding libcgi-perl: obsolete extended description
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.)
--
475589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=475589
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libcgi-perl
Version: 2.76-25
Severity: normal
2.76 is very old, and stein.cshl.org mentions 3.05 as being current.
But it is finally outdated as well: CPAN reports 3.05 to released in
2004, and 3.35 to be current.
It is quite unusual to have such an old version in Debian, so maybe
there's a compatibility issue of some sort. But the extended
description does not mention anything like this - worse, it refers to
libcgi-pm-perl, which is not any more in Debian, but maybe that
package indeed contained those more recent versions at some time ?
Anyway, at least some amount of clarification is needed.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (90, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.23.8-smp (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=french (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages libcgi-perl depends on:
ii liburi-perl 1.35.dfsg.1-1 Manipulates and accesses URI strin
ii libwww-perl 5.808-1 WWW client/server library for Perl
ii perl 5.8.8-12 Larry Wall's Practical Extraction
libcgi-perl recommends no packages.
--- End Message ---
--- Begin Message ---
Hi,
This package has been removed, so the bug is no longer relevant. Thank you
for your effort in reporting it, though.
cheers,
Thijs
--- End Message ---
