Bug#1031460: marked as done (enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' != '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.

Your message dated Sun, 26 Feb 2023 07:19:06 + with message-id and subject line Bug#1031460: fixed in enlighten 1.11.2-1 has caused the Debian Bug report #1031460, regarding enlighten: FTBFS: AssertionError: '1.00[31 chars]0.00 s/B | 128.00 KiB | 896.00 KiB | 512.00 K[105 chars] s/B' !=

Processed: Re: mdadm --re-add Segmentation Fault

Processing commands for cont...@bugs.debian.org: > close 784874 3.3.4-1 Bug #784874 [mdadm] mdadm --re-add Segmentation Fault Marked as fixed in versions mdadm/3.3.4-1. Bug #784874 [mdadm] mdadm --re-add Segmentation Fault Marked Bug as done > thanks Stopping processing here. Please contact me

Processed: Re: mdadm crashing when trying to grow an array with big disks

Processing commands for cont...@bugs.debian.org: > close 985536 4.1-1 Bug #985536 [mdadm] mdadm crashing when trying to grow an array with big disks Marked as fixed in versions mdadm/4.1-1. Bug #985536 [mdadm] mdadm crashing when trying to grow an array with big disks Marked Bug as done > thanks

Processed: Re: /sbin/mdadm --detail --scan fails in d-i

Processing commands for cont...@bugs.debian.org: > close 569359 Bug #569359 [mdadm] /sbin/mdadm --detail --scan fails in d-i Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 569359: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=569359 Debian

Bug#1029983: marked as done (slang2: configure script uses ncurses5-config, which is going away)

Your message dated Sun, 26 Feb 2023 06:07:58 + with message-id and subject line Bug#1029983: fixed in slang2 2.3.3-3 has caused the Debian Bug report #1029983, regarding slang2: configure script uses ncurses5-config, which is going away to be marked as done. This means that you claim that

Bug#860983: marked as done (pylint: called emacs-package-install as a new-style add-on, but has no compat file)

Your message dated Sun, 26 Feb 2023 02:46:57 + with message-id and subject line Bug#860983: fixed in pylint 2.16.2-1 has caused the Debian Bug report #860983, regarding pylint: called emacs-package-install as a new-style add-on, but has no compat file to be marked as done. This means that

Bug#613646: marked as done (pylint.el redefines emacs key bindings which are reserved for the user)

Your message dated Sun, 26 Feb 2023 02:46:57 + with message-id and subject line Bug#613646: fixed in pylint 2.16.2-1 has caused the Debian Bug report #613646, regarding pylint.el redefines emacs key bindings which are reserved for the user to be marked as done. This means that you claim that

Bug#563000: marked as done (pylint: wrongly tries to open emacs locks)

Your message dated Sun, 26 Feb 2023 02:46:57 + with message-id and subject line Bug#563000: fixed in pylint 2.16.2-1 has caused the Debian Bug report #563000, regarding pylint: wrongly tries to open emacs locks to be marked as done. This means that you claim that the problem has been dealt

Processed: closing 613646

Processing commands for cont...@bugs.debian.org: > close 613646 2.16.2-1 Bug #613646 [pylint] pylint.el redefines emacs key bindings which are reserved for the user There is no source info for the package 'pylint' at version '2.16.2-1' with architecture '' Unable to make a source version for

Processed: closing 613646

Processing commands for cont...@bugs.debian.org: > close 613646 2.16.2-1 Bug #613646 {Done: Sandro Tosi } [pylint] pylint.el redefines emacs key bindings which are reserved for the user There is no source info for the package 'pylint' at version '2.16.2-1' with architecture '' Unable to make a

Processed: Merge duplicates

Processing commands for cont...@bugs.debian.org: > unarchive 927341 Bug #927341 {Done: Gregor Jasny } [libdvbv5-0] libdvbv5-0: upgrade to version 1.16.3-2 break kaffeine Unarchived Bug 927341 > forcemerge 927341 927696 Bug #927341 {Done: Gregor Jasny } [libdvbv5-0] libdvbv5-0: upgrade to

Bug#1010936: marked as done (python3-dkim should depend on python3-dnspython)

Your message dated Sat, 25 Feb 2023 23:04:39 + with message-id and subject line Bug#1010936: fixed in dkimpy 1.1.0-1 has caused the Debian Bug report #1010936, regarding python3-dkim should depend on python3-dnspython to be marked as done. This means that you claim that the problem has been

Bug#1031904: marked as done (firmware-ath9k-htc: insufficient coordination around moving files between packages)

Your message dated Sat, 25 Feb 2023 23:43:04 +0100 with message-id <0955c399-3144-fd25-40c5-d5a42a82d...@debian.org> and subject line Re: Bug#1031904: firmware-ath9k-htc: insufficient coordination around moving files between packages has caused the Debian Bug report #1031904, regarding

Processed: Re: please add a note about /usr/share/doc/mdadm/README.recipes.gz at the top of the man page

Processing commands for cont...@bugs.debian.org: > close 609795 Bug #609795 [mdadm] please add a note about /usr/share/doc/mdadm/README.recipes.gz at the top of the man page Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 609795:

Processed: Re: mdadm: mdadm.8.in -- Order items alphabetically in manual page

Processing commands for cont...@bugs.debian.org: > close 619265 Bug #619265 [mdadm] mdadm: mdadm.8.in -- Order items alphabetically in manual page Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 619265:

Processed: Re: mdadm: rounding errors in human_size()

Processing commands for cont...@bugs.debian.org: > close 763917 3.3.4-1 Bug #763917 [mdadm] mdadm: rounding errors in human_size() Marked as fixed in versions mdadm/3.3.4-1. Bug #763917 [mdadm] mdadm: rounding errors in human_size() Marked Bug as done > thanks Stopping processing here. Please

Bug#769178: marked as done (drslib: wrong homepage url)

Your message dated Sat, 25 Feb 2023 23:37:58 +0200 with message-id and subject line Fixed since 0.3.1.p3-1 has caused the Debian Bug report #769178, regarding drslib: wrong homepage url to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Processed: Re: mdadm: RAID1 unknown partition table kernel messages for raid disks

Processing commands for cont...@bugs.debian.org: > close 821355 Bug #821355 [mdadm] mdadm: RAID1 unknown partition table kernel messages for raid disks Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 821355:

Bug#997179: marked as done (tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security])

Your message dated Sat, 25 Feb 2023 21:13:03 + with message-id and subject line Bug#997179: fixed in tty-clock 2.3-2 has caused the Debian Bug report #997179, regarding tty-clock: FTBFS: ttyclock.c:278:73: error: format not a string literal and no format arguments [-Werror=format-security]

Bug#1031935: marked as done (firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata)

Your message dated Sat, 25 Feb 2023 21:10:44 + with message-id and subject line Bug#1031935: fixed in open-ath9k-htc-firmware 1.4.0-108-gd856466+dfsg1-1.3 has caused the Debian Bug report #1031935, regarding firmware-ath9k-htc: missing hardware identifiers in dep-11 metadata to be marked as

Bug#1031478: marked as done (nrepl-clojure: FTBFS: Build randomly either hangs or fails with test errors)

Your message dated Sat, 25 Feb 2023 21:10:33 + with message-id and subject line Bug#1031478: fixed in nrepl-clojure 1.0.0-5 has caused the Debian Bug report #1031478, regarding nrepl-clojure: FTBFS: Build randomly either hangs or fails with test errors to be marked as done. This means that

Bug#1028625: marked as done (src:x-loader: fails to migrate to testing for too long: FTBFS)

Your message dated Sat, 25 Feb 2023 21:13:18 + with message-id and subject line Bug#1028625: fixed in x-loader 1.5.1+git20110715+fca7cd2-4 has caused the Debian Bug report #1028625, regarding src:x-loader: fails to migrate to testing for too long: FTBFS to be marked as done. This means that

Bug#1026364: marked as done (FTBFS: error: dangling pointer ‘dentptr’ to ‘dent’ may be used)

Your message dated Sat, 25 Feb 2023 21:13:18 + with message-id and subject line Bug#1026364: fixed in x-loader 1.5.1+git20110715+fca7cd2-4 has caused the Debian Bug report #1026364, regarding FTBFS: error: dangling pointer ‘dentptr’ to ‘dent’ may be used to be marked as done. This means that

Bug#977458: marked as done (micro: Please register micro for the editor alternative)

Your message dated Sat, 25 Feb 2023 21:09:53 + with message-id and subject line Bug#977458: fixed in micro 2.0.11-1 has caused the Debian Bug report #977458, regarding micro: Please register micro for the editor alternative to be marked as done. This means that you claim that the problem has

Bug#1031917: marked as done ([INTL:ro] Romanian debconf templates translation of iproute2)

Your message dated Sat, 25 Feb 2023 21:09:23 + with message-id and subject line Bug#1031917: fixed in iproute2 6.1.0-2 has caused the Debian Bug report #1031917, regarding [INTL:ro] Romanian debconf templates translation of iproute2 to be marked as done. This means that you claim that the

Bug#1031947: marked as done (eos-sdk: FTBFS everywhere)

Your message dated Sat, 25 Feb 2023 20:54:51 + with message-id and subject line Bug#1031947: fixed in eos-sdk 0~git20230107+ds-2 has caused the Debian Bug report #1031947, regarding eos-sdk: FTBFS everywhere to be marked as done. This means that you claim that the problem has been dealt

Bug#1031937: marked as done (unblock: python-recipe-scrapers/14.32.0-1)

Your message dated Sat, 25 Feb 2023 21:56:26 +0100 with message-id <64f9154c-ae2b-ecf6-d616-eb2de5e0d...@debian.org> and subject line Re: Bug#1031937: unblock: python-recipe-scrapers/14.32.0-1 has caused the Debian Bug report #1031937, regarding unblock: python-recipe-scrapers/14.32.0-1 to be

Bug#1028955: marked as done (Our Drawing version is severely outdated)

Your message dated Sat, 25 Feb 2023 20:52:15 + with message-id and subject line Bug#1028955: fixed in drawing 1.0.2-1 has caused the Debian Bug report #1028955, regarding Our Drawing version is severely outdated to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: W: mdadm: failed to auto-generate the mdadm.conf file

Processing commands for cont...@bugs.debian.org: > close 873767 Bug #873767 [mdadm] W: mdadm: failed to auto-generate the mdadm.conf file Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 873767:

Processed: Re: Bug#705454: mdadm: --examine --scan generates wrong #spares

Processing commands for cont...@bugs.debian.org: > close 705454 Bug #705454 [mdadm] mdadm: --examine --scan generates wrong #spares Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 705454: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705454

Bug#1031906: marked as done (openconnect: Fails with Unexpected Pulse config packet using newer pulse server)

Your message dated Sat, 25 Feb 2023 19:35:14 + with message-id and subject line Bug#1031906: fixed in openconnect 9.01-3 has caused the Debian Bug report #1031906, regarding openconnect: Fails with Unexpected Pulse config packet using newer pulse server to be marked as done. This means that

Bug#983130: marked as done (artikulate: remove libqtgstreamer-dev from Build-Depends)

Your message dated Sat, 25 Feb 2023 19:24:14 + with message-id and subject line Bug#983130: fixed in artikulate 4:22.12.2-1 has caused the Debian Bug report #983130, regarding artikulate: remove libqtgstreamer-dev from Build-Depends to be marked as done. This means that you claim that the

Bug#1031930: marked as done (nmu: binutils-mingw-w64_10.3, gdb-mingw-w64_12)

Your message dated Sat, 25 Feb 2023 20:02:15 +0100 with message-id and subject line Re: Bug#1031930: nmu: binutils-mingw-w64_10.3, gdb-mingw-w64_12 has caused the Debian Bug report #1031930, regarding nmu: binutils-mingw-w64_10.3, gdb-mingw-w64_12 to be marked as done. This means that you claim

Processed: Re: mdadm: Newly-created array doesn't assemble at boot - related to hostname change?

Processing commands for cont...@bugs.debian.org: > close 844640 Bug #844640 [mdadm] mdadm: Newly-created array doesn't assemble at boot - related to hostname change? Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 844640:

Processed: Re: mdadm --size -G: size is truncated below 4TiB (on a 32bit platform)

Processing commands for cont...@bugs.debian.org: > close 855235 Bug #855235 [mdadm] mdadm --size -G: size is truncated below 4TiB (on a 32bit platform) Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 855235:

Processed: Re: initramfs-tools: boot fails using root=UUID= for root-device on software, raid /dev/md*

Processing commands for cont...@bugs.debian.org: > close 789150 Bug #789150 [mdadm] initramfs-tools: boot fails using root=UUID= for root-device on software, raid /dev/md* Bug #789152 [mdadm] boot fails using root=UUID= for root-device on software, raid /dev/md* Marked Bug as done Marked Bug as

Processed: Re: mdadm: eats all cpu time on all cores

Processing commands for cont...@bugs.debian.org: > close 810687 Bug #810687 [mdadm] mdadm: eats all cpu time on all cores Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 810687: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810687 Debian

Processed: Re: openconnect: fails to restore previous network configuration

Processing control commands: > tags -1 upstream Bug #1026961 [openconnect] openconnect: fails to restore previous network configuration Added tag(s) upstream. > close -1 Bug #1026961 [openconnect] openconnect: fails to restore previous network configuration Marked Bug as done -- 1026961:

Processed: Re: mdadm: Each file copy to array grown by MDADM results in copies with different md5sum values

Processing commands for cont...@bugs.debian.org: > close 675394 4.2-1 Bug #675394 [mdadm] mdadm: Each file copy to array grown by MDADM results in copies with different md5sum values Marked as fixed in versions mdadm/4.2-1. Bug #675394 [mdadm] mdadm: Each file copy to array grown by MDADM

Bug#980974: marked as done (apparmor blocks cups backend outgoing network connections)

Your message dated Sat, 25 Feb 2023 18:24:11 + (UTC) with message-id and subject line Closing this bug (BTS maintenance for debian-printing) has caused the Debian Bug report #977813, regarding apparmor blocks cups backend outgoing network connections to be marked as done. This means that

Bug#977813: marked as done (cupsd requests net_admin capability, but AppArmor denies)

Your message dated Sat, 25 Feb 2023 18:24:11 + (UTC) with message-id and subject line Closing this bug (BTS maintenance for debian-printing) has caused the Debian Bug report #977813, regarding cupsd requests net_admin capability, but AppArmor denies to be marked as done. This means that you

Bug#912575: marked as done (cups: ipp backend is not able to authenticate using kerberos)

Your message dated Sat, 25 Feb 2023 18:01:51 + (UTC) with message-id and subject line Closing this bug (BTS maintenance for debian-printing) has caused the Debian Bug report #912575, regarding cups: ipp backend is not able to authenticate using kerberos to be marked as done. This means that

Bug#1030678: marked as done (dhewm3: An additional copyright entry may be appropriate)

Your message dated Sat, 25 Feb 2023 19:31:23 +0100 with message-id and subject line Re: Bug#1030678: dhewm3: An additional copyright entry may be appropriate has caused the Debian Bug report #1030678, regarding dhewm3: An additional copyright entry may be appropriate to be marked as done. This

Bug#1017408: marked as done (cups 2.4.2-1+b1 and changelog.Debian)

Your message dated Sat, 25 Feb 2023 18:30:03 + (UTC) with message-id and subject line Closing this bug (BTS maintenance for debian-printing) has caused the Debian Bug report #1017408, regarding cups 2.4.2-1+b1 and changelog.Debian to be marked as done. This means that you claim that the

Processed: Re: mdadm: add "containers" to emergency config file

Processing commands for cont...@bugs.debian.org: > close 749062 4.2-1 Bug #749062 [mdadm] mdadm: add "containers" to emergency config file Marked as fixed in versions mdadm/4.2-1. Bug #749062 [mdadm] mdadm: add "containers" to emergency config file Marked Bug as done > thanks Stopping processing

Processed: Re: mdadm will only start root device degraded

Processing commands for cont...@bugs.debian.org: > close 864145 Bug #864145 [mdadm] mdadm will only start root device degraded Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 864145: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864145

Processed: Re: mdadm: upgraded mdadm now does not recognize RAID6 array causing boot to drop into emergency mode

Processing commands for cont...@bugs.debian.org: > close 806215 4.2-1 Bug #806215 [mdadm] mdadm: upgraded mdadm now does not recognize RAID6 array causing boot to drop into emergency mode Marked as fixed in versions mdadm/4.2-1. Bug #806215 [mdadm] mdadm: upgraded mdadm now does not recognize

Bug#996622: marked as done (mdadm prints warning on every boot due to evifarfs on non-EFI system)

Your message dated Sat, 25 Feb 2023 18:19:39 + with message-id and subject line Bug#996622: fixed in mdadm 4.2+20230223-1 has caused the Debian Bug report #996622, regarding mdadm prints warning on every boot due to evifarfs on non-EFI system to be marked as done. This means that you claim

Bug#1031942: marked as done (sphinxbase: Please drop the ltrace build dependency on mipsel)

Your message dated Sat, 25 Feb 2023 18:20:19 + with message-id and subject line Bug#1031942: fixed in sphinxbase 0.8+5prealpha+1-16 has caused the Debian Bug report #1031942, regarding sphinxbase: Please drop the ltrace build dependency on mipsel to be marked as done. This means that you

Bug#1003352: marked as done (mdadm: Intel RST RAID not detected because /sys/firmware/efi/efivars wasn't mount)

Your message dated Sat, 25 Feb 2023 18:19:39 + with message-id and subject line Bug#1003352: fixed in mdadm 4.2+20230223-1 has caused the Debian Bug report #1003352, regarding mdadm: Intel RST RAID not detected because /sys/firmware/efi/efivars wasn't mount to be marked as done. This means

Bug#916596: marked as done (iptables.postinst failure on link creation)

Your message dated Sat, 25 Feb 2023 20:17:15 +0200 with message-id and subject line Re: Bug#916596: iptables.postinst failure on link creation has caused the Debian Bug report #916596, regarding iptables.postinst failure on link creation to be marked as done. This means that you claim that the

Bug#1031895: marked as done (zoph fails to purge when mariadb-client is not installed)

Your message dated Sat, 25 Feb 2023 17:59:25 + with message-id and subject line Bug#1031895: fixed in zoph 1.0.1-3 has caused the Debian Bug report #1031895, regarding zoph fails to purge when mariadb-client is not installed to be marked as done. This means that you claim that the problem

Bug#1025590: marked as done (winetricks: recommends transitional policykit-1 package)

Your message dated Sat, 25 Feb 2023 17:59:14 + with message-id and subject line Bug#1025590: fixed in winetricks 20230212-1 has caused the Debian Bug report #1025590, regarding winetricks: recommends transitional policykit-1 package to be marked as done. This means that you claim that the

Bug#1031436: marked as done (ubuntu-dev-tools: FTBFS because of ./run-linters during build)

Your message dated Sat, 25 Feb 2023 17:55:00 + with message-id and subject line Bug#1031436: fixed in ubuntu-dev-tools 0.193 has caused the Debian Bug report #1031436, regarding ubuntu-dev-tools: FTBFS because of ./run-linters during build to be marked as done. This means that you claim that

Bug#963433: marked as done (libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2)

Your message dated Sat, 25 Feb 2023 17:52:14 + with message-id and subject line Bug#961147: fixed in libcolor-calc-perl 1.074-3 has caused the Debian Bug report #961147, regarding libcolor-calc-perl: FTBFS: dh_auto_test: error: perl Build test --verbose 1 returned exit code 2 to be marked as

Bug#961147: marked as done (libcolor-calc-perl: broken by new libgraphics-colornames-perl)

Your message dated Sat, 25 Feb 2023 17:52:14 + with message-id and subject line Bug#961147: fixed in libcolor-calc-perl 1.074-3 has caused the Debian Bug report #961147, regarding libcolor-calc-perl: broken by new libgraphics-colornames-perl to be marked as done. This means that you claim

Bug#1031744: marked as done (httpdirfs: usage of ubsan might introduce vulnerabilities)

Your message dated Sat, 25 Feb 2023 17:51:09 + with message-id and subject line Bug#1031744: fixed in httpdirfs-fuse 1.2.5-1 has caused the Debian Bug report #1031744, regarding httpdirfs: usage of ubsan might introduce vulnerabilities to be marked as done. This means that you claim that the

Bug#837385: marked as done (firmware-atheros: move DFSG-free ath9k_htc firmware to main)

Your message dated Sat, 25 Feb 2023 17:20:14 + with message-id and subject line Bug#837385: fixed in firmware-nonfree 20230210-2 has caused the Debian Bug report #837385, regarding firmware-atheros: move DFSG-free ath9k_htc firmware to main to be marked as done. This means that you claim

Bug#980746: marked as done (remove ath9k_htc, provided by libre package firmware-ath9k-htc)

Your message dated Sat, 25 Feb 2023 17:20:14 + with message-id and subject line Bug#837385: fixed in firmware-nonfree 20230210-2 has caused the Debian Bug report #837385, regarding remove ath9k_htc, provided by libre package firmware-ath9k-htc to be marked as done. This means that you claim

Bug#1030848: marked as done (qpdview FTCBFS: uses the build architecture pkg-config)

Your message dated Sat, 25 Feb 2023 17:21:39 + with message-id and subject line Bug#1030848: fixed in qpdfview 0.5.0+ds-2 has caused the Debian Bug report #1030848, regarding qpdview FTCBFS: uses the build architecture pkg-config to be marked as done. This means that you claim that the

Bug#1026027: marked as done (graphical installer: using nano in a installer shell fails)

Your message dated Sat, 25 Feb 2023 17:06:39 + with message-id and subject line Bug#1026027: fixed in debian-installer-utils 1.145 has caused the Debian Bug report #1026027, regarding graphical installer: using nano in a installer shell fails to be marked as done. This means that you claim

Bug#1031442: marked as done (gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2)

Your message dated Sat, 25 Feb 2023 19:01:09 +0200 with message-id and subject line Re: Bug#1031442: gnustep-base: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 messages=yes returned exit code 2 has caused the Debian Bug report #1031442, regarding

Bug#1031438: marked as done (qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2)

Your message dated Sat, 25 Feb 2023 16:34:07 + with message-id and subject line Bug#1031438: fixed in qca2 2.3.5-2 has caused the Debian Bug report #1031438, regarding qca2: FTBFS: dh_auto_test: error: cd build && make -j8 test ARGS\+=--verbose ARGS\+=-j8 returned exit code 2 to be marked as

Bug#1028007: marked as done (jove: [INTL:pt_BR] Brazilian Portuguese debconf templates translation)

Your message dated Sat, 25 Feb 2023 16:20:00 + with message-id and subject line Bug#1028007: fixed in jove 4.17.5.1-1 has caused the Debian Bug report #1028007, regarding jove: [INTL:pt_BR] Brazilian Portuguese debconf templates translation to be marked as done. This means that you claim

Bug#1031706: marked as done (optuna: test_create_new_trial randomly fails on s390x)

Your message dated Sat, 25 Feb 2023 15:49:16 + with message-id and subject line Bug#1031706: fixed in optuna 3.1.0-4 has caused the Debian Bug report #1031706, regarding optuna: test_create_new_trial randomly fails on s390x to be marked as done. This means that you claim that the problem has

Bug#1031528: marked as done (gnome-shell-pomodoro: Screen overlay can't be cleared)

Your message dated Sat, 25 Feb 2023 15:49:06 + with message-id and subject line Bug#1031528: fixed in gnome-shell-pomodoro 0.22.1-1 has caused the Debian Bug report #1031528, regarding gnome-shell-pomodoro: Screen overlay can't be cleared to be marked as done. This means that you claim that

Processed: Re: mdadm --add fails, can not add spares (regression)

Processing commands for cont...@bugs.debian.org: > close 837964 4.2-1 Bug #837964 [mdadm] mdadm --add fails, can not add spares (regression) Marked as fixed in versions mdadm/4.2-1. Bug #837964 [mdadm] mdadm --add fails, can not add spares (regression) Marked Bug as done > thanks Stopping

Processed: Re: mdadm: device rescan missing in initrd root device loop

Processing commands for cont...@bugs.debian.org: > close 818344 4.2-1 Bug #818344 [mdadm] mdadm: device rescan missing in initrd root device loop Marked as fixed in versions mdadm/4.2-1. Bug #818344 [mdadm] mdadm: device rescan missing in initrd root device loop Marked Bug as done > thanks

Processed: Re: mdadm: subprocess installed post-installation script returned error exit status 128

Processing commands for cont...@bugs.debian.org: > close 857284 4.2-1 Bug #857284 [mdadm] mdadm: subprocess installed post-installation script returned error exit status 128 Marked as fixed in versions mdadm/4.2-1. Bug #857284 [mdadm] mdadm: subprocess installed post-installation script

Bug#1026501: marked as done (request-tracker4: FTBFS: make[1]: *** [Makefile:381: test-parallel] Error 1)

Your message dated Sat, 25 Feb 2023 15:20:59 + with message-id and subject line Bug#1026501: fixed in request-tracker4 4.4.6+dfsg-1.1 has caused the Debian Bug report #1026501, regarding request-tracker4: FTBFS: make[1]: *** [Makefile:381: test-parallel] Error 1 to be marked as done. This

Processed: Re: mdadm.conf: missing explicit hotplug POLICY

Processing commands for cont...@bugs.debian.org: > close 780941 Bug #780941 [mdadm] mdadm.conf: missing explicit hotplug POLICY Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 780941: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780941

Processed: Re: /usr/share/mdadm/checkarray should not report an error if the MD subsystem is not loaded

Processing commands for cont...@bugs.debian.org: > close 616688 4.1-3 Bug #616688 [mdadm] /usr/share/mdadm/checkarray should not report an error if the MD subsystem is not loaded Marked as fixed in versions mdadm/4.1-3. Bug #616688 [mdadm] /usr/share/mdadm/checkarray should not report an error

Processed: Re: apt updates initramfs incorrectly, breaks RAID/mdadm

Processing commands for cont...@bugs.debian.org: > close 854830 4.2-1 Bug #854830 [mdadm] apt updates initramfs incorrectly, breaks RAID/mdadm Marked as fixed in versions mdadm/4.2-1. Bug #854830 [mdadm] apt updates initramfs incorrectly, breaks RAID/mdadm Marked Bug as done > thanks Stopping

Processed: Re: mdadm destroys my LSI Megaraid software raid

Processing commands for cont...@bugs.debian.org: > close 865976 Bug #865976 [mdadm] mdadm destroys my LSI Megaraid software raid Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 865976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865976

Processed: Re: mdadm: Debian stable system does not boot after kernel upgrade, RAID0 not activated

Processing commands for cont...@bugs.debian.org: > close 954816 4.2-1 Bug #954816 [mdadm] mdadm: Debian stable system does not boot after kernel upgrade, RAID0 not activated Marked as fixed in versions mdadm/4.2-1. Bug #954816 [mdadm] mdadm: Debian stable system does not boot after kernel

Bug#1031801: marked as done (libduktape.so.207: undefined symbol: log2)

Your message dated Sat, 25 Feb 2023 14:35:29 + with message-id and subject line Bug#1031801: fixed in duktape 2.7.0-2 has caused the Debian Bug report #1031801, regarding libduktape.so.207: undefined symbol: log2 to be marked as done. This means that you claim that the problem has been dealt

Bug#1028654: marked as done (dpkg: add loongarch64 architecture GNU triplet)

Your message dated Sat, 25 Feb 2023 14:35:14 + with message-id and subject line Bug#1028654: fixed in dpkg 1.21.21 has caused the Debian Bug report #1028654, regarding dpkg: add loongarch64 architecture GNU triplet to be marked as done. This means that you claim that the problem has been

Bug#1013277: marked as done (opendkim crash)

Your message dated Sat, 25 Feb 2023 15:28:56 +0100 with message-id and subject line opendkim crash has caused the Debian Bug report #1013277, regarding opendkim crash to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your

Processed: Re: mdadm 3.4-4's new initramfs script location broke my system boot

Processing commands for cont...@bugs.debian.org: > close 844652 4.2-1 Bug #844652 [mdadm] mdadm 3.4-4's new initramfs script location broke my system boot Marked as fixed in versions mdadm/4.2-1. Bug #844652 [mdadm] mdadm 3.4-4's new initramfs script location broke my system boot Marked Bug as

Processed: Re: Using mdadm to install Debian on Intel IMSM RAID array stopped working between Wheezy 7.8 and Jessie RC1

Processing commands for cont...@bugs.debian.org: > close 777140 4.2-1 Bug #777140 [mdadm] Using mdadm to install Debian on Intel IMSM RAID array stopped working between Wheezy 7.8 and Jessie RC1 Marked as fixed in versions mdadm/4.2-1. Bug #777140 [mdadm] Using mdadm to install Debian on Intel

Processed: Re: mdadm: raid array always checked during reboot

Processing commands for cont...@bugs.debian.org: > close 812608 4.2-1 Bug #812608 [mdadm] mdadm: raid array always checked during reboot Marked as fixed in versions mdadm/4.2-1. Bug #812608 [mdadm] mdadm: raid array always checked during reboot Marked Bug as done > thanks Stopping processing

Processed: Re: mdadm: maximum of 27 block devices for RAID assembly

Processing commands for cont...@bugs.debian.org: > close 855871 4.2-1 Bug #855871 [mdadm] mdadm: maximum of 27 block devices for RAID assembly Marked as fixed in versions mdadm/4.2-1. Bug #855871 [mdadm] mdadm: maximum of 27 block devices for RAID assembly Marked Bug as done > thanks Stopping

Processed: Re: mdadm: Provide stable update for new efivarfs module name

Processing commands for cont...@bugs.debian.org: > close 995093 Bug #995093 [mdadm] mdadm: Provide stable update for new efivarfs module name Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 995093:

Bug#1031766: marked as done (ValueError: Namespace Handy not available)

Your message dated Sat, 25 Feb 2023 13:34:17 + with message-id and subject line Bug#1031766: fixed in numberstation 1.3.0-1 has caused the Debian Bug report #1031766, regarding ValueError: Namespace Handy not available to be marked as done. This means that you claim that the problem has been

Bug#975383: marked as done (cal3d: Wrong homepage + new version)

Your message dated Sat, 25 Feb 2023 13:34:05 + with message-id and subject line Bug#975383: fixed in cal3d 0.11.0-8 has caused the Debian Bug report #975383, regarding cal3d: Wrong homepage + new version to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1031705: marked as done (pymatgen: 7th item of test_babel randomly hangs autopkgtest)

Your message dated Sat, 25 Feb 2023 13:34:40 + with message-id and subject line Bug#1031705: fixed in pymatgen 2022.11.7+dfsg1-10 has caused the Debian Bug report #1031705, regarding pymatgen: 7th item of test_babel randomly hangs autopkgtest to be marked as done. This means that you claim

Processed: closing 986613, fixed 986613 in 0.9.7-1

Processing commands for cont...@bugs.debian.org: > close 986613 Bug #986613 [kpatch] kpatch: Package quite out of date wrt. to upstream releases (0.6.0 vs 0.9.2) Marked Bug as done > # Obviously fixed in the upload of kpatch 0.9.7-1 to Debian Experimental > fixed 986613 0.9.7-1 Bug #986613

Processed: Re: mdadm should check version to ensure not to corrupt an old array

Processing commands for cont...@bugs.debian.org: > close 534470 4.2-1 Bug #534470 [mdadm] mdadm should check version to ensure not to corrupt an old array Marked as fixed in versions mdadm/4.2-1. Bug #534470 [mdadm] mdadm should check version to ensure not to corrupt an old array Marked Bug as

Bug#1031920: marked as done (upstream-ontologist and lintian-brush need hinting into testing)

Your message dated Sat, 25 Feb 2023 13:53:27 +0100 with message-id and subject line Re: Bug#1031920: upstream-ontologist and lintian-brush need hinting into testing has caused the Debian Bug report #1031920, regarding upstream-ontologist and lintian-brush need hinting into testing to be marked

Processed: bts

Processing commands for cont...@bugs.debian.org: > close 1006464 4.2-2 Bug #1006464 [mdadm] Please use "mdadm monitoring " as default MAILFROM Marked as fixed in versions mdadm/4.2-2. Bug #1006464 [mdadm] Please use "mdadm monitoring " as default MAILFROM Marked Bug as done > thanks Stopping

Bug#1023926: marked as done (Missing dependeny on libavahi-client-dev)

Your message dated Sat, 25 Feb 2023 12:04:07 + with message-id and subject line Bug#1023926: fixed in pappl 1.3.1-2 has caused the Debian Bug report #1023926, regarding Missing dependeny on libavahi-client-dev to be marked as done. This means that you claim that the problem has been dealt

Bug#1031886: marked as done ([INTL:ro] Romanian debconf templates translation of foomatic-filters)

Your message dated Sat, 25 Feb 2023 11:49:03 + with message-id and subject line Bug#1031886: fixed in foomatic-filters 4.0.17-16 has caused the Debian Bug report #1031886, regarding [INTL:ro] Romanian debconf templates translation of foomatic-filters to be marked as done. This means that you

Bug#1031916: marked as done (RFS: foomatic-filters/4.0.17-16 -- OpenPrinting printer support - filters)

Your message dated Sat, 25 Feb 2023 12:44:48 +0100 with message-id <0ed49cbc-87c2-2322-af05-1bafeb19f...@debian.org> and subject line Re: RFS: foomatic-filters/4.0.17-16 -- OpenPrinting printer support - filters has caused the Debian Bug report #1031916, regarding RFS: foomatic-filters/4.0.17-16

Bug#975635: marked as done (wfrench does not require special Rules-Requires-Root handling, revert to "no")

Your message dated Sat, 25 Feb 2023 11:47:32 +0100 with message-id <910a332cbf050c901bea8ba00803c43fde2c9f1a.ca...@praksys.org> and subject line wfrench does not require special Rules-Requires-Root handling, revert to "no" has caused the Debian Bug report #975635, regarding wfrench does not

Bug#912691: marked as done (certmonger FTCBFS: configure.ac hard codes the wrong pkg-config)

Your message dated Sat, 25 Feb 2023 10:49:20 + with message-id and subject line Bug#912691: fixed in certmonger 0.79.17-1 has caused the Debian Bug report #912691, regarding certmonger FTCBFS: configure.ac hard codes the wrong pkg-config to be marked as done. This means that you claim that

Processed: closing 980542

Processing commands for cont...@bugs.debian.org: > close 980542 2.3.1-1 Bug #980542 [cockpit-389-ds] cockpit : 389ds tab is empty and does not appear in installed applications Ignoring request to alter fixed versions of bug #980542 to the same values previously set Bug #980542 [cockpit-389-ds]

Bug#1027965: marked as done (VTK-vtk-module-find-packages.cmake should not require Qt5)

Your message dated Sat, 25 Feb 2023 09:55:15 +0100 with message-id and subject line Re: Bug#1027965: Fix for the RC bug in vtk has caused the Debian Bug report #1027965, regarding VTK-vtk-module-find-packages.cmake should not require Qt5 to be marked as done. This means that you claim that the

Bug#1031908: marked as done (filelight: missing dependency on qml-module-qt-labs-platform)

Your message dated Sat, 25 Feb 2023 08:22:56 + with message-id and subject line Bug#1031908: fixed in filelight 4:22.12.2-2 has caused the Debian Bug report #1031908, regarding filelight: missing dependency on qml-module-qt-labs-platform to be marked as done. This means that you claim that