Bug#793987: xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0

2015-08-24 Thread Jacob Appelbaum
On 8/24/15, intrigeri intrig...@debian.org wrote:
 Hi Ben, hi Jacob,

 Ben Bailess wrote (29 Jul 2015 15:55:12 GMT) :
 I recently installed Torbirdy using the pkg xul-ext-torbirdy in order to
 have
 connection to system tor by default. When I open icedove, I do not see the

 typical green text at the bottom of the status bar stating Torbirdy
 Enabled:
 Tor... so I purged the pkg and reinstalled, with no change.

 Thanks for this bug report. It seems that Icedove 31.7 landed in
 stable and testing ~3 months ago, so I'm kinda surprised that nobody
 else reported this problem to Debian. popcon is low, but still.


I'm also surprised - I totally missed this bug though, so I'm not too surprised.

 Jake: are you aware of this problem? Is it fixed upstream in 0.1.4?

I think it is indeed fixed in 0.1.4 and it seems that Ben has confirmed it.

 Do you have time to take care of it? Or should we look into other
 options (e.g. pkg-moz-ext, as suggested a while ago, and/or the new
 pkg-privacy team)?


I don't have time in the next week or two - no.

 Also, note that torbirdy is scheduled to be removed from testing in
 a few days, due to this bug.

Oh dear - I had missed that entirely.


 I then purged the pkg again and installed from Icedove add-ons, and
 it worked as intended, [...]

 Ben: what exact version of Torbirdy did you install this way?

I think based on timing it had to be 0.1.4 if it was installed from
addons.mozilla.org.


 Let me know if I can help with anything to facilitate the package
 being updated.

 Ben: If you are knowledgeable about Debian packaging, the you'll find
 all the pointers you need there:
 https://tracker.debian.org/pkg/torbirdy

If I understand the issue, I believe we just need to upload 0.1.4 - it
is straight forward.



Bug#793987: xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0

2015-08-24 Thread intrigeri
Hi Ben, hi Jacob,

Ben Bailess wrote (29 Jul 2015 15:55:12 GMT) :
 I recently installed Torbirdy using the pkg xul-ext-torbirdy in order to have 
 connection to system tor by default. When I open icedove, I do not see the 
 typical green text at the bottom of the status bar stating Torbirdy Enabled: 
 Tor... so I purged the pkg and reinstalled, with no change.

Thanks for this bug report. It seems that Icedove 31.7 landed in
stable and testing ~3 months ago, so I'm kinda surprised that nobody
else reported this problem to Debian. popcon is low, but still.

Jake: are you aware of this problem? Is it fixed upstream in 0.1.4?
Do you have time to take care of it? Or should we look into other
options (e.g. pkg-moz-ext, as suggested a while ago, and/or the new
pkg-privacy team)?

Also, note that torbirdy is scheduled to be removed from testing in
a few days, due to this bug.

 I then purged the pkg again and installed from Icedove add-ons, and
 it worked as intended, [...]

Ben: what exact version of Torbirdy did you install this way?

 Let me know if I can help with anything to facilitate the package
 being updated.

Ben: If you are knowledgeable about Debian packaging, the you'll find
all the pointers you need there:
https://tracker.debian.org/pkg/torbirdy

Cheers,
--
intrigeri



Bug#793987: xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0

2015-08-24 Thread intrigeri
Hi,

[fully quoting because I'm adding the privacy team to recipients.]

Jacob Appelbaum wrote (24 Aug 2015 20:33:02 GMT) :
 On 8/24/15, intrigeri intrig...@debian.org wrote:
 Hi Ben, hi Jacob,

 Ben Bailess wrote (29 Jul 2015 15:55:12 GMT) :
 I recently installed Torbirdy using the pkg xul-ext-torbirdy in order to
 have
 connection to system tor by default. When I open icedove, I do not see the

 typical green text at the bottom of the status bar stating Torbirdy
 Enabled:
 Tor... so I purged the pkg and reinstalled, with no change.

 Thanks for this bug report. It seems that Icedove 31.7 landed in
 stable and testing ~3 months ago, so I'm kinda surprised that nobody
 else reported this problem to Debian. popcon is low, but still.


 I'm also surprised - I totally missed this bug though, so I'm not too 
 surprised.

 Jake: are you aware of this problem? Is it fixed upstream in 0.1.4?

 I think it is indeed fixed in 0.1.4 and it seems that Ben has confirmed it.

 Do you have time to take care of it? Or should we look into other
 options (e.g. pkg-moz-ext, as suggested a while ago, and/or the new
 pkg-privacy team)?


 I don't have time in the next week or two - no.

@Privacy team: can anyone give a hand?

 Also, note that torbirdy is scheduled to be removed from testing in
 a few days, due to this bug.

 Oh dear - I had missed that entirely.


 I then purged the pkg again and installed from Icedove add-ons, and
 it worked as intended, [...]

 Ben: what exact version of Torbirdy did you install this way?

 I think based on timing it had to be 0.1.4 if it was installed from
 addons.mozilla.org.


 Let me know if I can help with anything to facilitate the package
 being updated.

 Ben: If you are knowledgeable about Debian packaging, the you'll find
 all the pointers you need there:
 https://tracker.debian.org/pkg/torbirdy

 If I understand the issue, I believe we just need to upload 0.1.4 - it
 is straight forward.

OK, thanks a lot for the clarification!

Cheers,
-- 
intrigeri



Bug#793987: xul-ext-torbirdy: Torbirdy options not visible in Icedove 31.7.0

2015-07-29 Thread Ben Bailess
Package: xul-ext-torbirdy
Version: 0.1.3-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

I recently installed Torbirdy using the pkg xul-ext-torbirdy in order to have 
connection to system tor by default. When I open icedove, I do not see the 
typical green text at the bottom of the status bar stating Torbirdy Enabled: 
Tor... so I purged the pkg and reinstalled, with no change. I then purged the
pkg again and installed from Icedove add-ons, and it worked as intended, albeit
it uses the wrong port (9150) for Tor instead of system tor's 9050 as 
discussed in previous bug reports.

I much prefer to use the system Tor since tor for jessie/stable has been built 
with seccomp sandboxing capability while I'm not sure if Tor for TBB has.

Let me know if I can help with anything to facilitate the package being updated.

Many thanks,

Ben



-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xul-ext-torbirdy depends on:
ii  icedove  31.7.0-1~deb8u1
ii  tor  0.2.5.12-1

xul-ext-torbirdy recommends no packages.

xul-ext-torbirdy suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org