Control: tag -1 + pending
Hi,
here's how I managed to reproduce this bug on a sid system:
1. install torbrowser-launcher 0.1.9-1+deb8u1
2. upgrade torbrowser-launcher to 0.2.2-1
3. upgrade torbrowser-launcher to 0.2.8-4
This seems to fix the problem:
--- a/debian/torbrowser-launcher.maintscrip
intrigeri:
> I *thought* I had fixed this bug already:
> torbrowser-launcher (0.2.5-1) unstable; urgency=medium
> […]
> * Remove obsolete conffile /etc/apparmor.d/torbrowser.start-tor-browser
> thanks to Paul Wise. (Closes: #805706)
> … but apparently I failed to get the rm_conffile line ri
Hi,
u:
> I can't reproduce this on a stable system using the latest
> torbrowser-launcher from jessie-backports.
> Did you test this on a clean installation?
A clean installation won't expose this bug: it can only happen when
one had installed a version that shipped
/etc/apparmor.d/torbrowser.st
Hi Shirish,
thanks for reporting this.
I can't reproduce this on a stable system using the latest
torbrowser-launcher from jessie-backports.
Did you test this on a clean installation?
Cheers!
u.
4 matches
Mail list logo
