Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
Attempting a routine package upgrade via KDE's Discovery app
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
Clicked on "refresh" and then "update all"
   * What was the outcome of this action?
<html>Dependency resolution failed:<br/><br/>The following packages have unmet
dependencies:
  linux-image-amd64: Depends: linux-base-amd64 (= 7.1.13-1~bpo13+1) but
7.2.6-1~bpo13+1 is to be installed
</html>
   * What outcome did you expect instead?
I expected a successful kernel update as happened from 7.1.8 to 7.1.13. I had
not changed any settings in Discover. I have had no issues with my boot
partition. I tried to update using apt, but that too does not work. Neither
linux-base-amd64  nor linux-image-amd64 will upgrade. Otherwise, the system
function normally.

*** End of the template - remove these template lines ***

Hi,

Can you please provide the output of:

apt-get update
apt-get -t trixie-backports -s install linux-image-amd64

Regards,
Salvatore

The cloud team encountered similar failures during trixie-backports
image builds. See [1] for an example.  I believe that this was a
transient archive issue that was resolved when 7.2.6-1~bpo13+1 was
uploaded to trixie-backports.

It might be worth asking the archive operations team to investigate.

noah

1. https://salsa.debian.org/cloud-admin-team/debian-cloud-images-daily/-/jobs/10419119

This seems to be a bug in `apt`, I've filed https://bugs.debian.org/1150427

Cheers!

$ apt-get update
apt-get -t trixie-backports -s install linux-image-amd64

Reading package lists... Done
E: Could not open lock file /var/lib/apt/lists/lock - open (13:
Permission denied)
E: Unable to lock directory /var/lib/apt/lists/
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches
(13: Permission denied)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin -
RemoveCaches (13: Permission denied)
NOTE: This is only a simulation!
       apt-get 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
The following additional packages will be installed:
   linux-base linux-base-7.2.6+deb13-amd64 linux-base-amd64
linux-binary-7.2.6+deb13-amd64 linux-image-7.2.6+deb13-amd64
linux-modules-7.2.6+deb13-amd64
   linux-sysctl-defaults
Suggested packages:
   debian-kernel-handbook linux-doc-7.2
The following NEW packages will be installed:
   linux-base-7.2.6+deb13-amd64 linux-binary-7.2.6+deb13-amd64
linux-image-7.2.6+deb13-amd64 linux-modules-7.2.6+deb13-amd64
The following packages will be upgraded:
   linux-base linux-base-amd64 linux-image-amd64 linux-sysctl-defaults
4 upgraded, 4 newly installed, 0 to remove and 157 not upgraded.
Inst linux-base [4.12.1] (4.17~bpo13+1 Debian Backports:stable-backports
[all])
Inst linux-base-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Inst linux-binary-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Inst linux-modules-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Conf linux-base (4.17~bpo13+1 Debian Backports:stable-backports [all])
Inst linux-image-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Inst linux-sysctl-defaults [4.12.1] (4.17~bpo13+1 Debian
Backports:stable-backports [all])
Inst linux-image-amd64 [7.1.13-1~bpo13+1] (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64]) []
Inst linux-base-amd64 [7.1.13-1~bpo13+1] (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Conf linux-base-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Conf linux-binary-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Conf linux-modules-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Conf linux-image-7.2.6+deb13-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Conf linux-sysctl-defaults (4.17~bpo13+1 Debian
Backports:stable-backports [all])
Conf linux-image-amd64 (7.2.6-1~bpo13+1 Debian
Backports:stable-backports [amd64])
Conf linux-base-amd64 (7.2.6-1~bpo13+1 Debian Backports:stable-backports
[amd64])
$

Thank you for the quick response. I had previously tried

apt udpate
sudo apt upgrade

and I would get

Not upgrading:
   linux-base-amd64  linux-image-amd64

Summary:
   Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 2
$


Regards,
Jason A Banks

So as explained in #1150427, this is the intended `apt` behavior and there's currently no mechanism to work-around it automatically.
A manual solution for situation like this (a new dependency on a version not available in the "base" 500-prio suites) is to "re-tell" `apt` to install any needed dependencies from `trixie-backports` with
```
apt install -t trixie-backports linux-image-amd64
```

Cheers!

This is intentional APT policy and I don't plan to work around it.

Ben.

This worked. Report 1150352 can be closed.

Thanks you,
Jason A Banks