From: Vagrant Cascadian <vagrant@debian.org>
To: 65588@debbugs.gnu.org
Cc: liliana.prikler@gmail.com, iyzsong@envs.net
Subject: [bug#65588] Update vcmi game to 1.3.1.
Date: Mon, 28 Aug 2023 19:19:40 -0700 [thread overview]
Message-ID: <87h6oid1z7.fsf@wireframe> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 99 bytes --]
This patch updates vcmi to 1.3.1.
Even tested it for a while, works nicely!
live well,
vagrant
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: 0001-gnu-vcmi-Update-to-1.3.1.patch --]
[-- Type: text/x-diff, Size: 1262 bytes --]
From 0cca7f73b63f645dcea30d199c227f384fa56e40 Mon Sep 17 00:00:00 2001
From: Vagrant Cascadian <vagrant@debian.org>
Date: Sun, 27 Aug 2023 19:59:35 -0700
Subject: [PATCH] gnu: vcmi: Update to 1.3.1.
* gnu/packages/games.scm (vcmi): Update to 1.3.1.
---
gnu/packages/games.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/games.scm b/gnu/packages/games.scm
index 453d742fb1..0af129b210 100644
--- a/gnu/packages/games.scm
+++ b/gnu/packages/games.scm
@@ -10973,7 +10973,7 @@ (define-public fheroes2
(define-public vcmi
(package
(name "vcmi")
- (version "1.2.1")
+ (version "1.3.1")
(source (origin
(method git-fetch)
(uri (git-reference
@@ -10982,7 +10982,7 @@ (define-public vcmi
(file-name (git-file-name name version))
(sha256
(base32
- "0f3fk1fc2wb7f2j4pxz89dzr8zjnrdh435mijia483a3bq59w7pk"))
+ "0jq84i6lxp96xkzq9mq8n2bbmincjzi39vijj9ws8i59c7xvjw5f"))
(patches (search-patches "vcmi-disable-privacy-breach.patch"))))
(build-system cmake-build-system)
(arguments
base-commit: 541b1c3e74cbb7965b7398d342882a038c893fbb
--
2.39.2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
reply other threads:[~2023-08-29 2:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87h6oid1z7.fsf@wireframe \
--to=vagrant@debian.org \
--cc=65588@debbugs.gnu.org \
--cc=iyzsong@envs.net \
--cc=liliana.prikler@gmail.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).