Jonathan Nieder wrote:
> Harald Dunkel wrote:
>> Any hint how to get out of this mess without corrupting the
>> database would be highly appreciated.
>
> Just a guess, but wouldn’t "dpkg --clear-avail" work?
Err, no, it wouldn’t. But you can edit /var/lib/dpkg/status
and change the version strin
Processing commands for cont...@bugs.debian.org:
> forcemerge 590885 591692
Bug#590885: upgrade fails w/ 'dpkg: parse error' due to Lenny version of
non-free VirtualBox package
Bug#591692: new dpkg can't read /var/lib/dpkg/status anymore
Bug#590896: dpkg: Fails at invalid version identifiers (e.g
forcemerge 590885 591692
quit
Hi Harald,
Harald Dunkel wrote:
> Seems that the new dpkg cannot read /var/lib/dpkg/status anymore.
Known bug in dealing with iffy version strings.
> Any hint how to get out of this mess without corrupting the
> database would be highly appreciated.
Just a guess,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PS: I checked the backups: The "virtualbox" record in the status file
hasn't changed since March 25th. Thats the oldest backup I have.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: dpkg
Version: 1.15.8.3
Seems that the new dpkg cannot read /var/lib/dpkg/status anymore.
Trying to downgrade I get
# dpkg -i dpkg_1.15.8.2_amd64.deb dpkg-dev_1.15.8.2_all.deb
dpkg: parse error, in file '/var/lib/dpkg/status' near line 4099 p
> Am I correct in assuming that anyone with that line in their sources.list
> will
> have a failed upgrade?
Assumption is correct.
I had the same errors and corrected them manually in /var/lib/dpkg/available.
Hi,
On Tue, Aug 03, 2010 at 04:01:48PM -0400, Loïc Minier wrote:
> I wonder whether it makes sense to look into /usr/lib at all when
> cross-building?
Not really, I think.
> If that's not an option, I think the routine checking the format of
> executable could run the cross-objdump and if i
7 matches
Mail list logo
