Bug#1000807: marked as done (python-mpv: patch to fix flaky test on ppc64el)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 17:40:50 + with message-id and subject line Bug#1000807: fixed in python-mpv 0.5.2-3 has caused the Debian Bug report #1000807, regarding python-mpv: patch to fix flaky test on ppc64el to be marked as done. This means that you claim that the problem has

Bug#997959: marked as done (RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:42:25 + with message-id and subject line Bug#997959: Removed package(s) from unstable has caused the Debian Bug report #997959, regarding RM: git-annex [armel armhf] -- ROM; enduring issues building on 32-bit ARM architectures to be marked as done.

Bug#998277: marked as done (RM: opencaster -- RoQA; Depends on Python 2, dead upstream)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:44:25 + with message-id and subject line Bug#998277: Removed package(s) from unstable has caused the Debian Bug report #998277, regarding RM: opencaster -- RoQA; Depends on Python 2, dead upstream to be marked as done. This means that you claim that the

Bug#998276: marked as done (RM: libvirt-sandbox -- RoQA; Depends on Python 2, dead upstream)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:43:21 + with message-id and subject line Bug#998276: Removed package(s) from unstable has caused the Debian Bug report #998276, regarding RM: libvirt-sandbox -- RoQA; Depends on Python 2, dead upstream to be marked as done. This means that you claim

Bug#998324: marked as done (RM: openjdk-16 -- superseded by openjdk-17)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:42:47 + with message-id and subject line Bug#998324: Removed package(s) from unstable has caused the Debian Bug report #998324, regarding RM: openjdk-16 -- superseded by openjdk-17 to be marked as done. This means that you claim that the problem has

Bug#884753: marked as done (virt-sandbox: crash (SIGSEGV) when starting two instances at the same time)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:43:26 + with message-id and subject line Bug#998276: Removed package(s) from unstable has caused the Debian Bug report #884753, regarding virt-sandbox: crash (SIGSEGV) when starting two instances at the same time to be marked as done. This means that

Bug#966755: marked as done (libvirt-sandbox: Unversioned Python removal in sid/bullseye)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:43:26 + with message-id and subject line Bug#998276: Removed package(s) from unstable has caused the Debian Bug report #936935, regarding libvirt-sandbox: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that

Bug#939940: marked as done (libvirt-sandbox: missing python build-dependency causes FTBFS with gtk-doc-tools 1.32)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:43:26 + with message-id and subject line Bug#998276: Removed package(s) from unstable has caused the Debian Bug report #939940, regarding libvirt-sandbox: missing python build-dependency causes FTBFS with gtk-doc-tools 1.32 to be marked as done. This

Bug#887232: marked as done (virt-sandbox should depend on e2fsprogs explicitly)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:43:26 + with message-id and subject line Bug#998276: Removed package(s) from unstable has caused the Debian Bug report #887232, regarding virt-sandbox should depend on e2fsprogs explicitly to be marked as done. This means that you claim that the problem

Bug#936935: marked as done (libvirt-sandbox: Python2 removal in sid/bullseye)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:43:26 + with message-id and subject line Bug#998276: Removed package(s) from unstable has caused the Debian Bug report #936935, regarding libvirt-sandbox: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#858463: marked as done (opencaster: /usr/bin/oc-update script invoke invalid file2mod.py and mod2sec.py scripts)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:44:31 + with message-id and subject line Bug#998277: Removed package(s) from unstable has caused the Debian Bug report #858463, regarding opencaster: /usr/bin/oc-update script invoke invalid file2mod.py and mod2sec.py scripts to be marked as done. This

Bug#966769: marked as done (opencaster: Unversioned Python removal in sid/bullseye)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:44:31 + with message-id and subject line Bug#998277: Removed package(s) from unstable has caused the Debian Bug report #937194, regarding opencaster: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#937194: marked as done (opencaster: Python2 removal in sid/bullseye)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:44:31 + with message-id and subject line Bug#998277: Removed package(s) from unstable has caused the Debian Bug report #937194, regarding opencaster: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#1000156: marked as done (roundcube: XSS vulnerability in handling attachment filename extension in MIME type mismatch warnings)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 17:47:28 + with message-id and subject line Bug#1000156: fixed in roundcube 1.4.12+dfsg.1-1~deb11u1 has caused the Debian Bug report #1000156, regarding roundcube: XSS vulnerability in handling attachment filename extension in MIME type mismatch warnings

Bug#997025: marked as done (RM: node-request-promise-core -- ROM; Obsolete and now useless)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:37:49 + with message-id and subject line Bug#997025: Removed package(s) from unstable has caused the Debian Bug report #997025, regarding RM: node-request-promise-core -- ROM; Obsolete and now useless to be marked as done. This means that you claim that

Bug#997612: marked as done (vatnumber: FTBFS: error in vatnumber setup command: use_2to3 is invalid.)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:38:52 + with message-id and subject line Bug#997815: Removed package(s) from unstable has caused the Debian Bug report #997612, regarding vatnumber: FTBFS: error in vatnumber setup command: use_2to3 is invalid. to be marked as done. This means that you

Bug#997692: marked as done (RM: crystalhd -- ROM; unusable without usable firmware)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:38:18 + with message-id and subject line Bug#997692: Removed package(s) from unstable has caused the Debian Bug report #997692, regarding RM: crystalhd -- ROM; unusable without usable firmware to be marked as done. This means that you claim that the

Bug#997815: marked as done (RM: vatnumber -- ROM; abandoned by upstream)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:38:46 + with message-id and subject line Bug#997815: Removed package(s) from unstable has caused the Debian Bug report #997815, regarding RM: vatnumber -- ROM; abandoned by upstream to be marked as done. This means that you claim that the problem has

Bug#976351: marked as done (node-request: deprecated upstream: should not be part of next stable Debian release)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:37:53 + with message-id and subject line Bug#997025: Removed package(s) from unstable has caused the Debian Bug report #976351, regarding node-request: deprecated upstream: should not be part of next stable Debian release to be marked as done. This

Bug#996067: marked as done (gnome-shell-extension-no-annoyance: does not declare compatibility with GNOME Shell 41)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:36:06 + with message-id and subject line Bug#997007: Removed package(s) from unstable has caused the Debian Bug report #996067, regarding gnome-shell-extension-no-annoyance: does not declare compatibility with GNOME Shell 41 to be marked as done. This

Bug#997017: marked as done (RM: rust-capstone [armel armhf i386 mips64el mipsel ppc64el s390x] -- ROM; Only {amd,arm}64 for now)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:36:24 + with message-id and subject line Bug#997017: Removed package(s) from unstable has caused the Debian Bug report #997017, regarding RM: rust-capstone [armel armhf i386 mips64el mipsel ppc64el s390x] -- ROM; Only {amd,arm}64 for now to be marked as

Bug#997018: marked as done (RM: rust-elfx86exts [armhf i386 mips64el mipsel ppc64el s390x] -- ROM; Only {amd,arm}64 for now)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:37:23 + with message-id and subject line Bug#997018: Removed package(s) from unstable has caused the Debian Bug report #997018, regarding RM: rust-elfx86exts [armhf i386 mips64el mipsel ppc64el s390x] -- ROM; Only {amd,arm}64 for now to be marked as

Bug#997007: marked as done (RM: gnome-shell-extension-no-annoyance -- ROM; No longer needed/useful for gnome-shell version 40+)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:36:01 + with message-id and subject line Bug#997007: Removed package(s) from unstable has caused the Debian Bug report #997007, regarding RM: gnome-shell-extension-no-annoyance -- ROM; No longer needed/useful for gnome-shell version 40+ to be marked as

Bug#897124: marked as done (crystalhd cannot be rebuilt from source: autoreconf fails in filters/gst/gst-plugin)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:38:25 + with message-id and subject line Bug#997692: Removed package(s) from unstable has caused the Debian Bug report #897124, regarding crystalhd cannot be rebuilt from source: autoreconf fails in filters/gst/gst-plugin to be marked as done. This

Bug#934242: marked as done (crystalhd: unusable without (available and properly working) firmware)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:38:25 + with message-id and subject line Bug#997692: Removed package(s) from unstable has caused the Debian Bug report #934242, regarding crystalhd: unusable without (available and properly working) firmware to be marked as done. This means that you

Bug#958689: marked as done (node-request-promise-core: Remove dependency to node-request)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:37:53 + with message-id and subject line Bug#997025: Removed package(s) from unstable has caused the Debian Bug report #958689, regarding node-request-promise-core: Remove dependency to node-request to be marked as done. This means that you claim that

Bug#942587: marked as done (Build crystalhd on ppc64el)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:38:25 + with message-id and subject line Bug#997692: Removed package(s) from unstable has caused the Debian Bug report #942587, regarding Build crystalhd on ppc64el to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#572568: marked as done (libhttpclient-ruby1.9.1: formating suggestions for long description)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 21:04:41 + with message-id and subject line Bug#572568: fixed in ruby-httpclient 2.8.3+git20211122.4658227-1 has caused the Debian Bug report #572568, regarding libhttpclient-ruby1.9.1: formating suggestions for long description to be marked as done. This

Bug#996294: marked as done (ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed.)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 21:04:41 + with message-id and subject line Bug#996294: fixed in ruby-httpclient 2.8.3+git20211122.4658227-1 has caused the Debian Bug report #996294, regarding ruby-httpclient: FTBFS with ruby3.0: ERROR: Test "ruby3.0" failed. to be marked as done. This

Bug#928278: marked as done (dmeventd: raid1 fails to automatically rebuild when raid_fault_policy="allocate")

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 13:13:21 -0800 with message-id and subject line fixed since v2_03_06 has caused the Debian Bug report #928278, regarding dmeventd: raid1 fails to automatically rebuild when raid_fault_policy="allocate" to be marked as done. This means that you claim that the

Bug#979915: marked as done (isso: node-uglify is deprecated in favor of uglifyjs)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:11:59 + with message-id and subject line Bug#1000677: Removed package(s) from unstable has caused the Debian Bug report #979915, regarding isso: node-uglify is deprecated in favor of uglifyjs to be marked as done. This means that you claim that the

Bug#993630: marked as done (isso depends on deprecated node-jade which is going to be removed)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:11:59 + with message-id and subject line Bug#1000677: Removed package(s) from unstable has caused the Debian Bug report #993630, regarding isso depends on deprecated node-jade which is going to be removed to be marked as done. This means that you claim

Bug#1000554: marked as done (RFS: libfm-qt/1.0.0-0.1 [NMU] [RC] -- Language package for libfm-qt)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 13:12:45 -0500 with message-id <290df257-a2e4-0fee-c103-f83198a04...@gmail.com> and subject line has caused the Debian Bug report #1000554, regarding RFS: libfm-qt/1.0.0-0.1 [NMU] [RC] -- Language package for libfm-qt to be marked as done. This means that you

Bug#1000635: marked as done (node-monocle is incompatible with current node-readdirp)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:13:06 + with message-id and subject line Bug#1000687: Removed package(s) from unstable has caused the Debian Bug report #1000635, regarding node-monocle is incompatible with current node-readdirp to be marked as done. This means that you claim that the

Bug#1000677: marked as done (RM: isso -- ROM; RC-buggy for a long time)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:11:54 + with message-id and subject line Bug#1000677: Removed package(s) from unstable has caused the Debian Bug report #1000677, regarding RM: isso -- ROM; RC-buggy for a long time to be marked as done. This means that you claim that the problem has

Bug#1000641: marked as done (RM: libopencv4.2-java -- ROM; superseeded by libopencv4.5-java)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:11:04 + with message-id and subject line Bug#1000641: Removed package(s) from unstable has caused the Debian Bug report #1000641, regarding RM: libopencv4.2-java -- ROM; superseeded by libopencv4.5-java to be marked as done. This means that you claim

Bug#1000686: marked as done (RM: node-jade -- ROM; Broken, orphaned upstream and useless)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:12:29 + with message-id and subject line Bug#1000686: Removed package(s) from unstable has caused the Debian Bug report #1000686, regarding RM: node-jade -- ROM; Broken, orphaned upstream and useless to be marked as done. This means that you claim that

Bug#1000687: marked as done (RM: node-monocle -- ROM; Broken, useless and orphaned upstream)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:13:03 + with message-id and subject line Bug#1000687: Removed package(s) from unstable has caused the Debian Bug report #1000687, regarding RM: node-monocle -- ROM; Broken, useless and orphaned upstream to be marked as done. This means that you claim

Bug#932484: marked as done (isso gives 404 when started via systemd)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:11:59 + with message-id and subject line Bug#1000677: Removed package(s) from unstable has caused the Debian Bug report #932484, regarding isso gives 404 when started via systemd to be marked as done. This means that you claim that the problem has been

Bug#959644: marked as done (isso: FTBFS: TypeError: Jade:1)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:11:59 + with message-id and subject line Bug#1000677: Removed package(s) from unstable has caused the Debian Bug report #959644, regarding isso: FTBFS: TypeError: Jade:1 to be marked as done. This means that you claim that the problem has been dealt

Bug#987967: marked as done (jade replaced by pug for ages, doesn't work anymore)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:12:32 + with message-id and subject line Bug#1000686: Removed package(s) from unstable has caused the Debian Bug report #987967, regarding jade replaced by pug for ages, doesn't work anymore to be marked as done. This means that you claim that the

Bug#995101: marked as done (ImportError: cannot import name SharedDataMiddleware)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:11:59 + with message-id and subject line Bug#1000677: Removed package(s) from unstable has caused the Debian Bug report #995101, regarding ImportError: cannot import name SharedDataMiddleware to be marked as done. This means that you claim that the

Bug#165865: marked as done (logidee-tools: should use standard xml:lang attribute instead of Makefile variable)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #165865, regarding logidee-tools: should use standard xml:lang attribute instead of Makefile variable to be marked as done. This

Bug#996703: marked as done (RM: gnome-shell-timer -- ROM; No upstream maintainer)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:01 + with message-id and subject line Bug#996703: Removed package(s) from unstable has caused the Debian Bug report #996703, regarding RM: gnome-shell-timer -- ROM; No upstream maintainer to be marked as done. This means that you claim that the

Bug#996874: marked as done (RM: theme-d-gnome -- ROM; Not compatible with Guile 3.0)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:35:18 + with message-id and subject line Bug#996874: Removed package(s) from unstable has caused the Debian Bug report #996874, regarding RM: theme-d-gnome -- ROM; Not compatible with Guile 3.0 to be marked as done. This means that you claim that the

Bug#996776: marked as done (RM: logidee-tools -- ROM; no longer maintained and no longer used)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:35 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #996776, regarding RM: logidee-tools -- ROM; no longer maintained and no longer used to be marked as done. This means that you claim

Bug#166066: marked as done (logidee-tools: message for disallowed sub*section is too terse)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #166066, regarding logidee-tools: message for disallowed sub*section is too terse to be marked as done. This means that you claim that

Bug#997404: marked as done (theme-d-gnome: FTBFS: dh_auto_configure: Error: Guile version 2.2 not found.)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:35:24 + with message-id and subject line Bug#996874: Removed package(s) from unstable has caused the Debian Bug report #997404, regarding theme-d-gnome: FTBFS: dh_auto_configure: Error: Guile version 2.2 not found. to be marked as done. This means that

Bug#997522: marked as done (logidee-tools: FTBFS: make[2]: kpsepath: No such file or directory)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #997522, regarding logidee-tools: FTBFS: make[2]: kpsepath: No such file or directory to be marked as done. This means that you claim

Bug#169605: marked as done (logidee-tools: wrong rendering of within module's title)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #169605, regarding logidee-tools: wrong rendering of within module's title to be marked as done. This means that you claim that the

Bug#171050: marked as done (logidee-tools: within is rendered as normal text)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #171050, regarding logidee-tools: within is rendered as normal text to be marked as done. This means that you claim that the problem

Bug#170679: marked as done (logidee-tools: replace TRAINER= parameter with *_trainer.tex targets)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #170679, regarding logidee-tools: replace TRAINER= parameter with *_trainer.tex targets to be marked as done. This means that you

Bug#171158: marked as done (logidee-tools: a slide per exercise would be nice)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #171158, regarding logidee-tools: a slide per exercise would be nice to be marked as done. This means that you claim that the problem

Bug#993204: marked as done (gnome-shell-timer: does not declare compatibility with GNOME Shell 41)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:04 + with message-id and subject line Bug#996703: Removed package(s) from unstable has caused the Debian Bug report #993204, regarding gnome-shell-timer: does not declare compatibility with GNOME Shell 41 to be marked as done. This means that you

Bug#996079: marked as done (gnome-shell-timer: does not declare compatibility with GNOME Shell 41)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:04 + with message-id and subject line Bug#996703: Removed package(s) from unstable has caused the Debian Bug report #993204, regarding gnome-shell-timer: does not declare compatibility with GNOME Shell 41 to be marked as done. This means that you

Bug#165210: marked as done (logidee-tools: block-level elements should be allowed outside of paras)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #165210, regarding logidee-tools: block-level elements should be allowed outside of paras to be marked as done. This means that you

Bug#995445: marked as done (logidee-tools: creates incorrect TeX code, breaks other packages via autopkgtests)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #995445, regarding logidee-tools: creates incorrect TeX code, breaks other packages via autopkgtests to be marked as done. This means

Bug#996675: marked as done (RM: memkind/experimental -- NVIU; manual removal due to dropped archs)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:33:10 + with message-id and subject line Bug#996675: Removed package(s) from experimental has caused the Debian Bug report #996675, regarding RM: memkind/experimental -- NVIU; manual removal due to dropped archs to be marked as done. This means that you

Bug#293640: marked as done (logidee-tools: Lacks translation to brazilian portuguese)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #293640, regarding logidee-tools: Lacks translation to brazilian portuguese to be marked as done. This means that you claim that the

Bug#163184: marked as done (logidee-tools: should issue meaningful error when requested CHARTE is inexistant)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #163184, regarding logidee-tools: should issue meaningful error when requested CHARTE is inexistant to be marked as done. This means

Bug#861933: marked as done (gnome-shell-timer: changing defaults or presets does not change menu until GNOME shell restarts)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:04 + with message-id and subject line Bug#996703: Removed package(s) from unstable has caused the Debian Bug report #861933, regarding gnome-shell-timer: changing defaults or presets does not change menu until GNOME shell restarts to be marked as

Bug#165206: marked as done (logidee-tools: PDFs should be generated without intermediate PS)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #165206, regarding logidee-tools: PDFs should be generated without intermediate PS to be marked as done. This means that you claim

Bug#157728: marked as done (logidee-tools: legal notice put in the wrong place)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #157728, regarding logidee-tools: legal notice put in the wrong place to be marked as done. This means that you claim that the problem

Bug#163211: marked as done (logidee-tools: annoying rendering of )

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #163211, regarding logidee-tools: annoying rendering of to be marked as done. This means that you claim that the problem has been

Bug#164850: marked as done (logidee-tools: seems limited to 52chars width)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #164850, regarding logidee-tools: seems limited to 52chars width to be marked as done. This means that you claim that the problem has

Bug#165917: marked as done (logidee-tools: should allow inside and )

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:34:46 + with message-id and subject line Bug#996776: Removed package(s) from unstable has caused the Debian Bug report #165917, regarding logidee-tools: should allow inside and to be marked as done. This means that you claim that the problem has been

Bug#984180: marked as done (htdig: ftbfs with GCC-11)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:48:48 + with message-id and subject line Bug#984180: fixed in htdig 1:3.2.0b6-19 has caused the Debian Bug report #984180, regarding htdig: ftbfs with GCC-11 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#998475: marked as done (RM: boolean.py -- ROM; superseded by src:python-boolean.py)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:49:39 + with message-id and subject line Bug#998475: Removed package(s) from unstable has caused the Debian Bug report #998475, regarding RM: boolean.py -- ROM; superseded by src:python-boolean.py to be marked as done. This means that you claim that the

Bug#967496: marked as done (gtkmathview: depends on deprecated GTK 2)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:20:02 + with message-id and subject line Bug#702011: Removed package(s) from unstable has caused the Debian Bug report #967496, regarding gtkmathview: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been

Bug#797509: marked as done (RFA: gtkmathview -- rendering engine for MathML documents)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:20:02 + with message-id and subject line Bug#702011: Removed package(s) from unstable has caused the Debian Bug report #797509, regarding RFA: gtkmathview -- rendering engine for MathML documents to be marked as done. This means that you claim that the

Bug#1000799: marked as done (django-rules: Duplicate package of python-django-rules)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:18:18 + with message-id and subject line Bug#1000800: Removed package(s) from unstable has caused the Debian Bug report #1000799, regarding django-rules: Duplicate package of python-django-rules to be marked as done. This means that you claim that the

Bug#1000800: marked as done (RM: django-rules -- RoQA; duplicate source package; dak rm -S)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:18:12 + with message-id and subject line Bug#1000800: Removed package(s) from unstable has caused the Debian Bug report #1000800, regarding RM: django-rules -- RoQA; duplicate source package; dak rm -S to be marked as done. This means that you claim

Bug#560741: marked as done (FTBFS: /usr/bin/ld: cannot find -lstdc++)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:20:02 + with message-id and subject line Bug#702011: Removed package(s) from unstable has caused the Debian Bug report #560741, regarding FTBFS: /usr/bin/ld: cannot find -lstdc++ to be marked as done. This means that you claim that the problem has been

Bug#702011: marked as done (RM: gtkmathview -- RoQA; dead upstream)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:19:55 + with message-id and subject line Bug#702011: Removed package(s) from unstable has caused the Debian Bug report #702011, regarding RM: gtkmathview -- RoQA; dead upstream to be marked as done. This means that you claim that the problem has been

Bug#967652: marked as done (nekobee: depends on deprecated GTK 2)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:27:50 + with message-id and subject line Bug#992319: Removed package(s) from unstable has caused the Debian Bug report #967652, regarding nekobee: depends on deprecated GTK 2 to be marked as done. This means that you claim that the problem has been

Bug#992319: marked as done (RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:27:43 + with message-id and subject line Bug#992319: Removed package(s) from unstable has caused the Debian Bug report #992319, regarding RM: nekobee -- RoQA, unmaintained, RC-buggy, dead-upstream, python2 to be marked as done. This means that you claim

Bug#993294: marked as done (RM: libidn11-java [all] -- NBS; needs manual cruft removal)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:29:13 + with message-id and subject line Bug#993294: Removed package(s) from unstable has caused the Debian Bug report #993294, regarding RM: libidn11-java [all] -- NBS; needs manual cruft removal to be marked as done. This means that you claim that the

Bug#937126: marked as done (nekobee: Python2 removal in sid/bullseye)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:27:50 + with message-id and subject line Bug#992319: Removed package(s) from unstable has caused the Debian Bug report #937126, regarding nekobee: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#957588: marked as done (nekobee: ftbfs with GCC-10)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:27:50 + with message-id and subject line Bug#992319: Removed package(s) from unstable has caused the Debian Bug report #957588, regarding nekobee: ftbfs with GCC-10 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#967182: marked as done (nekobee: Unversioned Python removal in sid/bullseye)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:27:50 + with message-id and subject line Bug#992319: Removed package(s) from unstable has caused the Debian Bug report #967182, regarding nekobee: Unversioned Python removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#1000215: marked as done (glusterfs: FTBFS on armel, armhf, mipsel)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 19:33:46 + with message-id and subject line Bug#1000215: fixed in glusterfs 10.0-1.3 has caused the Debian Bug report #1000215, regarding glusterfs: FTBFS on armel, armhf, mipsel to be marked as done. This means that you claim that the problem has been

Bug#856380: marked as done (Updating the ruby-wirble Uploaders list)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:40:38 + with message-id and subject line Bug#997893: Removed package(s) from unstable has caused the Debian Bug report #856380, regarding Updating the ruby-wirble Uploaders list to be marked as done. This means that you claim that the problem has been

Bug#980348: marked as done (ruby-wirble: ship with bullseye?)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:40:38 + with message-id and subject line Bug#997893: Removed package(s) from unstable has caused the Debian Bug report #980348, regarding ruby-wirble: ship with bullseye? to be marked as done. This means that you claim that the problem has been dealt

Bug#984809: marked as done (php8.0: please make the build (mostly) reproducible)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:39:40 + with message-id and subject line Bug#997821: Removed package(s) from unstable has caused the Debian Bug report #984809, regarding php8.0: please make the build (mostly) reproducible to be marked as done. This means that you claim that the

Bug#980759: marked as done (php8.0: imageftbbox returns too small bounding box)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:39:40 + with message-id and subject line Bug#997821: Removed package(s) from unstable has caused the Debian Bug report #980759, regarding php8.0: imageftbbox returns too small bounding box to be marked as done. This means that you claim that the problem

Bug#982797: marked as done (phpY.Z: do not switch to apache2-mod on major upgrade)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:39:40 + with message-id and subject line Bug#997821: Removed package(s) from unstable has caused the Debian Bug report #982797, regarding phpY.Z: do not switch to apache2-mod on major upgrade to be marked as done. This means that you claim that the

Bug#997764: marked as done (pgaudit: FTBFS: pg_buildext: error: No current PostgreSQL versions are supported by this package)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:40:08 + with message-id and subject line Bug#997888: Removed package(s) from unstable has caused the Debian Bug report #997764, regarding pgaudit: FTBFS: pg_buildext: error: No current PostgreSQL versions are supported by this package to be marked as

Bug#997821: marked as done (RM: php8.0 -- ROM; Superseded by php8.1)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:39:30 + with message-id and subject line Bug#997821: Removed package(s) from unstable has caused the Debian Bug report #997821, regarding RM: php8.0 -- ROM; Superseded by php8.1 to be marked as done. This means that you claim that the problem has been

Bug#997888: marked as done (RM: pgaudit -- ROM; superseded by pgaudit-1.6)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:40:02 + with message-id and subject line Bug#997888: Removed package(s) from unstable has caused the Debian Bug report #997888, regarding RM: pgaudit -- ROM; superseded by pgaudit-1.6 to be marked as done. This means that you claim that the problem has

Bug#993235: marked as done (php8.0: Please depend on media-types instead of mime-support)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:39:40 + with message-id and subject line Bug#997821: Removed package(s) from unstable has caused the Debian Bug report #993235, regarding php8.0: Please depend on media-types instead of mime-support to be marked as done. This means that you claim that

Bug#986097: marked as done (libphp8.0-embed: unusual unversioned soname: libphp.so)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:39:40 + with message-id and subject line Bug#997821: Removed package(s) from unstable has caused the Debian Bug report #986097, regarding libphp8.0-embed: unusual unversioned soname: libphp.so to be marked as done. This means that you claim that the

Bug#997063: marked as done (php8.0: FTBFS on hurd-i386)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:39:40 + with message-id and subject line Bug#997821: Removed package(s) from unstable has caused the Debian Bug report #997063, regarding php8.0: FTBFS on hurd-i386 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#977206: marked as done (cylc: Wrong homepage)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:15:25 + with message-id and subject line Bug#1000691: Removed package(s) from unstable has caused the Debian Bug report #977206, regarding cylc: Wrong homepage to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#949407: marked as done (libisds: FTBFS with libxml2 not shipping xml2-config)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:17:00 + with message-id and subject line Bug#1000699: Removed package(s) from unstable has caused the Debian Bug report #949407, regarding libisds: FTBFS with libxml2 not shipping xml2-config to be marked as done. This means that you claim that the

Bug#982807: marked as done (datovka: version too old to be useful)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:16:17 + with message-id and subject line Bug#1000698: Removed package(s) from unstable has caused the Debian Bug report #982807, regarding datovka: version too old to be useful to be marked as done. This means that you claim that the problem has been

Bug#1000156: marked as done (roundcube: XSS vulnerability in handling attachment filename extension in MIME type mismatch warnings)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:17:25 + with message-id and subject line Bug#1000156: fixed in roundcube 1.3.17+dfsg.1-1~deb10u1 has caused the Debian Bug report #1000156, regarding roundcube: XSS vulnerability in handling attachment filename extension in MIME type mismatch warnings

Bug#1000691: marked as done (RM: cylc -- ROM; replaced by cylc-flow)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:15:19 + with message-id and subject line Bug#1000691: Removed package(s) from unstable has caused the Debian Bug report #1000691, regarding RM: cylc -- ROM; replaced by cylc-flow to be marked as done. This means that you claim that the problem has been

Bug#1000698: marked as done (RM: datovka -- ROM; maintained outside the repository)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:16:11 + with message-id and subject line Bug#1000698: Removed package(s) from unstable has caused the Debian Bug report #1000698, regarding RM: datovka -- ROM; maintained outside the repository to be marked as done. This means that you claim that the

Bug#1000699: marked as done (RM: libisds -- ROM; only user of the library removed; dead upstream)

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:16:56 + with message-id and subject line Bug#1000699: Removed package(s) from unstable has caused the Debian Bug report #1000699, regarding RM: libisds -- ROM; only user of the library removed; dead upstream to be marked as done. This means that you

Bug#997893: marked as done (RM: ruby-wirble -- ROM; No longer compatible with current versions of Ruby (incorporated))

2021-11-29 Thread Debian Bug Tracking System
Your message dated Mon, 29 Nov 2021 18:40:34 + with message-id and subject line Bug#997893: Removed package(s) from unstable has caused the Debian Bug report #997893, regarding RM: ruby-wirble -- ROM; No longer compatible with current versions of Ruby (incorporated) to be marked as done.

  1   2   >