Your message dated Fri, 14 Oct 2022 02:50:46 +0200
with message-id <[email protected]>
and subject line Re: Bug#1012034: dpkg: warning: unknown dpkg database file
/var/lib/dpkg/format is not a misplaced alternative state
has caused the Debian Bug report #1012034,
regarding dpkg: warning: unknown dpkg database file /var/lib/dpkg/format is not
a misplaced alternative state
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.)
--
1012034: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012034
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.21.8
Severity: normal
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On a host running Testing, I got the message below this morning:
Unpacking dpkg (1.21.8) over (1.21.7) ...
Setting up dpkg (1.21.8) ...
dpkg: warning: unknown dpkg database file /var/lib/dpkg/format is not a
misplaced alternative state... leaving as is
dpkg-db-backup.service is a disabled or a static unit not running, not starting
it.
No amount of googling told me what the line about /var/lib/dpkg/format means or
whether this is something to worry about. This probably needs to be documented,
especially if it's expected to appear during an upgrade from Bullseye to
Bookworm.
Martin-Éric
- -- Package-specific info:
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing-debug
APT policy: (500, 'testing-debug'), (500, 'stable-security'), (500, 'testing')
Architecture: i386 (i586)
Kernel: Linux 5.17.0-1-686 (SMP w/1 CPU thread; PREEMPT)
Locale: LANG=fi_FI.UTF-8, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8), LANGUAGE=fi:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages dpkg depends on:
ii libbz2-1.0 1.0.8-5
ii libc6 2.33-7
ii liblzma5 5.2.5-2.1
ii libselinux1 3.3-1+b2
ii tar 1.34+dfsg-1
ii zlib1g 1:1.2.11.dfsg-4
dpkg recommends no packages.
Versions of packages dpkg suggests:
ii apt 2.5.0
pn debsig-verify <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmKTDZUACgkQrh+Cd8S0
17YDDhAAr+jhvprRj0z6e4d6fRpwM3fql3HwKaZA/WsKEpO0eTQvbXPjuTceE9+s
JSUV+A1bRkzVoY/Dsxhto3CHMWurNrS5VO9WsKauJU+zf0AcQRToI0cAXE8XcFIP
CezCLb3vtLXDRFrHs0Qa/VKCM0fHJ26Q+DlZJYAiKPfSkXo7EKLAoY4PDCHsQXcc
CmUt4sRPNTE53NBzZzWBEmnNA47U1QY9yI8Mi/zesQv1yzoKaXmUUMaWpj5aNGLg
pRHZL4ybit5LxJ7MxDPlUgtRU3lEsvJEUIznnSKJpWkupwYBDitjOECBa3KzfsCk
dznArPDxZuKxCCMfv+G92q6SzL8m8/fTx+etnGK1OUt2Gzl2X3vFHCHs2h2cYw7Y
yPkx0NYaGW1dsk6Bu8wEK0X2nFBjkkdZCcnRiO91gzs3U3nilWv9n3syDL6H1TM0
KkpQYgRyhtELTaYdPwQYjJOjib9GfgniLgr9sDHRbYK+C7yIUonD3Y/7toylPStF
uu9Vpz5XObEPZhjROH8gr2EZbgM3IvFSlHITSrCH8T10OuyX3dRUPOGokaLj8L9m
19+m4+4xD0RGaR7JG/v4ykSPdHPATwkv9+NIh8gRFIwSj9hV1vgp1nVOvIgRez/z
UTAvX0teQEFZf2Of3mQAJ9QNSAaornEhpOO4HtLI+yVU8lZ78h0=
=Nj7Y
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi!
On Sun, 2022-05-29 at 15:39:06 +0300, Martin-Éric Racine wrote:
> On Sun, May 29, 2022 at 2:47 PM Guillem Jover <[email protected]> wrote:
> > On Sun, 2022-05-29 at 09:07:25 +0300, Martin-Éric Racine wrote:
> > > Package: dpkg
> > > Version: 1.21.8
> > > Severity: normal
> >
> > > On a host running Testing, I got the message below this morning:
> > >
> > > Unpacking dpkg (1.21.8) over (1.21.7) ...
> > > Setting up dpkg (1.21.8) ...
> > > dpkg: warning: unknown dpkg database file /var/lib/dpkg/format is not a
> > > misplaced alternative state... leaving as is
> > > dpkg-db-backup.service is a disabled or a static unit not running, not
> > > starting it.
> >
> > > No amount of googling told me what the line about /var/lib/dpkg/format
> > > means or whether this is something to worry about. This probably needs
> > > to be documented, especially if it's expected to appear during an
> > > upgrade from Bullseye to Bookworm.
> >
> > This file is really not supposed to be there, and was not the target
> > of that check, which was added to fix a very short-lived mess up with
> > dpkg 1.21.0, so it should not affect bullseye users, but might catch
> > this kind of unrelated breakage, so I'm considering keeping the check
> > part (not the u-a fixing part) and integrating it properly into
> > «dpkg --audit» or similar.
> >
> > The only format file expected to be present in the dpkg db is
> > /var/lib/dpkg/info/format, but certainly not on the db root. What are
> > the contents for that file?
>
> $ ls -al /var/lib/dpkg/format
> -rw-r--r-- 1 root root 1 2011-03-15 18:38 /var/lib/dpkg/format
>
> $ cat /var/lib/dpkg/format
> 2
Given the contents and the last modification date, this looks
plausibly like a leftover from an unofficial dpkg with multiarch
support (from experimental, from one of the half backed implementation
branches or from Ubuntu I guess?). In any case, should be safe to
remove now. I'm thus going to close this report.
Thanks,
Guillem
--- End Message ---
