Your message dated Mon, 01 Sep 2008 19:31:20 +0300
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#496191: Package description misses a space at the
begining of a line, causing "dpkg -l" to fail.
has caused the Debian Bug report #496191,
regarding Package description misses a space at the begining of a line, causing
"dpkg -l" to fail.
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.)
--
496191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=496191
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: libsasl2-2
Version: 2.1.22.dfsg1-22
Architecture: armel
Source: cyrus-sasl2
Hi!
Here is a small problem with this package (Or I think it comes from the package)
# dpkg -l
dpkg-query: erreur d'analyse syntaxique, dans le fichier
« /var/lib/dpkg/status » près de la ligne 1760 paquet « libsasl2-2 »:
le nom de champ « suse » doit être suivi de deux points (:)
In english it says that the field "suse" should be followed by ':'
but in fact there's a space missing at the beginning of the line.
In the Description:
.
Any of: ANONYMOUS, CRAM-MD5, DIGEST-MD5, GSSAPI (MIT or Heimdal
Kerberos 5), NTLM, OTP, PLAIN, or LOGIN can be used. If you intend to
-suse this package on a server that provides SASL authentication, then
+ suse this package on a server that provides SASL authentication, then
you must install some of the libsasl2-modules* packages.
Homepage: http://asg.web.cmu.edu/sasl/sasl-library.html
Thanks.
Have fun
--- End Message ---
--- Begin Message ---
On Mon, 2008-09-01 at 12:13 -0400, Roberto C.Sánchez wrote:
> This looks to me like a case of the dpkg database getting corrupted.
> I've had it happen to me on various systems and it always manifests
> itself in some different way. I move that we close the bug report as
> there is no evidence that it is anything else.
With this message, I'm closing the bug.
Nathael, if you find a way to reproduce this bug, then please reopen it
or submit a new bug. Your help is very much appreciated!
Thanks,
--
Fabian Fagerholm <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part
--- End Message ---
