From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Vivien Kraus <vivien@planete-kraus.eu>
Cc: rg@raghavgururajan.name, liliana.prikler@gmail.com,
67421@debbugs.gnu.org
Subject: [bug#67421] [PATCH gnome-team] gnu: libgee: Update to 0.20.6.
Date: Sun, 03 Dec 2023 20:09:10 -0500 [thread overview]
Message-ID: <87zfyqu62x.fsf@gmail.com> (raw)
In-Reply-To: <3487d4df148b0a36820272e3dfa7d2d1e61f7b00.1700781654.git.vivien@planete-kraus.eu> (Vivien Kraus's message of "Fri, 24 Nov 2023 00:20:12 +0100")
Hi,
Vivien Kraus <vivien@planete-kraus.eu> writes:
> * gnu/packages/gnome.scm (libgee): Update to 0.20.6.
>
> Change-Id: I102a31bb7b6bbeed340b14b5fd35b8f2e34c1ac9
> ---
> 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 194a443484..cc558a2738 100644
> --- a/gnu/packages/gnome.scm
> +++ b/gnu/packages/gnome.scm
> @@ -7400,7 +7400,7 @@ (define-public yelp-tools
> (define-public libgee
> (package
> (name "libgee")
> - (version "0.20.5")
> + (version "0.20.6")
> (source (origin
> (method url-fetch)
> (uri (string-append "mirror://gnome/sources/libgee/"
> @@ -7408,7 +7408,7 @@ (define-public libgee
> "libgee-" version ".tar.xz"))
> (sha256
> (base32
> - "060mbj6ihca315a6wqj47mfzm2881azwm5bl0vwjg9ymay4km1ii"))))
> + "0kbd8y70dd5q40i8gxzvhxkn9niqvp0x6knp4ihwqq0dw7sk9y0v"))))
> (build-system gnu-build-system)
> (arguments
> (list
>
> base-commit: 60db3a6b3f6e4d1bd751d04b7d9ad1e894febf93
Reviewed-by: Maxim Cournoyer <maxim.cournoyer@gmail.com>
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-12-04 1:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-23 23:20 [bug#67421] [PATCH gnome-team] gnu: libgee: Update to 0.20.6 Vivien Kraus via Guix-patches via
2023-12-04 1:09 ` Maxim Cournoyer [this message]
2023-12-05 17:42 ` bug#67421: Applied, closing Vivien Kraus via Guix-patches via
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=87zfyqu62x.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=67421@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=rg@raghavgururajan.name \
--cc=vivien@planete-kraus.eu \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.