Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #80877 > unrolled thread

Bug#1055931: apt ignores bullseye-backports

Started byVincent Lefevre <vincent@vinc17.net>
First post2023-11-14 15:00 +0100
Last post2023-11-16 18:10 +0100
Articles 3 — 1 participant

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Bug#1055931: apt ignores bullseye-backports Vincent Lefevre <vincent@vinc17.net> - 2023-11-14 15:00 +0100
    Bug#1055931: apt ignores bullseye-backports Vincent Lefevre <vincent@vinc17.net> - 2023-11-14 15:20 +0100
      Bug#1055931: apt ignores bullseye-backports Vincent Lefevre <vincent@vinc17.net> - 2023-11-16 18:10 +0100

#80877 — Bug#1055931: apt ignores bullseye-backports

FromVincent Lefevre <vincent@vinc17.net>
Date2023-11-14 15:00 +0100
SubjectBug#1055931: apt ignores bullseye-backports
Message-ID<HA27n-5oPf-5@gated-at.bofh.it>
On 2023-11-14 13:45:21 +0100, Vincent Lefevre wrote:
> But "apt show -a linux-image-6.1.0-13-amd64" just gives the 6.1.55-1
> version (no 6.1.55+1~bpo11+1 version), and
> 
>   apt install -t bullseye-backports linux-image-6.1.0-13-amd64
> 
> also thinks that 6.1.55-1 is the version to be installed.

This may be specific to the kernel image. The following is rather
confusing:

$ apt install -s -t bullseye-backports linux-image-6.1.0-13-amd64/bullseye-backports
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-image-6.1.0-13-amd64 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  linux-image-6.1.0-13-amd64-unsigned

E: Release 'bullseye-backports' for 'linux-image-6.1.0-13-amd64' was not found
$ apt install -s -t bullseye-backports linux-image-6.1.0-13-amd64-unsigned/bullseye-backports
NOTE: This is only a simulation!
      apt needs root privileges for real execution.
      Keep also in mind that locking is deactivated,
      so don't depend on the relevance to the real current situation!
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package linux-image-6.1.0-13-amd64-unsigned is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  linux-image-6.1.0-13-amd64

E: Release 'bullseye-backports' for 'linux-image-6.1.0-13-amd64-unsigned' was not found

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.

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

[toc] | [next] | [standalone]


#80878

FromVincent Lefevre <vincent@vinc17.net>
Date2023-11-14 15:20 +0100
Message-ID<HA2qJ-5paI-3@gated-at.bofh.it>
In reply to#80877
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)

[toc] | [prev] | [next] | [standalone]


#80887

FromVincent Lefevre <vincent@vinc17.net>
Date2023-11-16 18:10 +0100
Message-ID<HAO2m-5SAg-17@gated-at.bofh.it>
In reply to#80878
Hi Nis,

On 2023-11-16 17:31:13 +0100, Nis Martensen wrote:
> On 14.11.2023 15.17, Vincent Lefevre wrote:
> >> 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
> 
> > So I'm wondering where this information comes from.
> 
> I can find "6.1.55+1~bpo11+1" in https://ftp-master.debian.org/new.822
> so it must come from there.

Thanks. I had first looked at

  https://ftp-master.debian.org/new.html

(as output by reportbug), and it doesn't appear on this page
(I searched for both "linux" and "6.1.55"). Note that clicking
on "Click to toggle all/binary-NEW packages" does not make this
kernel appear either.

FYI, I later looked at https://ftp-master.debian.org/new.822 too
(as I could see it in the strace output), but only searched for
linux-image there, explaining that I didn't find it either (it
actually appears as linux-signed-amd64).

At the bottom of the new.html page:
"You can also look at the RFC822 version."

But why are the contents different? (linux-signed-amd64 appears
only in the RFC822 version.)

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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web