Bug#498067: marked as done (dh_install wildcard exception mechanism request)

Your message dated Mon, 30 Oct 2023 17:24:39 +1100 with message-id and subject line Fixed in dh-exec 0.24 has caused the Debian Bug report #498067, regarding dh_install wildcard exception mechanism request to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#831786: marked as done (dh-exec: breaks dh_install --fail-missing)

Your message dated Mon, 30 Oct 2023 17:25:41 +1100 with message-id and subject line Fixed in dh-exec 0.24 has caused the Debian Bug report #831786, regarding dh-exec: breaks dh_install --fail-missing to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1051979: marked as done (Do not suggest APT::Default-Release setting)

Your message dated Mon, 30 Oct 2023 05:19:01 + with message-id and subject line Bug#1051979: fixed in debian-reference 2.104 has caused the Debian Bug report #1051979, regarding Do not suggest APT::Default-Release setting to be marked as done. This means that you claim that the problem has be

Bug#1054872: marked as done (libjose4j-java: CVE-2023-31582)

Your message dated Mon, 30 Oct 2023 04:34:03 + with message-id and subject line Bug#1054872: fixed in libjose4j-java 0.7.12-2 has caused the Debian Bug report #1054872, regarding libjose4j-java: CVE-2023-31582 to be marked as done. This means that you claim that the problem has been dealt wit

Bug#1054583: marked as done (dpkg-dev: really enable -fstack-clash-protection on armhf/armel)

Your message dated Mon, 30 Oct 2023 03:49:09 + with message-id and subject line Bug#1054583: fixed in dpkg 1.22.1 has caused the Debian Bug report #1054583, regarding dpkg-dev: really enable -fstack-clash-protection on armhf/armel to be marked as done. This means that you claim that the probl

Bug#1054510: marked as done (dpkg: [INTL:sv] Update Swedish translation ("main" branch))

Your message dated Mon, 30 Oct 2023 03:49:09 + with message-id and subject line Bug#1054510: fixed in dpkg 1.22.1 has caused the Debian Bug report #1054510, regarding dpkg: [INTL:sv] Update Swedish translation ("main" branch) to be marked as done. This means that you claim that the problem ha

Bug#1053364: marked as done ([INTL:ro] Translation of "dselect" to Romanian)

Your message dated Mon, 30 Oct 2023 03:49:08 + with message-id and subject line Bug#1053364: fixed in dpkg 1.22.1 has caused the Debian Bug report #1053364, regarding [INTL:ro] Translation of "dselect" to Romanian to be marked as done. This means that you claim that the problem has been dealt

Bug#1053778: marked as done (dpkg: add loong64 to mask builtin feature list)

Your message dated Mon, 30 Oct 2023 03:49:09 + with message-id and subject line Bug#1053778: fixed in dpkg 1.22.1 has caused the Debian Bug report #1053778, regarding dpkg: add loong64 to mask builtin feature list to be marked as done. This means that you claim that the problem has been dealt

Bug#1053481: marked as done (libdpkg-perl: dpkg-source fails to generate (complete) Testsuite-Triggers if test deps have :native qualifier)

Your message dated Mon, 30 Oct 2023 03:49:09 + with message-id and subject line Bug#1053481: fixed in dpkg 1.22.1 has caused the Debian Bug report #1053481, regarding libdpkg-perl: dpkg-source fails to generate (complete) Testsuite-Triggers if test deps have :native qualifier to be marked as

Bug#1053236: marked as done (dpkg: [INTL:nl] Dutch translation for the dpkg package)

Your message dated Mon, 30 Oct 2023 03:49:08 + with message-id and subject line Bug#1053236: fixed in dpkg 1.22.1 has caused the Debian Bug report #1053236, regarding dpkg: [INTL:nl] Dutch translation for the dpkg package to be marked as done. This means that you claim that the problem has be

Bug#1053235: marked as done (dselect: [INTL:nl] Dutch translation for the dselect package)

Your message dated Mon, 30 Oct 2023 03:49:08 + with message-id and subject line Bug#1053235: fixed in dpkg 1.22.1 has caused the Debian Bug report #1053235, regarding dselect: [INTL:nl] Dutch translation for the dselect package to be marked as done. This means that you claim that the problem

Bug#1051209: marked as done (dpkg-dev: dpkg-source --commit should use configured default editor instead of forcing nano)

Your message dated Mon, 30 Oct 2023 03:49:08 + with message-id and subject line Bug#1051209: fixed in dpkg 1.22.1 has caused the Debian Bug report #1051209, regarding dpkg-dev: dpkg-source --commit should use configured default editor instead of forcing nano to be marked as done. This means

Bug#1051085: marked as done (dpkg: dpkg-db-backup.timer stopped after upgrades)

Your message dated Mon, 30 Oct 2023 03:49:08 + with message-id and subject line Bug#1051085: fixed in dpkg 1.22.1 has caused the Debian Bug report #1051085, regarding dpkg: dpkg-db-backup.timer stopped after upgrades to be marked as done. This means that you claim that the problem has been de

Bug#1055017: marked as done (node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED)

Your message dated Mon, 30 Oct 2023 03:19:03 + with message-id and subject line Bug#1055017: fixed in node-html-webpack-plugin 5.5.3+repack1-1 has caused the Debian Bug report #1055017, regarding node-html-webpack-plugin_5.5.3+~cs14.4.8-1_all-buildd.changes REJECTED to be marked as done. This

Bug#1054630: marked as done (dgit - cant import llvm-toolchain-15.)

Your message dated Mon, 30 Oct 2023 02:49:00 + with message-id and subject line Bug#1054630: fixed in dgit 11.4 has caused the Debian Bug report #1054630, regarding dgit - cant import llvm-toolchain-15. to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#1054252: marked as done (g2o: binary-all FTBFS)

Your message dated Mon, 30 Oct 2023 01:36:24 + with message-id and subject line Bug#1054252: fixed in g2o 0~20230806-3 has caused the Debian Bug report #1054252, regarding g2o: binary-all FTBFS to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#1050831: marked as done (wrk: No manual page)

Your message dated Sun, 29 Oct 2023 23:34:11 + with message-id and subject line Bug#1050831: fixed in wrk 4.1.0-4 has caused the Debian Bug report #1050831, regarding wrk: No manual page to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Processed (with 2 errors): Closing #1042688

Processing commands for cont...@bugs.debian.org: > close 1042688 Bug #1042688 [src:python-pykka] python-pykka: FTBFS with Sphinx 7.1, docutils 0.20: TypeError: not all arguments converted during string formatting Marked Bug as done > This issue was resolved in Pykka 4.0.0, which has been in Debia

Bug#717778: marked as done (checkinstall: mkdir -p fails (fstrans broken again?))

Your message dated Sun, 29 Oct 2023 21:49:08 + with message-id and subject line Bug#717778: fixed in checkinstall 1.6.2+git20170426.d24a630-4 has caused the Debian Bug report #717778, regarding checkinstall: mkdir -p fails (fstrans broken again?) to be marked as done. This means that you clai

Bug#850871: marked as done (please provide VCS fields)

Your message dated Sun, 29 Oct 2023 21:34:08 + with message-id and subject line Bug#850871: fixed in blockdiag 2.0.1+dfsg-2 has caused the Debian Bug report #850871, regarding please provide VCS fields to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#1049331: marked as done (python3-blockdiag: fails with Pil 10)

Your message dated Sun, 29 Oct 2023 21:34:08 + with message-id and subject line Bug#1049331: fixed in blockdiag 2.0.1+dfsg-2 has caused the Debian Bug report #1049331, regarding python3-blockdiag: fails with Pil 10 to be marked as done. This means that you claim that the problem has been deal

Bug#1052748: marked as done (mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known)

Your message dated Sun, 29 Oct 2023 22:14:08 +0100 with message-id <41d44ed9f524f9289caf0f4c8f946...@debian.org> and subject line Re: Bug#1052748: mpi4py fails test_dynproc.TestDPM.testJoin: socket.gaierror: [Errno -2] Name or service not known has caused the Debian Bug report #1052748, regarding

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

Your message dated Sun, 29 Oct 2023 21:10:19 +0100 with message-id and subject line Re: Bug#1054965: guile-2.2: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 has caused the Debian Bug report #1054965, regarding guile-2.2: FTBFS: dh_auto_t

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

Your message dated Sun, 29 Oct 2023 21:09:21 +0100 with message-id and subject line Re: Bug#1054980: django-dirtyfields: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 has caused the Debian Bug report #1054980, regarding django-dirtyfiel

Bug#1054507: marked as done (golang-github-weaveworks-promrus: FTBFS with "invalid memory address" if the machine is not very fast (?))

Your message dated Sun, 29 Oct 2023 19:49:51 + with message-id and subject line Bug#1054507: fixed in golang-github-weaveworks-promrus 1.2.0+git20210208.77c195c-3 has caused the Debian Bug report #1054507, regarding golang-github-weaveworks-promrus: FTBFS with "invalid memory address" if the

Bug#1042660: marked as done (votca: FTBFS with Sphinx 7.1, docutils 0.20: make[5]: *** [share/doc/CMakeFiles/doc.dir/build.make:81: share/doc/CMakeFiles/doc] Error 2)

Your message dated Sun, 29 Oct 2023 19:37:40 + with message-id and subject line Bug#1042660: fixed in votca 2022.1-2 has caused the Debian Bug report #1042660, regarding votca: FTBFS with Sphinx 7.1, docutils 0.20: make[5]: *** [share/doc/CMakeFiles/doc.dir/build.make:81: share/doc/CMakeFiles

Bug#1036924: marked as done (ITP: obfuscate -- Censor private information from images)

Your message dated Sun, 29 Oct 2023 19:35:42 + with message-id and subject line Bug#1036924: fixed in obfuscate 0.0.9-2 has caused the Debian Bug report #1036924, regarding ITP: obfuscate -- Censor private information from images to be marked as done. This means that you claim that the proble

Bug#1054588: marked as done (ITP: ocaml-metadata -- read metadata from various formats)

Your message dated Sun, 29 Oct 2023 19:00:12 + with message-id and subject line Bug#1054588: fixed in ocaml-metadata 0.2.0-1~exp1 has caused the Debian Bug report #1054588, regarding ITP: ocaml-metadata -- read metadata from various formats to be marked as done. This means that you claim that

Bug#1054206: marked as done (ITP: lsprotocol -- Python implementation of the Language Server Protocol types)

Your message dated Sun, 29 Oct 2023 19:00:11 + with message-id and subject line Bug#1054206: fixed in lsprotocol 2023.0.0~b1-1 has caused the Debian Bug report #1054206, regarding ITP: lsprotocol -- Python implementation of the Language Server Protocol types to be marked as done. This means

Bug#1053413: marked as done (ITP: tox-current-env -- tox plugin to run tests in)

Your message dated Sun, 29 Oct 2023 19:00:13 + with message-id and subject line Bug#1053413: fixed in tox-current-env 0.0.11-1 has caused the Debian Bug report #1053413, regarding ITP: tox-current-env -- tox plugin to run tests in to be marked as done. This means that you claim that the probl

Bug#1051930: marked as done (ITP: node-node-pty -- Node.js library to allow one to fork processes with pseudoterminal file descriptors)

Your message dated Sun, 29 Oct 2023 19:00:11 + with message-id and subject line Bug#1051930: fixed in node-node-pty 1.0.0+~6.3.0-1 has caused the Debian Bug report #1051930, regarding ITP: node-node-pty -- Node.js library to allow one to fork processes with pseudoterminal file descriptors to

Bug#1000693: marked as done (ITP: libnet-mqtt-simple-perl -- Minimal MQTT version 3 interface)

Your message dated Sun, 29 Oct 2023 19:00:10 + with message-id and subject line Bug#1000693: fixed in libnet-mqtt-simple-perl 1.29-1 has caused the Debian Bug report #1000693, regarding ITP: libnet-mqtt-simple-perl -- Minimal MQTT version 3 interface to be marked as done. This means that you

Bug#1036924: marked as done (ITP: obfuscate -- Censor private information from images)

Your message dated Sun, 29 Oct 2023 19:00:12 + with message-id and subject line Bug#1036924: fixed in obfuscate 0.0.9-1 has caused the Debian Bug report #1036924, regarding ITP: obfuscate -- Censor private information from images to be marked as done. This means that you claim that the proble

Bug#1052859: marked as done (geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 returned exit code 2)

Your message dated Sun, 29 Oct 2023 18:50:29 + with message-id and subject line Bug#1052859: fixed in geonames 0.3.0-2 has caused the Debian Bug report #1052859, regarding geonames: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && make -j8 test ARGS\+=--verbose ARGS\+=-j8 VERBOSE=1 retu

Bug#1044225: marked as done (geonames: Fails to build source after successful build)

Your message dated Sun, 29 Oct 2023 18:50:29 + with message-id and subject line Bug#1044225: fixed in geonames 0.3.0-2 has caused the Debian Bug report #1044225, regarding geonames: Fails to build source after successful build to be marked as done. This means that you claim that the problem h

Processed: cloning 1054233, reassign -1 to mda-lv2, closing -1 ..., cloning 1054233 ..., closing -2

Processing commands for cont...@bugs.debian.org: > clone 1054233 -1 Bug #1054233 [liblilv-0-0] liblilv-0-0: Package does not follow FHS, it adds /usr/lib/$(DEB_HOST_MULTIARCH) to the --default-lv2-path waf configure option, see rules file, line 21. Bug 1054233 cloned as bug 1055029 > reassign -1

Bug#1025376: marked as done (libcds: FTBFS on mips64el, s390x, riscv64)

Your message dated Sun, 29 Oct 2023 18:05:04 + with message-id and subject line Bug#1025376: fixed in libcds 2.3.3-4 has caused the Debian Bug report #1025376, regarding libcds: FTBFS on mips64el, s390x, riscv64 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1052076: marked as done (ITP: node-mathjax-full -- JavaScript library to display math in browsers)

Your message dated Sun, 29 Oct 2023 18:00:10 + with message-id and subject line Bug#1052076: fixed in node-mathjax-full 3.2.2+~cs4.2.1-1 has caused the Debian Bug report #1052076, regarding ITP: node-mathjax-full -- JavaScript library to display math in browsers to be marked as done. This me

Bug#1042643: marked as done (libtext-markup-perl: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: /usr/bin/perl Build test --verbose 1 returned exit code 1)

Your message dated Sun, 29 Oct 2023 17:35:07 + with message-id and subject line Bug#1042643: fixed in libtext-markup-perl 0.24-2 has caused the Debian Bug report #1042643, regarding libtext-markup-perl: FTBFS with Sphinx 7.1, docutils 0.20: dh_auto_test: error: /usr/bin/perl Build test --verb

Bug#1052097: marked as done (gnome-shell-extension-freon: needs update for GNOME Shell 45)

Your message dated Sun, 29 Oct 2023 18:33:45 +0100 with message-id <878r7l2v0m.fsf@localhost> and subject line Re: Bug#1052097: gnome-shell-extension-freon: needs update for GNOME Shell 45 has caused the Debian Bug report #1052097, regarding gnome-shell-extension-freon: needs update for GNOME Shel

Bug#1055023: marked as done (FTBFS: libpoe-component-client-dns-perl requires DNS during tests.)

Your message dated Sun, 29 Oct 2023 17:19:28 + with message-id and subject line Bug#1055023: fixed in libpoe-component-client-dns-perl 1:1.054-4 has caused the Debian Bug report #1055023, regarding FTBFS: libpoe-component-client-dns-perl requires DNS during tests. to be marked as done. This

Bug#1054337: marked as done (reportbug: lv2 version in debian is outdated)

Your message dated Sun, 29 Oct 2023 17:19:40 + with message-id and subject line Bug#1054337: fixed in lv2 1.18.10-1 has caused the Debian Bug report #1054337, regarding reportbug: lv2 version in debian is outdated to be marked as done. This means that you claim that the problem has been dealt

Bug#1054625: marked as done (boxes: New upstream release)

Your message dated Sun, 29 Oct 2023 17:19:05 + with message-id and subject line Bug#1054625: fixed in boxes 2.2.1-1 has caused the Debian Bug report #1054625, regarding boxes: New upstream release to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1051242: marked as done (ITP: a2d/2.0.0-1 -- APRS to DAPNET portal)

Your message dated Sun, 29 Oct 2023 17:00:09 + with message-id and subject line Bug#1051242: fixed in a2d 2.0.0-1 has caused the Debian Bug report #1051242, regarding ITP: a2d/2.0.0-1 -- APRS to DAPNET portal to be marked as done. This means that you claim that the problem has been dealt with

Bug#1053489: marked as done (ITP: scikit-build-core -- Python package build systems and CMake integration)

Your message dated Sun, 29 Oct 2023 17:00:11 + with message-id and subject line Bug#1053489: fixed in scikit-build-core 0.5.1-1 has caused the Debian Bug report #1053489, regarding ITP: scikit-build-core -- Python package build systems and CMake integration to be marked as done. This means t

Bug#1020507: marked as done (libcleri breaks siridb-server autopkgtest, siridb-server rebuild "fixes" the issue)

Your message dated Sun, 29 Oct 2023 16:19:23 + with message-id and subject line Bug#1020507: fixed in libcleri 1.0.1-2 has caused the Debian Bug report #1020507, regarding libcleri breaks siridb-server autopkgtest, siridb-server rebuild "fixes" the issue to be marked as done. This means that

Processed: reassign 1048451 to dh-raku, forcibly merging 1045217 1048451

Processing commands for cont...@bugs.debian.org: > reassign 1048451 dh-raku Bug #1048451 [src:raku-readline] raku-readline: Fails to build source after successful build Bug reassigned from package 'src:raku-readline' to 'dh-raku'. No longer marked as found in versions raku-readline/0.1.6-3. Ignor

Processed: reassign 1048293 to dh-raku, forcibly merging 1045217 1048293

Processing commands for cont...@bugs.debian.org: > reassign 1048293 dh-raku Bug #1048293 [src:raku-meta6] raku-meta6: Fails to build source after successful build Bug reassigned from package 'src:raku-meta6' to 'dh-raku'. No longer marked as found in versions raku-meta6/0.0.29-1. Ignoring request

Processed: reassign 1045492 to dh-raku, forcibly merging 1045217 1045492

Processing commands for cont...@bugs.debian.org: > reassign 1045492 dh-raku Bug #1045492 [src:raku-license-spdx] raku-license-spdx: Fails to build source after successful build Bug reassigned from package 'src:raku-license-spdx' to 'dh-raku'. No longer marked as found in versions raku-license-spd

Processed: reassign 1045623 to dh-raku, forcibly merging 1045217 1045623

Processing commands for cont...@bugs.debian.org: > reassign 1045623 dh-raku Bug #1045623 [src:raku-librarycheck] raku-librarycheck: Fails to build source after successful build Bug reassigned from package 'src:raku-librarycheck' to 'dh-raku'. No longer marked as found in versions raku-librarychec

Processed: reassign 1046598 to dh-raku, forcibly merging 1045217 1046598

Processing commands for cont...@bugs.debian.org: > reassign 1046598 dh-raku Bug #1046598 [src:raku-json-unmarshal] raku-json-unmarshal: Fails to build source after successful build Bug reassigned from package 'src:raku-json-unmarshal' to 'dh-raku'. No longer marked as found in versions raku-json-

Processed: reassign 1045323 to dh-raku, forcibly merging 1045217 1045323

Processing commands for cont...@bugs.debian.org: > reassign 1045323 dh-raku Bug #1045323 [src:raku-json-optin] raku-json-optin: Fails to build source after successful build Bug reassigned from package 'src:raku-json-optin' to 'dh-raku'. No longer marked as found in versions raku-json-optin/0.0.2-

Processed: reassign 1045670 to dh-raku, forcibly merging 1045217 1045670

Processing commands for cont...@bugs.debian.org: > reassign 1045670 dh-raku Bug #1045670 [src:raku-json-name] raku-json-name: Fails to build source after successful build Bug reassigned from package 'src:raku-json-name' to 'dh-raku'. No longer marked as found in versions raku-json-name/0.0.7-3. I

Processed: reassign 1045921 to dh-raku, forcibly merging 1045217 1045921

Processing commands for cont...@bugs.debian.org: > reassign 1045921 dh-raku Bug #1045921 [src:raku-zef] raku-zef: Fails to build source after successful build Bug reassigned from package 'src:raku-zef' to 'dh-raku'. No longer marked as found in versions raku-zef/0.13.8-1. Ignoring request to alte

Processed: reassign 1048691 to dh-raku, forcibly merging 1045217 1048691

Processing commands for cont...@bugs.debian.org: > reassign 1048691 dh-raku Bug #1048691 [src:raku-uri] raku-uri: Fails to build source after successful build Bug reassigned from package 'src:raku-uri' to 'dh-raku'. No longer marked as found in versions raku-uri/0.3.5-3. Ignoring request to alter

Processed: reassign 1048022 to dh-raku, forcibly merging 1045217 1048022

Processing commands for cont...@bugs.debian.org: > reassign 1048022 dh-raku Bug #1048022 [src:raku-test-meta] raku-test-meta: Fails to build source after successful build Bug reassigned from package 'src:raku-test-meta' to 'dh-raku'. No longer marked as found in versions raku-test-meta/0.0.17-1.

Processed: reassign 1046941 to dh-raku, forcibly merging 1045217 1046941

Processing commands for cont...@bugs.debian.org: > reassign 1046941 dh-raku Bug #1046941 [src:raku-json-fast] raku-json-fast: Fails to build source after successful build Bug reassigned from package 'src:raku-json-fast' to 'dh-raku'. No longer marked as found in versions raku-json-fast/0.17-1. Ig

Bug#1037395: marked as done (mediascanner2: build-depends on transitional package libgdk-pixbuf2.0-dev)

Your message dated Sun, 29 Oct 2023 15:34:40 + with message-id and subject line Bug#1037395: fixed in mediascanner2 0.115-4 has caused the Debian Bug report #1037395, regarding mediascanner2: build-depends on transitional package libgdk-pixbuf2.0-dev to be marked as done. This means that you

Processed: reassign 1046178 to dh-raku, forcibly merging 1045217 1046178

Processing commands for cont...@bugs.debian.org: > reassign 1046178 dh-raku Bug #1046178 [src:raku-json-marshal] raku-json-marshal: Fails to build source after successful build Bug reassigned from package 'src:raku-json-marshal' to 'dh-raku'. No longer marked as found in versions raku-json-marsha

Processed: reassign 1047625 to dh-raku, forcibly merging 1045217 1047625

Processing commands for cont...@bugs.debian.org: > reassign 1047625 dh-raku Bug #1047625 [src:raku-json-class] raku-json-class: Fails to build source after successful build Bug reassigned from package 'src:raku-json-class' to 'dh-raku'. No longer marked as found in versions raku-json-class/0.0.19

Bug#1054788: marked as done (libseccomp: FTBFS: dh_install: error: missing files, aborting)

Your message dated Sun, 29 Oct 2023 15:19:05 + with message-id and subject line Bug#1054788: fixed in libseccomp 2.5.4-2 has caused the Debian Bug report #1054788, regarding libseccomp: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the

Bug#1033641: marked as done (libseccomp failing to build from source on bookworm with python 3.11)

Your message dated Sun, 29 Oct 2023 15:19:05 + with message-id and subject line Bug#1033641: fixed in libseccomp 2.5.4-2 has caused the Debian Bug report #1033641, regarding libseccomp failing to build from source on bookworm with python 3.11 to be marked as done. This means that you claim th

Bug#1050659: marked as done (libseccomp: update d/watch file)

Your message dated Sun, 29 Oct 2023 15:19:05 + with message-id and subject line Bug#1050659: fixed in libseccomp 2.5.4-2 has caused the Debian Bug report #1050659, regarding libseccomp: update d/watch file to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#1054536: marked as done (cyrus-sasl2 FTBFS: sphinx failure: AttributeError("'str' object has no attribute 'attributes'"))

Your message dated Sun, 29 Oct 2023 16:14:57 +0100 with message-id and subject line Re: Bug#1054536: cyrus-sasl2 FTBFS: sphinx failure: AttributeError("'str' object has no attribute 'attributes'") has caused the Debian Bug report #1054536, regarding cyrus-sasl2 FTBFS: sphinx failure: AttributeErr

Bug#1054994: marked as done (xrootd: FTBFS on hppa - open with O_CREAT or O_TMPFILE in second argument needs 3 arguments)

Your message dated Sun, 29 Oct 2023 15:06:24 + with message-id and subject line Bug#1054994: fixed in xrootd 5.6.3-3 has caused the Debian Bug report #1054994, regarding xrootd: FTBFS on hppa - open with O_CREAT or O_TMPFILE in second argument needs 3 arguments to be marked as done. This mea

Bug#1054874: marked as done (openimageio: CVE-2023-42295)

Your message dated Sun, 29 Oct 2023 15:05:44 + with message-id and subject line Bug#1054873: fixed in openimageio 2.4.16.0+dfsg-1 has caused the Debian Bug report #1054873, regarding openimageio: CVE-2023-42295 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1054873: marked as done (openimageio: CVE-2023-42295)

Your message dated Sun, 29 Oct 2023 15:05:44 + with message-id and subject line Bug#1054873: fixed in openimageio 2.4.16.0+dfsg-1 has caused the Debian Bug report #1054873, regarding openimageio: CVE-2023-42295 to be marked as done. This means that you claim that the problem has been dealt wi

Bug#1021872: marked as done (debmake: Debmake does not work unless wget is installed, but stand-alone curl is able to download source package)

Your message dated Sun, 29 Oct 2023 14:34:04 + with message-id and subject line Bug#1021872: fixed in debmake 4.4.0-2 has caused the Debian Bug report #1021872, regarding debmake: Debmake does not work unless wget is installed, but stand-alone curl is able to download source package to be mar

Bug#969177: marked as done (debmake: cannot create deb for nodejs modeule)

Your message dated Sun, 29 Oct 2023 14:34:04 + with message-id and subject line Bug#969177: fixed in debmake 4.4.0-2 has caused the Debian Bug report #969177, regarding debmake: cannot create deb for nodejs modeule to be marked as done. This means that you claim that the problem has been deal

Bug#1052102: marked as done (gnome-shell-extension-hard-disk-led: needs update for GNOME Shell 45)

Your message dated Sun, 29 Oct 2023 14:34:13 + with message-id and subject line Bug#1052102: fixed in gnome-shell-extension-hard-disk-led 35-1~exp1 has caused the Debian Bug report #1052102, regarding gnome-shell-extension-hard-disk-led: needs update for GNOME Shell 45 to be marked as done.

Bug#1028595: marked as done (debmake creates invalid debian/source/control)

Your message dated Sun, 29 Oct 2023 14:34:04 + with message-id and subject line Bug#1028595: fixed in debmake 4.4.0-2 has caused the Debian Bug report #1028595, regarding debmake creates invalid debian/source/control to be marked as done. This means that you claim that the problem has been de

Bug#1054834: marked as done (coreboot: FTBFS: make[1]: *** [debian/rules:29: override_dh_auto_build] Error 2)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054834, regarding coreboot: FTBFS: make[1]: *** [debian/rules:29: override_dh_auto_build] Error 2 to be marked as done. This means that

Bug#1054867: marked as done (python-pyftpdlib: FTBFS: make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054867, regarding python-pyftpdlib: FTBFS: make[1]: *** [debian/rules:21: override_dh_auto_build] Error 2 to be marked as done. This mea

Bug#1054855: marked as done (powerline: FTBFS: make[1]: *** [debian/rules:17: override_dh_installdocs] Error 2)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054855, regarding powerline: FTBFS: make[1]: *** [debian/rules:17: override_dh_installdocs] Error 2 to be marked as done. This means tha

Bug#1054837: marked as done (pyodc: FTBFS: make: *** [debian/rules:11: binary] Error 25)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054837, regarding pyodc: FTBFS: make: *** [debian/rules:11: binary] Error 25 to be marked as done. This means that you claim that the pro

Bug#1054833: marked as done (openshot-qt: FTBFS: make[1]: *** [debian/rules:11: execute_after_dh_auto_build] Error 2)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054833, regarding openshot-qt: FTBFS: make[1]: *** [debian/rules:11: execute_after_dh_auto_build] Error 2 to be marked as done. This mea

Bug#1054811: marked as done (python-oslo.rootwrap: FTBFS: tests failed)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054811, regarding python-oslo.rootwrap: FTBFS: tests failed to be marked as done. This means that you claim that the problem has been dea

Bug#1054817: marked as done (terminaltables: FTBFS: InputError: [Errno 2] No such file or directory: 'README.rst'.)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054817, regarding terminaltables: FTBFS: InputError: [Errno 2] No such file or directory: 'README.rst'. to be marked as done. This means

Bug#1054807: marked as done (python-psutil: FTBFS: make[1]: *** [Makefile:58: html] Error 2)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054807, regarding python-psutil: FTBFS: make[1]: *** [Makefile:58: html] Error 2 to be marked as done. This means that you claim that the

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

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054769, regarding quilt: FTBFS: dh_auto_test: error: make -j8 check "TESTSUITEFLAGS=-j8 --verbose" VERBOSE=1 returned exit code 2 to be m

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

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1054721, regarding python-igraph: FTBFS: dh_auto_test: error: pybuild --test -i python{version} -p 3.11 returned exit code 13 to be marked

Bug#1052924: marked as done (gyoto: FTBFS: mkdir: cannot create directory ‘././sbuild-nonexistent’: Permission denied)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052924, regarding gyoto: FTBFS: mkdir: cannot create directory ‘././sbuild-nonexistent’: Permission denied to be marked as done. This me

Bug#1052925: marked as done (python-kaptan: FTBFS: chmod: cannot access '/<>/kaptan.egg-info/*': No such file or directory)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052925, regarding python-kaptan: FTBFS: chmod: cannot access '/<>/kaptan.egg-info/*': No such file or directory to be marked as done. Th

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

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052864, regarding simgear: FTBFS: dh_auto_test: error: cd build && make -j1 test ARGS\+=--verbose ARGS\+=-j1 returned exit code 2 to be m

Bug#1052899: marked as done (python-fido2: FTBFS: chmod: cannot access 'fido2.egg-info/*': No such file or directory)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052899, regarding python-fido2: FTBFS: chmod: cannot access 'fido2.egg-info/*': No such file or directory to be marked as done. This mea

Bug#1052888: marked as done (epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052888, regarding epics-base: FTBFS: make[2]: *** [configure/RULES_TOP:62: runtests] Error 1 to be marked as done. This means that you c

Bug#1052774: marked as done (php-arthurhoaro-web-thumbnailer: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052774, regarding php-arthurhoaro-web-thumbnailer: FTBFS: make[1]: *** [debian/rules:26: override_dh_auto_test] Error 1 to be marked as d

Bug#1052729: marked as done (cogl: FTBFS if Mesa is currently a release candidate)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1052729, regarding cogl: FTBFS if Mesa is currently a release candidate to be marked as done. This means that you claim that the problem h

Bug#1042231: marked as done (ipxe: FTBFS: arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push')

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1042231, regarding ipxe: FTBFS: arch/x86/image/bootsector.c:85: Error: operand size mismatch for `push' to be marked as done. This means

Bug#1027613: marked as done (onetbb: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned exit code 1)

Your message dated Sun, 29 Oct 2023 14:06:35 +0100 with message-id and subject line Re: Bug#1027613: update has caused the Debian Bug report #1027613, regarding onetbb: FTBFS: dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 MESON_TESTTHREADS=8 ninja test returned exit code 1 to be

Bug#1042153: marked as done (xrdesktop: FTBFS: dh_install: error: missing files, aborting)

Your message dated Sun, 29 Oct 2023 14:28:40 +0100 with message-id and subject line Closing bugs I cannot reproduce anymore. has caused the Debian Bug report #1042153, regarding xrdesktop: FTBFS: dh_install: error: missing files, aborting to be marked as done. This means that you claim that the p

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

Your message dated Sun, 29 Oct 2023 14:05:41 +0100 with message-id and subject line Re: Bug#1031435: python-inotify: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 has caused the Debian Bug report #1031435, regarding python-inotify: FTBFS

Bug#1013560: marked as done (trilinos: FTBFS: src.cxx:6:3: error: ‘isnan’ was not declared in this scope; did you mean ‘std::isnan’?)

Your message dated Sun, 29 Oct 2023 14:09:21 +0100 with message-id and subject line Re: Bug#1013560: trilinos: FTBFS: src.cxx:6:3: error: ‘isnan’ was not declared in this scope; did you mean ‘std::isnan’? has caused the Debian Bug report #1013560, regarding trilinos: FTBFS: src.cxx:6:3: error: ‘i

Bug#1016244: marked as done (trapperkeeper-scheduler-clojure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity)

Your message dated Sun, 29 Oct 2023 14:07:38 +0100 with message-id and subject line Re: Bug#1016244: trapperkeeper-scheduler-clojure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #1016244, regarding trapperkeeper-scheduler-clojure: FTBFS

Bug#982663: marked as done (trapperkeeper-scheduler-clojure: testsuite hangs on buildds)

Your message dated Sun, 29 Oct 2023 14:07:38 +0100 with message-id and subject line Re: Bug#1016244: trapperkeeper-scheduler-clojure: FTBFS: E: Build killed with signal TERM after 150 minutes of inactivity has caused the Debian Bug report #1016244, regarding trapperkeeper-scheduler-clojure: tests

Bug#1011928: marked as done (trilinos: FTBFS with onetbb 2021.5.0)

Your message dated Sun, 29 Oct 2023 14:09:21 +0100 with message-id and subject line Re: Bug#1013560: trilinos: FTBFS: src.cxx:6:3: error: ‘isnan’ was not declared in this scope; did you mean ‘std::isnan’? has caused the Debian Bug report #1013560, regarding trilinos: FTBFS with onetbb 2021.5.0 to

Bug#1031457: marked as done (ruby-redis: FTBFS: ERROR: Test "ruby3.1" failed.)

Your message dated Sun, 29 Oct 2023 14:01:48 +0100 with message-id and subject line Re: Bug#1031457: Unreproducible has caused the Debian Bug report #1031457, regarding ruby-redis: FTBFS: ERROR: Test "ruby3.1" failed. to be marked as done. This means that you claim that the problem has been dealt

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

Your message dated Sun, 29 Oct 2023 14:04:28 +0100 with message-id and subject line Re: Bug#1031444: poetry: FTBFS: dh_auto_test: error: pybuild --test --test-pytest -i python{version} -p 3.11 returned exit code 13 has caused the Debian Bug report #1031444, regarding poetry: FTBFS: dh_auto_test:

Bug#1054777: marked as done (libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2)

Your message dated Sun, 29 Oct 2023 12:34:08 + with message-id and subject line Bug#1054777: fixed in libfiu 1.1-5 has caused the Debian Bug report #1054777, regarding libfiu: FTBFS: dh_auto_test: error: make -j8 test V=1 LC_ALL=C returned exit code 2 to be marked as done. This means that yo

Bug#1054687: marked as done (nmap: FTBFS: ld: nse_main.o:(.data.rel.ro+0x38): undefined reference to `luaopen_lpeg(lua_State*)')

Your message dated Sun, 29 Oct 2023 12:19:35 + with message-id and subject line Bug#1054687: fixed in nmap 7.94+git20230807.3be01efb1+dfsg-2 has caused the Debian Bug report #1054687, regarding nmap: FTBFS: ld: nse_main.o:(.data.rel.ro+0x38): undefined reference to `luaopen_lpeg(lua_State*)'

  1   2   >