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#764896: marked as done (sandboxgamemaker: sandbox_unix fails to start, "cannot find core textures")

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 #764896, regarding sandboxgamemaker: sandbox_unix fails to start, "cannot find core textures" to be marked as done. This means that

Bug#682272: marked as done (usbprog-gui: Menu Help->Users's Manual doesn't work)

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 #682272, regarding usbprog-gui: Menu Help->Users's Manual doesn't work to be marked as done. This means that you claim that the

Bug#685968: marked as done (manpages-es: Please *really* drop debconf l10n)

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 #685968, regarding manpages-es: Please *really* drop debconf l10n to be marked as done. This means that you claim that the problem has

Bug#810463: marked as done (usbprog: please switch to libusb 1.0)

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 #810463, regarding usbprog: please switch to libusb 1.0 to be marked as done. This means that you claim that the problem has been

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#757865: marked as done ([INTL:tr] Turkish debconf template translation for sandboxgamemaker)

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 #757865, regarding [INTL:tr] Turkish debconf template translation for sandboxgamemaker to be marked as done. This means that you claim

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

Bug#942263: marked as done (RM: rlplot -- RoQA; Dead upstream, depends on Qt4)

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

Bug#860177: marked as done (manpages-es: Very outdated manpages)

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 #860177, regarding manpages-es: Very outdated manpages to be marked as done. This means that you claim that the problem has been dealt

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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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#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

<    1   2