debian-arm  

Messages by Thread

• texlive-bin: test builds on your architectures Preuße , Hilmar
  • Re: texlive-bin: test builds on your architectures Bo YU
  • Re: texlive-bin: test builds on your architectures Preuße , Hilmar
• autopkgtest qemu kvm with gic-version=max Johannes Schauer Marin Rodrigues
• Bug#1051900: ohcount: aborts with segfaul or bus error 90% of the time on arm64 Antonio Terceiro
• Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Salvatore Bonaccorso
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Adrian Bunk
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Salvatore Bonaccorso
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Domenico Andreoli
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Paul Gevers
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Bastian Blank
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Andrew M.A. Cater
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Paul Wise
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Gianluca Renzi
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems bodhi
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Philippe Clérié
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Domenico Andreoli
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Ben Hutchings
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Domenico Andreoli
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Adrian Bunk
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Salvatore Bonaccorso
  • Re: Releasing linux/6.1.52-1 bookworm-security update without armel build, Image size problems Fan Naibed
• abel.debian.org is down Mathieu Malaterre
  • Re: abel.debian.org is down Wookey
  • Re: abel.debian.org is down Mathieu Malaterre
  • Re: abel.debian.org is down Wookey
  • Re: abel.debian.org is down Mathieu Malaterre
  • Re: abel.debian.org is down Wookey
  • Re: abel.debian.org is down Mathieu Malaterre
• Re: Using Raspberry POE hat with bullseye Uwe Kleine-König
• Bug#1050014: mutter: rethink the approach to forcing gles2 as default on armel, armhf Simon McVittie
• Happy 30 Years Debian Project Luna Jernberg
  • Re: Happy 30 Years Debian Project Tuco Ramirez
• Just tried arm64 netinstall on a bananai-m5 gene heskett
  • Re: Just tried arm64 netinstall on a bananai-m5 Vagrant Cascadian
  • Re: Just tried arm64 netinstall on a bananai-m5 gene heskett
  • Re: Just tried arm64 netinstall on a bananai-m5 peter green
  • Re: Just tried arm64 netinstall on a bananai-m5 Marcin Juszkiewicz
  • Re: Just tried arm64 netinstall on a bananai-m5 gene heskett
  • Re: Just tried arm64 netinstall on a bananai-m5 Alan Corey
  • Re: Just tried arm64 netinstall on a bananai-m5 gene heskett
  • Re: Just tried arm64 netinstall on a bananai-m5 Andrew M.A. Cater
  • Re: Just tried arm64 netinstall on a bananai-m5 Marco d'Itri
  • Re: Just tried arm64 netinstall on a bananai-m5 gene heskett
• Bug#1043467: spinlock_gcc_arm.hpp possibly doesn't take into accout LDREX on arm64 Santiago Ruano Rincón
• kvm on arm64 Ross Vandegrift
  • Re: kvm on arm64 Emanuele Rocca
  • Re: kvm on arm64 Ross Vandegrift
  • Re: kvm on arm64 Ross Vandegrift
  • Re: kvm on arm64 Ross Vandegrift
• Add QNAP model Q703 Kevin Read
  • Re: Add QNAP model Q703 Martin Michlmayr
  • Re: Add QNAP model Q703 Arnd Bergmann
  • Re: Add QNAP model Q703 Timo Jyrinki
  • Re: Add QNAP model Q703 Timo Jyrinki
  • Re: Add QNAP model Q703 Martin Michlmayr
• Enabling -fstack-clash-protection for trixie Moritz Mühlenhoff
  • Re: Enabling -fstack-clash-protection for trixie Emanuele Rocca
  • Re: Enabling -fstack-clash-protection for trixie Lucas Nussbaum
  • Re: Enabling -fstack-clash-protection for trixie Emanuele Rocca
  • Re: Enabling -fstack-clash-protection for trixie Lucas Nussbaum
  • Re: Enabling -fstack-clash-protection for trixie Emanuele Rocca
  • Re: Enabling -fstack-clash-protection for trixie [armhf rebuild] Lucas Nussbaum
  • Re: Enabling -fstack-clash-protection for trixie [armhf rebuild] Emanuele Rocca
  • Re: Enabling -fstack-clash-protection for trixie [armhf rebuild] Emanuele Rocca
  • Re: Enabling -fstack-clash-protection for trixie [armhf rebuild] Lucas Nussbaum
  • Re: Enabling -fstack-clash-protection for trixie Guillem Jover
• Cubox-i bullseye -> bookworm Upgrade failure Rainer Dorsch
  • Re: Cubox-i bullseye -> bookworm Upgrade failure RobJE Debian ARM
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Rainer Dorsch
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Reco
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Steve Langasek
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Reco
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Steve Langasek
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Rainer Dorsch
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Steve Langasek
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Rainer Dorsch
  • Re: Cubox-i bullseye -> bookworm Upgrade failure Paul Wise
  • device name changed after upgrade to bookworm [was: Cubox-i bullseye -> bookworm Upgrade failure] Rainer Dorsch
  • Re: device name changed after upgrade to bookworm [was: Cubox-i bullseye -> bookworm Upgrade failure] Fan Naibed
  • Re: device name changed after upgrade to bookworm [was: Cubox-i bullseye -> bookworm Upgrade failure] Rainer Dorsch
• How can I tell Debian on a Raspberry Pi 4B (4GB) which kernel image to load at boot time? Rick Thomas
  • Fwd: How can I tell Debian on a Raspberry Pi 4B (4GB) which kernel image to load at boot time? Hank Barta
• Run a test build für texlive-bin on armhf? Hilmar Preuße
  • Re: Run a test build für texlive-bin on armhf? Preuße , Hilmar
• Re: [syzbot] [hfs?] WARNING in hfs_write_inode Matthew Wilcox
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Jeff Layton
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Dave Chinner
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Finn Thain
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Matthew Wilcox
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Finn Thain
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode gene heskett
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Theodore Ts'o
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode gene heskett
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Jeffrey Walton
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Matthew Wilcox
  • Re: [syzbot] [hfs?] WARNING in hfs_write_inode Linus Torvalds
• POE Hat and dtoverlays in Debian 12 Markus Falb
  • Re: POE Hat and dtoverlays in Debian 12 Sebastian Kuzminsky
• unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures John Paul Adrian Glaubitz
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Rob Landley
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Rob Landley
  • Re: unbreaking LibreOffices tests on at least release architectures Kurt Roeckx
  • Re: unbreaking LibreOffices tests on at least release architectures Jan Engelhardt
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Rob Landley
  • Re: unbreaking LibreOffices tests on at least release architectures Steve McIntyre
  • Re: unbreaking LibreOffices tests on at least release architectures Omer Turpault
  • Re: unbreaking LibreOffices tests on at least release architectures Adrian Bunk
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Jeffrey Walton
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Jeffrey Walton
  • Re: unbreaking LibreOffices tests on at least release architectures Adrian Bunk
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Adrian Bunk
  • Re: unbreaking LibreOffices tests on at least release architectures Kirsten Bromilow
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures) Rene Engelhard
  • Re: LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures) Rene Engelhard
  • Re: LibreOffice bridges/smoketest on mips(64)el (was: Re: unbreaking LibreOffices tests on at least release architectures) Adrian Bunk
  • Re: unbreaking LibreOffices tests on at least release architectures Kurt Roeckx
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Kurt Roeckx
  • Re: unbreaking LibreOffices tests on at least release architectures Paul Wise
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Andreas Schwab
  • Re: unbreaking LibreOffices tests on at least release architectures Rene Engelhard
  • Re: unbreaking LibreOffices tests on at least release architectures Jeffrey Walton
• Proper invocation of flash-kernel? Nate Bargmann
• Thinkpad X13s boot loop after dist-upgrade Lionel Élie Mamane
  • Re: Thinkpad X13s boot loop after dist-upgrade Lionel Élie Mamane
  • Re: Thinkpad X13s boot loop after dist-upgrade Lionel Élie Mamane
  • Thinkpad X13s no battery level Lionel Élie Mamane
• ARM64 platform, very serious, UEFI hardware damage problem chipo
  • Re: ARM64 platform, very serious, UEFI hardware damage problem Georg Gast
• Bug#1035515: [pre-approval] unblock: gdb/13.1-2.1 Emanuele Rocca
• Bug#1029843: brcmfmac: requested firmware filename inconsistent with linux-firmware.git on non-devicetree systems James Addison
• Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..." Axel Beckert
• Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters James Addison
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Pete Batard
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters James Addison
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Pete Batard
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters James Addison
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Pete Batard
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Lennart Sorensen
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Pete Batard
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Lennart Sorensen
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Steve McIntyre
  • Re: Bug#1029843: live-boot: Devices Requiring Firmware: multiple requested files in single line overlapping / special characters Paul Wise
• RFC: android-style boot image support for flash-kernel Roger Shimizu
  • Re: RFC: android-style boot image support for flash-kernel Diederik de Haas
  • Re: RFC: android-style boot image support for flash-kernel Vagrant Cascadian
  • Re: RFC: android-style boot image support for flash-kernel Roger Shimizu
• Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Guillem Jover
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Steve McIntyre
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Wookey
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Guillem Jover
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Emanuele Rocca
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Guillem Jover
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Emanuele Rocca
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Emanuele Rocca
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Vagrant Cascadian
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Guillem Jover
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Emanuele Rocca
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Emanuele Rocca
  • Re: Status of dpkg-shlibdeps tracking ARM object linkage ABI mismatches Emanuele Rocca
• Secure Boot on arm64 working in sid Emanuele Rocca
• Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Rick Thomas
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Diederik de Haas
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Georg Gast
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Diederik de Haas
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Rick Thomas
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Reco
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Rick Thomas
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Reco
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Rick Thomas
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Paul Wise
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Rick Thomas
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Paul Wise
  • Re: Activate a Real Time Clock chip on I2C in Raspberry Pi 4B with Debian (not Raspbian) Rick Thomas

• Earlier messages
• Later messages