Bug#1074863: caribou: FTBFS with gcc-14

On Fri, 17 Jan 2025 at 18:53:31 +0100, Fabio Fantoni wrote: > > On Thu, 16 Jan 2025 at 12:52:04 +, Simon McVittie wrote: > > If there is still a need for Caribou to be in Debian (for example for > > Cinnamon's benefit), I would like someone who knows how to test it t

Bug#1093275: autopkgtest: flaky autopkgtest on riscv64: tests involving timeouts often fail

Source: autopkgtest Version: 5.42 Severity: serious User: debian...@lists.debian.org Usertags: flaky X-Debbugs-Cc: debian...@lists.debian.org autopkgtest has several tests that attempt to set a timeout such that the copy of autopkgtest under test will fail, by timing out at a specified point in th

Bug#1093258: libsecret-tools: file conflict with bash-completion

Package: libsecret-tools,bash-completion Severity: serious Justification: Policy 7.6 Tags: trixie sid User: debian...@lists.debian.org Usertags: fileconflict Control: found -1 libsecret-tools/0.21.6-1 Control: found -1 bash-completion/1:2.16.0-6 Forwarded: https://github.com/scop/bash-completion/is

Bug#1093200: librsvg: FTBFS on mips64el: error: failed to acquire jobserver token; Caused by: Bad address (os error 14)

On Fri, 17 Jan 2025 at 01:12:41 +0200, Adrian Bunk wrote: > There is recently a general instability/race in mips64el Rust/Go/Erlang > builds, the most common pattern is that the build often (but not always) > fails. In Go/Erlang packages, was this also with error messages suggesting EFAULT ("Bad

Bug#1074863: caribou: FTBFS with gcc-14

Control: tags -1 - pending Control: tags -1 + patch help On Thu, 16 Jan 2025 at 12:52:04 +, Simon McVittie wrote: > This looks like code that was generated by valac. Patching the C code > that was generated by valac is not sustainable: the actual source code > is modules/gtk3/ca

Bug#1074863: marked as pending in caribou

Control: tag -1 pending Hello, Bug #1074863 in caribou reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/caribou/-/commit/ee157f6a182da35ccadea2926fa03

Bug#1074863: caribou: FTBFS with gcc-14

Control: tags -1 - patch On Wed, 04 Dec 2024 at 21:37:39 +, Rebecca N. Palmer wrote: > Control: tags -1 patch > > This (untested) patch may fix this bug ... > - CaribouKeyboard* _tmp2_ = NULL; > - CaribouKeyboard* _tmp3_ = NULL; > + GAsyncInitable* _t

Bug#1093200: Some packages consistently FTBFS with EFAULT (Bad address) on most mips64el buildds

hat am 16.01.2025 11:55 CET > > geschrieben: > > On Thu, 16 Jan 2025 11:45, Simon McVittie wrote: > > >The error message "failed to acquire jobserver token" seems to come from > > >rustc or cargo, so I think this FTBFS bug should probably be reassigned > >

Bug#1093200: librsvg: FTBFS on mips64el: error: failed to acquire jobserver token; Caused by: Bad address (os error 14)

Control: found -1 2.58.93+dfsg-2 On Thu, 16 Jan 2025 at 10:45:28 +, Simon McVittie wrote: > librsvg/2.59.2+dfsg-1 failed to build on mips64el across multiple retries, > most recently in > <https://buildd.debian.org/status/fetch.php?pkg=librsvg&arch=mips64el&ver=2

Bug#1091629: src:librsvg: fails to migrate to testing for too long

On Sat, 28 Dec 2024 at 21:21:37 +0100, Paul Gevers wrote: > Your package src:librsvg has been trying to migrate for 31 days [2], > hence this bug report. ... > Issues preventing migration: > ∙ ∙ missing build on mips64el As far as I can tell from build logs, this seems to be an architecture-specif

Bug#1093200: librsvg: FTBFS on mips64el: error: failed to acquire jobserver token; Caused by: Bad address (os error 14)

Source: librsvg Version: librsvg/2.59.2+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-r...@lists.debian.org, debian-m...@lists.debian.org User: debian-m...@lists.debian.org Usertags: mips64el Control: block 1

Bug#1075540: marked as pending in startup-notification

Control: tag -1 pending Hello, Bug #1075540 in startup-notification reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/startup-notification/-/commit/04c

Bug#1074854: brasero: FTBFS with gcc-14

On Sun, 12 Jan 2025 at 12:28:10 +, Simon McVittie wrote: > I have a USB optical drive and some media, so I can at least do a > smoke-test on it to get this RC bug fixed, assuming my blank media > haven't completely delaminated by now. In fact it doesn't work: with the patc

Bug#1030130: libgnome-bluetooth13: superseded version of gnome-bluetooth3, should be removed eventually

On Sun, 12 Jan 2025 at 20:36:25 +0100, Bastian Germann wrote: > On Fri, 6 Dec 2024 10:38:16 +0000 Simon McVittie wrote: > > We should remove this unmaintained upstream code from Debian, but at the > > moment we cannot, because budgie-control-center (#1059485) and budgie-core

Bug#1074854: brasero: FTBFS with gcc-14

On Tue, 03 Dec 2024 at 17:19:03 -0500, Jeremy Bícha wrote: > On Tue, Dec 3, 2024 at 4:48 PM Rebecca N. Palmer > wrote: > > This applies the above upstream patch to Debian brasero; it builds, but > > that's all the testing it's had. > > > > https://salsa.debian.org/rnpalmer-guest/brasero > > The D

Bug#1092086: marked as pending in autopkgtest

Control: tag -1 pending Hello, Bug #1092086 in autopkgtest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ci-team/autopkgtest/-/commit/d8f48d11c7901b66c42f4159

Bug#1092398: autopkgtest: FTBFS: tests fail

Control: tags -1 + pending On Tue, 07 Jan 2025 at 20:28:33 +0100, Lucas Nussbaum wrote: > > Traceback (most recent call last): > > File "/<>/tests/autopkgtest", line 1898, in > > test_build_parallel > > self.assertIn('dh build', err) > > AssertionError: 'dh build' not found in [a long strin

Bug#1092323: 0ad ftbfs with Python 3.13 as the default

On Tue, 07 Jan 2025 at 13:33:25 +0100, Matthias Klose wrote: > File > "/<>/libraries/source/spidermonkey/mozjs-78.6.0/third_party/python/virtualenv/virtualenv/discovery/cached_py_info.py", > line 11, in > import pipes > ModuleNotFoundError: No module named 'pipes' This is a vendored copy o

Bug#1092086: marked as pending in autopkgtest

Control: tag -1 pending Hello, Bug #1092086 in autopkgtest reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ci-team/autopkgtest/-/commit/4ac97c10528c9dc81351adde

Bug#1091959: wlmaker: FTBFS: fatal error: wlr/util/box.h: No such file or directory

Control: reassign -1 libwlroots-0.18-dev 0.18.2-1 Control: forcemerge 1091934 -1 On Thu, 02 Jan 2025 at 18:09:51 +, Santiago Vila wrote: > During a rebuild of all packages in unstable, [wlmaker] failed to build ... > Package lcms2 was not found in the pkg-config search path. > Perhaps you shou

Bug#1091934: [various packages]: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found

Control: reassign -1 libwlroots-0.18-dev 0.18.2-1 Control: forcemerge 1091934 -1 On Thu, 02 Jan 2025 at 18:45:41 +, Simon McVittie wrote: > On Thu, 02 Jan 2025 at 18:09:04 +, Santiago Vila wrote: > > During a rebuild of all packages in unstable, [gamescope] failed to build: >

Bug#1091934: libwlroots-0.18-dev: missing dependency on liblcms2-dev

On Thu, 02 Jan 2025 at 18:45:41 +, Simon McVittie wrote: > Control: reassign -1 libwlroots-0.18-dev 0.18.2-1 > Control: retitle -1 libwlroots-0.18-dev: missing dependency on liblcms2-dev Sorry, I forgot to cc the wlroots maintainers when reassigning. Quoting full text below. > On Th

Bug#1091934: gamescope: FTBFS: Package 'lcms2', required by 'wlroots-0.18', not found

Control: reassign -1 libwlroots-0.18-dev 0.18.2-1 Control: retitle -1 libwlroots-0.18-dev: missing dependency on liblcms2-dev Control: affects -1 + src:cage src:gamescope src:phoc src:reform-firedecor src:sway src:wayfire src:wayfire-shadows src:wcm src:wf-shell src:wstroke On Thu, 02 Jan 2025 at

Bug#1091290: marked as pending in xdg-desktop-portal

Control: tag -1 pending Hello, Bug #1091290 in xdg-desktop-portal reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/debian/xdg-desktop-portal/-/commit/6df913f62fe

Bug#1091290: FTBFS with libportal 0.9.0

Control: retitle -1 xdg-desktop-portal: FTBFS with libportal 0.9.0 Control: tags -1 = ftbfs trixie sid pending Control: fixed -1 1.19.0-1 On Mon, 23 Dec 2024 at 18:44:04 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, this package failed to build > on armhf. > > This packa

Bug#1075629: marked as pending in vte

Control: tag -1 pending Hello, Bug #1075629 in vte reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/vte/-/commit/7ce8009dad206da4c0b9340724a092079397e

Bug#885563: vte: Do not release with forky

Control: retitle -1 vte: Do not release with forky Control: tags -1 = forky sid experimental On Thu, 12 Jan 2023 at 10:17:07 +, Simon McVittie wrote: > The transition/toolchain freeze for bookworm is today, so it's clearly > too late to port d-i to GTK 3 for bookworm, and we are

Bug#1084705: rhythmbox: removal of Python standard libraries in Python 3.13

Control: tags -1 + fixed-upstream pending Control: forwarded -1 https://gitlab.gnome.org/GNOME/rhythmbox/-/merge_requests/185 On Mon, 07 Oct 2024 at 12:25:36 -0400, Louis-Philippe Véronneau wrote: > The following removed libraries were found in this package: > > cgi: plugins/context/AlbumTab.py:

Bug#1091290: xdg-desktop-portal: FTBFS on armhf: handle_add_notification: 'g_variant_equal (notification, arg_notification)' should be TRUE

Control: retitle -1 xdg-desktop-portal: FTBFS on armhf: handle_add_notification: 'g_variant_equal (notification, arg_notification)' should be TRUE Control: tags -1 + moreinfo On Mon, 23 Dec 2024 at 18:44:04 +0100, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, this package fail

Bug#1090228: marked as pending in gobject-introspection

Control: tag -1 pending Hello, Bug #1090228 in gobject-introspection reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/gobject-introspection/-/commit/c

Bug#1090228: gobject-introspection: FTBFS: dpkg-checkbuilddeps: error: Unmet build dependencies: python3-markdown:native

On Mon, 16 Dec 2024 at 17:50:25 +, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed to build The build log from reproducible-builds.org suggests that the problem is that apt and dpkg disagree on whether the build-dependencies are met, most likely trigger

Bug#1086701: autopkgtest: Same package version considered downgrade

Control: severity -1 important On Tue, 05 Nov 2024 at 08:02:45 +0100, Paul Gevers wrote: > This bug is not about a policy violation, or > makes the package unsuitable for release IMHO. This is a corner case that > hasn't surfaced in all those years. I agree that this is an important but non-RC bu

Bug#1089631: marked as pending in glib2.0

Control: tag -1 pending Hello, Bug #1089631 in glib2.0 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/glib/-/commit/7d961485542e1a4d53c038354d3ed2cf

Bug#1038835: marked as pending in autopkgtest

reading /etc/timezone when reading the host time zone, and create both /etc/localtime (unconditionally) and /etc/timezone (only if it already exists) when writing. Closes: #1038835 Signed-off-by: Simon McVittie (this message

Bug#1078361: maybe fixed Re: glib-networking FTBFS

Control: affects 1087919 + src:glib-networking On Sun, 08 Dec 2024 at 13:09:35 +, Rebecca N. Palmer wrote: > This package [...] > sometimes fails on armhf but that's a different problem, where it thinks > it's in a cross environment That's #1087919 in meson, which affects many GNOME-adjacent

Bug#1073400: gtk-doc: FTBFS with libxml2 2.12.x: XInclude error : could not load ../../examples/gobject.c

Control: retitle -1 gtk-doc: FTBFS with libxml2 2.12.x: XInclude error : could not load ../../examples/gobject.c Control: severity -1 important On Sun, 08 Dec 2024 at 12:59:06 +, Rebecca N. Palmer wrote: > gtk-doc also FTBFS in reproducible-builds from approximately 2024-05-30 to > 2024-09-24

Bug#1088319: trying to overwrite '/usr/share/doc/gprofng/examples.tar.gz', which is also in package binutils 2.43.50.20241126-1

On Tue, 26 Nov 2024 at 23:19:02 +0100, Johannes Schauer Marin Rodrigues wrote: > there is a file conflict between binutils and binutils-multiarch: ... > dpkg: error processing archive > /tmp/apt-dpkg-install-T6W0LR/8-binutils-multiarch_2.43.50.20241126-1_amd64.deb > (--unpack): > trying to overw

Bug#1087828: openal-soft: FTBFS on ppc64el: error: ‘tmp’ was not declared in this scope

Control: forwarded -1 https://github.com/kcat/openal-soft/issues/1061 On Tue, 19 Nov 2024 at 09:33:52 +0100, Matthias Klose wrote: > /<>/common/pffft.cpp: In function ‘void > {anonymous}::uninterleave2(v4sf, v4sf, v4sf&, v4sf&)’: ... > /<>/common/pffft.cpp:130:12: error: ‘tmp’ was not declared in

Bug#1087824: openal-soft: FTBFS on armel: static assertion failed: std::atomic::is_always_lock_free

Control: forwarded -1 https://github.com/kcat/openal-soft/issues/1059 On Tue, 19 Nov 2024 at 09:33:52 +0100, Matthias Klose wrote: > /<>/core/device.cpp:12:54: error: static assertion failed >12 | > static_assert(std::atomic::is_always_lock_free); If OpenAL now requires lock-free atomics, the

Bug#1087824: openal-soft ftbfs on armel and ppc64el

Control: clone -1 -2 Control: retitle -1 openal-soft: FTBFS on armel: static assertion failed: std::atomic::is_always_lock_free Control: retitle -2 openal-soft: FTBFS on ppc64el: error: ‘tmp’ was not declared in this scope On Tue, 19 Nov 2024 at 09:33:52 +0100, Matthias Klose wrote: > openal-sof

Bug#1087712: glib2.0: autopkgtest regression on amd64: gsubprocess.test timed out after 300 seconds

Source: glib2.0 Version: 2.82.2-2 Severity: serious Justification: rc_policy.txt 6a X-Debbugs-Cc: debian...@lists.debian.org GLib is failing its autopkgtests on amd64 since about 2024-11-12 (the most recent successful test was 2024-11-09, the first failed test I see was 2024-11-12). I think the im

Bug#1084616: marked as pending in mozjs

Control: tag -1 pending Hello, Bug #1084616 in mozjs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/mozjs/-/commit/3f45d5a35b020314088274999686944cf

Bug#1084616: mozjs128: removal of Python standard libraries in Python 3.13

On Mon, 07 Oct 2024 at 17:34:15 +0100, Simon McVittie wrote: > On Mon, 07 Oct 2024 at 12:19:25 -0400, Louis-Philippe Véronneau wrote: > > cgi: testing/web-platform/tests/tools/runner/report.py:9 > > cgi: testing/web-platform/tests/tools/wptserve/wptserve/request.py:4 > > telne

Bug#1084616: marked as pending in mozjs

Control: tag -1 pending Hello, Bug #1084616 in mozjs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/mozjs/-/commit/3f45d5a35b020314088274999686944cf

Bug#1082282: libunwind: FTBFS on i386: passing argument 1 of '_Ux86_sigreturn' from incompatible pointer type

On Fri, 15 Nov 2024 at 15:16:04 +0100, Alban Browaeys wrote: > Upgrading to 1.8.1 would fix this bug. If it is doable let's do it. But > it might requires a migration of the packages that depends on > libunwind-18 (would it be libunwind-19) so I it might not help with > these packages depending on

Bug#1087562: pcre2: FTBFS on mips64el: ld: unrecognised emulation mode: elf

On Fri, 15 Nov 2024 at 10:24:34 +, Simon McVittie wrote: > This looks like it might be a problem with some toolchain component > (but I don't know which one), so please reassign and set "affects" on > src:pcre2 as appropriate. In fact I think this could be a bug t

Bug#1087562: pcre2: FTBFS on mips64el: ld: unrecognised emulation mode: elf

On Fri, 15 Nov 2024 at 10:42:06 +, Matthew Vernon wrote: > Control: tags -1 help (Probably best to keep the Cc to debian-m...@lists.debian.org when asking for help with a mips*-specific bug!) > Hm. AFAICT there is no mips64el porterbox available to test things on, only > buildds which don't h

Bug#1087564: pcre2: FTBFS on 32-bit: test failures, memory allocations smaller than expected

Source: pcre2 Version: 10.44-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org, debian-h...@lists.debian.org, debian-powe...@lists.debian.org, b...@debian.org User: debian-...@lists.debian.org Us

Bug#1087563: pcre2: FTBFS on armel: RunTest and pcre2_jit_test segfault

Source: pcre2 Version: 10.44-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org User: debian-...@lists.debian.org Usertags: armel https://buildd.debian.org/status/fetch.php?pkg=pcre2&arch=armel&ve

Bug#1087562: pcre2: FTBFS on mips64el: ld: unrecognised emulation mode: elf

Source: pcre2 Version: 10.44-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-m...@lists.debian.org User: debian-m...@lists.debian.org Usertags: mips64el This looks like it might be a problem with some toolchain com

Bug#1087418: src:xorg-server FTBFS: Xvfb compile time check fails in pbuilder/cowbuilder chroot

On Wed, 13 Nov 2024 at 09:55:43 +, Mark Hindley wrote: > In version 21.1.14-2 of src:xorg-server, the new compile time Xvfb check fails > in a pbuilder/cowbuilder chroot: > > sudo cowbuilder --build --basepath /var/cache/pbuilder/base-sid.cow/ > xorg-server_21.1.14-2.dsc ... > # Check basic f

Bug#1075558: telepathy-glib: ftbfs with GCC-14

On Wed, 03 Jul 2024 at 12:45:35 +, Matthias Klose wrote: > The package fails to build in a test rebuild on at least amd64 with > gcc-14/g++-14, but succeeds to build with gcc-13/g++-13 Patch from upstream proposed at https://salsa.debian.org/telepathy-team/telepathy-glib/-/merge_requests/1 It

Bug#1085704: Bug#1084230: xvfb: please consider disabling libunwind, at least on armhf

Control: tags -1 + patch On Sun, 06 Oct 2024 at 23:15:55 +0100, Simon McVittie wrote: > Until libunwind can be investigated and fixed (presumably by a porter?), > I think it would be better to disable this optional feature on armhf, > so that X11-related packages can rely on being ab

Bug#1086552: marked as pending in mutter

Control: tag -1 pending Hello, Bug #1086552 in mutter reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/mutter/-/commit/04b79a1d36500d070a2fa5a650901d0

Bug#1086720: libsdl3: not ready to include in a stable release

Source: libsdl3 Version: 3.1.3+ds-1 Severity: serious Tags: upstream Forwarded: https://github.com/libsdl-org/SDL/milestone/10 With the 3.1.3 preview release having frozen the API and ABI, I think libsdl3 is ready to go to unstable, but it should probably not be included in trixie until we reach t

Bug#1086552: mutter: sometimes FTBFS: mutter:clutter+clutter/conform / timeline: FAIL: missed 1 frame

Source: mutter Version: 47.1-1 Severity: serious Tags: ftbfs experimental Justification: fails to build from source (but built successfully in the past) mutter failed to build from source on several architectures, including 'all', with this failure in the "mutter:clutter+clutter/conform / timeline

Bug#1086551: ansible-core: uninstallable in unstable: Depends: python3-resolvelib (< 1.1.0)

Package: ansible-core Version: 2.17.5-4 Severity: grave Tags: upstream Justification: renders package unusable Forwarded: https://github.com/ansible/ansible/issues/84217 X-Debbugs-Cc: python-resolve...@packages.debian.org, by...@debian.org $ podman run --rm -it debian:sid-slim # apt upate # apt up

Bug#1086443: mpg123: CVE-2024-10573: buffer overflow involving "Frankenstein streams" in versions before 1.32.8

Control: retitle -1 mpg123: CVE-2024-10573: buffer overflow involving "Frankenstein streams" in versions before 1.32.8 Control: forwarded -1 https://www.openwall.com/lists/oss-security/2024/10/30/2 On Wed, 30 Oct 2024 at 19:11:57 +0000, Simon McVittie wrote: > There is curren

Bug#1086443: mpg123: buffer overflow involving "Frankenstein streams" in versions before 1.32.8

Source: mpg123 Version: 0.59f-1 Severity: grave Tags: security upstream Justification: user security hole X-Debbugs-Cc: Debian Security Team Control: fixed -1 1.32.8-1 Forwarding this from : > There is possible buffer overflow > (writing

Bug#1086238: libgphoto2 FTBFS on 32-bit with gcc 14

Control: forwarded -1 https://github.com/gphoto/libgphoto2/issues/941 Control: tags -1 + fixed-upstream patch On Tue, 29 Oct 2024 at 15:14:19 +0200, Adrian Bunk wrote: > ptp2/chdk.c: In function 'yuv_live_to_jpeg': > ptp2/chdk.c:1187:41: error: passing argument 3 of 'jpeg_mem_dest' from > incompa

Bug#1086298: mozjs128: FTBFS: js/src/tests/non262/Date/parse-dashed-numeric-date.js fails to parse a post-Y10K date

Control: forwarded -1 https://bugzilla.mozilla.org/show_bug.cgi?id=1928015 Control: tags -1 + upstream patch pending On Tue, 29 Oct 2024 at 20:25:12 +0100, Santiago Vila wrote: > In this case, the package built ok in the buildds several weeks ago > but it fails to build now, so I would bet it's so

Bug#1086298: marked as pending in mozjs

Control: tag -1 pending Hello, Bug #1086298 in mozjs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/mozjs/-/commit/fa74cf3003b039ed847e978dfb4d8d8a9

Bug#1086295: closed by Simon McVittie (Re: Bug#1086295: meson-python: FTBFS: failing tests)

On Tue, 29 Oct 2024 at 20:37:16 +0100, Santiago Vila wrote: > El 29/10/24 a las 20:09, Debian Bug Tracking System escribió: > > I believe these test failures are all regressions triggered by new > > versions of meson-python's dependencies, and are fixed in 0.17.1 > > Can you tell me which packages

Bug#1086298: mozjs128: FTBFS: js/src/tests/non262/Date/parse-dashed-numeric-date.js fails to parse a post-Y10K date

On Tue, 29 Oct 2024 at 20:25:12 +0100, Santiago Vila wrote: > In this case, the package built ok in the buildds several weeks ago > but it fails to build now, so I would bet it's something related to > the recent tzdata changes. Jeremy uploaded 128.4.0 today, so let's wait for the buildds to try t

Bug#1086298: mozjs128: FTBFS: js/src/tests/non262/Date/parse-dashed-numeric-date.js fails to parse a post-Y10K date

Control: retitle -1 mozjs128: FTBFS: js/src/tests/non262/Date/parse-dashed-numeric-date.js fails to parse a post-Y10K date On Tue, 29 Oct 2024 at 19:47:44 +0100, Santiago Vila wrote: > The above is just how the build ends and not necessarily the most relevant > part. The only non-ignored test

Bug#1086241: libglobus-common-dev: breaks build of lcmaps by setting _FILE_OFFSET_BITS empty

Package: libglobus-common-dev Version: 18.14-2 Severity: serious Tags: ftbfs trixie sid Justification: breaks build of src:lcmaps X-Debbugs-Cc: denni...@nikhef.nl, jw...@jwilk.net, lcm...@packages.debian.org Control: affects -1 + src:lcmaps During the recent binNMUs of much of the archive, lcmaps

Bug#1086231: libchamplain: FTBFS on 32-bit with 64-bit time_t: passing argument 1 of ‘gmtime’ from incompatible pointer type

Source: libchamplain Version: 0.12.21-1 Severity: serious Tags: ftbfs trixie sid upstream Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org User: debian-...@lists.debian.org Usertags: armel armhf Forwarded: https://gitlab.gnome.

Bug#1086148: marked as pending in dbus

Control: tag -1 pending Hello, Bug #1086148 in dbus reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/utopia-team/dbus/-/commit/ede4b07ac1fc79b161c066ac30d4a3fbd8

Bug#1086140: ostree: FTBFS against gpg 2.2.45: gpg --import for revocation cert exits 2

Control: reassign -1 gpg 2.2.45-1 Control: affects -1 + src:ostree On Sun, 27 Oct 2024 at 18:08:16 +0100, Andreas Metzler wrote: > On 2024-10-27 Simon McVittie wrote: > [...] > > I can reproduce [a FTBFS in src:ostree]. > > Is it intentional that importing a revocation certi

Bug#1086148: dbus: FTBFS: ERROR: test-bus-dispatch - exited with status 134 (terminated by signal 6?)

Control: tags -1 + pending On Sun, 27 Oct 2024 at 15:56:11 +0100, Aurelien Jarno wrote: > I have tracked down the issue to the use of systemd >= 256~rc3-3 on the > host, which bumps the maximum number of open files hard limit from > 1048576 to 1073741816 [1]. Good catch! I have been looking into

Bug#1086140: ostree: FTBFS against gpg 2.2.45: gpg --import for revocation cert exits 2

Control: retitle -1 ostree: FTBFS against gpg 2.2.45: gpg --import for revocation cert exits 2 On Sun, 27 Oct 2024 at 11:14:57 +0100, Andreas Metzler wrote: > ostree throws a CI error and FTBFS against current sid with gpg > 2.2.45: > > ERROR: tests/test-remote-gpg-list-keys.sh - too few tests r

Bug#1086036: marked as pending in glib2.0

Control: tag -1 pending Hello, Bug #1086036 in glib2.0 reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/glib/-/commit/7f5123595c2599d6cf4bc7b555ee5943

Bug#1082723: marked as pending in pygobject

Control: tag -1 pending Hello, Bug #1082723 in pygobject reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/pygobject/-/commit/6de26f16648960f34567282ce

Bug#1086025: loupe: FTBFS with DEB_BUILD_OPTIONS=optimize=-lto: Unrecognized option: 'config'

Control: reassign -1 cargo Control: retitle -1 cargo wrapper: `--config lto` wrongly gets passed along to cargo test Control: affects -1 + src:loupe > > Where does that wrapper come from? I'm guessing src:rustc? Are its > > maintainers aware of this problem? > It comes from bin:cargo. f_g (added

Bug#1086025: loupe: FTBFS with DEB_BUILD_OPTIONS=optimize=-lto: Unrecognized option: 'config'

On Fri, 25 Oct 2024 at 16:24:40 +0200, Matthias Geiger wrote: > On Fri, 25 Oct 2024 10:41, Simon McVittie wrote: > > I don't know Rust, but this looks to me to be more like a problem with > > how `cargo test` is invoking the test executable, rather than a problem > >

Bug#1086028: loupe: FTBFS on mips64el: failed to acquire jobserver token: Bad address (os error 14)

Control: severity -1 important Control: tags -1 + unreproducible On Fri, 25 Oct 2024 at 09:48:45 +0100, Simon McVittie wrote: > > error: failed to acquire jobserver token > > > > Caused by: > > Bad address (os error 14) > > I've retried the build: if it succ

Bug#1086028: loupe: FTBFS on mips64el: failed to acquire jobserver token: Bad address (os error 14)

Source: loupe Version: 47.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-m...@lists.debian.org, debian-r...@lists.debian.org User: debian-m...@lists.debian.org Usertags: mips64el loupe 47.1-2 failed to build on

Bug#1086025: loupe: FTBFS with DEB_BUILD_OPTIONS=optimize=-lto: Unrecognized option: 'config'

Source: loupe Version: 47.1-2 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-r...@lists.debian.org loupe failed to build (again) on the 32-bit release architectures armel, armhf and i386: https://buildd.debian.org/

Bug#1082723: pygobject: FTBFS: ../tests/gimarshallingtestsextra.h:40:1: error: unknown type name ‘_GI_TEST_EXTERN’

Control: retitle -1 pygobject: FTBFS with gobject-introspection 1.82.0: unknown type name ‘_GI_TEST_EXTERN’ Control: fixed -1 3.50.0-1 Control: tags -1 + fixed-upstream On Wed, 25 Sep 2024 at 00:30:24 +0200, Santiago Vila wrote: > During a rebuild of all packages in unstable, your package failed

Bug#1085891: marked as pending in pygobject

Control: tag -1 pending Hello, Bug #1085891 in pygobject reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/gnome-team/pygobject/-/commit/5987bb5ea2a963042bac48b76

Bug#1085891: pygobject: 3.50.0 regression: FTBFS on big-endian: TestAsync failures

Source: pygobject Version: 3.50.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) User: debian-s...@lists.debian.org Usertags: s390x X-Debbugs-Cc: debian-s...@lists.debian.org, debian-powe...@lists.debian.org, debian-sp...@lists.debian

Bug#1085890: loupe: FTBFS on i386: rustc-LLVM ERROR: out of memory; Couldn't compile the test

Source: loupe Version: 47.0-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-r...@lists.debian.org, b...@debian.org Control: block 1085885 by -1 User: debian...@lists.debian.org Usertags: i386 loupe failed to build

Bug#1037307: totem: Gnome Video refuses to start complaining about missing important plugin.

Control: severity -1 important Control: tags -1 + moreinfo unreproducible On Sat, 10 Jun 2023 at 23:40:38 +0200, Abou Al Montacir wrote: > After installing Bookworm on my computer (kept my home from Bullseye), I can't > start any video/audio file using Gnome Video. Do you still see a similar prob

Bug#1084137: gnome-control-center: Appearance panel breaks when x-d-p-gnome >= 47 not available

Control: retitle -1 gnome-control-center: Appearance panel breaks when x-d-p-gnome >= 47 not available Control: severity -1 normal On Sat, 05 Oct 2024 at 10:59:20 -0400, Jeremy Bícha wrote: > we at least don't want gnome-control-center 47 to migrate > before xdg-desktop-portal-gnome so I'm filing

Bug#1084916: libgtk-4-1 should not recommend (CUPS v3) cpdb-backend-cups

On Thu, 10 Oct 2024 at 23:43:00 -0500, Daniel Lewart wrote: > Could Commit 1d4a5968 be reverted for the time being? I tried to revert this for Debian (while leaving Ubuntu as-is) in https://salsa.debian.org/gnome-team/gtk4/-/merge_requests/30 but I'm now seeing an intermittent crash (perhaps 50% o

Bug#1082121: libostree-1-1: `flatpak update` fails: src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached

On Wed, 18 Sep 2024 at 16:39:42 +0100, Simon McVittie wrote: > After upgrading curl to 8.10.0, `flatpak update` fails with: > > > OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should > > not be reached > > Bail out! OSTree:ERROR:src/libostree/o

Bug#1082121: libostree-1-1: `flatpak update` fails: src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached

On Fri, 04 Oct 2024 at 19:45:52 +0100, Simon McVittie wrote: > If you can downgrade libcurl3-gnutls back to the version > from stable, that should avoid this issue. On the upstream issue https://github.com/ostreedev/ostree/issues/3299, Github user phlibi tried to downgrade the curl, libcur

Bug#1082121: libostree-1-1: `flatpak update` fails: src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached

On Fri, 04 Oct 2024 at 19:45:52 +0100, Simon McVittie wrote: > I have asked the stable release team to include a fixed version of ostree > (compatible with the backported libcurl) in the next Debian 12 point > release, but the proposed version has not yet been approved. If/when > the

Bug#1084133: mutter: FTBFS on armhf: Directory "/tmp/.X11-unix" is not writable

Control: tags -1 + pending On Sun, 06 Oct 2024 at 22:54:54 +0100, Simon McVittie wrote: > I think what is happening in mutter could perhaps be this: > > mutter requires /tmp/.X11-unix (for Xwayland) for some of its unit tests. > > On architectures where xvfb-run works as inten

Bug#1084133: mutter: FTBFS on armhf: Directory "/tmp/.X11-unix" is not writable

On Sat, 05 Oct 2024 at 14:19:50 +0100, Simon McVittie wrote: > 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

Bug#1084133: mutter: FTBFS on armhf: Directory "/tmp/.X11-unix" is not writable

On Sat, 05 Oct 2024 at 17:35:46 +0200, Aurelien Jarno wrote: > Everything is fine on the buildds side. Both arm64 and armhf chroots on > the above buildds have an empty 1777 root:root /tmp directory. ... > Chroots are created identically in schroot and unshare mode. /tmp is > part of the chroot, an

Bug#1084133: mutter: FTBFS on armhf: Directory "/tmp/.X11-unix" is not writable

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 u

Bug#1082121: libostree-1-1: `flatpak update` fails: src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached

On Fri, 04 Oct 2024 at 11:59:02 -0400, Steve wrote: > How are we supposed to upgrade this when a package isn't available > unless one downloads from another repository, other than Stable? You did already install a core system library (libcurl3-gnutls) from a repository other than stable (bookworm-

Bug#1082121: libostree-1-1: `flatpak update` fails: src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should not be reached

Control: found -1 2022.7-2 On Wed, 18 Sep 2024 at 16:39:42 +0100, Simon McVittie wrote: > After upgrading curl to 8.10.0, `flatpak update` fails with: > > > OSTree:ERROR:src/libostree/ostree-fetcher-curl.c:534:sock_cb: code should > > not be reached > > Bail out! OS

Bug#1082679: freedoom: FTBFS with .dsc from archive: mis-detects that deutex does not support PNG

On Mon, 30 Sep 2024 at 15:46:24 +0200, Fabian Greffrath wrote: > Maybe the `deutex -h` output to stdout get spoiled by other build steps > running in parralel, so that it doesn't include "PNG" as an isolated word > anymore? That shouldn't be the case, assuming the shell is working correctly: it's

Bug#1083043: directvnc: should this package be removed?

Source: directvnc Severity: serious Tags: trixie sid User: debian...@lists.debian.org Usertags: directfb Control: block 1083037 by -1 directfb has been orphaned (unmaintained) in Debian since 2018 (see also #1083037) and I think it's time to consider removing it from the distribution. If I am read

Bug#1082679: freedoom: FTBFS with .dsc from archive: mis-detects that deutex does not support PNG

On Mon, 30 Sep 2024 at 13:06:31 +0200, Santiago Vila wrote: > - When I build with 1 CPU, I have never found the build problem so far. > - When I build with 2 CPUs, I got a failure rate of 66% > (16 failures over 24 tries so far). When I tried this, it was consistently failing if and only if I use

Bug#1083037: directfb: Should this package be removed?

Source: directfb Severity: serious Justification: ensure visibility for potential adopters X-Debbugs-Cc: debian-...@lists.debian.org, debian...@lists.debian.org User: debian...@lists.debian.org Usertags: directfb directfb has been unmaintained in Debian since 2018, and its web pages directfb.org a

Bug#1082679: freedoom: FTBFS with .dsc from archive: mis-detects that deutex does not support PNG

Control: retitle -1 freedoom: FTBFS with .dsc from archive: mis-detects that deutex does not support PNG On Tue, 24 Sep 2024 at 19:41:09 +0200, Santiago Vila forwarded: > deutex does not support PNG. Try building deutex with the PNG > libraries (libpng and libpng-devel or similar packages) instal

Bug#1082927: flatpak [LTS]: CVE-2024-42472: sandbox escape for apps with --persist=DIR permission

Source: flatpak Version: 1.10.8-0+deb11u2 Severity: grave Justification: user security hole Tags: bullseye security X-Debbugs-Cc: debian-...@lists.debian.org Control: found -1 1.2.5-0+deb10u4 Control: fixed -1 1.14.10-1~deb12u1 Control: fixed -1 1.14.10-1 Control: fixed -1 1.15.10-1 Advisory: http

  1   2   3   4   5   6   7   8   9   10   >