Bug#1060100: marked as done (r-cran-rstanarm: FTBFS: Error: segfault from C stack overflow)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 4 Feb 2024 08:10:23 +0100 with message-id and subject line Problem solved in new upstream version has caused the Debian Bug report #1060100, regarding r-cran-rstanarm: FTBFS: Error: segfault from C stack overflow to be marked as done. This means that you claim that the pro

Bug#1060933: marked as done (valinor: FTBFS: AssertionError: 1 != 0)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 04 Feb 2024 06:05:07 + with message-id and subject line Bug#1060933: fixed in valinor 1.1.4-8 has caused the Debian Bug report #1060933, regarding valinor: FTBFS: AssertionError: 1 != 0 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1047934: marked as done (libimage-png-libpng-perl: Fails to build source after successful build)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 04 Feb 2024 04:52:48 + with message-id and subject line Bug#1047934: fixed in libimage-png-libpng-perl 0.58-1 has caused the Debian Bug report #1047934, regarding libimage-png-libpng-perl: Fails to build source after successful build to be marked as done. This means th

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

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 4 Feb 2024 15:53:54 +1100 with message-id <67013ce0-fbbd-43a9-ae55-f8f64421b59b@undef.tools> and subject line Re: Bug#1061330: calamares: identified for time_t transition but no ABI in shlibs has caused the Debian Bug report #1061330, regarding calamares: identified for tim

Bug#1048118: marked as done (libyaml-libyaml-perl: Fails to build source after successful build)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 04 Feb 2024 03:31:23 + with message-id and subject line Bug#1048118: fixed in libyaml-libyaml-perl 0.89+ds-1 has caused the Debian Bug report #1048118, regarding libyaml-libyaml-perl: Fails to build source after successful build to be marked as done. This means that yo

Bug#1051724: marked as done (zbar: CVE-2023-40889 CVE-2023-40890)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 04 Feb 2024 00:47:08 + with message-id and subject line Bug#1051724: fixed in zbar 0.23.92-7+deb12u1 has caused the Debian Bug report #1051724, regarding zbar: CVE-2023-40889 CVE-2023-40890 to be marked as done. This means that you claim that the problem has been dealt

Bug#1051724: marked as done (zbar: CVE-2023-40889 CVE-2023-40890)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 04 Feb 2024 00:47:43 + with message-id and subject line Bug#1051724: fixed in zbar 0.23.90-1+deb11u1 has caused the Debian Bug report #1051724, regarding zbar: CVE-2023-40889 CVE-2023-40890 to be marked as done. This means that you claim that the problem has been dealt

Bug#1050606: marked as done (find: ‘/lib/systemd/system-sleep’: No such file or directory)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sun, 04 Feb 2024 00:47:08 + with message-id and subject line Bug#1050606: fixed in cryptsetup 2:2.6.1-4~deb12u2 has caused the Debian Bug report #1050606, regarding find: ‘/lib/systemd/system-sleep’: No such file or directory to be marked as done. This means that you claim

Processed: closing 1062554

2024-02-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1062554 Bug #1062554 [cups-browsed] cups-browsed is not detecting any network printers Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1062554: https://bugs.debian.org/cgi-bin/bugreport.cg

Bug#781745: marked as done (libwvstreams4.6-extras: Not handling whitespace in x509 extensions)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 23:35:49 + with message-id and subject line Bug#781745: fixed in wvstreams 4.6.1-17 has caused the Debian Bug report #781745, regarding libwvstreams4.6-extras: Not handling whitespace in x509 extensions to be marked as done. This means that you claim that t

Bug#1056886: marked as done (scalene: ftbfs with cython 3.0.x)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 23:34:32 + with message-id and subject line Bug#1056886: fixed in scalene 1.5.31.1-1 has caused the Debian Bug report #1056886, regarding scalene: ftbfs with cython 3.0.x to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1055725: marked as done (scalene ftbfs with Python 3.12)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 23:34:32 + with message-id and subject line Bug#1055725: fixed in scalene 1.5.31.1-1 has caused the Debian Bug report #1055725, regarding scalene ftbfs with Python 3.12 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1046700: marked as done (wvstreams: Fails to build source after successful build)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 23:35:49 + with message-id and subject line Bug#1046700: fixed in wvstreams 4.6.1-17 has caused the Debian Bug report #1046700, regarding wvstreams: Fails to build source after successful build to be marked as done. This means that you claim that the proble

Bug#1037852: marked as done (scalene: ftbfs with GCC-13)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 23:34:32 + with message-id and subject line Bug#1037852: fixed in scalene 1.5.31.1-1 has caused the Debian Bug report #1037852, regarding scalene: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1058229: marked as done (liac-arff: FTBFS: AttributeError: 'TestEncodeComment' object has no attribute 'assertRaisesRegexp'. Did you mean: 'assertRaisesRegex'?)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 23:19:17 + with message-id and subject line Bug#1058229: fixed in liac-arff 2.5.0-5 has caused the Debian Bug report #1058229, regarding liac-arff: FTBFS: AttributeError: 'TestEncodeComment' object has no attribute 'assertRaisesRegexp'. Did you mean: 'asser

Bug#1061747: marked as done (liac-arff ftbfs with Python 3.12 as default)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 23:19:17 + with message-id and subject line Bug#1061747: fixed in liac-arff 2.5.0-5 has caused the Debian Bug report #1061747, regarding liac-arff ftbfs with Python 3.12 as default to be marked as done. This means that you claim that the problem has been de

Bug#1062803: marked as done (libsigrok4t64: improper /usr-move mitigation)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 22:54:06 + with message-id and subject line Bug#1062803: fixed in libtirpc 1.3.4+ds-1.1~exp2 has caused the Debian Bug report #1062803, regarding libsigrok4t64: improper /usr-move mitigation to be marked as done. This means that you claim that the problem h

Bug#1044076: marked as done (influxdb-python: FTBFS with pandas 2.0)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 22:53:56 + with message-id and subject line Bug#1044076: fixed in influxdb-python 5.3.1-6 has caused the Debian Bug report #1044076, regarding influxdb-python: FTBFS with pandas 2.0 to be marked as done. This means that you claim that the problem has been d

Bug#1062704: marked as done (python-certvalidator: Please make it team-maintained)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 22:15:46 + with message-id and subject line Bug#1062704: fixed in python-certvalidator 0.11.1-4 has caused the Debian Bug report #1062704, regarding python-certvalidator: Please make it team-maintained to be marked as done. This means that you claim that th

Bug#1062801: marked as done (libtirpc3t64: ineffective /usr-move mitigation)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 13:31:16 -0800 with message-id and subject line Re: libtirpc: NMU diff for 64-bit time_t transition has caused the Debian Bug report #1062801, regarding libtirpc3t64: ineffective /usr-move mitigation to be marked as done. This means that you claim that the probl

Bug#1053256: marked as done (ITP: bypass-paywalls-firefox-clean -- Firefox browser plugin to bypass various paywalls)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 15:29:21 -0500 with message-id <5be62f98-6407-4d87-96fa-973471904...@queued.net> and subject line Re: ITP: bypass-paywalls-firefox-clean -- Firefox browser plugin to bypass various paywalls has caused the Debian Bug report #1053256, regarding ITP: bypass-paywalls

Bug#787741: marked as done ([empathy-skype] meta-contacts does not work with skype)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 21:09:06 +0100 with message-id <05cc2a8f-32bc-42c9-88b9-d89632698...@debian.org> and subject line Re: [empathy-skype] meta-contacts does not work with skype has caused the Debian Bug report #787741, regarding [empathy-skype] meta-contacts does not work with skype

Bug#712132: marked as done (pidgin-skype: Migration pidgin-skype with empathy 3.4.2.3-3)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 20:59:15 +0100 with message-id and subject line Re: pidgin-skype: Migration pidgin-skype with empathy 3.4.2.3-3 has caused the Debian Bug report #712132, regarding pidgin-skype: Migration pidgin-skype with empathy 3.4.2.3-3 to be marked as done. This means that

Processed: RFS: compton/1-1+deb11u1 [ITA] -- compositor for X11, based on xcompmgr

2024-02-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1061877 Bug #1061877 [sponsorship-requests] RFS: compton/1-1+deb11u1 [ITA] -- compositor for X11, based on xcompmgr Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1061877: https://bugs.deb

Bug#960779: marked as done (ITA: compton -- compositor for X11, based on xcompmgr)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 18:32:38 + with message-id and subject line Bug#960779: fixed in compton 1-1+deb11u1 has caused the Debian Bug report #960779, regarding ITA: compton -- compositor for X11, based on xcompmgr to be marked as done. This means that you claim that the problem h

Bug#1061558: marked as done (compton: Recommends 'picom', another X11 compositor.)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 18:32:38 + with message-id and subject line Bug#1061558: fixed in compton 1-1+deb11u1 has caused the Debian Bug report #1061558, regarding compton: Recommends 'picom', another X11 compositor. to be marked as done. This means that you claim that the problem

Bug#960779: marked as done (ITA: compton -- compositor for X11, based on xcompmgr)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 18:32:08 + with message-id and subject line Bug#960779: fixed in compton 1-1+deb12u1 has caused the Debian Bug report #960779, regarding ITA: compton -- compositor for X11, based on xcompmgr to be marked as done. This means that you claim that the problem h

Bug#1061558: marked as done (compton: Recommends 'picom', another X11 compositor.)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 18:32:08 + with message-id and subject line Bug#1061558: fixed in compton 1-1+deb12u1 has caused the Debian Bug report #1061558, regarding compton: Recommends 'picom', another X11 compositor. to be marked as done. This means that you claim that the problem

Bug#1061647: marked as done (libgccjit-14-doc: missing Breaks+Replaces: libgccjit-13-doc (and maybe more old versions))

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 18:48:52 +0100 with message-id <9a4e4be1-3645-4017-b267-bb9a6df00...@debian.org> and subject line fixed has caused the Debian Bug report #1061647, regarding libgccjit-14-doc: missing Breaks+Replaces: libgccjit-13-doc (and maybe more old versions) to be marked as

Bug#1060751: marked as done (atril: CVE-2023-51698)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:32:08 + with message-id and subject line Bug#1060751: fixed in atril 1.26.0-2+deb12u2 has caused the Debian Bug report #1060751, regarding atril: CVE-2023-51698 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1061582: marked as done (openssl: CVE-2024-0727)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:20:40 + with message-id and subject line Bug#1061582: fixed in openssl 3.2.1-1 has caused the Debian Bug report #1061582, regarding openssl: CVE-2024-0727 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1061582: marked as done (openssl: CVE-2024-0727)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:20:03 + with message-id and subject line Bug#1061582: fixed in openssl 3.1.5-1 has caused the Debian Bug report #1061582, regarding openssl: CVE-2024-0727 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1060858: marked as done (openssl: CVE-2023-6237: Checking excessively long invalid RSA public keys may take a long time)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:20:40 + with message-id and subject line Bug#1060858: fixed in openssl 3.2.1-1 has caused the Debian Bug report #1060858, regarding openssl: CVE-2023-6237: Checking excessively long invalid RSA public keys may take a long time to be marked as done. This

Bug#1060858: marked as done (openssl: CVE-2023-6237: Checking excessively long invalid RSA public keys may take a long time)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:20:03 + with message-id and subject line Bug#1060858: fixed in openssl 3.1.5-1 has caused the Debian Bug report #1060858, regarding openssl: CVE-2023-6237: Checking excessively long invalid RSA public keys may take a long time to be marked as done. This

Bug#1060347: marked as done (openssl: CVE-2023-6129)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:20:40 + with message-id and subject line Bug#1060347: fixed in openssl 3.2.1-1 has caused the Debian Bug report #1060347, regarding openssl: CVE-2023-6129 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1060347: marked as done (openssl: CVE-2023-6129)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:20:03 + with message-id and subject line Bug#1060347: fixed in openssl 3.1.5-1 has caused the Debian Bug report #1060347, regarding openssl: CVE-2023-6129 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1055877: marked as done (ndcube: FTBFS in bookworm: leap-second file is expired)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 17:04:01 + with message-id and subject line Bug#1055877: fixed in ndcube 2.2.0-1 has caused the Debian Bug report #1055877, regarding ndcube: FTBFS in bookworm: leap-second file is expired to be marked as done. This means that you claim that the problem has

Bug#1055892: marked as done (sunpy: FTBFS in bookworm: leap-second file is expired.)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 16:49:22 + with message-id and subject line Bug#1055892: fixed in sunpy 5.1.1-1 has caused the Debian Bug report #1055892, regarding sunpy: FTBFS in bookworm: leap-second file is expired. to be marked as done. This means that you claim that the problem has

Bug#1062813: marked as done (lfortran fails both autopkg tests)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 16:49:06 + with message-id and subject line Bug#1062813: fixed in lfortran 0.30.0-4 has caused the Debian Bug report #1062813, regarding lfortran fails both autopkg tests to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1056765: marked as done (gcc-9: Remove references to obsolete dpkg m32r and tilegx arches)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 14:38:41 + with message-id and subject line Bug#1056765: fixed in gcc-9 9.5.0-5 has caused the Debian Bug report #1056765, regarding gcc-9: Remove references to obsolete dpkg m32r and tilegx arches to be marked as done. This means that you claim that the pr

Processed: RFS: dpkg-dev-el/37.11 [RC] [Team] -- Emacs helpers specific to Debian development

2024-02-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1061653 Bug #1061653 [sponsorship-requests] RFS: dpkg-dev-el/37.11 [RC] [Team] -- Emacs helpers specific to Debian development Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1061653: https

Bug#1055152: marked as done (ca-certificates: Certificates from Sectigo Limited are not trusted)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 12:50:56 +0100 with message-id and subject line Re: Bug#1055152: ca-certificates: Certificates from Sectigo Limited are not trusted has caused the Debian Bug report #1055152, regarding ca-certificates: Certificates from Sectigo Limited are not trusted to be mark

Bug#1062716: marked as done (update-alternatives: error: alternative path /bin/mt-gnu doesn't exist)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 11:22:29 +0100 with message-id <20240203102229.ga2546...@subdivi.de> and subject line Re: Bug#1062716: update-alternatives: error: alternative path /bin/mt-gnu doesn't exist has caused the Debian Bug report #1062716, regarding update-alternatives: error: alternat

Processed: dup

2024-02-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1060690 Bug #1060690 [wnpp] ITP: Chatterino Chat client twitch.tv Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1060690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1060690 Debian Bu

Processed: src:mumble: fails to migrate to testing for too long: autopkgtest failure

2024-02-03 Thread Debian Bug Tracking System
Processing control commands: > close -1 1.5.517-1 Bug #1062798 [src:mumble] src:mumble: fails to migrate to testing for too long: autopkgtest failure Marked as fixed in versions mumble/1.5.517-1. Bug #1062798 [src:mumble] src:mumble: fails to migrate to testing for too long: autopkgtest failure

Processed: src:yt-dlp: fails to migrate to testing for too long: autopkgtest regression

2024-02-03 Thread Debian Bug Tracking System
Processing control commands: > close -1 2023.12.30-1 Bug #1062797 [src:yt-dlp] src:yt-dlp: fails to migrate to testing for too long: autopkgtest regression Marked as fixed in versions yt-dlp/2023.12.30-1. Bug #1062797 [src:yt-dlp] src:yt-dlp: fails to migrate to testing for too long: autopkgtest

Processed: src:ruby-re2: fails to migrate to testing for too long: FTBFS on armel

2024-02-03 Thread Debian Bug Tracking System
Processing control commands: > close -1 2.7.0-1 Bug #1062796 [src:ruby-re2] src:ruby-re2: fails to migrate to testing for too long: FTBFS on armel Marked as fixed in versions ruby-re2/2.7.0-1. Bug #1062796 [src:ruby-re2] src:ruby-re2: fails to migrate to testing for too long: FTBFS on armel Mark

Bug#1047518: marked as done (iraf-fitsutil: Fails to build source after successful build)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 09:49:08 + with message-id and subject line Bug#1047518: fixed in iraf-fitsutil 2018.07.06-6 has caused the Debian Bug report #1047518, regarding iraf-fitsutil: Fails to build source after successful build to be marked as done. This means that you claim tha

Bug#1047102: marked as done (iraf-mscred: Fails to build source after successful build)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 09:49:20 + with message-id and subject line Bug#1047102: fixed in iraf-mscred 5.05+2018.07.09-3 has caused the Debian Bug report #1047102, regarding iraf-mscred: Fails to build source after successful build to be marked as done. This means that you claim th

Bug#1046925: marked as done (iraf-sptable: Fails to build source after successful build)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 09:49:47 + with message-id and subject line Bug#1046925: fixed in iraf-sptable 1.0~pre20180612-3 has caused the Debian Bug report #1046925, regarding iraf-sptable: Fails to build source after successful build to be marked as done. This means that you claim

Bug#1045926: marked as done (iraf-rvsao: Fails to build source after successful build)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 09:49:31 + with message-id and subject line Bug#1045926: fixed in iraf-rvsao 2.8.5-2 has caused the Debian Bug report #1045926, regarding iraf-rvsao: Fails to build source after successful build to be marked as done. This means that you claim that the probl

Bug#1061650: marked as done (elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory, debian-bug)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 03 Feb 2024 08:34:39 + with message-id and subject line Bug#1061650: fixed in dpkg-dev-el 37.11 has caused the Debian Bug report #1061650, regarding elpa-dpkg-dev-el: fails to install: debian-bts-control.el:85:2: Error: Cannot open load file: No such file or directory,

Bug#1059675: marked as done (rust-ahash - autopkgtest failure on s390x.)

2024-02-03 Thread Debian Bug Tracking System
Your message dated Sat, 3 Feb 2024 08:11:53 + with message-id <73e06b0c-b0d9-4752-9bba-3c4498bde...@debian.org> and subject line rust-ahash - autopkgtest failure on s390x. has caused the Debian Bug report #1059675, regarding rust-ahash - autopkgtest failure on s390x. to be marked as done. This