debian-arm  

Messages by Thread

• • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Thorsten Glaser
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Jeffrey Walton
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Thorsten Glaser
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Wookey
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Wookey
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Thorsten Glaser
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Wookey
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Thorsten Glaser
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Wookey
  • Re: Bug#1036884: transition: time64_t - openjdk-17 needs re-bootstrap on armel,armhf Thorsten Glaser
• Bug#1067559: nmu: roc-toolkit_0.3.0+dfsg-7 Simon McVittie
• Bug#1067430: nmu: graphviz_2.42.2-9 Simon McVittie
• Bug#1067421: nmu: gstreamer1.0_1.24.0-1 Simon McVittie
  • Re: Bug#1067421: nmu: gstreamer1.0_1.24.0-1 Simon McVittie
• Bug#1067213: git: please consider temporarily disabling subversion/libsvn-perl build-dependencies on armhf and armel Emanuele Rocca
• Re: Bug#1062847: protobuf: Use dh-sequence-elpa in Build-Depends-Indep Simon McVittie
• Bug#1067043: libruby: needs updating for libruby3.1t64 Simon McVittie
  • Re: Bug#1067043: libruby: needs updating for libruby3.1t64 Chris Hofstaedtler
• Bug#1067026: graphviz: please build without librsvg except on rust platforms Thorsten Glaser
• Bug#1066982: curl: please consider temporarily disabling LDAP and build-time tests on 32-bit non-x86 Simon McVittie
• strange behavior with i2c on raspberry pi 4 basti
  • Re: strange behavior with i2c on raspberry pi 4 Alex
  • Re: strange behavior with i2c on raspberry pi 4 basti
  • Re: strange behavior with i2c on raspberry pi 4 basti
• Bug#1066847: openssh: please consider disabling ssh-askpass-gnome on 32-bit during the time_t transition Simon McVittie
• Bug#1066844: at-spi2-core: needs re-bootstrapping on armel, armhf for 64-bit time_t transition Simon McVittie
• Bug#1066832: fsverity-utils: hard Build-Depends on unportable package pandoc Thorsten Glaser
• Re: Bug#1036884: transition: time64_t Simon McVittie
  • Re: Bug#1036884: transition: time64_t Emanuele Rocca
  • Re: Bug#1036884: transition: time64_t Steve Langasek
  • Re: Bug#1036884: transition: time64_t Fabian Grünbichler
  • Re: Bug#1036884: transition: time64_t Emanuele Rocca
  • Re: Bug#1036884: transition: time64_t Emanuele Rocca
• Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Andrew M.A. Cater
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Hank Barta
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
  • Re: Governor problem with generic 6.1 arm64 kernel on Raspberry Alex
• python-cryptography vs. stainless steel ports Thorsten Glaser
  • Re: python-cryptography vs. stainless steel ports Jérémy Lal
  • Re: python-cryptography vs. stainless steel ports Thorsten Glaser
  • Re: python-cryptography vs. stainless steel ports Jérémy Lal
  • Re: python-cryptography vs. stainless steel ports Thorsten Glaser
  • Re: python-cryptography vs. stainless steel ports Thorsten Glaser
  • Re: python-cryptography vs. stainless steel ports Helge Deller
• Re: Bug#1065756: pngnq: FTBFS on arm{el, hf}: rwpng.c:242:13: error: implicit declaration of function ‘strncmp’ [-Werror=implicit-function-declaration] 肖盛文
  • Re: Bug#1065756: pngnq: FTBFS on arm{el, hf}: rwpng.c:242:13: error: implicit declaration of function ‘strncmp’ [-Werror=implicit-function-declaration] 肖盛文
  • Re: Bug#1065756: pngnq: FTBFS on arm{el, hf}: rwpng.c:242:13: error: implicit declaration of function ‘strncmp’ [-Werror=implicit-function-declaration] Sebastian Ramacher
  • Re: Bug#1065756: pngnq: FTBFS on arm{el, hf}: rwpng.c:242:13: error: implicit declaration of function ‘strncmp’ [-Werror=implicit-function-declaration] 肖盛文
• Bug#1061370: gcc-14 ftbfs on armel Matthias Klose
  • Bug#1061370: gcc-14 ftbfs on armel Emanuele Rocca
• Re: Bug#1061063: armhf: h5py's tests expose unaligned memory accesses during the build Aurelien Jarno
• Bug#1060849: mesa: FTBFS on armel: static assertion failed: "vn_ring_shared requires lock-free 32-bit atomic_uint" Simon McVittie
• Error: bad immediate value for offset (4100) Mathieu Malaterre
  • Re: Error: bad immediate value for offset (4100) Emanuele Rocca
  • Re: Error: bad immediate value for offset (4100) Peter Green
• Ability to further support 32bit architectures Bastian Blank
  • Re: Ability to further support 32bit architectures John Paul Adrian Glaubitz
  • Re: Ability to further support 32bit architectures Bastian Blank
  • Re: Ability to further support 32bit architectures Dimitri John Ledkov
  • Re: Ability to further support 32bit architectures John Paul Adrian Glaubitz
  • Re: Ability to further support 32bit architectures Bastian Blank
  • Re: Ability to further support 32bit architectures Adrian Bunk
  • Re: Ability to further support 32bit architectures Aurelien Jarno
  • Re: Ability to further support 32bit architectures Aurelien Jarno
  • Re: Ability to further support 32bit architectures Jeffrey Walton
  • Re: Ability to further support 32bit architectures rhys
  • Re: Ability to further support 32bit architectures YunQiang Su
  • Re: Ability to further support 32bit architectures rhys
  • Re: Ability to further support 32bit architectures Alan Corey
  • Re: Ability to further support 32bit architectures gene heskett
  • Re: Ability to further support 32bit architectures Alan Corey
  • Re: Ability to further support 32bit architectures Hank Barta
  • Re: Ability to further support 32bit architectures Bastian Blank
  • Re: Ability to further support 32bit architectures Dimitri John Ledkov
  • Re: Ability to further support 32bit architectures Bastian Blank
• What to do with d-i on armel? Bastian Blank
  • Re: What to do with d-i on armel? Emanuele Rocca
  • Re: What to do with d-i on armel? Martin
  • Re: What to do with d-i on armel? gene heskett
  • Re: What to do with d-i on armel? Peter Green
  • Re: What to do with d-i on armel? Martin
  • Re: What to do with d-i on armel? Gianluca Renzi
  • Re: What to do with d-i on armel? Christoph Biedl
  • Re: What to do with d-i on armel? Ástor Ayllón Lázaro
  • Re: What to do with d-i on armel? Frank Weißer
  • Re: What to do with d-i on armel? Arnd Bergmann
  • Future for armel? (was: Re: What to do with d-i on armel?) Bastian Blank
  • Re: Future for armel? (was: Re: What to do with d-i on armel?) Martin
  • Re: Future for armel? (was: Re: What to do with d-i on armel?) Dimitri John Ledkov
  • Re: What to do with d-i on armel? Ben Hutchings
  • Re: What to do with d-i on armel? Arnd Bergmann
  • Re: What to do with d-i on armel? Bastian Blank
  • Re: What to do with d-i on armel? Cyril Brulebois
  • Re: What to do with d-i on armel? Paul Gevers
  • Re: What to do with d-i on armel? Gerardo Ballabio
  • Re: What to do with d-i on armel? Adrian Bunk
• AR9271 Raspberry Pi 2B John Wick
  • Re: AR9271 Raspberry Pi 2B Andrew M.A. Cater
  • 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

• Earlier messages
• Later messages