From: ng0 <contact.ng0@cryptolab.net>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add nyx.
Date: Sun, 22 Jan 2017 18:44:50 +0000 [thread overview]
Message-ID: <87fukbvsrh.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <8737gcgq4i.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> ng0 <contact.ng0@cryptolab.net> writes:
>
>> Ludovic Courtès <ludo@gnu.org> writes:
>>
>>> contact.ng0@cryptolab.net skribis:
>>>
>>>> From: ng0 <ng0@libertad.pw>
>>>>
>>>> * gnu/packages/tor.scm (nyx): New variable.
>>>
>>> I applied the changes below and then realized that it fails to build:
>>>
>>> --8<---------------cut here---------------start------------->8---
>>> starting phase `install'
>>> running install
>>> running build
>>> running build_py
>>> running install_lib
>>> creating /gnu/store/alk9r3rir93pjmv8im20f8xrvv90219z-python-3.5.2/lib/python3.5/site-packages/nyx
>>> /gnu/store/alk9r3rir93pjmv8im20f8xrvv90219z-python-3.5.2/lib/python3.5/distutils/dist.py:261: UserWarning: Unknown distribution option: 'install_requires'
>>> warnings.warn(msg)
>>> error: could not create '/gnu/store/alk9r3rir93pjmv8im20f8xrvv90219z-python-3.5.2/lib/python3.5/site-packages/nyx': Permission denied
>>> phase `install' failed after 0.9 seconds
>>> --8<---------------cut here---------------end--------------->8---
>>>
>>> Could you send an update?
>>
>> That's exactly why I have sent it. I can't make it build because
>> it requires work to be done by someone involved more in python
>> than I am.
>
> In that case please don’t include “[PATCH]” in the subject line. There
> are many patches that need to be reviewed and it’s a drain on our
> limited resources to review patches that don’t yet result in buildable
> code.
That's automatically handled by git send-email.. I can't really
control what subject the second email AFTER the cover-leter gets.
But I'm looking for a way to improve this.
Now on nyx, I will give it another try. It might take a bit
longer though.
> I consider “[PATCH]” emails as delayed commits. We all have work in
> progress and it doesn’t make sense to share it early as it just
> displaces patches that are ready for review.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> https://elephly.net
>
--
♥Ⓐ ng0 -- https://www.inventati.org/patternsinthechaos/
next prev parent reply other threads:[~2017-01-22 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 16:39 Torproject software: Nyx (previously known as ARM) contact.ng0
2017-01-18 16:39 ` [PATCH] gnu: Add nyx contact.ng0
2017-01-18 16:57 ` contact.ng0
2017-01-20 13:24 ` Ludovic Courtès
2017-01-21 12:01 ` ng0
2017-01-21 19:38 ` Ricardo Wurmus
2017-01-22 18:44 ` ng0 [this message]
2017-01-22 19:20 ` Ricardo Wurmus
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=87fukbvsrh.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=contact.ng0@cryptolab.net \
--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).