Hi. On Thu, May 30, 2019 at 09:10:55AM -0400, Greg Wooledge wrote: > On Thu, May 30, 2019 at 01:00:19PM -0000, Curt wrote: > > On 2019-05-30, Greg Wooledge <wool...@eeg.ccf.org> wrote: > > > But libcap2-bin is priority important in both stretch and buster. > > > > Why is my Stretch apt-cache command telling me it's priority optional? > > Or am I once again missing some essential thing? > > Uh... > > arc3:~$ dpkg -s libcap2-bin | grep -i priority > Priority: important > arc3:~$ apt-cache show libcap2-bin | grep -i priority > Priority: optional
Both show "optional" to me BTW. > OK, I have no freaking idea what this means. strace(1) to the rescue. "dpkg -s" gets package state from /var/lib/dpkg/status. "apt-cache" also uses /var/lib/apt/lists/*. Basically your result tells that libcap2-bin is "optional" from the repository POV, but your local package database thinks it's "important". And in this case I trust the repository and have to assume that your local package database is somehow corrupt. Reco
