Bug#881965: marked as done (nheko: manual page is missing)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 07:43:27 +0100 with message-id and subject line MR was merged has caused the Debian Bug report #881965, regarding nheko: manual page is missing 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 n

Bug#1034088: marked as done (cyrus-imapd: fails to clean after successful build: No rule to make target 'Makefile.PL', needed by 'Makefile'.)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 04:34:19 + with message-id and subject line Bug#1034088: fixed in cyrus-imapd 3.8.0~rc1-1 has caused the Debian Bug report #1034088, regarding cyrus-imapd: fails to clean after successful build: No rule to make target 'Makefile.PL', needed by 'Makefile'. to

Processed: closing 997084

2023-04-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 997084 Bug #997084 [src:node-handlebars] node-handlebars: FTBFS: build hangs Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 997084: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=99708

Bug#1034945: marked as done (node-npm-run-path: missing Breaks+Replaces for node-execa when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:33:55 + with message-id and subject line Bug#1034945: fixed in node-npm-run-path 5.1.0+~4.0.0-8 has caused the Debian Bug report #1034945, regarding node-npm-run-path: missing Breaks+Replaces for node-execa when upgrading from bullseye to be marked as do

Bug#1034933: marked as done (node-whatwg-fetch: missing Breaks+Replaces for libjs-fetch when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:34:10 + with message-id and subject line Bug#1034933: fixed in node-whatwg-fetch 3.6.2-7 has caused the Debian Bug report #1034933, regarding node-whatwg-fetch: missing Breaks+Replaces for libjs-fetch when upgrading from bullseye to be marked as done. T

Bug#1035008: marked as done (node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:19:54 + with message-id and subject line Bug#1035008: fixed in node-jest 29.3.1~ds1+~cs70.48.25-2 has caused the Debian Bug report #1035008, regarding node-jest-worker: missing Breaks+Replaces for jest when upgrading from bullseye to be marked as done.

Bug#1035000: marked as done (node-core-js-pure: missing Breaks+Replaces for node-core-js when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1035000: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1035000, regarding node-core-js-pure: missing Breaks+Replaces for node-core-js when upgrading from bullseye to be marked as done. This

Bug#1034989: marked as done (node-core-js-bundle: missing Breaks+Replaces for node-core-js when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1034989: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1034989, regarding node-core-js-bundle: missing Breaks+Replaces for node-core-js when upgrading from bullseye to be marked as done. Th

Bug#1034924: marked as done (node-strip-eof: missing Breaks+Replaces for node-execa when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:20:09 + with message-id and subject line Bug#1034924: fixed in node-strip-eof 3.0.0-5 has caused the Debian Bug report #1034924, regarding node-strip-eof: missing Breaks+Replaces for node-execa when upgrading from bullseye to be marked as done. This mea

Bug#1034984: marked as done (node-parse5-htmlparser2-tree-adapter: missing Breaks+Replaces for node-cheerio when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:20:02 + with message-id and subject line Bug#1034984: fixed in node-parse5 7.1.2+dfsg-2 has caused the Debian Bug report #1034984, regarding node-parse5-htmlparser2-tree-adapter: missing Breaks+Replaces for node-cheerio when upgrading from bullseye to be

Bug#1034980: marked as done (node-core-js-builder: missing Breaks+Replaces for node-core-js when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1034980: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1034980, regarding node-core-js-builder: missing Breaks+Replaces for node-core-js when upgrading from bullseye to be marked as done. T

Bug#1034947: marked as done (node-core-js-compat: missing Breaks+Replaces for node-core-js when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 03:19:08 + with message-id and subject line Bug#1034947: fixed in node-core-js 3.26.1-2 has caused the Debian Bug report #1034947, regarding node-core-js-compat: missing Breaks+Replaces for node-core-js when upgrading from bullseye to be marked as done. Th

Bug#1034347: marked as done (spamd timeout after reboot: dns: bad dns reply: bgread: recv() failed)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Fri, 28 Apr 2023 00:34:30 + with message-id and subject line Bug#1034347: fixed in spamassassin 4.0.0-5 has caused the Debian Bug report #1034347, regarding spamd timeout after reboot: dns: bad dns reply: bgread: recv() failed to be marked as done. This means that you claim

Bug#1034997: marked as done (libdtkcommon: missing Breaks+Replaces for libdtkcore5 when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 23:33:47 + with message-id and subject line Bug#1034997: fixed in dtkcommon 5.5.23-2 has caused the Debian Bug report #1034997, regarding libdtkcommon: missing Breaks+Replaces for libdtkcore5 when upgrading from bullseye to be marked as done. This means th

Bug#1034923: marked as done (libdtkcommon-dev: missing Breaks+Replaces for libdtkcore-dev when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 23:33:47 + with message-id and subject line Bug#1034923: fixed in dtkcommon 5.5.23-2 has caused the Debian Bug report #1034923, regarding libdtkcommon-dev: missing Breaks+Replaces for libdtkcore-dev when upgrading from bullseye to be marked as done. This m

Bug#1034228: marked as done (zcfan: dh_installsystemd doesn't handle files in /usr/lib/systemd/system)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 22:19:41 + with message-id and subject line Bug#1034228: fixed in zcfan 1.2.1-2 has caused the Debian Bug report #1034228, regarding zcfan: dh_installsystemd doesn't handle files in /usr/lib/systemd/system to be marked as done. This means that you claim th

Bug#1032418: marked as done (zcfan service is not stopped on package removal)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 22:19:41 + with message-id and subject line Bug#1032418: fixed in zcfan 1.2.1-2 has caused the Debian Bug report #1032418, regarding zcfan service is not stopped on package removal to be marked as done. This means that you claim that the problem has been de

Bug#1017980: marked as done (zcfan should "Conflicts: thinkfan")

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 22:19:41 + with message-id and subject line Bug#1017980: fixed in zcfan 1.2.1-2 has caused the Debian Bug report #1017980, regarding zcfan should "Conflicts: thinkfan" to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1021490: marked as done (bookworm: please mention users must migrate off dmraid)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 22:03:43 +0200 with message-id <30d1f26e-7eff-a354-6942-2dca95a4c...@debian.org> and subject line Re: Bug#1021490: bookworm: please mention users must migrate off dmraid has caused the Debian Bug report #1021490, regarding bookworm: please mention users must mig

Bug#741537: marked as done (pssh: IPv6 host address processing broken)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 19:48:57 + with message-id and subject line Bug#741537: fixed in pssh 2.3.5-1 has caused the Debian Bug report #741537, regarding pssh: IPv6 host address processing broken to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1034634: marked as done (unblock: freetype/2.12.1+dfsg-5)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 21:38:50 +0200 with message-id <8dd0a695-32f3-4162-4ea9-c9ee0b8a9...@debian.org> and subject line Re: Bug#1034634: unblock: freetype/2.12.1+dfsg-5 has caused the Debian Bug report #1034634, regarding unblock: freetype/2.12.1+dfsg-5 to be marked as done. This mea

Bug#870200: marked as done (mariadb-server-10.1: jessie --> stretch: starting mariadb impossible (Failed at step NAMESPACE spawning /usr/bin/install: Value too large for defined data type))

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 20:59:46 +0200 with message-id <7d6f11c3-b3d0-46e8-c7e0-c6ac99109...@debian.org> and subject line mariadb-10.1 has been removed from Debian has caused the Debian Bug report #870200, regarding mariadb-server-10.1: jessie --> stretch: starting mariadb impossible (

Bug#887007: marked as done (my.cnf handling collides with MySQL)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 20:59:46 +0200 with message-id <7d6f11c3-b3d0-46e8-c7e0-c6ac99109...@debian.org> and subject line mariadb-10.1 has been removed from Debian has caused the Debian Bug report #887007, regarding my.cnf handling collides with MySQL to be marked as done. This means t

Bug#865534: marked as done (mariadb-server-10.1 apparmor: upgrade from jessie)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 20:59:46 +0200 with message-id <7d6f11c3-b3d0-46e8-c7e0-c6ac99109...@debian.org> and subject line mariadb-10.1 has been removed from Debian has caused the Debian Bug report #865534, regarding mariadb-server-10.1 apparmor: upgrade from jessie to be marked as done.

Bug#873460: marked as done (mariadb-server-10.1: Updates not restarting mariadb@xx services)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 20:59:46 +0200 with message-id <7d6f11c3-b3d0-46e8-c7e0-c6ac99109...@debian.org> and subject line mariadb-10.1 has been removed from Debian has caused the Debian Bug report #873460, regarding mariadb-server-10.1: Updates not restarting mariadb@xx services to be m

Bug#864943: marked as done (mariadb-server-10.1: Starting mariadb service does not terminate)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 20:59:46 +0200 with message-id <7d6f11c3-b3d0-46e8-c7e0-c6ac99109...@debian.org> and subject line mariadb-10.1 has been removed from Debian has caused the Debian Bug report #864943, regarding mariadb-server-10.1: Starting mariadb service does not terminate to be

Bug#1034764: marked as done (unblock: spf-engine/3.0.4-1)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 19:31:01 +0200 with message-id and subject line Re: Bug#1034764: unblock: spf-engine/3.0.4-1 has caused the Debian Bug report #1034764, regarding unblock: spf-engine/3.0.4-1 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1034899: marked as done (unblock: sssd/2.8.2-4)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 19:25:36 +0200 with message-id <2263393c-aff8-6392-6722-dd6fbb615...@debian.org> and subject line Re: Bug#1034899: unblock: sssd/2.8.2-4 has caused the Debian Bug report #1034899, regarding unblock: sssd/2.8.2-4 to be marked as done. This means that you claim th

Bug#1012838: marked as done (grub-pc: updating grub-pc in offline mode on reboot does not add other OS entries like Windows 10)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 18:15:50 +0100 with message-id <20230427171550.go812...@tack.einval.com> and subject line Re: Bug#1012838: Bug closed? has caused the Debian Bug report #1012838, regarding grub-pc: updating grub-pc in offline mode on reboot does not add other OS entries like Win

Bug#1034898: marked as done (unblock: speech-dispatcher-contrib/0.11.4-3)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 19:05:47 +0200 with message-id <3c56e81d-f71c-c59a-c17d-dc3b6b1fe...@debian.org> and subject line Re: Bug#1034898: unblock: speech-dispatcher-contrib/0.11.4-3 has caused the Debian Bug report #1034898, regarding unblock: speech-dispatcher-contrib/0.11.4-3 to be m

Bug#1034664: marked as done (unblock: node-xml2js/0.4.23+~cs15.4.0+dfsg-5)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 19:02:34 +0200 with message-id and subject line Re: Bug#1034664: unblock: node-xml2js/0.4.23+~cs15.4.0+dfsg-5 has caused the Debian Bug report #1034664, regarding unblock: node-xml2js/0.4.23+~cs15.4.0+dfsg-5 to be marked as done. This means that you claim that

Bug#911665: marked as done (dkms: how to *not* attempt to build a module for a known unsupported kernel?)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 16:36:18 + with message-id and subject line Bug#911665: fixed in dkms 3.0.11-1 has caused the Debian Bug report #911665, regarding dkms: how to *not* attempt to build a module for a known unsupported kernel? to be marked as done. This means that you claim

Bug#741399: marked as done (dkms: consider avoiding unnecessary rpm commands)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 16:36:18 + with message-id and subject line Bug#741399: fixed in dkms 3.0.11-1 has caused the Debian Bug report #741399, regarding dkms: consider avoiding unnecessary rpm commands to be marked as done. This means that you claim that the problem has been dea

Bug#1031561: marked as done (BUILD_EXCLUSIVE option errors out on non-matching kernels)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 16:36:18 + with message-id and subject line Bug#1031561: fixed in dkms 3.0.11-1 has caused the Debian Bug report #1031561, regarding BUILD_EXCLUSIVE option errors out on non-matching kernels to be marked as done. This means that you claim that the problem h

Bug#1034957: marked as done (qtxdg-tools: missing Breaks+Replaces for qtxdg-dev-tools when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 16:37:31 + with message-id and subject line Bug#1034957: fixed in qtxdg-tools 3.10.0-2 has caused the Debian Bug report #1034957, regarding qtxdg-tools: missing Breaks+Replaces for qtxdg-dev-tools when upgrading from bullseye to be marked as done. This mea

Bug#1035015: marked as done (Mail list requests failing with Recipient address rejected)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 17:32:11 +0100 with message-id and subject line Re: Bug#1035015: Mail list requests failing with Recipient address rejected has caused the Debian Bug report #1035015, regarding Mail list requests failing with Recipient address rejected to be marked as done. T

Bug#1034962: marked as done (libg2c-dev: missing Breaks+Replaces for libgrib2c-dev when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 15:49:07 + with message-id and subject line Bug#1034962: fixed in g2clib 1.7.0-3 has caused the Debian Bug report #1034962, regarding libg2c-dev: missing Breaks+Replaces for libgrib2c-dev when upgrading from bullseye to be marked as done. This means that y

Bug#1034942: marked as done (pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 15:06:35 + with message-id and subject line Bug#1034942: fixed in pdl 1:2.081-2 has caused the Debian Bug report #1034942, regarding pdl: missing Breaks+Replaces for libpdl-stats-perl when upgrading from bullseye to be marked as done. This means that you c

Bug#1034659: marked as done (freeipa-client: IPA client Kerberos configuration incompatible with java)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 14:49:32 + with message-id and subject line Bug#1034659: fixed in freeipa 4.9.11-2 has caused the Debian Bug report #1034659, regarding freeipa-client: IPA client Kerberos configuration incompatible with java to be marked as done. This means that you claim

Bug#1034972: marked as done (python3-hfst: missing Breaks+Replaces for python3-libhfst when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 14:34:44 + with message-id and subject line Bug#1034972: fixed in hfst 3.16.0-5 has caused the Debian Bug report #1034972, regarding python3-hfst: missing Breaks+Replaces for python3-libhfst when upgrading from bullseye to be marked as done. This means tha

Bug#1035001: marked as done (wbar: missing Breaks+Replaces for wbar-config when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 14:37:37 + with message-id and subject line Bug#1035001: fixed in wbar 2.3.4-13 has caused the Debian Bug report #1035001, regarding wbar: missing Breaks+Replaces for wbar-config when upgrading from bullseye to be marked as done. This means that you claim

Bug#1034956: marked as done (libeztrace0: missing Breaks+Replaces for libeztrace-dev when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 14:34:17 + with message-id and subject line Bug#1034956: fixed in eztrace 2.0+repack-12 has caused the Debian Bug report #1034956, regarding libeztrace0: missing Breaks+Replaces for libeztrace-dev when upgrading from bullseye to be marked as done. This mea

Bug#1034929: marked as done (apertium-lex-tools-dev: missing Breaks+Replaces for apertium-lex-tools when upgrading from bullseye)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 14:34:06 + with message-id and subject line Bug#1034929: fixed in apertium-lex-tools 0.4.2-2 has caused the Debian Bug report #1034929, regarding apertium-lex-tools-dev: missing Breaks+Replaces for apertium-lex-tools when upgrading from bullseye to be marke

Bug#1034886: marked as done (docker.io: CVE-2022-37708)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 15:14:47 +0200 with message-id <20230427131447.ga31...@inutil.org> and subject line Re: Bug#1034886: docker.io: CVE-2022-37708 has caused the Debian Bug report #1034886, regarding docker.io: CVE-2022-37708 to be marked as done. This means that you claim that the

Bug#1034612: marked as done (freetype: CVE-2023-2004)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 13:04:05 + with message-id and subject line Bug#1034612: fixed in freetype 2.12.1+dfsg-5 has caused the Debian Bug report #1034612, regarding freetype: CVE-2023-2004 to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1034727: marked as done (postfix-policyd-spf-python: Update logcheck regex)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:22:59 + with message-id and subject line Bug#1034727: fixed in spf-engine 3.0.4-2 has caused the Debian Bug report #1034727, regarding postfix-policyd-spf-python: Update logcheck regex to be marked as done. This means that you claim that the problem has

Bug#972100: marked as done (CVE-2019-15547 CVE-2019-15548)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:06:53 + with message-id and subject line Bug#1034909: Removed package(s) from unstable has caused the Debian Bug report #972100, regarding CVE-2019-15547 CVE-2019-15548 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#889244: marked as done (O: golang-github-go-macaron-csrf -- generate and validate csrf tokens for Macaron)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:05:07 + with message-id and subject line Bug#1034883: Removed package(s) from unstable has caused the Debian Bug report #889244, regarding O: golang-github-go-macaron-csrf -- generate and validate csrf tokens for Macaron to be marked as done. This means

Bug#1034909: marked as done (RM: rust-ncurses -- ROM; open security issues)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:06:49 + with message-id and subject line Bug#1034909: Removed package(s) from unstable has caused the Debian Bug report #1034909, regarding RM: rust-ncurses -- ROM; open security issues to be marked as done. This means that you claim that the problem has

Bug#1034885: marked as done (RM: golang-github-go-macaron-binding -- RoQA; Obsolete)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:06:01 + with message-id and subject line Bug#1034885: Removed package(s) from unstable has caused the Debian Bug report #1034885, regarding RM: golang-github-go-macaron-binding -- RoQA; Obsolete to be marked as done. This means that you claim that the pr

Bug#1034884: marked as done (RM: golang-github-go-macaron-gzip -- RoQA; Obsolete)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:05:30 + with message-id and subject line Bug#1034884: Removed package(s) from unstable has caused the Debian Bug report #1034884, regarding RM: golang-github-go-macaron-gzip -- RoQA; Obsolete to be marked as done. This means that you claim that the probl

Bug#1034883: marked as done (RM: golang-github-go-macaron-csrf -- RoQA; Obsolete, open security issues)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:05:02 + with message-id and subject line Bug#1034883: Removed package(s) from unstable has caused the Debian Bug report #1034883, regarding RM: golang-github-go-macaron-csrf -- RoQA; Obsolete, open security issues to be marked as done. This means that y

Bug#1033865: marked as done (Don't release with bookworm)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:05:07 + with message-id and subject line Bug#1034883: Removed package(s) from unstable has caused the Debian Bug report #1033865, regarding Don't release with bookworm to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1033115: marked as done (golang-github-go-macaron-csrf: CVE-2018-25060)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:05:07 + with message-id and subject line Bug#1034883: Removed package(s) from unstable has caused the Debian Bug report #1033115, regarding golang-github-go-macaron-csrf: CVE-2018-25060 to be marked as done. This means that you claim that the problem has

Bug#978444: marked as done (FTBFS: fails to contact repl server in tests)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 11:18:54 + with message-id and subject line Bug#978444: fixed in racket-mode 20230425git0-1 has caused the Debian Bug report #978444, regarding FTBFS: fails to contact repl server in tests to be marked as done. This means that you claim that the problem has

Bug#1033852: marked as done (racket-mode: autopkgtest regression: Process *Racket REPL* connection broken by remote peer)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 11:18:54 + with message-id and subject line Bug#1033852: fixed in racket-mode 20230425git0-1 has caused the Debian Bug report #1033852, regarding racket-mode: autopkgtest regression: Process *Racket REPL* connection broken by remote peer to be marked as don

Bug#1034872: marked as done (unblock: wpewebkit/2.38.6-1)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:34:52 +0200 with message-id and subject line Re: Bug#1034872: unblock: wpewebkit/2.38.6-1 has caused the Debian Bug report #1034872, regarding unblock: wpewebkit/2.38.6-1 to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1034293: marked as done (cross-instal-location.diff no longer applies)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 10:34:26 + with message-id and subject line Bug#1034293: fixed in gcc-13 13.1.0-1 has caused the Debian Bug report #1034293, regarding cross-instal-location.diff no longer applies to be marked as done. This means that you claim that the problem has been dea

Bug#1034715: marked as done (unblock: python-xmlschema/1.10.0)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:27:16 +0200 with message-id <7a20a3fc-5841-7b84-e799-69b850802...@debian.org> and subject line Re: Bug#1034715: unblock: python-xmlschema/1.10.0 has caused the Debian Bug report #1034715, regarding unblock: python-xmlschema/1.10.0 to be marked as done. This m

Bug#1034892: marked as done (php8.2: reproducible-builds: Timestamps in phar files)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 10:21:17 + with message-id and subject line Bug#1034892: fixed in php8.2 8.2.5-2 has caused the Debian Bug report #1034892, regarding php8.2: reproducible-builds: Timestamps in phar files to be marked as done. This means that you claim that the problem has

Bug#1034423: marked as done (php8.2: reproducible-builds: Paths to sed in php-config8.2 and and phpize8.2)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 10:21:17 + with message-id and subject line Bug#1034423: fixed in php8.2 8.2.5-2 has caused the Debian Bug report #1034423, regarding php8.2: reproducible-builds: Paths to sed in php-config8.2 and and phpize8.2 to be marked as done. This means that you cla

Bug#1034863: marked as done (unblock: guix/1.4.0-3)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:16:32 +0200 with message-id <79dd2915-2414-9981-de94-a6a27169b...@debian.org> and subject line Re: Bug#1034863: unblock: guix/1.4.0-3 has caused the Debian Bug report #1034863, regarding unblock: guix/1.4.0-3 to be marked as done. This means that you claim th

Bug#1034813: marked as done (unblock: pev/0.81-9)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 12:03:26 +0200 with message-id and subject line Re: Bug#1034813: unblock: pev/0.81-9 has caused the Debian Bug report #1034813, regarding unblock: pev/0.81-9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not th

Bug#1034245: marked as done (pre-approval: unblock: openvswitch/3.1.1 (CVE-2023-1668))

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 10:56:20 +0200 with message-id <8e6928b6-7ef8-4a68-0b16-1687a94c1...@debian.org> and subject line Re: Bug#1034245: pre-approval: unblock: openvswitch/3.1.1 (CVE-2023-1668) has caused the Debian Bug report #1034245, regarding pre-approval: unblock: openvswitch/3.

Processed: Re: Bug#967469: gst123: depends on deprecated GTK 2

2023-04-27 Thread Debian Bug Tracking System
Processing control commands: > close 967469 0.3.5-3 Bug #967469 [src:gst123] gst123: depends on deprecated GTK 2 Marked as fixed in versions gst123/0.3.5-3. Bug #967469 [src:gst123] gst123: depends on deprecated GTK 2 Marked Bug as done > reopen 947713 Bug #947713 {Done: أحمد المحمودي (Ahmed El-Ma

Bug#1034762: marked as done (unblock: nheko/0.11.3-2)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 10:46:19 +0200 with message-id <618f9263-d6c6-bf11-3d50-efa9fe1ec...@debian.org> and subject line Re: Bug#1034762: unblock: nheko/0.11.3-2 has caused the Debian Bug report #1034762, regarding unblock: nheko/0.11.3-2 to be marked as done. This means that you clai

Bug#1034759: marked as done (unblock: scanssh/2.0-4.3)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 10:42:35 +0200 with message-id and subject line Re: Bug#1034759: unblock: scanssh/2.0-4.3 has caused the Debian Bug report #1034759, regarding unblock: scanssh/2.0-4.3 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1034769: marked as done (singular: build-dependencies unsatifiable on architectures where sagemath is unavailable.)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 08:34:04 + with message-id and subject line Bug#1034769: fixed in singular 1:4.3.1-p3+ds-2 has caused the Debian Bug report #1034769, regarding singular: build-dependencies unsatifiable on architectures where sagemath is unavailable. to be marked as done.

Processed: closing 1028477

2023-04-27 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 1028477 Bug #1028477 [php8.2-odbc] php-odbc: regression - login failed with php 8.2, works under 8.1 Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 1028477: https://bugs.debian.org/cgi-b

Bug#1034894: marked as done (missing Breaks+Replaces: liblxqt0)

2023-04-27 Thread Debian Bug Tracking System
Your message dated Thu, 27 Apr 2023 07:03:51 + with message-id and subject line Bug#1034894: fixed in liblxqt 1.2.0-6 has caused the Debian Bug report #1034894, regarding missing Breaks+Replaces: liblxqt0 to be marked as done. This means that you claim that the problem has been dealt with. If