Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

Thanks, but can you sign this off? Ty! -- Sean Whitton

Bug#1066942: xmrig: FTBFS on armhf: cc: error: unrecognized command-line option ‘-maes’

Hello, Since my last message, I have tried to reproduce this in several ways, e.g. an sbuild chroot in both qemu-user-static and on actual hardware (Raspberry Pi 2), and also a direct build on an armhf VM. It always builds successfully. Since then, there has been a new upstream release of

Bug#1068290: python3-fastkml: ImportError since python3-pygeoif 1.4.0

Hi, On Wed, Apr 03, 2024 at 12:29:36AM +0100, Tomas Janousek wrote: I believe this is because both shapely and pygeoif deprecated asShape/as_shape respectively. The function is now called just "shape" in both. […] I think it might be okay to just patch fastkml/geometry.py to from

Bug#1068205: marked as done (gauche: FTBFS on arm{el,hf}: "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) == 0x7)

Your message dated Wed, 03 Apr 2024 00:19:22 + with message-id and subject line Bug#1068205: fixed in gauche 0.9.14-3 has caused the Debian Bug report #1068205, regarding gauche: FTBFS on arm{el,hf}: "list.c", line 827 (Scm__GetExtendedPairDescriptor): Assertion failed: (z->hiddenTag&0x7) ==

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 1067360 src:flint Bug #1067360 [src:macaulay2] macaulay2: FTBFS: make[3]: *** [../Makefile.library:235: /<>/M2/BUILD/tarfiles/normaliz-3.9.2.tar.gz] Error 1 Bug reassigned from package 'src:macaulay2' to 'src:flint'. No longer marked

Bug#1068290: python3-fastkml: ImportError since python3-pygeoif 1.4.0

Package: python3-fastkml Version: 0.12-3 Severity: grave Tags: upstream Justification: renders package unusable X-Debbugs-Cc: t...@nomi.cz Dear Maintainer, Since python3-pygeoif 1.4.0-1 appeared in Debian testing, fastkml cannot be imported at all: In [1]: import fastkml

Bug#1068288: openjdk-21: bootstrap builds required on armel and armhf

On 2024-04-03 00:20 +0200, Sebastian Ramacher wrote: > building openjdk-21 is currently still stuck on openjdk-21 > build-depending on itself: > > https://buildd.debian.org/status/package.php?p=openjdk-21 > > > Somebody did the work to provide boostrap builds of openjdk-17 on armel > and armhf.

Bug#1066289: marked as done (clipit: FTBFS: main.c:1080:9: error: implicit declaration of function ‘umask’ [-Werror=implicit-function-declaration])

Your message dated Tue, 02 Apr 2024 22:49:05 + with message-id and subject line Bug#1066289: fixed in clipit 1.4.5+git20210313-2 has caused the Debian Bug report #1066289, regarding clipit: FTBFS: main.c:1080:9: error: implicit declaration of function ‘umask’

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > reassign 1067262 src:flint Bug #1067262 {Done: Jerome Benoit } [src:e-antic] e-antic: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by

Bug#1056893: marked as done (uvloop: ftbfs with cython 3.0.x)

Your message dated Tue, 02 Apr 2024 22:22:27 + with message-id and subject line Bug#1056893: fixed in uvloop 0.19.0+ds1-2.1 has caused the Debian Bug report #1056893, regarding uvloop: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt

Processed: closing 1067286

Processing commands for cont...@bugs.debian.org: > # was a bug in flint > close 1067286 Bug #1067286 [src:msolve] msolve: FTBFS: dpkg-shlibdeps: error: no dependency information found for /lib/x86_64-linux-gnu/libflint.so.19 (used by debian/msolve/usr/bin/msolve) Marked Bug as done > thanks

Bug#1068288: openjdk-21: bootstrap builds required on armel and armhf

Source: openjdk-21 Version: 21.0.3~7ea-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org, debian-...@lists.debian.org Hi Matthias, hi arm* porters building openjdk-21 is currently still stuck on

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 1063596 3.1.1-1 Bug #1063596 {Done: "Torrance, Douglas" } [src:flint] flint: FTBFS on amd64: test segfault Marked as fixed in versions flint/3.1.1-1. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

Control: tags 1067796 + patch On Thu 2024-03-28 13:09:48 +0800, Sean Whitton wrote: > Please take a look into this test suite failure for your script. The attached patch should clean things up now that argcomplete is annotated. in my local tests, the script runs and exits cleanly. This patch

Processed: Re: Bug#1067796: mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment

Processing control commands: > tags 1067796 + patch Bug #1067796 [src:mailscripts] mailscripts: FTBFS: email-print-mime-structure:51: error: Unused "type: ignore" comment Added tag(s) patch. -- 1067796: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067796 Debian Bug Tracking System

Bug#1064728: marked as done (davfs2: FTBFS: configure: error: could not find neon)

Your message dated Tue, 02 Apr 2024 21:19:21 + with message-id and subject line Bug#1064728: fixed in davfs2 1.7.0-1 has caused the Debian Bug report #1064728, regarding davfs2: FTBFS: configure: error: could not find neon to be marked as done. This means that you claim that the problem has

Bug#1066439: marked as done (squidguard: FTBFS: ././conftest.c:17:(.text.startup+0xb): undefined reference to `yywrap')

Your message dated Tue, 02 Apr 2024 21:11:09 + with message-id and subject line Bug#1066439: fixed in squidguard 1.6.0-5 has caused the Debian Bug report #1066439, regarding squidguard: FTBFS: ././conftest.c:17:(.text.startup+0xb): undefined reference to `yywrap' to be marked as done. This

Bug#1068264: avfs: FTBFS on armel: ./src/xzread.c:185:(.text+0x1b0): undefined reference to `__atomic_fetch_add_8'

Source: avfs Version: 1.1.5-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: sramac...@debian.org https://buildd.debian.org/status/fetch.php?pkg=avfs=armel=1.1.5-1=1691158944=0 /bin/bash ../libtool --tag=CC

Bug#1063596: marked as done (flint: FTBFS on amd64: test segfault)

Your message dated Tue, 2 Apr 2024 21:00:12 + with message-id <87jzlfqy3t@piedmont.edu> and subject line Re: flint: FTBFS on amd64: test segfault has caused the Debian Bug report #1063596, regarding flint: FTBFS on amd64: test segfault to be marked as done. This means that you claim that

Bug#1067849: marked as done (util-linux: CVE-2024-28085: wall: escape sequence injection)

Your message dated Tue, 02 Apr 2024 20:33:09 + with message-id and subject line Bug#1067849: fixed in util-linux 2.36.1-8+deb11u2 has caused the Debian Bug report #1067849, regarding util-linux: CVE-2024-28085: wall: escape sequence injection to be marked as done. This means that you claim

Bug#1067115: marked as done (gross: CVE-2023-52159)

Your message dated Tue, 02 Apr 2024 20:32:32 + with message-id and subject line Bug#1067115: fixed in gross 1.0.2-4.1~deb11u1 has caused the Debian Bug report #1067115, regarding gross: CVE-2023-52159 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1067055: Bug#1064810: Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

On 2024-04-02 07:13:38 +0100, Alastair McKinstry wrote: > > On 01/04/2024 23:25, Sebastian Ramacher wrote: > > > There is a transition to openmpi-5 / mpi-defaults which is stalled by the > > > t64 transition. > > > > > > It drops 32-bit support from OpenMPI. > > > > > > Because of this, I don't

Bug#1068255: dnf: dnf aborts with ImportError: cannot import name '_module' from partially initialized module 'libdnf'

Package: dnf Version: 4.14.0-4.1 Severity: grave Justification: renders package unusable Dear Maintainer, I have just tried to start up dnf and it aborts with a following error: Traceback (most recent call last): File "/usr/bin/dnf", line 61, in from dnf.cli import main File

Bug#1068216: marked as done (aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures.)

Your message dated Tue, 02 Apr 2024 19:49:13 + with message-id and subject line Bug#1068216: fixed in aqemu 0.9.2-4 has caused the Debian Bug report #1068216, regarding aqemu, dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done. This means that you claim that

Bug#1067326: mkdocstrings: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13

Hi Carsten! On Wed, Mar 20, 2024 at 10:00:48PM +0100, Lucas Nussbaum wrote: > Source: mkdocstrings > Version: 0.24.1-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > User: lu...@debian.org > Usertags: ftbfs-20240319 ftbfs-trixie > > Hi, > > During a rebuild of all packages

Bug#1065305: marked as done (brewtarget: switch to boost 1.83)

Your message dated Tue, 02 Apr 2024 19:19:14 + with message-id and subject line Bug#1065305: fixed in brewtarget 3.0.11-1 has caused the Debian Bug report #1065305, regarding brewtarget: switch to boost 1.83 to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

Processing control commands: > found -1 glibc/2.37-15.1 Bug #1068188 [glibc-doc] pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1 Marked as found in versions glibc/2.37-15.1. -- 1068188: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068188 Debian Bug Tracking System Contact

Bug#1068188: pthread_cond_init.3.gz: conflict with manpages-dev 6.7-1

control: found -1 glibc/2.37-15.1 Hi, On 2024-04-01 16:23, Alejandro Colomar wrote: > Package: glibc-doc > Version: 2.38-6 > Severity: serious > Justification: Policy 7.4 > X-Debbugs-Cc: a...@kernel.org, mar...@debian.org > > Dear Maintainer, > > The Linux man-pages project has recently added

Bug#1068251: glibc: FTBFS on 32-bit architectures due to GCC defaulting to 64-bit time_t

Source: glibc Version: 2.37-15.1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) X-Debbugs-Cc: debian-...@lists.debian.org Starting with gcc-12 version 12.3.0-15, -D_TIME_BITS=64 together with -D_FILE_OFFSET_BITS=64 are passed by

Bug#1068213: marked as done (gnome-remote-desktop: hard-coded dependency on pre-t64 library)

Your message dated Tue, 02 Apr 2024 18:04:25 + with message-id and subject line Bug#1068213: fixed in gnome-remote-desktop 44.2-8 has caused the Debian Bug report #1068213, regarding gnome-remote-desktop: hard-coded dependency on pre-t64 library to be marked as done. This means that you

Processed: Re: Bug#1068016: bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2

Processing control commands: > tag -1 - confirmed + moreinfo Bug #1068016 [release.debian.org] bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2 Removed tag(s) confirmed. Bug #1068016 [release.debian.org] bookworm-pu: package node-babel7/7.20.15+ds1+~cs214.269.168-3+deb12u2

Bug#1068166: marked as done (manpages-dev: Fails to upgrade due to file conflict)

Your message dated Tue, 02 Apr 2024 16:50:01 + with message-id and subject line Bug#1068166: fixed in manpages 6.7-2 has caused the Debian Bug report #1068166, regarding manpages-dev: Fails to upgrade due to file conflict to be marked as done. This means that you claim that the problem has

Bug#1068167: marked as done (manpages-dev: Update to 6.7-1 fails)

Your message dated Tue, 02 Apr 2024 16:50:01 + with message-id and subject line Bug#1068166: fixed in manpages 6.7-2 has caused the Debian Bug report #1068166, regarding manpages-dev: Update to 6.7-1 fails to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1066194: marked as done (nstreams: FTBFS: parse_tcpdump.c:262:50: error: implicit declaration of function ‘int2proto’ [-Werror=implicit-function-declaration])

Your message dated Tue, 02 Apr 2024 16:34:58 + with message-id and subject line Bug#1066194: fixed in nstreams 1.0.4-1.1 has caused the Debian Bug report #1066194, regarding nstreams: FTBFS: parse_tcpdump.c:262:50: error: implicit declaration of function ‘int2proto’

Bug#1064170: mediastreamer2: NMU diff for 64-bit time_t transition

X-Debbugs-CC: Steve Langasek , Sebastian Ramacher Can I get confirmation that this will get uploaded before the autoremoval from testing on April 15th? Message #17 has the fixed NMU patch. Regards.

Processed: retitle 1059088 to whizzytex 1.3.7 is incompatible with texlive >= 2021, fixed 1059088 in 1.4.0-1 ...

Processing commands for cont...@bugs.debian.org: > retitle 1059088 whizzytex 1.3.7 is incompatible with texlive >= 2021 Bug #1059088 [whizzytex] whizzytex: deb file error Changed Bug title to 'whizzytex 1.3.7 is incompatible with texlive >= 2021' from 'whizzytex: deb file error'. > fixed 1059088

Processed: Re: python-meshplex: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-args=--ignore-glob=\*test_io\* returned exit code 13

Processing control commands: > tags -1 ftbfs Bug #1067308 [src:python-meshplex] python-meshplex: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-args=--ignore-glob=\*test_io\* returned exit code 13 Ignoring request to alter tags of bug #1067308

Bug#1067308: python-meshplex: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" --test-args=--ignore-glob=\*test_io\* returned exit code 13

Source: python-meshplex Followup-For: Bug #1067308 Control: tags -1 ftbfs I can't reproduce this error now. It must have been resolved by a separate library transition, or possibly a numpy update. If 0.17.1-3 passes tests successfully then we can close this bug.

Bug#1068243: marked as done (bsdgames: fails to configure)

Your message dated Tue, 02 Apr 2024 16:19:37 + with message-id and subject line Bug#1068243: fixed in bsdgames 2.17-32 has caused the Debian Bug report #1068243, regarding bsdgames: fails to configure to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1067378: marked as done (python-docs-theme: FTBFS: make: *** [debian/rules:4: build] Error 25)

Your message dated Tue, 02 Apr 2024 16:07:18 + with message-id and subject line Bug#1067378: fixed in python-docs-theme 2024.3-1 has caused the Debian Bug report #1067378, regarding python-docs-theme: FTBFS: make: *** [debian/rules:4: build] Error 25 to be marked as done. This means that you

Bug#1068243: bsdgames: fails to configure

Am 02.04.24 um 17:19 schrieb Sven Joachim: Package: bsdgames Version: 2.17-31 Severity: serious Your package fails to configure in a fresh installation (but not when upgrading from a previous version). This is what happens in a throwaway chroot (unrelated lines stripped from apt/dpkg output):

Bug#1067076: marked as done (x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’)

Your message dated Tue, 02 Apr 2024 15:53:44 + with message-id and subject line Bug#1067076: fixed in x11vnc 0.9.16-10 has caused the Debian Bug report #1067076, regarding x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’ to be marked as

Processed: Bug#1067076 marked as pending in x11vnc

Processing control commands: > tag -1 pending Bug #1067076 [src:x11vnc] x11vnc: FTBFS on arm{el,hf}: uinput.c:723:25: error: ‘struct input_event’ has no member named ‘time’ Added tag(s) pending. -- 1067076: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067076 Debian Bug Tracking System

Bug#1067076: marked as pending in x11vnc

Control: tag -1 pending Hello, Bug #1067076 in x11vnc 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:

Bug#1067391: marked as done (bitlbee-facebook: redundant dependency on libglib2.0-0)

Your message dated Tue, 02 Apr 2024 15:34:22 + with message-id and subject line Bug#1067391: fixed in bitlbee-facebook 1.2.2-3 has caused the Debian Bug report #1067391, regarding bitlbee-facebook: redundant dependency on libglib2.0-0 to be marked as done. This means that you claim that the

Bug#1068222: marked as done (libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures.)

Your message dated Tue, 02 Apr 2024 15:34:12 + with message-id and subject line Bug#1068222: fixed in appmenu-gtk-module 0.7.6-3 has caused the Debian Bug report #1068222, regarding libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures. to be marked as done.

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

On Tue, Apr 2, 2024 at 11:19 PM Sebastian Ramacher wrote: > > Hi > > On 2024-04-02 23:16:16 +0800, Bo YU wrote: > > Tags: patch > > > > Hi, > > > File "/<>/site_scons/extractdebbuild.py", line 61: > > >raise RuntimeError("We do not current support different different > > > dpkg-buildflags

Bug#1068222: marked as pending in appmenu-gtk-module

Control: tag -1 pending Hello, Bug #1068222 in appmenu-gtk-module 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:

Processed: Bug#1068222 marked as pending in appmenu-gtk-module

Processing control commands: > tag -1 pending Bug #1068222 [libappmenu-gtk3-parser0] libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) pending. -- 1068222: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068222 Debian Bug Tracking System

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

Hi On 2024-04-02 23:16:16 +0800, Bo YU wrote: > Tags: patch > > Hi, > > File "/<>/site_scons/extractdebbuild.py", line 61: > >raise RuntimeError("We do not current support different different > > dpkg-buildflags for C vs C++") > > make[1]: *** [debian/rules:65: override_dh_auto_build]

Bug#1068243: bsdgames: fails to configure

Package: bsdgames Version: 2.17-31 Severity: serious Your package fails to configure in a fresh installation (but not when upgrading from a previous version). This is what happens in a throwaway chroot (unrelated lines stripped from apt/dpkg output): , | # apt install bsdgames | Selecting

Bug#1068158: python-escript: FTBFS: RuntimeError: We do not current support different different dpkg-buildflags for C vs C++:

Tags: patch Hi, File "/<>/site_scons/extractdebbuild.py", line 61: raise RuntimeError("We do not current support different different dpkg-buildflags for C vs C++") make[1]: *** [debian/rules:65: override_dh_auto_build] Error 2 I have looked into this a bit. As the error hint here, the

Bug#1066248: [Pkg-electronics-devel] Bug#1066248: librnd: FTBFS: ../src/librnd/plugins/hid_lesstif/main.c:261:25: error: implicit declaration of function ‘lesstif_attr_sub_update_hidlib’ [-Werror=impl

Peter Michael Green writes: > The functions in question are defined in > src/librnd/plugins/hid_lesstif/dialogs.c > and used in src/librnd/plugins/hid_lesstif/main.c Correct. Upstream has fixed this and will have a new release on 10 April that I'm waiting for rather than patching the current

Bug#1068240: marked as done (nauty: autopkgtest regression in testing)

Your message dated Tue, 02 Apr 2024 15:05:06 + with message-id and subject line Bug#1068240: fixed in nauty 2.8.8+ds-3 has caused the Debian Bug report #1068240, regarding nauty: autopkgtest regression in testing to be marked as done. This means that you claim that the problem has been dealt

Processed: severity of 1056156 is important

Processing commands for cont...@bugs.debian.org: > severity 1056156 important Bug #1056156 [src:varnish] varnish: CVE-2023-44487: VSV00013 Varnish HTTP/2 Rapid Reset Attack Severity set to 'important' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#1060407: gtkwave update for {bookworm,bullseye,buster}-security

On Sun, Mar 31, 2024 at 01:52:40PM +0200, Moritz Mühlenhoff wrote: > Hi Adrian, Hi Moritz, >... > > debdiffs contain only changes to debian/ > > The bookworm/bullseye debdiffs looks good, please upload to security-master, > thanks! both are now uploaded. > Note that both need -sa, but dak

Processed: affects 1068242, block 1039583 with 1068242, block 1039612 with 1068242

Processing commands for cont...@bugs.debian.org: > affects 1068242 + src:libtool Bug #1068242 [release.debian.org] bookworm-pu: package libtool/2.4.7-7~deb12u1 Added indication that 1068242 affects src:libtool > block 1039583 with 1068242 Bug #1039583 {Done: Alastair McKinstry } [libltdl-dev]

Bug#1068240: nauty: autopkgtest regression in testing

Source: nauty Version: 2.8.8+ds-2 Severity: serious User: debian...@lists.debian.org Usertags: regression Hi Maintainer Sometime around 2024-01-23, nauty's autopkgtest regressed in testing [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1]

Processed: your mail

Processing commands for cont...@bugs.debian.org: > affects 1067226 src:polymake Bug #1067226 {Done: Doug Torrance } [src:flint] flint: libflint needs soversion bump to 19 Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for

Processed: your mail

Processing commands for cont...@bugs.debian.org: > forcemerge 1067226 1068140 Bug #1067226 {Done: Doug Torrance } [src:flint] flint: libflint needs soversion bump to 19 Bug #1067363 {Done: Doug Torrance } [src:flint] polymake: FTBFS: dpkg-shlibdeps: error: no dependency information found for

Processed: closing 1067339

Processing commands for cont...@bugs.debian.org: > close 1067339 Bug #1067339 [src:deal.ii] deal.ii: FTBFS: unsatisfiable build-dependencies Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1067339:

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

Hi, On Tue, Apr 02, 2024 at 02:32:16PM +0530, Pirate Praveen wrote: > Package: gnome-settings-daemon,phosh > severity: serious > > Recently automatic suspend stopped working. I think this was after gnome > settings daemon 46 was available. Some background >

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

On Tue, Apr 2, 2024 at 8:03 AM Jeremy Bícha wrote: > > On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen > wrote: > > Recently automatic suspend stopped working. I think this was after gnome > > settings daemon 46 was available. Some background > >

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

On Tue, Apr 2, 2024 at 5:31 AM Pirate Praveen wrote: > Recently automatic suspend stopped working. I think this was after gnome > settings daemon 46 was available. Some background > https://salsa.debian.org/Mobian-team/devices/librem5-support/-/issues/7 > > Not sure if phosh needs some

Bug#1066638: marked as done (ukui-screensaver: FTBFS: kylin-network-interface.c:199:5: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declarati

Your message dated Tue, 02 Apr 2024 11:55:00 + with message-id and subject line Bug#1066638: fixed in ukui-screensaver 3.0.3.3-1 has caused the Debian Bug report #1066638, regarding ukui-screensaver: FTBFS: kylin-network-interface.c:199:5: error: implicit declaration of function ‘asprintf’;

Processed: bug 1067712 is forwarded to https://github.com/rust-lang/stacker/issues/85

Processing commands for cont...@bugs.debian.org: > forwarded 1067712 https://github.com/rust-lang/stacker/issues/85 Bug #1067712 [src:rust-stacker] rust-stacker: FTBFS on mips64el: process didn't exit successfully: `/<>/target/mips64el-unknown-linux-gnuabi64/debug/deps/smoke-983e0e8761f2ceb1`

Processed: tagging 1068224, tagging 1068222, found 1067391 in 1.2.2-2, tagging 1067391, tagging 1068216 ...

Processing commands for cont...@bugs.debian.org: > tags 1068224 + sid trixie Bug #1068224 [deepin-movie] deepin-movie, dependencies unsatisfiable on 32-bit non-i386 architectures. Added tag(s) trixie and sid. > tags 1068222 + sid trixie Bug #1068222 [libappmenu-gtk3-parser0]

Processed: Re: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)

Processing control commands: > tag -1 sid trixie Bug #1068155 [src:lmms] lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp) Added tag(s) trixie and sid. -- 1068155:

Bug#1068155: lmms: FTBFS on i386: dh_install: warning: Cannot find (any matches for) "usr/lib/*/lmms/libvestige.so" (tried in ., debian/tmp)

Followup-For: Bug #1068155 Control: tag -1 sid trixie Comparing bookworm and sid buildlogs shows the following relevant differences during cmake: -Setting up libwine-dev:i386 (8.0~repack-4) ...^M +Setting up libwine-dev:i386 (9.0~repack-4+b1) ...^M --- Found Wine:

Processed: Re: fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed))

Processing control commands: > severity -1 normal Bug #1068067 [src:fpzip] fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed)) Severity set to 'normal' from 'serious' > found -1 1.3.0-2 Bug #1068067 [src:fpzip] fpzip: FTBFS on armel, armhf, i386 (1 -

Bug#1068067: fpzip: FTBFS on armel, armhf, i386 (1 - compress-decompress-validate (Failed))

Followup-For: Bug #1068067 Control: severity -1 normal Control: found -1 1.3.0-2 This is not a regression. Maybe a B-D: architecture-is-64-bit should be added. Andreas

Bug#1068230: automatic suspend regression with gnome-settings-daemon 46

Package: gnome-settings-daemon,phosh severity: serious Recently automatic suspend stopped working. I think this was after gnome settings daemon 46 was available. Some background Not sure if phosh needs some adjustments

Bug#1066594: octave-iso2mesh: FTBFS: nl_single_file.c:2505:26: error: implicit declaration of function ‘lsame_’ [-Werror=implicit-function-declaration]

* Qianqian Fang [2024-03-29 10:52]: On 3/29/24 01:24, Rafael Laboissière wrote: It seems so. If we fix Bug#1066594, then both octave-iso2mesh and octave-brain2mesh will be able to migrate into testing. thanks Rafael, replying to #1066594 it looks like someone from Fedora had submitted a

Bug#1067486: more information

On Mon, 1 Apr 2024 10:39:05 +0200 Bastian Blank wrote: binNMU are known to not work on the signing side of the archive. Shouldn't the affected packages fail early during the build (and with an informative error message) if a binNMU is attempted? S.t. these "broken" binNMUs don't show up in

Processed: opensearch: FTBFS with lucene9/9.10.0+dfsg

Processing control commands: > retitle -1 opensearch: FTBFS with lucene9/9.10.0+dfsg Bug #1066450 [src:opensearch] opensearch: FTBFS: server/src/main/java/org/opensearch/index/codec/CodecService.java:37: error: cannot find symbol Changed Bug title to 'opensearch: FTBFS with lucene9/9.10.0+dfsg'

Bug#1066450: opensearch: FTBFS with lucene9/9.10.0+dfsg

control: retitle -1 opensearch: FTBFS with lucene9/9.10.0+dfsg I have recently updated lucene9. Current FTBFS is caused by missing lucene9 classes. Thus it seems that lucene9 API has changed breaking backwards compatibility. Andrius

Processed: Re: Bug#1064708: pygame: FTBFS: AssertionError: "No video mode" does not match "Parameter 'surface' is invalid"

Processing control commands: > severity -1 serious Bug #1064708 [src:pygame] pygame: FTBFS: AssertionError: "No video mode" does not match "Parameter 'surface' is invalid" Severity set to 'serious' from 'important' -- 1064708: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1064708 Debian

Bug#1054486: marked as done (sogo: installs sogo.service twice once dh_installsystemd installs to /usr)

Your message dated Tue, 02 Apr 2024 10:20:52 +0200 with message-id and subject line Fixed in 5.9.1-1 has caused the Debian Bug report #1054486, regarding sogo: installs sogo.service twice once dh_installsystemd installs to /usr to be marked as done. This means that you claim that the problem

Bug#1059228: This is fixed in the next release 0.11.1

Hello, On Fri, 15 Mar 2024 13:53:18 +0100 =?UTF-8?Q?Sebastian_Sp=C3=A4th?= wrote: This is fixed in the next release 0.11.1. However, I fail to build a package (due to my unexperience I guess). When I try to build a package from https://salsa.debian.org/DebianOnMobile-team/s2geometry I get

Bug#1068226: libtrantor1, hardcoded dependency on libssl3

Package: libtrantor1 Version: 1.5.12+ds-1 Severity: grave User: debian-...@lists.debian.org Usertag: time-t libtrantor1 was recently binnmu'd for the time_t transition, however, despite the binnmu, it still depends on the old libssl3 because said dependency is hardcoded in the source package.

Bug#1067312: spirv-tools: FTBFS: operand.kinds-unified1.inc:566:97: error: ‘SPV_OPERAND_TYPE_NAMED_MAXIMUM_NUMBER_OF_REGISTERS’ was not declared in this scope

Hi, On Wed, 20 Mar 2024 21:58:27 +0100 Lucas Nussbaum wrote:> During a rebuild of all packages in sid, your package failed to build on amd64. I'm having the same problem. As a data point, builds succeeds as soon as I revert spirv-headers to 1.6.1+1.3.275.0-1. HTH, Gio.

Bug#1068224: deepin-movie, dependencies unsatisfiable on 32-bit non-i386 architectures.

Package: deepin-movie Version: 5.10.8-2 Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, deepin-movie still depends on libqt5concurrent5. As a result it is uninstallable on architectures that are undergoing the time64 transition

Bug#1066555: marked as done (kylin-nm: FTBFS: src/kylin-network-interface.c:197:5: error: implicit declaration of function ‘asprintf’; did you mean ‘vsprintf’? [-Werror=implicit-function-declaration])

Your message dated Tue, 02 Apr 2024 07:34:12 + with message-id and subject line Bug#1066555: fixed in kylin-nm 3.0.3.1-1 has caused the Debian Bug report #1066555, regarding kylin-nm: FTBFS: src/kylin-network-interface.c:197:5: error: implicit declaration of function ‘asprintf’; did you mean

Bug#1066630: Patch to address Debian Bug report #1066630

The following patch results in a clean build. I will work to get the patch uploaded. (I am not a Debian Developer) Index: libnet-ldapapi-perl/Makefile.PL === --- libnet-ldapapi-perl.orig/Makefile.PL 2024-03-29 07:00:25.037139644

Bug#1068223: cyrus-imapd - FTBFS on 32-bit non-i386 architectures

Package: cyrus-imapd Version: 3.8.2-1 Severity: serious User: debian-...@lists.debian.org Usertag: time-t cyrus-imapd is failing to build on the architectures affected by the time_t transition (armel, armhf, several debian-ports architectures) with the following error. unit: fatal(Internal

Bug#1068222: libappmenu-gtk3-parser0, dependencies unsatisfiable on 32-bit non-i386 architectures.

Package: libappmenu-gtk3-parser0 Version: 0.7.6-2.1 Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, libappmenu-gtk3-parser0 depends on both libgtk3-0 and libgtk3-0t64. As a result it is uninstallable on architectures that are

Bug#1068221: comet-ms, dependencies unsatisfiable on 32-bit non-i386 architectures.

Package: comet-ms Version: 2019015+cleaned1-4 Severity: grave User: debian-...@lists.debian.org Usertag: time-t After being rebuilt for the time64 transition, comet-ms depends on both libmstoolkit82 and libmstoolkit82t64. As a result it is uninstallable on architectures that are undergoing the

Bug#1067055: openmpi: error: implicit declaration of function 'OPAL_THREAD_ADD_FETCH64'

On 01/04/2024 23:25, Sebastian Ramacher wrote: There is a transition to openmpi-5 / mpi-defaults which is stalled by the t64 transition. It drops 32-bit support from OpenMPI. Because of this, I don't think the solution is to  port 32-bit atomics for armel/armhf, as it will be removed in a few

Bug#1063922: libnfft3-long4 has an undeclared file conflict

Package: libnfft3-long4 Version: 3.5.3-3 Followup-For: Bug #1063922 X-Debbugs-Cc: neel...@gmail.com There is a typo in the soname change patch. It should Breaks+Replaces libnfft3-long2 but in fact it does B+R libnfft3-single2. https://salsa.debian.org/science-