Github messages for voidlinux
 help / color / mirror / Atom feed
From: Piraty <Piraty@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: jitterentropy: update to 3.0.1.
Date: Sun, 24 Jan 2021 17:09:59 +0100	[thread overview]
Message-ID: <20210124160959.5_hT_jt2FQdcNVPyfILOK1j12ZevaqxLaaMffP580Kg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28073@inbox.vuxu.org>

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

New comment by Piraty on void-packages repository

https://github.com/void-linux/void-packages/pull/28073#issuecomment-766374451

Comment:
it is bsd OR gpl2, and since Void doesn't comply to SPDX syntax yet (https://github.com/void-linux/void-packages/issues/11240), we keep it to BSD
> Copyright (C) 2017 - 2021, Stephan Mueller <smueller@chronox.de>
> 
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions
> are met:
> 1. Redistributions of source code must retain the above copyright
>    notice, and the entire permission notice in its entirety,
>    including the disclaimer of warranties.
> 2. Redistributions in binary form must reproduce the above copyright
>    notice, this list of conditions and the following disclaimer in the
>    documentation and/or other materials provided with the distribution.
> 3. The name of the author may not be used to endorse or promote
>    products derived from this software without specific prior
>    written permission.
> 
> ALTERNATIVELY, this product may be distributed under the terms of
> the GNU General Public License, in which case the provisions of the GPL2
> are required INSTEAD OF the above restrictions.  (This clause is
> necessary due to a potential bad interaction between the GPL and
> the restrictions contained in a BSD-style copyright.)
> 
> THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED
> WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
> OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, ALL OF
> WHICH ARE HEREBY DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR BE
> LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
> CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
> OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
> BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
> LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
> USE OF THIS SOFTWARE, EVEN IF NOT ADVISED OF THE POSSIBILITY OF SUCH
> DAMAGE.

  parent reply	other threads:[~2021-01-24 16:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 10:15 [PR PATCH] " UsernameRandomlyGenerated
2021-01-21 10:29 ` [PR PATCH] [Updated] " UsernameRandomlyGenerated
2021-01-22  4:05 ` ericonr
2021-01-22  4:05 ` ericonr
2021-01-22  9:04 ` Piraty
2021-01-24 12:37 ` [PR PATCH] [Updated] " UsernameRandomlyGenerated
2021-01-24 12:40 ` UsernameRandomlyGenerated
2021-01-24 16:09 ` Piraty [this message]
2021-01-24 16:10 ` Piraty
2021-01-24 16:13 ` [PR PATCH] [Closed]: " Piraty

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=20210124160959.5_hT_jt2FQdcNVPyfILOK1j12ZevaqxLaaMffP580Kg@z \
    --to=piraty@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).