Fwd: Problem with versions in repo being different from index.

2023-12-10 Thread Martyn Ayshford
-- Forwarded message - From: Martyn Ayshford Date: Sun, 10 Dec 2023 at 18:56 Subject: Problem with versions in repo being different from index. To: Hi Don't really know what I'm doing, however. Err:5 http://ftp.uk.debian.org/debian bookworm/main amd64 linux-libc-dev amd64

Bug#1057926: 403 Access Denied on some packages on official Debian repo

2023-12-10 Thread Juan J. Fernandez
Package: linux-image-6.1.0-14-rt-amd64 Version: 6.1.64-1 When I run apt upgrade command it shows Error 403 Access Denied Here is a transcript: E: Failed to fetch http://ftp.debian.org/debian/pool/main/l/linux-signed-amd64/linux-image-6.1.0-14-rt-amd64_6.1.64-1_amd64.deb 403 Access denied -

Bug#1057967: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-10 Thread Kevin Price
Package: linux-image-6.1.0-15-amd64 Version: 6.1.66-1 Severity: critical Control: -1 notfound 6.1.64-1 When booting 6.1.0-15, my physical amd64/bookworm/gnome computer misbehaves in many ways, rendering it largely unusable. With kernels up to 6.1.0-13, and even briefly with the otherwise broken

Re: Fwd: Problem with versions in repo being different from index.

2023-12-10 Thread Martyn Ayshford
Thanks. The packages file had been updated I saw timestamp change - after I did apt update and upgrade it all worked. Guess I was just unlucky. brought my proxmox cluster up and whilst all up ran an update on each member. Caught that window when things were a problem. regards Martyn On

Re: Fwd: Problem with versions in repo being different from index.

2023-12-10 Thread Salvatore Bonaccorso
Hi, On Sun, Dec 10, 2023 at 07:01:39PM +, Martyn Ayshford wrote: > -- Forwarded message - > From: Martyn Ayshford > Date: Sun, 10 Dec 2023 at 18:56 > Subject: Problem with versions in repo being different from index. > To: > > > Hi > > Don't really know what I'm doing,

Re: 6.1.0-15/6.1.66-1 broken too?

2023-12-10 Thread Kevin Price
I confirm that 6.1.66-1 (6.1.0-15) severely breaks my amd64/bookworm/gnome physical machine, which runs fine with 6.1.52-1 and 6.1.55-1. Am 10.12.23 um 20:24 schrieb Andrew M.A. Cater: > On Sun, Dec 10, 2023 at 08:02:03PM +0100, Kevin Price wrote: >> Am 09.12.23 um 19:09 schrieb Dan Ritter: >>>

Re: 6.1.0-15/6.1.66-1 broken too?

2023-12-10 Thread Stephan Verbücheln
Hello everybody I can confirm the same problems. At first I thought the network problem was due to proprietary Broadcom driver because network connectivity was the most obvious problem. However, most problems persisted after removing the driver. I do not have any other proprietary or custom

linux-signed-arm64_6.1.66+1_source.changes ACCEPTED into proposed-updates

2023-12-10 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Dec 2023 16:48:39 +0100 Source: linux-signed-arm64 Architecture: source Version: 6.1.66+1 Distribution: bookworm-proposed-updates Urgency: medium Maintainer: Debian

Bug#1057843: Guidelines for affected users

2023-12-10 Thread Dale Richards
On Sun, 10 Dec 2023 07:56:36 + Stephan =?ISO-8859- 1?Q?Verb=FCcheln?= wrote: > > - Is it safe to assume that other filesystems (like BTRFS) are not > affected? > - Does this cause filesystem corruption or only file corruption? > - Does this affect metadata or only file contents? > - Is there

linux-signed-i386_6.1.66+1_source.changes is NEW

2023-12-10 Thread Debian FTP Masters
Mapping bookworm-proposed-updates to proposed-updates. binary:acpi-modules-6.1.0-15-686-di is NEW. binary:acpi-modules-6.1.0-15-686-pae-di is NEW. binary:ata-modules-6.1.0-15-686-di is NEW. binary:ata-modules-6.1.0-15-686-pae-di is NEW. binary:btrfs-modules-6.1.0-15-686-di is NEW.

Bug#1057843: Guidelines for affected users which use etx4

2023-12-10 Thread Umberto Zappi
Are there any guidelines for affected users who already updated before they got the warning? For example, is it fine to start with the previous kernel 6.1.0-13-amd64 (version 6.1.55-1) ? Thanks UmbertoZ.

Bug#1057843: Guidelines for affected users

2023-12-10 Thread Tim Connors
Meanwhile, can the ftp admins pull this faulty version? I just managed to download and install this, but fortunately didn't reboot on all of my systems before coming across this bug via LWN via reddit. If you're in such a pickle as myself, you're able to get around it for now by: apt install

Bug#1057843: Guidelines for affected users

2023-12-10 Thread Stephan Verbücheln
Are there any guidelines for affected users who already updated before they got the warning? Interesting questions for affected users: - Is it safe to assume that other filesystems (like BTRFS) are not affected? - Does this cause filesystem corruption or only file corruption? - Does this affect

linux-signed-amd64_6.1.66+1_source.changes ACCEPTED into proposed-updates

2023-12-10 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Dec 2023 16:48:39 +0100 Source: linux-signed-amd64 Architecture: source Version: 6.1.66+1 Distribution: bookworm-proposed-updates Urgency: medium Maintainer: Debian

Processing of linux-signed-i386_6.1.66+1_source.changes

2023-12-10 Thread Debian FTP Masters
linux-signed-i386_6.1.66+1_source.changes uploaded successfully to localhost along with the files: linux-signed-i386_6.1.66+1.dsc linux-signed-i386_6.1.66+1.tar.xz Greetings, Your Debian queue daemon (running on host usper.debian.org)

linux-signed-i386_6.1.66+1_source.changes ACCEPTED into proposed-updates

2023-12-10 Thread Debian FTP Masters
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 09 Dec 2023 16:48:39 +0100 Source: linux-signed-i386 Architecture: source Version: 6.1.66+1 Distribution: bookworm-proposed-updates Urgency: medium Maintainer: Debian

Processed: linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable

2023-12-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1057967 6.1.64-1 Bug #1057967 [linux-image-6.1.0-15-amd64] linux-image-6.1.0-15-amd64 renders my physical bookworm/gnome computer largely unusable There is no source info for the package 'linux-image-6.1.0-15-amd64' at version

Processing of iproute2_6.6.0-1~bpo12+1_source.changes

2023-12-10 Thread Debian FTP Masters
iproute2_6.6.0-1~bpo12+1_source.changes uploaded successfully to localhost along with the files: iproute2_6.6.0-1~bpo12+1.dsc iproute2_6.6.0-1~bpo12+1.debian.tar.xz iproute2_6.6.0-1~bpo12+1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

iproute2_6.6.0-1~bpo12+1_source.changes ACCEPTED into stable-backports

2023-12-10 Thread Debian FTP Masters
Thank you for your contribution to Debian. Mapping bookworm-backports to stable-backports. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 10 Dec 2023 13:12:08 + Source: iproute2 Architecture: source Version: 6.6.0-1~bpo12+1 Distribution: bookworm-backports

Bug#1057260: iwlwifi: `N' invalid for parameter `enable_ini'

2023-12-10 Thread Prabin Dahal
Hi, I also had iwlwifi.conf in /etc/modprobe.d/ folder. I guess, the wifi connection was dropping randomly and I followed a stackoverflow answer where it suggested to add `enable_ini=N`to prevent the firmware to crash. Thank you for the information. I removed that file and now the wifi works on

Bug#1057260: iwlwifi: `N' invalid for parameter `enable_ini'

2023-12-10 Thread Salvatore Bonaccorso
Hi, On Sun, Dec 10, 2023 at 03:40:30PM +0100, Prabin Dahal wrote: > Hi, > > I also had iwlwifi.conf in /etc/modprobe.d/ folder. I guess, the wifi > connection was dropping randomly and I followed a stackoverflow answer > where it suggested to add `enable_ini=N`to prevent the firmware to crash. >

Bug#1057843: linux-image-6.1.0-13-amd64: Workaround

2023-12-10 Thread Sebastian Niehaus
Package: src:linux Followup-For: Bug #1057843 FYI: there is a nice workaround to avoid upgrading to the affected kernel: https://octodon.social/@alienghic/111554146479489358 ===[ snip ] This should block just the buggy kernel. Which might