Processing of adplay_1.8-1_source.changes

2019-10-17 Thread Debian FTP Masters
adplay_1.8-1_source.changes uploaded successfully to localhost along with the files: adplay_1.8-1.dsc adplay_1.8.orig.tar.gz adplay_1.8-1.debian.tar.xz adplay_1.8-1_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)

adplay_1.8-1_source.changes ACCEPTED into unstable

2019-10-17 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 17 Oct 2019 10:23:04 -0400 Source: adplay Architecture: source Version: 1.8-1 Distribution: unstable Urgency: medium Maintainer: Debian QA Group Changed-By: Boyuan Yang Changes: adplay (1.8-1) unstable; urgency

Bug#889573: marked as done (Project moved to github and released a newer version)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Thu, 17 Oct 2019 15:28:03 -0400 with message-id <93d820b14ecd6ddeb96b3f67bce0bb56aea583c9.ca...@debian.org> and subject line Re: Project moved to github and released a newer version has caused the Debian Bug report #889573, regarding Project moved to github and released a newer v

Bug#937200: RM opendict

2019-10-17 Thread Scott Talbert
Control: reassign -1 ftp.debian.org Control: retitle -1 RM: opendict -- RoQA; dead upstream; unmaintained; orphaned; low popcon; blocking py2 removal

Processed: RM opendict

2019-10-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 ftp.debian.org Bug #937200 [src:opendict] opendict: Python2 removal in sid/bullseye Bug reassigned from package 'src:opendict' to 'ftp.debian.org'. No longer marked as found in versions opendict/0.6.8-1. Ignoring request to alter fixed versions of bug #93

Bug#195210: marked as done (bittorrent: btdownloadgui eating memory like shit)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #195210, regarding bittorrent: btdownloadgui eating memory like shit to be marked as done. This means that you claim that the problem h

Bug#242907: marked as done (bittorrent: Can't connect to tracker when supplying DNS name with --ip)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #242907, regarding bittorrent: Can't connect to tracker when supplying DNS name with --ip to be marked as done. This means that you cla

Bug#245336: marked as done (bittorrent: Please put bittorrent configuration in /etc)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #245336, regarding bittorrent: Please put bittorrent configuration in /etc to be marked as done. This means that you claim that the pro

Bug#254293: marked as done (frequently hangs and crashes)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #254293, regarding frequently hangs and crashes to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#309904: marked as done (Exciting new bittorrent version 4.1.8 beta available)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #298814, regarding Exciting new bittorrent version 4.1.8 beta available to be marked as done. This means that you claim that the proble

Bug#237797: marked as done (bittorrent: btlaunchmany / btlaunchmanycurses strangeness)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #237797, regarding bittorrent: btlaunchmany / btlaunchmanycurses strangeness to be marked as done. This means that you claim that the p

Bug#198941: marked as done (bittorrent: downloader opens too many files and doesn't close them)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #198941, regarding bittorrent: downloader opens too many files and doesn't close them to be marked as done. This means that you claim t

Bug#365331: marked as done (bittorrent: Please package latest release 4.4.0)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #298814, regarding bittorrent: Please package latest release 4.4.0 to be marked as done. This means that you claim that the problem has

Bug#247448: marked as done (bittorrent: With UTF-8 locale btdownloadgui crashes XServer (XFree 4.3.0-7))

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #247448, regarding bittorrent: With UTF-8 locale btdownloadgui crashes XServer (XFree 4.3.0-7) to be marked as done. This means that y

Bug#568053: marked as done (bittorrent: "trouble accessing files - [Errno 24] Too many open files: ..." error.)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #198941, regarding bittorrent: "trouble accessing files - [Errno 24] Too many open files: ..." error. to be marked as done. This means

Bug#298814: marked as done (bittorrent: New upstream version available)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #298814, regarding bittorrent: New upstream version available to be marked as done. This means that you claim that the problem has been

Bug#329707: marked as done (bittorrent: New upstream version available (4.0.4))

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #298814, regarding bittorrent: New upstream version available (4.0.4) to be marked as done. This means that you claim that the problem

Bug#248196: marked as done (bittorrent: btlaunchmanycurses seems to ignore command line option)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #248196, regarding bittorrent: btlaunchmanycurses seems to ignore command line option to be marked as done. This means that you claim t

Bug#252773: marked as done (btdownloadgui: does not remember previous download location)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #252773, regarding btdownloadgui: does not remember previous download location to be marked as done. This means that you claim that the

Bug#302613: marked as done (bittorrent: New upstream version available (4.04))

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #298814, regarding bittorrent: New upstream version available (4.04) to be marked as done. This means that you claim that the problem h

Bug#364315: marked as done (bittorrent-gui: segfaults when passed a file with utf8 chars in name)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #364315, regarding bittorrent-gui: segfaults when passed a file with utf8 chars in name to be marked as done. This means that you claim

Bug#341451: marked as done (bittorrent: btdownloadgui fails to draw ui for >4gig torrent)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #341451, regarding bittorrent: btdownloadgui fails to draw ui for >4gig torrent to be marked as done. This means that you claim that th

Bug#471810: marked as done (bittorrent: btdownloadmany ignores command line option)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #471810, regarding bittorrent: btdownloadmany ignores command line option to be marked as done. This means that you claim that the prob

Bug#451696: marked as done (bittorrent: Please include a doc-base registration file)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #451696, regarding bittorrent: Please include a doc-base registration file to be marked as done. This means that you claim that the pro

Bug#343247: marked as done (mandb: warning: /usr/share/man/man1/btcompletedirgui.1.gz is a dangling symlink (sarge version))

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #343247, regarding mandb: warning: /usr/share/man/man1/btcompletedirgui.1.gz is a dangling symlink (sarge version) to be marked as done

Bug#465808: marked as done (bittorrent-gui: needlessly alarming vague usage in prompt: "replace" & "overwrite")

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #465808, regarding bittorrent-gui: needlessly alarming vague usage in prompt: "replace" & "overwrite" to be marked as done. This mean

Bug#364313: marked as done (bittornado-gui: fails to download torrent - cannot cope with non-ascii bytes ?)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #364313, regarding bittornado-gui: fails to download torrent - cannot cope with non-ascii bytes ? to be marked as done. This means tha

Bug#346495: marked as done (bittorrent-gui: does not grok non-ascii chars)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #346495, regarding bittorrent-gui: does not grok non-ascii chars to be marked as done. This means that you claim that the problem has b

Bug#389002: marked as done (please use utf-8 to draw nicer display)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #389002, regarding please use utf-8 to draw nicer display to be marked as done. This means that you claim that the problem has been dea

Bug#376998: marked as done (btmakemetafile is not option-compatible with bittornado)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #376998, regarding btmakemetafile is not option-compatible with bittornado to be marked as done. This means that you claim that the pro

Bug#482478: marked as done (bittorrent: btlaunchmany checks all files at once which hits the system hard)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #482478, regarding bittorrent: btlaunchmany checks all files at once which hits the system hard to be marked as done. This means that

Bug#511181: marked as done (bittorrent: bad data from tracker - error without details from btdownloadcurses)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #511181, regarding bittorrent: bad data from tracker - error without details from btdownloadcurses to be marked as done. This means th

Bug#481276: marked as done (bittorrent: Is trying to connect on random ports)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #481276, regarding bittorrent: Is trying to connect on random ports to be marked as done. This means that you claim that the problem ha

Bug#589479: marked as done (DeprecationWarning: the sha module is deprecated; use the hashlib module instead)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #589479, regarding DeprecationWarning: the sha module is deprecated; use the hashlib module instead to be marked as done. This means t

Bug#466274: marked as done (bittorrent: check to see if file is a torrent before reading it in to memory)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #466274, regarding bittorrent: check to see if file is a torrent before reading it in to memory to be marked as done. This means that

Bug#478758: marked as done (/usr/bin/btlaunchmany.bittorrent: btlaunchmany stops reading dir, responding to ^C after a connect fails)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #478758, regarding /usr/bin/btlaunchmany.bittorrent: btlaunchmany stops reading dir, responding to ^C after a connect fails to be marke

Bug#568054: marked as done (bittorrent: "trouble accessing files - [Errno 24] Too many open files: ..." error.)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #568054, regarding bittorrent: "trouble accessing files - [Errno 24] Too many open files: ..." error. to be marked as done. This means

Bug#705378: marked as done (bittorrent: --allowed_dir should support recursion)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #705378, regarding bittorrent: --allowed_dir should support recursion to be marked as done. This means that you claim that the problem

Bug#698804: marked as done (bittorrent: update-alternatives error)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #698804, regarding bittorrent: update-alternatives error to be marked as done. This means that you claim that the problem has been deal

Bug#488900: marked as done (bittorrent: Patch for four bugs)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #488900, regarding bittorrent: Patch for four bugs to be marked as done. This means that you claim that the problem has been dealt with

Bug#543273: marked as done (bittorrent: does not handle announce url which already contains server variable)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #543273, regarding bittorrent: does not handle announce url which already contains server variable to be marked as done. This means th

Bug#730409: marked as done (bittorrent: Add IPv6 support)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #730409, regarding bittorrent: Add IPv6 support to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#638194: marked as done (bittorrent: Problem connecting to tracker - )

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #638194, regarding bittorrent: Problem connecting to tracker - to be marked as done. This means that you claim that the problem has be

Bug#550229: marked as done (bittorrent leave obsolete init.d script after upgrade)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #550229, regarding bittorrent leave obsolete init.d script after upgrade to be marked as done. This means that you claim that the probl

Bug#728327: marked as done (OSError: [Errno 2] No such file or directory: '--minport')

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #728327, regarding OSError: [Errno 2] No such file or directory: '--minport' to be marked as done. This means that you claim that the p

Bug#482746: marked as done (bittorrent: Patch to add a global maxium upload cap)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #482746, regarding bittorrent: Patch to add a global maxium upload cap to be marked as done. This means that you claim that the problem

Bug#910132: marked as done (bittorrent-gui: bittorrent error (+ no autobugreport))

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #910132, regarding bittorrent-gui: bittorrent error (+ no autobugreport) to be marked as done. This means that you claim that the probl

Bug#638145: marked as done (bittorrent: Should Operate as a Background System Service)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #638145, regarding bittorrent: Should Operate as a Background System Service to be marked as done. This means that you claim that the p

Bug#733449: marked as done (bittorrent-gui: Program icon doesn't appear in menu.)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #733449, regarding bittorrent-gui: Program icon doesn't appear in menu. to be marked as done. This means that you claim that the proble

Bug#648333: marked as done (bittorrent: Should this package be orphaned (or removed)?)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:23:38 + with message-id and subject line Bug#936210: Removed package(s) from unstable has caused the Debian Bug report #648333, regarding bittorrent: Should this package be orphaned (or removed)? to be marked as done. This means that you claim that the p

Bug#938446: marked as done (sclapp: Python2 removal in sid/bullseye)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:30:05 + with message-id and subject line Bug#942327: Removed package(s) from unstable has caused the Debian Bug report #938446, regarding sclapp: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has been de

Bug#938825: marked as done (wifi-radar: Python2 removal in sid/bullseye)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:30:48 + with message-id and subject line Bug#942347: Removed package(s) from unstable has caused the Debian Bug report #938825, regarding wifi-radar: Python2 removal in sid/bullseye to be marked as done. This means that you claim that the problem has bee

Bug#488027: marked as done ([wifi-radar] WEP authentication doesn't work)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:30:48 + with message-id and subject line Bug#942347: Removed package(s) from unstable has caused the Debian Bug report #488027, regarding [wifi-radar] WEP authentication doesn't work to be marked as done. This means that you claim that the problem has be

Bug#510844: marked as done (wifi-radar doesn't allow wep key 2,3 or 4)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:30:48 + with message-id and subject line Bug#942347: Removed package(s) from unstable has caused the Debian Bug report #510844, regarding wifi-radar doesn't allow wep key 2,3 or 4 to be marked as done. This means that you claim that the problem has been

Bug#666739: marked as done (libnss-lwres: README.Debian wrongly says lwresd not started by default in Debian)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:11 + with message-id and subject line Bug#942500: Removed package(s) from unstable has caused the Debian Bug report #666739, regarding libnss-lwres: README.Debian wrongly says lwresd not started by default in Debian to be marked as done. This means t

Bug#888500: marked as done (libnss-lwres: Recommends lwresd, yet this package do not exist (it is virtual). Maybe recommend (or depend) on bind9?)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:11 + with message-id and subject line Bug#942500: Removed package(s) from unstable has caused the Debian Bug report #888500, regarding libnss-lwres: Recommends lwresd, yet this package do not exist (it is virtual). Maybe recommend (or depend) on bind9

Bug#936210: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: bittorrent | 3.4.2-12 | source, all bittorrent-gui | 3.4.2-12 | all python-bittorrent | 3.4.2-12 | all --- Reason --- RoQA; unmaintained; orphaned for

Bug#920659: marked as done (caffe-cuda: Fails to find the right cuda driver: "CUDA driver version is insufficient for CUDA runtime version")

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:37:24 + with message-id and subject line Bug#942484: Removed package(s) from unstable has caused the Debian Bug report #920659, regarding caffe-cuda: Fails to find the right cuda driver: "CUDA driver version is insufficient for CUDA runtime version" to b

Bug#198562: marked as done (bhl: no tabs, ie no lists etc)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #198562, regarding bhl: no tabs, ie no lists etc to be marked as done. This means that you claim that the problem has been dealt with.

Bug#922570: marked as done (FTBFS against opencv 4.0.1 (exp))

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:37:24 + with message-id and subject line Bug#942484: Removed package(s) from unstable has caused the Debian Bug report #922570, regarding FTBFS against opencv 4.0.1 (exp) to be marked as done. This means that you claim that the problem has been dealt wit

Bug#318250: marked as done (bhl: adds a spurious column to some tables)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #318250, regarding bhl: adds a spurious column to some tables to be marked as done. This means that you claim that the problem has been

Bug#340734: marked as done (bhl: there is a new version available)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #340734, regarding bhl: there is a new version available to be marked as done. This means that you claim that the problem has been deal

Bug#446169: marked as done (Confused by filenames with newlines)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #446169, regarding Confused by filenames with newlines to be marked as done. This means that you claim that the problem has been dealt

Bug#231194: marked as done (both no-init-file option and no-site-file option should be used when byte-compiling emacs-lisp sources)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #231194, regarding both no-init-file option and no-site-file option should be used when byte-compiling emacs-lisp sources to be marked

Bug#339444: marked as done (bhl: offline conversion tools are missing)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #339444, regarding bhl: offline conversion tools are missing to be marked as done. This means that you claim that the problem has been

Bug#406310: marked as done (bhl: documentation bug)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #406310, regarding bhl: documentation bug to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#942347: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
Version: 2.0.s08+dfsg-2+rm Dear submitter, as the package wifi-radar has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942

Bug#942327: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
Version: 0.5.3-3+rm Dear submitter, as the package sclapp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942327 The ve

Bug#942327: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: python-sclapp |0.5.3-3 | all sclapp |0.5.3-3 | source --- Reason --- RoQA; orphaned; dead upstream; no Python 3 support and no reverse deps

Bug#942347: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: wifi-radar | 2.0.s08+dfsg-2 | source, all --- Reason --- RoQA; orphaned, dead upstream, depends on legacy libs -

Bug#942484: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: caffe-contrib | 1.0.0+git20180821.99bd997-4 | source caffe-cuda | 1.0.0+git20180821.99bd997-4 | amd64 caffe-tools-cuda | 1.0.0+git20180821.99bd997-4 | amd64 libcaffe-cuda-dev | 1.0.0+git201

Bug#942484: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
Version: 1.0.0+git20180821.99bd997-4+rm Dear submitter, as the package caffe-contrib has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bug

Bug#942500: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
Version: 0.93-7+rm Dear submitter, as the package libnss-lwres has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942500 T

Bug#942509: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
Version: 1.7.3-3+rm Dear submitter, as the package bhl has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/942509 The versi

Bug#942500: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: libnss-lwres | 0.93-7 | source libnss-lwres | 0.93-7+b3 | arm64, mips64el, ppc64el libnss-lwres | 0.93-7+b4 | amd64, armel, armhf, i386, s390x libnss-lwres | 0.93-7+b5 | mipsel

Bug#942509: Removed package(s) from unstable

2019-10-17 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: bhl |1.7.3-3 | source, all --- Reason --- RoQA; RoQA: orphaned, buggy, low popcon -- Note that the p

Bug#668681: marked as done (bhl: help mode access to source code)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #668681, regarding bhl: help mode access to source code to be marked as done. This means that you claim that the problem has been dealt

Bug#669319: marked as done (bhl: visiting .bhl after --remove)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #669319, regarding bhl: visiting .bhl after --remove to be marked as done. This means that you claim that the problem has been dealt wi

Bug#845324: marked as done (FTBFS: /bin/sh: 1: emacs: not found)

2019-10-17 Thread Debian Bug Tracking System
Your message dated Fri, 18 Oct 2019 04:38:40 + with message-id and subject line Bug#942509: Removed package(s) from unstable has caused the Debian Bug report #845324, regarding FTBFS: /bin/sh: 1: emacs: not found to be marked as done. This means that you claim that the problem has been dealt