Bug#1042282: marked as done (node-rollup-plugin-buble: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_build] Error 1)

Your message dated Sun, 13 Aug 2023 05:48:47 + with message-id and subject line Bug#1042282: fixed in node-rollup-plugin-buble 1.0.1+ds1+~0.19.8-2 has caused the Debian Bug report #1042282, regarding node-rollup-plugin-buble: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_build] Error

Bug#1042309: marked as done (node-buble: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

Your message dated Sun, 13 Aug 2023 05:33:47 + with message-id and subject line Bug#1042309: fixed in node-buble 0.20.0+~0.20.1-5 has caused the Debian Bug report #1042309, regarding node-buble: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marked

Processed: Bug#1042282 marked as pending in node-rollup-plugin-buble

Processing control commands: > tag -1 pending Bug #1042282 [src:node-rollup-plugin-buble] node-rollup-plugin-buble: FTBFS: make[1]: *** [debian/rules:8: override_dh_auto_build] Error 1 Added tag(s) pending. -- 1042282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042282 Debian Bug Trackin

Bug#1042282: marked as pending in node-rollup-plugin-buble

Control: tag -1 pending Hello, Bug #1042282 in node-rollup-plugin-buble reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-rollup-plugin-buble/-/commi

Processed: Bug#1042309 marked as pending in node-buble

Processing control commands: > tag -1 pending Bug #1042309 [src:node-buble] node-buble: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 Added tag(s) pending. -- 1042309: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1042309 Debian Bug Tracking System Co

Bug#1042309: marked as pending in node-buble

Control: tag -1 pending Hello, Bug #1042309 in node-buble reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-buble/-/commit/9d0191904173cee876b2f686e5

Bug#1032552: marked as done (libjs-img.srcset: FTBFS in testing: build-dependency not installable: node-uglify)

Your message dated Sun, 13 Aug 2023 04:49:33 + with message-id and subject line Bug#1032552: fixed in libjs-img.srcset 2.0.0~20131003~dfsg-4 has caused the Debian Bug report #1032552, regarding libjs-img.srcset: FTBFS in testing: build-dependency not installable: node-uglify to be marked as d

Bug#1041217: marked as done (src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure)

Your message dated Sun, 13 Aug 2023 04:49:56 + with message-id and subject line Bug#1041217: fixed in node-chart.js 3.9.1+~cs3.1.2-3 has caused the Debian Bug report #1041217, regarding src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure to be marked as done. Thi

Bug#1039918: marked as done (node-chart.js: autopkgtest regression: Testing chartjs-plugin-annotation: NOT FOUND)

Your message dated Sun, 13 Aug 2023 04:49:56 + with message-id and subject line Bug#1039918: fixed in node-chart.js 3.9.1+~cs3.1.2-3 has caused the Debian Bug report #1039918, regarding node-chart.js: autopkgtest regression: Testing chartjs-plugin-annotation: NOT FOUND to be marked as done.

Processed: This blocks migration of a fix for an RC bug, so must be RC too

Processing commands for cont...@bugs.debian.org: > severity 1042079 serious Bug #1042079 [src:onednn] onednn 2.7.4-1 FTBFS on arm64 Severity set to 'serious' from 'normal' > tags 1042079 + ftbfs Bug #1042079 [src:onednn] onednn 2.7.4-1 FTBFS on arm64 Added tag(s) ftbfs. > End of message, stopping

Processed: Bug#1032552 marked as pending in libjs-img.srcset

Processing control commands: > tag -1 pending Bug #1032552 [src:libjs-img.srcset] libjs-img.srcset: FTBFS in testing: build-dependency not installable: node-uglify Added tag(s) pending. -- 1032552: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032552 Debian Bug Tracking System Contact ow..

Bug#1032552: marked as pending in libjs-img.srcset

Control: tag -1 pending Hello, Bug #1032552 in libjs-img.srcset reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/libjs-img.srcset/-/commit/eba3c765eb078c

Bug#1041217: marked as pending in node-chart.js

Control: tag -1 pending Hello, Bug #1041217 in node-chart.js reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-chart.js/-/commit/f49158cca0323e1d16aa

Processed: Bug#1041217 marked as pending in node-chart.js

Processing control commands: > tag -1 pending Bug #1041217 [src:node-chart.js] src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure Added tag(s) pending. -- 1041217: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041217 Debian Bug Tracking System Contact ow...@bu

Processed: reopening 1041217

Processing commands for cont...@bugs.debian.org: > reopen 1041217 Bug #1041217 {Done: Paul Gevers } [src:node-chart.js] src:node-chart.js: fails to migrate to testing for too long: autopkgtest failure 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will

Bug#1037729: marked as done (libmygpo-qt: ftbfs with GCC-13)

Your message dated Sun, 13 Aug 2023 02:49:07 + with message-id and subject line Bug#1037729: fixed in libmygpo-qt 1.1.0-4.1 has caused the Debian Bug report #1037729, regarding libmygpo-qt: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1042149: marked as done (libmygpo-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff output below)

Your message dated Sun, 13 Aug 2023 02:49:07 + with message-id and subject line Bug#1037729: fixed in libmygpo-qt 1.1.0-4.1 has caused the Debian Bug report #1037729, regarding libmygpo-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns disappeared in the symbols file: see diff outpu

Bug#845848: marked as done (gnokii: switch to build depend on the metapackage default-libmysqlclient-dev)

Your message dated Sun, 13 Aug 2023 02:59:54 +0200 with message-id and subject line Re: gnokii: switch to build depend on the metapackage default-libmysqlclient-dev has caused the Debian Bug report #845848, regarding gnokii: switch to build depend on the metapackage default-libmysqlclient-dev to

Bug#1043559: gnome-calculator: open display blank window

Package: gnome-calculator Version: 1:45~beta-1 Severity: grave Justification: renders package unusable Dear Maintainer, This version only show blank window with Gtk-CRITICAL error: michiaki@debian$ gnome-calculator

Bug#1041307: marked as done (xtrx-dkms: module fails to build for Linux 6.4: error: too many arguments to function 'class_create')

Your message dated Sat, 12 Aug 2023 23:48:54 + with message-id and subject line Bug#1041307: fixed in xtrx-dkms 0.0.1+git20190320.5ae3a3e-3.4 has caused the Debian Bug report #1041307, regarding xtrx-dkms: module fails to build for Linux 6.4: error: too many arguments to function 'class_creat

Bug#1037817: marked as done (phyx: ftbfs with GCC-13)

Your message dated Sat, 12 Aug 2023 22:33:51 + with message-id and subject line Bug#1037817: fixed in phyx 1.3.1+ds-1 has caused the Debian Bug report #1037817, regarding phyx: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this is n

Bug#1042032: marked as done (phyx: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Sat, 12 Aug 2023 22:33:51 + with message-id and subject line Bug#1037817: fixed in phyx 1.3.1+ds-1 has caused the Debian Bug report #1037817, regarding phyx: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity to be marked as done. This means that you c

Bug#1028111: r-cran-clock: autopkgtest failure on 32bit

The 'bug fix' applied to the _previous_ version of CRAN package clock, namely a somewhat 'wild' sed patching of a single ie # Ignore single test for i386 architecture. This is a workaround for bug #1024828 of r-cran-igraph if [ "$hostarch" = "i386" -o "$hostarch" = "armel" -o "$hostarch" = "ar

Bug#1037817: marked as pending in phyx

Control: tag -1 pending Hello, Bug #1037817 in phyx reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/phyx/-/commit/203d3d14a39bccf797ae712cde57ae73283ee

Processed: Bug#1037817 marked as pending in phyx

Processing control commands: > tag -1 pending Bug #1037817 [src:phyx] phyx: ftbfs with GCC-13 Bug #1042032 [src:phyx] phyx: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity Added tag(s) pending. Added tag(s) pending. -- 1037817: https://bugs.debian.org/cgi-bin/bugreport.c

Bug#1043118: marked as done (victoriametrics: FTBFS: test failure)

Your message dated Sun, 13 Aug 2023 00:02:24 +0200 with message-id and subject line Re: Bug#1043118: victoriametrics: FTBFS: test failure has caused the Debian Bug report #1043118, regarding victoriametrics: FTBFS: test failure to be marked as done. This means that you claim that the problem has

Processed: forward

Processing commands for cont...@bugs.debian.org: > forwarded 109 https://github.com/KhronosGroup/OpenCOLLADA/issues/655 Bug #109 [src:opencollada] opencollada: depends on obsolete pcre3 library Set Bug forwarded-to-address to 'https://github.com/KhronosGroup/OpenCOLLADA/issues/655'. > End

Bug#1037801: marked as done (openexr: ftbfs with GCC-13)

Your message dated Sat, 12 Aug 2023 19:34:06 + with message-id and subject line Bug#1037801: fixed in openexr 3.1.5-5.1 has caused the Debian Bug report #1037801, regarding openexr: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1037655: marked as done (filtlong: ftbfs with GCC-13)

Your message dated Sat, 12 Aug 2023 19:33:53 + with message-id and subject line Bug#1037655: fixed in filtlong 0.2.1-4 has caused the Debian Bug report #1037655, regarding filtlong: ftbfs with GCC-13 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#1037655: marked as pending in filtlong

Control: tag -1 pending Hello, Bug #1037655 in filtlong reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/med-team/filtlong/-/commit/be6173ef06dbd6bb29f239d652c24

Processed: Bug#1037655 marked as pending in filtlong

Processing control commands: > tag -1 pending Bug #1037655 [src:filtlong] filtlong: ftbfs with GCC-13 Added tag(s) pending. -- 1037655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1037655 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1043542: marked as done (waybar: FTBFS on mips64el (test fails due to UTC time not available))

Your message dated Sat, 12 Aug 2023 19:41:53 +0200 with message-id <4a252ddb-f02a-469b-bd81-85cdaf27b...@debian.org> and subject line Re: waybar: FTBFS on mips64el (test fails due to UTC time not available) has caused the Debian Bug report #1043542, regarding waybar: FTBFS on mips64el (test fails

Bug#1043542: waybar: FTBFS on mips64el (test fails due to UTC time not available)

On Sat, 12 Aug 2023 19:24:16 +0200 Bastian Germann wrote: > Source: waybar > Version: 0.9.20-2 > Severity: serious > > The build fails on mips64el due to: > > test: waybar > start time: 15:11:25 > duration: 0.02s > result: killed by signal 6 SIGABRT > command: MALLOC_PER

Bug#1043542: waybar: FTBFS on mips64el (test fails due to UTC time not available)

Source: waybar Version: 0.9.20-2 Severity: serious The build fails on mips64el due to: test: waybar start time: 15:11:25 duration: 0.02s result: killed by signal 6 SIGABRT command: MALLOC_PERTURB_=25 /<>/obj-mips64el-linux-gnuabi64/test/waybar_test -

Bug#1038684: marked as done (firmware-ath9k-htc: TP-Link TL-WN722N is not reported by "iw dev".)

Your message dated Sat, 12 Aug 2023 17:17:09 + with message-id and subject line Bug#1038684: fixed in open-ath9k-htc-firmware 1.4.0-108-gd856466+dfsg1-1.3+deb12u1 has caused the Debian Bug report #1038684, regarding firmware-ath9k-htc: TP-Link TL-WN722N is not reported by "iw dev". to be mark

Processed: src:gcc-sh-elf: fails to migrate to testing for too long: unresolved RC issue

Processing control commands: > close -1 7 Bug #1043541 [src:gcc-sh-elf] src:gcc-sh-elf: fails to migrate to testing for too long: unresolved RC issue Marked as fixed in versions gcc-sh-elf/7. Bug #1043541 [src:gcc-sh-elf] src:gcc-sh-elf: fails to migrate to testing for too long: unresolved RC is

Bug#1043541: src:gcc-sh-elf: fails to migrate to testing for too long: unresolved RC issue

Source: gcc-sh-elf Version: 6 Severity: serious Control: close -1 7 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1040960 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstable for more

Bug#1006386: marked as done (libcrypt-openssl-pkcs12-perl: FTBFS with OpenSSL 3.0)

Your message dated Sat, 12 Aug 2023 16:21:43 + with message-id and subject line Bug#1006386: fixed in libcrypt-openssl-pkcs12-perl 1.9-2 has caused the Debian Bug report #1006386, regarding libcrypt-openssl-pkcs12-perl: FTBFS with OpenSSL 3.0 to be marked as done. This means that you claim th

Processed: forward the issue to upstream

Processing commands for cont...@bugs.debian.org: > forwarded 1042342 https://github.com/aio-libs/yarl/issues/894 Bug #1042342 [src:yarl] yarl: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 Set Bug forwarded-to-address to 'https://github.

Bug#1042258: marked as done (node-marked-man: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1)

Your message dated Sat, 12 Aug 2023 15:21:25 + with message-id and subject line Bug#1042258: fixed in node-marked-man 1.3.4-1 has caused the Debian Bug report #1042258, regarding node-marked-man: FTBFS: dh_auto_test: error: /bin/sh -ex debian/tests/pkg-js/test returned exit code 1 to be marke

Processed: src:tpm2-tss: fails to migrate to testing for too long: unresolved RC issue

Processing control commands: > close -1 4.0.1-2 Bug #1043535 [src:tpm2-tss] src:tpm2-tss: fails to migrate to testing for too long: unresolved RC issue Marked as fixed in versions tpm2-tss/4.0.1-2. Bug #1043535 [src:tpm2-tss] src:tpm2-tss: fails to migrate to testing for too long: unresolved RC

Bug#1043535: src:tpm2-tss: fails to migrate to testing for too long: unresolved RC issue

Source: tpm2-tss Version: 3.2.1-3 Severity: serious Control: close -1 4.0.1-2 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1040521 Dear maintainer(s), The Release Team considers packages that are out-of-sync between testing and unstabl

Processed: only bookworm is affected

Processing commands for cont...@bugs.debian.org: > # experimental isn't affected anymore either > tag 1035654 - experimental Bug #1035654 {Done: Julian Andres Klode } [src:apt] non-essential adduser poses problems to purging packages Removed tag(s) experimental. > thanks Stopping processing here.

Processed: only bookworm is affected

Processing commands for cont...@bugs.debian.org: > # enable migration > tag 1035654 - sid Bug #1035654 {Done: Julian Andres Klode } [src:apt] non-essential adduser poses problems to purging packages Removed tag(s) sid. > thanks Stopping processing here. Please contact me if you need assistance.

Processed: Monkeysphere Debian bug maintenance

Processing commands for cont...@bugs.debian.org: > owner 1011900 John Scott Bug #1011900 [src:monkeysphere] monkeysphere: FTBFS: ...Could not chdir to home directory /home/user42: No such file or directory Owner recorded as John Scott . > owner 861457 John Scott Bug #861457 [src:monkeysphere] m

Bug#1034851: marked as done (node-nodemailer: autopkgtest regression: ipv4.single.dev.ethereal.email changed IP)

Your message dated Sat, 12 Aug 2023 13:52:54 + with message-id and subject line Bug#1034851: fixed in node-nodemailer 6.9.4+~6.4.9-1 has caused the Debian Bug report #1034851, regarding node-nodemailer: autopkgtest regression: ipv4.single.dev.ethereal.email changed IP to be marked as done. T

Processed: src:giac: fails to migrate to testing for too long: FTBFS

Processing control commands: > close -1 1.9.0.57+dfsg2-1 Bug #1043529 [src:giac] src:giac: fails to migrate to testing for too long: FTBFS Marked as fixed in versions giac/1.9.0.57+dfsg2-1. Bug #1043529 [src:giac] src:giac: fails to migrate to testing for too long: FTBFS Marked Bug as done > blo

Bug#1043529: src:giac: fails to migrate to testing for too long: FTBFS

Source: giac Version: 1.9.0.35+dfsg2-1.1 Severity: serious Control: close -1 1.9.0.57+dfsg2-1 Tags: sid trixie User: release.debian@packages.debian.org Usertags: out-of-sync Control: block -1 by 1040889 Dear maintainer(s), The Release Team considers packages that are out-of-sync between test

Bug#1042934: marked as done (pytango autopkg tests fail on amd64 in unstable)

Your message dated Sat, 12 Aug 2023 10:05:01 -0300 with message-id and subject line Re: Bug#1042934: pytango autopkg tests fail on amd64 in unstable has caused the Debian Bug report #1042934, regarding pytango autopkg tests fail on amd64 in unstable to be marked as done. This means that you clai

Bug#1043519: marked as done (node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twice?)

Your message dated Sat, 12 Aug 2023 12:36:54 + with message-id and subject line Bug#1043519: fixed in node-json-stable-stringify 1.0.2+repack1+~cs1.0.34-1 has caused the Debian Bug report #1043519, regarding node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twic

Bug#1043519: marked as done (node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twice?)

Your message dated Sat, 12 Aug 2023 12:36:45 + with message-id and subject line Bug#1043519: fixed in node-fast-json-stable-stringify 2.1.0-2 has caused the Debian Bug report #1043519, regarding node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twice? to be marke

Bug#1043523: RM: bitmeter -- RoQA; unmaintained; depends on gtk2

Source: bitmeter Severity: serious Version: 1.2-4 X-Debbugs-Cc: d...@jones.dk bitmeter does not seem to be used a lot anymore. I intend to file a RM bug. If you have any reasons to keep it in Debian please voice them here. To get people's attention, I am filing as a serious bug and will reassi

Bug#1043519: marked as pending in node-fast-json-stable-stringify

Control: tag -1 pending Hello, Bug #1043519 in node-fast-json-stable-stringify reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/node-fast-json-stable-st

Processed: Bug#1043519 marked as pending in node-fast-json-stable-stringify

Processing control commands: > tag -1 pending Bug #1043519 [node-json-stable-stringify,node-fast-json-stable-stringify] node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twice? Added tag(s) pending. -- 1043519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=104

Bug#1043519: node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twice?

Package: node-json-stable-stringify,node-fast-json-stable-stringify Severity: serious Tags: sid trixie User: debian...@lists.debian.org Usertags: piuparts Control: found -1 1.0.2+~cs5.2.34-1 Control: found -1 2.1.0-1 Hi, during a test with piuparts I noticed your package failed to install because

Processed: node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twice?

Processing control commands: > found -1 1.0.2+~cs5.2.34-1 Bug #1043519 [node-json-stable-stringify,node-fast-json-stable-stringify] node-json-stable-stringify,node-fast-json-stable-stringify: same files packaged twice? There is no source info for the package 'node-fast-json-stable-stringify' at

Bug#1043305: marked as done (intel-microcode: CVE-2022-40982 CVE-2022-41804 CVE-2023-23908)

Your message dated Sat, 12 Aug 2023 11:04:39 + with message-id and subject line Bug#1043305: fixed in intel-microcode 3.20230808.1~deb11u1 has caused the Debian Bug report #1043305, regarding intel-microcode: CVE-2022-40982 CVE-2022-41804 CVE-2023-23908 to be marked as done. This means that y

Bug#1041423: marked as done (cjose: CVE-2023-37464)

Your message dated Sat, 12 Aug 2023 11:02:08 + with message-id and subject line Bug#1041423: fixed in cjose 0.6.2.1-1+deb12u1 has caused the Debian Bug report #1041423, regarding cjose: CVE-2023-37464 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#1043305: marked as done (intel-microcode: CVE-2022-40982 CVE-2022-41804 CVE-2023-23908)

Your message dated Sat, 12 Aug 2023 11:02:12 + with message-id and subject line Bug#1043305: fixed in intel-microcode 3.20230808.1~deb12u1 has caused the Debian Bug report #1043305, regarding intel-microcode: CVE-2022-40982 CVE-2022-41804 CVE-2023-23908 to be marked as done. This means that y

Bug#1041423: marked as done (cjose: CVE-2023-37464)

Your message dated Sat, 12 Aug 2023 11:02:43 + with message-id and subject line Bug#1041423: fixed in cjose 0.6.1+dfsg1-1+deb11u1 has caused the Debian Bug report #1041423, regarding cjose: CVE-2023-37464 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#1043510: RM: rox -- RoQA; dead upstream; depends on gtk2

Source: rox Severity: serious Version: 1:2.11-7 rox does not seem to be used a lot anymore. I intend to file a RM bug. If you have any reasons to keep it in Debian please voice them here. To get people's attention, I am filing as a serious bug and will reassign to the FTP team when the package i

Bug#1025548: marked as done (arduino: recommends transitional policykit-1 package)

Your message dated Sat, 12 Aug 2023 08:34:53 + with message-id and subject line Bug#1025548: fixed in arduino 2:1.8.19+dfsg1-2 has caused the Debian Bug report #1025548, regarding arduino: recommends transitional policykit-1 package to be marked as done. This means that you claim that the pro

Bug#969907: marked as done (inkscape, etc. crashing with mismatched libpoppler102 and libpoppler-glib8)

Your message dated Sat, 12 Aug 2023 07:10:12 + with message-id and subject line Bug#969907: fixed in poppler 23.08.0-1 has caused the Debian Bug report #969907, regarding inkscape, etc. crashing with mismatched libpoppler102 and libpoppler-glib8 to be marked as done. This means that you clai

Bug#1012532: marked as done (inkscape: PDF import no longer works)

Your message dated Sat, 12 Aug 2023 07:10:12 + with message-id and subject line Bug#969907: fixed in poppler 23.08.0-1 has caused the Debian Bug report #969907, regarding inkscape: PDF import no longer works to be marked as done. This means that you claim that the problem has been dealt with.