Re: torsocks 2.0 bug

[swedebugia]

On 2016-01-29 12:28, Efraim Flashner wrote:
> On Fri, 29 Jan 2016 11:45:59 +0100
> address@hidden wrote:
>
> > Hi
> >
> > I found after reconfiguring my system lately that the update to 
> > torsocks
> > 2.0 broke this:
> >
> > $ torsocks icecat
> >
> > Which I use all the time.
> >
> > I tested with the former 2-3 versions of Icecat in my store and they 
> > all
> > fail silently. Passing debug options does not give a clue to whats
> > wrong.
>
> What type of things don't work? That update was about 2.5 months ago, 
> did you
> do all the normal things like rebooting after reconfiguring?
>
> > I tested torsocks 2.0 with youtube-dl and lynx and both work.
> >
> > I would like to patch tor.scm to have the option of installing an
> > earlier version of torsocks but dont know hot to check out the old
> > version.
> >
> > cheers swedebugia
>
> here's the patch that updated torsocks. (attached)
>
> to have your own, custom torsocks from the previous version, you could 
> add a
> file torsocks.scm, and build it with `guix build -f torsocks.scm`
>
> #:use-module ...
>
> (define-public torsocks-custom  <-- I'm not sure if this line is 
> necessary here
>   (package (inherit torsocks)
>     (name "torsocks-custom")
>     (version "1.2")
>       (source (origin
>                 (method url-fetch)
>                 (uri (string-append
> "http://torsocks.googlecode.com/files/torsocks-";
>                                    version ".tar.gz"))
>                (sha256
>                 (base32
>                  
> "1m0is5q24sf7jjlkl0icfkdc0m53nbkg0q72s57p48yp4hv7v9dy"))))
>     (arguments '())
>     (native-inputs '(()))))

Thanks for the tips.
I looked into torsocks and it seems:
* they moved to https://gitweb.torproject.org/torsocks.git
* there is a version 2.1 (from 8 months ago) here: 
https://gitweb.torproject.org/torsocks.git/commit/?id=a43a3656a5bb4391fb1654d5ff44a5257e1f165f
* 2.0 branch is a complete rewrite of 1.3 which was the last stable 
1.x-version. 
https://lists.torproject.org/pipermail/tor-dev/2013-August/005319.html

I propose: we update to 2.1 first and see if this fixes the problem with 
only icecat.

cheers
sdb