Bug#1013875: marked as done (lintian: false-postive for experimental-to-unstable-without-comment)

Your message dated Mon, 29 Aug 2022 08:43:29 +0200 with message-id and subject line Accepted lintian 2.115.3 (source) into unstable has caused the Debian Bug report #1013875, regarding lintian: false-postive for experimental-to-unstable-without-comment to be marked as done. This means that you cl

Bug#1018363: marked as done (gallery-dl: build-depends on python3-nose or uses it for autopkgtest)

Your message dated Mon, 29 Aug 2022 06:33:52 + with message-id and subject line Bug#1018363: fixed in gallery-dl 1.23.0-1 has caused the Debian Bug report #1018363, regarding gallery-dl: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim t

Bug#1018686: marked as done (libgtkhex-4-1: cannot be upgraded)

Your message dated Mon, 29 Aug 2022 03:09:00 + with message-id and subject line Bug#1018686: fixed in ghex 43~alpha-3 has caused the Debian Bug report #1018686, regarding libgtkhex-4-1: cannot be upgraded to be marked as done. This means that you claim that the problem has been dealt with. If

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

Your message dated Mon, 29 Aug 2022 03:10:00 + with message-id and subject line Bug#1018452: fixed in pysolar 0.10+repack-1 has caused the Debian Bug report #1018452, regarding pysolar: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim th

Bug#1005924: marked as done (roger-router: bump B-D to librm-dev (>= 2.2.2+really2.2.0))

Your message dated Sun, 28 Aug 2022 18:24:02 -0400 with message-id and subject line Re: roger-router: bump B-D to librm-dev (>= 2.2.2+really2.2.0) has caused the Debian Bug report #1005924, regarding roger-router: bump B-D to librm-dev (>= 2.2.2+really2.2.0) to be marked as done. This means that

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

Your message dated Sun, 28 Aug 2022 21:58:05 + with message-id and subject line Bug#1018450: fixed in pyrfc3339 1.1-4 has caused the Debian Bug report #1018450, regarding pyrfc3339: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim that t

Bug#1014618: marked as done (tpot: FTBFS in unstable)

Your message dated Sun, 28 Aug 2022 20:59:50 + with message-id and subject line Bug#1014618: fixed in tpot 0.11.7+dfsg-4 has caused the Debian Bug report #1014618, regarding tpot: FTBFS in unstable to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1018621: marked as done (ros-catkin-tools: build-depends on python3-nose or uses it for autopkgtest)

Your message dated Sun, 28 Aug 2022 20:55:43 + with message-id and subject line Bug#1018621: fixed in ros-catkin-tools 0.9.0+ds-4 has caused the Debian Bug report #1018621, regarding ros-catkin-tools: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means t

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

Your message dated Sun, 28 Aug 2022 20:51:14 + with message-id and subject line Bug#1018362: fixed in fuzzywuzzy 0.18.0-3 has caused the Debian Bug report #1018362, regarding fuzzywuzzy: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means that you claim t

Bug#1018535: marked as done (python-nameparser: build-depends on python3-nose or uses it for autopkgtest)

Your message dated Sun, 28 Aug 2022 19:35:55 + with message-id and subject line Bug#1018535: fixed in python-nameparser 1.1.1-2 has caused the Debian Bug report #1018535, regarding python-nameparser: build-depends on python3-nose or uses it for autopkgtest to be marked as done. This means th

Bug#1016496: marked as done (nmu: abinit_9.6.2-1)

Your message dated Sun, 28 Aug 2022 21:07:19 +0200 with message-id and subject line Re: Bug#1016496: nmu: abinit_9.6.2-1 has caused the Debian Bug report #1016496, regarding nmu: abinit_9.6.2-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#1015885: marked as done (lz4-java: FTBFS on mips64el, mipsel, armel)

Your message dated Sun, 28 Aug 2022 19:05:22 + with message-id and subject line Bug#1015885: fixed in lz4-java 1.8.0-3 has caused the Debian Bug report #1015885, regarding lz4-java: FTBFS on mips64el, mipsel, armel to be marked as done. This means that you claim that the problem has been deal

Bug#1005429: marked as done (ruby-vcr: FTBFS: ERROR: Test "ruby3.0" failed: RuntimeError:)

Your message dated Sun, 28 Aug 2022 18:43:09 + with message-id and subject line Bug#1005429: fixed in ruby-vcr 6.0.0+really5.0.0-3 has caused the Debian Bug report #1005429, regarding ruby-vcr: FTBFS: ERROR: Test "ruby3.0" failed: RuntimeError: to be marked as done. This means that you claim

Bug#1018266: marked as done (gnome-shell-extension-easyscreencast: needs update for GNOME Shell 43)

Your message dated Sun, 28 Aug 2022 18:38:50 + with message-id and subject line Bug#1018266: fixed in gnome-shell-extension-easyscreencast 1.7.0-1 has caused the Debian Bug report #1018266, regarding gnome-shell-extension-easyscreencast: needs update for GNOME Shell 43 to be marked as done.

Bug#483637: marked as done (Better widescreen support)

Your message dated Sun, 28 Aug 2022 18:10:40 + with message-id and subject line Bug#483637: fixed in uqm 0.8.0+dfsg-1 has caused the Debian Bug report #483637, regarding Better widescreen support to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#640881: marked as done (uqm: upstream version updated to 0.7)

Your message dated Sun, 28 Aug 2022 18:10:40 + with message-id and subject line Bug#640881: fixed in uqm 0.8.0+dfsg-1 has caused the Debian Bug report #640881, regarding uqm: upstream version updated to 0.7 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1014748: marked as done (thunderbird (102.0.1): Launching leads to generic Dash icon named "thunderbird-default")

Your message dated Sun, 28 Aug 2022 18:10:13 + with message-id and subject line Bug#1017420: fixed in thunderbird 1:102.2.0-1 has caused the Debian Bug report #1017420, regarding thunderbird (102.0.1): Launching leads to generic Dash icon named "thunderbird-default" to be marked as done. Thi

Bug#1017420: marked as done (thunderbird: Thunderbird 102.1.1 does not show its own icon in GNOME Wayland)

Your message dated Sun, 28 Aug 2022 18:10:13 + with message-id and subject line Bug#1017420: fixed in thunderbird 1:102.2.0-1 has caused the Debian Bug report #1017420, regarding thunderbird: Thunderbird 102.1.1 does not show its own icon in GNOME Wayland to be marked as done. This means tha

Bug#1014748: marked as done (thunderbird (102.0.1): Launching leads to generic Dash icon named "thunderbird-default")

Your message dated Sun, 28 Aug 2022 18:10:13 + with message-id and subject line Bug#1014748: fixed in thunderbird 1:102.2.0-1 has caused the Debian Bug report #1014748, regarding thunderbird (102.0.1): Launching leads to generic Dash icon named "thunderbird-default" to be marked as done. Thi

Bug#1017420: marked as done (thunderbird: Thunderbird 102.1.1 does not show its own icon in GNOME Wayland)

Your message dated Sun, 28 Aug 2022 18:10:13 + with message-id and subject line Bug#1014748: fixed in thunderbird 1:102.2.0-1 has caused the Debian Bug report #1014748, regarding thunderbird: Thunderbird 102.1.1 does not show its own icon in GNOME Wayland to be marked as done. This means tha

Bug#1010861: marked as done (ITS: uqm, uqm-content)

Your message dated Sun, 28 Aug 2022 18:10:40 + with message-id and subject line Bug#1010861: fixed in uqm 0.8.0+dfsg-1 has caused the Debian Bug report #1010861, regarding ITS: uqm, uqm-content to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1018281: marked as done (calamares: Add accessibility support)

Your message dated Sun, 28 Aug 2022 20:04:34 +0200 with message-id and subject line Re: Bug#1018281: calamares: Add accessibility support has caused the Debian Bug report #1018281, regarding calamares: Add accessibility support to be marked as done. This means that you claim that the problem has

Bug#1018293: marked as done (terminus: needs update for GNOME Shell 43)

Your message dated Sun, 28 Aug 2022 20:02:22 +0200 with message-id and subject line Re: Bug#1018293: terminus: needs update for GNOME Shell 43 has caused the Debian Bug report #1018293, regarding terminus: needs update for GNOME Shell 43 to be marked as done. This means that you claim that the p

Processed: closing 813252

Processing commands for cont...@bugs.debian.org: > tag 813252 + unreproducible Bug #813252 [libgit2-dev] pkg-config --libs libgit2 should include -lhttp_parser too Added tag(s) unreproducible. > close 813252 Bug #813252 [libgit2-dev] pkg-config --libs libgit2 should include -lhttp_parser too Mar

Bug#1015850: marked as done (Updating the gpsprune Uploaders list)

Your message dated Sun, 28 Aug 2022 17:36:33 + with message-id and subject line Bug#1015850: fixed in gpsprune 22-1 has caused the Debian Bug report #1015850, regarding Updating the gpsprune Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#985667: marked as done (pkgconf: make use of personalities to replace the cross wrapper)

Your message dated Sun, 28 Aug 2022 17:00:14 + with message-id and subject line Bug#985667: fixed in pkgconf 1.8.0-2 has caused the Debian Bug report #985667, regarding pkgconf: make use of personalities to replace the cross wrapper to be marked as done. This means that you claim that the pro

Bug#1011722: marked as done (fis-gtm: FTBFS: lke_getcli.c:29:6: error: conflicting types for ‘lke_getcli’; have ‘int4(_Bool *, _Bool *, _Bool *, int4 *, mstr *, mstr *, mstr *, _Bool *, _Bool *, boole

Your message dated Sun, 28 Aug 2022 17:00:11 + with message-id and subject line Bug#1011722: fixed in fis-gtm 7.0-002-1 has caused the Debian Bug report #1011722, regarding fis-gtm: FTBFS: lke_getcli.c:29:6: error: conflicting types for ‘lke_getcli’; have ‘int4(_Bool *, _Bool *, _Bool *, int4

Bug#1012194: marked as done (abseil: tests spuriously fail due to overly restrictive TZ handling)

Your message dated Sun, 28 Aug 2022 17:00:10 + with message-id and subject line Bug#1012194: fixed in abseil 0~20220623.0-1 has caused the Debian Bug report #1012194, regarding abseil: tests spuriously fail due to overly restrictive TZ handling to be marked as done. This means that you claim

Bug#892999: marked as done (Provide pkg-config.multiarch)

Your message dated Sun, 28 Aug 2022 17:00:14 + with message-id and subject line Bug#892999: fixed in pkgconf 1.8.0-2 has caused the Debian Bug report #892999, regarding Provide pkg-config.multiarch to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#1009900: marked as done (fis-gtm: Multiple CVEs in fis-gtm)

Your message dated Sun, 28 Aug 2022 17:00:11 + with message-id and subject line Bug#1009900: fixed in fis-gtm 7.0-002-1 has caused the Debian Bug report #1009900, regarding fis-gtm: Multiple CVEs in fis-gtm to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1008730: marked as done (abseil: Please update to latest upstream version)

Your message dated Sun, 28 Aug 2022 17:00:10 + with message-id and subject line Bug#1008730: fixed in abseil 0~20220623.0-1 has caused the Debian Bug report #1008730, regarding abseil: Please update to latest upstream version to be marked as done. This means that you claim that the problem ha

Bug#1013911: marked as done (linuxcnc-uspace: Please add manual entry for latency-histogram)

Your message dated Sun, 28 Aug 2022 18:56:31 +0200 with message-id and subject line [Debian FTP Masters] Accepted linuxcnc 2.9.0~pre0+git20220827.f7d1c37ffd-1 (source) into unstable has caused the Debian Bug report #1013911, regarding linuxcnc-uspace: Please add manual entry for latency-histogra

Processed: closing 17140

Processing commands for cont...@bugs.debian.org: > close 17140 Bug #17140 [freeciv-server] Saving extra food Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 17140: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=17140 Debian Bug Tracking Syste

Bug#1018245: marked as done (RM: gnome-todo -- RoM; superseded by endeavour)

Your message dated Sun, 28 Aug 2022 15:32:35 + with message-id and subject line Bug#1018245: Removed package(s) from unstable has caused the Debian Bug report #1018245, regarding RM: gnome-todo -- RoM; superseded by endeavour to be marked as done. This means that you claim that the problem ha

Bug#1018237: marked as done (RM: proj-rdnap -- ROM; Obsolete)

Your message dated Sun, 28 Aug 2022 15:31:06 + with message-id and subject line Bug#1018237: Removed package(s) from unstable has caused the Debian Bug report #1018237, regarding RM: proj-rdnap -- ROM; Obsolete to be marked as done. This means that you claim that the problem has been dealt wi

Bug#998611: marked as done (rust-tokio-executor: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.19-~~))

Your message dated Sun, 28 Aug 2022 15:23:03 + with message-id and subject line Bug#1012380: Removed package(s) from unstable has caused the Debian Bug report #998611, regarding rust-tokio-executor: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.19-~~) to be

Bug#998570: marked as done (rust-tokio-io: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.18-~~))

Your message dated Sun, 28 Aug 2022 15:24:03 + with message-id and subject line Bug#1012380: Removed package(s) from unstable has caused the Debian Bug report #998570, regarding rust-tokio-io: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.18-~~) to be marked

Bug#998543: marked as done (rust-tokio-sync: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.19-~~))

Your message dated Sun, 28 Aug 2022 15:25:14 + with message-id and subject line Bug#1012380: Removed package(s) from unstable has caused the Debian Bug report #998543, regarding rust-tokio-sync: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.19-~~) to be mark

Bug#952137: marked as done (rust-tokio-core: FTBFS: build-dependency not installable: librust-scoped-tls-0.1+default-dev)

Your message dated Sun, 28 Aug 2022 15:20:29 + with message-id and subject line Bug#1012380: Removed package(s) from unstable has caused the Debian Bug report #952137, regarding rust-tokio-core: FTBFS: build-dependency not installable: librust-scoped-tls-0.1+default-dev to be marked as done.

Bug#998552: marked as done (rust-tokio-buf: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.23-~~))

Your message dated Sun, 28 Aug 2022 15:19:35 + with message-id and subject line Bug#1012380: Removed package(s) from unstable has caused the Debian Bug report #998552, regarding rust-tokio-buf: FTBFS: build-dependency not installable: librust-futures-0.1+default-dev (>= 0.1.23-~~) to be marke

Bug#1018259: marked as done (nmu: libidn2_2.3.3-1)

Your message dated Sun, 28 Aug 2022 17:17:22 +0200 with message-id and subject line Re: Bug#1018259: nmu: libidn2_2.3.3-1 has caused the Debian Bug report #1018259, regarding nmu: libidn2_2.3.3-1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#1017705: marked as done (transition: benchmark)

Your message dated Sun, 28 Aug 2022 17:18:04 +0200 with message-id and subject line Re: Bug#1017705: transition: benchmark has caused the Debian Bug report #1017705, regarding transition: benchmark to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1016871: marked as done (transition: dpdk)

Your message dated Sun, 28 Aug 2022 17:19:13 +0200 with message-id and subject line Re: Bug#1016871: transition: dpdk has caused the Debian Bug report #1016871, regarding transition: dpdk to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case

Bug#1012380: marked as done (RM: obsolete rust-tokio-* packages)

Your message dated Sun, 28 Aug 2022 15:19:32 + with message-id and subject line Bug#1012380: Removed package(s) from unstable has caused the Debian Bug report #1012380, regarding RM: obsolete rust-tokio-* packages to be marked as done. This means that you claim that the problem has been dealt

Bug#1018287: marked as done (python3-requests-cache: The "pip3 check" complains dependency of the attr module.)

Your message dated Sun, 28 Aug 2022 11:04:49 -0400 with message-id and subject line Re: Bug#1018287: python3-requests-cache: The "pip3 check" complains dependency of the attr module. has caused the Debian Bug report #1018287, regarding python3-requests-cache: The "pip3 check" complains dependen

Bug#995492: marked as done (lintian: Broken --fails-on=none as default never got reverted)

Your message dated Sun, 28 Aug 2022 14:51:11 + with message-id and subject line Bug#995492: fixed in lintian 2.115.3 has caused the Debian Bug report #995492, regarding lintian: Broken --fails-on=none as default never got reverted to be marked as done. This means that you claim that the probl

Bug#996837: marked as done (lintian displays errors when checking webpack 5.58)

Your message dated Sun, 28 Aug 2022 14:51:11 + with message-id and subject line Bug#993613: fixed in lintian 2.115.3 has caused the Debian Bug report #993613, regarding lintian displays errors when checking webpack 5.58 to be marked as done. This means that you claim that the problem has been

Bug#1014254: marked as done (lintian: Complex regular subexpression recursion limit (65534) exceeded at /usr/share/lintian/lib/Lintian/Check/Cruft.pm line 449.)

Your message dated Sun, 28 Aug 2022 14:51:11 + with message-id and subject line Bug#993613: fixed in lintian 2.115.3 has caused the Debian Bug report #993613, regarding lintian: Complex regular subexpression recursion limit (65534) exceeded at /usr/share/lintian/lib/Lintian/Check/Cruft.pm lin

Bug#993613: marked as done (lintian: Complex regular subexpression recursion limit exceeded in cruft check)

Your message dated Sun, 28 Aug 2022 14:51:11 + with message-id and subject line Bug#993613: fixed in lintian 2.115.3 has caused the Debian Bug report #993613, regarding lintian: Complex regular subexpression recursion limit exceeded in cruft check to be marked as done. This means that you cl

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

Your message dated Sun, 28 Aug 2022 14:51:54 + with message-id and subject line Bug#1010120: fixed in thrift 0.16.0-6 has caused the Debian Bug report #1010120, regarding thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2 to be mar

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

Your message dated Sun, 28 Aug 2022 14:51:54 + with message-id and subject line Bug#1015049: fixed in thrift 0.16.0-6 has caused the Debian Bug report #1015049, regarding thrift: FTBFS: dh_auto_test: error: make -j1 check "TESTSUITEFLAGS=-j1 --verbose" VERBOSE=1 returned exit code 2 to be mar

Bug#1014156: marked as done (lintian: very-long-line-length-in-source-file for non-text source files)

Your message dated Sun, 28 Aug 2022 14:51:11 + with message-id and subject line Bug#1014156: fixed in lintian 2.115.3 has caused the Debian Bug report #1014156, regarding lintian: very-long-line-length-in-source-file for non-text source files to be marked as done. This means that you claim t

Bug#993132: marked as done (python3-fife: prints "is"/"is not" used-with-a-literal warnings at install time)

Your message dated Sun, 28 Aug 2022 14:43:34 + with message-id and subject line Bug#993132: fixed in fife 0.4.2-5 has caused the Debian Bug report #993132, regarding python3-fife: prints "is"/"is not" used-with-a-literal warnings at install time to be marked as done. This means that you clai

Processed: closing 719236

Processing commands for cont...@bugs.debian.org: > close 719236 Bug #719236 [dh-python] dh-python: shebang rewriting can't ignore paths with -X Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 719236: https://bugs.debian.org/cgi-bin/bugreport.cgi

Bug#1017268: marked as done (golang-go4: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 go4.org/bytereplacer go4.org/cloud/cloudlaunch go4.org/cloud/google/gceutil go4

Your message dated Sun, 28 Aug 2022 13:36:08 + with message-id and subject line Bug#1017268: fixed in golang-go4 0.0~git20201209.d4a0794-1 has caused the Debian Bug report #1017268, regarding golang-go4: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && go test -vet=off -v -p 8 go4.org/b

Bug#1016321: marked as done (boost1.74: FTBFS: runtime error: file /<>/tools/boostbook/xsl/annotation.xsl line 432 element element xsl:element: The effective name '' is not a valid QName.

Your message dated Sun, 28 Aug 2022 12:51:27 + with message-id and subject line Bug#1016321: fixed in boost1.74 1.74.0-17 has caused the Debian Bug report #1016321, regarding boost1.74: FTBFS: runtime error: file /<>/tools/boostbook/xsl/annotation.xsl line 432 element element xsl:element: Th

Bug#1015998: marked as done (boost1.74: shlibs don't generate *-py310 dependencies with Python 3.10)

Your message dated Sun, 28 Aug 2022 12:51:27 + with message-id and subject line Bug#1015998: fixed in boost1.74 1.74.0-17 has caused the Debian Bug report #1015998, regarding boost1.74: shlibs don't generate *-py310 dependencies with Python 3.10 to be marked as done. This means that you claim

Bug#1005442: marked as done (ruby-em-http-request: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Sun, 28 Aug 2022 12:29:29 + with message-id and subject line Bug#1005442: fixed in ruby-em-http-request 1.1.7-1 has caused the Debian Bug report #1005442, regarding ruby-em-http-request: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as

Bug#1006985: marked as done (ruby-em-http-request: autopkgtest regression: timeout)

Your message dated Sun, 28 Aug 2022 12:29:29 + with message-id and subject line Bug#1006985: fixed in ruby-em-http-request 1.1.7-1 has caused the Debian Bug report #1006985, regarding ruby-em-http-request: autopkgtest regression: timeout to be marked as done. This means that you claim that th

Processed: closing 866931, tagging 631775, tagging 605543, tagging 118128, closing 118128

Processing commands for cont...@bugs.debian.org: > close 866931 Bug #866931 [freeciv-server] freeciv-server: Please build server with mysql support Marked Bug as done > tags 631775 + upstream fixed-upstream Bug #631775 [freeciv-client-gtk] freeciv-client-gtk: messages box forgets its contents Ad

Bug#991057: marked as done (gri FTBFS with imagemagick with the #987504 change)

Your message dated Sun, 28 Aug 2022 12:02:09 + with message-id and subject line Bug#991057: fixed in gri 2.12.27-1.1~deb11u1 has caused the Debian Bug report #991057, regarding gri FTBFS with imagemagick with the #987504 change to be marked as done. This means that you claim that the problem

Bug#1015740: marked as done (libc6: Include patch to make grantpt usable after multi-threaded fork in more cases)

Your message dated Sun, 28 Aug 2022 12:02:08 + with message-id and subject line Bug#1015740: fixed in glibc 2.31-13+deb11u4 has caused the Debian Bug report #1015740, regarding libc6: Include patch to make grantpt usable after multi-threaded fork in more cases to be marked as done. This mean

Bug#1014735: marked as done (rpcsvc-proto: The /usr/include/rpc/* files is not included)

Your message dated Sun, 28 Aug 2022 12:02:08 + with message-id and subject line Bug#1014735: fixed in glibc 2.31-13+deb11u4 has caused the Debian Bug report #1014735, regarding rpcsvc-proto: The /usr/include/rpc/* files is not included to be marked as done. This means that you claim that the

Bug#1014534: marked as done (dlt-daemon: CVE-2022-31291)

Your message dated Sun, 28 Aug 2022 12:02:08 + with message-id and subject line Bug#1014534: fixed in dlt-daemon 2.18.6-1+deb11u1 has caused the Debian Bug report #1014534, regarding dlt-daemon: CVE-2022-31291 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1013342: marked as done (systemd - Please backport support for Hyper-V on arm64 to stable)

Your message dated Sun, 28 Aug 2022 12:02:09 + with message-id and subject line Bug#1013342: fixed in systemd 247.3-7+deb11u1 has caused the Debian Bug report #1013342, regarding systemd - Please backport support for Hyper-V on arm64 to stable to be marked as done. This means that you claim t

Bug#983228: marked as done (unknown-horizons: Syntax warning while installing update)

Your message dated Sun, 28 Aug 2022 11:36:05 + with message-id and subject line Bug#983228: fixed in unknown-horizons 2019.1-5 has caused the Debian Bug report #983228, regarding unknown-horizons: Syntax warning while installing update to be marked as done. This means that you claim that the

Bug#1018167: marked as done (gettext: FTBFS on hurd-i386)

Your message dated Sun, 28 Aug 2022 13:35:38 +0200 with message-id <20220828113538.smbicdm4fvpn4vn7@begin> and subject line Re: Bug#1018167: gettext: FTBFS on hurd-i386 has caused the Debian Bug report #1018167, regarding gettext: FTBFS on hurd-i386 to be marked as done. This means that you claim

Bug#1014084: marked as done (unknown-horizons: Crashes with "AttributeError: module 'collections' has no attribute 'Iterable'")

Your message dated Sun, 28 Aug 2022 11:36:05 + with message-id and subject line Bug#1014084: fixed in unknown-horizons 2019.1-5 has caused the Debian Bug report #1014084, regarding unknown-horizons: Crashes with "AttributeError: module 'collections' has no attribute 'Iterable'" to be marked a

Processed: Re: Carriers can deadlock stoping delivery and removal of goods

Processing control commands: > forwarded -1 https://github.com/widelands/widelands/issues/2309 Bug #671719 [widelands] Carriers can deadlock stoping delivery and removal of goods Changed Bug forwarded-to-address to 'https://github.com/widelands/widelands/issues/2309' from 'https://bugs.launchpa

Processed: fixed 492323 in 2:1.0-1, closing 492323

Processing commands for cont...@bugs.debian.org: > fixed 492323 2:1.0-1 Bug #492323 [widelands] [widelands] option to disable (most of the) output Marked as fixed in versions widelands/2:1.0-1. > close 492323 Bug #492323 [widelands] [widelands] option to disable (most of the) output Marked Bug as

Bug#1017791: marked as done (valgrind: does not support rseq syscall)

Your message dated Sun, 28 Aug 2022 11:21:08 + with message-id and subject line Bug#1017791: fixed in valgrind 1:3.19.0-1 has caused the Debian Bug report #1017791, regarding valgrind: does not support rseq syscall to be marked as done. This means that you claim that the problem has been deal

Bug#997015: marked as done (valgrind: Please remove x32 from the architecture list)

Your message dated Sun, 28 Aug 2022 11:21:08 + with message-id and subject line Bug#997015: fixed in valgrind 1:3.19.0-1 has caused the Debian Bug report #997015, regarding valgrind: Please remove x32 from the architecture list to be marked as done. This means that you claim that the problem

Bug#1018283: marked as done (gnome-shell-extension-vertical-overview: needs update for GNOME Shell 43)

Your message dated Sun, 28 Aug 2022 11:18:49 + with message-id and subject line Bug#1018283: fixed in gnome-shell-extension-vertical-overview 9-2 has caused the Debian Bug report #1018283, regarding gnome-shell-extension-vertical-overview: needs update for GNOME Shell 43 to be marked as done

Processed: tagging 852230, closing 852230

Processing commands for cont...@bugs.debian.org: > tags 852230 + wontfix Bug #852230 [unknown-horizons] unknown-horizons: have another program where dependencies are sorted out for unknown-horizons. Added tag(s) wontfix. > close 852230 Bug #852230 [unknown-horizons] unknown-horizons: have another

Bug#1014414: marked as done (xen: New unreleased upstream fixes for 6 vulnerabilities in testing/unstable)

Your message dated Sun, 28 Aug 2022 12:59:52 +0200 with message-id <2976148.Z1ClUSbBXi@prancing-pony> and subject line Re: Fixed in version 4.16.2-1 has caused the Debian Bug report #1014414, regarding xen: New unreleased upstream fixes for 6 vulnerabilities in testing/unstable to be marked as don

Bug#1017890: marked as done (Ships autogenerated files that can't be renegerated with the code in Debian main)

Your message dated Sun, 28 Aug 2022 10:49:10 + with message-id and subject line Bug#1017890: fixed in gobject-introspection 1.73.0+ds-1 has caused the Debian Bug report #1017890, regarding Ships autogenerated files that can't be renegerated with the code in Debian main to be marked as done.

Bug#992036: marked as done (freeradius 3.0.x crashes with "attempting double-free")

Your message dated Sun, 28 Aug 2022 10:47:29 + with message-id and subject line Bug#992036: fixed in freeradius 3.0.17+dfsg-1.1+deb10u1 has caused the Debian Bug report #992036, regarding freeradius 3.0.x crashes with "attempting double-free" to be marked as done. This means that you claim th

Bug#991649: marked as done (libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2)

Your message dated Sun, 28 Aug 2022 10:47:30 + with message-id and subject line Bug#991649: fixed in libhttp-cookiejar-perl 0.008-1+deb10u1 has caused the Debian Bug report #991649, regarding libhttp-cookiejar-perl: FTBFS: dh_auto_test: error: make -j4 test TEST_VERBOSE=1 returned exit code 2

Bug#991089: marked as done (libnet-freedb-perl: Defaults to defunct freedb.freedb.org)

Your message dated Sun, 28 Aug 2022 10:47:30 + with message-id and subject line Bug#991089: fixed in libnet-freedb-perl 0.10-2~deb10u1 has caused the Debian Bug report #991089, regarding libnet-freedb-perl: Defaults to defunct freedb.freedb.org to be marked as done. This means that you claim

Bug#990123: marked as done ([buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration of function ‘ref_module’" (Upstream kernel API regression in 4.

Your message dated Sun, 28 Aug 2022 10:47:30 + with message-id and subject line Bug#990123: fixed in iptables-netflow 2.3-5+deb10u1 has caused the Debian Bug report #990123, regarding [buster regression] iptables-netflow-dkms: No more compiles since linux-*-4.19.0-17-*: "implicit declaration

Bug#982804: marked as done (libvirt_node_get_cpu_stats segmentation fault)

Your message dated Sun, 28 Aug 2022 10:47:31 + with message-id and subject line Bug#982804: fixed in libvirt-php 0.5.4-3+deb10u1 has caused the Debian Bug report #982804, regarding libvirt_node_get_cpu_stats segmentation fault to be marked as done. This means that you claim that the problem h

Bug#988028: marked as done (ruby-riddle FTBFS in buster: Mysql2::Error: Load data local infile forbidden)

Your message dated Sun, 28 Aug 2022 10:47:32 + with message-id and subject line Bug#988028: fixed in ruby-riddle 2.3.1-2~deb10u1 has caused the Debian Bug report #988028, regarding ruby-riddle FTBFS in buster: Mysql2::Error: Load data local infile forbidden to be marked as done. This means t

Bug#978208: marked as done (gnucash: FTBFS: test failed)

Your message dated Sun, 28 Aug 2022 10:47:29 + with message-id and subject line Bug#978208: fixed in gnucash 1:3.4-1+deb10u1 has caused the Debian Bug report #978208, regarding gnucash: FTBFS: test failed to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#971161: marked as done (evemu: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2)

Your message dated Sun, 28 Aug 2022 10:47:29 + with message-id and subject line Bug#971161: fixed in evemu 2.7.0-1+deb10u1 has caused the Debian Bug report #971161, regarding evemu: FTBFS: dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2 to be marked as done. This means tha

Bug#962627: marked as done (eboard: playing against crafty causes "*** buffer overflow detected ***: eboard terminated")

Your message dated Sun, 28 Aug 2022 10:47:28 + with message-id and subject line Bug#962627: fixed in eboard 1.1.3-0.4~deb10u1 has caused the Debian Bug report #962627, regarding eboard: playing against crafty causes "*** buffer overflow detected ***: eboard terminated" to be marked as done.

Bug#954305: marked as done (python-udatetime: shared library is not properly linked with libm)

Your message dated Sun, 28 Aug 2022 10:47:32 + with message-id and subject line Bug#954305: fixed in python-udatetime 0.0.16-1+deb10u1 has caused the Debian Bug report #954305, regarding python-udatetime: shared library is not properly linked with libm to be marked as done. This means that yo

Bug#962482: marked as done (FTBFS: test failure in t/db-object-manager.t)

Your message dated Sun, 28 Aug 2022 10:47:31 + with message-id and subject line Bug#962482: fixed in librose-db-object-perl 1:0.815-1+deb10u1 has caused the Debian Bug report #962482, regarding FTBFS: test failure in t/db-object-manager.t to be marked as done. This means that you claim that t

Bug#953539: marked as done (test fails in current unstable during the build)

Your message dated Sun, 28 Aug 2022 10:47:31 + with message-id and subject line Bug#953539: fixed in python-udatetime 0.0.16-1+deb10u1 has caused the Debian Bug report #953539, regarding test fails in current unstable during the build to be marked as done. This means that you claim that the p

Bug#934081: marked as done (esorex: testsuite failures on armhf/riscv64 due to wrong usage of ffi_prep_cif)

Your message dated Sun, 28 Aug 2022 10:47:28 + with message-id and subject line Bug#934081: fixed in esorex 3.13.1-1+deb10u1 has caused the Debian Bug report #934081, regarding esorex: testsuite failures on armhf/riscv64 due to wrong usage of ffi_prep_cif to be marked as done. This means tha

Bug#893206: marked as done (CPL not usable with Python on armhf and ppc64el)

Your message dated Sun, 28 Aug 2022 10:47:28 + with message-id and subject line Bug#893206: fixed in esorex 3.13.1-1+deb10u1 has caused the Debian Bug report #893206, regarding CPL not usable with Python on armhf and ppc64el to be marked as done. This means that you claim that the problem has

Bug#1017620: marked as done (opencascade-draw-7.6: Depends on -dev packages needed?)

Your message dated Sun, 28 Aug 2022 10:36:28 + with message-id and subject line Bug#1017620: fixed in opencascade 7.6.3+dfsg1-3 has caused the Debian Bug report #1017620, regarding opencascade-draw-7.6: Depends on -dev packages needed? to be marked as done. This means that you claim that the

Bug#1018222: marked as done (hydapaper: Missing depdencies)

Your message dated Sun, 28 Aug 2022 10:04:17 + with message-id and subject line Bug#1018222: fixed in hydrapaper 3.3.1-2 has caused the Debian Bug report #1018222, regarding hydapaper: Missing depdencies to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: RFS: mazeofgalious/0.63+dfsg1-1 [ITA] -- The Maze of Galious

Processing commands for cont...@bugs.debian.org: > close 994750 Bug #994750 [sponsorship-requests] RFS: mazeofgalious/0.63+dfsg1-1 [ITA] -- The Maze of Galious Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 994750: https://bugs.debian.org/cgi-bi