Bug#614143: os-prober: generated linux entries don't use UUIDs for root= parameter

11-12-13 by Marcin but it seemed to corrupt my grub.cfg (not surprising, given the age and that it was perhaps for CentOS). My hack solution was to change /etc/grub.d/30_os-prober line 248 to be: |linux ${LKERNEL} root=UUID=${boot_device_id}| ...which I assume is a Bad Idea for some reason,

Re: Uploading linux (6.12.37-1)

Hi Cyril, On Wed, Jul 16, 2025 at 08:12:28AM +0200, Cyril Brulebois wrote: > Hi, > > Salvatore Bonaccorso (2025-07-16): > > Ack. But I think then at least 6.12.38-1 needs to follow now. The > > reason is the following, 6.12.38 was a single commit upload fixing a > > problem with the TSA itigatio

Re: Uploading linux (6.12.37-1)

Hi, Salvatore Bonaccorso (2025-07-16): > Ack. But I think then at least 6.12.38-1 needs to follow now. The > reason is the following, 6.12.38 was a single commit upload fixing a > problem with the TSA itigations. I was not hurring it just after the > import given we had not yet the microcode part

Re: Uploading linux (6.12.37-1)

unstable, which will be 6.12.37-1, though depending on an ack/nack > > from SRM and/or debian-boot. > > That was ACK'd and uploaded, but we're still lacking linux-signed-arm64: > it's in NEW, and it'd be great to have it accepted. Ack, given that see below. &

Re: Uploading linux (6.12.37-1)

Hi kernel and ftp teams, Salvatore Bonaccorso (2025-07-10): > I would like to upload next version of the 6.12.y stable series to > unstable, which will be 6.12.37-1, though depending on an ack/nack > from SRM and/or debian-boot. That was ACK'd and uploaded, but we're still l

Re: Uploading linux (6.12.37-1)

Hi Salvatore, Salvatore Bonaccorso (2025-07-10): > I would like to upload next version of the 6.12.y stable series to > unstable, which will be 6.12.37-1, though depending on an ack/nack > from SRM and/or debian-boot. As far as I'm concerned, feel free to go ahead. Cheers, -- Cyril Brulebois

Uploading linux (6.12.37-1)

er support the cgroups v1 API. https://salsa.debian.org/kernel-team/linux/-/commit/4c797eb8f8e2c6074c707cd906a452a2167bc67f (we asked upstream if that can be officially reverted, but we guess we will need to ship this patch indepently for trixie's lifecycle). * rtw89: Enable RTW89_8851BE, R

Bug#1108599: firmware-linux-free: please add support MT7921/MT7925 WIFI Combo Cards

aW4gKOael+aZuuaWjCk=?= > > wrote: > > > Package: firmware-linux-free > > > Version: 20241210-2 > > > Severity: normal > > > > > > Dear Maintainer, > > > > > > 1. Please help to include firmware for MT7921 and MT7925 WIFI Combo > > >

Re: Uploading linux (6.12.35-1)

Hi Cyril, On Thu, Jul 03, 2025 at 07:58:22AM +0200, Salvatore Bonaccorso wrote: > Hi Cyril, > > On Thu, Jul 03, 2025 at 01:33:34AM +0200, Cyril Brulebois wrote: > > Salvatore Bonaccorso (2025-06-29): > > > Ack in this case holding back the unstable upload until having your > > > "go". Good luck

Re: Uploading linux (6.12.35-1)

Hi Cyril, On Thu, Jul 03, 2025 at 01:33:34AM +0200, Cyril Brulebois wrote: > Salvatore Bonaccorso (2025-06-29): > > Ack in this case holding back the unstable upload until having your > > "go". Good luck with the next d-i release! > > Thanks! Feel free to go ahead now. Thank you, will finalize

Re: Uploading linux (6.12.35-1)

Salvatore Bonaccorso (2025-06-29): > Ack in this case holding back the unstable upload until having your > "go". Good luck with the next d-i release! Thanks! Feel free to go ahead now. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- Release

Processed: Re: firmware-linux-free: please add support MT7921/MT7925 WIFI Combo Cards

Processing control commands: > reassign -1 hw-detect Bug #1108599 [firmware-linux-free] firmware-linux-free: please add support MT7921/MT7925 WIFI Combo Cards Bug reassigned from package 'firmware-linux-free' to 'hw-detect'. No longer marked as found in versions f

Re: firmware-linux-free: please add support MT7921/MT7925 WIFI Combo Cards

Control: reassign -1 hw-detect Control: tag -1 moreinfo On Tue, 1 Jul 2025 08:06:34 + =?utf- 8?B?TWFjcGF1bCBMaW4gKOael+aZuuaWjCk=?= wrote: > Package: firmware-linux-free > Version: 20241210-2 > Severity: normal > > Dear Maintainer, > > 1. Please help to include fi

Re: Uploading linux (6.12.35-1)

> > I'd like to get a release going within a few days, so it'd be great if > you could hold off for a little while. I /think/ we could manage if > linux* were updated in unstable but it's a little safer to avoid that > (if that doesn't hold you back too much). Ack in this case holding back the unstable upload until having your "go". Good luck with the next d-i release! Regards, Salvatore

Re: Uploading linux (6.12.35-1)

I believe it's beneficial to already pick this in advance > still. Yeah, that looked like a worrisome regression… I'd like to get a release going within a few days, so it'd be great if you could hold off for a little while. I /think/ we could manage if linux* were updated in uns

Uploading linux (6.12.35-1)

Hi I would like to upload next version of the 6.12.y stable series to unstable, which would be 6.12.35-1. This is a bigger one than usual. The update would consist of two stable series versions 6.12.34 and 6.12.35 which were released in and after the 6.16 merge window. Depending on upstream timing

Re: Uploading linux (6.12.33-1)

Hi Salvatore, On 19-06-2025 11:33, Salvatore Bonaccorso wrote: I'm glad to take any advice from both you as release team and specifically as well d-i folks on where we should start to draw the line. From the Release Team point of view, we'll let you know explicitly when we want you to stop u

Uploading linux (6.12.33-1)

Hi I would like to upload next version of the 6.12.y stable series to unstable, which is 6.12.33-1. This was a very small release itself consisting of only of 25 commits, the main reason for this upload is bringing in the packaging changes mentioned last time about moving the package revision and

Re: Uploading linux (6.12.32-1)

Hi Cyril, On Thu, Jun 05, 2025 at 10:23:08PM +0200, Cyril Brulebois wrote: > Hi, > > Salvatore Bonaccorso (2025-06-05): > > I would like to upload the next version of the 6.12.y stable series to > > unstable (once linux/6.12.30-1 migrates to testing). There are two > &g

Re: Uploading linux (6.12.32-1)

Hi, Salvatore Bonaccorso (2025-06-05): > I would like to upload the next version of the 6.12.y stable series to > unstable (once linux/6.12.30-1 migrates to testing). There are two > upstream stable versions imported, 6.12.31 and 6.12.32 where 6.12.31 > was of considerable size (n

Uploading linux (6.12.32-1)

Hi I would like to upload the next version of the 6.12.y stable series to unstable (once linux/6.12.30-1 migrates to testing). There are two upstream stable versions imported, 6.12.31 and 6.12.32 where 6.12.31 was of considerable size (note there is onging merge window for 6.16 ongoing and from

Re: Uploading linux (6.12.30-1)

Hi Cyril, On Wed, May 28, 2025 at 01:43:10PM +0200, Cyril Brulebois wrote: > Hi Salvatore, > > Salvatore Bonaccorso (2025-05-27): > > I would like to upload the next version of the 6.12.y. stable series > > to unstable, this time with the aim to really have it migrating to > > testing (covering

Re: Uploading linux (6.12.30-1)

Hi Salvatore, Salvatore Bonaccorso (2025-05-27): > I would like to upload the next version of the 6.12.y. stable series > to unstable, this time with the aim to really have it migrating to > testing (covering the previous ITS mitigations, but blocked by > #1106070). This is still fine with me re

Uploading linux (6.12.30-1)

to have some still important changes to go in, they relate to the already uploaded linux-base change adding the linux-run-hooks command). Regards, Salvatore signature.asc Description: PGP signature

Searching for Linux 6.12 / Trixie supported Wi-Fi 7 chips!

[ Dropping leader@, focus on the actual hardware chase, and adding debian-kernel@ in case I manage to nerd-snipe some hardware guru ] Cyril Brulebois (2025-05-25): > For example: > - MSI BE6500 (~ 80 EUR) > - NEWFAST BE6500 (~ 70 EUR) > - TP-Link BE6500 (~ 70 EUR) > > I haven't really l

Re: Bug#1106070: linux-image-6.12.29-amd64: loop device cannot mount live squashfs any more

fail to boot. > > The change happened between 20250518T201633Z and 20250519T021902Z, which > matches the upload of 6.12.29 > (https://tracker.debian.org/news/1646619/accepted-linux-signed-amd64-612291-source-into-unstable/) > at 20250518T230426Z. > > To reproduce: >

Re: Bug#1106070: Fwd: linux-image-6.12.29-amd64: loop device cannot mount live squashfs any more

Roland Clobus (2025-05-19): > I forgot the @lists.debian.org, so I'll forward the bugreport. > (It is #1106070) Thank you very much! Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- Release team member -- Freelance Consultant signature.asc

Bug#1106070: Fwd: linux-image-6.12.29-amd64: loop device cannot mount live squashfs any more

I forgot the @lists.debian.org, so I'll forward the bugreport. (It is #1106070) With kind regards, Roland Clobus Forwarded Message Subject: linux-image-6.12.29-amd64: loop device cannot mount live squashfs any more Date: Mon, 19 May 2025 12:15:10 +0200 From: Roland C

Re: Uploading linux (6.12.29-1)

Hi Salvatore, Salvatore Bonaccorso (2025-05-18): > With the knowledge of beeing now in the hard freeze (i.e this will > later on require as well an unblock request): I would like to upload > the next version of the 6.12.y stable series to unstable, with the aim > that this should migrate to trixi

Uploading linux (6.12.29-1)

Hi With the knowledge of beeing now in the hard freeze (i.e this will later on require as well an unblock request): I would like to upload the next version of the 6.12.y stable series to unstable, with the aim that this should migrate to trixie. Two new stable versions are imported 6.12.28 and 6.

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

gt; > Version: 6.1.137-1 > > Severity: important > > X-Debbugs-Cc: r...@graphiant.com > > > > rob@graph-dev-bookworm:~$ sudo modprobe watchdog > > modprobe: ERROR: could not insert 'watchdog': Bad message > > > > Using extract-module-sig

Re: Bug#1105882: unblock: util-linux/2.41-5

ve them > [x] attach debdiff against the package in testing > > [ Other info ] > util-linux builds udebs. Thanks for the explanations, from the changelog entry and the bug report's normal severity alone, I had decided not to ask/wonder about this particular package for RC 1. The ud

Bug#1105882: unblock: util-linux/2.41-5

Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: util-li...@packages.debian.org, debian-boot@lists.debian.org Control: affects -1 + src:util-linux Please unblock package util-linux. [ Reason ] Helmut Grohne requested in

Re: Bug#1076723: grub-common: duplicate GNU/Linux in menuentry and submenu lines of /boot/grub/grub.cfg

Hello, Mate Kukri (2025-01-09): > Sorry I was off for the holidays but the fix for this was discussed > and is planned very soon. Sorry to bother you again, but since that's the first thing I'm seeing with a freshly installed trixie system (with a tentative D-I Trixie RC 1 image), here's a littl

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

Adam D. Barratt (2025-05-13): > The d-i diffs look good, thanks. > > I've not seen any suggestion to change the plan, so please go ahead > with d-i-n-i when convenient. debdiffs for the locally-built d-i-n-i binaries didn't look crazy, source package on its way; please let me know if anything po

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

[CC list trimmed] On Tue, 2025-05-13 at 02:06 +0200, Cyril Brulebois wrote: > Cyril Brulebois (2025-05-12): > > Unless you tell me otherwise I'll stick to testing then uploading > > d-i > > with the ABI bumped to 35. (And it can still be rejected from pu- > > NEW > > anyway?) > > Local testing l

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

Cyril Brulebois (2025-05-12): > Unless you tell me otherwise I'll stick to testing then uploading d-i > with the ABI bumped to 35. (And it can still be rejected from pu-NEW > anyway?) Local testing looked good, so src:debian-installer is on its way. Please let me know if and when I should move o

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

Hi, Jonathan Wiltshire (2025-05-12): > We discussed briefly just now and decided that: > > - as it's "just" amd64 watchdog and w83977f_wdt modules, and It's been a while since I last toyed with watchdogs (and those needed explicit actions to be enabled anyway), but I'd expect those not to be s

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

watchdog': Bad message > > > > > > Using extract-module-sig.pl from > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/scripts/extract-module-sig.pl > > > shows there is no signature present for the watchdog kernel object > >

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

; > X-Debbugs-Cc: r...@graphiant.com > > > > rob@graph-dev-bookworm:~$ sudo modprobe watchdog > > modprobe: ERROR: could not insert 'watchdog': Bad message > > > > Using extract-module-sig.pl from > > https://git.kernel.org/pub/scm/linux/ke

Re: Bug#1105164: linux-image-6.1.0-35-amd64: watchdog kernel module load errors with "Bad message"

obe: ERROR: could not insert 'watchdog': Bad message > > Using extract-module-sig.pl from > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/plain/scripts/extract-module-sig.pl > shows there is no signature present for the watchdog kernel object > file: &

Re: Uploading linux (6.12.26-1)

make it in time to have it > > migrated within the 10 days, but if we see there are no major > > regression we can ask release team to migrate it earlier if this d-i > > release would approach. > > After just a quick look, linux* seem rather OK to me. Are you happy with >

Re: Uploading linux (6.12.26-1)

n we can ask release team to migrate it earlier if this d-i > release would approach. After just a quick look, linux* seem rather OK to me. Are you happy with their state (from the kernel team point of view) and with their possibly getting into testing as they are, in a matter of hours? Ch

Bug#1104907: marked as done (base-installer: linux-image-*-signed-template should not be in kernel selection)

Your message dated Sat, 10 May 2025 17:34:05 + with message-id and subject line Bug#1104907: fixed in base-installer 1.224 has caused the Debian Bug report #1104907, regarding base-installer: linux-image-*-signed-template should not be in kernel selection to be marked as done. This means

Bug#1104907: base-installer: linux-image-*-signed-template should not be in kernel selection

On 10/05/2025 at 01:48, Cyril Brulebois wrote: Pascal Hambourg (2025-05-08): When booting the installer with an amd64 netboot image in expert mode, linux-image-amd64-signed-template is wrongly included in the kernel selection dialog. See attached screenshot. Merge request for amd64, arm64

Bug#1104907: base-installer: linux-image-*-signed-template should not be in kernel selection

Hi, Pascal Hambourg (2025-05-08): > When booting the installer with an amd64 netboot image in expert mode, > linux-image-amd64-signed-template is wrongly included in the kernel > selection dialog. See attached screenshot. > > Merge request for amd64, arm64 and ri

Bug#1104907: base-installer: linux-image-*-signed-template should not be in kernel selection

Package: src:base-installer Version: 1.223 Severity: minor Tags: patch Dear maintainer, When booting the installer with an amd64 netboot image in expert mode, linux-image-amd64-signed-template is wrongly included in the kernel selection dialog. See attached screenshot. Merge request for

Re: Uploading linux (6.12.26-1)

Hi Cyril, On Tue, May 06, 2025 at 11:26:39PM +0200, Cyril Brulebois wrote: > Salvatore Bonaccorso (2025-05-06): > > Thanks, I have uploaded 6.1.27-1 to unstable and is now in the NEW > > queue. I think we will not be able to make it in time to have it > > migrated within the 10 days, but if we se

Re: Uploading linux (6.12.26-1)

Salvatore Bonaccorso (2025-05-06): > Thanks, I have uploaded 6.1.27-1 to unstable and is now in the NEW > queue. I think we will not be able to make it in time to have it > migrated within the 10 days, but if we see there are no major > regression we can ask release team to migrate it earlier if t

Re: Uploading linux (6.12.26-1)

the > > intention of uploading another linux version 6.12.26-1 to unstable > > (planned 6.12.26-1, but might be 6.12.27-1 depending on progress in > > next days) > > > > linux/6.12.25-1 should migrate to testing in the next 2 days. > > > > Debian Boot how is th

Re: Uploading linux (6.12.26-1)

Hi Salvatore, Salvatore Bonaccorso (2025-05-05): > Following the tradition to keep up with upstream stable releases and > aiming to have a trixie close to upstream, this is to declare the > intention of uploading another linux version 6.12.26-1 to unstable > (planned 6.12.26-1,

Uploading linux (6.12.26-1)

Hi Following the tradition to keep up with upstream stable releases and aiming to have a trixie close to upstream, this is to declare the intention of uploading another linux version 6.12.26-1 to unstable (planned 6.12.26-1, but might be 6.12.27-1 depending on progress in next days) linux

Re: Uploading linux (6.12.24-1)

aiming to have a trixie close to upstream, I would like to upload >> linux version 6.12.24-1 to unstable. >> >> 6.12.22-1 has moved already to testing so far. >> >> Debian Boot, Release team how is the timing with respect potential d-i >> work? >> >

Re: Uploading linux (6.12.24-1)

Hi all, On Mon, Apr 21, 2025 at 02:02:19PM +0200, Salvatore Bonaccorso wrote: > Hi > > Following the tradition to keep up with upstream stable releases and > aiming to have a trixie close to upstream, I would like to upload > linux version 6.12.24-1 to unstable. > > 6.12.2

Re: Uploading linux (6.12.24-1)

Hi Adrian, On Mon, Apr 21, 2025 at 06:45:49PM +0200, John Paul Adrian Glaubitz wrote: > Hi Salvatore, > > On Mon, 2025-04-21 at 14:02 +0200, Salvatore Bonaccorso wrote: > >* [arm64,powerpc,ppc64,ppc64el,riscv64,s390x] Enable KALLSYMS_ALL on > > all architectures where DEBUG_INFO_BTF is o

Re: Uploading linux (6.12.24-1)

Hi Salvatore, On Mon, 2025-04-21 at 14:02 +0200, Salvatore Bonaccorso wrote: >* [arm64,powerpc,ppc64,ppc64el,riscv64,s390x] Enable KALLSYMS_ALL on > all architectures where DEBUG_INFO_BTF is on (Closes: #1100634) >* hfs/hfsplus: fix slab-out-of-bounds in hfs_bnode_read_key > > (note

Re: Uploading linux (6.12.24-1)

Hi, Salvatore Bonaccorso (2025-04-21): > Debian Boot, Release team how is the timing with respect potential d-i > work? That's fine for d-i. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- Release team member -- Freelance Consultant sign

Uploading linux (6.12.24-1)

Hi Following the tradition to keep up with upstream stable releases and aiming to have a trixie close to upstream, I would like to upload linux version 6.12.24-1 to unstable. 6.12.22-1 has moved already to testing so far. Debian Boot, Release team how is the timing with respect potential d-i

Uploading linux (6.12.22-1)

Hi I would like to upload linux version 6.12.22-1 to unstable. It imports 6.12.22 on top of the current packaging and is a rather small stable series upload. The next one will actually be the big bump after the 6.15 merge window closed, so I would like to have that separated. There are on top

Uploading linux (6.12.21-1)

Hi I would like to upload linux version 6.12.21-1 to unstable. It imports 6.12.21 only on top of the current packaging, which includes security fixes. There are on top additional changes for the packaging and adding support. In details they are the following: * lintian: Restore override for

Uploading linux (6.12.20-1)

Hi I would like to upload linux version 6.12.20-1 to unstable. 6.12.19-1 has migrated to testing. It imports 6.12.20 on top of the current packaging. On top there are some packaging changes as follows: * drivers/nvme/target: Enable NVME_TARGET_PASSTHRU * drivers/nvme/target: Enable

Re: Uploading linux (6.12.19-1)

Hi Emilio, On Tue, Mar 18, 2025 at 04:18:32PM +0100, Emilio Pozuelo Monfort wrote: > On 15/03/2025 07:27, Salvatore Bonaccorso wrote: > > Hi > > > > I would like to upload linuxversion 6.12.19-1 to unstable (with the > > aim that this should migrate to testing for trixie). > > > > It imports 6.1

Bug#1092949: debian-installer could propose installing linux-image-cloud when run inside a VM

Hi Gioele, Gioele Barabucci (2025-01-13): > currently d-i installs `linux-image-$arch` regardless of the kind of > machine it is installed on. That's the general idea but that's not really what's actually happening (devil, details, etc.). > When used inside a virtua

Bug#1092949: debian-installer could propose installing linux-image-cloud when run inside a VM

Package: debian-installer Version: 20241227 Dear debian-installer developers, currently d-i installs `linux-image-$arch` regardless of the kind of machine it is installed on. When used inside a virtual machine, it could make sense to ask the user if they want to install linux-image-cloud

Re: Bug#1076723: grub-common: duplicate GNU/Linux in menuentry and submenu lines of /boot/grub/grub.cfg

; > >> After a recent grub2 upgrade, there are now duplicate "GNU/Linux" > >> in menuentry and submenu lines of /boot/grub/grub.cfg, e.g. > >> > >> menuentry 'Debian GNU/Linux GNU/Linux' --class debian --class gnu-linux > >> --class gnu

Re: Uploading linux (6.12.6-1)

Hi Cyril, On Wed, Jan 01, 2025 at 01:07:10PM +0100, Cyril Brulebois wrote: > Cyril Brulebois (2024-12-26): > > Perfect, thanks. I've hinted the linux-* lot a few britney ago and they > > migrated. I'm currently busy discovering and tying up loose ends… I'm > >

Re: Uploading linux (6.12.6-1)

Cyril Brulebois (2024-12-26): > Perfect, thanks. I've hinted the linux-* lot a few britney ago and they > migrated. I'm currently busy discovering and tying up loose ends… I'm > not sure how many of them there are, but hopefully that's a manageable > number (fa

Re: Bug#1076723: grub-common: duplicate GNU/Linux in menuentry and submenu lines of /boot/grub/grub.cfg

Control: tags -1 patch On 26/12/2024 at 20:37, Cyril Brulebois wrote: Vincent Lefevre (2024-07-22): After a recent grub2 upgrade, there are now duplicate "GNU/Linux" in menuentry and submenu lines of /boot/grub/grub.cfg, e.g. menuentry 'Debian GNU/Linux GNU/Linux' --clas

Re: Bug#1076723: grub-common: duplicate GNU/Linux in menuentry and submenu lines of /boot/grub/grub.cfg

Control: severity -1 important Vincent Lefevre (2024-07-22): > Package: grub-common > Version: 2.12-5 > Severity: normal > > After a recent grub2 upgrade, there are now duplicate "GNU/Linux" > in menuentry and submenu lines of /boot/grub/grub.cfg, e.g. > > men

Re: Uploading linux (6.12.6-1)

ait for your ack for > proceeding. > > Does this works out? Perfect, thanks. I've hinted the linux-* lot a few britney ago and they migrated. I'm currently busy discovering and tying up loose ends… I'm not sure how many of them there are, but hopefully that's a manageabl

Re: Uploading linux (6.12.6-1)

Hi Cyril, On Wed, Dec 25, 2024 at 10:10:52AM +0100, Cyril Brulebois wrote: > Hi Salvatore, > > Salvatore Bonaccorso (2024-12-20): > > I would like to upload linux version 6.12.6-1 to unstable. > > > > It imports 6.12.6 on top of what is currently in unstable, it fixe

Re: Uploading linux (6.12.6-1)

Hi Salvatore, Salvatore Bonaccorso (2024-12-20): > I would like to upload linux version 6.12.6-1 to unstable. > > It imports 6.12.6 on top of what is currently in unstable, it fixes > additionally with the new upstream stable version CVE-2024-53240 and > CVE-2024-53241 (which

Bug#1091099: override: linux-sysctl-defaults:kernel/important

Package: ftp.debian.org Severity: normal User: ftp.debian@packages.debian.org Usertags: override X-Debbugs-Cc: debian-boot@lists.debian.org linux-sysctl-defaults should be installed by default on typical Debian systems. See #1090811 for background. Thanks noah

Re: Uploading linux (6.12.3-1)

.1.15-2) unstable; urgency=medium . * New upstream release. * patches: Fix pci detection on recent linux. (Closes: #1075713) With thanks to Timo for including this patch in that upload, and of course to Tj who really put quite some efforts into debugging this. Cheers, -- Cyril Bru

Processed: Re: Bug#1090811: debian-installer: install linux-sysctl-defaults by default

Processing control commands: > reassign -1 general Bug #1090811 [src:debian-installer] debian-installer: install linux-sysctl-defaults by default Bug reassigned from package 'src:debian-installer' to 'general'. No longer marked as found in versions debian-installer/202409

Bug#1090811: debian-installer: install linux-sysctl-defaults by default

Control: reassign -1 general On Thu, Dec 19, 2024 at 04:24:49PM +0100, Cyril Brulebois wrote: > > The linux-sysctl-defaults provides a "sysctl configuration file setting some > > sensible defaults for Linux". Among other things, the settings provided by > > this pa

Bug#1090811: debian-installer: install linux-sysctl-defaults by default

Hi Noah, Noah Meyerhans (2024-12-19): > Source: debian-installer > Version: 20240914 > Severity: normal > > The linux-sysctl-defaults provides a "sysctl configuration file setting some > sensible defaults for Linux". Among other things, the settings provided by

Bug#1090811: debian-installer: install linux-sysctl-defaults by default

Source: debian-installer Version: 20240914 Severity: normal The linux-sysctl-defaults provides a "sysctl configuration file setting some sensible defaults for Linux". Among other things, the settings provided by this package are needed in order to allow unprivileged users to run

Re: Uploading linux (6.12.3-1)

On 08/12/2024 at 03:55, Cyril Brulebois wrote: Cyril Brulebois (2024-12-08): FWIW the X server no longer starts when d-i is built against 6.12.3, it loops with “no screens found”. This is the gtk mini.iso, standard QEMU in stable, and 2G of RAM (i.e. `kvm -cdrom netboot/gtk/mini.iso -m 2G`).

Re: Uploading linux (6.12.3-1)

On Sun, Dec 08, 2024 at 03:55:38AM +0100, Cyril Brulebois wrote: > I see upstream seems to have renamed something: > > -## choice: Module compression mode > +## choice: Module compression type > CONFIG_MODULE_COMPRESS_XZ=y > ## end choice > > but that seems to be about setting a

Re: Uploading linux (6.12.3-1)

actually debug that other issue) which kicks in depending on the presence of drm.ko (initially), then drm.ko.xz (once modules got compressed), to ship more DRM modules in some d-i images. But linux-image-6.12.3-amd64 only ships *.ko now, which makes the workaround ineffective. Dropping the .xz suff

Re: Uploading linux (6.12.3-1)

[ Adjusting recipients for the heads-up… ] Salvatore Bonaccorso (2024-12-07): > I would like to upload linux version 6.12.3-1 to unstable. > > This is a new upstream version with, as usual, many changes. > This is a LTS release upstream[1] and *is* the version we aim to have > i

Re: Bug#1088008: bookworm-pu: package util-linux/2.38.1-5+deb12u3

Jonathan Wiltshire (2024-11-25): > Control: tag -1 d-i > > On Thu, Nov 21, 2024 at 09:36:13PM +0100, Chris Hofstaedtler wrote: > > [ Reason ] > > In the mitigation for CVE-2024-28085 util-linux intended to disable > > setgid on write and wall. I used --disabl

Re: Bug#1088008: bookworm-pu: package util-linux/2.38.1-5+deb12u3

Control: tag -1 d-i On Thu, Nov 21, 2024 at 09:36:13PM +0100, Chris Hofstaedtler wrote: > [ Reason ] > In the mitigation for CVE-2024-28085 util-linux intended to disable > setgid on write and wall. I used --disable-tty-group to achieve this. > However this causes `mesg y` to behave

Bug#848972: marked as done (console-setup-linux: Datei /tmp/tmpkbd.BRzn8j kann nicht geöffnet werden)

Your message dated Mon, 28 Oct 2024 22:18:04 +0100 with message-id <20241028221804.7368225e7db6fa3514989...@mailbox.org> and subject line Re: Bug#848972: console-setup-linux: Datei /tmp/tmpkbd.BRzn8j kann nicht geöffnet werden has caused the Debian Bug report #848972, regarding console

Re: Uploaded linux (6.11.2-1)

Ben Hutchings (2024-10-07): > On Sun, 2024-10-06 at 18:06 +0200, Ben Hutchings wrote: > > I've just uploaded linux 6.11.2-1 to unstable. > > > > This is a new upstream version with, as usual, many changes. > > > > Some significant changes to the package

Re: Uploaded linux (6.11.2-1)

On Sun, 2024-10-06 at 18:06 +0200, Ben Hutchings wrote: > I've just uploaded linux 6.11.2-1 to unstable. > > This is a new upstream version with, as usual, many changes. > > Some significant changes to the package are: > > * [i386] Stop building kernel packages &g

Re: Handling next linux upload to unstable

Hi, On Sun, Sep 22, 2024 at 10:16:11AM +0100, Steve McIntyre wrote: > Hey Salvatore! > > On Fri, Sep 20, 2024 at 03:46:29PM +0200, Salvatore Bonaccorso wrote: > > > >Hope you and family are doing better already now. > > Thanks! > > >Just double-checking as well, given debian-installer moved to

Re: Handling next linux upload to unstable

Hey Salvatore! On Fri, Sep 20, 2024 at 03:46:29PM +0200, Salvatore Bonaccorso wrote: > >Hope you and family are doing better already now. Thanks! >Just double-checking as well, given debian-installer moved to testing, >is it now fine to do other src:linux uploads to unstable or are we yet >waiti

Re: Handling next linux upload to unstable

Hi Steve, On Sun, Sep 15, 2024 at 09:26:07PM +0100, Steve McIntyre wrote: > On Sun, Sep 15, 2024 at 12:31:12AM +0200, Cyril Brulebois wrote: > >Steve McIntyre (2024-09-14): > >> > >> That looks great for me, thanks. > > > >Then I think my work here is done: > > > >kibi@respighi:~$ dak ls deb

Re: Handling next linux upload to unstable

On Sun, Sep 15, 2024 at 11:08:34PM +0200, Cyril Brulebois wrote: >Steve McIntyre (2024-09-15): >> Kibi: just checking, are you happy for me to call this trixie d-i >> alpha 1? > >As communicated a few times in previous mails already: not at all. Understood, I'm glad I checked. I'll call this some

Re: Handling next linux upload to unstable

Steve McIntyre (2024-09-15): > Kibi: just checking, are you happy for me to call this trixie d-i > alpha 1? As communicated a few times in previous mails already: not at all. Cheers, -- Cyril Brulebois (k...@debian.org) D-I release manager -- Release team memb

Re: Handling next linux upload to unstable

On Sun, Sep 15, 2024 at 12:31:12AM +0200, Cyril Brulebois wrote: >Steve McIntyre (2024-09-14): >> >> That looks great for me, thanks. > >Then I think my work here is done: > >kibi@respighi:~$ dak ls debian-installer -s testing,unstable -a source >debian-installer | 20240914 | testing

Re: Handling next linux upload to unstable

Hi, Steve McIntyre (2024-09-14): > On Sat, Sep 14, 2024 at 01:49:46AM +0200, Cyril Brulebois wrote: > > I'm trying to see if I can get everything lined up for an upload > > that would have a chance to migrate, which I think would be enough > > to unblock Steve on the shim* front. > > Nod. Great

Re: Handling next linux upload to unstable

Hey guys, On Sat, Sep 14, 2024 at 01:49:46AM +0200, Cyril Brulebois wrote: >Salvatore Bonaccorso (2024-09-13): >> >> So we are now there. linux/6.10.9-1 should now be able to migrate to >> testing, no major issues were reported so far, and I think you can let >>

Re: Handling next linux upload to unstable

11.y since I'd guess we would get more > > > things to look at. > > > > Yes, 6.11.y won't go to unstable anyway before 6.11 is released. So > > that will take still some weeks. That means for unstable we will > > continue following the 6.10.y series for

Bug#1071648: marked as done (busybox: FTBFS with Linux 6.8+)

Your message dated Tue, 16 Jul 2024 10:19:24 + with message-id and subject line Bug#1071648: fixed in busybox 1:1.36.1-8 has caused the Debian Bug report #1071648, regarding busybox: FTBFS with Linux 6.8+ to be marked as done. This means that you claim that the problem has been dealt with

Re: Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

Tj (2024-07-13): > After reverting the recent sysfb commits: > > linux$ git l -n 15 > e932a4281dfd4 2024-07-13 17:27:49 +0100 N Tj Revert "firmware/sysfb: Set > firmware-framebuffer parent device" > c16bbb2e6863d 2024-07-13 17:27:49 +0100 N Tj Revert "firmware

Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

ep=(nil)) > [15.609] (II) fbdev_open() using dev from env FRAMEBUFFER=(null) > [15.609] (II) fbdev_open() using default dev=/dev/fb0 > [15.609] (II) fbdev_open() sysfs_path=/sys/class/graphics/fb0 > [15.609] (II) fbdev_open() > buf=../../devices/pci:00/:00:01.0/v

Processed: Re: Bug#1075713: linux: D-I's X fails to start under kvm -vga qxl

Processing control commands: > reassign -1 src:linux 6.9.2-1~exp1 Bug #1075713 [src:debian-installer] linux: D-I's X fails to start under kvm -vga qxl Bug reassigned from package 'src:debian-installer' to 'src:linux'. No longer marked as found in versions debia

  1   2   3   4   5   6   7   8   9   10   >