Bug#1009384: marked as done (ruby-html-proofer: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(output).to match('successfully')[

Your message dated Sun, 17 Jul 2022 06:35:53 + with message-id and subject line Bug#1009384: fixed in ruby-html-proofer 3.19.2-6 has caused the Debian Bug report #1009384, regarding ruby-html-proofer: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(output).to mat

Bug#871456: marked as done (pgpgpg FTCBFS: uses the build architecture compiler)

Your message dated Sun, 17 Jul 2022 05:03:56 + with message-id and subject line Bug#871456: fixed in pgpgpg 0.13-11 has caused the Debian Bug report #871456, regarding pgpgpg FTCBFS: uses the build architecture compiler to be marked as done. This means that you claim that the problem has been

Bug#809015: marked as done (pgpgpg: New homepage)

Your message dated Sun, 17 Jul 2022 05:03:56 + with message-id and subject line Bug#809015: fixed in pgpgpg 0.13-11 has caused the Debian Bug report #809015, regarding pgpgpg: New homepage to be marked as done. This means that you claim that the problem has been dealt with. If this is not the

Bug#439430: marked as done (pgpgpg: debian/rules should generate md5sums control file)

Your message dated Sun, 17 Jul 2022 05:03:56 + with message-id and subject line Bug#439430: fixed in pgpgpg 0.13-11 has caused the Debian Bug report #439430, regarding pgpgpg: debian/rules should generate md5sums control file to be marked as done. This means that you claim that the problem ha

Bug#1015172: marked as done (wiki.debian.org: Sid installation fails - No kernel modules found - Wiki issue)

Your message dated Sun, 17 Jul 2022 11:23:29 +0800 with message-id and subject line Re: wiki.debian.org: Sid installation fails - No kernel modules found - Wiki issue has caused the Debian Bug report #1015172, regarding wiki.debian.org: Sid installation fails - No kernel modules found - Wiki iss

Bug#1015109: marked as done (rust-sequoia-sq: FTBFS: build-dependency not installable: librust-sequoia-net-0.24-dev)

: 0.26.0-2 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully

Bug#1010362: marked as done (cruft-ng: Segmentation fault in cruft-ng)

Your message dated Sat, 16 Jul 2022 23:33:46 + with message-id and subject line Bug#1010362: fixed in cruft-ng 0.4.53 has caused the Debian Bug report #1010362, regarding cruft-ng: Segmentation fault in cruft-ng to be marked as done. This means that you claim that the problem has been dealt w

Bug#1002109: marked as done (ruby-slim: FTBFS: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:130:in `block (3 levels) in define': Command failed with sta

Your message dated Sat, 16 Jul 2022 23:19:09 + with message-id and subject line Bug#1002109: fixed in ruby-slim 4.1.0-1 has caused the Debian Bug report #1002109, regarding ruby-slim: FTBFS: ERROR: Test "ruby3.0" failed: /usr/lib/ruby/gems/3.0.0/gems/rake-13.0.3/lib/rake/testtask.rb:130:in `b

Bug#1015107: marked as done (gap-hap: FTBFS: make: *** [debian/rules:42: clean] Error 1)

Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Entering directory '/<>/doc' > rm -f {.,../tutorial}/*.{ht

Bug#872615: marked as done (policykit-1: There is no trace of the policyconfig.dtd?)

Your message dated Sat, 16 Jul 2022 22:19:00 + with message-id and subject line Bug#872615: fixed in policykit-1 121-1 has caused the Debian Bug report #872615, regarding policykit-1: There is no trace of the policyconfig.dtd? to be marked as done. This means that you claim that the problem h

Bug#1009384: marked as done (ruby-html-proofer: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(output).to match('successfully')[

Your message dated Sat, 16 Jul 2022 22:04:28 + with message-id and subject line Bug#1009384: fixed in ruby-html-proofer 3.19.2-5 has caused the Debian Bug report #1009384, regarding ruby-html-proofer: FTBFS: ERROR: Test "ruby3.0" failed: Failure/Error: expect(output).to mat

Bug#1015059: marked as done (node-dagre-d3-renderer: FTBFS: make[1]: *** [debian/rules:11: override_dh_auto_build] Error 1)

-dagre-d3-renderer Version: 0.6.4+dfsg-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > make[1]: Enter

Bug#1010035: marked as done (cryptsetup-nuke-password: [INTL:nl] Dutch translation of debconf messages)

Your message dated Sat, 16 Jul 2022 21:34:19 + with message-id and subject line Bug#1010035: fixed in cryptsetup-nuke-password 4 has caused the Debian Bug report #1010035, regarding cryptsetup-nuke-password: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means tha

Bug#1008527: marked as done ([INTL:es] Spanish translation of the debconf template)

Your message dated Sat, 16 Jul 2022 21:34:19 + with message-id and subject line Bug#1008527: fixed in cryptsetup-nuke-password 4 has caused the Debian Bug report #1008527, regarding [INTL:es] Spanish translation of the debconf template to be marked as done. This means that you claim that the

Bug#1007933: marked as done (cryptsetup-nuke-password: [INTL:de] initial German debconf translation)

Your message dated Sat, 16 Jul 2022 21:34:19 + with message-id and subject line Bug#1007933: fixed in cryptsetup-nuke-password 4 has caused the Debian Bug report #1007933, regarding cryptsetup-nuke-password: [INTL:de] initial German debconf translation to be marked as done. This means that yo

Bug#1007237: marked as done (cryptsetup-nuke-password: autopkgtest failure)

Your message dated Sat, 16 Jul 2022 21:34:19 + with message-id and subject line Bug#1007237: fixed in cryptsetup-nuke-password 4 has caused the Debian Bug report #1007237, regarding cryptsetup-nuke-password: autopkgtest failure to be marked as done. This means that you claim that the problem

Bug#1015099: marked as done (wayvnc: FTBFS: ../src/main.c:504:9: error: too few arguments to function ‘nvnc_set_userdata’)

Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > cc -Iwayvnc.p -I. -I.. -I../include -I/usr/include/pixma

Processed: closing 1015041

Processing commands for cont...@bugs.debian.org: > close 1015041 Bug #1015041 [gyp] node-opencv: FTBFS: ModuleNotFoundError: No module named 'six' Bug #1015051 [gyp] node-re2: FTBFS: ModuleNotFoundError: No module named 'six' Bug #1015058 [gyp] node-expat: FTBFS: ModuleNotFoundError: No module na

Bug#999909: marked as done (ckeditor: CVE-2021-41164 CVE-2021-41165)

Your message dated Sat, 16 Jul 2022 21:04:35 + with message-id and subject line Bug#09: fixed in ckeditor 4.19.0+dfsg-1 has caused the Debian Bug report #09, regarding ckeditor: CVE-2021-41164 CVE-2021-41165 to be marked as done. This means that you claim that the problem has been dea

Bug#1014930: marked as done (irssi: FTBFS with Perl 5.36: ISO C90 forbids mixed declarations and code)

Your message dated Sat, 16 Jul 2022 21:05:24 + with message-id and subject line Bug#1014930: fixed in irssi 1.4.2-1 has caused the Debian Bug report #1014930, regarding irssi: FTBFS with Perl 5.36: ISO C90 forbids mixed declarations and code to be marked as done. This means that you claim th

Processed: RFS: streamlink/4.2.0-1~bpo11+1 -- CLI for extracting video streams from various websites to a video player

Processing commands for cont...@bugs.debian.org: > close 1015143 Bug #1015143 [sponsorship-requests] RFS: streamlink/4.2.0-1~bpo11+1 -- CLI for extracting video streams from various websites to a video player Marked Bug as done > stop Stopping processing here. Please contact me if you need assis

Bug#1002925: marked as done (systemd-cron: please add support for cron.yearly)

Your message dated Sat, 16 Jul 2022 20:45:40 + with message-id and subject line Bug#1002925: fixed in systemd-cron 1.15.19-1 has caused the Debian Bug report #1002925, regarding systemd-cron: please add support for cron.yearly to be marked as done. This means that you claim that the problem h

Bug#1015124: marked as done (python-pluggy: FTBFS: dpkg-buildpackage: error: dpkg-source -b . subprocess returned exit status 2)

-pluggy Version: 1.0.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part (hopefully): > debian/rules clean > dh

Bug#1015068: marked as done (python-dbusmock: FTBFS: AssertionError: Regex didn't match: b'[0-9.]+ Notify "fooApp" 0 "warning_icon" "title" "my text" \\[\\] {"urgency": 1} 27\n' not found in b'1657951

ng System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: python-dbusmock Version: 0.28.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your p

Bug#997866: marked as done (usrmerge: cannot handle generated files that have already been re-generated in the new location)

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#997866: fixed in usrmerge 26 has caused the Debian Bug report #997866, regarding usrmerge: cannot handle generated files that have already been re-generated in the new location to be marked as done. This mean

Bug#997866: marked as done (usrmerge: cannot handle generated files that have already been re-generated in the new location)

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#997866: fixed in usrmerge 27 has caused the Debian Bug report #997866, regarding usrmerge: cannot handle generated files that have already been re-generated in the new location to be marked as done. This mean

Bug#1008203: marked as done (usrmerge: add switch to skip conversion (for special-purpose systems like buildds))

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#1008203: fixed in usrmerge 27 has caused the Debian Bug report #1008203, regarding usrmerge: add switch to skip conversion (for special-purpose systems like buildds) to be marked as done. This means that you

Bug#1008203: marked as done (usrmerge: add switch to skip conversion (for special-purpose systems like buildds))

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#1008203: fixed in usrmerge 26 has caused the Debian Bug report #1008203, regarding usrmerge: add switch to skip conversion (for special-purpose systems like buildds) to be marked as done. This means that you

Bug#1008202: marked as done (usrmerge: conversion fails in Docker container (due to overlayfs))

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#1008202: fixed in usrmerge 27 has caused the Debian Bug report #1008202, regarding usrmerge: conversion fails in Docker container (due to overlayfs) to be marked as done. This means that you claim that the pro

Bug#1008202: marked as done (usrmerge: conversion fails in Docker container (due to overlayfs))

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#1008202: fixed in usrmerge 26 has caused the Debian Bug report #1008202, regarding usrmerge: conversion fails in Docker container (due to overlayfs) to be marked as done. This means that you claim that the pro

Bug#1002888: marked as done (usrmerge: please add a "Conflicts: cruft")

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#1002888: fixed in usrmerge 26 has caused the Debian Bug report #1002888, regarding usrmerge: please add a "Conflicts: cruft" to be marked as done. This means that you claim that the problem has been dealt with

Bug#1002888: marked as done (usrmerge: please add a "Conflicts: cruft")

Your message dated Sat, 16 Jul 2022 20:10:09 + with message-id and subject line Bug#1002888: fixed in usrmerge 27 has caused the Debian Bug report #1002888, regarding usrmerge: please add a "Conflicts: cruft" to be marked as done. This means that you claim that the problem has been dealt with

Bug#1006094: marked as done (fonts-roboto-slab: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distribution was not found and is required by fonttools)

Your message dated Sat, 16 Jul 2022 21:54:38 +0200 with message-id <6dcef693-8a59-8558-0604-04d097712...@debian.org> and subject line FTBFS resolved has caused the Debian Bug report #1006094, regarding fonts-roboto-slab: FTBFS: pkg_resources.DistributionNotFound: The 'unicodedata2>=14.0.0' distrib

Bug#1014691: marked as done (wireplumber: kernel complains with wireplumber)

Your message dated Sat, 16 Jul 2022 22:01:29 +0200 with message-id and subject line Re: Bug#1014691: Solved by installing alsa-ucm-conf has caused the Debian Bug report #1014691, regarding wireplumber: kernel complains with wireplumber to be marked as done. This means that you claim that the pro

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

--- Begin Message --- Source: node-configurable-http-proxy Version: 4.5.0+~cs15.1.4-4 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to build on amd64

Bug#1013539: marked as done (newsboat: FTBFS: unsatisfiable build-dependencies: librust-gettext-rs-0.4-dev, librust-gettext-sys-0.19-dev, librust-proptest-0.9+bit-set-dev, librust-proptest-0.9+rusty-f

Your message dated Sat, 16 Jul 2022 19:49:24 + with message-id and subject line Bug#1013539: fixed in newsboat 2.21-1.3 has caused the Debian Bug report #1013539, regarding newsboat: FTBFS: unsatisfiable build-dependencies: librust-gettext-rs-0.4-dev, librust-gettext-sys-0.19-dev, librust-pr

Bug#1011620: marked as done (newsboat - needs update for new gettext crates.)

Your message dated Sat, 16 Jul 2022 19:49:24 + with message-id and subject line Bug#1011620: fixed in newsboat 2.21-1.3 has caused the Debian Bug report #1011620, regarding newsboat - needs update for new gettext crates. to be marked as done. This means that you claim that the problem has bee

Bug#965850: marked as done (ttf-bitstream-vera: Removal of obsolete debhelper compat 5 and 6 in bookworm)

Your message dated Sat, 16 Jul 2022 21:30:53 +0200 with message-id and subject line Already fixed has caused the Debian Bug report #965850, regarding ttf-bitstream-vera: Removal of obsolete debhelper compat 5 and 6 in bookworm to be marked as done. This means that you claim that the problem has

Bug#1015087: marked as done (isoquery: FTBFS: po4a::chooser: Module loading error: Can't locate Syntax/Keyword/Try.pm in @INC)

Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: isoquery Version: 3.3.0-1 Severity: serious Justification: FTBFS Tags: bookworm sid ftbfs User: lu...@debian.org Usertags: ftbfs-20220716 ftbfs-bookworm Hi, During a rebuild of all packages in sid, your package failed to buil

Bug#976243: marked as done (ITP: deepin-log-viewer -- System log viewer of Deepin Desktop Environment)

Your message dated Sat, 16 Jul 2022 19:00:09 + with message-id and subject line Bug#976243: fixed in deepin-log-viewer 5.9.3+ds-1 has caused the Debian Bug report #976243, regarding ITP: deepin-log-viewer -- System log viewer of Deepin Desktop Environment to be marked as done. This means tha

Bug#922102: marked as done (ITP: libopusenc -- High-level API for encoding Ogg Opus audio streams)

Your message dated Sat, 16 Jul 2022 19:00:09 + with message-id and subject line Bug#922102: fixed in libopusenc 0.2.1-1~exp1 has caused the Debian Bug report #922102, regarding ITP: libopusenc -- High-level API for encoding Ogg Opus audio streams to be marked as done. This means that you clai

Bug#1010997: marked as done (ITP: r-cran-leidenbase -- GNU R and C/C++ Wrappers to Run the Leiden find_partition() Function)

Your message dated Sat, 16 Jul 2022 19:00:10 + with message-id and subject line Bug#1010997: fixed in r-cran-leidenbase 0.1.11-1 has caused the Debian Bug report #1010997, regarding ITP: r-cran-leidenbase -- GNU R and C/C++ Wrappers to Run the Leiden find_partition() Function to be marked as

Bug#685575: marked as done (ITP: opentracker -- An open and free bittorrent tracker)

Your message dated Sat, 16 Jul 2022 19:00:10 + with message-id and subject line Bug#685575: fixed in opentracker 0.0~git20210823.110868e-1 has caused the Debian Bug report #685575, regarding ITP: opentracker -- An open and free bittorrent tracker to be marked as done. This means that you clai

Bug#882901: marked as done (php-numbers-words FTBFS with phpunit 6.4.4-2)

Your message dated Sat, 16 Jul 2022 18:32:16 + with message-id and subject line Bug#1015141: Removed package(s) from unstable has caused the Debian Bug report #882901, regarding php-numbers-words FTBFS with phpunit 6.4.4-2 to be marked as done. This means that you claim that the problem has b

Bug#860336: marked as done (parse error in Request.php)

Your message dated Sat, 16 Jul 2022 18:31:11 + with message-id and subject line Bug#1015140: Removed package(s) from unstable has caused the Debian Bug report #860336, regarding parse error in Request.php to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#792195: marked as done (Is this package still useful in Debian?)

Your message dated Sat, 16 Jul 2022 18:30:31 + with message-id and subject line Bug#1015139: Removed package(s) from unstable has caused the Debian Bug report #792195, regarding Is this package still useful in Debian? to be marked as done. This means that you claim that the problem has been d

Bug#1015139: marked as done (RM: php-services-weather -- RoQA; Not maintained upstream)

Your message dated Sat, 16 Jul 2022 18:30:28 + with message-id and subject line Bug#1015139: Removed package(s) from unstable has caused the Debian Bug report #1015139, regarding RM: php-services-weather -- RoQA; Not maintained upstream to be marked as done. This means that you claim that the

Bug#1015141: marked as done (RM: php-numbers-words -- RoQA; Not maintained upstream)

Your message dated Sat, 16 Jul 2022 18:32:13 + with message-id and subject line Bug#1015141: Removed package(s) from unstable has caused the Debian Bug report #1015141, regarding RM: php-numbers-words -- RoQA; Not maintained upstream to be marked as done. This means that you claim that the pr

Bug#1015140: marked as done (RM: php-http-request -- RoQA; Superseded, not used anymore)

Your message dated Sat, 16 Jul 2022 18:31:08 + with message-id and subject line Bug#1015140: Removed package(s) from unstable has caused the Debian Bug report #1015140, regarding RM: php-http-request -- RoQA; Superseded, not used anymore to be marked as done. This means that you claim that th

Bug#960553: marked as done (O: libnet-google-safebrowsing2-perl -- Perl extension for the Google Safe Browsing v2 API)

Your message dated Sat, 16 Jul 2022 18:28:56 + with message-id and subject line Bug#1014985: Removed package(s) from unstable has caused the Debian Bug report #960553, regarding O: libnet-google-safebrowsing2-perl -- Perl extension for the Google Safe Browsing v2 API to be marked as done. Th

Bug#941264: marked as done (phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache)

Your message dated Sat, 16 Jul 2022 18:27:02 + with message-id and subject line Bug#1014698: Removed package(s) from unstable has caused the Debian Bug report #941264, regarding phpunit breaks php-cache-lite autopkgtest: tries to write to /usr/bin/.phpunit.result.cache to be marked as done.

Bug#940275: marked as done (FTBFS with recent PHPUnit (8))

Your message dated Sat, 16 Jul 2022 18:27:02 + with message-id and subject line Bug#1014698: Removed package(s) from unstable has caused the Debian Bug report #940275, regarding FTBFS with recent PHPUnit (8) to be marked as done. This means that you claim that the problem has been dealt with.

Bug#882910: marked as done (php-http-request2 FTBFS with phpunit 6.4.4-2)

Your message dated Sat, 16 Jul 2022 18:27:41 + with message-id and subject line Bug#1014700: Removed package(s) from unstable has caused the Debian Bug report #882910, regarding php-http-request2 FTBFS with phpunit 6.4.4-2 to be marked as done. This means that you claim that the problem has b

Bug#1014985: marked as done (RM: libnet-google-safebrowsing2-perl -- RoQA; orphaned, deprecated, low popcon)

Your message dated Sat, 16 Jul 2022 18:28:53 + with message-id and subject line Bug#1014985: Removed package(s) from unstable has caused the Debian Bug report #1014985, regarding RM: libnet-google-safebrowsing2-perl -- RoQA; orphaned, deprecated, low popcon to be marked as done. This means t

Bug#1014700: marked as done (RM: php-http-request2 -- RoQA; Useless in Debian)

Your message dated Sat, 16 Jul 2022 18:27:38 + with message-id and subject line Bug#1014700: Removed package(s) from unstable has caused the Debian Bug report #1014700, regarding RM: php-http-request2 -- RoQA; Useless in Debian to be marked as done. This means that you claim that the problem

Bug#1014698: marked as done (RM: php-cache-lite -- RoQA; Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:26:59 + with message-id and subject line Bug#1014698: Removed package(s) from unstable has caused the Debian Bug report #1014698, regarding RM: php-cache-lite -- RoQA; Abandoned upstream to be marked as done. This means that you claim that the problem ha

Bug#988440: marked as done (golang-github-seccomp-containers-golang: Keep out of bookworm)

Your message dated Sat, 16 Jul 2022 18:24:54 + with message-id and subject line Bug#1014673: Removed package(s) from unstable has caused the Debian Bug report #988440, regarding golang-github-seccomp-containers-golang: Keep out of bookworm to be marked as done. This means that you claim that

Bug#976794: marked as done (Useless in Debian)

Your message dated Sat, 16 Jul 2022 18:25:17 + with message-id and subject line Bug#1014688: Removed package(s) from unstable has caused the Debian Bug report #976794, regarding Useless in Debian to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1014697: marked as done (RM: php-xml-rpc2 -- RoQA; Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:26:10 + with message-id and subject line Bug#1014697: Removed package(s) from unstable has caused the Debian Bug report #1014697, regarding RM: php-xml-rpc2 -- RoQA; Abandoned upstream to be marked as done. This means that you claim that the problem has

Bug#1014695: marked as done (RM: nanopolish [s390x] -- ROM; nanopolish transitively depends on streamvbyte which does not build on s390x)

Your message dated Sat, 16 Jul 2022 18:25:47 + with message-id and subject line Bug#1014695: Removed package(s) from unstable has caused the Debian Bug report #1014695, regarding RM: nanopolish [s390x] -- ROM; nanopolish transitively depends on streamvbyte which does not build on s390x to be

Bug#1014688: marked as done (RM: php-doctrine-reflection -- ROM; Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:25:14 + with message-id and subject line Bug#1014688: Removed package(s) from unstable has caused the Debian Bug report #1014688, regarding RM: php-doctrine-reflection -- ROM; Abandoned upstream to be marked as done. This means that you claim that the pr

Bug#1014673: marked as done (RM: golang-github-seccomp-containers-golang -- RoQA; Upstream discontinued; obsoleted by golang-github-containers-common)

Your message dated Sat, 16 Jul 2022 18:24:50 + with message-id and subject line Bug#1014673: Removed package(s) from unstable has caused the Debian Bug report #1014673, regarding RM: golang-github-seccomp-containers-golang -- RoQA; Upstream discontinued; obsoleted by golang-github-containers-

Bug#949016: marked as done (Useless in Debian)

Your message dated Sat, 16 Jul 2022 18:24:21 + with message-id and subject line Bug#1014671: Removed package(s) from unstable has caused the Debian Bug report #949016, regarding Useless in Debian to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#1014671: marked as done (RM: php-doctrine-cache-bundle -- ROM; Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:24:18 + with message-id and subject line Bug#1014671: Removed package(s) from unstable has caused the Debian Bug report #1014671, regarding RM: php-doctrine-cache-bundle -- ROM; Abandoned upstream to be marked as done. This means that you claim that the

Bug#1014670: marked as done (RM: php-xml-htmlsax3 -- ROM; Not maintained upstream)

Your message dated Sat, 16 Jul 2022 18:23:46 + with message-id and subject line Bug#1014670: Removed package(s) from unstable has caused the Debian Bug report #1014670, regarding RM: php-xml-htmlsax3 -- ROM; Not maintained upstream to be marked as done. This means that you claim that the prob

Bug#1005383: marked as done (Useless in Debian)

Your message dated Sat, 16 Jul 2022 18:23:49 + with message-id and subject line Bug#1014670: Removed package(s) from unstable has caused the Debian Bug report #1005383, regarding Useless in Debian to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#970342: marked as done (sapphire FTCBFS: does not pass cross tools to make)

Your message dated Sat, 16 Jul 2022 18:20:47 + with message-id and subject line Bug#1014632: Removed package(s) from unstable has caused the Debian Bug report #970342, regarding sapphire FTCBFS: does not pass cross tools to make to be marked as done. This means that you claim that the problem

Bug#999133: marked as done (sapphire: missing required debian/rules targets build-arch and/or build-indep)

Your message dated Sat, 16 Jul 2022 18:20:47 + with message-id and subject line Bug#1014632: Removed package(s) from unstable has caused the Debian Bug report #999133, regarding sapphire: missing required debian/rules targets build-arch and/or build-indep to be marked as done. This means tha

Bug#936459: marked as done (dvcs-autosync: Python2 removal in sid/bullseye)

Your message dated Sat, 16 Jul 2022 18:21:52 + with message-id and subject line Bug#1014656: Removed package(s) from unstable has caused the Debian Bug report #936459, regarding dvcs-autosync: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#935639: marked as done (Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:23:25 + with message-id and subject line Bug#1014669: Removed package(s) from unstable has caused the Debian Bug report #935639, regarding Abandoned upstream to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#910813: marked as done (doc-linux-fr: FTBFS, latex error "Package inputenc Error: Invalid UTF-8 byte sequence")

Your message dated Sat, 16 Jul 2022 18:22:21 + with message-id and subject line Bug#1014667: Removed package(s) from unstable has caused the Debian Bug report #910813, regarding doc-linux-fr: FTBFS, latex error "Package inputenc Error: Invalid UTF-8 byte sequence" to be marked as done. This

Bug#935384: marked as done (Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:22:53 + with message-id and subject line Bug#1014668: Removed package(s) from unstable has caused the Debian Bug report #935384, regarding Abandoned upstream to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#880786: marked as done (doc-linux-fr build depends on removed transitional package lynx-cur)

Your message dated Sat, 16 Jul 2022 18:22:21 + with message-id and subject line Bug#1014667: Removed package(s) from unstable has caused the Debian Bug report #880786, regarding doc-linux-fr build depends on removed transitional package lynx-cur to be marked as done. This means that you claim

Bug#906953: marked as done (doc-linux-fr: French translations of horribly outdated documentation)

Your message dated Sat, 16 Jul 2022 18:22:21 + with message-id and subject line Bug#1014667: Removed package(s) from unstable has caused the Debian Bug report #906953, regarding doc-linux-fr: French translations of horribly outdated documentation to be marked as done. This means that you clai

Bug#726236: marked as done (dvcs-autosync: crashes when attempting to log configuration warning)

Your message dated Sat, 16 Jul 2022 18:21:52 + with message-id and subject line Bug#1014656: Removed package(s) from unstable has caused the Debian Bug report #726236, regarding dvcs-autosync: crashes when attempting to log configuration warning to be marked as done. This means that you claim

Bug#530068: marked as done (doc-linux-fr-html: bashism in /bin/sh script)

Your message dated Sat, 16 Jul 2022 18:22:21 + with message-id and subject line Bug#1014667: Removed package(s) from unstable has caused the Debian Bug report #530068, regarding doc-linux-fr-html: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has b

Bug#699365: marked as done (sapphire: cobwebby package description)

Your message dated Sat, 16 Jul 2022 18:20:47 + with message-id and subject line Bug#1014632: Removed package(s) from unstable has caused the Debian Bug report #699365, regarding sapphire: cobwebby package description to be marked as done. This means that you claim that the problem has been de

Bug#1014669: marked as done (RM: phpunit-dbunit -- ROM; Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:23:18 + with message-id and subject line Bug#1014669: Removed package(s) from unstable has caused the Debian Bug report #1014669, regarding RM: phpunit-dbunit -- ROM; Abandoned upstream to be marked as done. This means that you claim that the problem has

Bug#1014668: marked as done (RM: phpunit-git -- ROM; Abandoned upstream)

Your message dated Sat, 16 Jul 2022 18:22:47 + with message-id and subject line Bug#1014668: Removed package(s) from unstable has caused the Debian Bug report #1014668, regarding RM: phpunit-git -- ROM; Abandoned upstream to be marked as done. This means that you claim that the problem has be

Bug#1014667: marked as done (RM: doc-linux-fr -- ROM; Outdated documentation, FTBFS)

Your message dated Sat, 16 Jul 2022 18:22:12 + with message-id and subject line Bug#1014667: Removed package(s) from unstable has caused the Debian Bug report #1014667, regarding RM: doc-linux-fr -- ROM; Outdated documentation, FTBFS to be marked as done. This means that you claim that the pr

Bug#1014656: marked as done (RM: dvcs-autosync -- RoM; Unmaintained; Blocking Python2 Removal)

Your message dated Sat, 16 Jul 2022 18:21:44 + with message-id and subject line Bug#1014656: Removed package(s) from unstable has caused the Debian Bug report #1014656, regarding RM: dvcs-autosync -- RoM; Unmaintained; Blocking Python2 Removal to be marked as done. This means that you claim t

Bug#1014632: marked as done (RM: sapphire -- RoQA; FTBFS; dead upstream; unmaintained; very low popcon)

Your message dated Sat, 16 Jul 2022 18:20:39 + with message-id and subject line Bug#1014632: Removed package(s) from unstable has caused the Debian Bug report #1014632, regarding RM: sapphire -- RoQA; FTBFS; dead upstream; unmaintained; very low popcon to be marked as done. This means that y

Bug#1014411: marked as done (dvcs-autosync: Should we remove this package?)

Your message dated Sat, 16 Jul 2022 18:21:52 + with message-id and subject line Bug#1014656: Removed package(s) from unstable has caused the Debian Bug report #1014411, regarding dvcs-autosync: Should we remove this package? to be marked as done. This means that you claim that the problem has

Bug#997138: marked as done (ffdiaporama: FTBFS: engine/_EncodeVideo.cpp:134:46: error: ‘AVStream’ {aka ‘struct AVStream’} has no member named ‘probe_data’; did you mean ‘priv_data’?)

Your message dated Sat, 16 Jul 2022 18:17:10 + with message-id and subject line Bug#1014378: Removed package(s) from unstable has caused the Debian Bug report #997138, regarding ffdiaporama: FTBFS: engine/_EncodeVideo.cpp:134:46: error: ‘AVStream’ {aka ‘struct AVStream’} has no member named ‘

Bug#993538: marked as done (libzapojit: CVE-2021-39360)

Your message dated Sat, 16 Jul 2022 18:19:42 + with message-id and subject line Bug#1014464: Removed package(s) from unstable has caused the Debian Bug report #993538, regarding libzapojit: CVE-2021-39360 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#909869: marked as done (O: libgroove -- audio dispatching library)

Your message dated Sat, 16 Jul 2022 18:18:46 + with message-id and subject line Bug#1014384: Removed package(s) from unstable has caused the Debian Bug report #909869, regarding O: libgroove -- audio dispatching library to be marked as done. This means that you claim that the problem has been

Bug#829891: marked as done (libzapojit: Uses deprecated gnome-common macros/variables)

Your message dated Sat, 16 Jul 2022 18:19:42 + with message-id and subject line Bug#1014464: Removed package(s) from unstable has caused the Debian Bug report #829891, regarding libzapojit: Uses deprecated gnome-common macros/variables to be marked as done. This means that you claim that the

Bug#1014462: marked as done (libzapojit: unmaintained, only used by gnome-documents)

Your message dated Sat, 16 Jul 2022 18:19:42 + with message-id and subject line Bug#1014464: Removed package(s) from unstable has caused the Debian Bug report #1014462, regarding libzapojit: unmaintained, only used by gnome-documents to be marked as done. This means that you claim that the pr

Bug#909756: marked as done (ffdiaporama: Files not showing)

Your message dated Sat, 16 Jul 2022 18:17:10 + with message-id and subject line Bug#1014378: Removed package(s) from unstable has caused the Debian Bug report #909756, regarding ffdiaporama: Files not showing to be marked as done. This means that you claim that the problem has been dealt with

Bug#802570: marked as done (ffdiaporama: Program crash when trying to create a movie with codec H264 in 1080p 25 FPS)

Your message dated Sat, 16 Jul 2022 18:17:10 + with message-id and subject line Bug#1014378: Removed package(s) from unstable has caused the Debian Bug report #802570, regarding ffdiaporama: Program crash when trying to create a movie with codec H264 in 1080p 25 FPS to be marked as done. Thi

Bug#1014464: marked as done (RM: libzapojit -- RoM; unmaintained)

Your message dated Sat, 16 Jul 2022 18:19:34 + with message-id and subject line Bug#1014464: Removed package(s) from unstable has caused the Debian Bug report #1014464, regarding RM: libzapojit -- RoM; unmaintained to be marked as done. This means that you claim that the problem has been deal

Bug#1004613: marked as done (nordlicht: FTBFS with ffmpeg 5.0)

Your message dated Sat, 16 Jul 2022 18:17:47 + with message-id and subject line Bug#1014381: Removed package(s) from unstable has caused the Debian Bug report #1004613, regarding nordlicht: FTBFS with ffmpeg 5.0 to be marked as done. This means that you claim that the problem has been dealt w

Bug#1014384: marked as done (RM: libgroove -- RoQA; dead upstream, orphaned, unused)

Your message dated Sat, 16 Jul 2022 18:18:39 + with message-id and subject line Bug#1014384: Removed package(s) from unstable has caused the Debian Bug report #1014384, regarding RM: libgroove -- RoQA; dead upstream, orphaned, unused to be marked as done. This means that you claim that the pr

Bug#1014378: marked as done (RM: ffdiaporama -- RoQA; dead upstream, unmaintained)

Your message dated Sat, 16 Jul 2022 18:17:02 + with message-id and subject line Bug#1014378: Removed package(s) from unstable has caused the Debian Bug report #1014378, regarding RM: ffdiaporama -- RoQA; dead upstream, unmaintained to be marked as done. This means that you claim that the prob

Bug#1013422: marked as done (libgroove FTBFS with ffmpeg 5.0.1)

Your message dated Sat, 16 Jul 2022 18:18:46 + with message-id and subject line Bug#1014384: Removed package(s) from unstable has caused the Debian Bug report #1013422, regarding libgroove FTBFS with ffmpeg 5.0.1 to be marked as done. This means that you claim that the problem has been dealt

Bug#1014381: marked as done (RM: nordlicht -- RoQA; dead upstream)

Your message dated Sat, 16 Jul 2022 18:17:40 + with message-id and subject line Bug#1014381: Removed package(s) from unstable has caused the Debian Bug report #1014381, regarding RM: nordlicht -- RoQA; dead upstream to be marked as done. This means that you claim that the problem has been dea

Bug#1014281: marked as done (ffdiaporama: Crashes on start with "malloc(): corrupted top size")

Your message dated Sat, 16 Jul 2022 18:17:10 + with message-id and subject line Bug#1014378: Removed package(s) from unstable has caused the Debian Bug report #1014281, regarding ffdiaporama: Crashes on start with "malloc(): corrupted top size" to be marked as done. This means that you claim

Bug#980023: marked as done (petri-foo: FTBFS with GCC 10)

Your message dated Sat, 16 Jul 2022 18:14:51 + with message-id and subject line Bug#1014144: Removed package(s) from unstable has caused the Debian Bug report #980023, regarding petri-foo: FTBFS with GCC 10 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#967691: marked as done (petri-foo: depends on deprecated GTK 2)

Your message dated Sat, 16 Jul 2022 18:14:51 + with message-id and subject line Bug#1014144: Removed package(s) from unstable has caused the Debian Bug report #967691, regarding petri-foo: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been de

Bug#885781: marked as done (petri-foo: Depends on libgnomecanvas)

Your message dated Sat, 16 Jul 2022 18:14:51 + with message-id and subject line Bug#1014144: Removed package(s) from unstable has caused the Debian Bug report #885781, regarding petri-foo: Depends on libgnomecanvas to be marked as done. This means that you claim that the problem has been deal

  1   2   >