[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: apt ignores bullseye-backports



Cc'ing Reportbug Maintainers.

On 2023-11-14 14:51:18 +0100, Vincent Lefevre wrote:
> Going back to what reportbug says, it still outputs
> 
> [...]
> Getting status for linux-image-6.1.0-13-amd64...
> Verifying package integrity...
> Checking for newer versions at madison and https://ftp-master.debian.org/new.html
> 
> Your version (6.1.55-1) of linux-image-6.1.0-13-amd64 appears to be out of date.
> The following newer release(s) are available in the Debian archive:
>   bullseye-backports (backports-policy): 6.1.55+1~bpo11+1
> Please try to verify if the bug you are about to report is already addressed by these releases.  Do you still want to file a report [y|N|q|?]? 
> 
> So I've looked at https://ftp-master.debian.org/new.html with Firefox
> and "linux-image" doesn't appear anywhere. So the information comes
> from madison.
> 
> $ apt-cache madison linux-image-6.1.0-13-amd64
> linux-image-6.1.0-13-amd64 |   6.1.55-1 | https://ftp.debian.org/debian stable/main amd64 Packages
> linux-signed-amd64 |   6.1.55+1 | https://ftp.debian.org/debian stable/main Sources
> 
> No mentions of 6.1.55+1~bpo11+1, so this is more and more confusing.

After removing bullseye-backports from my sources lists and doing
"apt update", I've tried

  strace -o str.out -f -s 999999 reportbug linux-image-6.1.0-13-amd64

but in the strace output, the string "bpo11" appears in 2 places only:

[...] manpages-de (<< 4.17.0-2~bpo11+1), manpages-fr (<< 4.17.0-2~bpo11+1) [...]

(thus unrelated to this issue) and in the message

193537 write(1, "  bullseye-backports (backports-policy): 6.1.55+1~bpo11+1\n", 58) = 58

So I'm wondering where this information comes from.

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


Reply to: