From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Hilton Chain <hako@ultrarare.space>
Cc: 58351-done@debbugs.gnu.org
Subject: bug#58351: [PATCH] gnu: libxkbcommon: Update to 1.4.1.
Date: Sat, 08 Oct 2022 01:25:28 -0400 [thread overview]
Message-ID: <87zge6zy2f.fsf@gmail.com> (raw)
In-Reply-To: <y76pmf3hk7q.wl-hako@ultrarare.space> (Hilton Chain's message of "Fri, 07 Oct 2022 20:49:45 +0800")
Hello,
Hilton Chain <hako@ultrarare.space> writes:
> * gnu/packages/xdisorg.scm (libxkbcommon): Update to 1.4.1.
> ---
> gnu/packages/xdisorg.scm | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/gnu/packages/xdisorg.scm b/gnu/packages/xdisorg.scm
> index 9908f29191..8217f66584 100644
> --- a/gnu/packages/xdisorg.scm
> +++ b/gnu/packages/xdisorg.scm
> @@ -486,14 +486,14 @@ (define-public xclip
> (define-public libxkbcommon
> (package
> (name "libxkbcommon")
> - (version "1.3.0")
> + (version "1.4.1")
> (source (origin
> (method url-fetch)
> (uri (string-append "https://xkbcommon.org/download/libxkbcommon-"
> version ".tar.xz"))
> (sha256
> (base32
> - "0ysynzzgzd9jdrh1321r4bgw8wd5zljrlyn5y1a31g39xacf02bv"))))
> + "0fbb2dyjvf71p42y2jmwdcylsvj03w52f5rb23c2d00rwahhfg4l"))))
> (build-system meson-build-system)
> (inputs
> (list libx11
>
> base-commit: 9ca0f9e5a9ee0f7aaa86719cc61757734a37eee6
This would cause a mass rebuild of packages (see 'guix refresh -l
libxkbcommon'). In the future, please use the [PATCH core-updates]
prefix for such submission (git send-email --subject-prefix='PATCH
core-updates') or staging, depending on the dependent packages count.
I've applied it to core-updates, thank you!
--
Maxim
next prev parent reply other threads:[~2022-10-08 5:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 12:49 [bug#58351] [PATCH] gnu: libxkbcommon: Update to 1.4.1 Hilton Chain via Guix-patches via
2022-10-08 5:25 ` Maxim Cournoyer [this message]
2022-10-09 9:45 ` Hilton Chain 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=87zge6zy2f.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=58351-done@debbugs.gnu.org \
--cc=hako@ultrarare.space \
/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.