Bug#899295: marked as done (python-cloudflare: Invalid address letsencrypt-de...@lists.alioth.debian.org in Uploaders: field)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 05:18:42 + with message-id and subject line Bug#899295: fixed in python-cloudflare 2.6.5-1 has caused the Debian Bug report #899295, regarding python-cloudflare: Invalid address letsencrypt-de...@lists.alioth.debian.org in Uploaders: field to be marked as

Bug#866049: marked as done (fonts-deva-extra: upgrade does not clean up obsoleted directories)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 05:03:45 + with message-id and subject line Bug#866049: fixed in fonts-deva-extra 3.0-5 has caused the Debian Bug report #866049, regarding fonts-deva-extra: upgrade does not clean up obsoleted directories to be marked as done. This means that you claim

Bug#938750: marked as done (u-msgpack-python: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 05:04:27 + with message-id and subject line Bug#938750: fixed in u-msgpack-python 2.3.0-2 has caused the Debian Bug report #938750, regarding u-msgpack-python: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem

Bug#937558: marked as done (pytest: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 05:04:16 + with message-id and subject line Bug#937558: fixed in pytest 4.6.9-3 has caused the Debian Bug report #937558, regarding pytest: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

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

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 03:05:00 + with message-id and subject line Bug#937758: fixed in python-flaky 3.6.1-3 has caused the Debian Bug report #937758, regarding python-flaky: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

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

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:44 + with message-id and subject line Bug#956645: Removed package(s) from unstable has caused the Debian Bug report #937844, regarding python-ipcalc: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#956651: marked as done (RM: backports.functools-lru-cache -- ROM; python2-only; backport of a python3.3 module; no rdeps)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:54:15 + with message-id and subject line Bug#956651: Removed package(s) from unstable has caused the Debian Bug report #956651, regarding RM: backports.functools-lru-cache -- ROM; python2-only; backport of a python3.3 module; no rdeps to be marked as

Bug#945271: marked as done (O: python-ipcalc -- Python IP subnet calculator)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:44 + with message-id and subject line Bug#956645: Removed package(s) from unstable has caused the Debian Bug report #945271, regarding O: python-ipcalc -- Python IP subnet calculator to be marked as done. This means that you claim that the problem

Bug#936179: marked as done (backports.functools-lru-cache: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:54:20 + with message-id and subject line Bug#956651: Removed package(s) from unstable has caused the Debian Bug report #936179, regarding backports.functools-lru-cache: Python2 removal in sid/bullseye to be marked as done. This means that you claim that

Bug#956622: marked as done (RM: drobo-utils -- RoQA; Depends on Python 2, dead upstream)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:51:57 + with message-id and subject line Bug#956622: Removed package(s) from unstable has caused the Debian Bug report #956622, regarding RM: drobo-utils -- RoQA; Depends on Python 2, dead upstream to be marked as done. This means that you claim that

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

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:21 + with message-id and subject line Bug#956623: Removed package(s) from unstable has caused the Debian Bug report #956623, regarding RM: ibniz -- RoQA; Depends on Python 2, dead upstream, unmaintained to be marked as done. This means that you claim

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

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:49 + with message-id and subject line Bug#956642: Removed package(s) from unstable has caused the Debian Bug report #938189, regarding python-sptest: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#956645: marked as done (RM: python-ipcalc -- RoQA; Depends on Python 2, no reverse deps, orphaned)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:37 + with message-id and subject line Bug#956645: Removed package(s) from unstable has caused the Debian Bug report #956645, regarding RM: python-ipcalc -- RoQA; Depends on Python 2, no reverse deps, orphaned to be marked as done. This means that

Bug#592010: marked as done (python-xmpp: Please, update to 0.5.0rc1)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #592010, regarding python-xmpp: Please, update to 0.5.0rc1 to be marked as done. This means that you claim that the problem has been

Bug#725005: marked as done (ibniz: minor typo in package description (s/Mainsteam/Mainstream/))

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:29 + with message-id and subject line Bug#956623: Removed package(s) from unstable has caused the Debian Bug report #725005, regarding ibniz: minor typo in package description (s/Mainsteam/Mainstream/) to be marked as done. This means that you claim

Bug#935078: marked as done (Wrong name in DroboIOctl.py)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:07 + with message-id and subject line Bug#956622: Removed package(s) from unstable has caused the Debian Bug report #935078, regarding Wrong name in DroboIOctl.py to be marked as done. This means that you claim that the problem has been dealt with.

Bug#875459: marked as done (O: python-xmpp -- Python library for communication with XMPP (Jabber) servers)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #875459, regarding O: python-xmpp -- Python library for communication with XMPP (Jabber) servers to be marked as done. This means

Bug#956644: marked as done (RM: python-xmpp -- RoQA; Depends on Python 2, dead upstream, orphaned/unmaintained)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:08 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #956644, regarding RM: python-xmpp -- RoQA; Depends on Python 2, dead upstream, orphaned/unmaintained to be marked as done. This

Bug#869906: marked as done (python-xmpp: dns resolver throws exception)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #869906, regarding python-xmpp: dns resolver throws exception to be marked as done. This means that you claim that the problem has

Bug#799453: marked as done (ibniz: building with DEB_BUILD_OPTIONS=nostrip still strips debug symbols)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:29 + with message-id and subject line Bug#956623: Removed package(s) from unstable has caused the Debian Bug report #799453, regarding ibniz: building with DEB_BUILD_OPTIONS=nostrip still strips debug symbols to be marked as done. This means that

Bug#630525: marked as done (please ignore (configuration) caches for dnspython too)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #630525, regarding please ignore (configuration) caches for dnspython too to be marked as done. This means that you claim that the

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

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #938280, regarding python-xmpp: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#943127: marked as done (ibniz: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:29 + with message-id and subject line Bug#956623: Removed package(s) from unstable has caused the Debian Bug report #943127, regarding ibniz: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been

Bug#890574: marked as done (ibniz: unused Build-Depends: perl)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:29 + with message-id and subject line Bug#956623: Removed package(s) from unstable has caused the Debian Bug report #890574, regarding ibniz: unused Build-Depends: perl to be marked as done. This means that you claim that the problem has been dealt

Bug#956642: marked as done (RM: python-sptest -- RoQA; Depends on Python 2, dead upstream, unmaintained)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:42 + with message-id and subject line Bug#956642: Removed package(s) from unstable has caused the Debian Bug report #956642, regarding RM: python-sptest -- RoQA; Depends on Python 2, dead upstream, unmaintained to be marked as done. This means that

Bug#799408: marked as done (ibniz: crashes after pressing F12 then Ctrl+s)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:29 + with message-id and subject line Bug#956623: Removed package(s) from unstable has caused the Debian Bug report #799408, regarding ibniz: crashes after pressing F12 then Ctrl+s to be marked as done. This means that you claim that the problem has

Bug#680942: marked as done (drobo-utils: Drobo reports second LUN with incorrect size)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:07 + with message-id and subject line Bug#956622: Removed package(s) from unstable has caused the Debian Bug report #680942, regarding drobo-utils: Drobo reports second LUN with incorrect size to be marked as done. This means that you claim that the

Bug#593836: marked as done (python-xmpp: control file "Recommends" section recommends twice the same package python-dnspython)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #593836, regarding python-xmpp: control file "Recommends" section recommends twice the same package python-dnspython to be marked as

Bug#887260: marked as done (drobo-utils should depend on e2fsprogs explicitly)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:07 + with message-id and subject line Bug#956622: Removed package(s) from unstable has caused the Debian Bug report #887260, regarding drobo-utils should depend on e2fsprogs explicitly to be marked as done. This means that you claim that the problem

Bug#936445: marked as done (drobo-utils: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:07 + with message-id and subject line Bug#956622: Removed package(s) from unstable has caused the Debian Bug report #936445, regarding drobo-utils: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Processed: RFS: freecdb/0.76 [QA] -- creating and reading constant databases

2020-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 956648 Bug #956648 [sponsorship-requests] RFS: freecdb/0.76 [QA] -- creating and reading constant databases Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 956648:

Bug#614830: marked as done (Fix detecting drobo device)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:07 + with message-id and subject line Bug#956622: Removed package(s) from unstable has caused the Debian Bug report #614830, regarding Fix detecting drobo device to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#585341: marked as done (python-xmpp: Python string exceptions no more allowed in Python 2.6)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #585341, regarding python-xmpp: Python string exceptions no more allowed in Python 2.6 to be marked as done. This means that you claim

Bug#782707: marked as done (python-xmpp: PLAIN Authentication error when JID and password have specific length (base64 trailing newline))

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:53:20 + with message-id and subject line Bug#956644: Removed package(s) from unstable has caused the Debian Bug report #782707, regarding python-xmpp: PLAIN Authentication error when JID and password have specific length (base64 trailing newline) to be

Bug#776114: marked as done (drobo-utils: Git directory present in source tarball)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:52:07 + with message-id and subject line Bug#956622: Removed package(s) from unstable has caused the Debian Bug report #776114, regarding drobo-utils: Git directory present in source tarball to be marked as done. This means that you claim that the

Bug#813981: marked as done (pyentropy: FTBFS: ndexError: invalid slice)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:46:52 + with message-id and subject line Bug#956603: Removed package(s) from unstable has caused the Debian Bug report #813981, regarding pyentropy: FTBFS: ndexError: invalid slice to be marked as done. This means that you claim that the problem has

Bug#953452: marked as done (O: diff-match-patch -- diff/match/patch algorithms implemented in JavaScript)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:47:59 + with message-id and subject line Bug#956618: Removed package(s) from unstable has caused the Debian Bug report #953452, regarding O: diff-match-patch -- diff/match/patch algorithms implemented in JavaScript to be marked as done. This means that

Bug#956618: marked as done (RM: diff-match-patch -- RoQA; unmaintained, lacking years behind upstream, no reverse dependencies)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:47:54 + with message-id and subject line Bug#956618: Removed package(s) from unstable has caused the Debian Bug report #956618, regarding RM: diff-match-patch -- RoQA; unmaintained, lacking years behind upstream, no reverse dependencies to be marked as

Bug#937426: marked as done (pyentropy: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:46:52 + with message-id and subject line Bug#956603: Removed package(s) from unstable has caused the Debian Bug report #937426, regarding pyentropy: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#670514: marked as done (When open a ssh session with tcsh as shell, "noise" show up in the terminal)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:47:15 + with message-id and subject line Bug#956610: Removed package(s) from unstable has caused the Debian Bug report #670514, regarding When open a ssh session with tcsh as shell, "noise" show up in the terminal to be marked as done. This means that

Bug#559205: marked as done (desktop-profiles cannot apply gconf setting correctly (mandatory and default))

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:47:15 + with message-id and subject line Bug#956610: Removed package(s) from unstable has caused the Debian Bug report #559205, regarding desktop-profiles cannot apply gconf setting correctly (mandatory and default) to be marked as done. This means

Bug#956603: marked as done (RM: pyentropy -- RoQA; Depends on Python 2, RC-buggy for a long time, no rev deps)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:46:44 + with message-id and subject line Bug#956603: Removed package(s) from unstable has caused the Debian Bug report #956603, regarding RM: pyentropy -- RoQA; Depends on Python 2, RC-buggy for a long time, no rev deps to be marked as done. This means

Bug#344030: marked as done (Profiles are not active upon logins like ssh -X)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:47:15 + with message-id and subject line Bug#956610: Removed package(s) from unstable has caused the Debian Bug report #344030, regarding Profiles are not active upon logins like ssh -X to be marked as done. This means that you claim that the problem

Bug#956610: marked as done (RM: desktop-profiles -- ROM; unused)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:47:07 + with message-id and subject line Bug#956610: Removed package(s) from unstable has caused the Debian Bug report #956610, regarding RM: desktop-profiles -- ROM; unused to be marked as done. This means that you claim that the problem has been dealt

Bug#956084: marked as done (inetutils-telnetd: CVE-2020-10188)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:34:15 + with message-id and subject line Bug#956084: fixed in inetutils 2:1.9.4-12 has caused the Debian Bug report #956084, regarding inetutils-telnetd: CVE-2020-10188 to be marked as done. This means that you claim that the problem has been dealt

Bug#951680: marked as done (inetutils-inetd)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:34:15 + with message-id and subject line Bug#951680: fixed in inetutils 2:1.9.4-12 has caused the Debian Bug report #951680, regarding inetutils-inetd to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#804766: marked as done (inetutils-inetd: please support ipv6)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 02:34:15 + with message-id and subject line Bug#804766: fixed in inetutils 2:1.9.4-12 has caused the Debian Bug report #804766, regarding inetutils-inetd: please support ipv6 to be marked as done. This means that you claim that the problem has been dealt

Processed: closing 928792

2020-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 928792 3.35.91-1 Bug #928792 [gnome-shell] Please bump dependency on gjs to >= 1.54.0 (for gnome-shell >= 3.32.1) There is no source info for the package 'gnome-shell' at version '3.35.91-1' with architecture '' Unable to make a source

Processed: closing 765696

2020-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 765696 3.20.2-2 Bug #765696 [gnome-shell] gnome-shell: Dependency on gnome-icon-theme-symbolic Marked as fixed in versions gnome-shell/3.20.2-2. Bug #765696 [gnome-shell] gnome-shell: Dependency on gnome-icon-theme-symbolic Marked Bug as

Bug#956339: marked as done (unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 23:04:37 + with message-id and subject line Bug#956339: fixed in unattended-upgrades 2.3 has caused the Debian Bug report #956339, regarding unattended-upgrades: regression: packages with conffile prompts are no longer skipped, leading to upgrade failures

Bug#952095: marked as done (xfsdump: FTBFS: gcc: fatal error: no input files)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 08:33:25 +1000 with message-id and subject line Re: xfsdump: FTBFS: gcc: fatal error: no input files has caused the Debian Bug report #952095, regarding xfsdump: FTBFS: gcc: fatal error: no input files to be marked as done. This means that you claim that the

Bug#757409: marked as done (freecdb: FTBFS with clang instead gcc)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:19:04 + with message-id and subject line Bug#757409: fixed in freecdb 0.76 has caused the Debian Bug report #757409, regarding freecdb: FTBFS with clang instead gcc to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#952098: marked as done (trigger-rally: FTBFS: SDL_image.h:27:10: fatal error: SDL.h: No such file or directory)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:19:21 + with message-id and subject line Bug#952098: fixed in libsdl2 2.0.10+dfsg1-3 has caused the Debian Bug report #952098, regarding trigger-rally: FTBFS: SDL_image.h:27:10: fatal error: SDL.h: No such file or directory to be marked as done. This

Bug#952046: marked as done (mrboom: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:19:21 + with message-id and subject line Bug#952046: fixed in libsdl2 2.0.10+dfsg1-3 has caused the Debian Bug report #952046, regarding mrboom: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory to be marked as done. This

Bug#952066: marked as done (jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:19:21 + with message-id and subject line Bug#952066: fixed in libsdl2 2.0.10+dfsg1-3 has caused the Debian Bug report #952066, regarding jag: FTBFS: SDL_mixer.h:25:10: fatal error: SDL_stdinc.h: No such file or directory to be marked as done. This

Bug#952182: marked as done (awl: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:18:47 + with message-id and subject line Bug#952182: fixed in awl 0.61-1 has caused the Debian Bug report #952182, regarding awl: FTBFS: dh_auto_test: error: make -j1 test returned exit code 2 to be marked as done. This means that you claim that the

Bug#956650: marked as done (awl: CVE-2020-11728 CVE-2020-11729)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:18:47 + with message-id and subject line Bug#956650: fixed in awl 0.61-1 has caused the Debian Bug report #956650, regarding awl: CVE-2020-11728 CVE-2020-11729 to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#951962: marked as done (fife: FTBFS: Could NOT find SDL2 (missing: SDL2_INCLUDE_DIR))

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:19:20 + with message-id and subject line Bug#951962: fixed in libsdl2 2.0.10+dfsg1-3 has caused the Debian Bug report #951962, regarding fife: FTBFS: Could NOT find SDL2 (missing: SDL2_INCLUDE_DIR) to be marked as done. This means that you claim that

Bug#951087: marked as done (libsdl2-dev: Packages that embed FindSDL2.cmake fail to find SDL2)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:19:20 + with message-id and subject line Bug#951087: fixed in libsdl2 2.0.10+dfsg1-3 has caused the Debian Bug report #951087, regarding libsdl2-dev: Packages that embed FindSDL2.cmake fail to find SDL2 to be marked as done. This means that you claim

Bug#955416: marked as done (hedgewars: FTBFS with newer SDL)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:19:21 + with message-id and subject line Bug#955416: fixed in libsdl2 2.0.10+dfsg1-3 has caused the Debian Bug report #955416, regarding hedgewars: FTBFS with newer SDL to be marked as done. This means that you claim that the problem has been dealt

Bug#956613: marked as done (lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 17:47:36 -0400 with message-id <877dyjys5j@fifthhorseman.net> and subject line Re: Bug#956613: lintian: inconsistent-appstream-metadata-license is confused when appstream metadata file is generated has caused the Debian Bug report #956613, regarding

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

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:04:29 + with message-id and subject line Bug#938256: fixed in python-webencodings 0.5.1-2 has caused the Debian Bug report #938256, regarding python-webencodings: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#937559: marked as done (pytest-expect: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:04:23 + with message-id and subject line Bug#937559: fixed in pytest-expect 1.1.0-2 has caused the Debian Bug report #937559, regarding pytest-expect: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has

Bug#936599: marked as done (genshi: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:04:06 + with message-id and subject line Bug#936599: fixed in genshi 0.7.3-2 has caused the Debian Bug report #936599, regarding genshi: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#932914: marked as done (gitlab: Increase version dependency of ruby-fog-google)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 03:19:15 +0530 with message-id <239f3210-fc03-4b1c-99c6-0d8b98e1f...@onenetbeyond.org> and subject line Closing old bug has caused the Debian Bug report #932914, regarding gitlab: Increase version dependency of ruby-fog-google to be marked as done. This means

Bug#925606: marked as done (gitlab: Fail to upgrade (error with activesupport gem))

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 03:16:07 +0530 with message-id and subject line Closing old bug has caused the Debian Bug report #925606, regarding gitlab: Fail to upgrade (error with activesupport gem) to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#925254: marked as done (gitlab: Failed to upgrade (google-api-client not installed))

2020-04-13 Thread Debian Bug Tracking System
Your message dated Tue, 14 Apr 2020 03:13:29 +0530 with message-id and subject line Closing old bug has caused the Debian Bug report #925254, regarding gitlab: Failed to upgrade (google-api-client not installed) to be marked as done. This means that you claim that the problem has been dealt

Bug#942937: marked as done (dawgdic: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:33:41 + with message-id and subject line Bug#942937: fixed in dawgdic 0.4.5-3 has caused the Debian Bug report #942937, regarding dawgdic: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

Bug#951739: marked as done (fontmatrix FTCBFS: runs cmake for the build architecture)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:34:19 + with message-id and subject line Bug#951739: fixed in fontmatrix 0.9.99-2 has caused the Debian Bug report #951739, regarding fontmatrix FTCBFS: runs cmake for the build architecture to be marked as done. This means that you claim that the

Bug#953705: marked as done (src:rust-futures: fails to migrate to testing for too long)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 22:15:20 +0100 with message-id and subject line re: src:rust-futures: fails to migrate to testing for too long has caused the Debian Bug report #953705, regarding src:rust-futures: fails to migrate to testing for too long to be marked as done. This means that

Bug#946328: marked as done (pd-bsaylor FTCBFS: strips with the wrong strip)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:05:06 + with message-id and subject line Bug#946328: fixed in pd-bsaylor 0.1-6 has caused the Debian Bug report #946328, regarding pd-bsaylor FTCBFS: strips with the wrong strip to be marked as done. This means that you claim that the problem has been

Bug#956300: marked as done (facter: FTBFS if bundler is installed)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:04:11 + with message-id and subject line Bug#956300: fixed in facter 3.11.0-4.1 has caused the Debian Bug report #956300, regarding facter: FTBFS if bundler is installed to be marked as done. This means that you claim that the problem has been dealt

Bug#956301: marked as done (facter: missing dependency on ruby)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:04:11 + with message-id and subject line Bug#956301: fixed in facter 3.11.0-4.1 has caused the Debian Bug report #956301, regarding facter: missing dependency on ruby to be marked as done. This means that you claim that the problem has been dealt with.

Bug#956043: marked as done (pd-wiimote FTCBFS: strips with the wrong strip)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:05:42 + with message-id and subject line Bug#956043: fixed in pd-wiimote 0.3.2-4 has caused the Debian Bug report #956043, regarding pd-wiimote FTCBFS: strips with the wrong strip to be marked as done. This means that you claim that the problem has been

Bug#956408: marked as done (minetest-mod-xdecor: please make the build reproducible)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:04:31 + with message-id and subject line Bug#956408: fixed in minetest-mod-xdecor 1.0+dfsg1-2 has caused the Debian Bug report #956408, regarding minetest-mod-xdecor: please make the build reproducible to be marked as done. This means that you claim

Processed: RFS: libcyaml/1.0.2-1 [ITP] -- library to read and write YAML documents (shared library)

2020-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 956601 Bug #956601 [sponsorship-requests] RFS: libcyaml/1.0.2-1 [ITP] -- library to read and write YAML documents (shared library) Marked Bug as done > stop Stopping processing here. Please contact me if you need assistance. -- 956601:

Bug#917767: marked as done (gnome-terminal outputs debug messages when started from the command line)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:51:04 +0100 with message-id <20200413205104.ga192...@espresso.pseudorandom.co.uk> and subject line Re: Bug#917767: gnome-terminal outputs debug messages when started from the command line has caused the Debian Bug report #917767, regarding gnome-terminal

Bug#948175: marked as done (pd-bassemu FTCBFS: strips with the build architecture strip)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 20:04:47 + with message-id and subject line Bug#948175: fixed in pd-bassemu 0.3-6 has caused the Debian Bug report #948175, regarding pd-bassemu FTCBFS: strips with the build architecture strip to be marked as done. This means that you claim that the

Bug#948174: marked as done (pd-beatpipe FTCBFS: strips with the wrong strip)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 20:04:52 + with message-id and subject line Bug#948174: fixed in pd-beatpipe 0.1-6 has caused the Debian Bug report #948174, regarding pd-beatpipe FTCBFS: strips with the wrong strip to be marked as done. This means that you claim that the problem has been

Bug#939097: marked as done (conway-polynomials needs to be pickled with Python 2 as long as sagemath uses Python 2)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:56:37 +0200 with message-id <929e0e5802e37e97921d5c5d80d61ddb5b77e866.ca...@gmail.com> and subject line 0.5-7 fixing this is in unstable and testing has caused the Debian Bug report #939097, regarding conway-polynomials needs to be pickled with Python 2 as

Bug#953139: marked as done (python3-jupyter-core: Sid python3-jupyter-core 4.6.3-2 Needs python3-distutils)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 21:46:59 +0200 with message-id and subject line Fixed in an upload which went into testing has caused the Debian Bug report #953139, regarding python3-jupyter-core: Sid python3-jupyter-core 4.6.3-2 Needs python3-distutils to be marked as done. This means that

Bug#956505: marked as done (Relax dependency on responders gem)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 19:19:41 + with message-id and subject line Bug#956505: fixed in open-build-service 2.9.4-3 has caused the Debian Bug report #956505, regarding Relax dependency on responders gem to be marked as done. This means that you claim that the problem has been

Bug#926198: marked as done (obs-api: Permissions and database setup should be done in maintainers scripts, not in a post-installation one)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 19:19:41 + with message-id and subject line Bug#926198: fixed in open-build-service 2.9.4-3 has caused the Debian Bug report #926198, regarding obs-api: Permissions and database setup should be done in maintainers scripts, not in a post-installation one to

Bug#956504: marked as done (Switch dependency from ruby-parser to ruby-ruby-parser)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 19:19:41 + with message-id and subject line Bug#956504: fixed in open-build-service 2.9.4-3 has caused the Debian Bug report #956504, regarding Switch dependency from ruby-parser to ruby-ruby-parser to be marked as done. This means that you claim that the

Processed: src:sleef: fails to migrate to testing for too long: FTBFS on multiple archs

2020-04-13 Thread Debian Bug Tracking System
Processing control commands: > close -1 3.4.1-2 Bug #956629 [src:sleef] src:sleef: fails to migrate to testing for too long: FTBFS on multiple archs Marked as fixed in versions sleef/3.4.1-2. Bug #956629 [src:sleef] src:sleef: fails to migrate to testing for too long: FTBFS on multiple archs

Bug#956578: marked as done (libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 18:48:46 + with message-id and subject line Bug#956578: fixed in casacore 3.2.1-5 has caused the Debian Bug report #956578, regarding libcasa-python3-4: package became uninstallable with update of libboost-python1.67.0 to be marked as done. This means

Bug#758566: marked as done (FTBFS with clang instead of gcc)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 18:49:25 + with message-id and subject line Bug#758566: fixed in paxtest 1:0.9.15-1 has caused the Debian Bug report #758566, regarding FTBFS with clang instead of gcc to be marked as done. This means that you claim that the problem has been dealt with. If

Bug#946572: marked as done (abcm2ps FTCBFS: builds for the build architecture)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 18:03:32 + with message-id and subject line Bug#946572: fixed in abcm2ps 8.14.7-0.1 has caused the Debian Bug report #946572, regarding abcm2ps FTCBFS: builds for the build architecture to be marked as done. This means that you claim that the problem has

Bug#763943: marked as done (libphonenumber: FTBFS on arm64)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 19:36:23 +0200 with message-id <0a6168c7ae25627245fb035a41b426894a3fdf74.ca...@debian.org> and subject line Re: libphonenumber: FTBFS on arm64 has caused the Debian Bug report #763943, regarding libphonenumber: FTBFS on arm64 to be marked as done. This means

Bug#956585: marked as done (openjfx: FTBFS on all making openjfx uninstallable)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 17:35:55 + with message-id and subject line Bug#956585: fixed in openjfx 11.0.7+0-2 has caused the Debian Bug report #956585, regarding openjfx: FTBFS on all making openjfx uninstallable to be marked as done. This means that you claim that the problem has

Processed: closing 915201

2020-04-13 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > close 915201 1.50+dfsg-1 Bug #915201 [espeak-ng] espeak-ng: Mbrola voices not working properly There is no source info for the package 'espeak-ng' at version '1.50+dfsg-1' with architecture '' Unable to make a source version for version

Bug#956608: marked as done (mediathekview main GUI broken: shrinked to minimum size)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 19:10:21 +0200 (CEST) with message-id <1735269417.17928.1586797821...@office.mailbox.org> and subject line has caused the Debian Bug report #956608, regarding mediathekview main GUI broken: shrinked to minimum size to be marked as done. This means that you

Bug#936973: marked as done (lxml: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 17:05:12 + with message-id and subject line Bug#936973: fixed in lxml 4.5.0-1.1 has caused the Debian Bug report #936973, regarding lxml: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt with.

Bug#867347: marked as done (balsa: please transition to gmime 3.0)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 17:03:40 + with message-id and subject line Bug#867347: fixed in balsa 2.6.0-1 has caused the Debian Bug report #867347, regarding balsa: please transition to gmime 3.0 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#956574: marked as done (josm: exception when attempting to upload "Can't find bundle for base name ch.poole.openinghoursparser.Messages")

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 16:50:17 + with message-id and subject line Bug#956574: fixed in josm 0.0.svn16239+dfsg-2 has caused the Debian Bug report #956574, regarding josm: exception when attempting to upload "Can't find bundle for base name ch.poole.openinghoursparser.Messages"

Bug#939903: marked as done (openvpn: systemd does not start openvpn after upgrade from stretch tu buster)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 18:40:31 +0200 with message-id <91cbe842571db08b35e7b3b7b927c9e3e6a0f48e.camel@jff.email> and subject line Re: openvpn: systemd does not start openvpn after upgrade from stretch tu buster has caused the Debian Bug report #939903, regarding openvpn: systemd does

Bug#803909: marked as done (Assertion `bm->bus->dma->aiocb == ((void *)0)' failed)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 19:39:12 +0300 with message-id <7be09e1a-6606-b6c7-560b-ce9f6f87a...@msgid.tls.msk.ru> and subject line Re: Assertion `bm->bus->dma->aiocb == ((void *)0)' failed has caused the Debian Bug report #803909, regarding Assertion `bm->bus->dma->aiocb == ((void *)0)'

Bug#940956: marked as done (systemd unit description worded misleadingly)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 18:30:43 +0200 with message-id <8f9c823ea86365e6ec0fc5525d7e2e8b07082fef.camel@jff.email> and subject line Re: systemd unit description worded misleadingly has caused the Debian Bug report #940956, regarding systemd unit description worded misleadingly to be

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

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 12:32:32 -0400 with message-id and subject line Re: Bug#937847 marked as pending in python-iso8601 has caused the Debian Bug report #937847, regarding python-iso8601: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the

Bug#936709: marked as done (html5lib: Python2 removal in sid/bullseye)

2020-04-13 Thread Debian Bug Tracking System
Your message dated Mon, 13 Apr 2020 16:33:40 + with message-id and subject line Bug#936709: fixed in html5lib 1.0.1-3 has caused the Debian Bug report #936709, regarding html5lib: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been dealt

  1   2   >