From: John Kehayias via Guix-patches via <guix-patches@gnu.org>
To: Daniel Ziltener <dziltener@lyrion.ch>
Cc: 67888@debbugs.gnu.org
Subject: [bug#67888] [PATCH] gnu: libdrm: Update to 2.4.118.
Date: Sun, 31 Dec 2023 20:09:05 +0000 [thread overview]
Message-ID: <87zfxqp21w.fsf@protonmail.com> (raw)
In-Reply-To: <a135e30556ce1852165511a0087514c9@lyrion.ch>
Hello,
On Mon, Dec 18, 2023 at 11:38 PM, Daniel Ziltener wrote:
> ---
> 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 485d55a8d3..ac2854f9e9 100644
> --- a/gnu/packages/xdisorg.scm
> +++ b/gnu/packages/xdisorg.scm
> @@ -735,7 +735,7 @@ (define-public pixman
> (define-public libdrm
> (package
> (name "libdrm")
> - (version "2.4.117")
> + (version "2.4.118")
> (source (origin
> (method url-fetch)
> (uri (string-append
> @@ -743,7 +743,7 @@ (define-public libdrm
> version ".tar.xz"))
> (sha256
> (base32
> - "0ar4c4ikcbm1s4sg09ld406izq5s1yk7b2n0mmvql77bwdlqv252"))))
> + "125bcyarlzlxfq57viyvmxy32y0561c21j46z1brrz5mya2vsxx7"))))
> (build-system meson-build-system)
> (arguments
> (list #:configure-flags
This will have to be for core-updates I think, as I saw it after the
most recent mesa-updates round. Cuirass is currently way behind on
builds so I won't be able to add this in the current branch I don't
think unless core-updates is months away.
Also, just noticed that 2.4.119 is showing up as latest version, so we
could apply a patch for that on core-updates.
John
next prev parent reply other threads:[~2023-12-31 20:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 22:38 [bug#67888] [PATCH] gnu: libdrm: Update to 2.4.118 Daniel Ziltener via Guix-patches via
2023-12-31 20:09 ` John Kehayias via Guix-patches via [this message]
2024-01-26 15:30 ` Daniel Ziltener 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=87zfxqp21w.fsf@protonmail.com \
--to=guix-patches@gnu.org \
--cc=67888@debbugs.gnu.org \
--cc=dziltener@lyrion.ch \
--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 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.