Your message dated Fri, 18 Mar 2022 00:35:26 +0100
with message-id <[email protected]>
and subject line Re: Bug#990796: dpkg: warning: package not in status nor
available database at line
has caused the Debian Bug report #990796,
regarding dpkg: warning: package not in status nor available database at line
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.)
--
990796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990796
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Severity: normal
Hi.
I've seen the following several times now when upgrading from stretch to buster
via aptitude:
Setting up libgail-common:amd64 (2.24.32-3) ...
Setting up xscreensaver (5.42+dfsg1-1) ...
=> at this point /var/log/apt/term.log stops, which I guess it shouldn't...
Errors were encountered while processing:
netfilter-persistent
iptables-persistent
=> that this fails is probably related to iptables switching nft compatibiltiy
stuff and/or the old kernel being purged by myself during the upgrade
But the following is the actual reason I'm writing:
dpkg: warning: package not in status nor available database at line 4:
clang-3.8:amd64
dpkg: warning: package not in status nor available database at line 5:
libclang1-3.8:amd64
dpkg: warning: package not in status nor available database at line 6:
python-lldb-3.8:amd64
dpkg: warning: package not in status nor available database at line 7:
liblldb-3.8-dev:amd64
dpkg: warning: package not in status nor available database at line 8:
lldb-3.8:amd64
dpkg: warning: package not in status nor available database at line 9:
llvm-3.8-dev:amd64
dpkg: warning: package not in status nor available database at line 10:
llvm-3.8:amd64
dpkg: warning: package not in status nor available database at line 11:
libllvm3.8:amd64
dpkg: warning: package not in status nor available database at line 12:
libperl5.24:amd64
dpkg: warning: package not in status nor available database at line 13:
perl-modules-5.24:all
dpkg: warning: package not in status nor available database at line 14:
libpython3.5:amd64
dpkg: warning: package not in status nor available database at line 15:
python3.5:amd64
dpkg: warning: package not in status nor available database at line 16:
libpython3.5-stdlib:amd64
dpkg: warning: package not in status nor available database at line 17:
openjdk-8-jdk:amd64
dpkg: warning: package not in status nor available database at line 18:
openjdk-8-jre:amd64
dpkg: warning: package not in status nor available database at line 19:
libllvm3.9:amd64
dpkg: warning: package not in status nor available database at line 20:
ca-cacert:all
dpkg: warning: package not in status nor available database at line 21:
clang-3.8-doc:all
dpkg: warning: package not in status nor available database at line 22:
gcc-6-locales:all
dpkg: warning: package not in status nor available database at line 24:
linux-headers-4.9.0-14-amd64:amd64
dpkg: warning: package not in status nor available database at line 25:
linux-compiler-gcc-6-x86:amd64
dpkg: warning: package not in status nor available database at line 26:
gcc-6:amd64
dpkg: warning: package not in status nor available database at line 27:
cpp-6:amd64
dpkg: warning: package not in status nor available database at line 28:
cpp-6-doc:all
dpkg: warning: package not in status nor available database at line 30:
g++-6-multilib:amd64
dpkg: warning: package not in status nor available database at line 31:
g++-6:amd64
dpkg: warning: package not in status nor available database at line 32:
libx32stdc++-6-dev:amd64
dpkg: warning: package not in status nor available database at line 33:
gcc-6-multilib:amd64
dpkg: warning: package not in status nor available database at line 34:
gcc-6-base:amd64
dpkg: warning: package not in status nor available database at line 35:
gcc-6-doc:all
dpkg: warning: package not in status nor available database at line 38:
lib32stdc++-6-dev:amd64
dpkg: warning: package not in status nor available database at line 39:
lib32gcc-6-dev:amd64
dpkg: warning: package not in status nor available database at line 40:
libx32gcc-6-dev:amd64
dpkg: warning: package not in status nor available database at line 41:
lib32asan3:amd64
dpkg: warning: package not in status nor available database at line 42:
libstdc++-6-dev:amd64
dpkg: warning: package not in status nor available database at line 43:
libobjc-6-dev:amd64
dpkg: warning: package not in status nor available database at line 44:
libgcc-6-dev:amd64
dpkg: warning: package not in status nor available database at line 45:
libasan3:amd64
dpkg: warning: package not in status nor available database at line 46:
libbind9-140:amd64
dpkg: warning: package not in status nor available database at line 47:
libblas-common:amd64
dpkg: warning: package not in status nor available database at line 48:
libboost-filesystem1.62.0:amd64
dpkg: warning: package not in status nor available database at line 49:
libcephfs1:amd64
dpkg: warning: package not in status nor available database at line 50:
libboost-iostreams1.62.0:amd64
dpkg: warning: package not in status nor available database at line 51:
libboost-program-options1.62.0:amd64
dpkg: warning: package not in status nor available database at line 52:
libboost-random1.62.0:amd64
dpkg: warning: package not in status nor available database at line 53:
libboost-regex1.62.0:amd64
dpkg: warning: package not in status nor available database at line 54:
libboost-thread1.62.0:amd64
dpkg: warning: package not in status nor available database at line 55:
libboost-system1.62.0:amd64
dpkg: warning: package not in status nor available database at line 56:
libclang-common-3.8-dev:amd64
dpkg: warning: package not in status nor available database at line 57:
libconfuse1:amd64
dpkg: warning: package not in status nor available database at line 60:
libdns-export162:amd64
dpkg: warning: package not in status nor available database at line 61:
libisccfg140:amd64
dpkg: warning: package not in status nor available database at line 62:
libdns162:amd64
dpkg: warning: package not in status nor available database at line 64:
libf2fs0:amd64
dpkg: warning: package not in status nor available database at line 65:
ruby2.3:amd64
dpkg: warning: package not in status nor available database at line 66:
libruby2.3:amd64
dpkg: warning: package not in status nor available database at line 69:
libicu57:amd64
dpkg: warning: package not in status nor available database at line 72:
libipset3:amd64
dpkg: warning: package not in status nor available database at line 73:
libisc-export160:amd64
dpkg: warning: package not in status nor available database at line 74:
libisccc140:amd64
dpkg: warning: package not in status nor available database at line 75:
libisc160:amd64
dpkg: warning: package not in status nor available database at line 76:
libisl15:amd64
dpkg: warning: package not in status nor available database at line 77:
liblldb-3.8:amd64
dpkg: warning: package not in status nor available database at line 78:
liblogging-stdlog0:amd64
dpkg: warning: package not in status nor available database at line 80:
liblvm2cmd2.02:amd64
dpkg: warning: package not in status nor available database at line 81:
liblwres141:amd64
dpkg: warning: package not in status nor available database at line 82:
libmariadbclient18:amd64
dpkg: warning: package not in status nor available database at line 84:
libntfs-3g871:amd64
dpkg: warning: package not in status nor available database at line 85:
libprocps6:amd64
dpkg: warning: package not in status nor available database at line 88:
librpmsign3:amd64
dpkg: warning: package not in status nor available database at line 92:
python-libsmbios:all
dpkg: warning: package not in status nor available database at line 95:
libtxc-dxtn-s2tc:amd64
dpkg: warning: package not in status nor available database at line 96:
libunbound2:amd64
dpkg: warning: package not in status nor available database at line 98:
libx32asan3:amd64
dpkg: warning: package not in status nor available database at line 100:
linux-doc-4.9:all
dpkg: warning: package not in status nor available database at line 101:
linux-headers-4.9.0-14-common:all
dpkg: warning: package not in status nor available database at line 102:
linux-kbuild-4.9:amd64
dpkg: warning: package not in status nor available database at line 103:
llvm-3.8-doc:all
dpkg: warning: package not in status nor available database at line 104:
llvm-3.8-runtime:amd64
dpkg: warning: package not in status nor available database at line 107:
openjdk-8-doc:all
dpkg: warning: package not in status nor available database at line 108:
openjdk-8-jre-zero:amd64
dpkg: warning: package not in status nor available database at line 110:
openjdk-8-jdk-headless:amd64
dpkg: warning: package not in status nor available database at line 111:
openjdk-8-jre-dcevm:amd64
dpkg: warning: package not in status nor available database at line 112:
pxz:amd64
dpkg: warning: package not in status nor available database at line 113:
python3.5-doc:all
dpkg: warning: found unknown packages; this might mean the available database
is outdated, and needs to be updated through a frontend method;
please see the FAQ <https://wiki.debian.org/Teams/Dpkg/FAQ>
[ Rootkit Hunter version 1.4.6 ]
File updated: searched for 181 files, found 156
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up netfilter-persistent (1.0.11+deb10u1) ...
Job for netfilter-persistent.service failed because the control process exited
with error code.
See "systemctl status netfilter-persistent.service" and "journalctl -xe" for
details.
invoke-rc.d: initscript netfilter-persistent, action "restart" failed.
? netfilter-persistent.service - netfilter persistent configuration
Loaded: loaded (/etc/systemd/system/netfilter-persistent.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2021-07-07 18:53:05 CEST; 7ms
ago
Process: 18126 ExecStart=/usr/sbin/netfilter-persistent start (code=exited,
status=1/FAILURE)
Main PID: 18126 (code=exited, status=1/FAILURE)
Jul 07 18:53:05 lcg-lrz-xcache1 systemd[1]: Starting netfilter persistent
configuration...
Jul 07 18:53:05 lcg-lrz-xcache1 netfilter-persistent[18126]: run-parts:
executing /usr/share/netfilter-persistent/plugins.d/15-ip4tables start
Jul 07 18:53:05 lcg-lrz-xcache1 netfilter-persistent[18126]:
iptables-restore/1.8.2 Failed to initialize nft: Protocol not supported
Jul 07 18:53:05 lcg-lrz-xcache1 netfilter-persistent[18126]: run-parts:
/usr/share/netfilter-persistent/plugins.d/15-ip4tables exited with return code 1
Jul 07 18:53:05 lcg-lrz-xcache1 netfilter-persistent[18126]: run-parts:
executing /usr/share/netfilter-persistent/plugins.d/25-ip6tables start
Jul 07 18:53:05 lcg-lrz-xcache1 netfilter-persistent[18126]:
ip6tables-restore/1.8.2 Failed to initialize nft: Protocol not supported
Jul 07 18:53:05 lcg-lrz-xcache1 netfilter-persistent[18126]: run-parts:
/usr/share/netfilter-persistent/plugins.d/25-ip6tables exited with return code 1
Jul 07 18:53:05 lcg-lrz-xcache1 systemd[1]: netfilter-persistent.service: Main
process exited, code=exited, status=1/FAILURE
Jul 07 18:53:05 lcg-lrz-xcache1 systemd[1]: netfilter-persistent.service:
Failed with result 'exit-code'.
Jul 07 18:53:05 lcg-lrz-xcache1 systemd[1]: Failed to start netfilter
persistent configuration.
dpkg: error processing package netfilter-persistent (--configure):
installed netfilter-persistent package post-installation script subprocess
returned error exit status 1
dpkg: dependency problems prevent configuration of iptables-persistent:
iptables-persistent depends on netfilter-persistent (= 1.0.11+deb10u1);
however:
Package netfilter-persistent is not configured yet.
dpkg: error processing package iptables-persistent (--configure):
dependency problems - leaving unconfigured
Processing triggers for libgdk-pixbuf2.0-0:amd64 (2.38.1+dfsg-1) ...
Processing triggers for rkhunter (1.4.6-5) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-4.19.0-17-amd64
cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
nor crypto modules. If that's on purpose, you may want to uninstall the
'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
integration and avoid this warning.
W: Possible missing firmware /lib/firmware/bnx2/bnx2-rv2p-09ax-6.0.17.fw for
module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-rv2p-09-6.0.17.fw for
module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-mips-09-6.2.1b.fw for
module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-rv2p-06-6.0.15.fw for
module bnx2
W: Possible missing firmware /lib/firmware/bnx2/bnx2-mips-06-6.2.3.fw for
module bnx2
I: The initramfs will attempt to resume from /dev/dm-1
I: (/dev/mapper/vg_system-swap)
I: Set the RESUME variable to override this.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for ca-certificates (20200601~deb10u2) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
done.
Errors were encountered while processing:
netfilter-persistent
iptables-persistent
Press Return to continue, 'q' followed by Return to quit.
So no idea why these:
dpkg: warning: package not in status nor available database at line
occur.
They don't show up on all systems I upgrade, that is even if another one
as exactly the same config/packages.
And after that (and after repairing the netfilter-persistent issues),
everything seems just fine.
So not sure if it's really worth to follow this up, but I thought maybe
it helps you guys by ringing some bell.
Cheers,
Chris.
--- End Message ---
--- Begin Message ---
Hi!
On Tue, 2021-08-24 at 00:25:50 +0200, Christoph Anton Mitterer wrote:
> On Mon, 2021-08-23 at 23:36 +0200, Guillem Jover wrote:
> > Also where some of these "unknown" package really new installs
> > instead
> > of upgrades (for example the pxz above)?
> pxz was just an upgrade, ... I took some random samples for the others
> and it seems all of them were just upgrades.
>
> > Hard to tell, TBH.
>
> Well from my side you can also just close the ticket. The upgrade
> seemed to work fine - despite of those messages.
>
> Just wanted to let you guys know :-)
Sure, thanks. I think this might have been probably some old
misinteraction between dpkg and apt, which should already be fixed now
(related to the selections and available entries updates). So I'll be
closing this, but if you happen to hit this again, please either
reopen or file a new bug.
Thanks,
Guillem
--- End Message ---
