debian-boot  

Messages by Thread

• • Re: Bug#1103454: libparted detects ext4 without journal as ext2 Colin Watson
  • Re: Bug#1103454: libparted detects ext4 without journal as ext2 Pascal Hambourg
• Bug#1106796: busybox-static: statically linked against glibc without a Built-Using: field Aurelien Jarno
  • Re: Bug#1106796: busybox-static: statically linked against glibc without a Built-Using: field Aurelien Jarno
  • Processed: Re: Bug#1106796: busybox-static: statically linked against glibc without a Built-Using: field Debian Bug Tracking System
  • Processed: Bug#1106796 marked as pending in busybox Debian Bug Tracking System
  • Bug#1106796: marked as done (busybox-static: statically linked against glibc without a Built-Using: field) Debian Bug Tracking System
• Bug#901722: marked as done (debian-installer: unable to use custom or local mirror) Debian Bug Tracking System
• Re: Bug#1106761: bookworm-pu: package glibc/2.36-9+deb12u11 Adam D. Barratt
  • Re: Bug#1106761: bookworm-pu: package glibc/2.36-9+deb12u11 Aurelien Jarno
• Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Cyril Brulebois
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Re: Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Re: Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Paul Gevers
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Paul Gevers
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Paul Gevers
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Cyril Brulebois
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Pascal Hambourg
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Steve McIntyre
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Steve McIntyre
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Trupti
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Bastian Blank
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Bastian Blank
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Michael Tokarev
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Bastian Blank
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Lennart Sorensen
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Michael Tokarev
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Sachin Sant
  • Bug#1106757: ppc64el Trixie: Need default 64KB page kernel or installer option Bastian Blank
• Re: #901722debian-installer: unable to use custom or local mirror Holger Wansing
• Bug#1106712: makedev referenced by chroot installation instructions Philipp Kern
  • Bug#1106712: makedev referenced by chroot installation instructions Chris Hofstaedtler
• Bug#1106694: debian installer report Carles Pina i Estany
• Uploading linux (6.12.30-1) Salvatore Bonaccorso
  • Re: Uploading linux (6.12.30-1) Cyril Brulebois
  • Re: Uploading linux (6.12.30-1) Salvatore Bonaccorso
• Bug#1106658: installation-reports: Touchpad not active Roland Clobus
  • Bug#1106658: installation-reports: Touchpad not active Pascal Hambourg
  • Bug#1106658: installation-reports: Touchpad not active Roland Clobus
  • Bug#1106658: installation-reports: Touchpad not active Cyril Brulebois
  • Bug#1106658: installation-reports: Touchpad not active Salvatore Bonaccorso
  • Bug#1106658: installation-reports: Touchpad not active Roland Clobus
  • Bug#1106658: installation-reports: Touchpad not active Cyril Brulebois
  • Bug#1106658: installation-reports: Touchpad not active Pascal Hambourg
  • Bug#1106658: installation-reports: Touchpad not active Roland Clobus
  • Bug#1106658: marked as done (installation-reports: Touchpad not active) Debian Bug Tracking System
• grub-installer_1.210_source.changes ACCEPTED into unstable Debian FTP Masters
• Processing of grub-installer_1.210_source.changes Debian FTP Masters
• Processed: Bug#593105 marked as pending in tasksel Debian Bug Tracking System
• Processing of apt-setup_0.195_source.changes Debian FTP Masters
• Bug#1102140: marked as done (CD-ROM is still first priority package repository in Test/Trixia) Debian Bug Tracking System
  • Bug#1102140: marked as done (CD-ROM is still first priority package repository in Test/Trixia) Debian Bug Tracking System
• Bug#1103650: marked as done (Debian installer adds the CDROM in APT sources even when the installation source is not a CDROM) Debian Bug Tracking System
  • Bug#1103650: marked as done (Debian installer adds the CDROM in APT sources even when the installation source is not a CDROM) Debian Bug Tracking System
• apt-setup_0.195_source.changes ACCEPTED into unstable Debian FTP Masters
• Processed: forcibly merging 1106495 1106496 Debian Bug Tracking System
• Processed: Bug#1103650 marked as pending in apt-setup Debian Bug Tracking System
• Processed: Bug#1102140 marked as pending in apt-setup Debian Bug Tracking System
• Processing of partman-crypto_132_source.changes Debian FTP Masters
• partman-crypto_132_source.changes ACCEPTED into unstable Debian FTP Masters
• tasksel vs. trixie? Cyril Brulebois
  • Re: tasksel vs. trixie? Cyril Brulebois
  • Re: tasksel vs. trixie? Paul Gevers
  • Re: tasksel vs. trixie? Cyril Brulebois
  • Re: tasksel vs. trixie? Paul Gevers
  • Re: tasksel vs. trixie? Cyril Brulebois
• Re: Bug#1106070: Raising the severity? Salvatore Bonaccorso
  • Re: Bug#1106070: Raising the severity? Cyril Brulebois
  • Re: Bug#1106070: Raising the severity? Roland Clobus
  • Re: Bug#1106070: Raising the severity? Salvatore Bonaccorso
  • Re: Bug#1106070: Raising the severity? Chris Hofstaedtler
• Bug#1106506: unblock: apt/3.0.2 Julian Andres Klode
  • Re: Bug#1106506: unblock: apt/3.0.2 Cyril Brulebois
• Automated testing of d-i Roland Clobus
  • Re: Preparing dual boot (Was: Automated testing of d-i) Roland Clobus
  • Re: Preparing dual boot (Was: Automated testing of d-i) Pascal Hambourg
  • Re: First version of automated test for dual boot activated (Was: Automated testing of d-i) Roland Clobus
• Tentative reimbursement request for Debian hardware Cyril Brulebois
  • Searching for Linux 6.12 / Trixie supported Wi-Fi 7 chips! Cyril Brulebois
  • Re: Tentative reimbursement request for Debian hardware Andreas Tille
  • Re: Tentative reimbursement request for Debian hardware Cyril Brulebois
  • Re: Tentative reimbursement request for Debian hardware Marc Haber
  • Re: Tentative reimbursement request for Debian hardware Cyril Brulebois
  • Re: Tentative reimbursement request for Debian hardware Marc Haber
  • Re: Tentative reimbursement request for Debian hardware Cyril Brulebois
  • Re: Tentative reimbursement request for Debian hardware Holger Levsen
• Processing of rescue_1.103_source.changes Debian FTP Masters
• rescue_1.103_source.changes ACCEPTED into unstable Debian FTP Masters
• Bug#697985: marked as done (debian-installer: Remove explicit field exporting rules from docs) Debian Bug Tracking System
• Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Guido Günther
  • Re: Are follow-up steps for Lomiri/Phosh desktop required? Roland Clobus
  • Re: Are follow-up steps for Lomiri/Phosh desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri/Phosh desktop required? Guido Günther
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Guido Günther
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Holger Wansing
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Philip Hands
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Holger Wansing
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Cyril Brulebois
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Holger Wansing
  • Re: Are follow-up steps for Lomiri desktop required? Guido Günther
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Philip Hands
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
  • Re: Are follow-up steps for Lomiri desktop required? Guido Günther
  • Re: Are follow-up steps for Lomiri desktop required? Mike Gabriel
• Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Sistemas Jaguar
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Holger Wansing
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Sistemas Jaguar
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Holger Wansing
  • Processed: Re: Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Debian Bug Tracking System
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Sistemas Jaguar
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Pascal Hambourg
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Holger Wansing
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Sistemas Jaguar
  • Bug#1106495: installation-reports: kernel image missing (Trixie RC1) Sistemas Jaguar
• Bug#1106496: installation-reports: kernel image missing (Trixie RC1) Sistemas Jaguar
  • Bug#1106496: installation-reports: kernel image missing (Trixie RC1) Steve McIntyre
  • Bug#1106496: installation-reports: kernel image missing (Trixie RC1) Steve McIntyre
• fonts-motoya-l-cedar vs. trixie? Cyril Brulebois
  • Re: fonts-motoya-l-cedar vs. trixie? Paul Gevers
  • Re: fonts-motoya-l-cedar vs. trixie? Cyril Brulebois
• Re: Bug#1106401: unblock: fuse3/3.17.2-2 (pre-approval) Cyril Brulebois
• Bug#1106381: flash-kernel: Add Raspberry Pi 4 Model B support Kurva Prashanth
  • Bug#1106381: flash-kernel: Add Raspberry Pi 4 Model B support) Kurva Prashanth
• Processing of rootskel-gtk_13.0.3_source.changes Debian FTP Masters
• rootskel-gtk_13.0.3_source.changes ACCEPTED into unstable Debian FTP Masters
• Processing of blendsel_0.9_source.changes Debian FTP Masters
• blendsel_0.9_source.changes ACCEPTED into unstable Debian FTP Masters
• Re: Bug#1104976: unblock: glib2.0/2.84.2-1 Simon McVittie
  • Re: Bug#1104976: unblock: glib2.0/2.84.2-1 Cyril Brulebois
• Live installer (calamares) crashes on any LVM creation Patrick Plenefisch
  • Re: Live installer (calamares) crashes on any LVM creation Holger Wansing
  • Re: Live installer (calamares) crashes on any LVM creation Roland Clobus
• Bug#1106196: Failure to install Trixie RC-1, Could not verify system name. V Bruce Hunt
  • Bug#1106196: Failure to install Trixie RC-1, Could not verify system name. Pascal Hambourg
• Bug#1004090: tasksel: A comma in a task's Description breaks tasksel Cyril Brulebois
• USB stick installer rob stone
  • Re: USB stick installer Peter Ehlert
  • Re: USB stick installer Pascal Hambourg
  • Re: USB stick installer Nicholas D Steeves
• Bug#1106144: debian-installer: UI scaling/font tiny on 4k iMac 2017 Francis Hennigan
• Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Dave Hibberd
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Re: Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Dave Hibberd
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Roland Clobus
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Holger Wansing
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Holger Wansing
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Bug#1106127: blendsel: Blendsel does not install hamradio blend from installer Cyril Brulebois
  • Bug#1106127: marked as done (blendsel: Blendsel does not install hamradio blend from installer) Debian Bug Tracking System
• busybox security fixes Sean Whitton
  • Re: busybox security fixes Michael Tokarev
  • Re: busybox security fixes Michael Tokarev
  • Re: busybox security fixes Sean Whitton
• Bug#1106077: installation-reports Tyan TN71-BP012 POWER8 debian-trixie-DI-rc1-ppc64el oliviosu_ppc64el
• Re: Bug#1106070: linux-image-6.12.29-amd64: loop device cannot mount live squashfs any more Cyril Brulebois
• Bug#1106070: Fwd: linux-image-6.12.29-amd64: loop device cannot mount live squashfs any more Roland Clobus
  • Re: Bug#1106070: Fwd: linux-image-6.12.29-amd64: loop device cannot mount live squashfs any more Cyril Brulebois
• Bug#1106029: installation-reports: trixie RC1 fails to add a boot entry or create a bootx64.efi on EFI (=> installs unbootable system) nabijaczleweli
  • Bug#1106029: installation-reports: trixie RC1 fails to add a boot entry or create a bootx64.efi on EFI (=> installs unbootable system) наб
  • Processed: Re: Bug#1106029: installation-reports: trixie RC1 fails to add a boot entry or create a bootx64.efi on EFI (=> installs unbootable system) Debian Bug Tracking System
• Re: Bug#1105965: Remove mips64el from testing Cyril Brulebois
• Bug#1106005: installation-reports: I end up with all the files of "firmware-sof-signed" installed, but not the package itself Alexandre Detiste
  • Bug#1106005: Acknowledgement (installation-reports: I end up with all the files of "firmware-sof-signed" installed, but not the package itself) Alexandre Detiste
  • Bug#1106005: installation-reports: I end up with all the files of "firmware-sof-signed" installed, but not the package itself Pascal Hambourg
  • Bug#1106005: installation-reports: I end up with all the files of "firmware-sof-signed" installed, but not the package itself Pascal Hambourg

• Earlier messages
• Later messages