From: Vagrant Cascadian <vagrant@debian.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 34365@debbugs.gnu.org
Subject: [bug#34365] [PATCH] gnu: Add python-daemon.
Date: Thu, 07 Feb 2019 03:42:29 -0800 [thread overview]
Message-ID: <87sgwz7rkq.fsf@ponder> (raw)
In-Reply-To: <874l9gexmz.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2167 bytes --]
On 2019-02-07, Ricardo Wurmus wrote:
>> * gnu/packages/python-xyz.scm (python-daemon): New variable.
>
> Thanks for the patch!
Thanks for the lightning fast review!
>> + (add-before 'check 'disable-tests
>> + (lambda _
>> + ;; FIXME: Determine why test fails
>> + (substitute* "test/test_daemon.py"
>> + (("test_detaches_process_context")
>> + "skip_test_detaches_process_context")))))))
>
> Before pushing this I’ll add a final #T to this phase. (In the past #F
> would indicate failure, but that’s on longer the case. “substitute*”
> annoyingly returns an unspecified value.)
My eyes still have trouble identifying where exactly this would
go... and #T/#F vs. #t/#f has me a bit confused for good measure!
Obviously, it'd be better to fix the test, or at least understand why it
fails...
>> + (propagated-inputs
>> + `(("python-docutils" ,python-docutils)
>> + ("python-lockfile" ,python-lockfile)
>> + ("python-setuptools" ,python-setuptools)))
>> + (native-inputs
>> + `(("python-unittest2" ,python-unittest2)
>> + ("python-testtools" ,python-testtools)
>> + ("python-testscenarios" ,python-testscenarios)
>> + ("python-mock" ,python-mock)
>> + ("python-docutils" ,python-docutils)))
>
> Docutils is both among native inputs as well as regular inputs. Is this
> intended?
I *think* it only needs to be in native-inputs; I think propagated
outputs was generated by the importer... and now that my attention is
drawn to it, I'm dubious of python-setuptools needing to be in
propagated-inputs as well. I can update it and check again later...
>> + (license (list license:asl2.0 license:gpl3+))))
>
> What does this list mean?
I guess it's best practice in Guix to make a comment when multiple
licenses are listed?
Apparently only setup.py is gpl3+, everything else is apache 2.0
licensed. That was my quick look at the code itself, and basically
confirmed by:
https://sources.debian.org/src/python-daemon/2.2.3-1/debian/copyright/
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-02-07 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 9:42 [bug#34365] [PATCH] gnu: Add python-daemon Vagrant Cascadian
2019-02-07 9:49 ` Ricardo Wurmus
2019-02-07 11:42 ` Vagrant Cascadian [this message]
2019-02-07 13:07 ` Ricardo Wurmus
2019-02-07 14:49 ` Vagrant Cascadian
2019-02-11 9:48 ` bug#34365: " Danny Milosavljevic
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=87sgwz7rkq.fsf@ponder \
--to=vagrant@debian.org \
--cc=34365@debbugs.gnu.org \
--cc=rekado@elephly.net \
/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).