Bug#878385: marked as done (please drop transitional packages deluge-torrent and deluge-webui)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 02:39:46 + with message-id and subject line Bug#878385: fixed in deluge 2.0.3-2 has caused the Debian Bug report #878385, regarding please drop transitional packages deluge-torrent and deluge-webui to be marked as done. This means that you claim that the pr

Bug#950573: marked as done (deluged: deluge-2.0.3 requires libtorrent >= 1.1.2.0)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 02:39:46 + with message-id and subject line Bug#950573: fixed in deluge 2.0.3-2 has caused the Debian Bug report #950573, regarding deluged: deluge-2.0.3 requires libtorrent >= 1.1.2.0 to be marked as done. This means that you claim that the problem has bee

Bug#952759: marked as done (FTBFS with libsass 3.6.3, please upgrade to 0.19.4)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 01:34:32 + with message-id and subject line Bug#952759: fixed in libsass-python 0.19.4-0.1 has caused the Debian Bug report #952759, regarding FTBFS with libsass 3.6.3, please upgrade to 0.19.4 to be marked as done. This means that you claim that the proble

Bug#951842: marked as done (gringo needs a new upstream, and fixes for python3.8)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 01:22:33 + with message-id and subject line Bug#951842: fixed in gringo 5.3.0-11 has caused the Debian Bug report #951842, regarding gringo needs a new upstream, and fixes for python3.8 to be marked as done. This means that you claim that the problem has be

Bug#951707: marked as done (gringo ftbfs with Python 3.8)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 01:22:33 + with message-id and subject line Bug#951707: fixed in gringo 5.3.0-11 has caused the Debian Bug report #951707, regarding gringo ftbfs with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this i

Bug#944178: marked as done (gringo: non-standard gcc/g++ used for build (gcc-8))

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 01:22:33 + with message-id and subject line Bug#944178: fixed in gringo 5.3.0-11 has caused the Debian Bug report #944178, regarding gringo: non-standard gcc/g++ used for build (gcc-8) to be marked as done. This means that you claim that the problem has bee

Bug#952475: marked as done (ats2-lang: Please make another source-only upload to allow testing migration)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 01:04:15 + with message-id and subject line Bug#952475: fixed in ats2-lang 0.4.0-1 has caused the Debian Bug report #952475, regarding ats2-lang: Please make another source-only upload to allow testing migration to be marked as done. This means that you cl

Bug#951293: marked as done (procps: obsolete conffile left behind)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 01:04:58 + with message-id and subject line Bug#951293: fixed in procps 2:3.3.16-4 has caused the Debian Bug report #951293, regarding procps: obsolete conffile left behind to be marked as done. This means that you claim that the problem has been dealt with

Bug#953459: marked as done (procps: Non-source-only upload in the latest revision)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 12:00:01 +1100 with message-id and subject line Re: Bug#953459: procps: Non-source-only upload in the latest revision has caused the Debian Bug report #953459, regarding procps: Non-source-only upload in the latest revision to be marked as done. This means th

Bug#953461: marked as done (Updating the weupnp Uploaders list)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:01:42 + with message-id and subject line Bug#953492: Removed package(s) from unstable has caused the Debian Bug report #953461, regarding Updating the weupnp Uploaders list to be marked as done. This means that you claim that the problem has been dealt w

Bug#953492: marked as done (RM: weupnp -- ROM; Not used, low popcon)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:01:39 + with message-id and subject line Bug#953492: Removed package(s) from unstable has caused the Debian Bug report #953492, regarding RM: weupnp -- ROM; Not used, low popcon to be marked as done. This means that you claim that the problem has been de

Bug#953490: marked as done (RM: jmxetric -- ROM; Not used, low popcon)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:01:01 + with message-id and subject line Bug#953490: Removed package(s) from unstable has caused the Debian Bug report #953490, regarding RM: jmxetric -- ROM; Not used, low popcon to be marked as done. This means that you claim that the problem has been

Bug#953445: marked as done (Updating the jmxetric Uploaders list)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:01:05 + with message-id and subject line Bug#953490: Removed package(s) from unstable has caused the Debian Bug report #953445, regarding Updating the jmxetric Uploaders list to be marked as done. This means that you claim that the problem has been dealt

Bug#946667: marked as done (mercurial-server: can't clone to or push repository to server (object has no attribute 'changectx'))

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:43 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #946667, regarding mercurial-server: can't clone to or push repository to server (object has no attribute 'changectx') to be marked as

Bug#937013: marked as done (mercurial-server: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:43 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #937013, regarding mercurial-server: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#953463: marked as done (Updating the jsmpp Uploaders list)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:59:46 + with message-id and subject line Bug#953480: Removed package(s) from unstable has caused the Debian Bug report #953463, regarding Updating the jsmpp Uploaders list to be marked as done. This means that you claim that the problem has been dealt wi

Bug#705673: marked as done (mercurial-server: impossible to clone anything after creation of a repo with a space in its path name)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:43 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #705673, regarding mercurial-server: impossible to clone anything after creation of a repo with a space in its path name to be marked a

Bug#772309: marked as done (mercurial-server: bashism in /bin/sh script)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:43 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #772309, regarding mercurial-server: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has bee

Bug#757506: marked as done ([INTL:tr] Turkish debconf template translation for mercurial-server)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:43 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #757506, regarding [INTL:tr] Turkish debconf template translation for mercurial-server to be marked as done. This means that you claim

Bug#938736: marked as done (txwinrm: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:16 + with message-id and subject line Bug#953482: Removed package(s) from unstable has caused the Debian Bug report #938736, regarding txwinrm: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#953482: marked as done (RM: txwinrm -- RoQA; Depends on Python 2)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:09 + with message-id and subject line Bug#953482: Removed package(s) from unstable has caused the Debian Bug report #953482, regarding RM: txwinrm -- RoQA; Depends on Python 2 to be marked as done. This means that you claim that the problem has been d

Bug#953480: marked as done (RM: jsmpp -- ROM; Not used, low popcon)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:59:43 + with message-id and subject line Bug#953480: Removed package(s) from unstable has caused the Debian Bug report #953480, regarding RM: jsmpp -- ROM; Not used, low popcon to be marked as done. This means that you claim that the problem has been dea

Bug#953436: marked as done (RM: ldaptor -- RoQA; Depends on Python 2, unmaintained)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:25 + with message-id and subject line Bug#953436: Removed package(s) from unstable has caused the Debian Bug report #953436, regarding RM: ldaptor -- RoQA; Depends on Python 2, unmaintained to be marked as done. This means that you claim that the prob

Bug#953434: marked as done (RM: flashbake -- RoQA; Depends on Python 2, unmaintained)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:03 + with message-id and subject line Bug#953434: Removed package(s) from unstable has caused the Debian Bug report #953434, regarding RM: flashbake -- RoQA; Depends on Python 2, unmaintained to be marked as done. This means that you claim that the pr

Bug#699183: marked as done (mercurial-server: user name 'hg' is too generic)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:43 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #699183, regarding mercurial-server: user name 'hg' is too generic to be marked as done. This means that you claim that the problem has

Bug#953475: marked as done (RM: python-netsyslog -- ROM; python2-only; no rdeps in testing; unmaintained)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:59:06 + with message-id and subject line Bug#953475: Removed package(s) from unstable has caused the Debian Bug report #953475, regarding RM: python-netsyslog -- ROM; python2-only; no rdeps in testing; unmaintained to be marked as done. This means that

Bug#953454: marked as done (Updating the python-netsyslog Uploaders list)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:59:10 + with message-id and subject line Bug#953475: Removed package(s) from unstable has caused the Debian Bug report #953454, regarding Updating the python-netsyslog Uploaders list to be marked as done. This means that you claim that the problem has be

Bug#699182: marked as done (/usr/share/mercurial-server/init/hginit should be called even if not adding the hg user)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:43 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #699182, regarding /usr/share/mercurial-server/init/hginit should be called even if not adding the hg user to be marked as done. This

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

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:59:10 + with message-id and subject line Bug#953475: Removed package(s) from unstable has caused the Debian Bug report #937943, regarding python-netsyslog: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem h

Bug#953483: marked as done (RM: mercurial-server -- RoQA; Depends on Python 2, dead upstream, unmaintained)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Tue, 10 Mar 2020 00:00:36 + with message-id and subject line Bug#953483: Removed package(s) from unstable has caused the Debian Bug report #953483, regarding RM: mercurial-server -- RoQA; Depends on Python 2, dead upstream, unmaintained to be marked as done. This means tha

Bug#805349: marked as done (/usr/bin/ldaptor-search: ldaptor-search - AttributeError: 'module' object has no attribute 'UsageError')

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:30 + with message-id and subject line Bug#953436: Removed package(s) from unstable has caused the Debian Bug report #805349, regarding /usr/bin/ldaptor-search: ldaptor-search - AttributeError: 'module' object has no attribute 'UsageError' to be marked

Bug#953433: marked as done (RM: moap -- RoQA; Dead upstream, depends on Python 2, unmaintained)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:57:41 + with message-id and subject line Bug#953433: Removed package(s) from unstable has caused the Debian Bug report #953433, regarding RM: moap -- RoQA; Dead upstream, depends on Python 2, unmaintained to be marked as done. This means that you claim t

Bug#795247: marked as done (ldaptor-utils: ldaptor-find-server throws "ImportError")

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:30 + with message-id and subject line Bug#953436: Removed package(s) from unstable has caused the Debian Bug report #795247, regarding ldaptor-utils: ldaptor-find-server throws "ImportError" to be marked as done. This means that you claim that the pro

Bug#852391: marked as done (Updating the moap Uploaders list)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:57:46 + with message-id and subject line Bug#953433: Removed package(s) from unstable has caused the Debian Bug report #852391, regarding Updating the moap Uploaders list to be marked as done. This means that you claim that the problem has been dealt wit

Bug#936830: marked as done (ldaptor: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:30 + with message-id and subject line Bug#953436: Removed package(s) from unstable has caused the Debian Bug report #936830, regarding ldaptor: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#919009: marked as done (flashbake: Uses defunct hostname www.noreply.org)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:07 + with message-id and subject line Bug#953434: Removed package(s) from unstable has caused the Debian Bug report #919009, regarding flashbake: Uses defunct hostname www.noreply.org to be marked as done. This means that you claim that the problem ha

Bug#795248: marked as done (ldaptor: please package new upstream)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:30 + with message-id and subject line Bug#953436: Removed package(s) from unstable has caused the Debian Bug report #795248, regarding ldaptor: please package new upstream to be marked as done. This means that you claim that the problem has been dealt

Bug#937058: marked as done (moap: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:57:46 + with message-id and subject line Bug#953433: Removed package(s) from unstable has caused the Debian Bug report #937058, regarding moap: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been deal

Bug#566033: marked as done (moap doap crashes on any .doap file)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:57:46 + with message-id and subject line Bug#953433: Removed package(s) from unstable has caused the Debian Bug report #566033, regarding moap doap crashes on any .doap file to be marked as done. This means that you claim that the problem has been dealt

Bug#827419: marked as done (ldaptor: please make the build reproducible)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:30 + with message-id and subject line Bug#953436: Removed package(s) from unstable has caused the Debian Bug report #827419, regarding ldaptor: please make the build reproducible to be marked as done. This means that you claim that the problem has bee

Bug#936520: marked as done (flashbake: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:58:07 + with message-id and subject line Bug#953434: Removed package(s) from unstable has caused the Debian Bug report #936520, regarding flashbake: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#953429: marked as done (RM: pyptlib -- ROM; Package is obsolete)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:50:23 + with message-id and subject line Bug#953429: Removed package(s) from unstable has caused the Debian Bug report #953429, regarding RM: pyptlib -- ROM; Package is obsolete to be marked as done. This means that you claim that the problem has been de

Bug#728101: marked as done (failing autopkgtest: ImportError: No module named test.test_core)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:50:27 + with message-id and subject line Bug#953429: Removed package(s) from unstable has caused the Debian Bug report #728101, regarding failing autopkgtest: ImportError: No module named test.test_core to be marked as done. This means that you claim tha

Bug#937508: marked as done (pyptlib: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:50:27 + with message-id and subject line Bug#953429: Removed package(s) from unstable has caused the Debian Bug report #937508, regarding pyptlib: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been d

Bug#953408: marked as done (RM: coq [armel armhf i386 mipsel mips64el s390x] -- ROM; FTBFS (mostly on 32bit architectures, or where ocaml has only a bytecode compiler))

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:50:01 + with message-id and subject line Bug#953408: Removed package(s) from unstable has caused the Debian Bug report #953408, regarding RM: coq [armel armhf i386 mipsel mips64el s390x] -- ROM; FTBFS (mostly on 32bit architectures, or where ocaml has on

Bug#953398: marked as done (gnome-builder: uninstallable in unstable: gir1.2-glib-2.0 (>= 2.61.2) unavailable)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:04:18 + with message-id and subject line Bug#953398: fixed in gnome-builder 3.36.0-2 has caused the Debian Bug report #953398, regarding gnome-builder: uninstallable in unstable: gir1.2-glib-2.0 (>= 2.61.2) unavailable to be marked as done. This means t

Bug#941134: marked as done (bacula-director-mysql: Script grant_mysql_privileges always set password XXX_DBPASSWORD_XXX)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 23:57:36 +0100 with message-id <87pndli1b3@arioch.leonhardt.eu> and subject line Re: Bug#941134: bacula-director-mysql: Script grant_mysql_privileges always set password XXX_DBPASSWORD_XXX has caused the Debian Bug report #941134, regarding bacula-director-m

Bug#952416: marked as done (glom: Use python3-embed pkg-config instead of python3)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:37:01 + with message-id and subject line Bug#952416: fixed in glom 1.30.4-6 has caused the Debian Bug report #952416, regarding glom: Use python3-embed pkg-config instead of python3 to be marked as done. This means that you claim that the problem has bee

Bug#953346: marked as done (open-vm-tools: consider raise process priority of vmtoolsd)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:37:42 + with message-id and subject line Bug#953346: fixed in open-vm-tools 2:11.0.5-4 has caused the Debian Bug report #953346, regarding open-vm-tools: consider raise process priority of vmtoolsd to be marked as done. This means that you claim that the

Processed: closing 929061

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 929061 1.12.0-6 Bug #929061 [src:gpgme1.0] gpgme1.0: autopkgtest regression: python3.6 dependency Marked as fixed in versions gpgme1.0/1.12.0-6. Bug #929061 [src:gpgme1.0] gpgme1.0: autopkgtest regression: python3.6 dependency Marked Bug a

Bug#953446: marked as done (Updating the arbiterjs Uploaders list)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:19:04 + with message-id and subject line Bug#953446: fixed in arbiterjs 1.0-4 has caused the Debian Bug report #953446, regarding Updating the arbiterjs Uploaders list to be marked as done. This means that you claim that the problem has been dealt with.

Bug#746380: marked as done (yagf crashes when opening an image file)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:04:48 + with message-id and subject line Bug#746380: fixed in yagf 0.9.5+repack1-1 has caused the Debian Bug report #746380, regarding yagf crashes when opening an image file to be marked as done. This means that you claim that the problem has been dealt

Bug#859862: marked as done (yagf: Error while recognizing all pages in set)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:04:48 + with message-id and subject line Bug#859862: fixed in yagf 0.9.5+repack1-1 has caused the Debian Bug report #859862, regarding yagf: Error while recognizing all pages in set to be marked as done. This means that you claim that the problem has bee

Bug#791400: marked as done ([yagf] Please update to 0.9.5)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:04:48 + with message-id and subject line Bug#791400: fixed in yagf 0.9.5+repack1-1 has caused the Debian Bug report #791400, regarding [yagf] Please update to 0.9.5 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#875243: marked as done ([yagf] Future Qt4 removal from Buster)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:04:48 + with message-id and subject line Bug#875243: fixed in yagf 0.9.5+repack1-1 has caused the Debian Bug report #875243, regarding [yagf] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been dealt w

Bug#792015: marked as done (yagf: Crashes while opening images)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 21:04:48 + with message-id and subject line Bug#746380: fixed in yagf 0.9.5+repack1-1 has caused the Debian Bug report #746380, regarding yagf: Crashes while opening images to be marked as done. This means that you claim that the problem has been dealt with

Bug#936900: marked as done (libpeas: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 20:42:10 + with message-id and subject line Bug#936900: fixed in libpeas 1.26.0-1 has caused the Debian Bug report #936900, regarding libpeas: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt wi

Bug#925202: marked as done (Keep calypso out of testing/buster)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 20:40:11 + with message-id and subject line Bug#925202: fixed in calypso 2.0-2 has caused the Debian Bug report #925202, regarding Keep calypso out of testing/buster to be marked as done. This means that you claim that the problem has been dealt with. If th

Bug#953348: marked as done (libpeas: FTBFS with Python 3.8)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 20:42:10 + with message-id and subject line Bug#953348: fixed in libpeas 1.26.0-1 has caused the Debian Bug report #953348, regarding libpeas: FTBFS with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#952637: marked as done (ruby-asciidoctor-pdf: FTBFS: Could not find 'concurrent-ruby' (~> 1.0.5) - did find: [concurrent-ruby-1.1.6])

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 12:41:41 -0700 with message-id <874kuxz56y@keithp.org> and subject line Close bug 952637 has caused the Debian Bug report #952637, regarding ruby-asciidoctor-pdf: FTBFS: Could not find 'concurrent-ruby' (~> 1.0.5) - did find: [concurrent-ruby-1.1.6] to be ma

Bug#940055: marked as done (ruby-asciidoctor-pdf: Please package the latest version (1.5.0~beta.4))

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 12:42:49 -0700 with message-id <871rq1z552@keithp.org> and subject line Close bug 940055 has caused the Debian Bug report #940055, regarding ruby-asciidoctor-pdf: Please package the latest version (1.5.0~beta.4) to be marked as done. This means that you clai

Bug#952105: marked as done (planetblupi: FTBFS: blupi.h:23:10: fatal error: SDL.h: No such file or directory)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 19:50:59 + with message-id and subject line Bug#952105: fixed in planetblupi 1.14.2-2 has caused the Debian Bug report #952105, regarding planetblupi: FTBFS: blupi.h:23:10: fatal error: SDL.h: No such file or directory to be marked as done. This means that

Bug#950477: marked as done (budgie-desktop: Please update the homepage)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 19:49:09 + with message-id and subject line Bug#950477: fixed in budgie-desktop 10.5.1-4 has caused the Debian Bug report #950477, regarding budgie-desktop: Please update the homepage to be marked as done. This means that you claim that the problem has been

Bug#950468: marked as done (budgie-desktop: Please update the description of the package)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 19:49:09 + with message-id and subject line Bug#950468: fixed in budgie-desktop 10.5.1-4 has caused the Debian Bug report #950468, regarding budgie-desktop: Please update the description of the package to be marked as done. This means that you claim that th

Bug#953425: marked as done (icinga2: Function call 'mkstemp' for file [..] failed with error code 13, 'Permission denied')

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 18:49:26 + with message-id and subject line Bug#953425: fixed in icinga2 2.11.3-2 has caused the Debian Bug report #953425, regarding icinga2: Function call 'mkstemp' for file [..] failed with error code 13, 'Permission denied' to be marked as done. This m

Bug#950836: marked as done (gpg-agent: generator 90gpg-agent and user with no home crontask generate annoying logs)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 18:34:18 + with message-id and subject line Bug#950836: fixed in gnupg2 2.2.19-3 has caused the Debian Bug report #950836, regarding gpg-agent: generator 90gpg-agent and user with no home crontask generate annoying logs to be marked as done. This means tha

Processed: closing 951768

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 951768 0.5.0-1 Bug #951768 [python3-sphinx-gallery] skimage documentation build fails with python 3.8 Marked as fixed in versions sphinx-gallery/0.5.0-1. Bug #951768 [python3-sphinx-gallery] skimage documentation build fails with python 3.

Bug#925797: marked as done (opensurgsim: ftbfs with GCC-9)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 17:19:13 + with message-id and subject line Bug#925797: fixed in gpgme1.0 1.13.1-7 has caused the Debian Bug report #925797, regarding opensurgsim: ftbfs with GCC-9 to be marked as done. This means that you claim that the problem has been dealt with. If thi

Bug#948153: marked as done (tor: doesn't work with ipv6 emails)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 17:43:59 +0100 with message-id <87eeu1xyuo.fsf@manticora> and subject line Re: Bug#948153: tor: doesn't work with ipv6 emails has caused the Debian Bug report #948153, regarding tor: doesn't work with ipv6 emails to be marked as done. This means that you claim t

Bug#943028: marked as done (gedit-plugins: Python2 removal in sid/bullseye)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 16:19:07 + with message-id and subject line Bug#943028: fixed in gedit-plugins 3.36.0-1 has caused the Debian Bug report #943028, regarding gedit-plugins: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has b

Bug#953199: marked as done (r10k: autopkgtest needs update for new version of ruby-puppet-forge: strict undeclared dependency)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 15:50:57 + with message-id and subject line Bug#953199: fixed in r10k 3.4.0-1 has caused the Debian Bug report #953199, regarding r10k: autopkgtest needs update for new version of ruby-puppet-forge: strict undeclared dependency to be marked as done. This m

Bug#953331: marked as done (ldb: FTBFS with Python 3.8)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 14:48:32 + with message-id and subject line Bug#953331: fixed in ldb 2:2.0.8-2 has caused the Debian Bug report #953331, regarding ldb: FTBFS with Python 3.8 to be marked as done. This means that you claim that the problem has been dealt with. If this is no

Bug#953318: marked as done (hplip: Failed to upgrade/install: dpkg-statoverride: warning: no override present)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 14:48:19 + with message-id and subject line Bug#953318: fixed in hplip 3.20.2+dfsg0-3 has caused the Debian Bug report #953318, regarding hplip: Failed to upgrade/install: dpkg-statoverride: warning: no override present to be marked as done. This means th

Bug#953418: marked as done (josm: use standard default path $HOME/.config, $HOME/.cache and $HOME/.share)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 15:38:14 +0100 with message-id and subject line Re: Bug#953418: josm: use standard default path $HOME/.config, $HOME/.cache and $HOME/.share has caused the Debian Bug report #953418, regarding josm: use standard default path $HOME/.config, $HOME/.cache and $HO

Bug#953351: marked as done (warzone2100: FTBFS in unstable: No package 'harfbuzz' found)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 13:53:42 + with message-id and subject line Bug#953351: fixed in warzone2100 3.3.0-2 has caused the Debian Bug report #953351, regarding warzone2100: FTBFS in unstable: No package 'harfbuzz' found to be marked as done. This means that you claim that the pro

Processed: already fixed

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 706765 Bug #706765 [warzone2100] hex controls inaccessible when launched with smaller window sizes Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 706765: https://bugs.debian.org/cgi-bin/

Processed: closing, no further information and can't reproduce

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 581385 Bug #581385 [warzone2100] Segmentation fault when try to run the game whereas listen music by mplayer Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 581385: https://bugs.debian.or

Processed: not a bug

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 473382 Bug #473382 [warzone2100] 320x240 is to small Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 473382: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473382 Debian Bug Tracking Sy

Bug#953277: marked as done (golang: Cannot be built twice in a row)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 13:36:43 + with message-id and subject line Bug#953277: fixed in golang-1.14 1.14-2 has caused the Debian Bug report #953277, regarding golang: Cannot be built twice in a row to be marked as done. This means that you claim that the problem has been dealt wi

Bug#952702: marked as done (python3-xlib: updated version 0.26 available)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 09:08:56 -0400 with message-id and subject line closing 952702 has caused the Debian Bug report #952702, regarding python3-xlib: updated version 0.26 available to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Processed: closing 936004

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 936004 3.34.0-1 Bug #936004 [gedit-plugins] gedit-plugins: FTBFS with gedit 3.33 There is no source info for the package 'gedit-plugins' at version '3.34.0-1' with architecture '' Unable to make a source version for version '3.34.0-1' Marke

Processed: closing 941007

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 941007 3.34.0-3 Bug #941007 [gedit-plugins] Gedit plugin codecomment cannot be enabled (Namespace GtkSource is already loaded with version 4) Marked as fixed in versions gedit-plugins/3.34.0-3. Bug #941007 [gedit-plugins] Gedit plugin codec

Bug#953358: marked as done (python3-ball: missing (unversioned) Breaks+Replaces: python-ball)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 12:04:21 + with message-id and subject line Bug#953358: fixed in ball 1.5.0+git20180813.37fc53c-6 has caused the Debian Bug report #953358, regarding python3-ball: missing (unversioned) Breaks+Replaces: python-ball to be marked as done. This means that you

Processed: seems ok now.

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 635248 Bug #635248 [warzone2100] warzone2100: segmentation fault Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 635248: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635248 Debian Bug

Bug#950176: marked as done (source-highlight: FTBFS on all architectures other than amd64)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 11:08:13 + with message-id and subject line Bug#950176: fixed in source-highlight 3.1.9-1.1 has caused the Debian Bug report #950176, regarding source-highlight: FTBFS on all architectures other than amd64 to be marked as done. This means that you claim tha

Processed: Re: Bug#839037: warzone2100: D-Bug assertions when playing

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 839037 Bug #839037 [warzone2100] warzone2100: D-Bug assertions when playing Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 839037: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=839037

Bug#946978: marked as done (Package conflict with nvidia drivers and primus with bumblebee->tries to pull legacy drivers)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:49:17 + with message-id and subject line Bug#946978: fixed in primus 0~20150328-10 has caused the Debian Bug report #946978, regarding Package conflict with nvidia drivers and primus with bumblebee->tries to pull legacy drivers to be marked as done. Thi

Bug#952517: marked as done (Can not install package libgl1-nvidia-glvnd-glx with primus)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:49:17 + with message-id and subject line Bug#951914: fixed in primus 0~20150328-10 has caused the Debian Bug report #951914, regarding Can not install package libgl1-nvidia-glvnd-glx with primus to be marked as done. This means that you claim that the pr

Bug#953233: marked as done (r-cran-gnm: autopkgtest regression: cannot open *.R: No such file)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:49:31 + with message-id and subject line Bug#953233: fixed in r-cran-gnm 1.1-1-2 has caused the Debian Bug report #953233, regarding r-cran-gnm: autopkgtest regression: cannot open *.R: No such file to be marked as done. This means that you claim that th

Bug#952515: marked as done (Can not install package libgl1-nvidia-glvnd-glx)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:49:17 + with message-id and subject line Bug#951914: fixed in primus 0~20150328-10 has caused the Debian Bug report #951914, regarding Can not install package libgl1-nvidia-glvnd-glx to be marked as done. This means that you claim that the problem has be

Bug#896140: marked as done (primus: warning at every command launch with primusrun)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:49:17 + with message-id and subject line Bug#896140: fixed in primus 0~20150328-10 has caused the Debian Bug report #896140, regarding primus: warning at every command launch with primusrun to be marked as done. This means that you claim that the problem

Bug#952518: marked as done (Can not install package libgl1-nvidia-glvnd-glx with primus)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:49:17 + with message-id and subject line Bug#951914: fixed in primus 0~20150328-10 has caused the Debian Bug report #951914, regarding Can not install package libgl1-nvidia-glvnd-glx with primus to be marked as done. This means that you claim that the pr

Bug#951914: marked as done (primus: Unusable with newest glx driver)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:49:17 + with message-id and subject line Bug#951914: fixed in primus 0~20150328-10 has caused the Debian Bug report #951914, regarding primus: Unusable with newest glx driver to be marked as done. This means that you claim that the problem has been dealt

Bug#952947: marked as done (peewee: Package latest upstream (3.13.1))

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 10:19:20 + with message-id and subject line Bug#952947: fixed in peewee 3.13.1+dfsg-1 has caused the Debian Bug report #952947, regarding peewee: Package latest upstream (3.13.1) to be marked as done. This means that you claim that the problem has been deal

Bug#953395: marked as done (python-tinyalign: FTBFS due to various build dependency issues)

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 09:33:58 + with message-id and subject line Bug#953395: fixed in python-tinyalign 0.2-2 has caused the Debian Bug report #953395, regarding python-tinyalign: FTBFS due to various build dependency issues to be marked as done. This means that you claim that t

Processed: Merge duplicates

2020-03-09 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 916654 Bug #916654 {Done: Tobias Grimm } [vdr-plugin-epgsearch] vdr-plugin-epgsearch 2.2.0+git20170817-2 Unarchived Bug 916654 > severity 916654 grave Bug #916654 {Done: Tobias Grimm } [vdr-plugin-epgsearch] vdr-plugin-epgsearch 2.2.0+

Bug#953010: marked as done (glade: Upgrade to 3.22.2 ( to work with libglib2 >= 2.63.2 ))

2020-03-09 Thread Debian Bug Tracking System
Your message dated Mon, 09 Mar 2020 09:19:09 + with message-id and subject line Bug#953010: fixed in glade 3.22.2-1 has caused the Debian Bug report #953010, regarding glade: Upgrade to 3.22.2 ( to work with libglib2 >= 2.63.2 ) to be marked as done. This means that you claim that the proble

Processed: Re: Bug#953054: "DeprecationWarning: PY_SSIZE_T_CLEAN will be required" after python3.7 -> 3.8

2020-03-09 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 python3-apt 1.8.6 Bug #953054 [debsecan] "DeprecationWarning: PY_SSIZE_T_CLEAN will be required" after python3.7 -> 3.8 Bug reassigned from package 'debsecan' to 'python3-apt'. No longer marked as found in versions debsecan/0.4.20.1. Ignoring request to