debian-arm  

Messages by Thread

• • Re: AR9271 Raspberry Pi 2B Uwe Kleine-König
  • Re: AR9271 Raspberry Pi 2B John Wick
  • Re: AR9271 Raspberry Pi 2B John Wick
• Nouvel employé Joseph Parisien
  • Re: Nouvel employé [email protected]
  • Re: Nouvel employé Paul Wise
• Re: RM: icinga2 [armel mips64el ppc64el riscv64] -- ROM; FTBFS Aurelien Jarno
  • Re: RM: icinga2 [armel mips64el ppc64el riscv64] -- ROM; FTBFS Sebastiaan Couwenberg
  • Re: RM: icinga2 [armel mips64el ppc64el riscv64] -- ROM; FTBFS Jeffrey Walton
• Immediate fallouts from the big linux changes, and actions Cyril Brulebois
  • Re: Immediate fallouts from the big linux changes, and actions Bastian Blank
  • Re: Immediate fallouts from the big linux changes, and actions Cyril Brulebois
  • Re: Immediate fallouts from the big linux changes, and actions Timo Jyrinki
• Bug#1058740: gtk4,librsvg: big-endian support is at risk of being removed Simon McVittie
• Bug#1057797: glib2.0: thread-pool-slow test intermittently times out on 32-bit ARM Simon McVittie
• Re: Bug#1023652: glib2.0: gobject/tests/threadtests.c can take more than 5 minutes on armhf, armel Simon McVittie
• Bug#1057469: gcc-12: Please build with -mbranch-protection=standard to enable PAC/BTI support on arm64 Emanuele Rocca
• Bug#1057339: dash FTCBFS: host CFLAGS leak into build compiler invocation Helmut Grohne
• debugging gsasl autopkg test error on armhf Andreas Metzler
  • Re: debugging gsasl autopkg test error on armhf Mate Kukri
  • Re: debugging gsasl autopkg test error on armhf Adrien Nader
  • Re: debugging gsasl autopkg test error on armhf Emanuele Rocca
  • Re: debugging gsasl autopkg test error on armhf Andreas Metzler
• Bug#1057133: RM: armel and mips64el binaries of creduce and cvise Matthias Klose
• Raspberry Pi 5 Robert Wilkinson
  • Re: Raspberry Pi 5 peter green
  • Re: Raspberry Pi 5 Marcin Juszkiewicz
  • Re: Raspberry Pi 5 Larry Dighera
  • Re: Raspberry Pi 5 Larry Dighera
  • Raspberry PI 5 John Danielsson
  • Re: Raspberry PI 5 Lennart Sorensen
• Really enable -fstack-clash-protection on armhf/armel? Matthias Klose
  • Re: Really enable -fstack-clash-protection on armhf/armel? Guillem Jover
  • Re: Really enable -fstack-clash-protection on armhf/armel? Emanuele Rocca
  • Re: Really enable -fstack-clash-protection on armhf/armel? Matthias Klose
  • Re: Really enable -fstack-clash-protection on armhf/armel? Adrien Nader
  • Re: Really enable -fstack-clash-protection on armhf/armel? Emanuele Rocca
  • Re: Really enable -fstack-clash-protection on armhf/armel? Emanuele Rocca
  • Re: Really enable -fstack-clash-protection on armhf/armel? Mate Kukri
  • Re: Really enable -fstack-clash-protection on armhf/armel? Mate Kukri
  • Re: Really enable -fstack-clash-protection on armhf/armel? Florian Weimer
  • Re: Really enable -fstack-clash-protection on armhf/armel? Wookey
  • Re: Really enable -fstack-clash-protection on armhf/armel? Emanuele Rocca
  • Re: Really enable -fstack-clash-protection on armhf/armel? Moritz Muehlenhoff
  • Re: Really enable -fstack-clash-protection on armhf/armel? Julian Andres Klode
• Re: Bug#1034159: Kernel support for more ChromeOS devices Alper Nebi Yasak
• Can't connect Raspberry Pi 3B+ Rev. 1.3 to Wifi 5G basti
  • Re: Can't connect Raspberry Pi 3B+ Rev. 1.3 to Wifi 5G Diederik de Haas
  • Re: Can't connect Raspberry Pi 3B+ Rev. 1.3 to Wifi 5G Tim Small
  • Re: Can't connect Raspberry Pi 3B+ Rev. 1.3 to Wifi 5G basti
  • Re: Can't connect Raspberry Pi 3B+ Rev. 1.3 to Wifi 5G Diederik de Haas
  • Re: Can't connect Raspberry Pi 3B+ Rev. 1.3 to Wifi 5G gene heskett
• Bug#1056115: llvm-toolchain-17 ftbfs on armel Matthias Klose
• help needed with LibreOffice Java bridge on armhf Rene Engelhard
  • Re: help needed with LibreOffice Java bridge on armhf Rene Engelhard
• Informatics p db
• Re: Bug#1054583: dpkg-dev: really enable -fstack-clash-protection on armhf/armel Guillem Jover
  • Re: Bug#1054583: dpkg-dev: really enable -fstack-clash-protection on armhf/armel Emanuele Rocca
  • Re: Bug#1054583: dpkg-dev: really enable -fstack-clash-protection on armhf/armel Steve McIntyre
  • Re: Bug#1054583: dpkg-dev: really enable -fstack-clash-protection onarmhf/armel gene heskett
  • Re: Bug#1054583: dpkg-dev: really enable -fstack-clash-protection onarmhf/armel Steve McIntyre
  • Re: Bug#1054583: dpkg-dev: really enable -fstack-clash-protection on armhf/armel Lennart Sorensen
  • Removing dpkg arch definition for arm64ilp32? Guillem Jover
  • Re: Removing dpkg arch definition for arm64ilp32? Wookey
  • Re: Removing dpkg arch definition for arm64ilp32? Steve McIntyre
  • Re: Removing dpkg arch definition for arm64ilp32? Guillem Jover
  • Re: Removing dpkg arch definition for arm64ilp32? Lennart Sorensen
  • Re: Bug#1054583: dpkg-dev: really enable -fstack-clash-protection on armhf/armel Wookey
• Gigabyte MP30AR0 - UEFI MMC Michael Howard
  • Re: Gigabyte MP30AR0 - UEFI MMC Marcin Juszkiewicz
  • Re: Gigabyte MP30AR0 - UEFI MMC Michael Howard
• Bug#1053767: chromium: please to add support for s390x or armel William Desportes
  • Re: Bug#1053767: chromium: please to add support for s390x or armel John Paul Adrian Glaubitz
• Raspi 2 Bookworm hang on first boot, Raspi 1,3 Trixie Make error? Fan Naibed
• Hung raspi2 Bookworm daily builds? Fan Naibed
• need a gparted clone that works as root gene heskett
  • Re: need a gparted clone that works as root Andrew M.A. Cater
• Help needed in reproducing FTBFS of eliom on armhf Stéphane Glondu
  • Re: Help needed in reproducing FTBFS of eliom on armhf Emanuele Rocca
• linux-config: Enabling Kernel Configurations for MediaTek Platforms (CONFIG_ARCH_MEDIATEK) (config-linux-6.5) Macpaul Lin
• linux-config: Enabling Kernel Configurations for MediaTek Platforms (CONFIG_ARCH_MEDIATEK) Macpaul Lin
  • Re: linux-config: Enabling Kernel Configurations for MediaTek Platforms (CONFIG_ARCH_MEDIATEK) Macpaul Lin
• 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

• Earlier messages
• Later messages