all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Prikler <leo.prikler@student.tugraz.at>
To: musics@tutanota.com
Cc: 45856@debbugs.gnu.org
Subject: bug#45856: Shadowsocks issue
Date: Thu, 14 Jan 2021 19:56:58 +0100	[thread overview]
Message-ID: <6e57cf87ef99c4443af1539a4f5d75f3f68c358d.camel@student.tugraz.at> (raw)
In-Reply-To: MR-hNi0--3-2@tutanota.com

Hello musics,

I don't think that's necessarily a bug in Guix or even in shadowsocks. 
shadowsocks actually has a wiki including an example configuration [1].
To be fair, however, that configuation is not immediately usable, as
you are supposed to change both server and password to make it run.

Even if you aren't very knowledgeable on it, you should try consulting
that manual first and not Guix folk here or in IRC.  There aren't many
shadowsocks users here -- the fact, that no one noticed it was missing
OpenSSL for more than 2.5 years, speaks volumes -- or in other words,
the overlap between "people who could help you set up shadowsocks" and
"people, who use Guix" is rather small.  The reason I was able to fix
that issue, was because I know a little Python and I know how to
package stuff in Guix, not because of some higher knowledge about
shadowsocks itself.  And I only noticed, because someone (else?) was
reporting it at the time.

The fact, that shadowsocks has not seen a single commit for two years
(and only one in nearly three years) does not make it seem as if it is
still maintained upstream either.  That being said, good luck getting
it to run.

Regards,
Leo

[1] 
https://github.com/shadowsocks/shadowsocks/wiki/Configuration-via-Config-File






  reply	other threads:[~2021-01-14 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14 11:43 bug#45856: Shadowsocks issue musics--- via Bug reports for GNU Guix
2021-01-14 18:56 ` Leo Prikler [this message]
2021-01-15 11:41 ` bug#45856: musics--- via Bug reports for GNU Guix
2021-01-15 11:42 ` bug#45856: Done musics--- via Bug reports for GNU Guix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6e57cf87ef99c4443af1539a4f5d75f3f68c358d.camel@student.tugraz.at \
    --to=leo.prikler@student.tugraz.at \
    --cc=45856@debbugs.gnu.org \
    --cc=musics@tutanota.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.