Processed: Re: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64

2022-10-22 Thread Debian Bug Tracking System
Processing control commands: > severity -1 critical Bug #1022232 [libffi8] libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64 Severity set to 'critical' from 'important' -- 1022232: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022232 Debian Bug Tracking System Contact

Bug#1022232: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64

2022-10-22 Thread Johannes Schauer Marin Rodrigues
Control: severity -1 critical On Sat, 22 Oct 2022 14:14:32 +0200 "Lukas F. Hartmann" wrote: > Since an `apt upgrade` yesterday on Debian unstable on an aarch64 system > (imx8mq based, cortex-a53), all wayland compositors and clients stopped > working, including sway, wayfire and weston. Since

Bug#1022232: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64

2022-10-22 Thread Lukas F. Hartmann
I have identified the breaking patch, it is: https://github.com/libffi/libffi/pull/739/files Reverting debian/patches/739.diff and rebuilding the library fixes the issue. If possible, please drop this patch until the issue is addressed by upstream.

Bug#1022232: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64

2022-10-22 Thread Lukas F. Hartmann
I've tried all recent versions from snapshots. libffi8_3.4.3-2_arm64.deb still works, while libffi8_3.4.3-3_arm64.deb breaks.

Bug#1022232: libffi8 3.4.3-3 breaks all wayland clients on arm64/aarch64

2022-10-22 Thread Lukas F. Hartmann
Package: libffi8 Version: 3.4.3-3 Severity: important Dear Maintainer, Since an `apt upgrade` yesterday on Debian unstable on an aarch64 system (imx8mq based, cortex-a53), all wayland compositors and clients stopped working, including sway, wayfire and weston. I narrowed it down to garbage

Bug#1021735: libffi upgrade breaks Wayland on aarch64

2022-10-22 Thread Daniel Stone
Hi, This libffi upgrade also completely breaks all use of Wayland on aarch64. We use libffi to dispatch protocol messages (requests received by the server and events received by the client) to native-code handlers, and we are now getting completely nonsensical values from it. Can this upgrade

libabigail_2.1-1_source.changes ACCEPTED into unstable

2022-10-22 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Sat, 22 Oct 2022 12:03:06 +0200 Source: libabigail Architecture: source Version: 2.1-1 Distribution: unstable Urgency: medium Maintainer: Debian GCC Maintainers Changed-By: Matthias Klose Changes: libabigail

Processing of libabigail_2.1-1_source.changes

2022-10-22 Thread Debian FTP Masters
libabigail_2.1-1_source.changes uploaded successfully to localhost along with the files: libabigail_2.1-1.dsc libabigail_2.1.orig.tar.gz libabigail_2.1-1.debian.tar.xz libabigail_2.1-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

Processed: List more affected packages

2022-10-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > affects 1021735 src:gjs src:glib2.0 src:gnustep-base src:libffi-platypus-perl > src:libglib-object-introspection-perl src:lua-lgi src:pypy3 src:python2.7 > ruby-ffi src:ruby3.0 src:ruby3.1 Bug #1021735 [src:libffi] libffi breaks python3.10