Github messages for voidlinux
 help / color / mirror / Atom feed
From: jcgruenhage <jcgruenhage@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] rusty-diceware: update to 0.3.6.
Date: Mon, 05 Sep 2022 22:22:12 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39118@inbox.vuxu.org> (raw)

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

There is a new pull request by jcgruenhage against master on the void-packages repository

https://github.com/jcgruenhage/void-packages rusty-diceware-0.3.6_1
https://github.com/void-linux/void-packages/pull/39118

rusty-diceware: update to 0.3.6.
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->
<!--
#### Local build testing
- 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
-->


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rusty-diceware-0.3.6_1-39118.patch --]
[-- Type: text/x-diff, Size: 3081 bytes --]

From f70a5c5b618725cecd53217ba4d3eb47b0732d55 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
 <jan.christian@gruenhage.xyz>
Date: Mon, 5 Sep 2022 22:20:44 +0200
Subject: [PATCH] rusty-diceware: update to 0.3.6.

---
 .../0001-Fix-values-in-test-cases.patch       | 38 -------------------
 srcpkgs/rusty-diceware/template               |  5 ++-
 2 files changed, 3 insertions(+), 40 deletions(-)
 delete mode 100644 srcpkgs/rusty-diceware/patches/0001-Fix-values-in-test-cases.patch

diff --git a/srcpkgs/rusty-diceware/patches/0001-Fix-values-in-test-cases.patch b/srcpkgs/rusty-diceware/patches/0001-Fix-values-in-test-cases.patch
deleted file mode 100644
index e9ded5de45c3..000000000000
--- a/srcpkgs/rusty-diceware/patches/0001-Fix-values-in-test-cases.patch
+++ /dev/null
@@ -1,38 +0,0 @@
-From 9f480fcbc9cb7bfb0d0bde8727dbfba9d878b596 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Jan=20Christian=20Gr=C3=BCnhage?=
- <jan.christian@gruenhage.xyz>
-Date: Sun, 4 Sep 2022 14:38:10 +0200
-Subject: [PATCH] Fix values in test cases
-
-SeedableRng values are "stable", but minor version bumps (which have
-happened since these cases were written) are allowed to change those. A
-breaking change here was documentated for 0.7.
----
- tests/tests.rs | 4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
-
-diff --git a/tests/tests.rs b/tests/tests.rs
-index d569663..ed4eff4 100644
---- a/tests/tests.rs
-+++ b/tests/tests.rs
-@@ -33,7 +33,7 @@ fn make_reinhold_vector() -> Vec<ReinholdWord> {
- 
- #[test]
- fn beale_rng_test() {
--    let wanted: Vec<BealeWord> = vec!["dr", "raced", "pvc", "moon"]
-+    let wanted: Vec<BealeWord> = vec!["io", "gavel", "beam", "time"]
-         .into_iter()
-         .map(BealeWord::new)
-         .collect();
-@@ -45,7 +45,7 @@ fn beale_rng_test() {
- 
- #[test]
- fn reinhold_rng_test() {
--    let wanted: Vec<ReinholdWord> = vec!["douse", "qo", "prune", "moan"]
-+    let wanted: Vec<ReinholdWord> = vec!["india", "gamma", "bcd", "theme"]
-         .into_iter()
-         .map(ReinholdWord::new)
-         .collect();
--- 
-2.37.3
-
diff --git a/srcpkgs/rusty-diceware/template b/srcpkgs/rusty-diceware/template
index f179e7db3eab..23fd72ffd93e 100644
--- a/srcpkgs/rusty-diceware/template
+++ b/srcpkgs/rusty-diceware/template
@@ -1,6 +1,6 @@
 # Template file for 'rusty-diceware'
 pkgname=rusty-diceware
-version=0.3.3
+version=0.3.6
 revision=1
 wrksrc="${pkgname}-v${version}"
 build_style=cargo
@@ -8,8 +8,9 @@ short_desc="Commandline diceware, sans dice, written in rustlang"
 maintainer="jcgruenhage <jan.christian@gruenhage.xyz>"
 license="AGPL-3.0-only"
 homepage="https://gitlab.com/yuvallanger/rusty-diceware"
+changelog="https://gitlab.com/yuvallanger/rusty-diceware/-/raw/master/CHANGELOG.md"
 distfiles="https://gitlab.com/yuvallanger/rusty-diceware/-/archive/v${version}/rusty-diceware-v${version}.tar.gz"
-checksum=906a082a2b85fe8d1f5db88705704f44a7b5cafcd419a2eccb29e9ccbdff9e0e
+checksum=3178f0e238ec71b76f210570c3b063d5a2b27b2b5868ac5ca4eb1d4971559f51
 
 post_install() {
 	vlicense LICENSE

             reply	other threads:[~2022-09-05 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05 20:22 jcgruenhage [this message]
2022-09-06  7:01 ` [PR PATCH] [Merged]: " classabbyamp

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39118@inbox.vuxu.org \
    --to=jcgruenhage@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).