From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: Re: (pre-release) [PATCH] torsocks update to 2.2.0-rc1
Date: Thu, 28 Jul 2016 09:44:21 +0000 [thread overview]
Message-ID: <8737mu5c7e.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87d1n1flqk.fsf@we.make.ritual.n0.is>
Hi,
I have this in use on Gentoo and GuixSD systems now for some time.
I know that we do not (?) package release candidate versions, but this
would fix our much older current torsocks. 2.1.x fails for some reasons,
this fixes it. There should be a release hopefully soon, otherwise I'll
ask tor-dev for it.
Could we make an exception for torsocks here, or should we stick with
2.0.0 until 2.2.0 has a version release?
> From fe94e760b8705f2972f04b565f02528a953277ae Mon Sep 17 00:00:00 2001
> From: ng0 <ng0@we.make.ritual.n0.is>
> Date: Tue, 28 Jun 2016 13:08:43 +0000
> Subject: [PATCH] gnu: torsocks: Update to 2.2.0-rc1.
>
> * gnu/packages/tor.scm (torsocks): Update to 2.2.0-rc1.
> ---
> gnu/packages/tor.scm | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/gnu/packages/tor.scm b/gnu/packages/tor.scm
> index 5155fc0..006334a 100644
> --- a/gnu/packages/tor.scm
> +++ b/gnu/packages/tor.scm
> @@ -2,6 +2,7 @@
> ;;; Copyright © 2013, 2014, 2015 Ludovic Courtès <ludo@gnu.org>
> ;;; Copyright © 2014, 2015 Mark H Weaver <mhw@netris.org>
> ;;; Copyright © 2016 Efraim Flashner <efraim@flashner.co.il>
> +;;; Copyright © 2016 ng0 <ng0@we.make.ritual.n0.is>
> ;;;
> ;;; This file is part of GNU Guix.
> ;;;
> @@ -70,16 +71,15 @@ applications based on the TCP protocol.")
> (define-public torsocks
> (package
> (name "torsocks")
> - (version "2.0.0")
> + (version "2.2.0-rc1")
> (source (origin
> - (method git-fetch)
> - (uri (git-reference
> - (url "https://git.torproject.org/torsocks.git")
> - (commit (string-append "v" version))))
> + (method url-fetch)
> + (uri (string-append "https://people.torproject.org/"
> + "~dgoulet/" name "/" name "-"
> + version ".tar.bz2"))
> (sha256
> (base32
> - "0an2q5ail9z414riyjbkjkm29504hy778j914baz2gn5hlv2cfak"))
> - (file-name (string-append name "-" version "-checkout"))
> + "184khqjzpg79vyc50q1k5i7rh8m48pjxa495clxbyyq8ihgqk4l6"))
> (patches (search-patches "torsocks-dns-test.patch"))))
> (build-system gnu-build-system)
> (arguments
> --
> 2.9.0
>
--
♥Ⓐ ng0
Current Keys: https://we.make.ritual.n0.is/ng0.txt
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-07-28 9:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 13:14 (pre-release) [PATCH] torsocks update to 2.2.0-rc1 ng0
2016-06-28 14:09 ` ng0
2016-07-28 9:44 ` ng0 [this message]
2016-07-28 13:03 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737mu5c7e.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).