Bug#1079604: epics-base:FTBFS:build failure (not support riscv64)

2024-08-24 Thread Yue Gui
Source: epics-base Version: 7.0.8.1+dfsg1-2 Severity: serious Tags: FTBFS, patch User: debian-ri...@lists.debian.org Usertags: riscv64 X-Debbugs-Cc: debian-ri...@lists.debian.org Dear epics-base Maintainer, The package epics-base build failed on arch riscv64.The crucial buildd log below: ``` dh_a

Bug#1073764: marked as done (openfpgaloader: move aliased files from / to /usr (DEP17))

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sun, 25 Aug 2024 06:19:11 + with message-id and subject line Bug#1073764: fixed in openfpgaloader 0.12.1-1 has caused the Debian Bug report #1073764, regarding openfpgaloader: move aliased files from / to /usr (DEP17) to be marked as done. This means that you claim that the

Bug#1075589: marked as done (tuxguitar: ftbfs with GCC-14)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sun, 25 Aug 2024 01:04:34 + with message-id and subject line Bug#1075589: fixed in tuxguitar 1.6.4+dfsg1-1 has caused the Debian Bug report #1075589, regarding tuxguitar: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1075589: marked as pending in tuxguitar

2024-08-24 Thread gregor herrmann
Control: tag -1 pending Hello, Bug #1075589 in tuxguitar 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/java-team/tuxguitar/-/commit/ead951af438d55ae7db42c5e28

Processed: Bug#1075589 marked as pending in tuxguitar

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1075589 [src:tuxguitar] tuxguitar: ftbfs with GCC-14 Added tag(s) pending. -- 1075589: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1075589 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Processed: tags

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1075018 + trixie sid Bug #1075018 {Done: IOhannes m zmölnig (Debian/GNU) } [src:gmerlin-encoders] gmerlin-encoders: ftbfs with GCC-14 Added tag(s) sid and trixie. > tags 1079483 + trixie sid Bug #1079483 [src:spacebar] spacebar: FTBFS Added

Bug#1069218: marked as done (rocketcea ftbfs with Python 3.12)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:24:05 + with message-id and subject line Bug#1069218: fixed in rocketcea 1.2.1-1 has caused the Debian Bug report #1069218, regarding rocketcea ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#957639: marked as done (openmx: ftbfs with GCC-10)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:21:47 + with message-id and subject line Bug#1079306: Removed package(s) from unstable has caused the Debian Bug report #957639, regarding openmx: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#952059: marked as done (mxt-app: FTBFS: src/test/run_unit_tests.h:32: error: "assert_float_equal" redefined [-Werror])

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:21:16 + with message-id and subject line Bug#1079304: Removed package(s) from unstable has caused the Debian Bug report #952059, regarding mxt-app: FTBFS: src/test/run_unit_tests.h:32: error: "assert_float_equal" redefined [-Werror] to be marked as done.

Bug#780480: marked as done (navi2ch: Please change default server)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:20:48 + with message-id and subject line Bug#1079303: Removed package(s) from unstable has caused the Debian Bug report #780480, regarding navi2ch: Please change default server to be marked as done. This means that you claim that the problem has been dea

Bug#952259: marked as done (navi2ch: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3387.)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:20:48 + with message-id and subject line Bug#1079303: Removed package(s) from unstable has caused the Debian Bug report #952259, regarding navi2ch: FTBFS: Malformed UTF-8 character (fatal) at /usr/share/texinfo/Texinfo/ParserNonXS.pm line 3387. to be mar

Bug#1026439: marked as done (xtide: FTBFS (invalid conversion from ‘char**’ to ‘const char**’))

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:19:09 + with message-id and subject line Bug#1079297: Removed package(s) from unstable has caused the Debian Bug report #1026439, regarding xtide: FTBFS (invalid conversion from ‘char**’ to ‘const char**’) to be marked as done. This means that you claim

Bug#966877: marked as done (termtris: FTBFS: ld: src/game.o:/<>/src/game.h:21: multiple definition of `quit'; src/ansi.o:/<>/src/game.h:21: first defined here)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:17:17 + with message-id and subject line Bug#1079294: Removed package(s) from unstable has caused the Debian Bug report #966877, regarding termtris: FTBFS: ld: src/game.o:/<>/src/game.h:21: multiple definition of `quit'; src/ansi.o:/<>/src/game.h:21: fir

Bug#1079588: mandos-client postrm purge can mysteriously fail

2024-08-24 Thread Ben Hutchings
Package: mandos-client Version: 1.8.16-1 Severity: serious mandos-client's postrm script can fail on purge with no obvious error message. dpkg reports that it exited with error code 128 but it's not clear why. I can reproduce this in a bookworm/amd64 or unstable/amd64 build chroot by running:

Bug#997617: marked as done (twofish: FTBFS: ar: libdeps specified more than once)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:15:58 + with message-id and subject line Bug#1079290: Removed package(s) from unstable has caused the Debian Bug report #997617, regarding twofish: FTBFS: ar: libdeps specified more than once to be marked as done. This means that you claim that the probl

Bug#999956: marked as done (snort: depends on obsolete pcre3 library)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:14:31 + with message-id and subject line Bug#1079286: Removed package(s) from unstable has caused the Debian Bug report #56, regarding snort: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been

Bug#965548: marked as done (gems: Removal of obsolete debhelper compat 5 and 6 in bookworm)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:14:59 + with message-id and subject line Bug#1079287: Removed package(s) from unstable has caused the Debian Bug report #965548, regarding gems: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that

Bug#1068036: marked as done (FTBFS: no B-D: libtirpc-dev)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:14:31 + with message-id and subject line Bug#1079286: Removed package(s) from unstable has caused the Debian Bug report #1068036, regarding FTBFS: no B-D: libtirpc-dev to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1067951: marked as done (snort: non-free Sun RPC code)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:14:31 + with message-id and subject line Bug#1079286: Removed package(s) from unstable has caused the Debian Bug report #1067951, regarding snort: non-free Sun RPC code to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1064328: marked as done (snort: identified for time_t transition but no ABI in shlibs)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:14:31 + with message-id and subject line Bug#1079286: Removed package(s) from unstable has caused the Debian Bug report #1064328, regarding snort: identified for time_t transition but no ABI in shlibs to be marked as done. This means that you claim that

Bug#1021276: marked as done (snort: CVE-2020-3315 CVE-2021-1223 CVE-2021-1224 CVE-2021-1494 CVE-2021-1495 CVE-2021-34749 CVE-2021-40114)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:14:31 + with message-id and subject line Bug#1079286: Removed package(s) from unstable has caused the Debian Bug report #1021276, regarding snort: CVE-2020-3315 CVE-2021-1223 CVE-2021-1224 CVE-2021-1494 CVE-2021-1495 CVE-2021-34749 CVE-2021-40114 to be m

Bug#1019230: marked as done (Current version is EOLed)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:14:31 + with message-id and subject line Bug#1079286: Removed package(s) from unstable has caused the Debian Bug report #1019230, regarding Current version is EOLed to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#975926: marked as done (enigmail should not be shipped in bookworm)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:13:42 + with message-id and subject line Bug#1079285: Removed package(s) from unstable has caused the Debian Bug report #975926, regarding enigmail should not be shipped in bookworm to be marked as done. This means that you claim that the problem has bee

Bug#1014623: marked as done (xjig: build-depends on obsolete libnetpbm10-dev, ftbfs with libnetpbm11-dev)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:15:28 + with message-id and subject line Bug#1079289: Removed package(s) from unstable has caused the Debian Bug report #1014623, regarding xjig: build-depends on obsolete libnetpbm10-dev, ftbfs with libnetpbm11-dev to be marked as done. This means that

Bug#1016403: marked as done (switch build depends on libnetpbm10-dev to libnetpbm-dev)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:15:28 + with message-id and subject line Bug#1079289: Removed package(s) from unstable has caused the Debian Bug report #1016403, regarding switch build depends on libnetpbm10-dev to libnetpbm-dev to be marked as done. This means that you claim that the

Bug#1030405: marked as done (enigmail: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:13:42 + with message-id and subject line Bug#1079285: Removed package(s) from unstable has caused the Debian Bug report #1030186, regarding enigmail: FTBFS: dh_auto_test: error: make -j8 test "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2

Bug#1030186: marked as done (enigmail: FTBFS (Error: Cannot find module 'chalk'))

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:13:42 + with message-id and subject line Bug#1079285: Removed package(s) from unstable has caused the Debian Bug report #1030186, regarding enigmail: FTBFS (Error: Cannot find module 'chalk') to be marked as done. This means that you claim that the probl

Bug#896580: marked as done (mixer.app: Fails to work with ALSA)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:08:14 + with message-id and subject line Bug#1079108: Removed package(s) from unstable has caused the Debian Bug report #896580, regarding mixer.app: Fails to work with ALSA to be marked as done. This means that you claim that the problem has been dealt

Bug#1077909: marked as done (meep-openmpi: Does this package still make sense?)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:06:34 + with message-id and subject line Bug#1079000: Removed package(s) from unstable has caused the Debian Bug report #1077909, regarding meep-openmpi: Does this package still make sense? to be marked as done. This means that you claim that the problem

Bug#1075268: marked as done (mgt: ftbfs with GCC-14)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 22:07:04 + with message-id and subject line Bug#1079001: Removed package(s) from unstable has caused the Debian Bug report #1075268, regarding mgt: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1078528: marked as done (python-thriftpy: RM? upstream archived)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 21:48:29 + with message-id and subject line Bug#1078577: Removed package(s) from unstable has caused the Debian Bug report #1078528, regarding python-thriftpy: RM? upstream archived to be marked as done. This means that you claim that the problem has been d

Bug#1079582: marked as done (nvidia-driver: Cannot install nvidia-driver in sid: unsatisfied dependencies)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 23:41:14 +0200 with message-id <91ba2a98-3912-55b0-f19f-30e994aa6...@debian.org> and subject line Re: Bug#1079582: nvidia-driver: Cannot install nvidia-driver in sid: unsatisfied dependencies has caused the Debian Bug report #1079582, regarding nvidia-driver: Ca

Bug#1073907: marked as done (FTBFS with OCaml 5.2.0 (Uses String.lowercase))

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 21:37:31 + with message-id and subject line Bug#1078266: Removed package(s) from unstable has caused the Debian Bug report #1073907, regarding FTBFS with OCaml 5.2.0 (Uses String.lowercase) to be marked as done. This means that you claim that the problem ha

Bug#1079583: jpy FTBFS on Zero-Assembler architectures with OpenJDK 21

2024-08-24 Thread Adrian Bunk
Source: jpy Version: 0.17.0-1 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/jpy-consortium/jpy/pull/162 https://buildd.debian.org/status/logs.php?pkg=jpy&ver=0.18.0-1 ... dh clean --with python3 --buildsystem=pybuild dh_auto_clean -O--buildsystem=pybuild pybuild --c

Bug#1079582: nvidia-driver: Cannot install nvidia-driver in sid: unsatisfied dependencies

2024-08-24 Thread Forrest Cahoon
Package: nvidia-driver Severity: grave Justification: renders package unusable X-Debbugs-Cc: forrest.cah...@gmail.com Dear Maintainer, Attempting to install the nvidia-driver package on my Debian sid system gives these dependency errors: Some packages could not be installed. This may mean that y

Processed: severity of 968604 is serious

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 968604 serious Bug #968604 [acpi-override-initramfs] acpi-override-initramfs makes update-initramfs fail when /var/lib/acpi-override/ is empty Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me

Processed: found 1063700 in 0.15-4+b1

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 1063700 0.15-4+b1 Bug #1063700 {Done: Alberto Bertogli } [kxc] kxc fails to install because /etc/kxc is missing Marked as found in versions kxd/0.15-4. > thanks Stopping processing here. Please contact me if you need assistance. -- 106370

Bug#1073052: fixed in cryptsetup 2:2.7.4-1

2024-08-24 Thread Guilhem Moulin
On Sat, 24 Aug 2024 at 21:25:03 +0200, Paul Gevers wrote: > On 24-08-2024 20:53, Guilhem Moulin wrote: >> Awesome, thanks! Right now these tests have “Architecture: amd64 i386”, >> is the runner able to run i386 too or should I remove it from the list? > > Tests with isolation-machine will only ru

Bug#1079578: Secure Shell is disabled after being enabled

2024-08-24 Thread Phil Wyett
On Sat, 2024-08-24 at 21:05 +0100, Phil Wyett wrote: > Source: gnome-control-center > Source-Version: 1:46.4-1 > Severity: grave > Usertags: trixie > > Dear Maintainers, > > Secure Shell is disabled after being enabled. > > 1. Login to GNOME on trixie. > 2. Launch 'Settings'. > 3. Go to 'System'

Bug#1079578: Secure Shell is disabled after being enabled

2024-08-24 Thread Phil Wyett
Source: gnome-control-center Source-Version: 1:46.4-1 Severity: grave Usertags: trixie Dear Maintainers, Secure Shell is disabled after being enabled. 1. Login to GNOME on trixie. 2. Launch 'Settings'. 3. Go to 'System'. 4. Select 'Secure Shell'. 5. Enable Secure Shell and provide super user pas

Processed: retitle 1078313 to qtermwidget: Missing build dependency on qttools5-dev

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1078313 qtermwidget: Missing build dependency on qttools5-dev Bug #1078313 [src:qtermwidget] qtermwidget: FTBFS: Could not find a package configuration file provided by "Qt5LinguistTools" Changed Bug title to 'qtermwidget: Missing build d

Bug#1073052: fixed in cryptsetup 2:2.7.4-1

2024-08-24 Thread Paul Gevers
Hi, On 24-08-2024 20:53, Guilhem Moulin wrote: Awesome, thanks! Right now these tests have “Architecture: amd64 i386”, is the runner able to run i386 too or should I remove it from the list? Tests with isolation-machine will only run on amd64, no need to special case them further. If there a

Bug#1054814: (no subject)

2024-08-24 Thread Aleksandr Mikhalitsyn
On Sat, Aug 24, 2024 at 8:48 PM Salvatore Bonaccorso wrote: > > Hi, Hi Salvatore, > > On Sat, Aug 24, 2024 at 08:28:20PM +0200, Alexander Mikhalitsyn wrote: > > Dear friends, > > > > I'm trying to fix CRIU package in Ubuntu Noble: > > https://bugs.launchpad.net/ubuntu/+source/criu/+bug/2066148 >

Bug#1079572: libfabric ftbfs on i386

2024-08-24 Thread Matthias Klose
Package: src:libfabric Version: 1.17.0-3 Severity: serious Tags: sid trixie libfabric ftbfs at least on i386, there might be more follow-up errors: [...] /bin/bash ./libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I./include -D_GNU_SOURCE -D__USE_XOPEN2K8 -DSYSCONFDIR=\"/etc\" -DRD

Bug#1078244: at-spi2-core: Packaging issue

2024-08-24 Thread Samuel Thibault
Jean-Philippe MENGUAL, le ven. 23 août 2024 08:44:41 +0200, a ecrit: > The fact is that when upstream suggests to downgrade at-spi2, it is > difficult to know what should be downgraded. Basically we downgrade > at-spi2-core, and it should be enough (i.e. it should downgrade or make user > downgrade

Bug#1073052: fixed in cryptsetup 2:2.7.4-1

2024-08-24 Thread Guilhem Moulin
On Sat, 24 Aug 2024 at 19:16:01 +0200, Paul Gevers wrote: > On 24-08-2024 19:10, Guilhem Moulin wrote: >> Great news that would be much appreciated, thanks! > > Done. > > I triggered a migration-reference/0 run in testing. Awesome, thanks! Right now these tests have “Architecture: amd64 i386”, is

Bug#1054814: (no subject)

2024-08-24 Thread Salvatore Bonaccorso
Hi, On Sat, Aug 24, 2024 at 08:28:20PM +0200, Alexander Mikhalitsyn wrote: > Dear friends, > > I'm trying to fix CRIU package in Ubuntu Noble: > https://bugs.launchpad.net/ubuntu/+source/criu/+bug/2066148 > > We had a discussion with my colleague Simon Déziel about my > debdiff [1] for CRIU pack

Bug#966926: marked as done (dltlyse: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 18:34:07 + with message-id and subject line Bug#966926: fixed in dltlyse 1.4.3-0.1 has caused the Debian Bug report #966926, regarding dltlyse: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.8 returned exit code 13 to be marked as done.

Bug#1054814: (no subject)

2024-08-24 Thread Alexander Mikhalitsyn
Dear friends, I'm trying to fix CRIU package in Ubuntu Noble: https://bugs.launchpad.net/ubuntu/+source/criu/+bug/2066148 We had a discussion with my colleague Simon Déziel about my debdiff [1] for CRIU package in Ubuntu and he pointed me out that there is a bug on Debian bugtracker about these b

Bug#1073304: firmware-microbit-micropython: FTBFS: cc1plus: error: '-fcf-protection=full' is not supported for this target

2024-08-24 Thread Santiago Vila
El 24/8/24 a las 19:29, Petter Reinholdtsen escribió: I also tried with export DEB_BUILD_MAINT_OPTIONS = hardening=-all Hi. As an experiment, I tried that and managed to remove all "proper-compiling" errors. The error which happens at the end is actually a linking error. I suspect the b

Bug#1073304: firmware-microbit-micropython: FTBFS: cc1plus: error: '-fcf-protection=full' is not supported for this target

2024-08-24 Thread Petter Reinholdtsen
I was recommended that updating debian/rules with hardening=-branch could help, ie like this: export DEB_BUILD_MAINT_OPTIONS = hardening=-branch But it only triggered other build problems. I also tried with export DEB_BUILD_MAINT_OPTIONS = hardening=-all I suspect the best solution is to n

Bug#1073052: fixed in cryptsetup 2:2.7.4-1

2024-08-24 Thread Paul Gevers
Hi, On 24-08-2024 19:10, Guilhem Moulin wrote: Great news that would be much appreciated, thanks! Done. I triggered a migration-reference/0 run in testing. Paul OpenPGP_signature.asc Description: OpenPGP digital signature

Bug#1073052: fixed in cryptsetup 2:2.7.4-1

2024-08-24 Thread Guilhem Moulin
Hi Paul, On Sat, 24 Aug 2024 at 17:50:22 +0200, Paul Gevers wrote: > On Sun, 04 Aug 2024 22:19:30 + Debian FTP Masters > wrote: >> * DEP-8: Mark cryptroot-* as flaky. To be re-evaluated if/when the >> tests only run on environment where KVM is available. (Closes: #1073052) > > On amd64 we

Bug#1073304: firmware-microbit-micropython: FTBFS: cc1plus: error: '-fcf-protection=full' is not supported for this target

2024-08-24 Thread Petter Reinholdtsen
[Lucas Nussbaum] > During a rebuild of all packages in sid, your package failed to > build on amd64. The problematic flag seem to originate from dpkg-buildflags: % for f in $(dpkg-buildflags --list); do echo $f=$(dpkg-buildflags --get $f); done ASFLAGS= ASFLAGS_FOR_BUILD= CFLAGS=-g -O2 -Werror=i

Bug#1075035: marked as done (gperiodic: ftbfs with GCC-14)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 16:49:25 + with message-id and subject line Bug#1075035: fixed in gperiodic 3.0.3-2 has caused the Debian Bug report #1075035, regarding gperiodic: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1079518: marked as done (libprotobuf-dev/experimental: Missing dependency on libabsl-dev)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 16:49:57 + with message-id and subject line Bug#1079518: fixed in protobuf 3.25.4-1 has caused the Debian Bug report #1079518, regarding libprotobuf-dev/experimental: Missing dependency on libabsl-dev to be marked as done. This means that you claim that the

Bug#1079557: marked as done (rust-rustls - autopkgtest failure - test dependency issue.)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 16:21:54 + with message-id and subject line Bug#1079557: fixed in rust-rustls 0.21.12-5 has caused the Debian Bug report #1079557, regarding rust-rustls - autopkgtest failure - test dependency issue. to be marked as done. This means that you claim that the

Bug#1074695: marked as done (mnemosyne: FTBFS: ModuleNotFoundError: No module named 'imp')

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 16:21:03 + with message-id and subject line Bug#1074695: fixed in mnemosyne 2.9+ds1-2 has caused the Debian Bug report #1074695, regarding mnemosyne: FTBFS: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that you claim that the

Bug#1078137: marked as done (blimps: FTBFS with GCC 14: error: implicit declaration of function 'gets')

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 16:19:21 + with message-id and subject line Bug#1078137: fixed in blimps 3.9+ds-3 has caused the Debian Bug report #1078137, regarding blimps: FTBFS with GCC 14: error: implicit declaration of function 'gets' to be marked as done. This means that you claim

Processed: retitle 1053138 to RM: unittest2 -- ROM; obsolete copy of unittest from Standard Lib.

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > retitle 1053138 RM: unittest2 -- ROM; obsolete copy of unittest from Standard > Lib. Bug #1053138 [ftp.debian.org] unittest2: RM unittest2 Changed Bug title to 'RM: unittest2 -- ROM; obsolete copy of unittest from Standard Lib.' from 'unittest2:

Processed: severity of 1053138 is normal

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > severity 1053138 normal Bug #1053138 [ftp.debian.org] RM: unittest2 -- ROM; obsolete copy of unittest from Standard Lib. Severity set to 'normal' from 'serious' > thanks Stopping processing here. Please contact me if you need assistance. -- 105

Processed: block 1053138 with 1078186

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > block 1053138 with 1078186 Bug #1053138 [ftp.debian.org] unittest2: RM unittest2 1053138 was blocked by: 1058959 1058968 1058969 1058970 1058975 1058976 1058977 1058980 1058984 1059888 1060629 1060632 1060634 1060637 1060641 1066063 1066129 1066

Processed: reassign 1053138 to ftp.debian.org

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1053138 ftp.debian.org Bug #1053138 [src:unittest2] unittest2: RM unittest2 Bug reassigned from package 'src:unittest2' to 'ftp.debian.org'. No longer marked as found in versions unittest2/1.1.0-9. Ignoring request to alter fixed versions

Processed: tagging 1053138

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 1053138 + moreinfo Bug #1053138 [src:unittest2] unittest2: RM unittest2 Added tag(s) moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 1053138: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=105313

Processed: Bug#1078137 marked as pending in blimps

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > tag -1 pending Bug #1078137 [src:blimps] blimps: FTBFS with GCC 14: error: implicit declaration of function 'gets' Added tag(s) pending. -- 1078137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078137 Debian Bug Tracking System Contact ow...@bugs.debian.org

Bug#1078137: marked as pending in blimps

2024-08-24 Thread Étienne Mollier
Control: tag -1 pending Hello, Bug #1078137 in blimps 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/med-team/blimps/-/commit/b42a21d6ff3427601845fee6263819eee

Bug#997602: marked as done (iptables-converter: FTBFS: error in iptables-converter setup command: use_2to3 is invalid.)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 15:50:19 + with message-id and subject line Bug#997602: fixed in iptables-converter 0.9.11-0.1 has caused the Debian Bug report #997602, regarding iptables-converter: FTBFS: error in iptables-converter setup command: use_2to3 is invalid. to be marked as don

Bug#1078068: marked as done (accerciser: Broken with Python 3.12: ModuleNotFoundError: No module named 'imp')

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 15:49:04 + with message-id and subject line Bug#1078068: fixed in accerciser 3.44.1-1 has caused the Debian Bug report #1078068, regarding accerciser: Broken with Python 3.12: ModuleNotFoundError: No module named 'imp' to be marked as done. This means that

Bug#1073052: fixed in cryptsetup 2:2.7.4-1

2024-08-24 Thread Paul Gevers
Hi Guilhem, On Sun, 04 Aug 2024 22:19:30 + Debian FTP Masters wrote: * DEP-8: Mark cryptroot-* as flaky. To be re-evaluated if/when the tests only run on environment where KVM is available. (Closes: #1073052) On amd64 we have KVM available, but currently that needs actions from

Processed: forcibly merging 1073470 1079549

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > forcemerge 1073470 1079549 Bug #1073470 [src:symfony] symfony: FTBFS: PHP Warning: rmdir(/myfakevendor): No such file or directory in /<>/build/Symfony/Bridge/PhpUnit/Tests/DeprecationErrorHandler/DeprecationTest.php on line 269 Bug #1073470 [

Bug#1079562: libnop FTBFS on mips64el/alpha

2024-08-24 Thread Adrian Bunk
Source: libnop Version: 0.0~git20200728.45dfe0f-4 Severity: serious Tags: ftbfs patch Forwarded: https://github.com/google/libnop/issues/32 https://buildd.debian.org/status/fetch.php?pkg=libnop&arch=mips64el&ver=0.0~git20200728.45dfe0f-4%2Bb1&stamp=1723833797&raw=0 https://buildd.debian.org/status

Bug#1075583: marked as done (transcriber: ftbfs with GCC-14)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 15:20:42 + with message-id and subject line Bug#1075583: fixed in transcriber 1.5.1.1-11 has caused the Debian Bug report #1075583, regarding transcriber: ftbfs with GCC-14 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1076913: marked as done (python-untokenize: FTBFS: ModuleNotFoundError: No module named 'lib2to3')

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 15:09:10 + with message-id and subject line Bug#1076913: fixed in python-untokenize 0.1.1-4 has caused the Debian Bug report #1076913, regarding python-untokenize: FTBFS: ModuleNotFoundError: No module named 'lib2to3' to be marked as done. This means that

Bug#1079560: ansible: autopkgtest regression: AttributeError: 'called_once_with' is not a valid assertion.

2024-08-24 Thread Paul Gevers
Source: ansible Version: 10.1.0+dfsg-1 Severity: serious User: debian...@lists.debian.org Usertags: regression Dear maintainer(s), Your package has an autopkgtest, great. However, it fails. Can you please investigate the situation and fix it? I copied some of the output at the bottom of this r

Bug#1074375: marked as done (astra-toolbox: autopkgtest failure: ModuleNotFoundError: No module named 'six')

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 15:04:57 + with message-id and subject line Bug#1074375: fixed in astra-toolbox 2.1.0-5 has caused the Debian Bug report #1074375, regarding astra-toolbox: autopkgtest failure: ModuleNotFoundError: No module named 'six' to be marked as done. This means tha

Bug#1074137: marked as done (org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331))

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 14:32:40 + with message-id and subject line Bug#1074137: fixed in emacs 1:27.1+1-3.1+deb11u5 has caused the Debian Bug report #1074137, regarding org-link-expand-abbrev: Do not evaluate arbitrary unsafe Elisp code (CVE-2024-39331) to be marked as done. Thi

Bug#1078074: marked as done (python-django: CVE-2024-41989 CVE-2024-41990 CVE-2024-41991 CVE-2024-42005)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 14:32:09 + with message-id and subject line Bug#1078074: fixed in python-django 3:3.2.19-1+deb12u2 has caused the Debian Bug report #1078074, regarding python-django: CVE-2024-41989 CVE-2024-41990 CVE-2024-41991 CVE-2024-42005 to be marked as done. This me

Bug#1079557: rust-rustls - autopkgtest failure - test dependency issue.

2024-08-24 Thread Peter Michael Green
Package: rust-rustls Version: 0.21.12-4 Severity: serious The autopkgtests for rust-rustls are failing with > 46s bash: line 1: /usr/share/dh-rust/bin/cargo-auto-test: No such file or directory I presume you need to change the test dependency from dh-cargo to dh-rust to match the name of th

Bug#1077773: marked as done (slime: does not work with sbcl 2:2.3.7-2)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 07:01:20 -0700 with message-id <87y14m6mvj@tethera.net> and subject line release the block has caused the Debian Bug report #103, regarding slime: does not work with sbcl 2:2.3.7-2 to be marked as done. This means that you claim that the problem has been

Processed: src:libxs-parse-keyword-perl: fails to migrate to testing for too long: triggers autopkgtest issues

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.44-1 Bug #1079556 [src:libxs-parse-keyword-perl] src:libxs-parse-keyword-perl: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions libxs-parse-keyword-perl/0.44-1. Bug #1079556 [src:libxs-parse-keyword-perl] s

Bug#1079556: src:libxs-parse-keyword-perl: fails to migrate to testing for too long: triggers autopkgtest issues

2024-08-24 Thread Paul Gevers
Source: libxs-parse-keyword-perl Version: 0.42-1 Severity: serious Control: close -1 0.44-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

Processed: src:lxqt-session: fails to migrate to testing for too long: uploader built arch:all binary

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.4.0-1 Bug #1079554 [src:lxqt-session] src:lxqt-session: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions lxqt-session/1.4.0-1. Bug #1079554 [src:lxqt-session] src:lxqt-session: fails to migrate to testin

Bug#1079554: src:lxqt-session: fails to migrate to testing for too long: uploader built arch:all binary

2024-08-24 Thread Paul Gevers
Source: lxqt-session Version: 1.3.0-1 Severity: serious Control: close -1 1.4.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 a

Bug#1079553: src:zziplib: fails to migrate to testing for too long: FTBFS on s390x

2024-08-24 Thread Paul Gevers
Source: zziplib Version: 0.13.72+dfsg.1-1.2 Severity: serious Control: close -1 0.13.72+dfsg.1-1.3 Tags: sid trixie ftbfs 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

Processed: src:msc-generator: fails to migrate to testing for too long: FTBFS on armel/armhf

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 8.6.2-2 Bug #1079552 [src:msc-generator] src:msc-generator: fails to migrate to testing for too long: FTBFS on armel/armhf Marked as fixed in versions msc-generator/8.6.2-2. Bug #1079552 [src:msc-generator] src:msc-generator: fails to migrate to testing fo

Processed: src:zziplib: fails to migrate to testing for too long: FTBFS on s390x

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.13.72+dfsg.1-1.3 Bug #1079553 [src:zziplib] src:zziplib: fails to migrate to testing for too long: FTBFS on s390x Marked as fixed in versions zziplib/0.13.72+dfsg.1-1.3. Bug #1079553 [src:zziplib] src:zziplib: fails to migrate to testing for too long: FT

Bug#1079552: src:msc-generator: fails to migrate to testing for too long: FTBFS on armel/armhf

2024-08-24 Thread Paul Gevers
Source: msc-generator Version: 8.5-1 Severity: serious Control: close -1 8.6.2-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1077995 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unst

Processed: src:php-parser: fails to migrate to testing for too long: uploader built arch:all binary

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 5.1.0-1 Bug #1079551 [src:php-parser] src:php-parser: fails to migrate to testing for too long: uploader built arch:all binary Marked as fixed in versions php-parser/5.1.0-1. Bug #1079551 [src:php-parser] src:php-parser: fails to migrate to testing for too

Bug#1079551: src:php-parser: fails to migrate to testing for too long: uploader built arch:all binary

2024-08-24 Thread Paul Gevers
Source: php-parser Version: 5.0.2-3 Severity: serious Control: close -1 5.1.0-1 Tags: sid trixie pending 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#1079550: src:ruby-timecop: fails to migrate to testing for too long: autopkgtest regression on 32 bit archs

2024-08-24 Thread Paul Gevers
Source: ruby-timecop Version: 0.9.8-1 Severity: serious Control: close -1 0.9.10-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

Processed: src:ruby-timecop: fails to migrate to testing for too long: autopkgtest regression on 32 bit archs

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.9.10-1 Bug #1079550 [src:ruby-timecop] src:ruby-timecop: fails to migrate to testing for too long: autopkgtest regression on 32 bit archs Marked as fixed in versions ruby-timecop/0.9.10-1. Bug #1079550 [src:ruby-timecop] src:ruby-timecop: fails to migrate

Processed: src:symfony: fails to migrate to testing for too long: uploader built arch:all binaries

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > close -1 6.4.10+dfsg-1 Bug #1079549 [src:symfony] src:symfony: fails to migrate to testing for too long: uploader built arch:all binaries Marked as fixed in versions symfony/6.4.10+dfsg-1. Bug #1079549 [src:symfony] src:symfony: fails to migrate to testing for too

Bug#1079549: src:symfony: fails to migrate to testing for too long: uploader built arch:all binaries

2024-08-24 Thread Paul Gevers
Source: symfony Version: 6.4.7+dfsg-1 Severity: serious Control: close -1 6.4.10+dfsg-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

Processed: gtk4: Upload 4.15 to Unstable

2024-08-24 Thread Debian Bug Tracking System
Processing control commands: > block -1 by 1079545 1079546 Bug #1079548 [src:gtk4] gtk4: Upload 4.15 to Unstable 1079548 was not blocked by any bugs. 1079548 was not blocking any bugs. Added blocking bug(s) of 1079548: 1079546 and 1079545 -- 1079548: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#1079546: gtk4: two css tests are failing on s390x

2024-08-24 Thread Jeremy Bícha
Source: gtk4 Version: 4.15.5+ds-2 Severity: serious Tags: ftbfs User: debian-s...@lists.debian.org Usertags: s390x X-Debbugs-CC: debian-s...@lists.debian.org 2 new tests added in gtk4 4.15.* are failing on s390x but not on any other release architecture. We need to either fix these issues or ignor

Bug#1079545: gtk4: css/parser/math2.css test fails on armel

2024-08-24 Thread Jeremy Bícha
Source: gtk4 Version: 4.15.5+ds-2 Severity: serious Tags: ftbfs User: debian-...@lists.debian.org Usertags: armel X-Debbugs-CC: debian-...@lists.debian.org A new test added in gtk4 4.15.* is failing on armel but not on any other release architecture. We need to either fix this issue or ignore this

Processed: unarchiving 1072394, found 1072394 in 1.1.0-14, tagging 1072394

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 1072394 Bug #1072394 {Done: Jordi Mallach } [src:fcgiwrap] fcgiwrap: autopkgtest failures: The requested URL returned error: 500 Unarchived Bug 1072394 > found 1072394 1.1.0-14 Bug #1072394 {Done: Jordi Mallach } [src:fcgiwrap] fcgiwrap

Bug#1058575: marked as done (glogic: Fails to start due AttributeError)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 15:13:19 +0200 with message-id <20240824151319.7d105bba@debian-i7> and subject line hopefully REALLY fixing the bug has caused the Debian Bug report #1058575, regarding glogic: Fails to start due AttributeError to be marked as done. This means that you claim tha

Processed: Mark as fixed (properly this time?)

2024-08-24 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1058575 glogic/2.6-7 Bug #1058575 [glogic] glogic: Fails to start due AttributeError The source glogic and version 2.6-7 do not appear to match any binary packages Marked as fixed in versions glogic/2.6-7. > thanks Stopping processing here.

Bug#1077299: marked as done (git: Not migrating to testing for long time due to autopkgtest results)

2024-08-24 Thread Debian Bug Tracking System
Your message dated Sat, 24 Aug 2024 14:47:19 +0200 with message-id and subject line Re: Bug#1077299: git: Not migrating to testing for long time due to autopkgtest results has caused the Debian Bug report #1077299, regarding git: Not migrating to testing for long time due to autopkgtest results t

  1   2   >