Bug#1053580: marked as done (mirror submission for mirror.matnetwrk.net)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Sat, 7 Oct 2023 08:30:37 +0200 with message-id and subject line Re: Bug#1053580: mirror submission for mirror.matnetwrk.net has caused the Debian Bug report #1053580, regarding mirror submission for mirror.matnetwrk.net to be marked as done. This means that you claim that the p

Processed: src:mame: fails to migrate to testing for too long: FTBFS on armel

2023-10-06 Thread Debian Bug Tracking System
Processing control commands: > close -1 0.258+dfsg.1-1 Bug #1053586 [src:mame] src:mame: fails to migrate to testing for too long: FTBFS on armel Marked as fixed in versions mame/0.258+dfsg.1-1. Bug #1053586 [src:mame] src:mame: fails to migrate to testing for too long: FTBFS on armel Marked Bug

Bug#1053538: marked as done (kexec-tools: kexec reboot even if "systemctl reboot" via initscripts - Debian stable and testing)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Sat, 07 Oct 2023 05:36:43 +0200 with message-id <934db139f2fe464a2fb3b83b3bd21d685dba7cc0.ca...@yahoo.com> and subject line Re: Bug#1053538: kexec-tools: kexec reboot even if "systemctl reboot" via initscripts - Debian stable and testing has caused the Debian Bug report #1053538

Bug#1053277: marked as done (libcups2: typo in NEWS)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 19:33:21 -0400 with message-id and subject line Re: Bug#1053277: libcups2: typo in NEWS has caused the Debian Bug report #1053277, regarding libcups2: typo in NEWS to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1042604: marked as done (sphinx-notfound-page: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 22:21:10 + with message-id and subject line Bug#1042604: fixed in sphinx-notfound-page 0.8.3-3 has caused the Debian Bug report #1042604, regarding sphinx-notfound-page: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: pybuild --test --test-pytest

Bug#1052853: marked as done (sphinx-notfound-page: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 22:21:10 + with message-id and subject line Bug#1052853: fixed in sphinx-notfound-page 0.8.3-3 has caused the Debian Bug report #1052853, regarding sphinx-notfound-page: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 ret

Bug#1036834: marked as done (mark libmunge2 Multi-Arch: same)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 22:21:02 + with message-id and subject line Bug#1036834: fixed in munge 0.5.15-3 has caused the Debian Bug report #1036834, regarding mark libmunge2 Multi-Arch: same to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1053075: marked as done (pixelmed-codec: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 21:58:49 + with message-id and subject line Bug#1053075: fixed in pixelmed-codec 20200328-6 has caused the Debian Bug report #1053075, regarding pixelmed-codec: FTBFS with OpenJDK 21 due to unsupported javac source/target level 7 to be marked as done. This

Bug#1038611: marked as done (lightdm 1.32 fails to start X on nvidia binary driver)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 23:11:09 +0200 with message-id and subject line Re: Bug#1038611: Help with investigating a bug in the LightDM/logind/DDX stack has caused the Debian Bug report #1038611, regarding lightdm 1.32 fails to start X on nvidia binary driver to be marked as done. This

Bug#935755: marked as done (please migrate to Breezy)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 21:08:27 +0100 with message-id and subject line This has now happened; upstream as well has caused the Debian Bug report #935755, regarding please migrate to Breezy to be marked as done. This means that you claim that the problem has been dealt with. If this is

Processed: closing 1016042

2023-10-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1016042 0.9.1.8-1 Bug #1016042 [src:haskell-inline-c] haskell-inline-c FTBFS on 32bit: ghc runs forever Marked as fixed in versions haskell-inline-c/0.9.1.8-1. Bug #1016042 [src:haskell-inline-c] haskell-inline-c FTBFS on 32bit: ghc runs f

Bug#1052697: marked as done (tech-ctte: proposed change to apt-listchanges algorithm needs expert consideration)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 20:47:23 +0100 with message-id <87fs2nbkj8@melete.silentflame.com> and subject line Re: Bug#1052697: tech-ctte: proposed change to apt-listchanges algorithm needs expert consideration has caused the Debian Bug report #1052697, regarding tech-ctte: proposed c

Bug#1051310: marked as done (sarsen: autopkgtest failures)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 21:44:01 +0200 with message-id <74f1d507-382d-4c8f-9c16-f24fa7495...@debian.org> and subject line Re: sarsen: autopkgtest needs update for python-xarray 2023.08.0 has caused the Debian Bug report #1050832, regarding sarsen: autopkgtest failures to be marked as do

Bug#1050832: marked as done (sarsen: autopkgtest needs update for python-xarray 2023.08.0)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 21:44:01 +0200 with message-id <74f1d507-382d-4c8f-9c16-f24fa7495...@debian.org> and subject line Re: sarsen: autopkgtest needs update for python-xarray 2023.08.0 has caused the Debian Bug report #1050832, regarding sarsen: autopkgtest needs update for python-xar

Bug#1033734: marked as done (munin-plugins-core: nginx_*: example configuration does not work with ipv6 localhost)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 19:37:02 + with message-id and subject line Bug#1033734: fixed in munin 2.0.74-1 has caused the Debian Bug report #1033734, regarding munin-plugins-core: nginx_*: example configuration does not work with ipv6 localhost to be marked as done. This means that

Bug#1053379: marked as done (munin-node: logrotate.d/munin-node should call invoke-rc.d)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 19:37:02 + with message-id and subject line Bug#1053379: fixed in munin 2.0.74-1 has caused the Debian Bug report #1053379, regarding munin-node: logrotate.d/munin-node should call invoke-rc.d to be marked as done. This means that you claim that the problem

Bug#738098: marked as done (O: grun -- GTK based run dialog)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #738098, regarding O: grun -- GTK based run dialog to be marked as done. This means that you claim that the problem has been dealt wit

Bug#967465: marked as done (grun: depends on deprecated GTK 2)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #967465, regarding grun: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been dealt w

Bug#669004: marked as done (grun: wishlist)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #669004, regarding grun: wishlist to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#750862: marked as done (grun: Typo in package description: "staring")

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #750862, regarding grun: Typo in package description: "staring" to be marked as done. This means that you claim that the problem has b

Bug#635435: marked as done (grun: [INTL:sk] Slovak app translation)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #635435, regarding grun: [INTL:sk] Slovak app translation to be marked as done. This means that you claim that the problem has been de

Bug#601796: marked as done (grun: [INTL:pt] Updated Portuguese translation for package messages)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #601796, regarding grun: [INTL:pt] Updated Portuguese translation for package messages to be marked as done. This means that you claim

Bug#496744: marked as done (grun: It's hard to run programs with short name)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #496744, regarding grun: It's hard to run programs with short name to be marked as done. This means that you claim that the problem ha

Bug#411802: marked as done (grun: The icon is ugly)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #411802, regarding grun: The icon is ugly to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#394861: marked as done (grun: Loses environment settings)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #394861, regarding grun: Loses environment settings to be marked as done. This means that you claim that the problem has been dealt wi

Bug#322349: marked as done (grun should strip spaces)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #322349, regarding grun should strip spaces to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#313760: marked as done (grun: [INTL:de] German PO file corrections)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #313760, regarding grun: [INTL:de] German PO file corrections to be marked as done. This means that you claim that the problem has bee

Bug#310748: marked as done (order of entries should be LRU)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #310748, regarding order of entries should be LRU to be marked as done. This means that you claim that the problem has been dealt with

Bug#246954: marked as done (grun segfaults on exit)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #246954, regarding grun segfaults on exit to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#309921: marked as done (two bugs in the UI widget)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #309921, regarding two bugs in the UI widget to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#984771: marked as done (rust-nom-3: depends on multiple unavailable packages)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:58:02 + with message-id and subject line Bug#1051982: Removed package(s) from unstable has caused the Debian Bug report #984771, regarding rust-nom-3: depends on multiple unavailable packages to be marked as done. This means that you claim that the probl

Bug#1052024: marked as done (RM: grun -- RoQA; dead upstream; orphaned; depends on gtk2)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:00 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #1052024, regarding RM: grun -- RoQA; dead upstream; orphaned; depends on gtk2 to be marked as done. This means that you claim that th

Bug#436905: marked as done (gatos: not handling nostrip build option (policy 10.1))

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #436905, regarding gatos: not handling nostrip build option (policy 10.1) to be marked as done. This means that you claim that the pro

Bug#1045088: marked as done (grun: Fails to build source after successful build)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:59:10 + with message-id and subject line Bug#1052024: Removed package(s) from unstable has caused the Debian Bug report #1045088, regarding grun: Fails to build source after successful build to be marked as done. This means that you claim that the proble

***UNCHECKED*** Bug#715655: marked as done ([Mayhem] Bug report on gatos: atisplit crashes with exit status 139)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #715655, regarding [Mayhem] Bug report on gatos: atisplit crashes with exit status 139 to be marked as done. This means that you claim

Bug#647146: marked as done (gatos: Formatting and grammar errors in Control File)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #647146, regarding gatos: Formatting and grammar errors in Control File to be marked as done. This means that you claim that the probl

Bug#1051982: marked as done (RM: rust-nom-3 -- ROM; depends on unavailable packages, obsolete)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:58 + with message-id and subject line Bug#1051982: Removed package(s) from unstable has caused the Debian Bug report #1051982, regarding RM: rust-nom-3 -- ROM; depends on unavailable packages, obsolete to be marked as done. This means that you claim t

Bug#451773: marked as done (xatitv doesn't hide window manager decorations when in fullscreen mode)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #451773, regarding xatitv doesn't hide window manager decorations when in fullscreen mode to be marked as done. This means that you cl

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

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:26 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #1051947, regarding RM: gatos -- RoQA; dead upstream; orphaned; low popcon to be marked as done. This means that you claim that the pr

Bug#391468: marked as done (xatitv: fails to start with: "GATOS: gatos_inita(): Invalid argument")

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #391468, regarding xatitv: fails to start with: "GATOS: gatos_inita(): Invalid argument" to be marked as done. This means that you cla

Bug#383585: marked as done (gatos-conf produces error messages with saving (bogus path))

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #383585, regarding gatos-conf produces error messages with saving (bogus path) to be marked as done. This means that you claim that th

Bug#1050467: marked as done (O: gatos -- ATI All-in-Wonder TV capture software)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #1050467, regarding O: gatos -- ATI All-in-Wonder TV capture software to be marked as done. This means that you claim that the problem

Bug#1043164: marked as done (gatos: please consider upgrading to 3.0 source format)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:57:34 + with message-id and subject line Bug#1051947: Removed package(s) from unstable has caused the Debian Bug report #1043164, regarding gatos: please consider upgrading to 3.0 source format to be marked as done. This means that you claim that the pro

Bug#1051771: marked as done (RM: genx [arm64 armel armhf i386 mips64el s390x] -- ROM; failure due to the numba dependency)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:56:33 + with message-id and subject line Bug#1051771: Removed package(s) from unstable has caused the Debian Bug report #1051771, regarding RM: genx [arm64 armel armhf i386 mips64el s390x] -- ROM; failure due to the numba dependency to be marked as done.

Bug#1051767: marked as done (RM: bornagain [arm64 armel armhf i386 ppc64el s390x] -- ROM; not yet supported by upstream)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:56:11 + with message-id and subject line Bug#1051767: Removed package(s) from unstable has caused the Debian Bug report #1051767, regarding RM: bornagain [arm64 armel armhf i386 ppc64el s390x] -- ROM; not yet supported by upstream to be marked as done.

Bug#1051745: marked as done (RM: r-cran-mlmrev [i386] -- ROM; Does not pass its autopkgtest on i386)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 14:55:22 -0400 with message-id <3265345.NinTjTxNON@localhost> and subject line Re: RM: r-cran-mlmrev [i386] -- ROM; Does not pass its autopkgtest on i386 has caused the Debian Bug report #1051745, regarding RM: r-cran-mlmrev [i386] -- ROM; Does not pass its auto

Bug#1051684: marked as done (RM: lldb liblldb-dev python3-lldb [mips64el] -- NBS; uninstallable, not in bookworm)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:52:51 + with message-id and subject line Bug#1051684: Removed package(s) from unstable has caused the Debian Bug report #1051684, regarding RM: lldb liblldb-dev python3-lldb [mips64el] -- NBS; uninstallable, not in bookworm to be marked as done. This me

Bug#1051626: marked as done (RM: rust-block-buffer-0.9 -- RoM; obsolete duplicate of rust-block-buffer)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:50:18 + with message-id and subject line Bug#1051626: Removed package(s) from unstable has caused the Debian Bug report #1051626, regarding RM: rust-block-buffer-0.9 -- RoM; obsolete duplicate of rust-block-buffer to be marked as done. This means that y

Bug#1051622: marked as done (RM: rust-sha-1 -- RoM; obsolete duplicate of rust-sha1)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:48:42 + with message-id and subject line Bug#1051622: Removed package(s) from unstable has caused the Debian Bug report #1051622, regarding RM: rust-sha-1 -- RoM; obsolete duplicate of rust-sha1 to be marked as done. This means that you claim that the pr

Bug#1051624: marked as done (RM: rust-sha2-0.9 -- RoM; obsolete duplicate of rust-sha2)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:49:42 + with message-id and subject line Bug#1051624: Removed package(s) from unstable has caused the Debian Bug report #1051624, regarding RM: rust-sha2-0.9 -- RoM; obsolete duplicate of rust-sha2 to be marked as done. This means that you claim that the

Bug#1051623: marked as done (RM: rust-sha-1-0.9 -- RoM; obsolete duplicate of rust-sha1)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:49:11 + with message-id and subject line Bug#1051623: Removed package(s) from unstable has caused the Debian Bug report #1051623, regarding RM: rust-sha-1-0.9 -- RoM; obsolete duplicate of rust-sha1 to be marked as done. This means that you claim that th

Bug#1051620: marked as done (RM: rust-ipfs-unixfs -- RoM; depends on obsolete Rust crates)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:48:10 + with message-id and subject line Bug#1051620: Removed package(s) from unstable has caused the Debian Bug report #1051620, regarding RM: rust-ipfs-unixfs -- RoM; depends on obsolete Rust crates to be marked as done. This means that you claim that

Bug#1051606: marked as done (RM: sysprof [i386] -- RoM; ANAIS; The GUI binary package is no longer built)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:47:12 + with message-id and subject line Bug#1051606: Removed package(s) from unstable has caused the Debian Bug report #1051606, regarding RM: sysprof [i386] -- RoM; ANAIS; The GUI binary package is no longer built to be marked as done. This means that

Bug#1051131: marked as done (RM: jpeg-xl/experimental -- ROM; Newer version upstream)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:46:09 + with message-id and subject line Bug#1051131: Removed package(s) from experimental has caused the Debian Bug report #1051131, regarding RM: jpeg-xl/experimental -- ROM; Newer version upstream to be marked as done. This means that you claim that t

Bug#1042155: marked as done (rust-ipfs-unixfs: FTBFS: build-dependency not installable: librust-block-padding-0.2+default-dev)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:48:15 + with message-id and subject line Bug#1051620: Removed package(s) from unstable has caused the Debian Bug report #1042155, regarding rust-ipfs-unixfs: FTBFS: build-dependency not installable: librust-block-padding-0.2+default-dev to be marked as d

Bug#1040246: marked as done (librust-block-buffer-0.9+block-padding-dev: uninstallable after upgrade of rust-block-padding.)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:50:21 + with message-id and subject line Bug#1051626: Removed package(s) from unstable has caused the Debian Bug report #1040246, regarding librust-block-buffer-0.9+block-padding-dev: uninstallable after upgrade of rust-block-padding. to be marked as don

Bug#1020890: marked as done (rust-ipfs-unixfs - depends on old version of multihash.)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:48:15 + with message-id and subject line Bug#1051620: Removed package(s) from unstable has caused the Debian Bug report #1020890, regarding rust-ipfs-unixfs - depends on old version of multihash. to be marked as done. This means that you claim that the p

Bug#1035421: marked as done (librust-sha-1+asm-dev: depends on unavailable librust-sha1-asm-0.4+default-dev)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:48:47 + with message-id and subject line Bug#1051622: Removed package(s) from unstable has caused the Debian Bug report #1035421, regarding librust-sha-1+asm-dev: depends on unavailable librust-sha1-asm-0.4+default-dev to be marked as done. This means t

Bug#1009123: marked as done (rust-sha-1: diff for NMU version 0.8.1-2.1)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 18:48:47 + with message-id and subject line Bug#1051622: Removed package(s) from unstable has caused the Debian Bug report #1009123, regarding rust-sha-1: diff for NMU version 0.8.1-2.1 to be marked as done. This means that you claim that the problem has be

Bug#1053572: marked as done (libosmgpsmap-1.0-1: libosmgpsmap and GeocodeGlib are incompatible and cannot be used together)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 20:10:48 +0200 with message-id <06986328-2ab3-4009-b745-66a06a83f...@xs4all.nl> and subject line Re: Bug#1053572: libosmgpsmap-1.0-1: libosmgpsmap and GeocodeGlib are incompatible and cannot be used together has caused the Debian Bug report #1053572, regarding li

Bug#1052827: marked as done (liblouisutdml: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 17:51:06 + with message-id and subject line Bug#1052827: fixed in liblouisutdml 2.11.0-4 has caused the Debian Bug report #1052827, regarding liblouisutdml: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit co

Bug#1048800: marked as done (liblouisutdml: Fails to build source after successful build)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 17:51:06 + with message-id and subject line Bug#1048800: fixed in liblouisutdml 2.11.0-4 has caused the Debian Bug report #1048800, regarding liblouisutdml: Fails to build source after successful build to be marked as done. This means that you claim that th

Bug#1053119: marked as done (orca fails to read file names when navigating some folders in caja+mate menu issues)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 17:51:26 + with message-id and subject line Bug#1053119: fixed in orca 45.1-1 has caused the Debian Bug report #1053119, regarding orca fails to read file names when navigating some folders in caja+mate menu issues to be marked as done. This means that you

Bug#1051366: marked as done (liblouisutdml FTCBFS: passes host cflags to native build)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 17:51:06 + with message-id and subject line Bug#1051366: fixed in liblouisutdml 2.11.0-4 has caused the Debian Bug report #1051366, regarding liblouisutdml FTCBFS: passes host cflags to native build to be marked as done. This means that you claim that the p

Bug#1053406: marked as done (skanpage: should depend on qml-mnodule-org-kde-kquickimageeditor)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 17:27:40 + with message-id and subject line Bug#1053406: fixed in skanpage 23.08.1-2 has caused the Debian Bug report #1053406, regarding skanpage: should depend on qml-mnodule-org-kde-kquickimageeditor to be marked as done. This means that you claim that t

Bug#1053463: marked as done (quilt: quilt functions corrupt patches if awk is not gawk)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 16:56:10 + with message-id and subject line Bug#1053463: fixed in quilt 0.67+really0.67-4 has caused the Debian Bug report #1053463, regarding quilt: quilt functions corrupt patches if awk is not gawk to be marked as done. This means that you claim that the

Bug#1053007: marked as done (transition: suitesparse-7.2)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 18:34:13 +0200 with message-id and subject line Re: Bug#1053007: transition: suitesparse-7.2 has caused the Debian Bug report #1053007, regarding transition: suitesparse-7.2 to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: reassign 1053558

2023-10-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > reassign 1053558 gnome-control-center 1:45.0-1 Bug #1053558 [network-manager-openconnect-gnome] Impossible to add VPN connection or change settings of existing profiles Bug reassigned from package 'network-manager-openconnect-gnome' to 'gnome-co

Bug#1052814: marked as done (python-recurring-ical-events: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 15:05:06 + with message-id and subject line Bug#1052814: fixed in python-recurring-ical-events 2.1.0-1 has caused the Debian Bug report #1052814, regarding python-recurring-ical-events: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{vers

Bug#1036981: marked as done (prosody-modules: please add mod_net_proxy)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 13:50:45 + with message-id and subject line Bug#1036981: fixed in prosody-modules 0.0~hg20231001.e5ad3f1f48bd+dfsg-1 has caused the Debian Bug report #1036981, regarding prosody-modules: please add mod_net_proxy to be marked as done. This means that you cl

Bug#1053566: marked as done (gnome-control-center: fails to add or edit vpn)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 13:35:10 + with message-id and subject line Bug#1053566: fixed in gnome-control-center 1:45.0-2 has caused the Debian Bug report #1053566, regarding gnome-control-center: fails to add or edit vpn to be marked as done. This means that you claim that the prob

Bug#1040899: marked as done (debian-cd: "Failed to mount /target/proc" during GRUB installation)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 15:14:59 +0200 with message-id <9820fdd3-6176-44bc-8bd8-cd1e2834f...@svario.it> and subject line Re: Bug#1040899: debian-cd: "Failed to mount /target/proc" during GRUB installation has caused the Debian Bug report #1040899, regarding debian-cd: "Failed to mount /

Bug#1052898: marked as done (python-datetimerange: FTBFS: tests fail)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 13:05:01 + with message-id and subject line Bug#1052898: fixed in python-typepy 1.3.1-1 has caused the Debian Bug report #1052898, regarding python-datetimerange: FTBFS: tests fail to be marked as done. This means that you claim that the problem has been de

Bug#1035477: marked as done (installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services...")

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 15:06:38 +0200 with message-id and subject line Re: Bug#1035477: installation-reports: grub or kernel of D-I image hangs on Thinkpad X13s after "EFI stub: Exiting boot services..." has caused the Debian Bug report #1035477, regarding installation-reports: grub o

Bug#1052798: marked as done (watcher-dashboard: FTBFS: AttributeError: 'NoneType' object has no attribute 'read')

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 13:47:49 +0200 with message-id <5db608a5-e289-41a3-bd8d-e2d29d157...@debian.org> and subject line Bug was in Horizon, fixed in 3:23.3.0-1 has caused the Debian Bug report #1052798, regarding watcher-dashboard: FTBFS: AttributeError: 'NoneType' object has no attri

Bug#1052851: marked as done (heat-dashboard: FTBFS: AttributeError: 'NoneType' object has no attribute 'read')

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 13:47:49 +0200 with message-id <5db608a5-e289-41a3-bd8d-e2d29d157...@debian.org> and subject line Bug was in Horizon, fixed in 3:23.3.0-1 has caused the Debian Bug report #1052851, regarding heat-dashboard: FTBFS: AttributeError: 'NoneType' object has no attribut

Bug#1052797: marked as done (senlin-dashboard: FTBFS: AttributeError: 'NoneType' object has no attribute 'read')

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 13:47:49 +0200 with message-id <5db608a5-e289-41a3-bd8d-e2d29d157...@debian.org> and subject line Bug was in Horizon, fixed in 3:23.3.0-1 has caused the Debian Bug report #1052797, regarding senlin-dashboard: FTBFS: AttributeError: 'NoneType' object has no attrib

Bug#1052777: marked as done (trove-dashboard: FTBFS: AttributeError: 'NoneType' object has no attribute 'read')

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 13:47:49 +0200 with message-id <5db608a5-e289-41a3-bd8d-e2d29d157...@debian.org> and subject line Bug was in Horizon, fixed in 3:23.3.0-1 has caused the Debian Bug report #1052777, regarding trove-dashboard: FTBFS: AttributeError: 'NoneType' object has no attribu

Bug#1050877: marked as done (devscripts: debchange v2.17.10 ignores EMAIL and DEBEMAIL env variables)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 06:49:30 -0500 with message-id <08e58575-2a1c-4a5a-9afb-0e3d49170...@peterhyman.com> and subject line Bug 1050877 may be closed has caused the Debian Bug report #1050877, regarding devscripts: debchange v2.17.10 ignores EMAIL and DEBEMAIL env variables to be mark

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

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 11:35:02 + with message-id and subject line Bug#1052862: fixed in python-icalendar 5.0.10-1 has caused the Debian Bug report #1052862, regarding python-icalendar: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned e

Bug#1052810: marked as done (golang-starlark: FTBFS: dh_auto_test fails: unknown time zone US/Eastern)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 11:34:22 + with message-id and subject line Bug#1052810: fixed in golang-starlark 0.0~git20230726.7dadff3-2 has caused the Debian Bug report #1052810, regarding golang-starlark: FTBFS: dh_auto_test fails: unknown time zone US/Eastern to be marked as done.

Bug#1053167: marked as done (Please remove librbd-dev build-depends on 32 bits arch)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 11:19:47 + with message-id and subject line Bug#1053167: fixed in fio 3.35-4 has caused the Debian Bug report #1053167, regarding Please remove librbd-dev build-depends on 32 bits arch to be marked as done. This means that you claim that the problem has bee

Processed: RFS: blender-doc/3.6-1 [ITP] -- Blender Manual by the Blender Foundation

2023-10-06 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1051150 Bug #1051150 [sponsorship-requests] RFS: blender-doc/3.6-1 [ITP] -- Blender Manual by the Blender Foundation Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 1051150: https://bugs.de

Bug#1052767: marked as done (python-unicodedata2: FTBFS: make[1]: *** [debian/rules:16: execute_before_dh_auto_build] Error 1)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 10:50:26 + with message-id and subject line Bug#1052767: fixed in python-unicodedata2 15.1.0+ds-1 has caused the Debian Bug report #1052767, regarding python-unicodedata2: FTBFS: make[1]: *** [debian/rules:16: execute_before_dh_auto_build] Error 1 to be mar

Bug#1052287: marked as done (python-unicodedata2: Fails to build with unicode-data 15.1.0)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 10:50:26 + with message-id and subject line Bug#1052287: fixed in python-unicodedata2 15.1.0+ds-1 has caused the Debian Bug report #1052287, regarding python-unicodedata2: Fails to build with unicode-data 15.1.0 to be marked as done. This means that you cla

Bug#1045417: marked as done (python-unicodedata2: Fails to build source after successful build)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 10:50:26 + with message-id and subject line Bug#1045417: fixed in python-unicodedata2 15.1.0+ds-1 has caused the Debian Bug report #1045417, regarding python-unicodedata2: Fails to build source after successful build to be marked as done. This means that yo

Bug#1052008: marked as done (gm2-13 Cannot Find Its Libraries At Link Time)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 10:22:14 + with message-id and subject line Bug#1052008: fixed in gcc-13 13.2.0-5 has caused the Debian Bug report #1052008, regarding gm2-13 Cannot Find Its Libraries At Link Time to be marked as done. This means that you claim that the problem has been de

Bug#1052314: marked as done (libquadmath (gcc): license may be inaccurate)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 10:22:14 + with message-id and subject line Bug#1052314: fixed in gcc-13 13.2.0-5 has caused the Debian Bug report #1052314, regarding libquadmath (gcc): license may be inaccurate to be marked as done. This means that you claim that the problem has been dea

Bug#1042670: marked as done (flycheck: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 02:53:54 -0700 with message-id <87h6n4nkjx@debian-hx90.lan> and subject line Re: Bug#1042670: flycheck: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting has caused the Debian Bug report #1042670, regarding

Bug#739384: marked as done (keepass2: does not start anymore (after upgrade to mono?))

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 10:19:12 +0200 with message-id and subject line Re: Bug#739384: keepass2: does not start anymore (after upgrade to mono?) has caused the Debian Bug report #739384, regarding keepass2: does not start anymore (after upgrade to mono?) to be marked as done. This me

Bug#1053540: marked as done (package contains license CC-BY-SA-2.0-uk)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 07:52:30 + with message-id and subject line Bug#1053540: fixed in libhtmlcleaner-java 2.29+dfsg-1 has caused the Debian Bug report #1053540, regarding package contains license CC-BY-SA-2.0-uk to be marked as done. This means that you claim that the problem

Bug#1053513: marked as done (openstack-cluster-installer-common: (oci-system-serial) Use system serial on QEMU VMs)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 08:42:26 + with message-id and subject line Bug#1053513: fixed in openstack-cluster-installer 42.3.0 has caused the Debian Bug report #1053513, regarding openstack-cluster-installer-common: (oci-system-serial) Use system serial on QEMU VMs to be marked as d

Bug#1051141: marked as done (mfem: broken build system?)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 07:35:26 + with message-id and subject line Bug#1051141: fixed in mfem 4.5.2+ds-1.2 has caused the Debian Bug report #1051141, regarding mfem: broken build system? to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1053514: marked as done (openstack-cluster-installer-agent: (oci-system-serial) Bugfix for handling NICs which do not report a speed)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 08:42:26 + with message-id and subject line Bug#1053514: fixed in openstack-cluster-installer 42.3.0 has caused the Debian Bug report #1053514, regarding openstack-cluster-installer-agent: (oci-system-serial) Bugfix for handling NICs which do not report a s

Bug#1053510: marked as done (openstack-cluster-installer: puppetserver sign command needs updating for puppet 7)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 08:42:26 + with message-id and subject line Bug#1053510: fixed in openstack-cluster-installer 42.3.0 has caused the Debian Bug report #1053510, regarding openstack-cluster-installer: puppetserver sign command needs updating for puppet 7 to be marked as done

Bug#1053507: marked as done (openstack-cluster-installer: 500 error on oci agent first report)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 08:42:26 + with message-id and subject line Bug#1053507: fixed in openstack-cluster-installer 42.3.0 has caused the Debian Bug report #1053507, regarding openstack-cluster-installer: 500 error on oci agent first report to be marked as done. This means that

Bug#1053506: marked as done (openstack-cluster-installer: ocicli machine-guess-racking returns error when no match found)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 08:42:26 + with message-id and subject line Bug#1053506: fixed in openstack-cluster-installer 42.3.0 has caused the Debian Bug report #1053506, regarding openstack-cluster-installer: ocicli machine-guess-racking returns error when no match found to be marke

Bug#1053471: marked as done (libpython3.11-testsuite: Installation fails with SyntaxError)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 6 Oct 2023 10:21:37 +0200 with message-id and subject line Fixed in 3.11.6-2 has caused the Debian Bug report #1053471, regarding libpython3.11-testsuite: Installation fails with SyntaxError to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1036221: marked as done (mfem: please make the build reproducible)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 07:35:38 + with message-id and subject line Bug#1036221: fixed in mfem 4.5.2+ds-1.3 has caused the Debian Bug report #1036221, regarding mfem: please make the build reproducible to be marked as done. This means that you claim that the problem has been dealt

Bug#1039302: marked as done (openstack-cluster-installer: ships sysv-init script without systemd unit)

2023-10-06 Thread Debian Bug Tracking System
Your message dated Fri, 06 Oct 2023 08:42:26 + with message-id and subject line Bug#1039302: fixed in openstack-cluster-installer 42.3.0 has caused the Debian Bug report #1039302, regarding openstack-cluster-installer: ships sysv-init script without systemd unit to be marked as done. This me

  1   2   >