Bug#1059976: marked as done (pulseaudio: Please move from liblircclient-dev to liblirc-dev)

Your message dated Fri, 05 Jan 2024 16:19:44 + with message-id and subject line Bug#1059976: fixed in pulseaudio 16.1+dfsg1-3 has caused the Debian Bug report #1059976, regarding pulseaudio: Please move from liblircclient-dev to liblirc-dev to be marked as done. This means that you claim

Bug#1032339: marked as done (pulseaudio: D-Bus policy is installed in /etc instead of /usr)

Your message dated Fri, 05 Jan 2024 16:19:44 + with message-id and subject line Bug#1032339: fixed in pulseaudio 16.1+dfsg1-3 has caused the Debian Bug report #1032339, regarding pulseaudio: D-Bus policy is installed in /etc instead of /usr to be marked as done. This means that you claim

Bug#992042: marked as done (please update to the last release 0.9.6)

Your message dated Fri, 5 Jan 2024 17:02:37 +0100 with message-id <7e443155-f235-4e5a-83dc-0fb37976a...@debian.org> and subject line Re: please update to the last release 0.9.6 has caused the Debian Bug report #992042, regarding please update to the last release 0.9.6 to be marked as done. This

Bug#1059947: marked as done (cnvkit: please remove extraneous build-dep on python3-future)

Your message dated Fri, 05 Jan 2024 16:04:21 + with message-id and subject line Bug#1059947: fixed in cnvkit 0.9.10-1 has caused the Debian Bug report #1059947, regarding cnvkit: please remove extraneous build-dep on python3-future to be marked as done. This means that you claim that the

Bug#904602: marked as done (pulseaudio-module-bluetooth: please backport a2dp sync fix from v12 to stretch)

Your message dated Fri, 5 Jan 2024 10:49:12 -0500 with message-id and subject line Re: Bug#904602: pulseaudio-module-bluetooth: please backport a2dp sync fix from v12 to stretch has caused the Debian Bug report #904602, regarding pulseaudio-module-bluetooth: please backport a2dp sync fix from

Bug#1059714: marked as done (spaced: packaging help likely needed)

Your message dated Fri, 05 Jan 2024 15:09:18 + with message-id and subject line Bug#1059714: fixed in spaced 1.2.0-201605+dfsg-4 has caused the Debian Bug report #1059714, regarding spaced: packaging help likely needed to be marked as done. This means that you claim that the problem has been

Bug#1059959: marked as done (sub...@bugs.debian.org)

Your message dated Fri, 5 Jan 2024 21:52:47 +0700 with message-id <7632d702-6d21-418d-9d85-e939548b2...@gmail.com> and subject line [xmake] Add loong64 support has caused the Debian Bug report #1059959, regarding sub...@bugs.debian.org to be marked as done. This means that you claim that the

Bug#1054342: marked as done (ITP: g-golf -- Guile Object Library for GNOME)

Your message dated Fri, 05 Jan 2024 14:10:11 + with message-id and subject line Bug#1054342: fixed in g-golf 0.8.0~rc1-1 has caused the Debian Bug report #1054342, regarding ITP: g-golf -- Guile Object Library for GNOME to be marked as done. This means that you claim that the problem has

Bug#1017587: marked as done (ITP: fheroes2 -- free remake of Heroes of Might and Magic II game engine)

Your message dated Fri, 05 Jan 2024 14:10:11 + with message-id and subject line Bug#1017587: fixed in fheroes2 1.0.9+dfsg-1 has caused the Debian Bug report #1017587, regarding ITP: fheroes2 -- free remake of Heroes of Might and Magic II game engine to be marked as done. This means that you

Bug#1060007: marked as done (mariadb: FTBFS on riscv64: tries to uses rdcycle, privileged since kernel 6.6)

Your message dated Fri, 05 Jan 2024 13:40:13 + with message-id and subject line Bug#1060007: fixed in mariadb 1:10.11.6-2 has caused the Debian Bug report #1060007, regarding mariadb: FTBFS on riscv64: tries to uses rdcycle, privileged since kernel 6.6 to be marked as done. This means that

Bug#1059904: marked as done (mariadb autopkgtest "upstream" is flaky, time sink)

Your message dated Fri, 05 Jan 2024 13:40:13 + with message-id and subject line Bug#1059904: fixed in mariadb 1:10.11.6-2 has caused the Debian Bug report #1059904, regarding mariadb autopkgtest "upstream" is flaky, time sink to be marked as done. This means that you claim that the problem

Bug#1053970: marked as done (python3-pylast: please upgrade to 5.2.0 and remove hardcoded python3-six dependency)

Your message dated Fri, 05 Jan 2024 13:06:04 + with message-id and subject line Bug#1053970: fixed in pylast 5.2.0-1 has caused the Debian Bug report #1053970, regarding python3-pylast: please upgrade to 5.2.0 and remove hardcoded python3-six dependency to be marked as done. This means that

Bug#995838: marked as done (RM: condor -- RoM; unmaintained, many RC bugs, toolchain issues (GCC9/Python2))

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#995838: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #995838, regarding RM: condor -- RoM; unmaintained, many RC bugs, toolchain issues (GCC9/Python2) to be marked as done. This means that

Bug#982050: marked as done (There are fresh upstream releases (8.9.11 ATM) which address security and other issues)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#982050: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #982050, regarding There are fresh upstream releases (8.9.11 ATM) which address security and other issues to be marked as done. This

Bug#966726: marked as done (condor: Unversioned Python removal in sid/bullseye)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#966726: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #966726, regarding condor: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#963777: marked as done (condor: CVE-2019-18823)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#963777: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #963777, regarding condor: CVE-2019-18823 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#936323: marked as done (condor: Python2 removal in sid/bullseye)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#936323: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #936323, regarding condor: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#925657: marked as done (condor: ftbfs with GCC-9)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#925657: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #925657, regarding condor: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#671467: marked as done (CMake setup too fragile/restrictive for OS derivatives)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#671467: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #671467, regarding CMake setup too fragile/restrictive for OS derivatives to be marked as done. This means that you claim that the

Bug#1008634: marked as done (condor: CVE-2022-26110 / HTCONDOR-2022-0003)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1008634: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1008634, regarding condor: CVE-2022-26110 / HTCONDOR-2022-0003 to be marked as done. This means that you claim that the problem has

Bug#1036393: marked as done (ITP: gtksheet -- GTK+3 GtkSheet widget)

Your message dated Fri, 05 Jan 2024 13:00:13 + with message-id and subject line Bug#1036393: fixed in gtksheet 4.3.12+dfsg-1 has caused the Debian Bug report #1036393, regarding ITP: gtksheet -- GTK+3 GtkSheet widget to be marked as done. This means that you claim that the problem has been

Bug#1002540: marked as done (condor: CVE-2021-45101)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1002540: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1002540, regarding condor: CVE-2021-45101 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1000130: marked as done (condor: depends on obsolete pcre3 library)

Your message dated Fri, 05 Jan 2024 13:00:12 + with message-id and subject line Bug#1000130: fixed in condor 23.2.0+dfsg-1 has caused the Debian Bug report #1000130, regarding condor: depends on obsolete pcre3 library to be marked as done. This means that you claim that the problem has been

Bug#152295: marked as done (python-pygresql: Two problems with python and postgresql:)

Your message dated Fri, 05 Jan 2024 12:17:48 + with message-id <3c94abf3-3752-43b7-9642-4b0d9a41a...@dalerichards.net> and subject line Re: python-pygresql: Two problems with python and postgresql has caused the Debian Bug report #152295, regarding python-pygresql: Two problems with python and

Bug#318428: marked as done (python-pygresql: handling of datetime values)

Your message dated Fri, 05 Jan 2024 12:16:16 + with message-id and subject line Re: python-pygresql: handling of datetime values has caused the Debian Bug report #318428, regarding python-pygresql: handling of datetime values to be marked as done. This means that you claim that the problem

Bug#143159: marked as done (python-pygresql: pygresql raises the wrong exception type)

Your message dated Fri, 05 Jan 2024 12:13:45 + with message-id <3493fb7b-6954-46a2-b6df-74a8ee287...@dalerichards.net> and subject line Re: python-pygresql: pygresql raises the wrong exception type has caused the Debian Bug report #143159, regarding python-pygresql: pygresql raises the wrong

Bug#1056031: marked as done (rust-rstest-test: autopkgtest failure)

Your message dated Fri, 5 Jan 2024 07:11:06 -0500 with message-id and subject line Fixed in 0.11.0-2 has caused the Debian Bug report #1056031, regarding rust-rstest-test: autopkgtest failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1053971: marked as done (python-absl: please package v2.0 and add a d/watch file)

Your message dated Fri, 05 Jan 2024 11:50:36 + with message-id and subject line Bug#1053971: fixed in python-absl 2.0.0-1 has caused the Debian Bug report #1053971, regarding python-absl: please package v2.0 and add a d/watch file to be marked as done. This means that you claim that the

Bug#1059544: marked as done (libpipewire-0.3-modules-x11: package requires libcanberra-pulse be installed)

Your message dated Fri, 05 Jan 2024 11:35:12 + with message-id and subject line Bug#1059544: fixed in pipewire 1.0.0-3 has caused the Debian Bug report #1059544, regarding libpipewire-0.3-modules-x11: package requires libcanberra-pulse be installed to be marked as done. This means that you

Bug#1043650: marked as done (bepasty: Fails to build source after successful build)

Your message dated Fri, 05 Jan 2024 10:49:11 + with message-id and subject line Bug#1043650: fixed in bepasty 1.2.0-1 has caused the Debian Bug report #1043650, regarding bepasty: Fails to build source after successful build to be marked as done. This means that you claim that the problem

Bug#1041814: marked as done (python-mechanicalsoup: CVE-2023-34457)

Your message dated Fri, 05 Jan 2024 10:50:50 + with message-id and subject line Bug#1041814: fixed in python-mechanicalsoup 1.3.0-1 has caused the Debian Bug report #1041814, regarding python-mechanicalsoup: CVE-2023-34457 to be marked as done. This means that you claim that the problem has

Bug#1040429: marked as done (python3-mechanicalsoup: please package new version 1.3.0 ...)

Your message dated Fri, 05 Jan 2024 10:50:50 + with message-id and subject line Bug#1040429: fixed in python-mechanicalsoup 1.3.0-1 has caused the Debian Bug report #1040429, regarding python3-mechanicalsoup: please package new version 1.3.0 ... to be marked as done. This means that you

Processed: closing 1060047

Processing commands for cont...@bugs.debian.org: > close 1060047 Bug #1060047 [safinaskar-fghklkk] safinaskar-fghklkk: lll Warning: Unknown package 'safinaskar-fghklkk' Marked Bug as done Warning: Unknown package 'safinaskar-fghklkk' > thanks Stopping processing here. Please contact me if you

Processed: closing 1060046

Processing commands for cont...@bugs.debian.org: > close 1060046 Bug #1060046 [safinaskar-jhgbfdrft] safinaskar-jhgbfdrft: l Warning: Unknown package 'safinaskar-jhgbfdrft' Marked Bug as done Warning: Unknown package 'safinaskar-jhgbfdrft' > thanks Stopping processing here. Please contact me

Bug#1060030: marked as done (xsar: Please drop python-setuptools-scm-git-archive from b-deps)

Your message dated Fri, 05 Jan 2024 10:36:10 + with message-id and subject line Bug#1060030: fixed in xsar 2023.09.0-2 has caused the Debian Bug report #1060030, regarding xsar: Please drop python-setuptools-scm-git-archive from b-deps to be marked as done. This means that you claim that the

Bug#1052976: marked as done (Update debian/copyright with upstream's 2.0.0 AGPL->MIT change)

Your message dated Fri, 5 Jan 2024 12:24:20 +0200 with message-id and subject line Re: Bug#1052976: Update debian/copyright with upstream's 2.0.0 AGPL->MIT change has caused the Debian Bug report #1052976, regarding Update debian/copyright with upstream's 2.0.0 AGPL->MIT change to be marked as

Bug#1051988: marked as done (civicrm-common: Not compatible with symfony 6)

Your message dated Fri, 05 Jan 2024 10:06:15 + with message-id and subject line Bug#1051988: fixed in civicrm 5.68.1+dfsg1-1 has caused the Debian Bug report #1051988, regarding civicrm-common: Not compatible with symfony 6 to be marked as done. This means that you claim that the problem has

Bug#1036284: marked as done (civicrm: CVE-2023-28115)

Your message dated Fri, 05 Jan 2024 10:06:14 + with message-id and subject line Bug#1036284: fixed in civicrm 5.68.1+dfsg1-1 has caused the Debian Bug report #1036284, regarding civicrm: CVE-2023-28115 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1036695: marked as done (civicrm: CVE-2023-25440)

Your message dated Fri, 05 Jan 2024 10:06:15 + with message-id and subject line Bug#1036695: fixed in civicrm 5.68.1+dfsg1-1 has caused the Debian Bug report #1036695, regarding civicrm: CVE-2023-25440 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1060041: marked as done (Is the python3-objgraph dependency too much)

Your message dated Fri, 05 Jan 2024 09:49:13 + with message-id and subject line Bug#1060041: fixed in cherrypy3 18.9.0-2 has caused the Debian Bug report #1060041, regarding Is the python3-objgraph dependency too much to be marked as done. This means that you claim that the problem has been

Bug#1060051: marked as done (linux-image-6.6-librem5: Lots of modem disconnection)

Your message dated Fri, 05 Jan 2024 10:34:17 +0100 with message-id <76d1c04100a11b71e22c2c4a5ef02ca8a8427eba.ca...@43-1.org> and subject line Re: linux-image-6.6-librem5: Lots of modem disconnection has caused the Debian Bug report #1060051, regarding linux-image-6.6-librem5: Lots of modem

Bug#1059971: marked as done (libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-1)

Your message dated Fri, 05 Jan 2024 09:36:39 + with message-id and subject line Bug#1059971: fixed in mesa 23.3.2-2 has caused the Debian Bug report #1059971, regarding libgl1-mesa-dri: X doesn't start after mesa upgrade from 23.2.1-1 to 23.3.2-1 to be marked as done. This means that you

Bug#1060017: marked as done (xvfb: Failed to start)

Your message dated Fri, 05 Jan 2024 09:36:39 + with message-id and subject line Bug#1060017: fixed in mesa 23.3.2-2 has caused the Debian Bug report #1060017, regarding xvfb: Failed to start to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1058914: marked as done (RFS: budgie-session/0.9-1 [ITP] -- Budgie Session Manager)

Your message dated Fri, 5 Jan 2024 10:02:20 +0100 with message-id <9989f8fb-0f80-41db-8b7a-1dc2a49d6...@debian.org> and subject line Re: budgie-session has caused the Debian Bug report #1058914, regarding RFS: budgie-session/0.9-1 [ITP] -- Budgie Session Manager to be marked as done. This means

Bug#612193: marked as done (ps2pdf (and thus gs) has very useless and misleading error message )

Your message dated Fri, 05 Jan 2024 01:01:13 -0600 with message-id <15204546.uLZWGnKmhe@riemann> and subject line Re: ps2pdf (and thus gs) has very useless and misleading error message has caused the Debian Bug report #612193, regarding ps2pdf (and thus gs) has very useless and misleading error

Bug#1058108: marked as done (pokrok: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?)

Your message dated Fri, 05 Jan 2024 08:55:44 + with message-id and subject line Bug#1058108: fixed in pokrok 0.2.0-5 has caused the Debian Bug report #1058108, regarding pokrok: FTBFS: AttributeError: module 'configparser' has no attribute 'SafeConfigParser'. Did you mean: 'RawConfigParser'?

Bug#995735: marked as done (dask.distributed: autopkgtest sometimes times out on ci.d.n worker since dask migrated)

Your message dated Fri, 05 Jan 2024 08:34:31 + with message-id and subject line Bug#995735: fixed in dask.distributed 2023.12.1+ds-3 has caused the Debian Bug report #995735, regarding dask.distributed: autopkgtest sometimes times out on ci.d.n worker since dask migrated to be marked as

Bug#988675: marked as done (python-distributed-doc: broken symlink: /usr/share/doc/python-distributed-doc/html/_static/js/html5shiv.min.js -> /sphinx_rtd_theme/static/js/html5shiv.min.js)

Your message dated Fri, 05 Jan 2024 08:34:31 + with message-id and subject line Bug#988675: fixed in dask.distributed 2023.12.1+ds-3 has caused the Debian Bug report #988675, regarding python-distributed-doc: broken symlink:

Bug#905540: marked as done (dask.distributed: autopkgtest fails with python3.7 in supported versions)

Your message dated Fri, 05 Jan 2024 08:34:31 + with message-id and subject line Bug#905540: fixed in dask.distributed 2023.12.1+ds-3 has caused the Debian Bug report #905540, regarding dask.distributed: autopkgtest fails with python3.7 in supported versions to be marked as done. This means

Bug#904944: marked as done (joblib/0.12.1-1 appears to break dask.distributed/1.21.8+ds.1-1 autopkgtest: __init__() missing 1 required positional argument: 'pickle_cache')

Your message dated Fri, 05 Jan 2024 08:34:31 + with message-id and subject line Bug#904944: fixed in dask.distributed 2023.12.1+ds-3 has caused the Debian Bug report #904944, regarding joblib/0.12.1-1 appears to break dask.distributed/1.21.8+ds.1-1 autopkgtest: __init__() missing 1 required

Bug#612223: marked as done (Improve gs man page about previewing)

Your message dated Fri, 05 Jan 2024 01:04:45 -0600 with message-id <5055248.44csPzL39Z@riemann> and subject line Re: gs is not a previewer has caused the Debian Bug report #612223, regarding Improve gs man page about previewing to be marked as done. This means that you claim that the problem has

<    1   2