Github messages for voidlinux
 help / color / mirror / Atom feed
From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] scryer-prolog: update to 0.9.3
Date: Sat, 04 Nov 2023 04:07:49 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47055@inbox.vuxu.org> (raw)

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

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

https://github.com/cinerea0/void-packages scryer
https://github.com/void-linux/void-packages/pull/47055

scryer-prolog: update to 0.9.3
#### Testing the changes
- I tested the changes in this PR: **YES**


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

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

From 9f3294edd398cc3c444029e0f06ef18fe983e6b3 Mon Sep 17 00:00:00 2001
From: cinerea0 <cinerea0@disroot.org>
Date: Fri, 3 Nov 2023 23:06:49 -0400
Subject: [PATCH] scryer-prolog: update to 0.9.3

---
 .../scryer-prolog/patches/update-cargo-lock.patch  | 14 ++++++++++++++
 srcpkgs/scryer-prolog/template                     |  4 ++--
 2 files changed, 16 insertions(+), 2 deletions(-)
 create mode 100644 srcpkgs/scryer-prolog/patches/update-cargo-lock.patch

diff --git a/srcpkgs/scryer-prolog/patches/update-cargo-lock.patch b/srcpkgs/scryer-prolog/patches/update-cargo-lock.patch
new file mode 100644
index 0000000000000..f039b6fa2da04
--- /dev/null
+++ b/srcpkgs/scryer-prolog/patches/update-cargo-lock.patch
@@ -0,0 +1,14 @@
+# v0.9.3 shipped with an outdated lockfile
+diff --git a/Cargo.lock b/Cargo.lock
+index f4a4952a6f4..315f61a7340 100644
+--- a/Cargo.lock
++++ b/Cargo.lock
+@@ -2032,7 +2032,7 @@ checksum = "94143f37725109f92c262ed2cf5e59bce7498c01bcc1502d7b9afe439a4e9f49"
+ 
+ [[package]]
+ name = "scryer-prolog"
+-version = "0.9.2"
++version = "0.9.3"
+ dependencies = [
+  "assert_cmd",
+  "base64 0.12.3",
diff --git a/srcpkgs/scryer-prolog/template b/srcpkgs/scryer-prolog/template
index ecd15239fdaa7..651cab92b2a10 100644
--- a/srcpkgs/scryer-prolog/template
+++ b/srcpkgs/scryer-prolog/template
@@ -1,6 +1,6 @@
 # Template file for 'scryer-prolog'
 pkgname=scryer-prolog
-version=0.9.2
+version=0.9.3
 revision=1
 build_style=cargo
 hostmakedepends="pkg-config"
@@ -10,7 +10,7 @@ maintainer="Hans-J. Schmid <knock@myopendoor.de>"
 license="BSD-3-Clause"
 homepage="https://github.com/mthom/scryer-prolog"
 distfiles="https://github.com/mthom/scryer-prolog/archive/refs/tags/v${version}.tar.gz"
-checksum=d8e89e0d6c54fdd34104513e231bba4c8499659b1dd3ae6abe187606e443a82c
+checksum=08bddb114cb377abccaf58df66e99c8cafc7af90dc2cf6ff2d8204fb6d514af4
 
 case "$XBPS_TARGET_MACHINE" in
 	x86_64*|i686*|arm*|aarch64*) ;;

             reply	other threads:[~2023-11-04  3:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04  3:07 cinerea0 [this message]
2023-11-13  3:45 ` [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-47055@inbox.vuxu.org \
    --to=cinerea0@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).