Your message dated Sat, 25 Aug 2012 07:27:42 +0800
with message-id <87wr0nq39t....@jidanni.org>
and subject line Re: Bug#685439: Use of uninitialized value $_[0] in hash
element at /usr/bin/apt-show-versions line 729.
has caused the Debian Bug report #685439,
regarding Use of uninitialized value $_[0] in hash element at
/usr/bin/apt-show-versions line 729.
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 ow...@bugs.debian.org
immediately.)
--
685439: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685439
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: apt-show-versions
Version: 0.18
Severity: grave
$ apt-show-versions |head
Use of uninitialized value $_[0] in hash element at /usr/bin/apt-show-versions
line 729.
Use of uninitialized value in string comparison (cmp) at
/usr/bin/apt-show-versions line 721.
Use of uninitialized value $_[0] in hash element at /usr/bin/apt-show-versions
line 729.
Use of uninitialized value in string comparison (cmp) at
/usr/bin/apt-show-versions line 721.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-3-486
Locale: LANG=zh_TW.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages apt-show-versions depends on:
ii apt 0.9.7.4
ii libapt-pkg-perl 0.1.26+b1
ii perl [libstorable-perl] 5.14.2-12
apt-show-versions recommends no packages.
apt-show-versions suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
>>>>> "CM" == Christoph Martin <mar...@uni-mainz.de> writes:
CM> I can't reproduce this on my sid system. Can you please give me more
CM> details? What is in your sources.list? Do you have repositories which
CM> have no proper Release file?
It seems to be cured today.
I'll reopen if it happens again.
--- End Message ---
