unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: 34365@debbugs.gnu.org
Subject: [bug#34365] [PATCH] gnu: Add python-daemon.
Date: Thu, 07 Feb 2019 10:49:40 +0100	[thread overview]
Message-ID: <874l9gexmz.fsf@elephly.net> (raw)
In-Reply-To: <87va1w6iki.fsf@ponder>


Hi Vagrant,

> * gnu/packages/python-xyz.scm (python-daemon): New variable.

Thanks for the patch!

> +         (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.)

> +    (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?

> +    (license (list license:asl2.0 license:gpl3+))))

What does this list mean?

-- 
Ricardo

  reply	other threads:[~2019-02-08  5:37 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 [this message]
2019-02-07 11:42   ` Vagrant Cascadian
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=874l9gexmz.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=34365@debbugs.gnu.org \
    --cc=vagrant@debian.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).