all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Nam Nguyen <namn@berkeley.edu>, 30159-done@debbugs.gnu.org
Cc: mike.rosset@gmail.com
Subject: bug#30159: [PATCH 1/2] gnu: Add deluge.
Date: Sat, 24 Nov 2018 01:56:44 +0100	[thread overview]
Message-ID: <87k1l3mgxf.fsf@fastmail.com> (raw)
In-Reply-To: <20181122081442.GB29686@antelope>

[-- Attachment #1: Type: text/plain, Size: 631 bytes --]

Nam Nguyen <namn@berkeley.edu> writes:

> Hi all,
>
> I used Mike's work to successfully write a recipe for deluge. I hope this
> is the correct place to post these patches.
>
> python2-service-identity is added so that deluge can verify TLS certificates
> with pyopenssl.

Hi Nam,

Thank you for these patches!

I've applied all three with minor changes:

* The libtorrent C++ fix was moved into libtorrent itself instead of a
  separate package.
* Dropped 'gettext' and 'setuptools' inputs from Deluge as they appeared
  unused.
* Added copyright notices for you in the relevant places.

Hope this was okay, and welcome to Guix!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2018-11-24  0:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 15:03 [bug#30159] [PATCH 1/2] gnu: Add deluge mike rosset
2018-01-18 15:03 ` [bug#30159] [PATCH 2/2] gnu: Add python2-libtorrent mike rosset
2018-01-18 19:13   ` Danny Milosavljevic
2018-01-18 16:56 ` [bug#30159] [PATCH 1/2] gnu: Add deluge Danny Milosavljevic
2018-01-30 21:09   ` Ludovic Courtès
2018-11-22  8:14 ` Nam Nguyen
2018-11-22  8:30   ` Nam Nguyen
2018-11-24  0:56   ` Marius Bakke [this message]
2018-11-24  2:25     ` Nam Nguyen
2018-11-22  9:49 ` [bug#30159] [PATCH] " Nam Nguyen
2018-11-22  9:49   ` [bug#30159] [PATCH] gnu: Add libtorrent-rasterbar-c++11 Nam Nguyen
2018-11-22  9:49   ` [bug#30159] [PATCH] gnu: Add python-service-identity Nam Nguyen

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=87k1l3mgxf.fsf@fastmail.com \
    --to=mbakke@fastmail.com \
    --cc=30159-done@debbugs.gnu.org \
    --cc=mike.rosset@gmail.com \
    --cc=namn@berkeley.edu \
    /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.