From: Jack Hill <jackhill@jackhill.us>
To: 65901@debbugs.gnu.org
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
Raghav Gururajan <rg@raghavgururajan.name>
Subject: [bug#65901] [PATCH gnome-team] gnu: vala: Update to 0.56.13.
Date: Tue, 12 Sep 2023 22:18:13 -0400 [thread overview]
Message-ID: <efd66c95c37c4a1b2901e70d4684df67e46782c5.1694571493.git.jackhill@jackhill.us> (raw)
* gnu/packages/gnome.scm (vala): Update to 0.56.13.
---
I noticed that Dino was failing to build on the gnome-team branch. It's
apparently because of some unintentional breaking changes in vala
0.56.11 and 0.56.12. This patch updates vala to 0.56.13 which restores
the previous behaviour.
https://github.com/dino/dino/issues/1479
https://gitlab.gnome.org/GNOME/vala/-/issues/1478
gnu/packages/gnome.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/gnome.scm b/gnu/packages/gnome.scm
index ad118090eb..c9a4290472 100644
--- a/gnu/packages/gnome.scm
+++ b/gnu/packages/gnome.scm
@@ -4424,7 +4424,7 @@ (define-public seahorse
(define-public vala
(package
(name "vala")
- (version "0.56.12")
+ (version "0.56.13")
(source (origin
(method url-fetch)
(uri (string-append "mirror://gnome/sources/vala/"
@@ -4432,7 +4432,7 @@ (define-public vala
"vala-" version ".tar.xz"))
(sha256
(base32
- "0n9m4l8d2n4wmgn9l5gdhnr6xl5ms7483ng5fxqak8xygi5xbjcj"))))
+ "01xfarnhpp30wmv9mwayw8751glwppl0sva79j3y9qf76qq25229"))))
(build-system glib-or-gtk-build-system)
(arguments
(list
base-commit: 20e3f3e1151b2f22ae7fb5aa8764148654f35090
--
2.41.0
next reply other threads:[~2023-09-13 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 2:18 Jack Hill [this message]
2023-09-13 15:43 ` [bug#65901] [PATCH gnome-team] gnu: vala: Update to 0.56.13 Maxim Cournoyer
2023-09-24 9:57 ` bug#65901: " Liliana Marie Prikler
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=efd66c95c37c4a1b2901e70d4684df67e46782c5.1694571493.git.jackhill@jackhill.us \
--to=jackhill@jackhill.us \
--cc=65901@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=maxim.cournoyer@gmail.com \
--cc=rg@raghavgururajan.name \
/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).