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

2020-02-11 Thread Debian Bug Tracking System
Your message dated Wed, 12 Feb 2020 00:34:31 + with message-id and subject line Bug#938866: fixed in yara-python 3.11.0-1 has caused the Debian Bug report #938866, regarding yara-python: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#947998: marked as done (notary FTBFS in testing/unstable)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Wed, 12 Feb 2020 13:12:52 +1100 with message-id <2750517.lavbA0dvI8@deblab> and subject line done: #947998 notary FTBFS in testing/unstable has caused the Debian Bug report #947998, regarding notary FTBFS in testing/unstable to be marked as done. This means that you claim that

Processed: Re: python-qtpy: FTBFS due to typo in debian/control

2020-02-11 Thread Debian Bug Tracking System
Processing control commands: > fixed -1 1.9.0-2 Bug #951032 [python-qtpy] python-qtpy: FTBFS due to typo in debian/control There is no source info for the package 'python-qtpy' at version '1.9.0-2' with architecture '' Unable to make a source version for version '1.9.0-2' Marked as fixed in

Processed: unarchiving 945023, closing 945023

2020-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 945023 Bug #945023 {Done: Salvatore Bonaccorso } [src:linux] Backport 'ipv4: Return -ENETUNREACH if we can't create route but saddr is valid' Unarchived Bug 945023 > close 945023 4.9.210-1 Bug #945023 {Done: Salvatore Bonaccorso }

Bug#951059: marked as done (mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 09:58:39 +0100 with message-id <20200211085839.GA1977251@falared> and subject line Re: [debian-mysql] Bug#951059: Bug#951059: mariadb-server-10.3: lc_messages=fr_FR leads to upgrade crash with apt has caused the Debian Bug report #951059, regarding

Bug#950852: marked as done (simpleeval fails its tests with Python 3.8)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 10:50:36 + with message-id and subject line Bug#950852: fixed in simpleeval 0.9.10-1 has caused the Debian Bug report #950852, regarding simpleeval fails its tests with Python 3.8 to be marked as done. This means that you claim that the problem has been

Bug#940199: marked as done (pluma: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 08:49:30 + with message-id and subject line Bug#940199: fixed in pluma 1.24.0-1 has caused the Debian Bug report #940199, regarding pluma: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#945690: marked as done (pluma: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 08:49:30 + with message-id and subject line Bug#940199: fixed in pluma 1.24.0-1 has caused the Debian Bug report #940199, regarding pluma: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#878469: marked as done (js-of-ocaml FTBFS: ocamlbuild: Command not found)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 09:19:18 + with message-id and subject line Bug#878469: fixed in js-of-ocaml 3.5.2-1 has caused the Debian Bug report #878469, regarding js-of-ocaml FTBFS: ocamlbuild: Command not found to be marked as done. This means that you claim that the problem has

Bug#936042: marked as done (Assertion `vao_formats.count(key) == 0' failed.)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 10:48:31 +0100 with message-id and subject line Re: Bug#936042: Assertion `vao_formats.count(key) == 0' failed. has caused the Debian Bug report #936042, regarding Assertion `vao_formats.count(key) == 0' failed. to be marked as done. This means that you claim

Bug#875296: marked as done (lmms: Problem with file openning (from nautilus or terminal) (unicode?))

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 10:46:45 +0100 with message-id and subject line Re: lmms: Problem with file openning has caused the Debian Bug report #875296, regarding lmms: Problem with file openning (from nautilus or terminal) (unicode?) to be marked as done. This means that you claim

Bug#934038: marked as done (ASSERT: "mImg == qImg->constBits()" in file common.cpp, line 63)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 10:48:15 +0100 with message-id <7902eac9-3405-1330-f202-7aca0059c...@debian.org> and subject line Re: Bug#934038: ASSERT: "mImg == qImg->constBits()" in file common.cpp, line 63 has caused the Debian Bug report #934038, regarding ASSERT: "mImg ==

Bug#949566: marked as done (iproute2: Please make autopkgtests cross-test-friendly)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 11:19:03 + with message-id and subject line Bug#949566: fixed in iproute2 5.5.0-1 has caused the Debian Bug report #949566, regarding iproute2: Please make autopkgtests cross-test-friendly to be marked as done. This means that you claim that the problem

Bug#951089: marked as done (iproute2, build-depends on removed package.)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 11:19:03 + with message-id and subject line Bug#951089: fixed in iproute2 5.5.0-1 has caused the Debian Bug report #951089, regarding iproute2, build-depends on removed package. to be marked as done. This means that you claim that the problem has been

Bug#950874: marked as done (RM: msrtool -- ROM; see #381727)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:56:22 + with message-id and subject line Bug#950865: Removed package(s) from unstable has caused the Debian Bug report #950874, regarding RM: msrtool -- ROM; see #381727 to be marked as done. This means that you claim that the problem has been dealt

Bug#950865: marked as done (RM: msrtool -- ROM; RM: see #381727)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:56:17 + with message-id and subject line Bug#950865: Removed package(s) from unstable has caused the Debian Bug report #950865, regarding RM: msrtool -- ROM; RM: see #381727 to be marked as done. This means that you claim that the problem has been dealt

Bug#950874: marked as done (RM: msrtool -- ROM; see #381727)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:56:17 + with message-id and subject line Bug#950865: Removed package(s) from unstable has caused the Debian Bug report #950865, regarding RM: msrtool -- ROM; see #381727 to be marked as done. This means that you claim that the problem has been dealt

Bug#950865: marked as done (RM: msrtool -- ROM; RM: see #381727)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:56:22 + with message-id and subject line Bug#950865: Removed package(s) from unstable has caused the Debian Bug report #950874, regarding RM: msrtool -- ROM; RM: see #381727 to be marked as done. This means that you claim that the problem has been dealt

Bug#950875: marked as done (RM: superiotool -- ROM; see #381727)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:56:40 + with message-id and subject line Bug#950875: Removed package(s) from unstable has caused the Debian Bug report #950875, regarding RM: superiotool -- ROM; see #381727 to be marked as done. This means that you claim that the problem has been dealt

Bug#950835: marked as done (RM: js-build-tools -- ROM; deprecated by upstream)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:54:30 + with message-id and subject line Bug#950835: Removed package(s) from unstable has caused the Debian Bug report #950835, regarding RM: js-build-tools -- ROM; deprecated by upstream to be marked as done. This means that you claim that the problem

Bug#847093: marked as done (msrtool: please restrict the build architectures)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:56:22 + with message-id and subject line Bug#950865: Removed package(s) from unstable has caused the Debian Bug report #847093, regarding msrtool: please restrict the build architectures to be marked as done. This means that you claim that the problem

Bug#784120: marked as done (msrtool: Description mentions "Pentium IIV")

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:56:22 + with message-id and subject line Bug#950865: Removed package(s) from unstable has caused the Debian Bug report #784120, regarding msrtool: Description mentions "Pentium IIV" to be marked as done. This means that you claim that the problem has

Bug#951074: marked as done (Missing depend libcache-cache-perl)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:26:04 + with message-id <20200211122604.ga6...@layer-acht.org> and subject line Re: Bug#951074: Missing depend libcache-cache-perl has caused the Debian Bug report #951074, regarding Missing depend libcache-cache-perl to be marked as done. This means

Bug#950255: marked as done (RM: rust-pcap -- ROM; no longer in use)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:50:03 + with message-id and subject line Bug#950255: Removed package(s) from unstable has caused the Debian Bug report #950255, regarding RM: rust-pcap -- ROM; no longer in use to be marked as done. This means that you claim that the problem has been

Bug#950864: marked as done (RM: inteltool -- ROM; RM: see #381727)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:55:20 + with message-id and subject line Bug#950864: Removed package(s) from unstable has caused the Debian Bug report #950864, regarding RM: inteltool -- ROM; RM: see #381727 to be marked as done. This means that you claim that the problem has been

Bug#950137: marked as done (freecad builds using a fixed python version (3.7))

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 13:04:21 + with message-id and subject line Bug#950137: fixed in freecad 0.18.4+dfsg2-1 has caused the Debian Bug report #950137, regarding freecad builds using a fixed python version (3.7) to be marked as done. This means that you claim that the problem

Bug#943277: marked as done (sogo: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:51:02 + with message-id and subject line Bug#943277: fixed in sogo 4.3.0-1 has caused the Debian Bug report #943277, regarding sogo: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#950798: marked as done (RM: leap-cli -- ROM; deprecated, no reverse-depends)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:52:45 + with message-id and subject line Bug#950798: Removed package(s) from unstable has caused the Debian Bug report #950798, regarding RM: leap-cli -- ROM; deprecated, no reverse-depends to be marked as done. This means that you claim that the

Bug#923011: marked as done (nuxwdog: FTBFS (/usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private'))

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:51:28 + with message-id and subject line Bug#950745: Removed package(s) from unstable has caused the Debian Bug report #923011, regarding nuxwdog: FTBFS (/usr/include/keyutils.h:204:48: error: expected ',' or '...' before 'private') to be marked as

Bug#951044: marked as done (Revdeps which use the typelib FTBFS: dh_girepository: error: Could not find ICalGLib-3.0.typelib dependency)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:50:16 + with message-id and subject line Bug#951044: fixed in libical3 3.0.7-2 has caused the Debian Bug report #951044, regarding Revdeps which use the typelib FTBFS: dh_girepository: error: Could not find ICalGLib-3.0.typelib dependency to be marked

Bug#947173: marked as done (debootstrap: Fails when run from path containing space character)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:49:00 + with message-id and subject line Bug#947173: fixed in debootstrap 1.0.117 has caused the Debian Bug report #947173, regarding debootstrap: Fails when run from path containing space character to be marked as done. This means that you claim that

Bug#950679: marked as done (RM: openbve-data -- RoQA; not useful without openbve (removed from Debian in 2017))

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:50:28 + with message-id and subject line Bug#950679: Removed package(s) from unstable has caused the Debian Bug report #950679, regarding RM: openbve-data -- RoQA; not useful without openbve (removed from Debian in 2017) to be marked as done. This

Bug#946815: marked as done ([debootstrap] Add script for future focal fossal Ubuntu)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:49:00 + with message-id and subject line Bug#946815: fixed in debootstrap 1.0.117 has caused the Debian Bug report #946815, regarding [debootstrap] Add script for future focal fossal Ubuntu to be marked as done. This means that you claim that the

Bug#944976: marked as done (debootstrap: please add Ubuntu focal)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:49:00 + with message-id and subject line Bug#944976: fixed in debootstrap 1.0.117 has caused the Debian Bug report #944976, regarding debootstrap: please add Ubuntu focal to be marked as done. This means that you claim that the problem has been dealt

Bug#950740: marked as done (RM: ruby-memfs -- ROM; unmaintained, no reverse dependencies)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:50:55 + with message-id and subject line Bug#950740: Removed package(s) from unstable has caused the Debian Bug report #950740, regarding RM: ruby-memfs -- ROM; unmaintained, no reverse dependencies to be marked as done. This means that you claim that

Bug#951096: marked as done (RM: ukui-indicators -- ROM; no longer in use)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 13:05:14 + with message-id and subject line Bug#951096: Removed package(s) from unstable has caused the Debian Bug report #951096, regarding RM: ukui-indicators -- ROM; no longer in use to be marked as done. This means that you claim that the problem has

Bug#943585: marked as done (kwin-x11: kwin (?) causes extreme flickering and tear on login)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 15:19:40 +0100 with message-id <3419414.9LKvrY20dy@grumly> and subject line [fixed] Re: Bug#943585: bug gone with kwin-x11 version 5.17 from experimental has caused the Debian Bug report #943585, regarding kwin-x11: kwin (?) causes extreme flickering and tear

Bug#950946: marked as done (RM: giira -- ROM; obsolete)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:57:03 + with message-id and subject line Bug#950946: Removed package(s) from unstable has caused the Debian Bug report #950946, regarding RM: giira -- ROM; obsolete to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#951021: marked as done (libmtp: switch to libusb-1.0 on hurd)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:34:10 + with message-id and subject line Bug#951021: fixed in libmtp 1.1.17-2 has caused the Debian Bug report #951021, regarding libmtp: switch to libusb-1.0 on hurd to be marked as done. This means that you claim that the problem has been dealt with.

Bug#740201: marked as done (rosegarden: Rosegarden has been built in "debug" mode)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 13:42:52 +0100 with message-id <9427bfe6-548f-4a73-8d32-f78ddfbf7...@kabelmail.de> and subject line Re: rosegarden: Rosegarden has been built in "debug" mode has caused the Debian Bug report #740201, regarding rosegarden: Rosegarden has been built in "debug"

Bug#392467: marked as done (makejail does not copy updated files into jail)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #392467, regarding makejail does not copy updated files into jail to be marked as done. This means that you claim that the problem has

Bug#763031: marked as done (makejail: userFiles and groupFiles options are not processed correctly)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #763031, regarding makejail: userFiles and groupFiles options are not processed correctly to be marked as done. This means that you

Bug#851024: marked as done (leap-cli: FTBFS: ERROR: Test "ruby2.3" failed.)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:52:53 + with message-id and subject line Bug#950798: Removed package(s) from unstable has caused the Debian Bug report #851024, regarding leap-cli: FTBFS: ERROR: Test "ruby2.3" failed. to be marked as done. This means that you claim that the problem has

Bug#950827: marked as done (RM: node-simplesmtp -- ROM; Orphaned & unmaintained)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:58 + with message-id and subject line Bug#950827: Removed package(s) from unstable has caused the Debian Bug report #950827, regarding RM: node-simplesmtp -- ROM; Orphaned & unmaintained to be marked as done. This means that you claim that the

Bug#763030: marked as done (makejail: userFiles and groupFiles options are not processed correctly)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #763030, regarding makejail: userFiles and groupFiles options are not processed correctly to be marked as done. This means that you

Bug#936984: marked as done (makejail: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #936984, regarding makejail: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#950745: marked as done (RM: nuxwdog -- ROM; obsolete)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:51:21 + with message-id and subject line Bug#950745: Removed package(s) from unstable has caused the Debian Bug report #950745, regarding RM: nuxwdog -- ROM; obsolete to be marked as done. This means that you claim that the problem has been dealt with.

Bug#570612: marked as done (Missing option to copy files to a different location inside the chroot)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #570612, regarding Missing option to copy files to a different location inside the chroot to be marked as done. This means that you

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

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:22 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #950818, regarding RM: makejail -- RoQA; unmaintained, dead upstream, depends on Python 2 to be marked as done. This means that you

Bug#570697: marked as done (fails to ldd existing binaries)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #570697, regarding fails to ldd existing binaries to be marked as done. This means that you claim that the problem has been dealt

Bug#913692: marked as done (makejail: Script accesses internal dpkg database)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #913692, regarding makejail: Script accesses internal dpkg database to be marked as done. This means that you claim that the problem

Bug#950770: marked as done (RM: swift-im -- RoQA; FTBFS, obsolete libraries, unmaintained, RC-buggy, not in testing)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:51:50 + with message-id and subject line Bug#950770: Removed package(s) from unstable has caused the Debian Bug report #950770, regarding RM: swift-im -- RoQA; FTBFS, obsolete libraries, unmaintained, RC-buggy, not in testing to be marked as done. This

Bug#680283: marked as done (makejail: packages= option is broken with 64-bit packages)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:53:35 + with message-id and subject line Bug#950818: Removed package(s) from unstable has caused the Debian Bug report #680283, regarding makejail: packages= option is broken with 64-bit packages to be marked as done. This means that you claim that the

Bug#950784: marked as done (RM: mgltools-gle -- ROM; Unmaintained, no Python2 port)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:52:19 + with message-id and subject line Bug#950784: Removed package(s) from unstable has caused the Debian Bug report #950784, regarding RM: mgltools-gle -- ROM; Unmaintained, no Python2 port to be marked as done. This means that you claim that the

Bug#937024: marked as done (mgltools-gle: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:52:26 + with message-id and subject line Bug#950784: Removed package(s) from unstable has caused the Debian Bug report #937024, regarding mgltools-gle: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#804949: marked as done (swift-im: Build slimber)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:51:56 + with message-id and subject line Bug#950770: Removed package(s) from unstable has caused the Debian Bug report #804949, regarding swift-im: Build slimber to be marked as done. This means that you claim that the problem has been dealt with. If

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

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:51:56 + with message-id and subject line Bug#950770: Removed package(s) from unstable has caused the Debian Bug report #915805, regarding Should this package be removed? to be marked as done. This means that you claim that the problem has been dealt

Bug#942146: marked as done (koji: CVE-2019-17109)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:58:11 + with message-id and subject line Bug#950958: Removed package(s) from unstable has caused the Debian Bug report #942146, regarding koji: CVE-2019-17109 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#936806: marked as done (koji: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:58:11 + with message-id and subject line Bug#950958: Removed package(s) from unstable has caused the Debian Bug report #936806, regarding koji: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#951083: marked as done (RM: python-django-gravatar2 -- ROM; Dead upstream, no reverse dependency, python2 package)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 08:01:13 -0500 with message-id <58572786.kYKGkkbFBk@l5580> and subject line Re: RM: python-django-gravatar2 -- ROM; Dead upstream, no reverse dependency, python2 package has caused the Debian Bug report #951083, regarding RM: python-django-gravatar2 -- ROM;

Bug#950958: marked as done (RM: koji -- RoQA; depends on Python 2, open security issues)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:58:04 + with message-id and subject line Bug#950958: Removed package(s) from unstable has caused the Debian Bug report #950958, regarding RM: koji -- RoQA; depends on Python 2, open security issues to be marked as done. This means that you claim that

Bug#941252: marked as done (migrate to python-requests-kerberos)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:58:11 + with message-id and subject line Bug#950958: Removed package(s) from unstable has caused the Debian Bug report #941252, regarding migrate to python-requests-kerberos to be marked as done. This means that you claim that the problem has been dealt

Bug#951017: marked as done (RM: golang-github-prometheus-tsdb -- ROM; Obsolete, integrated into prometheus main repo)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 12:58:31 + with message-id and subject line Bug#951017: Removed package(s) from unstable has caused the Debian Bug report #951017, regarding RM: golang-github-prometheus-tsdb -- ROM; Obsolete, integrated into prometheus main repo to be marked as done.

Bug#950888: marked as done (lots of entries in vmware-vmsvc-root.log "[ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name;)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 15:34:11 + with message-id and subject line Bug#950888: fixed in open-vm-tools 2:11.0.5-2 has caused the Debian Bug report #950888, regarding lots of entries in vmware-vmsvc-root.log "[ warning] [guestinfo] GuestInfoGetDiskDevice: Missing disk device name;

Processed: closing 918599

2020-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 918599 0.4.0-1 Bug #918599 [src:ruby-activerecord-nulldb-adapter] ruby-activerecord-nulldb-adapter FTBFS with rails 5.2 Marked as fixed in versions ruby-activerecord-nulldb-adapter/0.4.0-1. Bug #918599

Bug#883893: marked as done (digikam: freezing when using geolocation editor)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 17:21:14 +0100 with message-id <20200211162114.ga2...@agmartin.aq.upm.es> and subject line Re: Bug#883893: digikam: freezing when using geolocation editor has caused the Debian Bug report #883893, regarding digikam: freezing when using geolocation editor to be

Bug#941768: marked as done (open-vm-tools/10.3.10 does not compile with 4.19.0-6-amd64 on buster kernel upgrade)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 15:52:11 +0100 with message-id <36e81046-1dbf-6c40-cc5d-e8887b368...@bzed.de> and subject line closing bug has caused the Debian Bug report #941768, regarding open-vm-tools/10.3.10 does not compile with 4.19.0-6-amd64 on buster kernel upgrade to be marked as

Processed: closing 825810

2020-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 825810 Bug #825810 [open-vm-tools] After uninstall open-vm-tools in debian, the open-vm-tools version number is not 0 Bug #825812 [open-vm-tools] After uninstall open-vm-tools in debian, the open-vm-tools version number is not 0 Marked

Bug#887400: marked as done (lilv-utils is broken when naspro-bridges is installed)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 17:14:26 +0100 with message-id and subject line Re: lilv-utils is broken when naspro-bridges is installed has caused the Debian Bug report #887400, regarding lilv-utils is broken when naspro-bridges is installed to be marked as done. This means that you claim

Bug#942907: marked as done (actor-framework: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 15:04:20 + with message-id and subject line Bug#942907: fixed in actor-framework 0.16.3-0.3 has caused the Debian Bug report #942907, regarding actor-framework: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#937258: marked as done (pbsuite: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 16:00:12 + with message-id and subject line Bug#937258: fixed in pbsuite 15.8.24+dfsg-4 has caused the Debian Bug report #937258, regarding pbsuite: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#950768: marked as done (cluster3: missing Build-Depends: dh-python)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 16:00:11 + with message-id and subject line Bug#950768: fixed in cluster3 1.59+ds-1 has caused the Debian Bug report #950768, regarding cluster3: missing Build-Depends: dh-python to be marked as done. This means that you claim that the problem has been

Bug#910299: marked as done (drumgizmo hard codes location of semaphore.h)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 17:09:01 +0100 with message-id and subject line Re: drumgizmo hard codes location of semaphore.h has caused the Debian Bug report #910299, regarding drumgizmo hard codes location of semaphore.h to be marked as done. This means that you claim that the problem

Bug#912826: marked as done (clementine: please enable parallel building)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 16:49:30 + with message-id and subject line Bug#912826: fixed in clementine 1.4.0~rc1+dfsg-1 has caused the Debian Bug report #912826, regarding clementine: please enable parallel building to be marked as done. This means that you claim that the problem

Bug#949460: marked as done (openjdk-14 FTCBFS: missing build-depends and wrong tools)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 15:38:37 + with message-id and subject line Bug#949460: fixed in openjdk-14 14~36-1 has caused the Debian Bug report #949460, regarding openjdk-14 FTCBFS: missing build-depends and wrong tools to be marked as done. This means that you claim that the

Bug#942783: marked as done (openjdk-14-dbg: shares Build-IDs with openjdk-13-dbg)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 15:38:37 + with message-id and subject line Bug#942783: fixed in openjdk-14 14~36-1 has caused the Debian Bug report #942783, regarding openjdk-14-dbg: shares Build-IDs with openjdk-13-dbg to be marked as done. This means that you claim that the problem

Processed: your mail

2020-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 951060 Bug #951060 [libreoffice-writer] libreoffice-writer: Please make the package modify the user config while settings if a setting is deprecated Marked Bug as done > thanks Stopping processing here. Please contact me if you need

Bug#794337: marked as done (audacity: please include higher resolution icon (patch included))

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 19:02:38 +0100 with message-id <1ea6d252-b6a9-004a-239a-00407f2b5...@kabelmail.de> and subject line Re: audacity: please include higher resolution icon (patch included) has caused the Debian Bug report #794337, regarding audacity: please include higher

Bug#951124: marked as done (serpent: Fix __version__ for 1.30)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 18:04:39 + with message-id and subject line Bug#951124: fixed in serpent 1.30.2-1 has caused the Debian Bug report #951124, regarding serpent: Fix __version__ for 1.30 to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#939537: marked as done (ITP: vg -- tools for working with genome variation graphs)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 19:00:12 + with message-id and subject line Bug#939537: fixed in vg 1.21.0+ds2-1 has caused the Debian Bug report #939537, regarding ITP: vg -- tools for working with genome variation graphs to be marked as done. This means that you claim that the problem

Bug#949966: marked as done (libgclib-dev: getLine ABI uses off_t and thus depends on _FILE_OFFSET_BITS)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 20:11:59 + with message-id and subject line Bug#949966: fixed in libgclib 0.11.4-1~rc0 has caused the Debian Bug report #949966, regarding libgclib-dev: getLine ABI uses off_t and thus depends on _FILE_OFFSET_BITS to be marked as done. This means that you

Bug#951072: marked as done (ITP: htscodecs -- Custom compression for CRAM and others)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 20:11:58 + with message-id and subject line Bug#951072: fixed in htscodecs 0.5-1 has caused the Debian Bug report #951072, regarding ITP: htscodecs -- Custom compression for CRAM and others to be marked as done. This means that you claim that the problem

Bug#943043: marked as done (distorm3: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 21:21:52 + with message-id and subject line Bug#943043: fixed in distorm3 3.4.1-4 has caused the Debian Bug report #943043, regarding distorm3: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Processed: closing 921806

2020-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 921806 4.8.2-1 Bug #921806 [src:ruby-api-pagination] ruby-api-pagination: FTBFS (failing tests) Marked as fixed in versions ruby-api-pagination/4.8.2-1. Bug #921806 [src:ruby-api-pagination] ruby-api-pagination: FTBFS (failing tests) Marked

Bug#930925: marked as done (Persistent MySQLi connections: Missing SSL at reconnect)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 20:09:31 +0100 with message-id and subject line has caused the Debian Bug report #930925, regarding Persistent MySQLi connections: Missing SSL at reconnect to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#950969: marked as done (stringtie FTCBFS: uses the build architecture compiler as linker)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 19:50:15 + with message-id and subject line Bug#950969: fixed in stringtie 2.1.1+ds-2 has caused the Debian Bug report #950969, regarding stringtie FTCBFS: uses the build architecture compiler as linker to be marked as done. This means that you claim that

Processed: tagging 777230, closing 777230

2020-02-11 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 777230 + wontfix Bug #777230 [src:libmp3-info-perl] libmp3-info-perl: CVE-2013-6499: loading a module relative to the cwd Added tag(s) wontfix. > close 777230 Bug #777230 [src:libmp3-info-perl] libmp3-info-perl: CVE-2013-6499: loading a

Bug#951148: marked as done (RFS: par2cmdline/0.8.1-1 -- PAR 2.0 compatible file verification and repair tool)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 21:21:34 +0100 with message-id <20200211212134.614b3...@vip.jcf.pm> and subject line closing rfs has caused the Debian Bug report #951148, regarding RFS: par2cmdline/0.8.1-1 -- PAR 2.0 compatible file verification and repair tool to be marked as done. This

Bug#951165: marked as done (mmseqs2: autopkgtest regression: ./test_alignment: No such file or directory)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 22:38:56 + with message-id and subject line Bug#951165: fixed in mmseqs2 10-6d92c+ds-2 has caused the Debian Bug report #951165, regarding mmseqs2: autopkgtest regression: ./test_alignment: No such file or directory to be marked as done. This means that

Bug#943094: marked as done (gearmand: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 23:38:54 + with message-id and subject line Bug#943094: fixed in gearmand 1.1.18+ds-3.1 has caused the Debian Bug report #943094, regarding gearmand: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#949773: marked as done (ns3: unsatisfiable cross Build-Depends)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 21:50:07 + with message-id and subject line Bug#949773: fixed in ns3 3.30+dfsg-4 has caused the Debian Bug report #949773, regarding ns3: unsatisfiable cross Build-Depends to be marked as done. This means that you claim that the problem has been dealt

Bug#942922: marked as done (compass-susy-plugin: Python2 removal in sid/bullseye)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 22:05:24 + with message-id and subject line Bug#942922: fixed in compass-susy-plugin 2.2.12-1.1 has caused the Debian Bug report #942922, regarding compass-susy-plugin: Python2 removal in sid/bullseye to be marked as done. This means that you claim that

Bug#942280: marked as done (linux-image-4.19.0-6-amd64: Mouse wheel does not work)

2020-02-11 Thread Debian Bug Tracking System
Your message dated Tue, 11 Feb 2020 23:26:09 +0100 with message-id and subject line has caused the Debian Bug report #942280, regarding linux-image-4.19.0-6-amd64: Mouse wheel does not work to be marked as done. This means that you claim that the problem has been dealt with. If this is not the