unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Marius Bakke <mbakke@fastmail.com>, 31958@debbugs.gnu.org
Subject: [bug#31958] [PATCH] gnu: Add python-pyblake2.
Date: Mon, 25 Jun 2018 14:07:43 -0700	[thread overview]
Message-ID: <878t72o9r4.fsf@aikidev.net> (raw)
In-Reply-To: <874lhqej9d.fsf@fastmail.com>

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

On 2018-06-25, Marius Bakke wrote:
> Vagrant Cascadian <vagrant@debian.org> writes:
>
>> Add new package definition for python-pyblake2, needed to upgrade
>> python-trezor to recent versions.
>
> Thanks!  Some comments:
>
> [...]
>
>> * gnu/packages/libusb.scm (python-pyblake2): New variable.
>> ---
>>  gnu/packages/python.scm | 19 +++++++++++++++++++
>>  1 file changed, 19 insertions(+)
>
> There is a mismatch between the commit message and the code here :-)

Oops! obvious cut-and-paste error here...


> Though I think this is better suited in 'python-crypto.scm'.  WDYT?

I'll happily defer to someone who knows their way around guix more. :)


>> +    (home-page "https://github.com/dchest/pyblake2")
>> +    (synopsis
>> +     "BLAKE2 hash function extension module")
>
> Superfluous line break.

Will fix.


>> +    (description
>> +     "BLAKE2 hash function extension module")
>
> Can you try to expand on this a little?

I can try, sure.


>> +    (license license:cc0)))
>
> According to COPYING, this software is actually "octuple-licensed":
>
> * CC0 Universal 1.0 - http://creativecommons.org/publicdomain/zero/1.0
> * Unlicense — http://unlicense.org/
> * WTFPL Version 2 - http://www.wtfpl.net/
> * Apache Public License 2.0 - https://www.apache.org/licenses/LICENSE-2.0
> * OpenSSL License - https://www.openssl.org/source/license.html
> * MIT License - https://opensource.org/licenses/MIT
> * The BSD 3-Clause License - https://opensource.org/licenses/BSD-3-Clause
> * ISC License - https://opensource.org/licenses/ISC
>
> Can you add each of these, along with an explaning comment?

And all of those are merely fallback licenses to the author's intention
of public domain... and in the files themselves (pyblake2module.c,
setup.py), they only reference:

  http://creativecommons.org/publicdomain/zero/1.0

But if it's more appropriate for guix to list all possible licenses,
sure. :)


live well,
  vagrant

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

  reply	other threads:[~2018-06-25 21:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-24 20:06 [bug#31958] [PATCH] gnu: Add python-pyblake2 Vagrant Cascadian
2018-06-25 19:52 ` Marius Bakke
2018-06-25 21:07   ` Vagrant Cascadian [this message]
2018-06-25 21:20     ` Marius Bakke
2018-06-26  4:37       ` Vagrant Cascadian
2018-06-26 21:53         ` bug#31957: " Marius Bakke

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=878t72o9r4.fsf@aikidev.net \
    --to=vagrant@debian.org \
    --cc=31958@debbugs.gnu.org \
    --cc=mbakke@fastmail.com \
    /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).