Your message dated Fri, 31 Aug 2012 11:23:06 +0800
with message-id
<can3verchhqgjs9dhl0apjq6fq7aytsq7h2pgvzunvqvv2gl...@mail.gmail.com>
and subject line Re: Relaxed comment parsing in apt_preferences
has caused the Debian Bug report #345057,
regarding aptitude does not parse whitespace in /etc/apt/preferences correctly
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.)
--
345057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=345057
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
Version: 0.2.15.9-2
I am running Debian stable.
When the /etc/apt/preferences file has comments added to it
in certain patterns, the command "aptitude update" can fail.
If the preferences file contains the following contents:
# some comment
#
# Sid
Package: *
Pin: release a=unstable
Pin-priority: 80
Then "aptitude update" works normally and gives the output
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Hit http://ftp.debian.org stable/main Packages
Hit http://ftp.debian.org stable/main Release
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
On the other hand, if the preferences file contains the following contents:
# some comment
# Sid
Package: *
Pin: release a=unstable
Pin-priority: 80
Then "aptitude update" fails and gives the output
Reading Package Lists... Done
E: Invalid record in the preferences file, no Package header
Blank lines in /etc/apt/prefences do not always generate this error,
but the above pattern seems to be the simplest reproducible case
that forces out the problem.
I came across the problem when I was trying to nicely comment
the /etc/apt/preferences file.
The command "apt-get update" works normally for both cases.
As far as I can tell, the bug remains, regardless of the contents
of the /etc/apt/sources.list file.
Salutations,
Hugo Graumann
--- End Message ---
--- Begin Message ---
See #189866. Fixed in apt 0.7.22.
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
