Hi,
Sorry for reviving a thread from some time ago, but I thought others
might enjoy this one.
As the only workaround for now consisted of manually git cloning
repositories, no more!
Ola found out a nice workaround that's documented here:
https://github.com/agl/xmpp-client/issues/82#issuecomment-
Hi,
sycamore one:
and/or shell scripts like Coy is using
I wish there were a simple resolution to this, since hunting down
software is a pain, especially given the nuances of a Tails system;
example: svn.
A directory with every OS and the relevant install instructions seems
like the onl
intrigeri:
> What do you think should be do about it in Tails?
>
> I'm personally tempted to say: "nothing for the time being; those
> Tails users who actually use 'go get' will find ways around the
> limitations anyway;
This set unfortunately includes myself, but I would also say, that Tails
sho
Hi,
sycamore one wrote (02 Jan 2016 21:37:18 GMT) :
> Some comments about the problems of using "go get" in Tails.
> [...]
Thanks a lot for the detailed analysis.
What do you think should be do about it in Tails?
I'm personally tempted to say: "nothing for the time being; those
Tails users who a
intrigeri:
> billingscience...@ruggedinbox.com wrote (16 Sep 2015 18:30:51 GMT) :
>> > It seem that after the total removal of Polipo (Tails 1.3 and up [0]) Go's
>> > "go get" command does not work anymore in Tails ; giving "unrecognized
>> > import path" is supposedly a notice about refusing to co
On Fri, Oct 30, 2015 at 3:54 PM, wrote:
> Austin,
>
> can you write the exact command you've used? Tails 1.6?
>
> ___
> Tails-dev mailing list
> Tails-dev@boum.org
> https://mailman.boum.org/listinfo/tails-dev
> To unsubscribe from this list, send an em
Austin,
can you write the exact command you've used? Tails 1.6?
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
On Mon, Oct 12, 2015 at 10:47 AM, intrigeri wrote:
> Hi,
>
> billingscience...@ruggedinbox.com wrote (17 Sep 2015 20:25:14 GMT) :
>> Running git under torsocks under go get under torsocks fails because
>> the outer torsocks doesn't allow the inner torsocks to connect
>> to localhost.
>
> Interesti
Hi,
billingscience...@ruggedinbox.com wrote (17 Sep 2015 20:25:14 GMT) :
> Running git under torsocks under go get under torsocks fails because
> the outer torsocks doesn't allow the inner torsocks to connect
> to localhost.
Interesting statement: last time I checked, torsocks 2.x avoided
putting
torsocks probably wouldn't work as demonstrated and explained in the
github thread [1].
Quote
"WARNING torsocks[7342]: [connect] Connection to a local address are
denied since it might be a TCP DNS query to a local DNS server. Rejecting
it for safety reasons. (in tsocks_connect() at connect.c:177)
Hi,
billingscience...@ruggedinbox.com wrote (16 Sep 2015 18:30:51 GMT) :
> It seem that after the total removal of Polipo (Tails 1.3 and up [0]) Go's
> "go get" command does not work anymore in Tails ; giving "unrecognized
> import path" is supposedly a notice about refusing to connect [1].
> Doe
billingscience...@ruggedinbox.com:
> It seem that after the total removal of Polipo (Tails 1.3 and up [0]) Go's
> "go get" command does not work anymore in Tails ; giving "unrecognized
> import path" is supposedly a notice about refusing to connect [1].
>
> Does the Tails team plan to support "go
It seem that after the total removal of Polipo (Tails 1.3 and up [0]) Go's
"go get" command does not work anymore in Tails ; giving "unrecognized
import path" is supposedly a notice about refusing to connect [1].
Does the Tails team plan to support "go get" in the same way as "git
clone" [2]?
If
13 matches
Mail list logo
