Your message dated Wed, 20 Sep 2017 21:57:38 +0900
with message-id
<CAEQ9gEkpebKevM8Xd=-1m-nx9da6g6c35vr7bca4oifuzaw...@mail.gmail.com>
and subject line Re: Bug#861744: torbrowser-launcher: Should not be part of
Stretch
has caused the Debian Bug report #861744,
regarding torbrowser-launcher: Should not be part of Stretch
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
861744: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=861744
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: torbrowser-launcher
Severity: serious
I'm opening this RC bug in order to prevent torbrowser-launcher from
migrating to testing.
Currently, the design of the software makes the package very often
unusable, as soon as TorBrowser upstream gets signed with a different
OpenPGP key or the SSL certificate of the server changes. This is not
reliable and normal users will be unable to workaround these issues
themselves.
It'll be easier and safer to provide up-to-date versions to users using
stable-backports. This shall be documented on the Debian wiki.
Cheers!
u.
signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
This pkg didn't hit stretch.
But latest release already enters stretch-bpo.
So it's safe to close this ticket.
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
--- End Message ---
