Processed: src:nitime: fails to migrate to testing for too long: autopkgtest regression on 32 bits systems

2024-01-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.10.2-2 Bug #1061233 [src:nitime] src:nitime: fails to migrate to testing for too long: autopkgtest regression on 32 bits systems Marked as fixed in versions nitime/0.10.2-2. Bug #1061233 [src:nitime] src:nitime: fails to migrate to testing for too long:

Processed: src:coq: fails to migrate to testing for too long: triggers autopkgtest issues

2024-01-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 8.18.0+dfsg-1 Bug #1061232 [src:coq] src:coq: fails to migrate to testing for too long: triggers autopkgtest issues Marked as fixed in versions coq/8.18.0+dfsg-1. Bug #1061232 [src:coq] src:coq: fails to migrate to testing for too long: triggers autopkgtes

Bug#1052912: marked as done (python-maturin: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 101)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sun, 21 Jan 2024 00:51:02 + with message-id and subject line Bug#1052912: fixed in python-maturin 1.3.2-1 has caused the Debian Bug report #1052912, regarding python-maturin: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 101 to be marked as done. This

Bug#931769: marked as done (MIME::Decoder::Base64::encode_it() is too slow)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 23:50:32 + with message-id and subject line Bug#931769: fixed in libmime-tools-perl 5.512-1 has caused the Debian Bug report #931769, regarding MIME::Decoder::Base64::encode_it() is too slow to be marked as done. This means that you claim that the problem h

Bug#1054262: marked as done (faicd64-large_6.0.3.iso "Cannot find grub.cfg")

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 23:49:32 + with message-id and subject line Bug#1054262: fixed in fai 6.2 has caused the Debian Bug report #1054262, regarding faicd64-large_6.0.3.iso "Cannot find grub.cfg" to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1050383: marked as done (setup-storage confused by valid md device names)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 23:49:32 + with message-id and subject line Bug#1050383: fixed in fai 6.2 has caused the Debian Bug report #1050383, regarding setup-storage confused by valid md device names to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1030312: marked as done (fai-client: PACKAGES aptitude does not work anymore with fai6.0)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 23:49:32 + with message-id and subject line Bug#1030312: fixed in fai 6.2 has caused the Debian Bug report #1030312, regarding fai-client: PACKAGES aptitude does not work anymore with fai6.0 to be marked as done. This means that you claim that the problem h

Bug#1041609: marked as done (fai softupdate fails in get-config-dir-svn)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 23:49:32 + with message-id and subject line Bug#1041609: fixed in fai 6.2 has caused the Debian Bug report #1041609, regarding fai softupdate fails in get-config-dir-svn to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1057860: marked as done (breezy ftbfs with Python 3.12:)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 23:49:25 + with message-id and subject line Bug#1057860: fixed in breezy 3.3.5-1 has caused the Debian Bug report #1057860, regarding breezy ftbfs with Python 3.12: to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1054263: marked as done (faicd64-large_6.0.3.iso "Cannot find grub.cfg")

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 23:49:32 + with message-id and subject line Bug#1054263: fixed in fai 6.2 has caused the Debian Bug report #1054263, regarding faicd64-large_6.0.3.iso "Cannot find grub.cfg" to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1056649: marked as done (vectorscan: please make the build reproducible)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:56:31 + with message-id and subject line Bug#1056649: fixed in vectorscan 5.4.11-2 has caused the Debian Bug report #1056649, regarding vectorscan: please make the build reproducible to be marked as done. This means that you claim that the problem has be

Bug#825547: marked as done (tennix: please make the build reproducible)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:56:05 + with message-id and subject line Bug#825547: fixed in tennix 1.3.4-0.1 has caused the Debian Bug report #825547, regarding tennix: please make the build reproducible to be marked as done. This means that you claim that the problem has been dealt

Bug#1038570: marked as done (tennix: Depends on SDL 1.2)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:56:05 + with message-id and subject line Bug#1038570: fixed in tennix 1.3.4-0.1 has caused the Debian Bug report #1038570, regarding tennix: Depends on SDL 1.2 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1053924: marked as done (timew: autopkgtests fail with man-db 2.12.0)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:56:19 + with message-id and subject line Bug#1053924: fixed in timew 1.5.0+ds.1-2 has caused the Debian Bug report #1053924, regarding timew: autopkgtests fail with man-db 2.12.0 to be marked as done. This means that you claim that the problem has been d

Bug#992889: marked as done (/usr/sbin/update-gsfontmap: overly complicated)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:41:08 + with message-id and subject line Bug#992889: fixed in ghostscript 10.02.1~dfsg-3 has caused the Debian Bug report #992889, regarding /usr/sbin/update-gsfontmap: overly complicated to be marked as done. This means that you claim that the problem h

Bug#782901: marked as done (ghostscript: missing dependency on TeX)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:41:08 + with message-id and subject line Bug#782901: fixed in ghostscript 10.02.1~dfsg-3 has caused the Debian Bug report #782901, regarding ghostscript: missing dependency on TeX to be marked as done. This means that you claim that the problem has been

Bug#740959: marked as done (/usr/sbin/update-gsfontmap: sets wrong file permissions)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:41:08 + with message-id and subject line Bug#740959: fixed in ghostscript 10.02.1~dfsg-3 has caused the Debian Bug report #740959, regarding /usr/sbin/update-gsfontmap: sets wrong file permissions to be marked as done. This means that you claim that the

Bug#1056806: marked as done (guiqwt: ftbfs with cython 3.0.x)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:41:42 + with message-id and subject line Bug#1056806: fixed in guiqwt 4.4.4-1 has caused the Debian Bug report #1056806, regarding guiqwt: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1053377: marked as done (ghostscript-x: ghostscript 10.02.0~dfsg-2 does not remove ghostscript-x 10.01.2~dfsg-1 automatically)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:41:08 + with message-id and subject line Bug#1053377: fixed in ghostscript 10.02.1~dfsg-3 has caused the Debian Bug report #1053377, regarding ghostscript-x: ghostscript 10.02.0~dfsg-2 does not remove ghostscript-x 10.01.2~dfsg-1 automatically to be mark

Bug#1061210: marked as done (Please upgrade to llvm-toolchain-17)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 22:39:05 + with message-id and subject line Bug#1061210: fixed in bpftrace 0.19.1-1 has caused the Debian Bug report #1061210, regarding Please upgrade to llvm-toolchain-17 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1055848: marked as done (cfgrib: test failure - can't find eccodes)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 21:41:12 + with message-id and subject line Bug#1055848: fixed in ecmwflibs 2:0.5.7-4 has caused the Debian Bug report #1055848, regarding cfgrib: test failure - can't find eccodes to be marked as done. This means that you claim that the problem has been de

Bug#1056476: marked as done (python-importlib-metadata's autopkg tests fail with Python 3.12)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 17:37:36 -0400 with message-id and subject line Re: Bug#1056476: python-importlib-metadata's autopkg tests fail with Python 3.12 has caused the Debian Bug report #1056476, regarding python-importlib-metadata's autopkg tests fail with Python 3.12 to be marked a

Bug#610580: marked as done (add SEE ALSO to the man pages)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 14:35:39 -0600 with message-id <15878987.O9o76ZdvQC@riemann> and subject line Re: add SEE ALSO to the man pages has caused the Debian Bug report #610580, regarding add SEE ALSO to the man pages to be marked as done. This means that you claim that the problem has

Bug#610668: marked as done (mention gv more)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 15:02:33 -0600 with message-id <6250165.mvXUDI8C0e@riemann> and subject line Re: mention gv more has caused the Debian Bug report #610668, regarding mention gv more to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1043991: marked as done (bibutils: Fails to build source after successful build)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 21:03:16 + with message-id and subject line Bug#1043991: fixed in bibutils 7.2-3 has caused the Debian Bug report #1043991, regarding bibutils: Fails to build source after successful build to be marked as done. This means that you claim that the problem has

Bug#1033353: marked as done (libpwquality failing to build on bookworm with python 3.11)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 21:27:34 +0100 with message-id <2be42c59-0126-4e1a-bd31-826416f6e...@debian.org> and subject line Re: libpwquality failing to build on bookworm with python 3.11 has caused the Debian Bug report #1033353, regarding libpwquality failing to build on bookworm with py

Processed: closing 1060917

2024-01-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1060917 1:10.11.6-0+deb12u1 Bug #1060917 [mariadb] postfix-mysql broken in 3.7.9, results in unsupported dictionary type There is no source info for the package 'mariadb' at version '1:10.11.6-0+deb12u1' with architecture '' Unable to make

Bug#1058079: marked as done (tar: CVE-2023-39804: Incorrectly handled extension attributes in PAX archives can lead to a crash)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:47:42 + with message-id and subject line Bug#1058079: fixed in tar 1.34+dfsg-1+deb11u1 has caused the Debian Bug report #1058079, regarding tar: CVE-2023-39804: Incorrectly handled extension attributes in PAX archives can lead to a crash to be marked as

Bug#1054268: marked as done (mate-applets: mate weather applet not retrieving data)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:47:40 + with message-id and subject line Bug#1054268: fixed in libmateweather 1.24.1-1+deb11u1 has caused the Debian Bug report #1054268, regarding mate-applets: mate weather applet not retrieving data to be marked as done. This means that you claim that

Bug#1035389: marked as done (ruby-aws-sdk-core: The VERSION file is not packaged)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:47:42 + with message-id and subject line Bug#1035389: fixed in ruby-aws-sdk-core 3.104.3-3+deb11u2 has caused the Debian Bug report #1035389, regarding ruby-aws-sdk-core: The VERSION file is not packaged to be marked as done. This means that you claim th

Bug#1061197: marked as done (DEP17: move PAM module to /usr)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:34:26 + with message-id and subject line Bug#1061197: fixed in gnome-keyring 42.1-2 has caused the Debian Bug report #1061197, regarding DEP17: move PAM module to /usr to be marked as done. This means that you claim that the problem has been dealt with.

Bug#977716: marked as done (ITP: llhttp -- parser for HTTP messages)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:05:23 + with message-id and subject line Bug#977716: fixed in node-undici 5.28.2+dfsg1+~cs23.11.12.3-4 has caused the Debian Bug report #977716, regarding ITP: llhttp -- parser for HTTP messages to be marked as done. This means that you claim that the pr

Bug#1061174: marked as done (src:gmsh: fails to migrate to testing for too long: causes timeout of pygmsh autopkgtest on i386)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:05:22 + with message-id and subject line Bug#1061174: fixed in gmsh 4.12.0+ds1-1 has caused the Debian Bug report #1061174, regarding src:gmsh: fails to migrate to testing for too long: causes timeout of pygmsh autopkgtest on i386 to be marked as done.

Bug#1060715: marked as done (gmsh: requires source-only upload for migration to testing)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:05:21 + with message-id and subject line Bug#1060715: fixed in gmsh 4.12.0+ds1-1 has caused the Debian Bug report #1060715, regarding gmsh: requires source-only upload for migration to testing to be marked as done. This means that you claim that the prob

Bug#1061186: marked as done (oxigraph: fails to build from source)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:59:16 + with message-id and subject line Bug#1061186: fixed in oxigraph 0.3.22-5 has caused the Debian Bug report #1061186, regarding oxigraph: fails to build from source to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1054783: marked as done (libpwquality: FTBFS: dh_install: error: missing files, aborting)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:59:06 + with message-id and subject line Bug#1054783: fixed in libpwquality 1.4.5-2 has caused the Debian Bug report #1054783, regarding libpwquality: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that

Bug#1001264: marked as done (coinor-cbc is built with asserts enabled)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 19:59:47 +0100 with message-id <76e19f94-591b-434f-a9e1-d1e20768c...@debian.org> and subject line has caused the Debian Bug report #1001264, regarding coinor-cbc is built with asserts enabled to be marked as done. This means that you claim that the problem has

Bug#1059278: marked as done (systemd: CVE-2023-7008)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:47:08 + with message-id and subject line Bug#1059278: fixed in systemd 252.21-1~deb12u1 has caused the Debian Bug report #1059278, regarding systemd: CVE-2023-7008 to be marked as done. This means that you claim that the problem has been dealt with. If t

Processed: closing 741664, tagging 741664

2024-01-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 741664 Bug #741664 [gnome-keyring] provide gnome-keyring in wheezy-backports Marked Bug as done > tags 741664 + wontfix Bug #741664 {Done: Michael Biebl } [gnome-keyring] provide gnome-keyring in wheezy-backports Added tag(s) wontfix. > tha

Bug#994647: marked as done (O: tablix2 -- Kernel for solving general timetabling problems)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:14:21 + with message-id and subject line Bug#1059654: Removed package(s) from unstable has caused the Debian Bug report #994647, regarding O: tablix2 -- Kernel for solving general timetabling problems to be marked as done. This means that you claim that

Bug#1059654: marked as done (RM: tablix2 -- RoQA; orphaned; upstream deprecation notice; very low popcon)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:14:18 + with message-id and subject line Bug#1059654: Removed package(s) from unstable has caused the Debian Bug report #1059654, regarding RM: tablix2 -- RoQA; orphaned; upstream deprecation notice; very low popcon to be marked as done. This means that

Bug#928542: marked as done (ITA: python-fswrap -- unified object oriented interface to file system objects)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:11:27 + with message-id and subject line Bug#1061113: Removed package(s) from unstable has caused the Debian Bug report #928542, regarding ITA: python-fswrap -- unified object oriented interface to file system objects to be marked as done. This means th

Bug#928541: marked as done (O: commando -- wrapper for argparse to define declaratively)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:10:51 + with message-id and subject line Bug#1061128: Removed package(s) from unstable has caused the Debian Bug report #928541, regarding O: commando -- wrapper for argparse to define declaratively to be marked as done. This means that you claim that th

Bug#1061128: marked as done (RM: commando -- RoQA; dead upstream; orphaned; low popcon)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:10:47 + with message-id and subject line Bug#1061128: Removed package(s) from unstable has caused the Debian Bug report #1061128, regarding RM: commando -- RoQA; dead upstream; orphaned; low popcon to be marked as done. This means that you claim that the

Bug#1061113: marked as done (RM: python-fswrap -- ROM dead upstream, lowpopcon, RC buggy, orphaned)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:11:24 + with message-id and subject line Bug#1061113: Removed package(s) from unstable has caused the Debian Bug report #1061113, regarding RM: python-fswrap -- ROM dead upstream, lowpopcon, RC buggy, orphaned to be marked as done. This means that you cl

Bug#1059664: marked as done (python-fswrap: autopkgtest failure with Python 3.12)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:11:27 + with message-id and subject line Bug#1061113: Removed package(s) from unstable has caused the Debian Bug report #1059664, regarding python-fswrap: autopkgtest failure with Python 3.12 to be marked as done. This means that you claim that the probl

Bug#1018498: marked as done (python-fswrap: build-depends on python3-nose or uses it for autopkgtest)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:11:27 + with message-id and subject line Bug#1061113: Removed package(s) from unstable has caused the Debian Bug report #1018498, regarding python-fswrap: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you

Bug#1018330: marked as done (commando: build-depends on python3-nose or uses it for autopkgtest)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 18:10:51 + with message-id and subject line Bug#1061128: Removed package(s) from unstable has caused the Debian Bug report #1018330, regarding commando: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim

Bug#1033423: marked as done (lynx: Status line stuck on "HTTP/1.1 200 OK", body not rendered, no input accepted when receiving a specifically-formatted response)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 17:38:26 + with message-id and subject line Bug#1033423: fixed in lynx 2.9.0rel.0-1 has caused the Debian Bug report #1033423, regarding lynx: Status line stuck on "HTTP/1.1 200 OK", body not rendered, no input accepted when receiving a specifically-formatt

Bug#1041686: marked as done (Add support for HTTP Status Code 308 as described in RFC 7238 (with patch))

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 17:38:26 + with message-id and subject line Bug#1041686: fixed in lynx 2.9.0rel.0-1 has caused the Debian Bug report #1041686, regarding Add support for HTTP Status Code 308 as described in RFC 7238 (with patch) to be marked as done. This means that you cl

Bug#1037353: marked as done (lynx.1: a few formatting fixes for the manual)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 17:38:26 + with message-id and subject line Bug#1037353: fixed in lynx 2.9.0rel.0-1 has caused the Debian Bug report #1037353, regarding lynx.1: a few formatting fixes for the manual to be marked as done. This means that you claim that the problem has been

Bug#1060408: marked as done (edk2: CVE-2022-36763 CVE-2022-36764 CVE-2022-36765)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 17:05:22 + with message-id and subject line Bug#1060408: fixed in edk2 2023.11-5 has caused the Debian Bug report #1060408, regarding edk2: CVE-2022-36763 CVE-2022-36764 CVE-2022-36765 to be marked as done. This means that you claim that the problem has bee

Bug#1058079: marked as done (tar: CVE-2023-39804: Incorrectly handled extension attributes in PAX archives can lead to a crash)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 16:47:22 + with message-id and subject line Bug#1058079: fixed in tar 1.34+dfsg-1.2+deb12u1 has caused the Debian Bug report #1058079, regarding tar: CVE-2023-39804: Incorrectly handled extension attributes in PAX archives can lead to a crash to be marked a

Bug#972715: marked as done (atril: segfault on opening an epub file)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 16:47:08 + with message-id and subject line Bug#972715: fixed in atril 1.26.0-2+deb12u1 has caused the Debian Bug report #972715, regarding atril: segfault on opening an epub file to be marked as done. This means that you claim that the problem has been dea

Bug#1059060: marked as done (espeak-ng: CVE-2023-49990 CVE-2023-49991 CVE-2023-49992 CVE-2023-49993 CVE-2023-49994)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 16:47:17 + with message-id and subject line Bug#1059060: fixed in espeak-ng 1.51+dfsg-10+deb12u1 has caused the Debian Bug report #1059060, regarding espeak-ng: CVE-2023-49990 CVE-2023-49991 CVE-2023-49992 CVE-2023-49993 CVE-2023-49994 to be marked as done.

Bug#1040339: marked as done (pypdf2: CVE-2023-36464)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 16:47:21 + with message-id and subject line Bug#1040339: fixed in pypdf2 2.12.1-3+deb12u1 has caused the Debian Bug report #1040339, regarding pypdf2: CVE-2023-36464 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1040338: marked as done (pypdf: CVE-2023-36464)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 16:47:21 + with message-id and subject line Bug#1040338: fixed in pypdf 3.4.1-1+deb12u1 has caused the Debian Bug report #1040338, regarding pypdf: CVE-2023-36464 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1038603: marked as done (libisl23: amd64/i386 baseline violation: uses BMI instructions)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 16:47:18 + with message-id and subject line Bug#1038603: fixed in isl 0.25-1.1 has caused the Debian Bug report #1038603, regarding libisl23: amd64/i386 baseline violation: uses BMI instructions to be marked as done. This means that you claim that the probl

Bug#1061082: marked as done (libharfbuzz-dev: please add ${gir:Depends}, ${gir:Provides})

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 15:49:13 + with message-id and subject line Bug#1061082: fixed in harfbuzz 8.3.0-2 has caused the Debian Bug report #1061082, regarding libharfbuzz-dev: please add ${gir:Depends}, ${gir:Provides} to be marked as done. This means that you claim that the prob

Bug#1057964: marked as done (harfbuzz: Please update to 8.3.0)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 15:49:13 + with message-id and subject line Bug#1057964: fixed in harfbuzz 8.3.0-2 has caused the Debian Bug report #1057964, regarding harfbuzz: Please update to 8.3.0 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1031563: marked as done (polari: Could the dependency on gir1.2-soup-2.4 just be removed?)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 15:38:47 + with message-id and subject line Bug#1031563: fixed in polari 45.0-2 has caused the Debian Bug report #1031563, regarding polari: Could the dependency on gir1.2-soup-2.4 just be removed? to be marked as done. This means that you claim that the pr

Bug#1056130: marked as done (gthumb: (unused?) build-dependency on deprecated libsoup-gnome2.4-dev)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 16:05:57 +0100 with message-id <18a8835f-297f-49e4-b8aa-645ad8410...@debian.org> and subject line Re: gthumb: (unused?) build-dependency on deprecated libsoup-gnome2.4-dev has caused the Debian Bug report #1056130, regarding gthumb: (unused?) build-dependency on

Processed: closing 1060388

2024-01-20 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1060388 Bug #1060388 [sponsorship-requests] RFS: endless-sky/0.10.4-1.1 [NMU] [RC] -- space exploration, trading and combat game Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1060388: h

Bug#1059987: marked as done (FTBFS: 38 tests failed out of 39)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 13:35:09 + with message-id and subject line Bug#1059987: fixed in endless-sky 0.10.4-1 has caused the Debian Bug report #1059987, regarding FTBFS: 38 tests failed out of 39 to be marked as done. This means that you claim that the problem has been dealt with

Bug#1061104: marked as done (xtl-dev is not installed with libxsimd-dev transparently (missing Depends:))

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 12:51:15 + with message-id and subject line Bug#1061104: fixed in xsimd 11.2.0-2 has caused the Debian Bug report #1061104, regarding xtl-dev is not installed with libxsimd-dev transparently (missing Depends:) to be marked as done. This means that you clai

Bug#1060991: marked as done (tuba: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 12:36:28 + with message-id and subject line Bug#1060991: fixed in tuba 0.6.2-1 has caused the Debian Bug report #1060991, regarding tuba: FTBFS: make[1]: *** [debian/rules:16: override_dh_auto_test] Error 1 to be marked as done. This means that you claim t

Bug#1060566: marked as done (modemmanager: Please switch Build-Depends to systemd-dev)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 12:34:45 + with message-id and subject line Bug#1060566: fixed in modemmanager 1.22.0-3 has caused the Debian Bug report #1060566, regarding modemmanager: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the pr

Bug#1018339: marked as done (django-bitfield: build-depends on python3-nose or uses it for autopkgtest)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 12:07:02 + with message-id and subject line Bug#1018339: fixed in django-bitfield 2.2.0-1 has caused the Debian Bug report #1018339, regarding django-bitfield: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that y

Bug#1060889: marked as done (clamav cannot be cross-arch installed?)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 11:20:11 + with message-id and subject line Bug#1060889: fixed in clamav 1.0.4+dfsg-1 has caused the Debian Bug report #1060889, regarding clamav cannot be cross-arch installed? to be marked as done. This means that you claim that the problem has been dealt

Bug#1060559: marked as done (clamav: Please switch Build-Depends to systemd-dev)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 11:20:11 + with message-id and subject line Bug#1060559: fixed in clamav 1.0.4+dfsg-1 has caused the Debian Bug report #1060559, regarding clamav: Please switch Build-Depends to systemd-dev to be marked as done. This means that you claim that the problem ha

Bug#1059451: marked as done (opennds: CVE-2023-38313 CVE-2023-38314 CVE-2023-38315 CVE-2023-38316 CVE-2023-38320 CVE-2023-38322 CVE-2023-38324)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:34:42 + with message-id and subject line Bug#1059451: fixed in opennds 10.2.0+dfsg-1 has caused the Debian Bug report #1059451, regarding opennds: CVE-2023-38313 CVE-2023-38314 CVE-2023-38315 CVE-2023-38316 CVE-2023-38320 CVE-2023-38322 CVE-2023-38324 to

Bug#1040392: marked as done (opennds-daemon-common: broken symlink: /usr/share/man/man1/ndsctl.1.gz -> opennds.1.gz)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:34:42 + with message-id and subject line Bug#1040392: fixed in opennds 10.2.0+dfsg-1 has caused the Debian Bug report #1040392, regarding opennds-daemon-common: broken symlink: /usr/share/man/man1/ndsctl.1.gz -> opennds.1.gz to be marked as done. This m

Bug#1059452: marked as done (opennds: CVE-2023-41101 CVE-2023-41102)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:34:42 + with message-id and subject line Bug#1059452: fixed in opennds 10.2.0+dfsg-1 has caused the Debian Bug report #1059452, regarding opennds: CVE-2023-41101 CVE-2023-41102 to be marked as done. This means that you claim that the problem has been dea

Bug#1059842: marked as done (FTBFS: test fails: ZFP lib not compiled with -DBIT_STREAM_WORD_TYPE=uint8)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 11:13:46 +0100 (CET) with message-id <961716167.26479378.1705745626675.javamail.zim...@synchrotron-soleil.fr> and subject line FTBFS: test fails: ZFP lib not compiled with -DBIT_STREAM_WORD_TYPE=uint8 has caused the Debian Bug report #1059842, regarding FTBFS:

Bug#1054262: marked as done (faicd64-large_6.0.3.iso "Cannot find grub.cfg")

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:03:58 + with message-id and subject line Bug#1054262: fixed in fai 6.2~a1 has caused the Debian Bug report #1054262, regarding faicd64-large_6.0.3.iso "Cannot find grub.cfg" to be marked as done. This means that you claim that the problem has been dealt

Bug#1042499: marked as done (ocaml-duppy depends on obsolete pcre)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:05:01 + with message-id and subject line Bug#1042499: fixed in ocaml-duppy 0.9.3-2 has caused the Debian Bug report #1042499, regarding ocaml-duppy depends on obsolete pcre to be marked as done. This means that you claim that the problem has been dealt w

Bug#1041609: marked as done (fai softupdate fails in get-config-dir-svn)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:03:58 + with message-id and subject line Bug#1041609: fixed in fai 6.2~a1 has caused the Debian Bug report #1041609, regarding fai softupdate fails in get-config-dir-svn to be marked as done. This means that you claim that the problem has been dealt with

Bug#1061172: marked as done (pillow: CVE-2023-50447)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:05:22 + with message-id and subject line Bug#1061172: fixed in pillow 10.2.0-1 has caused the Debian Bug report #1061172, regarding pillow: CVE-2023-50447 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1054263: marked as done (faicd64-large_6.0.3.iso "Cannot find grub.cfg")

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:03:58 + with message-id and subject line Bug#1054263: fixed in fai 6.2~a1 has caused the Debian Bug report #1054263, regarding faicd64-large_6.0.3.iso "Cannot find grub.cfg" to be marked as done. This means that you claim that the problem has been dealt

Bug#1050383: marked as done (setup-storage confused by valid md device names)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:03:58 + with message-id and subject line Bug#1050383: fixed in fai 6.2~a1 has caused the Debian Bug report #1050383, regarding setup-storage confused by valid md device names to be marked as done. This means that you claim that the problem has been dealt

Bug#1030312: marked as done (fai-client: PACKAGES aptitude does not work anymore with fai6.0)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 10:03:58 + with message-id and subject line Bug#1030312: fixed in fai 6.2~a1 has caused the Debian Bug report #1030312, regarding fai-client: PACKAGES aptitude does not work anymore with fai6.0 to be marked as done. This means that you claim that the proble

Bug#1058040: marked as done (pymatgen: FTBFS with Python 3.12)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 09:50:10 + with message-id and subject line Bug#1058040: fixed in pymatgen 2023.06.23+dfsg1-3 has caused the Debian Bug report #1058040, regarding pymatgen: FTBFS with Python 3.12 to be marked as done. This means that you claim that the problem has been dea

Processed: src:pyocd: fails to migrate to testing for too long: triggers autopkgtest issues in valinor

2024-01-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.36.0-1 Bug #1061175 [src:pyocd] src:pyocd: fails to migrate to testing for too long: triggers autopkgtest issues in valinor Marked as fixed in versions pyocd/0.36.0-1. Bug #1061175 [src:pyocd] src:pyocd: fails to migrate to testing for too long: triggers

Bug#1056841: marked as done (pymatgen: ftbfs with cython 3.0.x)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 09:50:10 + with message-id and subject line Bug#1056841: fixed in pymatgen 2023.06.23+dfsg1-3 has caused the Debian Bug report #1056841, regarding pymatgen: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been de

Bug#1044346: marked as done (gnome-shell-extension-shortcuts: Fails to build source after successful build)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 09:49:09 + with message-id and subject line Bug#1044346: fixed in gnome-shell-extension-shortcuts 1.4.3-1~exp1 has caused the Debian Bug report #1044346, regarding gnome-shell-extension-shortcuts: Fails to build source after successful build to be marked a

Bug#1045877: marked as done (pymatgen: Fails to build source after successful build)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 09:50:10 + with message-id and subject line Bug#1045877: fixed in pymatgen 2023.06.23+dfsg1-3 has caused the Debian Bug report #1045877, regarding pymatgen: Fails to build source after successful build to be marked as done. This means that you claim that th

Processed: src:gmsh: fails to migrate to testing for too long: causes timeout of pygmsh autopkgtest on i386

2024-01-20 Thread Debian Bug Tracking System
Processing control commands: > close -1 4.11.1+ds1-1 Bug #1061174 [src:gmsh] src:gmsh: fails to migrate to testing for too long: causes timeout of pygmsh autopkgtest on i386 Marked as fixed in versions gmsh/4.11.1+ds1-1. Bug #1061174 [src:gmsh] src:gmsh: fails to migrate to testing for too long:

Bug#1032789: marked as done (please drop transitional package idle3 from src:python3-defaults)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 08:36:31 + with message-id and subject line Bug#1032789: fixed in python3-defaults 3.12.1-1 has caused the Debian Bug report #1032789, regarding please drop transitional package idle3 from src:python3-defaults to be marked as done. This means that you claim

Bug#1054813: marked as done (python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1)

2024-01-20 Thread Debian Bug Tracking System
Your message dated Sat, 20 Jan 2024 08:36:13 + with message-id and subject line Bug#1054813: fixed in python-dmidecode 3.12.3-1 has caused the Debian Bug report #1054813, regarding python-dmidecode: FTBFS: make[2]: *** [Makefile:4: test] Error 1 to be marked as done. This means that you claim