Re: Slow 'daily-build' command (Was: Bug#1091366: debian-installer: No graphical mode in sid)

2024-12-24 Thread Cyril Brulebois
Hi, Roland Clobus (2024-12-24): > On 24/12/2024 20:19, Cyril Brulebois wrote: > > Building with daily-build seems super slow for no obvious reasons, so I've > > just tried a regular `dpkg-buildpackage -b` instead, and I can replicate > > the issue with files below build/dest/cdrom/gtk after the b

Processed: closing 1059052

2024-12-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1059052 1:1.37.0-1 Bug #1059052 [src:busybox] busybox: CVE-2023-42365 Marked as fixed in versions busybox/1:1.37.0-1. Bug #1059052 [src:busybox] busybox: CVE-2023-42365 Marked Bug as done > thanks Stopping processing here. Please contact me

Processed: closing 1059051

2024-12-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1059051 1:1.37.0-1 Bug #1059051 [src:busybox] busybox: CVE-2023-42364 Marked as fixed in versions busybox/1:1.37.0-1. Bug #1059051 [src:busybox] busybox: CVE-2023-42364 Marked Bug as done > thanks Stopping processing here. Please contact me

Bug#1036523: should not install CPU microcode on virtualized systems

2024-12-24 Thread Cyril Brulebois
Daniel Lewart (2024-12-24): > I hope this can be resolved for Trixie. > > Patch attached. Tested with QEMU. Thanks, but that doesn't look appropriate: this disables not just CPU microcode but also modalias-based firmware lookup entirely… Cheers, -- Cyril Brulebois (k...@debian.org)

Bug#1036589: hw-detect: Investigate expanding virtualization detection

2024-12-24 Thread Daniel Lewart
I wrote: > Untested patch attached. An alternative patch with fewer quotation marks attached, also untested. Thank you! Daniel Lewart Urbana, Illinois diff -ru a/hw-detect.finish-install.d/08hw-detect b/hw-detect.finish-install.d/08hw-detect --- a/hw-detect.finish-install.d/08hw-detect 2023-03-1

Bug#1036589: hw-detect: Investigate expanding virtualization detection

2024-12-24 Thread Daniel Lewart
Cyril Brulebois (2023-05-23): > The hw-detect.finish-install.d/08hw-detect script was inspired by > systemd's detect_vm function, and that part was last touched in 2019. > > There were many changes in systemd, and it might make sense to catch up. > Its dmi_vendor_table looks like this currently:

Bug#1036523: should not install CPU microcode on virtualized systems

2024-12-24 Thread Daniel Lewart
Cyril Brulebois (2023-05-23): > > Since it's filed at severity normal I think I'll stick to my initial > > assessment which was: adjust hw-detect during the Trixie release cycle, > > and consider cherry-picks for Bookworm, once we get a better picture. > Given the first follow-up to #1036589, I'

Re: Slow 'daily-build' command (Was: Bug#1091366: debian-installer: No graphical mode in sid)

2024-12-24 Thread Roland Clobus
Hello Cyril, list, On 24/12/2024 20:19, Cyril Brulebois wrote: Building with daily-build seems super slow for no obvious reasons, so I've just tried a regular `dpkg-buildpackage -b` instead, and I can replicate the issue with files below build/dest/cdrom/gtk after the build. I've seen this slo

Processed: Re: Bug#1091366: debian-installer: No graphical mode in sid

2024-12-24 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 src:cdebconf 0.275 Bug #1091366 [src:debian-installer] debian-installer: No graphical mode in sid Bug reassigned from package 'src:debian-installer' to 'src:cdebconf'. Ignoring request to alter found versions of bug #1091366 to the same values previously

Bug#1091366: debian-installer: No graphical mode in sid

2024-12-24 Thread Cyril Brulebois
Control: reassign -1 src:cdebconf 0.275 Control: severity -1 serious Roland Clobus (2024-12-24): > reassign 1091366 cdebconf 0.275 > severity 1091366 important > thanks It doesn't look like that's been (b)cc'd to control@, so let's try again. I'm also calling this a serious regression, esp. when

Bug#1091366: debian-installer: No graphical mode in sid

2024-12-24 Thread Roland Clobus
reassign 1091366 cdebconf 0.275 severity 1091366 important thanks On 24/12/2024 20:19, Cyril Brulebois wrote: With cdebconf udebs reverted to their testing version (changing only that, feeding them via localudebs after deb-reversion), the problem goes away. Paging Colin and Gioele accordingly.

Bug#1091366: debian-installer: No graphical mode in sid

2024-12-24 Thread Cyril Brulebois
kernel build/dest/cdrom/gtk/vmlinuz -initrd > build/dest/cdrom/gtk/initrd.gz -m 2G Ah, some details, thanks. Trying that with today's files just works for me (the graphical installer starts): https://d-i.debian.org/daily-images/amd64/20241224-01:42/cdrom/gtk/ Building with daily-build see

Re: Bug#1091200: override: gpgv:utils/optional

2024-12-24 Thread Sean Whitton
Hello, On Mon 23 Dec 2024 at 01:31pm +01, Cyril Brulebois wrote: > Julian Andres Klode (2024-12-23): >> Package: ftp.debian.org >> Severity: normal >> X-Debbugs-Cc: gnu...@packages.debian.org, debian-boot@lists.debian.org, >> juli...@ubuntu.com >> Control: affects -1 + src:gnupg2 >> User: ftp.d

Bug#1091366: debian-installer: No graphical mode in sid

2024-12-24 Thread Roland Clobus
Hello Cyril, On 24/12/2024 18:58, Cyril Brulebois wrote: Roland Clobus (2024-12-24): The daily live images started to fail to run the graphical installer with the build from 20241224T021629Z [1], whereas the builds from 20241223T201700Z [2] still worked. The X environment is no longer started

Bug#1091366: debian-installer: No graphical mode in sid

2024-12-24 Thread Cyril Brulebois
Roland Clobus (2024-12-24): > The daily live images started to fail to run the graphical installer with > the build from 20241224T021629Z [1], whereas the builds from > 20241223T201700Z [2] still worked. > > The X environment is no longer started. > > With kind regards, > Roland Clobus > > Note

Bug#1091366: debian-installer: No graphical mode in sid

2024-12-24 Thread Roland Clobus
Source: debian-installer Severity: normal The daily live images started to fail to run the graphical installer with the build from 20241224T021629Z [1], whereas the builds from 20241223T201700Z [2] still worked. The X environment is no longer started. With kind regards, Roland Clobus Note: