Bug#990796: dpkg: warning: package not in status nor available database at line

[Christoph Anton Mitterer]

On Mon, 2021-08-23 at 23:36 +0200, Guillem Jover wrote:
> > => at this point /var/log/apt/term.log stops, which I guess it
> > shouldn't...
> 
> Because the upgrade continued with other package configurations that
> are
> not reflected there?

Yes, but this is probably what I've reported in #992309.


> W/o more context, and even then I'm not sure that might help much
> either, it's hard to tell what went wrong. In theory apt is supposed
> to update the available file so that dpkg knows about these packages.
> Given the term.log supposed truncation, and this, are you sure, say
> the system did not run out of space at some point?

Well at least I'd say it's very unlikely... these nodes have
sufficiently large system disks and I didn't have to clean them up
manually - so something would have needed to consume the whole space,
thereby causing the troubles, and then releasing it again.


> 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 :-)


Thanks,
Chris.

Bug#990796: dpkg: warning: package not in status nor available database at line

[Guillem Jover]

Control: tag -1 moreinfo unreproducible

Hi!

On Wed, 2021-07-07 at 19:00:34 +0200, Christoph Anton Mitterer wrote:
> Package: dpkg
> Severity: normal

> 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...

Because the upgrade continued with other package configurations that are
not reflected there?

> 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 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 
> [ 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)

W/o more context, and even then I'm not sure that might help much
either, it's hard to tell what went wrong. In theory apt is supposed
to update the available file so that dpkg knows about these packages.
Given the term.log supposed truncation, and this, are you sure, say
the system did not run out of space at some point?

Also where some of these "unknown" package really new installs instead
of upgrades (for example the pxz above)?

> So no idea why these:
>  dpkg: warning: package not in status nor available database at line
> occur.

That could happen if for some reason apt (or dpkg) failed to update the
available file when apt instructed it to.

> So not sure if it's really worth to follow this up, but I thought maybe
> it helps you guys by ringing some bell.

Hard to tell, TBH.

Thanks,
Guillem

Bug#990796: dpkg: warning: package not in status nor available database at line

[Christoph Anton Mitterer]

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: