Bug#937095: marked as done (mwparserfromhell: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:49:31 + with message-id and subject line Bug#937095: fixed in mwparserfromhell 0.5.4-2 has caused the Debian Bug report #937095, regarding mwparserfromhell: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#942229: marked as done (llvm-toolchain-9: Fails to compile on i386)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 07:43:28 +0200 with message-id <9215076f-27a1-37c5-00ab-9fef31bd2...@debian.org> and subject line Re: llvm-toolchain-9: Fails to compile on i386 has caused the Debian Bug report #942229, regarding llvm-toolchain-9: Fails to compile on i386 to be marked as done.

Bug#585221: marked as done (darcsweb: Python string exceptions no more allowed in Python 2.6)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #585221, regarding darcsweb: Python string exceptions no more allowed in Python 2.6 to be marked as done. This means that you claim

Bug#763607: marked as done (darcsweb: Newer version of darcsweb is available.)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #763607, regarding darcsweb: Newer version of darcsweb is available. to be marked as done. This means that you claim that the problem

Bug#942271: marked as done (RM: darcsweb -- RoQA; depends on Python 2, unmaintained, dead upstream)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:14 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #942271, regarding RM: darcsweb -- RoQA; depends on Python 2, unmaintained, dead upstream to be marked as done. This means that you

Bug#668735: marked as done (darcsweb: unowned files after purge (policy 6.8, 10.8): /etc/apache2/conf.d/darcsweb.conf)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #668735, regarding darcsweb: unowned files after purge (policy 6.8, 10.8): /etc/apache2/conf.d/darcsweb.conf to be marked as done.

Bug#440832: marked as done (darcsweb: Lighttpd config files)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #440832, regarding darcsweb: Lighttpd config files to be marked as done. This means that you claim that the problem has been dealt

Bug#578236: marked as done (darcsweb: stop shipping files in /etc/apache/)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #578236, regarding darcsweb: stop shipping files in /etc/apache/ to be marked as done. This means that you claim that the problem has

Bug#767254: marked as done (darcsweb: [INTL:nl] Dutch translation of debconf messages)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #767254, regarding darcsweb: [INTL:nl] Dutch translation of debconf messages to be marked as done. This means that you claim that the

Bug#444901: marked as done (darcsweb: please allow _darcs/prefs/motd as repository description)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #444901, regarding darcsweb: please allow _darcs/prefs/motd as repository description to be marked as done. This means that you claim

Bug#438945: marked as done (please add more examples for examples/mkconfig.py usage)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:03:25 + with message-id and subject line Bug#942271: Removed package(s) from unstable has caused the Debian Bug report #438945, regarding please add more examples for examples/mkconfig.py usage to be marked as done. This means that you claim that the

Bug#827063: marked as done (spek: segfault on first run)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:02:23 + with message-id and subject line Bug#941338: Removed package(s) from unstable has caused the Debian Bug report #827063, regarding spek: segfault on first run to be marked as done. This means that you claim that the problem has been dealt with.

Bug#933438: marked as done (spek: Please rebuild against wxWidgets GTK 3 package)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:02:23 + with message-id and subject line Bug#941338: Removed package(s) from unstable has caused the Debian Bug report #933438, regarding spek: Please rebuild against wxWidgets GTK 3 package to be marked as done. This means that you claim that the

Bug#935745: marked as done (RM: python-pushy -- RoQA; python2 only; dead upstream; low popcon; last upload in 2015)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:01:52 + with message-id and subject line Bug#935745: Removed package(s) from unstable has caused the Debian Bug report #935745, regarding RM: python-pushy -- RoQA; python2 only; dead upstream; low popcon; last upload in 2015 to be marked as done. This

Bug#941338: marked as done (RM: spek -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 05:02:17 + with message-id and subject line Bug#941338: Removed package(s) from unstable has caused the Debian Bug report #941338, regarding RM: spek -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy to be marked as done. This means that you claim

Bug#942266: marked as done (pulseaudio: Please exclude user root when enable pulseaudio service.)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 22:36:24 -0300 with message-id and subject line Re: Bug#942266: pulseaudio: Please exclude user root when enable pulseaudio service. has caused the Debian Bug report #942266, regarding pulseaudio: Please exclude user root when enable pulseaudio service. to be

Bug#936747: marked as done (isbnlib: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Mon, 14 Oct 2019 00:49:58 + with message-id and subject line Bug#936747: fixed in isbnlib 3.9.3-1.1 has caused the Debian Bug report #936747, regarding isbnlib: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#937741: marked as done (python-exif: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 23:57:04 + with message-id and subject line Bug#937741: fixed in python-exif 2.2.0-3 has caused the Debian Bug report #937741, regarding python-exif: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#937828: marked as done (python-ijson: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 22:56:14 + with message-id and subject line Bug#937828: fixed in python-ijson 2.3-2.1 has caused the Debian Bug report #937828, regarding python-ijson: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#937683: marked as done (python-cymruwhois: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 22:27:38 + with message-id and subject line Bug#937683: fixed in python-cymruwhois 1.6-3.2 has caused the Debian Bug report #937683, regarding python-cymruwhois: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#942278: marked as done (dpkg-www: Missing dependancy on perl module CGI.pm. At least when using lighttpd.)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 22:21:38 + with message-id and subject line Bug#942278: fixed in dpkg-www 2.60 has caused the Debian Bug report #942278, regarding dpkg-www: Missing dependancy on perl module CGI.pm. At least when using lighttpd. to be marked as done. This means that you

Bug#937524: marked as done (pyrlp: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 21:26:39 + with message-id and subject line Bug#937524: fixed in pyrlp 0.5.1-1.1 has caused the Debian Bug report #937524, regarding pyrlp: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#927513: marked as done (Updating the zipl-installer Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 21:11:46 + with message-id and subject line Bug#927513: fixed in zipl-installer 0.0.40 has caused the Debian Bug report #927513, regarding Updating the zipl-installer Uploaders list to be marked as done. This means that you claim that the problem has been

Bug#937112: marked as done (natsort: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:52:19 + with message-id and subject line Bug#937112: fixed in natsort 6.0.0-1.1 has caused the Debian Bug report #937112, regarding natsort: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#927514: marked as done (Updating the partman-base Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:53:58 + with message-id and subject line Bug#927514: fixed in partman-base 209 has caused the Debian Bug report #927514, regarding Updating the partman-base Uploaders list to be marked as done. This means that you claim that the problem has been dealt

Bug#927506: marked as done (Updating the s390-netdevice Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:54:34 + with message-id and subject line Bug#927506: fixed in s390-netdevice 0.0.69 has caused the Debian Bug report #927506, regarding Updating the s390-netdevice Uploaders list to be marked as done. This means that you claim that the problem has been

Bug#927536: marked as done (Updating the rescue Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:54:04 + with message-id and subject line Bug#927536: fixed in rescue 1.77 has caused the Debian Bug report #927536, regarding Updating the rescue Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#927508: marked as done (Updating the nobootloader Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:52:25 + with message-id and subject line Bug#927508: fixed in nobootloader 1.57 has caused the Debian Bug report #927508, regarding Updating the nobootloader Uploaders list to be marked as done. This means that you claim that the problem has been dealt

Bug#927524: marked as done (Updating the mdcfg Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:52:12 + with message-id and subject line Bug#927524: fixed in mdcfg 1.64 has caused the Debian Bug report #927524, regarding Updating the mdcfg Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#936563: marked as done (frozen-flask: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:44:52 + with message-id and subject line Bug#936563: fixed in frozen-flask 0.11-3.1 has caused the Debian Bug report #936563, regarding frozen-flask: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936331: marked as done (construct.legacy: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 20:40:15 + with message-id and subject line Bug#936331: fixed in construct.legacy 2.5.3-2.1 has caused the Debian Bug report #936331, regarding construct.legacy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#927502: marked as done (Updating the lvmcfg Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:50:14 + with message-id and subject line Bug#927502: fixed in lvmcfg 1.51 has caused the Debian Bug report #927502, regarding Updating the lvmcfg Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#934519: marked as done (fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman))

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:47:32 + with message-id and subject line Bug#934519: fixed in fence-agents 4.0.25-1+deb9u2 has caused the Debian Bug report #934519, regarding fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman) to be marked as done. This

Bug#940547: marked as done (python-cryptography: Testsuite fails with OpenSSL 1.1.1d)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:47:34 + with message-id and subject line Bug#940547: fixed in python-cryptography 1.7.1-3+deb9u2 has caused the Debian Bug report #940547, regarding python-cryptography: Testsuite fails with OpenSSL 1.1.1d to be marked as done. This means that you claim

Bug#936589: marked as done (gconf: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:34:47 + with message-id and subject line Bug#936589: fixed in gconf 3.2.6-6 has caused the Debian Bug report #936589, regarding gconf: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#941487: marked as done (gconf: autopkgtest fails with libglib2.0-0 (>= 2.62))

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:34:47 + with message-id and subject line Bug#941487: fixed in gconf 3.2.6-6 has caused the Debian Bug report #941487, regarding gconf: autopkgtest fails with libglib2.0-0 (>= 2.62) to be marked as done. This means that you claim that the problem has

Bug#935801: marked as done (Deprecated types in exported API as of GLib 2.62)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:34:47 + with message-id and subject line Bug#935801: fixed in gconf 3.2.6-6 has caused the Debian Bug report #935801, regarding Deprecated types in exported API as of GLib 2.62 to be marked as done. This means that you claim that the problem has been

Bug#941411: marked as done (shelldap: sometimes falls back to simple auth when it should do sasl)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:36:09 + with message-id and subject line Bug#941411: fixed in shelldap 1.5.1-1 has caused the Debian Bug report #941411, regarding shelldap: sometimes falls back to simple auth when it should do sasl to be marked as done. This means that you claim that

Bug#927541: marked as done (Updating the lilo-installer Uploaders list)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:35:52 + with message-id and subject line Bug#927541: fixed in lilo-installer 1.61 has caused the Debian Bug report #927541, regarding Updating the lilo-installer Uploaders list to be marked as done. This means that you claim that the problem has been

Bug#921278: marked as done (bibtex2html: Lacks several math-related translations)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:34:36 + with message-id and subject line Bug#921278: fixed in bibtex2html 1.99-3 has caused the Debian Bug report #921278, regarding bibtex2html: Lacks several math-related translations to be marked as done. This means that you claim that the problem

Bug#921593: marked as done (bibtex2html should transate math characters with overhead accents)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:34:36 + with message-id and subject line Bug#921593: fixed in bibtex2html 1.99-3 has caused the Debian Bug report #921593, regarding bibtex2html should transate math characters with overhead accents to be marked as done. This means that you claim that

Bug#919891: marked as done (navit: Crash when starting for the first time due to XML)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 21:34:04 +0200 with message-id and subject line Re: navit: Crash when starting for the first time due to XML has caused the Debian Bug report #919891, regarding navit: Crash when starting for the first time due to XML to be marked as done. This means that you

Bug#935210: marked as done (python-nbxmpp: Please port to Python 3 and/or drop Python 2 package)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:20:10 + with message-id and subject line Bug#935210: fixed in python-nbxmpp 0.6.10-1.1 has caused the Debian Bug report #935210, regarding python-nbxmpp: Please port to Python 3 and/or drop Python 2 package to be marked as done. This means that you

Bug#935492: marked as done (rpcbind: Broadcast requests broken)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:23 + with message-id and subject line Bug#939877: fixed in rpcbind 1.2.5-0.3+deb10u1 has caused the Debian Bug report #939877, regarding rpcbind: Broadcast requests broken to be marked as done. This means that you claim that the problem has been

Bug#941955: marked as done (memory leaks in open-vm-tools)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:11 + with message-id and subject line Bug#941955: fixed in open-vm-tools 2:10.3.10-1+deb10u2 has caused the Debian Bug report #941955, regarding memory leaks in open-vm-tools to be marked as done. This means that you claim that the problem has been

Bug#941987: marked as done (libssl1.1: Ciphers AES-*-CBC-HMAC-* are missing in libssl 1.1.1d, but available in 1.1.1c)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:11 + with message-id and subject line Bug#941987: fixed in openssl 1.1.1d-0+deb10u2 has caused the Debian Bug report #941987, regarding libssl1.1: Ciphers AES-*-CBC-HMAC-* are missing in libssl 1.1.1d, but available in 1.1.1c to be marked as done.

Bug#935724: marked as done (aegisub: Aegisub crashes immediately after opening the context menu)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:08 + with message-id and subject line Bug#935724: fixed in aegisub 3.2.2+dfsg-4+deb10u1 has caused the Debian Bug report #935724, regarding aegisub: Aegisub crashes immediately after opening the context menu to be marked as done. This means that you

Bug#910901: marked as done (plasma-applet-redshift-control: Mouse wheel only reduces color temperature, in either direction)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:21 + with message-id and subject line Bug#910901: fixed in plasma-applet-redshift-control 1.0.18-2+deb10u1 has caused the Debian Bug report #910901, regarding plasma-applet-redshift-control: Mouse wheel only reduces color temperature, in either

Bug#941189: marked as done (node-set-value: CVE-2019-10747)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:10 + with message-id and subject line Bug#941189: fixed in node-set-value 0.4.0-1+deb10u1 has caused the Debian Bug report #941189, regarding node-set-value: CVE-2019-10747 to be marked as done. This means that you claim that the problem has been

Bug#931855: marked as done (rpc.rquotad takes 100% CPU)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:22 + with message-id and subject line Bug#931855: fixed in quota 4.04-2+deb10u1 has caused the Debian Bug report #931855, regarding rpc.rquotad takes 100% CPU to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#933163: marked as done (cyrus-imapd: Data loss possible when upgrading to buster)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:08 + with message-id and subject line Bug#933163: fixed in cyrus-imapd 3.0.8-6+deb10u1 has caused the Debian Bug report #933163, regarding cyrus-imapd: Data loss possible when upgrading to buster to be marked as done. This means that you claim that

Bug#934519: marked as done (fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman))

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:09 + with message-id and subject line Bug#934519: fixed in fence-agents 4.3.3-2+deb10u1 has caused the Debian Bug report #934519, regarding fence-agents: FTBFS in stretch/buster/sid (ImportError: No module named pywsman) to be marked as done. This

Bug#939877: marked as done (rpcbind: Does not receive any broadcast queries resulting in complete breakage of NIS)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:23 + with message-id and subject line Bug#939877: fixed in rpcbind 1.2.5-0.3+deb10u1 has caused the Debian Bug report #939877, regarding rpcbind: Does not receive any broadcast queries resulting in complete breakage of NIS to be marked as done. This

Bug#941464: marked as done (picard: Crash when using Spanish locale)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:21 + with message-id and subject line Bug#941464: fixed in picard 2.1.2-1+deb10u1 has caused the Debian Bug report #941464, regarding picard: Crash when using Spanish locale to be marked as done. This means that you claim that the problem has been

Bug#939119: marked as done (gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:09 + with message-id and subject line Bug#939119: fixed in gnustep-base 1.26.0-4+deb10u1 has caused the Debian Bug report #939119, regarding gnustep-base-runtime: Upgrading to Debian 10 causes gdomap network service to become enabled to be marked as

Bug#940547: marked as done (python-cryptography: Testsuite fails with OpenSSL 1.1.1d)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:17:22 + with message-id and subject line Bug#940547: fixed in python-cryptography 2.6.1-3+deb10u1 has caused the Debian Bug report #940547, regarding python-cryptography: Testsuite fails with OpenSSL 1.1.1d to be marked as done. This means that you

Bug#940069: marked as done (gr-limesdr: FTBFS in unstable)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:04:22 + with message-id and subject line Bug#940069: fixed in gr-limesdr 2.0.0-27-gca01a64-2 has caused the Debian Bug report #940069, regarding gr-limesdr: FTBFS in unstable to be marked as done. This means that you claim that the problem has been

Bug#938833: marked as done (wsgicors: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:04:41 + with message-id and subject line Bug#938833: fixed in wsgicors 0.4.1-1.1 has caused the Debian Bug report #938833, regarding wsgicors: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#912196: marked as done (abgate FTCBFS: multiple reasons)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:04:03 + with message-id and subject line Bug#912196: fixed in abgate 1.1.9-2 has caused the Debian Bug report #912196, regarding abgate FTCBFS: multiple reasons to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#936662: marked as done (gr-limesdr: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:04:22 + with message-id and subject line Bug#936662: fixed in gr-limesdr 2.0.0-27-gca01a64-2 has caused the Debian Bug report #936662, regarding gr-limesdr: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#915597: marked as done (gr-limesdr: Homepage: points to dead page)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:04:22 + with message-id and subject line Bug#915597: fixed in gr-limesdr 2.0.0-27-gca01a64-2 has caused the Debian Bug report #915597, regarding gr-limesdr: Homepage: points to dead page to be marked as done. This means that you claim that the problem

Bug#935737: marked as done (transition: perl)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 21:05:19 +0200 with message-id <1553faab-0f1d-8f33-8c70-f52df130c...@debian.org> and subject line Re: Bug#935737: transition: perl has caused the Debian Bug report #935737, regarding transition: perl to be marked as done. This means that you claim that the

Bug#938474: marked as done (sgp4: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:04:35 + with message-id and subject line Bug#938474: fixed in sgp4 1.4-1.1 has caused the Debian Bug report #938474, regarding sgp4: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#941083: marked as done (ITP: stream-lib -- library for summarizing data in streams)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 19:00:10 + with message-id and subject line Bug#941083: fixed in stream-lib 2.9.8-1 has caused the Debian Bug report #941083, regarding ITP: stream-lib -- library for summarizing data in streams to be marked as done. This means that you claim that the

Bug#941963: marked as done (ITP: opentest4j -- Open Test Alliance for the JVM)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:18 + with message-id and subject line Bug#941963: fixed in opentest4j 1.2.0-1 has caused the Debian Bug report #941963, regarding ITP: opentest4j -- Open Test Alliance for the JVM to be marked as done. This means that you claim that the problem has

Bug#941965: marked as done (ITP: univocity-parsers -- Parsers for CSV, TSV and fixed width files)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:19 + with message-id and subject line Bug#941965: fixed in univocity-parsers 2.8.3-1 has caused the Debian Bug report #941965, regarding ITP: univocity-parsers -- Parsers for CSV, TSV and fixed width files to be marked as done. This means that you

Bug#933350: marked as done (ITP: ceph-iscsi -- common logic and CLI tools for creating and managing LIO gateways for Ceph)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:13 + with message-id and subject line Bug#933350: fixed in ceph-iscsi 3.2-1 has caused the Debian Bug report #933350, regarding ITP: ceph-iscsi -- common logic and CLI tools for creating and managing LIO gateways for Ceph to be marked as done. This

Bug#930979: marked as done (ITP: membernator -- Tool to scan membership cards to establish if they are valid)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:17 + with message-id and subject line Bug#930979: fixed in membernator 1.0.1-1 has caused the Debian Bug report #930979, regarding ITP: membernator -- Tool to scan membership cards to establish if they are valid to be marked as done. This means that

Bug#941976: marked as done (ITP: apiguardian -- Level of stability annotation for frameworks or applications)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:12 + with message-id and subject line Bug#941976: fixed in apiguardian 1.1.0-1 has caused the Debian Bug report #941976, regarding ITP: apiguardian -- Level of stability annotation for frameworks or applications to be marked as done. This means that

Bug#935785: marked as done (ITP: eckit -- C++ toolkit for ECMWF tools and Applications)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:14 + with message-id and subject line Bug#935785: fixed in eckit 1.1.1-1 has caused the Debian Bug report #935785, regarding ITP: eckit -- C++ toolkit for ECMWF tools and Applications to be marked as done. This means that you claim that the problem

Bug#940094: marked as done (ITP: mmtf-java -- Java API for macromolecular transmission format encoder/decoder)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:18 + with message-id and subject line Bug#940094: fixed in mmtf-java 1.0.9-1 has caused the Debian Bug report #940094, regarding ITP: mmtf-java -- Java API for macromolecular transmission format encoder/decoder to be marked as done. This means that

Bug#934964: marked as done (ITP: afl++ -- security related binary fuzzer (fork of american Fuzzy Lop))

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:12 + with message-id and subject line Bug#934964: fixed in aflplusplus 2.53c-1 has caused the Debian Bug report #934964, regarding ITP: afl++ -- security related binary fuzzer (fork of american Fuzzy Lop) to be marked as done. This means that you

Bug#934142: marked as done (ITP: python-in-toto -- software supply chain security framework)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:16 + with message-id and subject line Bug#934142: fixed in in-toto 0.4.0-1 has caused the Debian Bug report #934142, regarding ITP: python-in-toto -- software supply chain security framework to be marked as done. This means that you claim that the

Bug#940049: marked as done (ITP: pd.build-cmake-module -- Pure Data CMake Module)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:19 + with message-id and subject line Bug#940049: fixed in pd.build-cmake-module 0.1.0~ds1-1 has caused the Debian Bug report #940049, regarding ITP: pd.build-cmake-module -- Pure Data CMake Module to be marked as done. This means that you claim that

Bug#934700: marked as done (ITP: lz4-java -- LZ4 compression for Java)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:17 + with message-id and subject line Bug#934700: fixed in lz4-java 1.5.1-1 has caused the Debian Bug report #934700, regarding ITP: lz4-java -- LZ4 compression for Java to be marked as done. This means that you claim that the problem has been dealt

Bug#941938: marked as done (ITP: guava-mini -- utilities from Guava)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:15 + with message-id and subject line Bug#941938: fixed in guava-mini 0.1.2-1~exp1 has caused the Debian Bug report #941938, regarding ITP: guava-mini -- utilities from Guava to be marked as done. This means that you claim that the problem has been

Bug#941944: marked as done (ITP: zt-exec -- ZT Process Executor)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 18:00:20 + with message-id and subject line Bug#941944: fixed in zt-exec 1.11-1~exp1 has caused the Debian Bug report #941944, regarding ITP: zt-exec -- ZT Process Executor to be marked as done. This means that you claim that the problem has been dealt

Bug#941439: marked as done (Ships obsolete mimelnk directory)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 17:10:02 + with message-id and subject line Bug#941439: fixed in libreoffice 1:6.3.3~rc1-1 has caused the Debian Bug report #941439, regarding Ships obsolete mimelnk directory to be marked as done. This means that you claim that the problem has been dealt

Bug#941655: marked as done (libreoffice-impress: Exported html pages have black backgrounds)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 17:10:02 + with message-id and subject line Bug#941655: fixed in libreoffice 1:6.3.3~rc1-1 has caused the Debian Bug report #941655, regarding libreoffice-impress: Exported html pages have black backgrounds to be marked as done. This means that you claim

Bug#936104: marked as done (a2jmidid: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 17:04:21 + with message-id and subject line Bug#936104: fixed in a2jmidid 9-2 has caused the Debian Bug report #936104, regarding a2jmidid: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#941167: marked as done (a2jmidid: new upstream and new upstream version)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 17:04:21 + with message-id and subject line Bug#941167: fixed in a2jmidid 9-2 has caused the Debian Bug report #941167, regarding a2jmidid: new upstream and new upstream version to be marked as done. This means that you claim that the problem has been

Bug#938504: marked as done (smbmap: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 16:35:44 + with message-id and subject line Bug#938504: fixed in smbmap 1.1.0+git20191013-1 has caused the Debian Bug report #938504, regarding smbmap: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#938245: marked as done (python-urlobject: Python2 removal in sid/bullseye)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:49:45 + with message-id and subject line Bug#938245: fixed in python-urlobject 2.4.3-1 has caused the Debian Bug report #938245, regarding python-urlobject: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#595986: marked as done (loggerhead: Instructions to get branch give bad location.)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:32:52 + with message-id <20191013153252.ga...@jelmer.uk> and subject line Done has caused the Debian Bug report #595986, regarding loggerhead: Instructions to get branch give bad location. to be marked as done. This means that you claim that the problem

Bug#942039: marked as done (loggerhead: not co-installable with loggerhead-breezy)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:32:28 + with message-id <20191013153228.ga...@jelmer.uk> and subject line Resolved has caused the Debian Bug report #942039, regarding loggerhead: not co-installable with loggerhead-breezy to be marked as done. This means that you claim that the problem

Bug#942186: marked as done (RM: sandboxgamemaker -- RoQA; inactive upstream; NIT; broken; orphaned; RC-buggy; low popcon)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:16:34 + with message-id and subject line Bug#942186: Removed package(s) from unstable has caused the Debian Bug report #942186, regarding RM: sandboxgamemaker -- RoQA; inactive upstream; NIT; broken; orphaned; RC-buggy; low popcon to be marked as done.

Bug#879121: marked as done (unixodbc-gui-qt FTCBFS: uses AC_CHECK_FILE for /usr/include)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:18:08 + with message-id and subject line Bug#942264: Removed package(s) from unstable has caused the Debian Bug report #879121, regarding unixodbc-gui-qt FTCBFS: uses AC_CHECK_FILE for /usr/include to be marked as done. This means that you claim that

Bug#920554: marked as done (unixodbc-bin: Binaries listed in description don't match binaries provided)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:18:08 + with message-id and subject line Bug#942264: Removed package(s) from unstable has caused the Debian Bug report #920554, regarding unixodbc-bin: Binaries listed in description don't match binaries provided to be marked as done. This means that

Bug#875172: marked as done ([rlplot] Future Qt4 removal from Buster)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:17:21 + with message-id and subject line Bug#942263: Removed package(s) from unstable has caused the Debian Bug report #875172, regarding [rlplot] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#941180: marked as done (RM: usbprog -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:15:31 + with message-id and subject line Bug#941180: Removed package(s) from unstable has caused the Debian Bug report #941180, regarding RM: usbprog -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy to be marked as done. This means that you

Bug#941179: marked as done (O: sandboxgamemaker -- 3D game maker and 3D game design program)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:16:42 + with message-id and subject line Bug#942186: Removed package(s) from unstable has caused the Debian Bug report #941179, regarding O: sandboxgamemaker -- 3D game maker and 3D game design program to be marked as done. This means that you claim

Bug#933408: marked as done (usbprog: Please rebuild against wxWidgets GTK 3 package)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:15:38 + with message-id and subject line Bug#941180: Removed package(s) from unstable has caused the Debian Bug report #933408, regarding usbprog: Please rebuild against wxWidgets GTK 3 package to be marked as done. This means that you claim that the

Bug#933445: marked as done (sandboxgamemaker: Please rebuild against wxWidgets GTK 3 package)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:16:42 + with message-id and subject line Bug#942186: Removed package(s) from unstable has caused the Debian Bug report #933445, regarding sandboxgamemaker: Please rebuild against wxWidgets GTK 3 package to be marked as done. This means that you claim

Bug#941153: marked as done (RM: manpages-es -- RoQA; totally outdated manpages, unmaintained)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:15:01 + with message-id and subject line Bug#941153: Removed package(s) from unstable has caused the Debian Bug report #941153, regarding RM: manpages-es -- RoQA; totally outdated manpages, unmaintained to be marked as done. This means that you claim

Bug#934248: marked as done (Should this package be removed?)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:15:09 + with message-id and subject line Bug#941153: Removed package(s) from unstable has caused the Debian Bug report #934248, regarding Should this package be removed? to be marked as done. This means that you claim that the problem has been dealt

Bug#933411: marked as done (fwknop-gui: Please rebuild against wxWidgets GTK 3 package)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:16:13 + with message-id and subject line Bug#941240: Removed package(s) from unstable has caused the Debian Bug report #933411, regarding fwknop-gui: Please rebuild against wxWidgets GTK 3 package to be marked as done. This means that you claim that the

Bug#941240: marked as done (RM: fwknop-gui -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:16:08 + with message-id and subject line Bug#941240: Removed package(s) from unstable has caused the Debian Bug report #941240, regarding RM: fwknop-gui -- RoQA; dead upstream; unmaintained; low popcon; RC-buggy to be marked as done. This means that

Bug#942264: marked as done (RM: unixodbc-gui-qt -- RoQA; Depends on Qt4)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:18:02 + with message-id and subject line Bug#942264: Removed package(s) from unstable has caused the Debian Bug report #942264, regarding RM: unixodbc-gui-qt -- RoQA; Depends on Qt4 to be marked as done. This means that you claim that the problem has

Bug#875219: marked as done ([unixodbc-gui-qt] Future Qt4 removal from Buster)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:18:08 + with message-id and subject line Bug#942264: Removed package(s) from unstable has caused the Debian Bug report #875219, regarding [unixodbc-gui-qt] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem

Bug#942247: marked as done (RM: geary [s390x] -- ROM; ANAIS)

2019-10-13 Thread Debian Bug Tracking System
Your message dated Sun, 13 Oct 2019 15:16:54 + with message-id and subject line Bug#942247: Removed package(s) from unstable has caused the Debian Bug report #942247, regarding RM: geary [s390x] -- ROM; ANAIS to be marked as done. This means that you claim that the problem has been dealt

  1   2   >