Your message dated Fri, 31 Oct 2025 23:39:57 +0100
with message-id <[email protected]>
and subject line Re: Bug#1119805: Mismatch information between apt and dpkg
has caused the Debian Bug report #1119805,
regarding Mismatch information between apt and dpkg
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.)
--
1119805: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1119805
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: dpkg
Version: 1.22.21
When I run `apt-cache show bsdutils | grep Priority' I get:
```
Priority: required
```
However, if I run `cat /var/lib/dpkg/status | grep -A2 bsdutils', I get
```
Package: bsdutils
Status: install ok installed
Priority: standard
```
In one case the priority appears as `required' and in the other it appears as
`standard'.
I am using Debian GNU/Linux forky/sid, kernel 6.16.12+deb14+1-amd64.
Att.,
Carlos
--- End Message ---
--- Begin Message ---
Hi!
On Fri, 2025-10-31 at 15:36:54 +0000, Carlos Silva wrote:
> Package: dpkg
> Version: 1.22.21
> When I run `apt-cache show bsdutils | grep Priority' I get:
>
> ```
> Priority: required
> ```
>
> However, if I run `cat /var/lib/dpkg/status | grep -A2 bsdutils', I get
>
> ```
> Package: bsdutils
> Status: install ok installed
> Priority: standard
> ```
>
> In one case the priority appears as `required' and in the other it appears
> as `standard'.
While ideally the metadata in the repository and the one in the .deb
(which ends up in the dpkg status database) would match, that's not
always the case, as the archive operators apply overrides over it.
In this particular case, the archive is lagging behind and its
overrides need to be updated to match the .deb, see:
<https://bugs.debian.org/1119806>
But in any case there is no bug in dpkg, so closing.
Thanks,
Guillem
--- End Message ---
