Your message dated Mon, 07 Oct 2024 11:09:43 +0000 with message-id <e1sxlcv-00gysj...@fasolo.debian.org> and subject line Bug#1084133: fixed in mutter 47.0-3 has caused the Debian Bug report #1084133, regarding mutter: FTBFS on armhf: Directory "/tmp/.X11-unix" is not writable to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1084133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084133 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: mutter Version: 47.0-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org, ar...@buildd.debian.org User: debian-...@lists.debian.org Usertags: armhf Control: block 1081519 by -1 The recent upload of mutter in unstable FTBFS on multiple armhf buildds: arm-ubc-01, arm-conova-03, arm-ubc-05. Interestingly, the arm64 build on one of the same buildds (arm-conova-03) was successful. The error message suggests that there might be a problem with the chroot/container, or possibly with the host /tmp being shared with it: > Bail out! libmutter-FATAL-ERROR: Failed to start X Wayland: Directory > "/tmp/.X11-unix" is not writable Please could a buildd operator check whether something is not working as intended on these buildds? Ideally, mutter's build-dependencies would ensure that /tmp/.X11-unix is created with its canonical ownership and permissions (1777 root:root), but invocation of /etc/init.d/x11-common is suppressed in a chroot, and systemd's /usr/lib/tmpfiles.d/x11.conf only creates /tmp/.X11-unix during boot (and not when systemd is installed into a running system). Possibly this directory is sufficiently special that schroot and unshare ought to ensure its presence as an empty directory with the correct permissions during chroot setup, but that can be a separate feature request. The affected buildds seem to be using schroot, as opposed to unshare. I don't know precisely how it is configured (/tmp from the host, or /tmp part of the chroot, or what). Thanks, smcv
--- End Message ---
--- Begin Message ---Source: mutter Source-Version: 47.0-3 Done: Simon McVittie <s...@debian.org> We believe that the bug you reported is fixed in the latest version of mutter, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1084...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie <s...@debian.org> (supplier of updated mutter package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Format: 1.8 Date: Sun, 06 Oct 2024 23:51:55 +0100 Source: mutter Architecture: source Version: 47.0-3 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers <pkg-gnome-maintain...@lists.alioth.debian.org> Changed-By: Simon McVittie <s...@debian.org> Closes: 1084133 Changes: mutter (47.0-3) unstable; urgency=medium . * Team upload * d/rules: Send xvfb-run error messages to stderr, not to /dev/null. This would have told us that it's crashing on armhf (#1082659). * d/rules: Explicitly set a screen size for xvfb-run. For some reason, this works around a regression where Xvfb crashes on armhf since the update to libunwind 1.7.x. (Mitigates: #1082659) * d/rules, d/tests/ensure-x11-dir: Explicitly create /tmp/.X11-unix. mutter's test suite requires this directory, so create it explicitly instead of relying on xvfb-run to have created it. If creating it fails for whatever reason, this will at least give us better diagnostic information. We cannot create it with its canonical ownership (root:root) because the build isn't running as root, but we can at least make sure it has its canonical permissions. (Closes: #1084133) Checksums-Sha1: 84c8cd0767edd6a47df835c7bd7ff4bbdc5dbd03 4612 mutter_47.0-3.dsc 8b4370ce87772c03fce6ffd72aefbe36a5e8db51 88676 mutter_47.0-3.debian.tar.xz a464a06f64ab4130ca7b1d8709a7bf133c48c6aa 20426 mutter_47.0-3_source.buildinfo Checksums-Sha256: 8d4b2e1a9565c3e659955cd1bdcdf91f96cdf1939a6ecc8708e195132f6ac7ce 4612 mutter_47.0-3.dsc 1f40557386b1a2837344b15adc0de834c18d9b0bc1f870806e0b0a1625f02d90 88676 mutter_47.0-3.debian.tar.xz 6bb6ac763872cb0137e9f4fb2240119b6cdd984ed14ef948cbe870a2d5f280e3 20426 mutter_47.0-3_source.buildinfo Files: e0e9ed06fe411fb86d59fa5991a7a048 4612 x11 optional mutter_47.0-3.dsc 3c139ec5b595470e632e875cf0869dfd 88676 x11 optional mutter_47.0-3.debian.tar.xz 7f7eb350af7a918805a907ba5fc10e02 20426 x11 optional mutter_47.0-3_source.buildinfo -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEegc60a5pT6Jb/2LlI1wJnT6zMHYFAmcDIgIACgkQI1wJnT6z MHaRIBAAwVrKespqUkIGlDwLr159NAFczjP2l6w6Dxvv/8YX9QaenyKgx3/RYXXe Ln+MNzPZAdmD6EQg7PTKqUJMKU8B2Ey9+ZEQu1ejacBJOb4AWLhQgHbrN2RGOr6l 7ADTg9UkpPNUgfyEQRNlarhbbgWQAwd5rig/2KPbWJm5wgXcCjKUPmvurhJXe3Cc fc+I0jGPc7F3Puh2XKrEoTGOQag4/UK23n3xfo0MzigSxvFwi4ORB0Yg5fpNCrOs owZaxXuEpSsQSo2Zswq8KLV3Y2qIGb2cZHXqP/tVbP/XtxCDKiJWL+1pgSyCyZb5 lx48qKOM3SXyX4kUopj/yXVHn4u0t9Fui1D5MDTJ4tH3d5P9MLZyWKn6XnT6p56g zAOO7ZPuPwcoxQRIbqtNKlVL5vIjM65JTdZ+GiJuPI0B46wfzShB+bYg7UScqvhZ xZIQOUBdU7ql651RfQ0R5fDJOVcVWkDAuwh7/MxCWzZ0P3cmgD+waym1M1vPhS6l Wd8vbyscPzZXurlsXUcuXcEn1efQ2iwfb6HxzPknE7dGgUuAbGPDTNB/D6tdrjLU 78riS2pAvrwoORoUN8wbInV8T8a2df1k++mX5lVZMXLGfP7C6Y+ESPEMnMLLVuVE QqNlU64oeZD5mwnwDjklaLCTW+7LOVyqcWzALXSmXQC6bT/1os4= =PbpX -----END PGP SIGNATURE-----
pgpsUfeNYc0FH.pgp
Description: PGP signature
--- End Message ---
