Your message dated Sat, 2 Mar 2019 23:44:25 +0100
with message-id <[email protected]>
and subject line Re: Bug#303030: "parse error, in file
`/var/lib/dpkg/available'" after update
has caused the Debian Bug report #303030,
regarding "parse error, in file `/var/lib/dpkg/available'" after update
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.)
--
303030: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=303030
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Severity: normal
After my last update "dpkg -l" does not work any more. Here is what I
get:
----
$ dpkg -l galeon
dpkg-query: parse error, in file `/var/lib/dpkg/available' near line 1:
field name `bgucharmap4,' must be followed by colon
----
I did not modify /var/lib/dpkg/available, so I guess one of the programs
accessing this file (synaptic?) must have corrupted it. (I guess this is also
the
reason why reportbug was not able to put any package version information
at the end of this bug report.
Francois
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.10.guidog-patch2
Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15)
--- End Message ---
--- Begin Message ---
Control: tag -1 unreproducible
Hi!
On Mon, 2005-04-04 at 10:02:01 +0100, Francois Taiani wrote:
> Package: dpkg
> Severity: normal
> After my last update "dpkg -l" does not work any more. Here is what I
> get:
>
> ----
> $ dpkg -l galeon
> dpkg-query: parse error, in file `/var/lib/dpkg/available' near line 1:
> field name `bgucharmap4,' must be followed by colon
> ----
>
> I did not modify /var/lib/dpkg/available, so I guess one of the programs
> accessing this file (synaptic?) must have corrupted it. (I guess this is also
> the
> reason why reportbug was not able to put any package version information
> at the end of this bug report.
I don't think this is a dpkg problem, there's been no clear way to
reproduce this, and in general when this type of thing happens it is
hardware related, malfunctioning memory or disk or similar.
I'm going to close this, as currently unactionable. If there is new
evidence this is happening and is not attributed to hardware problems,
please either reopen or file a new bug.
Thanks,
Guillem
--- End Message ---
