Bug#1020698: marked as done (ITA: dlocate -- fast alternative to dpkg -L and dpkg -S)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 05:48:59 + with message-id and subject line Bug#1020698: fixed in dlocate 1.15 has caused the Debian Bug report #1020698, regarding ITA: dlocate -- fast alternative to dpkg -L and dpkg -S to be marked as done. This means that you claim that the problem has

Bug#1082933: marked as done (geoalchemy2: build failure on s390x)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 05:34:28 + with message-id and subject line Bug#1082933: fixed in geoalchemy2 0.15.2-1 has caused the Debian Bug report #1082933, regarding geoalchemy2: build failure on s390x to be marked as done. This means that you claim that the problem has been dealt w

Bug#1085151: marked as done (openmpi: FTBFS on arch:all: missing files, aborting)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 04:35:34 + with message-id and subject line Bug#1085151: fixed in openmpi 5.0.5-3 has caused the Debian Bug report #1085151, regarding openmpi: FTBFS on arch:all: missing files, aborting to be marked as done. This means that you claim that the problem has b

Bug#1085174: marked as done (genders: Please add Homepage to debian/control)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 03:19:08 + with message-id and subject line Bug#1085174: fixed in genders 1.27-3-3 has caused the Debian Bug report #1085174, regarding genders: Please add Homepage to debian/control to be marked as done. This means that you claim that the problem has been

Bug#1085168: marked as done (genders: FTBFS on mips64el and ppc64el: parallel build issue?)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 03:19:08 + with message-id and subject line Bug#1085168: fixed in genders 1.27-3-3 has caused the Debian Bug report #1085168, regarding genders: FTBFS on mips64el and ppc64el: parallel build issue? to be marked as done. This means that you claim that the pr

Bug#1085175: marked as done (genders: Frequent parallel build failure)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 03:19:08 + with message-id and subject line Bug#1085168: fixed in genders 1.27-3-3 has caused the Debian Bug report #1085168, regarding genders: Frequent parallel build failure to be marked as done. This means that you claim that the problem has been dealt

Bug#862957: marked as done (file-roller: Fails to deal correctly with filename encodings in zip files)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2024 05:00:49 +0300 with message-id and subject line i think it's fixed at some point has caused the Debian Bug report #862957, regarding file-roller: Fails to deal correctly with filename encodings in zip files to be marked as done. This means that you claim that

Bug#1085214: marked as done (xpenguins FTBFS on 32-bit with 64-bit time_t with gcc 14)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 22:20:29 + with message-id and subject line Bug#1085214: fixed in xpenguins 3.2.3-2 has caused the Debian Bug report #1085214, regarding xpenguins FTBFS on 32-bit with 64-bit time_t with gcc 14 to be marked as done. This means that you claim that the proble

Bug#1077834: marked as done (dm-writeboost-dkms: module fails to build for Linux 6.10: error: 'struct block_device' has no member named 'bd_inode')

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 22:18:59 + with message-id and subject line Bug#1077834: fixed in dm-writeboost 2.2.17-0.3 has caused the Debian Bug report #1077834, regarding dm-writeboost-dkms: module fails to build for Linux 6.10: error: 'struct block_device' has no member named 'bd_in

Bug#1085058: marked as done (iaito: FTBFS: Package libxxhash was not found in the pkg-config search path.)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 21:04:55 + with message-id and subject line Bug#1085058: fixed in iaito 5.9.4+ds-2 has caused the Debian Bug report #1085058, regarding iaito: FTBFS: Package libxxhash was not found in the pkg-config search path. to be marked as done. This means that you c

Bug#1056028: marked as done (rust-ntp-udp: autopkgtest failure)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 22:53:39 +0200 with message-id <71ec8871-0430-4fb0-9334-3267e4b80...@debian.org> and subject line done has caused the Debian Bug report #1056028, regarding rust-ntp-udp: autopkgtest failure to be marked as done. This means that you claim that the problem has bee

Bug#1046716: marked as done (xraylarch: Fails to build source after successful build)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 20:46:40 + with message-id and subject line Bug#1046716: fixed in xraylarch 0.9.81+ds1-1 has caused the Debian Bug report #1046716, regarding xraylarch: Fails to build source after successful build to be marked as done. This means that you claim that the pr

Bug#1079679: marked as done (xraylarch: tests fail with scipy 1.14)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 20:46:40 + with message-id and subject line Bug#1079679: fixed in xraylarch 0.9.81+ds1-1 has caused the Debian Bug report #1079679, regarding xraylarch: tests fail with scipy 1.14 to be marked as done. This means that you claim that the problem has been dea

Bug#1084586: marked as done (xraylarch: removal of Python standard libraries in Python 3.13)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 20:46:40 + with message-id and subject line Bug#1084586: fixed in xraylarch 0.9.81+ds1-1 has caused the Debian Bug report #1084586, regarding xraylarch: removal of Python standard libraries in Python 3.13 to be marked as done. This means that you claim that

Processed: closing 1071898

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1071898 0.9.74+ds1-2 Bug #1071898 [src:xraylarch] xraylarch: FTBFS: unsatisfiable build-dependencies The source 'xraylarch' and version '0.9.74+ds1-2' do not appear to match any binary packages Marked as fixed in versions xraylarch/0.9.74+d

Processed: closing 1041089

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1041089 1.1.0-1 Bug #1041089 [src:thin-provisioning-tools] thin-provisioning-tools FTBFS with googletest 1.13.0 Marked as fixed in versions thin-provisioning-tools/1.1.0-1. Bug #1041089 [src:thin-provisioning-tools] thin-provisioning-tools

Bug#1084953: marked as done (thin-provisioning-tools: Incorrect symlink)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 19:05:23 + with message-id and subject line Bug#1084953: fixed in thin-provisioning-tools 1.1.0-2 has caused the Debian Bug report #1084953, regarding thin-provisioning-tools: Incorrect symlink to be marked as done. This means that you claim that the proble

Processed: fixed 1065342 in 3.16.0+ds1-1, closing 1065342

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1065342 3.16.0+ds1-1 Bug #1065342 {Done: Moritz Schlarb } [nagstamon] nagstamon: upgrade warnings: SyntaxWarning: invalid escape sequence Ignoring request to alter fixed versions of bug #1065342 to the same values previously set > close 10

Processed: fixed 1065342 in 3.16.0+ds1-1, closing 1065342

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > fixed 1065342 3.16.0+ds1-1 Bug #1065342 [nagstamon] nagstamon: upgrade warnings: SyntaxWarning: invalid escape sequence Marked as fixed in versions nagstamon/3.16.0+ds1-1. > close 1065342 Bug #1065342 [nagstamon] nagstamon: upgrade warnings: Synt

Bug#1084043: marked as done (turtlefmt: FTBFS: method not found in `TurtleParser`)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 17:35:08 + with message-id and subject line Bug#1084043: fixed in turtlefmt 0.1.1-4 has caused the Debian Bug report #1084043, regarding turtlefmt: FTBFS: method not found in `TurtleParser` to be marked as done. This means that you claim that the problem ha

Processed: Re: RFP: gitea -- A painless self-hosted Git service

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 935834 Bug #935834 [wnpp] RFP: gitea -- A painless self-hosted Git service Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 935834: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935834

Bug#1085030: marked as done (libghc-swish-doc: Rebuild against GHC 9.6)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 17:34:27 + with message-id and subject line Bug#1085030: fixed in haskell-swish 0.10.9.0-2 has caused the Debian Bug report #1085030, regarding libghc-swish-doc: Rebuild against GHC 9.6 to be marked as done. This means that you claim that the problem has be

Processed: Update bug 1080510 -- sorry

2024-10-16 Thread Debian Bug Tracking System
Processing control commands: > severity -1 minor Bug #1080510 [src:onnxruntime] onnxruntime: please upgrade to latest upstream release 1.19.2 Severity set to 'minor' from 'serious' > notfound -1 4.4.1-1.1 Bug #1080510 [src:onnxruntime] onnxruntime: please upgrade to latest upstream release 1.19.

Bug#1084809: marked as done (xmlrpc-c FTCBFS: variable name for build architecture compiler changed)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 17:06:47 + with message-id and subject line Bug#1084809: fixed in xmlrpc-c 1.59.03-5 has caused the Debian Bug report #1084809, regarding xmlrpc-c FTCBFS: variable name for build architecture compiler changed to be marked as done. This means that you claim

Bug#1037113: marked as done (Should not be in /usr/games)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 16:42:15 + with message-id and subject line Bug#1037113: fixed in screen-message 0.27-1 has caused the Debian Bug report #1037113, regarding Should not be in /usr/games to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1085028: marked as done (libghc-hsyaml-doc: Rebuild against GHC 9.6)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 16:35:03 + with message-id and subject line Bug#1085028: fixed in haskell-hsyaml 0.2.1.4-2 has caused the Debian Bug report #1085028, regarding libghc-hsyaml-doc: Rebuild against GHC 9.6 to be marked as done. This means that you claim that the problem has b

Bug#1085029: marked as done (libghc-intern-doc: Rebuild against GHC 9.6)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 16:35:10 + with message-id and subject line Bug#1085029: fixed in haskell-intern 0.9.5-3 has caused the Debian Bug report #1085029, regarding libghc-intern-doc: Rebuild against GHC 9.6 to be marked as done. This means that you claim that the problem has bee

Processed: closing 1054230

2024-10-16 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1054230 Bug #1054230 [libvirt-daemon-system] Please change permissions on /var/lib/libvirt/images/ Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1054230: https://bugs.debian.org/cgi-bin

Bug#1083762: marked as done (scoary: (build-)depends on deprecated module python3-pkg-resources)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 15:50:46 + with message-id and subject line Bug#1083762: fixed in scoary 1.6.16-9 has caused the Debian Bug report #1083762, regarding scoary: (build-)depends on deprecated module python3-pkg-resources to be marked as done. This means that you claim that th

Bug#930315: marked as done (Please drop obsolete uniutils package)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 15:07:27 + with message-id and subject line Bug#930315: fixed in uniutils 2.28-1 has caused the Debian Bug report #930315, regarding Please drop obsolete uniutils package to be marked as done. This means that you claim that the problem has been dealt with.

Bug#740968: marked as done (uniutils: Fails to build with clang instead of gcc)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 15:07:27 + with message-id and subject line Bug#740968: fixed in uniutils 2.28-1 has caused the Debian Bug report #740968, regarding uniutils: Fails to build with clang instead of gcc to be marked as done. This means that you claim that the problem has been

Bug#1084925: marked as done (ITS: uniutils)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 15:07:27 + with message-id and subject line Bug#1084925: fixed in uniutils 2.28-1 has caused the Debian Bug report #1084925, regarding ITS: uniutils to be marked as done. This means that you claim that the problem has been dealt with. If this is not the cas

Bug#1083559: marked as done (propka: (build-)depends on deprecated module python3-pkg-resources)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 15:07:01 + with message-id and subject line Bug#1083559: fixed in propka 3.5.1-2 has caused the Debian Bug report #1083559, regarding propka: (build-)depends on deprecated module python3-pkg-resources to be marked as done. This means that you claim that the

Bug#1066323: marked as done (uniutils: FTBFS: uniname.c:531:43: error: implicit declaration of function ‘isspace’ [-Werror=implicit-function-declaration])

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 15:07:27 + with message-id and subject line Bug#1066323: fixed in uniutils 2.28-1 has caused the Debian Bug report #1066323, regarding uniutils: FTBFS: uniname.c:531:43: error: implicit declaration of function ‘isspace’ [-Werror=implicit-function-declaratio

Bug#1084375: marked as done (rust-rustls: FTBFS: error: failed to select a version for the requirement `base64 = "^0.21"`)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:50:49 + with message-id and subject line Bug#1084375: fixed in rust-rustls 0.21.12-6 has caused the Debian Bug report #1084375, regarding rust-rustls: FTBFS: error: failed to select a version for the requirement `base64 = "^0.21"` to be marked as done.

Bug#1084377: marked as done (rust-xor-name: FTBFS: error: lint `box_pointers` has been removed: it does not detect other kinds of allocations, and existed only for historical reasons)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:39:10 + with message-id and subject line Bug#1084377: fixed in rust-xor-name 5.0.0-8 has caused the Debian Bug report #1084377, regarding rust-xor-name: FTBFS: error: lint `box_pointers` has been removed: it does not detect other kinds of allocations, an

Bug#1083552: marked as done (poretools: (build-)depends on deprecated module python3-pkg-resources)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:38:30 + with message-id and subject line Bug#1083552: fixed in poretools 0.6.0+dfsg-7 has caused the Debian Bug report #1083552, regarding poretools: (build-)depends on deprecated module python3-pkg-resources to be marked as done. This means that you cla

Bug#1084298: marked as done (meli: FTBFS: error: failed to select a version for the requirement `base64 = ">=0.13, <=0.21"`)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:37:03 + with message-id and subject line Bug#1084298: fixed in meli 0.8.7+20241007+dfsg-1 has caused the Debian Bug report #1084298, regarding meli: FTBFS: error: failed to select a version for the requirement `base64 = ">=0.13, <=0.21"` to be marked as

Bug#1082819: marked as done (libisal: Update symbols file for hurd-amd64)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:36:23 + with message-id and subject line Bug#1082819: fixed in libisal 2.31.0-0.2 has caused the Debian Bug report #1082819, regarding libisal: Update symbols file for hurd-amd64 to be marked as done. This means that you claim that the problem has been d

Bug#1073941: marked as done (1oom has no launcher (.desktop file) or icon, and is totally invisuble to any GUI.)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 14:35:09 + with message-id and subject line Bug#1073941: fixed in 1oom 1.11-1 has caused the Debian Bug report #1073941, regarding 1oom has no launcher (.desktop file) or icon, and is totally invisuble to any GUI. to be marked as done. This means that you

Bug#1039134: marked as done (babeld: ships sysv-init script without systemd unit)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 13:34:24 + with message-id and subject line Bug#1039134: fixed in babeld 1.13.1+ds-1 has caused the Debian Bug report #1039134, regarding babeld: ships sysv-init script without systemd unit to be marked as done. This means that you claim that the problem ha

Bug#1081873: marked as done (pymdown-extensions: FTBFS: E AssertionError: False is not true)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 13:16:23 + with message-id and subject line Bug#1081873: fixed in pymdown-extensions 10.11.2-1 has caused the Debian Bug report #1081873, regarding pymdown-extensions: FTBFS: E AssertionError: False is not true to be marked as done. This means that you clai

Bug#1084980: marked as done (golang-github-containers-buildah: CVE-2024-9407 CVE-2024-9675)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:35:13 + with message-id and subject line Bug#1084980: fixed in golang-github-containers-buildah 1.37.4+ds1-1 has caused the Debian Bug report #1084980, regarding golang-github-containers-buildah: CVE-2024-9407 CVE-2024-9675 to be marked as done. This me

Bug#1085112: marked as done (python3-distro-info: filter by SOURCE_DATE_EPOCH when configured)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:34:16 + with message-id and subject line Bug#1085112: fixed in distro-info 1.12 has caused the Debian Bug report #1085112, regarding python3-distro-info: filter by SOURCE_DATE_EPOCH when configured to be marked as done. This means that you claim that the

Bug#1082314: marked as done (dokuwiki,php-phpseclib: aliasing conflict on /usr/share/php/phpseclib)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:34:47 + with message-id and subject line Bug#1082314: fixed in dokuwiki 0.0.20220731.a-3 has caused the Debian Bug report #1082314, regarding dokuwiki,php-phpseclib: aliasing conflict on /usr/share/php/phpseclib to be marked as done. This means that you

Bug#1082313: marked as done (dokuwiki,php-random-compat: aliasing conflict on /usr/share/php/random_compat)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:34:47 + with message-id and subject line Bug#1082313: fixed in dokuwiki 0.0.20220731.a-3 has caused the Debian Bug report #1082313, regarding dokuwiki,php-random-compat: aliasing conflict on /usr/share/php/random_compat to be marked as done. This means

Bug#1084356: marked as done (ros-joint-state-publisher: FTBFS: ModuleNotFoundError: No module named 'sensor_msgs')

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:14:08 + with message-id and subject line Bug#1084356: fixed in ros-joint-state-publisher 1.15.1-4 has caused the Debian Bug report #1084356, regarding ros-joint-state-publisher: FTBFS: ModuleNotFoundError: No module named 'sensor_msgs' to be marked as do

Bug#1085049: marked as done (python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:13:57 + with message-id and subject line Bug#1085049: fixed in pyvkfft-cuda 2024.1.4+ds1-3 has caused the Debian Bug report #1085049, regarding python3-pyvkfft-cuda has an undeclared file conflict on /usr/lib/python3/dist-packages/pyvkfft/cuda.py to be m

Bug#1084061: marked as done (golang-github-containers-common: CVE-2024-9341)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:07:03 + with message-id and subject line Bug#1084061: fixed in golang-github-containers-common 0.60.4+ds1-1 has caused the Debian Bug report #1084061, regarding golang-github-containers-common: CVE-2024-9341 to be marked as done. This means that you cla

Bug#1079583: marked as done (jpy FTBFS on Zero-Assembler architectures with OpenJDK 21)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 12:08:24 + with message-id and subject line Bug#1079583: fixed in jpy 0.18.0-2 has caused the Debian Bug report #1079583, regarding jpy FTBFS on Zero-Assembler architectures with OpenJDK 21 to be marked as done. This means that you claim that the problem ha

Bug#1056977: marked as done (regalloc2-tool: please update to v0.9.3)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 13:52:14 +0200 with message-id <172907953497.1303242.3112761216175769...@cairon.jones.dk> and subject line Re: regalloc2-tool: please update to v0.9.3 has caused the Debian Bug report #1056977, regarding regalloc2-tool: please update to v0.9.3 to be marked as don

Bug#1083655: marked as done (python-leidenalg: (build-)depends on deprecated module python3-pkg-resources)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 11:27:58 + with message-id and subject line Bug#1083655: fixed in python-leidenalg 0.10.2-2 has caused the Debian Bug report #1083655, regarding python-leidenalg: (build-)depends on deprecated module python3-pkg-resources to be marked as done. This means t

Bug#1083178: marked as done (mercurial: FTBFS: Failed test-patchbomb.t: output changed)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:41:12 + with message-id and subject line Bug#1083178: fixed in mercurial 6.8.1-1 has caused the Debian Bug report #1083178, regarding mercurial: FTBFS: Failed test-patchbomb.t: output changed to be marked as done. This means that you claim that the probl

Bug#1073467: marked as done (freecol: FTBFS: make: *** [debian/rules:8: binary] Error 25)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:22:00 + with message-id and subject line Bug#1073467: fixed in freecol 1.2.0-1 has caused the Debian Bug report #1073467, regarding freecol: FTBFS: make: *** [debian/rules:8: binary] Error 25 to be marked as done. This means that you claim that the probl

Bug#911331: marked as done (ploticus: randomly fails drawing lines)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:00:29 + with message-id and subject line Bug#911331: fixed in ploticus 2.42-8 has caused the Debian Bug report #911331, regarding ploticus: randomly fails drawing lines to be marked as done. This means that you claim that the problem has been dealt with.

Bug#960225: marked as done (ploticus FTCBFS: does not pass cross tools to make)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:00:29 + with message-id and subject line Bug#960225: fixed in ploticus 2.42-8 has caused the Debian Bug report #960225, regarding ploticus FTCBFS: does not pass cross tools to make to be marked as done. This means that you claim that the problem has been

Bug#1083383: marked as done (fastaq: (build-)depends on deprecated module python3-pkg-resources)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 09:54:56 + with message-id and subject line Bug#1083383: fixed in fastaq 3.17.0-8 has caused the Debian Bug report #1083383, regarding fastaq: (build-)depends on deprecated module python3-pkg-resources to be marked as done. This means that you claim that th

Bug#1081535: marked as done (nmu: llvm-toolchain-15_1:15.0.6-4+b1)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 11:42:39 +0200 with message-id and subject line Re: Bug#1081535: nmu: llvm-toolchain-15_1:15.0.6-4+b1 has caused the Debian Bug report #1081535, regarding nmu: llvm-toolchain-15_1:15.0.6-4+b1 to be marked as done. This means that you claim that the problem has

Bug#1085017: marked as done (nmu: libxxf86vm_1:1.1.4-1+b2)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 11:23:05 +0200 with message-id and subject line Re: Bug#1085017: nmu: libxxf86vm_1:1.1.4-1+b2 has caused the Debian Bug report #1085017, regarding nmu: libxxf86vm_1:1.1.4-1+b2 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1085052: marked as done (nmu: many packages for riscv64 coinstallation)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 11:21:25 +0200 with message-id and subject line Re: Bug#1085052: nmu: many packages for riscv64 coinstallation has caused the Debian Bug report #1085052, regarding nmu: many packages for riscv64 coinstallation to be marked as done. This means that you claim tha

Bug#1084381: marked as done (spectral-cube: FTBFS: failing tests)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 09:19:20 + with message-id and subject line Bug#1084353: fixed in radio-beam 0.3.7-5 has caused the Debian Bug report #1084353, regarding spectral-cube: FTBFS: failing tests to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1084353: marked as done (radio-beam: FTBFS: E astropy.units.core.UnitScaleError: cannot create a unit with a scale of 0.)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 09:19:20 + with message-id and subject line Bug#1084353: fixed in radio-beam 0.3.7-5 has caused the Debian Bug report #1084353, regarding radio-beam: FTBFS: E astropy.units.core.UnitScaleError: cannot create a unit with a scale of 0. to be marked as done.

Bug#1084304: marked as done (mypy: FTBFS: FAILED mypyc/test/test_run.py::TestRun::run-dicts.test::testDictIterationMethodsRun)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 10:50:48 +0200 with message-id and subject line Re: mypy: FTBFS: FAILED mypyc/test/test_run.py::TestRun::run-dicts.test::testDictIterationMethodsRun has caused the Debian Bug report #1084304, regarding mypy: FTBFS: FAILED mypyc/test/test_run.py::TestRun::run-d

Bug#1085102: marked as done (sdl-ball FTCBFS: strips with the build architecture strip)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 08:38:08 + with message-id and subject line Bug#1085102: fixed in sdl-ball 1.04+dfsg-2 has caused the Debian Bug report #1085102, regarding sdl-ball FTCBFS: strips with the build architecture strip to be marked as done. This means that you claim that the pr

Bug#1082978: marked as done (ros-interactive-markers: FTBFS: ERROR: The following tests failed to run: * testserver_test)

2024-10-16 Thread Debian Bug Tracking System
Your message dated Wed, 16 Oct 2024 09:14:12 +0200 with message-id and subject line Fwd: ros-interactive-markers_1.12.0-10_source.changes ACCEPTED into unstable has caused the Debian Bug report #1082978, regarding ros-interactive-markers: FTBFS: ERROR: The following tests failed to run: * tests