Your message dated Mon, 06 May 2019 20:47:04 +0200 with message-id <87lfzjo1xz.fsf@manticora> and subject line Re: [Pkg-privacy-maintainers] Bug#928511: torbrowser-launcher hasn't updated itself to 60.6.2esr has caused the Debian Bug report #928511, regarding torbrowser-launcher hasn't updated itself to 60.6.2esr 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.) -- 928511: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=928511 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: torbrowser-launcher Version: 0.3.1-2 Severity: grave Dear Maintainer, I looked at #928415 and updated to firefox-esr 60.6.2esr-1 as can be seen below - $ apt-cache policy firefox-esr firefox-esr: Installed: 60.6.2esr-1 Candidate: 60.6.2esr-1 Version table: *** 60.6.2esr-1 500 500 http://cdn-fastly.deb.debian.org/debian unstable/main amd64 Packages 100 /var/lib/dpkg/status 60.6.1esr-1 990 990 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Packages I was under the impression that just updating to the newest firefox would solve the issue but it doesn't seem as simple as that. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_IN, LC_CTYPE=en_IN (charmap=UTF-8), LANGUAGE=en_IN:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages torbrowser-launcher depends on: ii ca-certificates 20190110 ii libdbus-glib-1-2 0.110-4 ii python3 3.7.2-1 ii python3-gpg 1.12.0-6 ii python3-pyqt5 5.11.3+dfsg-1+b3 ii python3-requests 2.21.0-1 ii python3-socks 1.6.8+dfsg-1 Versions of packages torbrowser-launcher recommends: ii tor 0.3.5.8-1 Versions of packages torbrowser-launcher suggests: ii apparmor 2.13.2-10 -- no debconf information -- Regards, Shirish Agarwal शिरीष अग्रवाल My quotes in this email licensed under CC 3.0 http://creativecommons.org/licenses/by-nc/3.0/ http://flossexperiences.wordpress.com E493 D466 6D67 59F5 1FD0 930F 870E 9A5B 5869 609C
--- End Message ---
--- Begin Message ---Hi, shirish शिरीष: > I also saw > https://blog.torproject.org/noscript-temporarily-disabled-tor-browser > but it doesn't indicate that a new release is supposed to be out soon. FTR this is tracked on https://trac.torproject.org/projects/tor/ticket/30388. If you want to follow the minute-by-minute progress, lurk in #tor-dev on OFTC :) The release should be out later today or tomorrow. I'm closing this bug as torbrowser-launcher is an *installer*. All it does is installing Tor Browser. It does not include Tor Browser. So bugs in Tor Browser are better tracked elsewhere. Cheers, -- intrigeri
--- End Message ---
