Your message dated Sun, 17 Jun 2018 19:01:09 +0100
with message-id <1529258469.2082.28.ca...@adam-barratt.org.uk>
and subject line Re: Bug#884571: [Pkg-privacy-maintainers] Bug#884571: RM:
torbrowser-launcher/0.1.9-1+deb8u3
has caused the Debian Bug report #884571,
regarding RM: torbrowser-launcher/0.1.9-1+deb8u3
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.)
--
884571: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884571
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: rm
The old version of torbrowser-launcher cannot work properly anymore,
because it uses the embedded old key.
That's also the reason why it also missed the stretch release [0].
People want to use it in oldstable(jessie) should consider sloppy
backports [1].
So please kindly help to remove torbrowser-launcher/0.1.9-1+deb8u3.
Thank you!
[0] https://bugs.debian.org/861744
[1] https://wiki.debian.org/TorBrowser#Debian_8_.22Jessie.22
Cheers,
--
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1
--- End Message ---
--- Begin Message ---
On Wed, 2018-06-13 at 21:50 +0100, Adam D. Barratt wrote:
> On Sat, 2018-02-24 at 14:03 +0100, intrigeri wrote:
> > Adam D. Barratt:
> > > # Broken Depends:
> > > onionshare/contrib: onionshare
> >
> > So I guess Jessie should first get the fix we applied to onionshare
> > in
> > testing/sid, i.e. move torbrowser-launcher to Recommends.
>
> Ping?
>
Nothing further happened, and we've frozen for the final jessie point
release, so I'm closing this request now.
Regards,
Adam
--- End Message ---
