Hello,
On Mon, 20 May 2013, Hans-Juergen Becker wrote:
The missing files are existing, but doesn't have the :arch in
there filenames:
Somehow it means that you have /var/lib/dpkg/info/format with a content
of 1 when you shouldn't have it yet (you certainly shouldn't have it
before you upgraded dpkg).
Did you try a first upgrade and then forcefully unpack an older version of
dpkg at some point?
In theory, when you upgrade to a multiarch dpkg, things keep working as
usual (with the old layout) but as soon as you start dpkg on a operation
that implies writing to the database, the database gets upgraded to the
newer format for files and at that point it creates
/var/lib/dpkg/info/format with a value of 1.
Note that dpkg -C doesn't open the database in write mode so will not
trigger the upgrade to a multiarch compatible database.
Now while wrinting this bug report i've noticed that dpkgs' configuration
files also weren't correctly upgraded:
A removed conffile is never restored, that's normal behaviour.
In any case, the problem is certainly not affecting everybody and if you
don't have any idea of what you could have done wrong, it will be
difficult to solve.
Your log doesn't show the value of /var/lib/dpkg/info/format at the
different points, so it's difficul to know where you started from and
whether you see a real bug or the result of some bad operation of yours.
Attached is a log of the described problem, containing a -D dpkg
installation - perhaps you can figure something out of it.
Nope, it doesn't help much. The new dpkg is installed by the old one.
What's interesting is how the new one behaves after the initial
installation. And the upgrade code doesn't generate any log message, so
the strace output might be more interesting.
Cheers,
--
Raphaël Hertzog ◈ Debian Developer
Get the Debian Administrator's Handbook:
→ http://debian-handbook.info/get/
--
To UNSUBSCRIBE, email to debian-dpkg-bugs-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
