Github messages for voidlinux
 help / color / mirror / Atom feed
From: UsernameRandomlyGenerated <UsernameRandomlyGenerated@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] jitterentropy: update to 3.0.1.
Date: Sun, 24 Jan 2021 13:37:45 +0100	[thread overview]
Message-ID: <20210124123745.SSYdZdSnUkttbqvnmSJy5IZ_7hTerKGTZ8EAlA7KAew@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: 1650 bytes --]

There is an updated pull request by UsernameRandomlyGenerated against master on the void-packages repository

https://github.com/UsernameRandomlyGenerated/void-packages jitterentropy
https://github.com/void-linux/void-packages/pull/28073

jitterentropy: update to 3.0.1.
<!-- Mark items with [x] where applicable -->

#### General
- [ ] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [x] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->
@Piraty 


A patch file from https://github.com/void-linux/void-packages/pull/28073.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-jitterentropy-28073.patch --]
[-- Type: text/x-diff, Size: 1253 bytes --]

From e34c6dba714ce99972a20b738025c98fd14e9518 Mon Sep 17 00:00:00 2001
From: UsernameRandomlyGenerated <coredavid@tutanota.com>
Date: Thu, 21 Jan 2021 11:14:09 +0100
Subject: [PATCH] jitterentropy: add license

---
 srcpkgs/jitterentropy/template | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/jitterentropy/template b/srcpkgs/jitterentropy/template
index 746a015f9f5..ee319d1c1bf 100644
--- a/srcpkgs/jitterentropy/template
+++ b/srcpkgs/jitterentropy/template
@@ -1,15 +1,19 @@
 # Template file for 'jitterentropy'
 pkgname=jitterentropy
-version=3.0.0
+version=3.0.1
 revision=1
 wrksrc="${pkgname}-library-${version}"
 build_style=gnu-makefile
 short_desc="Hardware RNG based on CPU timing jitter"
 maintainer="Piraty <piraty1@inbox.ru>"
-license="BSD-3-Clause"
+license="BSD-3-Clause, GPL-2.0-or-later"
 homepage="https://www.chronox.de/jent.html"
 distfiles="https://github.com/smuellerDD/jitterentropy-library/archive/v${version}.tar.gz"
-checksum=e4e0e6a2ae19c8b927bb7d249c05610297c2ca8b6d4eb84ff348e8412f71d825
+checksum=015a443ebfaab7bc302caa24dcc124aefe1818046893f49591d2465bd3f58e16
+
+post_install() {
+	vlicense COPYING.bsd
+}
 
 jitterentropy-devel_package() {
 	short_desc+=" - development files"

  parent reply	other threads:[~2021-01-24 12:37 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 ` UsernameRandomlyGenerated [this message]
2021-01-24 12:40 ` UsernameRandomlyGenerated
2021-01-24 16:09 ` Piraty
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=20210124123745.SSYdZdSnUkttbqvnmSJy5IZ_7hTerKGTZ8EAlA7KAew@z \
    --to=usernamerandomlygenerated@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).