Your message dated Fri, 11 Aug 2023 07:41:49 +0200
with message-id <znxkhcthkbfti...@eldamar.lan>
and subject line Re: Bug#1043438: linux-headers-amd64: Package dependecy is
currently broken
has caused the Debian Bug report #1043438,
regarding linux-headers-amd64 cannot be upgraded to 6.1.38-3 (dependency is
unavailable)
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 ow...@bugs.debian.org
immediately.)
--
1043438: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1043438
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-headers-amd64
Version: 6.1.38-2
Severity: important
X-Debbugs-Cc: d...@forkbox.net
Dear Maintainer,
It looks like linux-headers-amd64 6.1.38-3 depends on
linux-headers-6.1.0-11-amd64 (=6.1.38-3), which makes sense.
Unfortunately, the only version of linux-headers-6.1.0-11-amd64
available is 6.1.38-4. There is no newer version of linux-headers-amd64
available right now.
I marked this "important" because trying to upgrade now will upgrade the
kernel, but not the headers. This means my system's latest kernel has no
headers, which breaks DKMS, and in particular, nvidia-kernel-dkms.
My system didn't attempt to bring up a GUI without nvidia_drm loaded.
I'm not entirely sure I understand what else went wrong here. I think I
tried reinstalling nvidia-kernel-dkms, which skipped the current kernel
because it couldn't find headers, but seemed to also skip the previous
kernel. This would explain why, when I tried rebooting into
6.1.0-10-amd64, I still had no GUI. Reinstalling nvidia-kernel-dkms
while booted into 6.1.0-10-amd64 got my GUI back.
-- System Information:
Debian Release: 12.1
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-10-amd64 (SMP w/8 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages linux-headers-amd64 depends on:
ii linux-headers-6.1.0-10-amd64 6.1.38-2
linux-headers-amd64 recommends no packages.
linux-headers-amd64 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Fri, Aug 11, 2023 at 12:33:54AM -0500, Caleb McKay wrote:
> Package: linux-headers-amd64
> Version: 6.1.38-3
> Severity: important
> X-Debbugs-Cc: ca...@candj.us
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
> * What led up to the situation?
> Atempted to install package linux-headers-amd64 (6.1.38-3)
> * What exactly did you do (or not do) that was effective (or
> ineffective)?
> Package fails to install because it depends on linux-headers-6.1.0-11-amd64
> (6.1.38-3) but only version 6.1.38-4 is available in the archive.
> * What was the outcome of this action?
> Package fails to install with error:
> The following packages have unmet dependencies:
> linux-headers-amd64 : Depends: linux-headers-6.1.0-11-amd64 (= 6.1.38-3) but
> 6.1.38-4 is to be installed
> * What outcome did you expect instead?
> Package to install.
This is known, there was a hick-up on releasing the linux updates
which should be resolved as soon FTP master unbreak the situation.
Then a regular DSA announcement will go out.
Regards,
Salvatore
--- End Message ---
