#777393 reportbug: package status determined from dpkg's desired state instead of current one

#777393#5
Date:
2015-02-07 22:56:18 UTC
From:
To:
Hi,

I filed bug #777387 using reportbug which contains:

Versions of packages network-manager-gnome depends on:
pn  network-manager                              <none>

That's strange, I know this package is installed. The problem is:

# dpkg -l network-manager
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name            Version     Architecture Description
+++-===============-==========-================================================================
ri  network-manager 0.9.10.0-5  amd64 network management framework (daemon and userspace tools)

So obviously reportbug uses the wrong status of the package, namely the
desired state instead of the current one.

I don't know why network-manager is considered for removal but assume it
was the result of a conflict resolution in aptitude which suggested to
remove the package (among many others). Afterwards I think I selected "Cancel pending actions".

Also in the following package dependence list (a few lines below) is a different error:
pn  python:any        <none>

aptitude tells me that python resolves this dependence, which is
installed: "ii  python".

Jens