Hi!

On Tue, 2014-09-23 at 00:05:27 +0800, 積丹尼 Dan Jacobson wrote:
> Package: dpkg
> Version: 1.17.13

> How did /var/lib/dpkg/status get corrupted?
> 
> $ dpkg -l
> dpkg-query: error: parsing file '/var/lib/dpkg/status' near line 26673 
> package 'libmailutils4':
>  '(installed' is not allowed for third (status) word in 'Status' field

Thanks for the bug report! But hmmm.

> $ tail /var/log/dpkg.log
> 2014-09-22 23:08:06 status unpacked libncurses5:i386 5.9+20140913-1
> 2014-09-22 23:08:07 startup packages configure
> 2014-09-22 23:08:07 configure libncurses5:i386 5.9+20140913-1 <none>
> 2014-09-22 23:08:07 status unpacked libncurses5:i386 5.9+20140913-1
> 2014-09-22 23:08:07 status half-configured libncurses5:i386 5.9+20140913-1
> 2014-09-22 23:08:07 status installed libncurses5:i386 5.9+20140913-1
> 2014-09-22 23:08:07 status triggers-pending libc-bin:i386 2.19-11
> 2014-09-22 23:08:07 trigproc libc-bin:i386 2.19-11 <none>
> 2014-09-22 23:08:07 status half-configured libc-bin:i386 2.19-11
> 2014-09-22 23:08:07 status installed libc-bin:i386 2.19-11
> $ diff /var/lib/dpkg/status-old /var/lib/dpkg/status
> 11796c11796
> < Status: install ok unpacked
> ---
> > Status: install ok installed
> 11805d11804
> < Config-Version: 5.9+20140712-2
> 26674c26673
> < Status: install ok installed
> ---
> > Status: install ok(installed
> 
> Well I just used ed(1) to change the ( to a space and was able to
> proceed. Not sure how it got corrupted but I'm reporting this anyway.
> Feel free to close this bug.

From the code, this should never happen, and I'm actually pretty lost
on how that would be a problem with the code. Of note is that the
difference between " " and "(" is just one bit (100000 vs 101000),
perhaps there is something fishy with your hardware, have you
experienced any other data corruption/loss, random crashes or similar,
you might want to perform some memory checks or similar.

As it stands I'm not sure much can be done with this bug report
though.

Thanks,
Guillem


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

Reply via email to