From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Hilton Chain <hako@ultrarare.space>
Cc: 64637@debbugs.gnu.org
Subject: [bug#64637] [PATCH mesa-updates] gnu: libdrm: Update to 2.4.115.
Date: Tue, 25 Jul 2023 21:20:45 +0000 [thread overview]
Message-ID: <87351bk7rr.fsf@protonmail.com> (raw)
In-Reply-To: <714c3cf73b1a8152ebdf17dab36541ec8ee52883.1689401598.git.hako@ultrarare.space>
Hi,
On Sat, Jul 15, 2023 at 02:24 PM, Hilton Chain wrote:
> * gnu/packages/xdisorg.scm (libdrm): Update to 2.4.115.
> ---
> 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 1f7539764c..d1c1c48f29 100644
> --- a/gnu/packages/xdisorg.scm
> +++ b/gnu/packages/xdisorg.scm
> @@ -711,7 +711,7 @@ (define-public pixman
> (define-public libdrm
> (package
> (name "libdrm")
> - (version "2.4.114")
> + (version "2.4.115")
> (source (origin
> (method url-fetch)
> (uri (string-append
> @@ -719,7 +719,7 @@ (define-public libdrm
> version ".tar.xz"))
> (sha256
> (base32
> - "09nhk3jx3qzggl5vyii3yh4zm0npjqsbxhzvxrg2xla77a2cyj9h"))))
> + "1sv53x41c1hws8c65mavjlmjhgpwpfzhagjf3cwxpga20pzgnk2m"))))
> (build-system meson-build-system)
> (arguments
> (list #:configure-flags
>
> base-commit: 00ed2901f5171e4f9435641a91678217cae38030
Looks fine to me, just haven't applied it to mesa-updates since this
causes many more rebuilds than just mesa dependents. Let's include with
other large changes (like freetype maybe? where I want to add brotli
support).
John
next prev parent reply other threads:[~2023-07-25 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-15 6:24 [bug#64637] [PATCH mesa-updates] gnu: libdrm: Update to 2.4.115 Hilton Chain via Guix-patches via
2023-07-25 21:20 ` John Kehayias via Guix-patches via [this message]
2023-11-28 5:38 ` bug#64637: " John Kehayias 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
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=87351bk7rr.fsf@protonmail.com \
--to=guix-patches@gnu.org \
--cc=64637@debbugs.gnu.org \
--cc=hako@ultrarare.space \
--cc=john.kehayias@protonmail.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).