Your message dated Wed, 06 Jun 2007 19:18:41 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Old & not-a-bug
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: aptitude
Version: 0.2.11.1-3
Severity: normal
# aptitude update
Reading Package Lists... 0%
Reading Package Lists... 100%
Reading Package Lists... Done
Building Dependency Tree... 0%
Building Dependency Tree... 0%
Building Dependency Tree... 50%
Building Dependency Tree... 50%
Building Dependency Tree... 85%
Building Dependency Tree
Lese erweiterte Statusinformationen... 0%
Lese erweiterte Statusinformationen... 0%
Lese erweiterte Statusinformationen... Done
E: Unable to parse package file
/var/lib/apt/lists/archive.debian.org_debian-archive_dists_bo_non-free_binary-i386_Packages
(1)
[0m[31;[EMAIL PROTECTED] tty1 /home/mirror [0m
#
apt-get doesn't seem to have problems, nor did the previous version of
aptitude.
Furthermore, if I remove that file, aptitude update doesn't re-fetch it but
complains that it's not there.
Something seems seriously broken.
-- System Information
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux khms.westfalen.de 2.4.19+kai.58 #1 Sam Sep 7 14:16:44 CEST 2002
i686
Locale: LANG=de_DE, LC_CTYPE=de_DE
Versions of packages aptitude depends on:
ii apt [libapt-pkg-libc6.2-3 0.5.4 Advanced front-end for dpkg
ii libc6 2.3.1-9 GNU C Library: Shared libraries an
ii libncurses5 5.3.20021109-2 Shared libraries for terminal hand
ii libsigc++0 1.0.4-3 Type-safe Signal Framework for C++
ii libstdc++2.10-glibc2.2 1:2.95.4-15 The GNU stdc++ library
--- End Message ---
--- Begin Message ---
It looks to me like the problem that was reported here was a mirror
problem; the code that's reporting errors isn't even part of aptitude.
The only issue in aptitude itself is the bogus warnings about missing
files, which have since been fixed. Closing this out.
Daniel
--- End Message ---
