Processed: RFS: splash/3.10.1-2 [ITA] -- Visualisation tool for Smoothed Particle Hydrodynamics simulation

Processing commands for cont...@bugs.debian.org: > close 1061666 Bug #1061666 [sponsorship-requests] RFS: splash/3.10.1-2 [ITA] -- Visualisation tool for Smoothed Particle Hydrodynamics simulation Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1

Bug#1061807: marked as done (lazygal fails its autopkg tests with Python 3.12)

Your message dated Wed, 31 Jan 2024 05:35:40 + with message-id and subject line Bug#1061807: fixed in lazygal 0.10.9-1 has caused the Debian Bug report #1061807, regarding lazygal fails its autopkg tests with Python 3.12 to be marked as done. This means that you claim that the problem has bee

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

Your message dated Tue, 30 Jan 2024 23:34:15 + with message-id and subject line Bug#1018379: fixed in ipywidgets 8.1.1-2 has caused the Debian Bug report #1018379, regarding ipywidgets: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim th

Bug#1054132: marked as done (podget: line 2532: ITEM_TITLE: unbound variable)

Your message dated Tue, 30 Jan 2024 16:29:35 -0700 with message-id and subject line Fixed in podget 0.9.3-1 has caused the Debian Bug report #1054132, regarding podget: line 2532: ITEM_TITLE: unbound variable to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1054131: marked as done (podget: line 2532: ITEM_TITLE: unbound variable)

Your message dated Tue, 30 Jan 2024 16:27:48 -0700 with message-id and subject line Fixed in podget 0.9.3-1 has caused the Debian Bug report #1054131, regarding podget: line 2532: ITEM_TITLE: unbound variable to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1054130: marked as done (podget: line 2532: ITEM_TITLE: unbound variable)

Your message dated Tue, 30 Jan 2024 16:17:22 -0700 with message-id and subject line Fixed in podget 0.9.3-1 has caused the Debian Bug report #1054130, regarding podget: line 2532: ITEM_TITLE: unbound variable to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1047610: marked as done (pd-flext: Fails to build source after successful build)

Your message dated Tue, 30 Jan 2024 22:52:46 + with message-id and subject line Bug#1047610: fixed in pd-flext 0.6.3-1 has caused the Debian Bug report #1047610, regarding pd-flext: Fails to build source after successful build to be marked as done. This means that you claim that the problem h

Bug#1059970: marked as done (fitspng: autopkgtest regression in testing)

Your message dated Tue, 30 Jan 2024 21:50:20 + with message-id and subject line Bug#1059970: fixed in fitspng 2.0-2 has caused the Debian Bug report #1059970, regarding fitspng: autopkgtest regression in testing to be marked as done. This means that you claim that the problem has been dealt w

Bug#1061984: marked as done (libboinc-app7t64 and libboinc7t64 have an undeclared file conflict)

Your message dated Tue, 30 Jan 2024 21:49:43 + with message-id and subject line Bug#1061984: fixed in boinc 7.20.5+dfsg-1.2~exp2 has caused the Debian Bug report #1061984, regarding libboinc-app7t64 and libboinc7t64 have an undeclared file conflict to be marked as done. This means that you cl

Bug#1061774: marked as done (fitspng: prints warnings on zlib updates)

Your message dated Tue, 30 Jan 2024 21:50:20 + with message-id and subject line Bug#1061774: fixed in fitspng 2.0-2 has caused the Debian Bug report #1061774, regarding fitspng: prints warnings on zlib updates to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1044078: marked as done (cnvkit: FTBFS with pandas 2.0)

Your message dated Tue, 30 Jan 2024 21:34:32 + with message-id <845d1345-7923-4fd7-a075-a4843bb59...@zoho.com> and subject line Re: cnvkit and pandas 2.x has caused the Debian Bug report #1044078, regarding cnvkit: FTBFS with pandas 2.0 to be marked as done. This means that you claim that the

Bug#1061949: marked as done (elan - upcoming rust-toml update.)

Your message dated Tue, 30 Jan 2024 20:51:19 + with message-id and subject line Bug#1061949: fixed in elan 3.0.0-3 has caused the Debian Bug report #1061949, regarding elan - upcoming rust-toml update. to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1061550: marked as done (elan: creates invalid settings file on startup)

Your message dated Tue, 30 Jan 2024 20:51:19 + with message-id and subject line Bug#1061550: fixed in elan 3.0.0-3 has caused the Debian Bug report #1061550, regarding elan: creates invalid settings file on startup to be marked as done. This means that you claim that the problem has been deal

Bug#1044079: marked as done (augur: FTBFS with pandas 2.0)

Your message dated Tue, 30 Jan 2024 20:46:34 + with message-id and subject line Bug#1044079: fixed in augur 24.0.0-1 has caused the Debian Bug report #1044079, regarding augur: FTBFS with pandas 2.0 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1059104: marked as done (rust-toml: please upgrade to v0.8)

Your message dated Tue, 30 Jan 2024 19:14:02 + with message-id and subject line Bug#1059104: fixed in rust-toml 0.8.8-2 has caused the Debian Bug report #1059104, regarding rust-toml: please upgrade to v0.8 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1044053: marked as done (dials: test failure with pandas 2.0)

Your message dated Tue, 30 Jan 2024 18:56:01 + with message-id and subject line Re: Bug#1043240: transition: pandas 1.5 -> 2.1 - please upload fixes has caused the Debian Bug report #1044053, regarding dials: test failure with pandas 2.0 to be marked as done. This means that you claim that t

Bug#1061318: marked as done (device-tree-compiler ftbfs with Python 3.12 as default)

Your message dated Tue, 30 Jan 2024 17:45:53 + with message-id and subject line Bug#1061318: fixed in device-tree-compiler 1.7.0-2 has caused the Debian Bug report #1061318, regarding device-tree-compiler ftbfs with Python 3.12 as default to be marked as done. This means that you claim that t

Bug#1061312: marked as done (mypaint ftbfs with Python 3.12 as the default)

Your message dated Tue, 30 Jan 2024 17:12:30 + with message-id and subject line Bug#1061312: fixed in mypaint 2.0.1-10 has caused the Debian Bug report #1061312, regarding mypaint ftbfs with Python 3.12 as the default to be marked as done. This means that you claim that the problem has been d

Bug#1048362: marked as done (q2-taxa: Fails to build source after successful build)

Your message dated Tue, 30 Jan 2024 16:54:01 + with message-id and subject line Bug#1048362: fixed in q2-taxa 2023.9.0+dfsg-1 has caused the Debian Bug report #1048362, regarding q2-taxa: Fails to build source after successful build to be marked as done. This means that you claim that the pro

Bug#1061854: marked as done (shishi: install PAM module into /usr)

Your message dated Tue, 30 Jan 2024 16:40:49 + with message-id and subject line Bug#1061854: fixed in shishi 1.0.3-2 has caused the Debian Bug report #1061854, regarding shishi: install PAM module into /usr to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1055515: marked as done (ldc: diff for NMU version 1:1.35.0-1.1)

Your message dated Tue, 30 Jan 2024 16:23:38 + with message-id and subject line Bug#1055515: fixed in ldc 1:1.35.0-1.1 has caused the Debian Bug report #1055515, regarding ldc: diff for NMU version 1:1.35.0-1.1 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1049550: marked as done (terraphast: Fails to build binary packages again after successful build)

Your message dated Tue, 30 Jan 2024 16:25:14 + with message-id and subject line Bug#1049550: fixed in terraphast 0.0+git20200413.8af2e4c+dfsg-3 has caused the Debian Bug report #1049550, regarding terraphast: Fails to build binary packages again after successful build to be marked as done. T

Bug#1053945: marked as done (seaborn: test failure with pandas 2.1)

Your message dated Tue, 30 Jan 2024 16:09:25 + with message-id and subject line Bug#1053945: fixed in seaborn 0.13.2-1 has caused the Debian Bug report #1053945, regarding seaborn: test failure with pandas 2.1 to be marked as done. This means that you claim that the problem has been dealt wit

Processed: RFS: streamlink/6.5.1-1~bpo12+1 -- CLI for extracting video streams from various websites to a video player

Processing commands for cont...@bugs.debian.org: > close 1061819 Bug #1061819 [sponsorship-requests] RFS: streamlink/6.5.1-1~bpo12+1 -- CLI for extracting video streams from various websites to a video player Marked Bug as done > stop Stopping processing here. Please contact me if you need assis

Bug#1061948: marked as done (precious - upcoming rust-toml-update)

Your message dated Tue, 30 Jan 2024 15:38:38 + with message-id and subject line Bug#1061948: fixed in precious 0.6.0-3 has caused the Debian Bug report #1061948, regarding precious - upcoming rust-toml-update to be marked as done. This means that you claim that the problem has been dealt with

Bug#1061714: marked as done (oath-toolkit: install PAM module into /usr)

Your message dated Tue, 30 Jan 2024 15:38:30 + with message-id and subject line Bug#1061714: fixed in oath-toolkit 2.6.11-2 has caused the Debian Bug report #1061714, regarding oath-toolkit: install PAM module into /usr to be marked as done. This means that you claim that the problem has been

Bug#1045829: marked as done (q2-demux: Fails to build source after successful build)

Your message dated Tue, 30 Jan 2024 15:39:03 + with message-id and subject line Bug#1045829: fixed in q2-demux 2023.9.1+dfsg-1 has caused the Debian Bug report #1045829, regarding q2-demux: Fails to build source after successful build to be marked as done. This means that you claim that the p

Bug#1061961: marked as done (fyba: NMU diff for 64-bit time_t transition)

Your message dated Tue, 30 Jan 2024 15:35:46 + with message-id and subject line Bug#1061961: fixed in fyba 4.1.1-9~exp1 has caused the Debian Bug report #1061961, regarding fyba: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the problem has been de

Processed: your mail

Processing commands for cont...@bugs.debian.org: > close 990343 1.4.2 Bug #990343 [backintime] backintime 1.1.24 - unhandled exception There is no source info for the package 'backintime' at version '1.4.2' with architecture '' Unable to make a source version for version '1.4.2' Marked as fixed i

Processed: your mail

Processing commands for cont...@bugs.debian.org: > close 1061973 Bug #1061973 [backintime] (no subject) Marked Bug as done > close 1061975 Bug #1061975 [backintime] (no subject) Marked Bug as done > End of message, stopping processing here. Please contact me if you need assistance. -- 1061973: h

Bug#1061939: marked as done (libtag-c-dev and libtag-dev have an undeclared file conflict)

Your message dated Tue, 30 Jan 2024 15:11:42 + with message-id and subject line Bug#1061939: fixed in taglib 2.0-1~exp3 has caused the Debian Bug report #1061939, regarding libtag-c-dev and libtag-dev have an undeclared file conflict to be marked as done. This means that you claim that the pr

Bug#1061935: marked as done (please don't link against the shared libbfd library)

Your message dated Tue, 30 Jan 2024 15:07:09 + with message-id and subject line Bug#1061935: fixed in lfortran 0.30.0-3 has caused the Debian Bug report #1061935, regarding please don't link against the shared libbfd library to be marked as done. This means that you claim that the problem has

Bug#1061648: marked as done (gnat-13-x86-64-linux-gnu: needs to inherit the Conflicts from gnat-13)

Changes: gcc-13 (13.2.0-13) unstable; urgency=medium . * Update to git 20240130 from the gcc-13 branch. - Fix PR preprocessor/105608. * Fix and add dependencies for -for-build and -for-host packages. * Correct conflicts with old gnat-N versions. Closes: #1061648. * Fix some

Bug#1060275: marked as done (asterisk: log flooded with ast_translate NOTICEs: lost frame(s))

Your message dated Tue, 30 Jan 2024 14:47:30 + with message-id and subject line Bug#1060275: fixed in asterisk 1:20.6.0~dfsg+~cs6.13.40431414-2 has caused the Debian Bug report #1060275, regarding asterisk: log flooded with ast_translate NOTICEs: lost frame(s) to be marked as done. This means

Processed: your mail

Processing commands for cont...@bugs.debian.org: > close 963849 1.3.3-1 Bug #963849 [backintime-qt] backintime-qt: GUI fails to launch Marked as fixed in versions backintime/1.3.3-1. Bug #963849 [backintime-qt] backintime-qt: GUI fails to launch Marked Bug as done > End of message, stopping proces

Bug#1061522: marked as done (atril: CVE-2023-52076)

Your message dated Tue, 30 Jan 2024 13:34:28 + with message-id and subject line Bug#1061522: fixed in atril 1.26.2-1 has caused the Debian Bug report #1061522, regarding atril: CVE-2023-52076 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

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

Your message dated Tue, 30 Jan 2024 12:30:16 + with message-id and subject line Bug#1060948: fixed in sqlreduce 1.3-1 has caused the Debian Bug report #1060948, regarding sqlreduce: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p "3.12 3.11" returned exit code 1

Bug#1061768: marked as done (vulkan-loader: new upstream release 1.3.275.0)

Your message dated Tue, 30 Jan 2024 11:58:58 + with message-id and subject line Bug#1061768: fixed in vulkan-loader 1.3.275.0-1 has caused the Debian Bug report #1061768, regarding vulkan-loader: new upstream release 1.3.275.0 to be marked as done. This means that you claim that the problem h

Bug#1061756: marked as done (python-twilio ftbfs with Python 3.12 as default)

Your message dated Tue, 30 Jan 2024 10:53:54 +0100 with message-id and subject line Re: python-twilio ftbfs with Python 3.12 as default has caused the Debian Bug report #1061756, regarding python-twilio ftbfs with Python 3.12 as default to be marked as done. This means that you claim that the pr

Bug#1061615: marked as done (src:nanobind: unsatisfied build dependency in testing: python3-torch)

Your message dated Tue, 30 Jan 2024 09:35:08 + with message-id and subject line Bug#1061615: fixed in nanobind 1.8.0-4 has caused the Debian Bug report #1061615, regarding src:nanobind: unsatisfied build dependency in testing: python3-torch to be marked as done. This means that you claim that

Bug#1061931: marked as done (biosquid: NMU diff for 64-bit time_t transition)

Your message dated Tue, 30 Jan 2024 08:34:14 + with message-id and subject line Bug#1061931: fixed in biosquid 1.9g+cvs20050121-14 has caused the Debian Bug report #1061931, regarding biosquid: NMU diff for 64-bit time_t transition to be marked as done. This means that you claim that the prob