Bug#1064554: jruby fails to build from source in unstable

2024-02-23 Thread Vladimir Petko
Source: jruby Version: 9.4.5.0+ds-1 Severity: serious Dear Maintainer, When building jruby in unstable, the following error occurs: [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-install-

Bug#1064553: libgdiplus: build-error on current sid (all warnings being treated as errors)

2024-02-23 Thread Andreas Metzler
Source: libgdiplus Version: 6.1+dfsg-1 Severity: serious Tags: ftbfs Justification: fails to build from source (but built successfully in the past) libgdiplus FTBFS on current sid: make[7]: Entering directory '/dev/shm/x/libgdiplus-6.1+dfsg/gtest_build' [ 12%] Building CXX object

Processed: telepathy-farstream: diff for NMU version 0.6.2-1.2

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > tags 1060972 + patch Bug #1060972 [src:telepathy-farstream] telepathy-farstream: FTBFS: make[3]: *** [/usr/share/gobject-introspection-1.0/Makefile.introspection:156: TelepathyFarstream-0.6.gir] Error 1 Added tag(s) patch. > tags 1060972 + pending Bug #1060972

Bug#1060972: telepathy-farstream: diff for NMU version 0.6.2-1.2

2024-02-23 Thread pino
Control: tags 1060972 + patch Control: tags 1060972 + pending Dear maintainer, I've prepared an NMU for telepathy-farstream (versioned as 0.6.2-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. diff -Nru

Processed: severity of 1062097 is important, reopening 1062097, tagging 1062097

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1062097 important Bug #1062097 {Done: John Goerzen } [src:gensio] gensio: NMU diff for 64-bit time_t transition Severity set to 'important' from 'serious' > reopen 1062097 Bug #1062097 {Done: John Goerzen } [src:gensio] gensio: NMU

Bug#1064128: your mail

2024-02-23 Thread Kyle Robbertze
I'm working on upgrading with disabled gstreamer. Removing the optional dependency is not sufficient, which is how it used to work - it still fails at the same point. Either way, fixing this is not the only issue currently. ocaml-lastfm needs fixing first before liquidsoap can migrate to

Bug#1064128: your mail

2024-02-23 Thread Bo YU
Hi, On Fri, Feb 23, 2024 at 01:02:08PM -0300, Andreas Hasenack wrote: ...and 2.2.4 also fails to build: https://github.com/savonet/liquidsoap/issues/3752 Thanks. $ make : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE"

Bug#919035: marked as done (elpa-persp-projectile: broken with recent elpa-perspective)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2024 04:04:55 + with message-id and subject line Bug#919035: fixed in persp-projectile 1:1.0.0+git20210618.4e374d7-1 has caused the Debian Bug report #919035, regarding elpa-persp-projectile: broken with recent elpa-perspective to be marked as done. This means

Bug#1035903: marked as done (tracker: datetime build tests failing on 32-bit)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Sat, 24 Feb 2024 03:21:32 + with message-id and subject line Bug#1035903: fixed in tracker 3.7~beta-2 has caused the Debian Bug report #1035903, regarding tracker: datetime build tests failing on 32-bit to be marked as done. This means that you claim that the problem has

Processed: Bug#1035903 marked as pending in tracker

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1035903 [src:tracker] tracker: datetime build tests failing on 32-bit Added tag(s) pending. -- 1035903: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1035903 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1035903: marked as pending in tracker

2024-02-23 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1035903 in tracker 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#1064548: tracker-miners: bmp-basic-1 test fails on big-endian

2024-02-23 Thread Jeremy Bícha
Source: tracker-miners Version: 3.5.0~beta-1 Severity: serious Tags: ftbfs experimental help X-Debbugs-CC: debian-s...@lists.debian.org User: debian-s...@lists.debian.org Usertags: s390x Forwarded: https://gitlab.gnome.org/GNOME/tracker-miners/-/issues/309 tracker-miners added new tests in

Bug#1061966: closed by Debian FTP Masters (reply to Steve Langasek ) (Bug#1061966: fixed in audit 1:3.1.2-2.1~exp2)

2024-02-23 Thread Steve Langasek
Thanks to discussion on debian-devel, it's become clear that a rename of libaudit1 is not required, only of libauparse0. Please find attached a follow-on patch for yet another NMU to experimental, reverting the libaudit package name change. On Fri, Feb 02, 2024 at 09:56:51AM -0800, Steve

Bug#1058670: marked as done (python3-poetry: fail with Can't instantiate abstract class IsolatedEnv with abstract methods executable, scripts_dir)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 22:52:14 + with message-id and subject line Bug#1058670: fixed in poetry 1.8.0.dev0~git20240220.cff4d7d5+dfsg-1 has caused the Debian Bug report #1058670, regarding python3-poetry: fail with Can't instantiate abstract class IsolatedEnv with abstract

Bug#1058111: marked as done (cmdtest: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 22:50:54 + with message-id and subject line Bug#1058111: fixed in cmdtest 0.32.14.gcdfe14e-6 has caused the Debian Bug report #1058111, regarding cmdtest: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim

Bug#1055067: isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update

2024-02-23 Thread Santiago Ruano Rincón
El 30/10/23 a las 18:29, Sven-Haegar Koch escribió: > Package: isc-dhcp-client > Version: 4.4.3-P1-4 > Severity: normal > > Dear Maintainer, > > I am using network manager with /etc/NetworkManager/NetworkManager.conf > > [main] > dhcp=dhclient > > and thus using isc-dhcp-client as

Bug#1064369: gobject-introspection dropped versioned dependency on python3

2024-02-23 Thread Jeremy Bícha
Matthias, Since glib and gobject-introspection have migrated out of noble-proposed, is there still a need to keep this bug open? Thank you, Jeremy Bícha

Bug#1058340: marked as done (mkdocstrings-python-handlers: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 20:59:08 + with message-id and subject line Bug#1058340: fixed in mkdocstrings-python-handlers 1.8.0-1 has caused the Debian Bug report #1058340, regarding mkdocstrings-python-handlers: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i

Bug#1061395: marked as done (gnucash: Stop using webkit2gtk 4.0)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 15:33:51 -0500 with message-id and subject line Re: gnucash: Stop using webkit2gtk 4.0 has caused the Debian Bug report #1061395, regarding gnucash: Stop using webkit2gtk 4.0 to be marked as done. This means that you claim that the problem has been dealt

Processed: src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > close -1 4.0.0.0-1 Bug #1064533 [src:peony] src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere Marked as fixed in versions peony/4.0.0.0-1. Bug #1064533 [src:peony] src:peony: fails to migrate to testing for too long:

Bug#1064533: src:peony: fails to migrate to testing for too long: new Build-Depends not available everywhere

2024-02-23 Thread Paul Gevers
Source: peony Version: 3.2.4-2 Severity: serious Control: close -1 4.0.0.0-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30 days as

Processed: src:dt-schema: fails to migrate to testing for too long: autopkgtest failure

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > close -1 2023.11-3 Bug #1064532 [src:dt-schema] src:dt-schema: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions dt-schema/2023.11-3. Bug #1064532 [src:dt-schema] src:dt-schema: fails to migrate to testing for too long:

Bug#1064532: src:dt-schema: fails to migrate to testing for too long: autopkgtest failure

2024-02-23 Thread Paul Gevers
Source: dt-schema Version: 2022.08.2-5 Severity: serious Control: close -1 2023.11-3 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more than 30

Bug#1061765: Help needed to fix python-coverage-test-runner

2024-02-23 Thread Gunnar Wolf
Andreas Tille dijo [Fri, Feb 23, 2024 at 03:22:27PM +0100]: > HI Andrius, > > Am Fri, Feb 23, 2024 at 09:29:27AM +0200 schrieb Andrius Merkys: > > > ModuleNotFoundError: No module named 'imp' > > > > I had a similar problem. I worked it around by depending on > > python3-zombie-imp, the original

Bug#1064531: src:amberol: unsatisfied build dependency in testing: librust-lofty-0.17-dev

2024-02-23 Thread Paul Gevers
Source: amberol Version: 0.10.3-2 Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: edos-uninstallable Dear maintainer(s), Dose [1] is reporting a build issue with your package, it's missing a build dependency. Obviously your build dependencies shouldn't be removed

Processed: found 1064514 in 2024.1.27+dfsg1-5

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1064514 2024.1.27+dfsg1-5 Bug #1064514 [src:pymatgen] pymatgen: CVE-2024-23346 Marked as found in versions pymatgen/2024.1.27+dfsg1-5. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064514:

Processed: found 1064516 in 2.2.7-1

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1064516 2.2.7-1 Bug #1064516 [src:ruby-rack] ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146 Marked as found in versions ruby-rack/2.2.7-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 1064516:

Processed: Bug#1058111 marked as pending in cmdtest

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1058111 [src:cmdtest] cmdtest: FTBFS: ModuleNotFoundError: No module named 'imp' Added tag(s) pending. -- 1058111: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1058111 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1058111: marked as pending in cmdtest

2024-02-23 Thread Antonio Terceiro
Control: tag -1 pending Hello, Bug #1058111 in cmdtest 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#1058372: marked as done (mkdocstrings-python-legacy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 19:43:38 +0100 with message-id and subject line Re: Bug#1058372: mkdocstrings-python-legacy: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 13 has caused the Debian Bug report #1058372, regarding

Processed: Re: Bug#1056232: celery's autopkg tests fail with Python 3.12

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-kombu Bug #1056232 [src:celery] celery's autopkg tests fail with Python 3.12 Bug reassigned from package 'src:celery' to 'python3-kombu'. No longer marked as found in versions celery/5.3.4-1. Ignoring request to alter fixed versions of bug

Processed: tagging 1064514, tagging 1064515, tagging 1064516, tagging 1064517

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1064514 + upstream Bug #1064514 [src:pymatgen] pymatgen: CVE-2024-23346 Added tag(s) upstream. > tags 1064515 + upstream Bug #1064515 [src:fastdds] fastdds: CVE-2023-50257 Added tag(s) upstream. > tags 1064516 + upstream Bug #1064516

Bug#1056232: celery's autopkg tests fail with Python 3.12

2024-02-23 Thread Colin Watson
Control: reassign -1 python3-kombu Control: forwarded -1 https://github.com/celery/kombu/issues/1804 Control: affects -1 src:celery Control: fixed -1 kombu/5.3.4-1 Control: close -1 On Sun, Nov 19, 2023 at 12:08:09PM +0100, Matthias Klose wrote: > celery's autopkg tests fail with Python 3.12. All

Processed: tagging 1064377, tagging 1014566 ..., found 1064086 in 4.1.8-2, tagging 1049808, tagging 1043996 ...

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1064377 + sid trixie Bug #1064377 [tcl-expect] tcl-expect: identified for time_t transition but no ABI in shlibs Added tag(s) sid and trixie. > tags 1014566 - sid bookworm Bug #1014566 [src:massivethreads] massivethreads: FTBFS with glibc

Bug#1028212: marked as done (prometheus-node-exporter-collectors: APT update deadlock - prevents unattended security upgrades)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 17:32:31 + with message-id and subject line Bug#1028212: fixed in prometheus-node-exporter-collectors 0.0~git20230203.6f710f8-1+deb12u1 has caused the Debian Bug report #1028212, regarding prometheus-node-exporter-collectors: APT update deadlock - prevents

Processed: Re: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > found -1 6.30.223.271-24~exp1 Bug #1057447 [broadcom-sta-dkms] broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers' Marked as found in versions broadcom-sta/6.30.223.271-24~exp1.

Bug#1057447: broadcom-sta-dkms: module build fails for Linux 6.6: wl_linux.c:486:12: error: 'struct net_device' has no member named 'wireless_handlers'

2024-02-23 Thread Andreas Beckmann
Followup-For: Bug #1057447 Control: found -1 6.30.223.271-24~exp1 Control: tag -1 + patch This issue is caused by a) version parsing that expects three numeric components (6.6.1-foo) and fails if there are only two (6.7-rc1) b) broken version comparison logic which turn on APICHOICE=FORCE_WEXT

Bug#1063918: marked as done (geary FTBFS with the nocheck build profile: ../meson.build:226:6: ERROR: Program 'update-desktop-database' not found or not executable)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 17:05:42 + with message-id and subject line Bug#1063918: fixed in geary 44.1-2 has caused the Debian Bug report #1063918, regarding geary FTBFS with the nocheck build profile: ../meson.build:226:6: ERROR: Program 'update-desktop-database' not found or not

Processed: Bug#1063918 marked as pending in geary

2024-02-23 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1063918 [src:geary] geary FTBFS with the nocheck build profile: ../meson.build:226:6: ERROR: Program 'update-desktop-database' not found or not executable Added tag(s) pending. -- 1063918:

Bug#1063918: marked as pending in geary

2024-02-23 Thread Jeremy Bicha
Control: tag -1 pending Hello, Bug #1063918 in geary 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#1044064: marked as done (pyranges: FTBFS with pandas 2.0)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 16:42:16 + with message-id and subject line Bug#1044064: fixed in pyranges 0.0.111+ds-7 has caused the Debian Bug report #1044064, regarding pyranges: FTBFS with pandas 2.0 to be marked as done. This means that you claim that the problem has been dealt

Bug#1061765: marked as done (vmdb2 ftbfs with Python 3.12 as default)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 16:20:47 + with message-id and subject line Bug#1061765: fixed in vmdb2 0.28-2 has caused the Debian Bug report #1061765, regarding vmdb2 ftbfs with Python 3.12 as default to be marked as done. This means that you claim that the problem has been dealt

Bug#1064128:

2024-02-23 Thread Andreas Hasenack
...and 2.2.4 also fails to build: https://github.com/savonet/liquidsoap/issues/3752 $ make : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning: "_FORTIFY_SOURCE" redefined : note: this is the location of the previous definition : warning:

Bug#1052869: marked as done (python-klein: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 15:49:37 + with message-id and subject line Bug#1052869: fixed in python-klein 23.12.0-1 has caused the Debian Bug report #1052869, regarding python-klein: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit

Bug#1064516: ruby-rack: CVE-2024-26141 CVE-2024-25126 CVE-2024-26146

2024-02-23 Thread Moritz Mühlenhoff
Source: ruby-rack X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerabilities were published for ruby-rack. CVE-2024-26141[0]: Reject Range headers which are too large https://github.com/rack/rack/releases/tag/v2.2.8.1

Bug#1064514: pymatgen: CVE-2024-23346

2024-02-23 Thread Moritz Mühlenhoff
Source: pymatgen X-Debbugs-CC: t...@security.debian.org Severity: grave Tags: security Hi, The following vulnerability was published for pymatgen. CVE-2024-23346[0]: | Pymatgen (Python Materials Genomics) is an open-source Python | library for materials analysis. A critical security

Bug#999931: marked as done (virtuoso-opensource: depends on obsolete pcre3 library)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 14:47:25 + with message-id and subject line Bug#31: fixed in virtuoso-opensource 7.2.5.1+dfsg1-0.6 has caused the Debian Bug report #31, regarding virtuoso-opensource: depends on obsolete pcre3 library to be marked as done. This means that you

Bug#1058112: marked as done (python-coverage-test-runner: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 14:44:30 + with message-id and subject line Bug#1058112: fixed in python-coverage-test-runner 1.13.1-5 has caused the Debian Bug report #1058112, regarding python-coverage-test-runner: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done.

Bug#1064128:

2024-02-23 Thread Andreas Hasenack
Upstream fixed[1] this in 2.2.4. There are big commits that could be used as patches, but it's probably best to just update to 2.2.4. 1. https://github.com/savonet/liquidsoap/issues/3750

Bug#1061765: Help needed to fix python-coverage-test-runner

2024-02-23 Thread Andreas Tille
HI Andrius, Am Fri, Feb 23, 2024 at 09:29:27AM +0200 schrieb Andrius Merkys: > > ModuleNotFoundError: No module named 'imp' > > I had a similar problem. I worked it around by depending on > python3-zombie-imp, the original code did not require any modifications. Nice hint - implemented. Thanks

Processed: notfound 1064492 in 0.9.27

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > notfound 1064492 0.9.27 Bug #1064492 [libdemeter-perl] libdemeter-perl: Use of wxTB_3DBUTTONS crashes the Artemis GUI There is no source info for the package 'libdemeter-perl' at version '0.9.27' with architecture '' Unable to make a source

Processed: found 1064492 in 0.9.27+ds6-1

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1064492 0.9.27+ds6-1 Bug #1064492 [libdemeter-perl] libdemeter-perl: Use of wxTB_3DBUTTONS crashes the Artemis GUI Marked as found in versions libdemeter-perl/0.9.27+ds6-1. > thanks Stopping processing here. Please contact me if you need

Bug#1061764: marked as done (unattended-upgrades ftbfs with Python 3.12 as default)

2024-02-23 Thread Debian Bug Tracking System
Your message dated Fri, 23 Feb 2024 10:26:46 +0100 with message-id <5d9d2952-1dc1-481b-9161-a7d4c0657...@app.fastmail.com> and subject line Re: Bug#1061764: unattended-upgrades ftbfs with Python 3.12 as default has caused the Debian Bug report #1061764, regarding unattended-upgrades ftbfs with

Processed: found 1055067 in 4.4.3-P1-2

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1055067 4.4.3-P1-2 Bug #1055067 [isc-dhcp-client] isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update Marked as found in versions isc-dhcp/4.4.3-P1-2. > thanks Stopping processing here. Please

Processed: found 1055067 in 4.4.3-P1-5

2024-02-23 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1055067 4.4.3-P1-5 Bug #1055067 [isc-dhcp-client] isc-dhcp-client: network-manager 1.44.2-3 changed path to nm-dhcp-helper, apparmor need update Marked as found in versions isc-dhcp/4.4.3-P1-5. > thanks Stopping processing here. Please

Bug#1053111: please upload DEP17-related patches

2024-02-23 Thread Helmut Grohne
user helm...@debian.org severity 1059981 important tags 1059981 + trixie sid severity 1061274 important tags 1061274 + trixie sid severity 1060269 important tags 1060269 + trixie sid patch severity 1060270 important tags 1060270 + trixie sid patch severity 106 important usertags 106 +

Bug#1064495: sitecopy FTBFS: incompatible neon version

2024-02-23 Thread Helmut Grohne
Source: sitecopy Version: 1:0.16.6-11 Severity: serious Tags: ftbfs sitecopy fails to build from source in unstable. I think the relevant part of the build log is: | checking for neon-config... /usr/bin/neon-config | checking linking against neon... yes | configure: incompatible neon library