Pierre Habouzit wrote:

Le sam 23 septembre 2006 02:50, The Wanderer a écrit :

Package: apt-listchanges
Version: 2.63
Severity: grave
Justification: renders package unusable


For some time now, every time I install a package via apt-get,
apt-listchanges does not pop up its display of changelogs. Instead,
I get the following (immediately after "Retrieving bug reports...
Done"):


Traceback (most recent call last):
   File "/usr/bin/apt-listchanges", line 210, in ?
     main()
   File "/usr/bin/apt-listchanges", line 65, in main
     status.readfile('/var/lib/dpkg/status')
   File "/usr/share/apt-listchanges/DebianControlParser.py", line 47, in 
readfile
     self.stanzas += [DebianControlStanza(x) for x in open(file, 
'r').read().split('\n\n') if x]
   File "/usr/share/apt-listchanges/DebianControlParser.py", line 19, in 
__init__
     field, value = line.split(':', 1)
ValueError: need more than 1 value to unpack

please send me your /var/lib/dpkg/status (not to the bts because of
its size).

If you still need that after the below, just let me know and I'll pass
it along with no further fuss. (I ordinarily hate bug reporters who
refuse to follow instructions, especially requests for information, and
I don't like the idea of being one - but in this instance I think I may
know just enough about what's going on to avoid having to send a
multi-megabyte file through the mail.)

it seems you have some odd thing in there, and I've no clue of what
is happening.

technically, it can only happen if you have a line that does not
starts with a space, nor is empty, and has no ':' in it.

so either there is a \t starting line or so, and I need to deal with
that (but that would be quite suprising) or you have some
ill-formatted file. well, with that file I could have a clue.

Yep - that seems to be the cause. I grepped out lines which fit those
three criteria, and the three lines remaining all begin with tabs - they
appear in the description of gnome-system-tools 0.26.1-1 (which I do not
actually have installed, its status is 'deinstall ok config-files'). I'm
not sure of how to correctly clear that out, since editing the file by
hand to insert the appropriate spaces does not seem remotely "correct";
any suggestions?

--
      The Wanderer

Warning: Simply because I argue an issue does not mean I agree with any
side of it.

Secrecy is the beginning of tyranny.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to