Bug#939784: marked as done (RM: libint2 [mipsel] -- ROM; autobuilders not able to build it)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:53:50 + with message-id and subject line Bug#939784: Removed package(s) from unstable has caused the Debian Bug report #939784, regarding RM: libint2 [mipsel] -- ROM; autobuilders not able to build it to be marked as done. This means that you claim that

Bug#902738: marked as done (netanim: Please package the latest upstream release 3.108-1)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:35:12 + with message-id and subject line Bug#939803: Removed package(s) from unstable has caused the Debian Bug report #902738, regarding netanim: Please package the latest upstream release 3.108-1 to be marked as done. This means that you claim that

Bug#728890: marked as done (libccss is unused and dead upstream)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:36:22 + with message-id and subject line Bug#939980: Removed package(s) from unstable has caused the Debian Bug report #728890, regarding libccss is unused and dead upstream to be marked as done. This means that you claim that the problem has been dealt

Bug#939902: marked as done (RM: xmlmarshaller -- ROM; removal triggered by the Python2 removal; popcon=26)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:35:33 + with message-id and subject line Bug#939902: Removed package(s) from unstable has caused the Debian Bug report #939902, regarding RM: xmlmarshaller -- ROM; removal triggered by the Python2 removal; popcon=26 to be marked as done. This means

Bug#939803: marked as done (RM: netanim -- RoQA; depends on qt4, unmaintained)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:35:06 + with message-id and subject line Bug#939803: Removed package(s) from unstable has caused the Debian Bug report #939803, regarding RM: netanim -- RoQA; depends on qt4, unmaintained to be marked as done. This means that you claim that the problem

Bug#938851: marked as done (xmlmarshaller: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:35:38 + with message-id and subject line Bug#939902: Removed package(s) from unstable has caused the Debian Bug report #938851, regarding xmlmarshaller: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#939954: marked as done (libccss: fails to build with gtk-doc 1.32)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:36:22 + with message-id and subject line Bug#939980: Removed package(s) from unstable has caused the Debian Bug report #939954, regarding libccss: fails to build with gtk-doc 1.32 to be marked as done. This means that you claim that the problem has been

Bug#875051: marked as done ([netanim] Future Qt4 removal from Buster)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:35:12 + with message-id and subject line Bug#939803: Removed package(s) from unstable has caused the Debian Bug report #875051, regarding [netanim] Future Qt4 removal from Buster to be marked as done. This means that you claim that the problem has been

Bug#939980: marked as done (RM: libccss -- ROM; dead upstream)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:36:16 + with message-id and subject line Bug#939980: Removed package(s) from unstable has caused the Debian Bug report #939980, regarding RM: libccss -- ROM; dead upstream to be marked as done. This means that you claim that the problem has been dealt

Bug#939774: marked as done (RM: fmit [armel armhf ia64 kfreebsd-amd64 kfreebsd-i386] -- RoQA; NBS)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:34:03 + with message-id and subject line Bug#939774: Removed package(s) from unstable has caused the Debian Bug report #939774, regarding RM: fmit [armel armhf ia64 kfreebsd-amd64 kfreebsd-i386] -- RoQA; NBS to be marked as done. This means that you

Bug#939746: marked as done (RM: python-rudolf -- ROM; no reverse dependencies)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:32:34 + with message-id and subject line Bug#939746: Removed package(s) from unstable has caused the Debian Bug report #939746, regarding RM: python-rudolf -- ROM; no reverse dependencies to be marked as done. This means that you claim that the problem

Bug#936594: marked as done (geda-xgsch2pcb: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:38 + with message-id and subject line Bug#939769: Removed package(s) from unstable has caused the Debian Bug report #936594, regarding geda-xgsch2pcb: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

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

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:32:38 + with message-id and subject line Bug#939746: Removed package(s) from unstable has caused the Debian Bug report #938151, regarding python-rudolf: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#928593: marked as done (Updating the python-hp3parclient Uploaders list)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:07 + with message-id and subject line Bug#939749: Removed package(s) from unstable has caused the Debian Bug report #928593, regarding Updating the python-hp3parclient Uploaders list to be marked as done. This means that you claim that the problem

Bug#885285: marked as done (geda-xgsch2pcb: Depends on unmaintained pygtk)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:38 + with message-id and subject line Bug#939769: Removed package(s) from unstable has caused the Debian Bug report #885285, regarding geda-xgsch2pcb: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has

Bug#939769: marked as done (RM: geda-xgsch2pcb -- ROM; Unmaintained by upstream)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:32 + with message-id and subject line Bug#939769: Removed package(s) from unstable has caused the Debian Bug report #939769, regarding RM: geda-xgsch2pcb -- ROM; Unmaintained by upstream to be marked as done. This means that you claim that the

Bug#937824: marked as done (python-ibm-db-sa: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:31:24 + with message-id and subject line Bug#939734: Removed package(s) from unstable has caused the Debian Bug report #937824, regarding python-ibm-db-sa: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#773410: marked as done (geda-xgsch2pcb does not pull in geda or gschem as a dependcy.)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:38 + with message-id and subject line Bug#939769: Removed package(s) from unstable has caused the Debian Bug report #773410, regarding geda-xgsch2pcb does not pull in geda or gschem as a dependcy. to be marked as done. This means that you claim that

Bug#939107: marked as done (linaro-image-tools: Python2 removal in sid/bullseye -- drop python-distutils-extra build dependency)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:30:02 + with message-id and subject line Bug#879386: Removed package(s) from unstable has caused the Debian Bug report #939107, regarding linaro-image-tools: Python2 removal in sid/bullseye -- drop python-distutils-extra build dependency to be marked as

Bug#831478: marked as done (Updating the geda-xgsch2pcb Uploaders list)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:38 + with message-id and subject line Bug#939769: Removed package(s) from unstable has caused the Debian Bug report #831478, regarding Updating the geda-xgsch2pcb Uploaders list to be marked as done. This means that you claim that the problem has

Bug#939743: marked as done (RM: python-positional -- ROM; no reverse dependencies)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:32:04 + with message-id and subject line Bug#939743: Removed package(s) from unstable has caused the Debian Bug report #939743, regarding RM: python-positional -- ROM; no reverse dependencies to be marked as done. This means that you claim that the

Bug#938039: marked as done (python-posix-ipc: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:31:46 + with message-id and subject line Bug#939742: Removed package(s) from unstable has caused the Debian Bug report #938039, regarding python-posix-ipc: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

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

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:32:08 + with message-id and subject line Bug#939743: Removed package(s) from unstable has caused the Debian Bug report #938038, regarding python-positional: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#937227: marked as done (RM: p4vasp -- removal triggered by the Python2 removal)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:30:52 + with message-id and subject line Bug#937227: Removed package(s) from unstable has caused the Debian Bug report #937227, regarding RM: p4vasp -- removal triggered by the Python2 removal to be marked as done. This means that you claim that the

Bug#939749: marked as done (RM: python-hp3parclient -- ROM; not in use anymore, py2 only)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:02 + with message-id and subject line Bug#939749: Removed package(s) from unstable has caused the Debian Bug report #939749, regarding RM: python-hp3parclient -- ROM; not in use anymore, py2 only to be marked as done. This means that you claim that

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

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:33:07 + with message-id and subject line Bug#939749: Removed package(s) from unstable has caused the Debian Bug report #937813, regarding python-hp3parclient: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#939734: marked as done (RM: python-ibm-db-sa -- ROM; Python 2 only, not in used anymore)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:31:20 + with message-id and subject line Bug#939734: Removed package(s) from unstable has caused the Debian Bug report #939734, regarding RM: python-ibm-db-sa -- ROM; Python 2 only, not in used anymore to be marked as done. This means that you claim

Bug#939742: marked as done (RM: python-posix-ipc -- ROM; Not in use, using python3-sysv-ipc instead)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:31:42 + with message-id and subject line Bug#939742: Removed package(s) from unstable has caused the Debian Bug report #939742, regarding RM: python-posix-ipc -- ROM; Not in use, using python3-sysv-ipc instead to be marked as done. This means that you

Bug#936948: marked as done (linaro-image-tools: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:30:02 + with message-id and subject line Bug#879386: Removed package(s) from unstable has caused the Debian Bug report #936948, regarding linaro-image-tools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#868775: marked as done (python-posix-ipc: New upstream 1.0.0 required for Django Channels ASGI IPC)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:31:46 + with message-id and subject line Bug#939742: Removed package(s) from unstable has caused the Debian Bug report #868775, regarding python-posix-ipc: New upstream 1.0.0 required for Django Channels ASGI IPC to be marked as done. This means that

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

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:09 + with message-id and subject line Bug#840041: Removed package(s) from unstable has caused the Debian Bug report #937782, regarding python-geohash: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#879386: marked as done (RM: linaro-image-tools -- RoQA; python2-only; orphaned; dead upstream; low popcon)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:56 + with message-id and subject line Bug#879386: Removed package(s) from unstable has caused the Debian Bug report #879386, regarding RM: linaro-image-tools -- RoQA; python2-only; orphaned; dead upstream; low popcon to be marked as done. This means

Bug#937319: marked as done (prelude-notify: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:32 + with message-id and subject line Bug#866937: Removed package(s) from unstable has caused the Debian Bug report #937319, regarding prelude-notify: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#885509: marked as done (p4vasp: Depends on unmaintained python-glade2)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:30:55 + with message-id and subject line Bug#937227: Removed package(s) from unstable has caused the Debian Bug report #885509, regarding p4vasp: Depends on unmaintained python-glade2 to be marked as done. This means that you claim that the problem has

Bug#928578: marked as done (Updating the python-ibm-db-sa Uploaders list)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:31:24 + with message-id and subject line Bug#939734: Removed package(s) from unstable has caused the Debian Bug report #928578, regarding Updating the python-ibm-db-sa Uploaders list to be marked as done. This means that you claim that the problem has

Bug#890161: marked as done (prelude-notify: Please switch to python-gobject-2/python-gi)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:32 + with message-id and subject line Bug#866937: Removed package(s) from unstable has caused the Debian Bug report #890161, regarding prelude-notify: Please switch to python-gobject-2/python-gi to be marked as done. This means that you claim that

Bug#690614: marked as done (linaro-image-tools: bashism in /bin/sh script)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:30:02 + with message-id and subject line Bug#879386: Removed package(s) from unstable has caused the Debian Bug report #690614, regarding linaro-image-tools: bashism in /bin/sh script to be marked as done. This means that you claim that the problem has

Bug#885362: marked as done (prelude-notify: Depends on unmaintained pygtk)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:32 + with message-id and subject line Bug#866937: Removed package(s) from unstable has caused the Debian Bug report #885362, regarding prelude-notify: Depends on unmaintained pygtk to be marked as done. This means that you claim that the problem has

Bug#866937: marked as done (RM: prelude-notify -- RoQA; python2-only; orphaned; dead upstream; low popcon)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:27 + with message-id and subject line Bug#866937: Removed package(s) from unstable has caused the Debian Bug report #866937, regarding RM: prelude-notify -- RoQA; python2-only; orphaned; dead upstream; low popcon to be marked as done. This means

Bug#826188: marked as done (python-geohash: Python3 package request)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:09 + with message-id and subject line Bug#840041: Removed package(s) from unstable has caused the Debian Bug report #826188, regarding python-geohash: Python3 package request to be marked as done. This means that you claim that the problem has been

Bug#914274: marked as done (please package python3 version)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:31:24 + with message-id and subject line Bug#939734: Removed package(s) from unstable has caused the Debian Bug report #914274, regarding please package python3 version to be marked as done. This means that you claim that the problem has been dealt

Bug#840041: marked as done (RM: python-geohash -- RoQA; python2-only; orphaned; dead upstream; low popcon)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 05:29:04 + with message-id and subject line Bug#840041: Removed package(s) from unstable has caused the Debian Bug report #840041, regarding RM: python-geohash -- RoQA; python2-only; orphaned; dead upstream; low popcon to be marked as done. This means

Bug#939938: marked as done (harfbuzz: missing python build-dependency causes FTBFS with gtk-doc 1.32)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 04:22:40 + with message-id and subject line Bug#939938: fixed in harfbuzz 2.6.1-3 has caused the Debian Bug report #939938, regarding harfbuzz: missing python build-dependency causes FTBFS with gtk-doc 1.32 to be marked as done. This means that you claim

Bug#939821: marked as done (capnproto: test failure due to new gcc-9)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Wed, 11 Sep 2019 04:03:49 + with message-id and subject line Bug#939821: fixed in capnproto 0.7.0-5 has caused the Debian Bug report #939821, regarding capnproto: test failure due to new gcc-9 to be marked as done. This means that you claim that the problem has been dealt

Bug#919877: marked as done (ruby-sprite-factory: FTBFS (failing test))

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 23:59:11 +0200 with message-id <20190910215907.GA10494@esfahan> and subject line fixed by 1.7.1-3 upload has caused the Debian Bug report #919877, regarding ruby-sprite-factory: FTBFS (failing test) to be marked as done. This means that you claim that the

Bug#934586: marked as done (chkboot: flawed profile.d script breaks on non-bash shells and pollutes environment)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 22:04:22 + with message-id and subject line Bug#934586: fixed in chkboot 1.3-3 has caused the Debian Bug report #934586, regarding chkboot: flawed profile.d script breaks on non-bash shells and pollutes environment to be marked as done. This means that

Bug#932190: marked as done (ruby-jekyll-gist: missing dependency on ruby-octokit)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 21:52:25 + with message-id and subject line Bug#932190: fixed in ruby-jekyll-gist 1.5.0-2 has caused the Debian Bug report #932190, regarding ruby-jekyll-gist: missing dependency on ruby-octokit to be marked as done. This means that you claim that the

Bug#936171: marked as done (autorenamer: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 21:19:49 + with message-id and subject line Bug#936171: fixed in autorenamer 0.5-1 has caused the Debian Bug report #936171, regarding autorenamer: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#916286: marked as done (traverso: baseline violation on i386)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 20:46:32 + with message-id and subject line Bug#916286: fixed in traverso 0.49.6-1 has caused the Debian Bug report #916286, regarding traverso: baseline violation on i386 to be marked as done. This means that you claim that the problem has been dealt

Bug#939684: marked as done (traverso FTCBFS: detects compiler flags from the current cpu)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 20:46:33 + with message-id and subject line Bug#939684: fixed in traverso 0.49.6-1 has caused the Debian Bug report #939684, regarding traverso FTCBFS: detects compiler flags from the current cpu to be marked as done. This means that you claim that the

Bug#852440: marked as done (lv2proc new upstream version)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 20:44:47 + with message-id and subject line Bug#852440: fixed in lv2proc 0.5.1-1 has caused the Debian Bug report #852440, regarding lv2proc new upstream version to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#936588: marked as done (gcc-9-cross-ports: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 20:41:24 + with message-id and subject line Bug#936588: fixed in gcc-9-cross-ports 10 has caused the Debian Bug report #936588, regarding gcc-9-cross-ports: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#934887: marked as done (CVE-2019-9512 CVE-2019-9514 CVE-2019-9515)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 19:54:43 + with message-id and subject line Bug#934887: fixed in trafficserver 8.0.2+ds-1+deb10u1 has caused the Debian Bug report #934887, regarding CVE-2019-9512 CVE-2019-9514 CVE-2019-9515 to be marked as done. This means that you claim that the problem

Bug#935314: marked as done (trafficserver: CVE-2019-9518)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 19:54:43 + with message-id and subject line Bug#935314: fixed in trafficserver 8.0.2+ds-1+deb10u1 has caused the Debian Bug report #935314, regarding trafficserver: CVE-2019-9518 to be marked as done. This means that you claim that the problem has been

Bug#598817: marked as done ([traverso] Crashes when opening file dialogs in KDE4)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 21:44:42 +0200 with message-id <20190910194442.ga4...@ramacher.at> and subject line Re: Bug#598817: [traverso] Crashes when opening file dialogs in KDE4 has caused the Debian Bug report #598817, regarding [traverso] Crashes when opening file dialogs in KDE4 to

Bug#939578: marked as done (fontforge: FTBFS: There is no package matching [libspiro1-dev] and noone provides it)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 19:49:11 + with message-id and subject line Bug#939578: fixed in d-shlibs 0.87 has caused the Debian Bug report #939578, regarding fontforge: FTBFS: There is no package matching [libspiro1-dev] and noone provides it to be marked as done. This means that

Bug#939927: marked as done (mariadb-server-10.1 Cannot complete the upgrade package)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 22:33:56 +0300 with message-id and subject line Re: [debian-mysql] Bug#939927: mariadb-server-10.1 Cannot complete the upgrade package has caused the Debian Bug report #939927, regarding mariadb-server-10.1 Cannot complete the upgrade package to be marked as

Bug#939863: marked as done (mariadb-server-10.3: won't start without libjemalloc1 from jessie)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 22:33:20 +0300 with message-id and subject line Re: [debian-mysql] Bug#939863: mariadb-server-10.3: won't start without libjemalloc1 from jessie has caused the Debian Bug report #939863, regarding mariadb-server-10.3: won't start without libjemalloc1 from

Bug#815139: marked as done (build ldb python3 bindings)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 20:59:38 +0200 with message-id and subject line Python3-ldb done has caused the Debian Bug report #815139, regarding build ldb python3 bindings to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is

Bug#939978: marked as done (buster-pu: package flightcrew/0.7.2+dfsg-13+deb10u1)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 19:11:20 +0100 with message-id <8878ff801666ef402d18c771343db4d2fd56d901.ca...@adam-barratt.org.uk> and subject line Re: Bug#939978: buster-pu: package flightcrew/0.7.2+dfsg-13+deb10u1 has caused the Debian Bug report #939978, regarding buster-pu: package

Bug#929032: marked as done (python-scapy: new upstream release)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 17:36:18 + with message-id and subject line Bug#929032: fixed in scapy 2.4.3-1 has caused the Debian Bug report #929032, regarding python-scapy: new upstream release to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#939403: marked as done (Incorrect python3-geoip in Suggests (replace with python3-geoip2))

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 17:36:18 + with message-id and subject line Bug#939403: fixed in scapy 2.4.3-1 has caused the Debian Bug report #939403, regarding Incorrect python3-geoip in Suggests (replace with python3-geoip2) to be marked as done. This means that you claim that the

Bug#907235: marked as done (python3-scapy: Please provide package without large 'Recommends')

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 17:36:18 + with message-id and subject line Bug#907235: fixed in scapy 2.4.3-1 has caused the Debian Bug report #907235, regarding python3-scapy: Please provide package without large 'Recommends' to be marked as done. This means that you claim that the

Bug#938439: marked as done (scapy: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 17:36:18 + with message-id and subject line Bug#938439: fixed in scapy 2.4.3-1 has caused the Debian Bug report #938439, regarding scapy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Processed: closing 939791

2019-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # migrated to testing together with the new version of lxml > close 939791 Bug #939791 [src:crmsh] crmsh: autopkgtest needs update for new version of lxml Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Processed: closing 939395

2019-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > # solved by configuration > close 939395 Bug #939395 [ocfs2-tools] ocfs2-tools - FS can't mount at boot on drbd device Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 939395:

Bug#936587: marked as done (gcc-9-cross: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 17:19:15 + with message-id and subject line Bug#936587: fixed in gcc-9-cross 12 has caused the Debian Bug report #936587, regarding gcc-9-cross: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#738763: marked as done (ale: Wrong upstream Homepage URL)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 17:04:02 + with message-id and subject line Bug#738763: fixed in ale 0.9.0.3-4 has caused the Debian Bug report #738763, regarding ale: Wrong upstream Homepage URL to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#935872: marked as done (pytest-sugar: FTBFS with pytest 4.6)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 15:05:53 + with message-id and subject line Bug#935872: fixed in pytest-sugar 0.9.2-2 has caused the Debian Bug report #935872, regarding pytest-sugar: FTBFS with pytest 4.6 to be marked as done. This means that you claim that the problem has been dealt

Bug#938740: marked as done (ubuntu-dev-tools: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 14:40:42 + with message-id and subject line Bug#938740: fixed in ubuntu-dev-tools 0.173 has caused the Debian Bug report #938740, regarding ubuntu-dev-tools: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#939923: marked as done (mono ftbfs in unstable (still calling python))

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 14:40:13 + with message-id and subject line Bug#939923: fixed in mono 5.18.0.240+dfsg-5 has caused the Debian Bug report #939923, regarding mono ftbfs in unstable (still calling python) to be marked as done. This means that you claim that the problem has

Bug#927147: marked as done (requestsync: Please port to python3)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 14:40:42 + with message-id and subject line Bug#927147: fixed in ubuntu-dev-tools 0.173 has caused the Debian Bug report #927147, regarding requestsync: Please port to python3 to be marked as done. This means that you claim that the problem has been dealt

Bug#773192: marked as done (disable DSA key generation by default)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 15:06:42 +0100 with message-id <20190910140642.ga11...@riva.ucam.org> and subject line Re: Bug#773192: disable DSA key generation by default has caused the Debian Bug report #773192, regarding disable DSA key generation by default to be marked as done. This

Bug#935243: marked as done (Does not work with Thunderbird 6x (60+))

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 15:19:39 +0200 with message-id and subject line Close Bug #935243 has caused the Debian Bug report #935243, regarding Does not work with Thunderbird 6x (60+) to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#923888: marked as done (goattracker FTCBFS: builds for the build architecture)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 12:35:22 + with message-id and subject line Bug#923888: fixed in goattracker 2.75-3 has caused the Debian Bug report #923888, regarding goattracker FTCBFS: builds for the build architecture to be marked as done. This means that you claim that the problem

Bug#939736: marked as done (mutter 3.33+: Please add "Breaks: apparmor (<< 2.13.3-5~)")

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 12:05:28 + with message-id and subject line Bug#939736: fixed in mutter 3.34.0-1 has caused the Debian Bug report #939736, regarding mutter 3.33+: Please add "Breaks: apparmor (<< 2.13.3-5~)" to be marked as done. This means that you claim that the problem

Processed: close 939941

2019-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 939941 Bug #939941 [nvidia-driver] nvidia-driver: "display engine hung" error at boot with gdm background frozen Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 939941:

Bug#939942: marked as done (php-pecl-http; undefined symbol: uidna_IDNToASCII)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 13:54:47 +0200 with message-id and subject line Re: Bug#939942: php-pecl-http; undefined symbol: uidna_IDNToASCII has caused the Debian Bug report #939942, regarding php-pecl-http; undefined symbol: uidna_IDNToASCII to be marked as done. This means that you

Bug#938134: marked as done (python-repoze.who: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 11:51:03 + with message-id and subject line Bug#938134: fixed in python-repoze.who 2.2-4 has caused the Debian Bug report #938134, regarding python-repoze.who: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#936220: marked as done (bluefish: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 13:21:46 +0200 with message-id and subject line Remove python2 modules has caused the Debian Bug report #936220, regarding bluefish: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#926301: marked as done (coda: please make the build reproducible)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 11:04:30 + with message-id and subject line Bug#926301: fixed in coda 2.21-2 has caused the Debian Bug report #926301, regarding coda: please make the build reproducible to be marked as done. This means that you claim that the problem has been dealt with.

Bug#936588: marked as done (gcc-9-cross-ports: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 11:04:40 + with message-id and subject line Bug#936588: fixed in cross-toolchain-base-ports 35 has caused the Debian Bug report #936588, regarding gcc-9-cross-ports: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#936587: marked as done (gcc-9-cross: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 11:04:35 + with message-id and subject line Bug#936587: fixed in cross-toolchain-base 42 has caused the Debian Bug report #936587, regarding gcc-9-cross: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

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

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 10:35:00 + with message-id and subject line Bug#937590: fixed in python-autobahn 17.10.1+dfsg1-6 has caused the Debian Bug report #937590, regarding python-autobahn: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#939304: marked as done (libgpiod: please mark some symbols as optional)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 10:19:52 + with message-id and subject line Bug#939304: fixed in libgpiod 1.4.1-3 has caused the Debian Bug report #939304, regarding libgpiod: please mark some symbols as optional to be marked as done. This means that you claim that the problem has been

Bug#896835: marked as done (libassimp-dev: CMake configuration resolves incorrect paths with multiarch lib directory)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 10:05:14 + with message-id and subject line Bug#896835: fixed in assimp 4.1.0~dfsg-6 has caused the Debian Bug report #896835, regarding libassimp-dev: CMake configuration resolves incorrect paths with multiarch lib directory to be marked as done. This

Bug#856122: marked as done (calf-plugins: UI not loaded in ardour (works in the standelone app))

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 11:01:23 +0200 with message-id <2911f3f2-2dc1-1f9b-709b-2e1b531d2...@debian.org> and subject line calf-plugins: UI not loaded in ardour (works in the standelone app) has caused the Debian Bug report #856122, regarding calf-plugins: UI not loaded in ardour

Bug#936856: marked as done (libfiu: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 09:49:29 + with message-id and subject line Bug#936856: fixed in libfiu 1.00-1 has caused the Debian Bug report #936856, regarding libfiu: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#736766: marked as done (/usr/bin/modplugplay: segfaults with xm sound files)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 11:33:03 +0200 with message-id and subject line these have been fixed has caused the Debian Bug report #736766, regarding /usr/bin/modplugplay: segfaults with xm sound files to be marked as done. This means that you claim that the problem has been dealt with.

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

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 09:34:27 + with message-id and subject line Bug#938104: fixed in python-pytimeparse 1.1.5-3 has caused the Debian Bug report #938104, regarding python-pytimeparse: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#937933: marked as done (python-multi-key-dict: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 09:21:34 + with message-id and subject line Bug#937933: fixed in python-multi-key-dict 2.0.3-2 has caused the Debian Bug report #937933, regarding python-multi-key-dict: Python2 removal in sid/bullseye to be marked as done. This means that you claim that

Bug#939834: marked as done (claws-mail: Does not respond to `can_change_accels`)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 10:01:33 +0100 with message-id <20190910100133.24f85...@shy.leonerd.org.uk> and subject line Re: Bug#939834: claws-mail: Does not respond to `can_change_accels` has caused the Debian Bug report #939834, regarding claws-mail: Does not respond to

Processed: closing 935304

2019-09-10 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 935304 Bug #935304 [libpam-systemd] libpam-systemd: Please relax Depends: systemd-sysv Marked Bug as done > thanks Stopping processing here. Please contact me if you need assistance. -- 935304:

Bug#936518: marked as done (fitgcp: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 08:49:18 + with message-id and subject line Bug#936518: fixed in fitgcp 0.0.20150429-3 has caused the Debian Bug report #936518, regarding fitgcp: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#925113: marked as done (Updating the zed Uploaders list)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 08:41:09 + with message-id and subject line Bug#925113: fixed in zed 2.0.3-1 has caused the Debian Bug report #925113, regarding Updating the zed Uploaders list to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#922891: marked as done (O: bluefish -- advanced Gtk+ text editor for web and software development)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 08:36:10 + with message-id and subject line Bug#922891: fixed in bluefish 2.2.10-2 has caused the Debian Bug report #922891, regarding O: bluefish -- advanced Gtk+ text editor for web and software development to be marked as done. This means that you

Bug#939582: marked as done (RM: teeworlds/stretch-security -- RoST; security issues; incompatible with current servers; removed from stretch)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 07:16:21 + with message-id and subject line Bug#939582: Removed package(s) from oldstable has caused the Debian Bug report #939582, regarding RM: teeworlds/stretch-security -- RoST; security issues; incompatible with current servers; removed from stretch

Bug#939745: marked as done (python-nameparser: needs a source-only upload)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 07:04:39 + with message-id and subject line Bug#939745: fixed in python-nameparser 1.0.4-2 has caused the Debian Bug report #939745, regarding python-nameparser: needs a source-only upload to be marked as done. This means that you claim that the problem

Bug#936281: marked as done (centrifuge: Python2 removal in sid/bullseye)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 06:49:12 + with message-id and subject line Bug#936281: fixed in centrifuge 1.0.3-3 has caused the Debian Bug report #936281, regarding centrifuge: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#931949: marked as done (transition: proj)

2019-09-10 Thread Debian Bug Tracking System
Your message dated Tue, 10 Sep 2019 08:06:12 +0200 with message-id <34824c6f-88d7-ef08-6d4e-8e96a1690...@xs4all.nl> and subject line Re: Bug#931949: transition: proj has caused the Debian Bug report #931949, regarding transition: proj to be marked as done. This means that you claim that the

  1   2   >