From: Kaelyn via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 49412@debbugs.gnu.org
Subject: [bug#49412] [PATCH core-updates] gnu: libdrm: Update to 2.4.107.
Date: Mon, 05 Jul 2021 15:58:24 +0000 [thread overview]
Message-ID: <5Pvsg9OZD8vKwdm4EQxqmpNKGC2KiZuZYe_EUcoTjyP7HJwIh_BR3K7AWrE0B4qvbzJE58sQivIwjMr0qXGzc0NI9dKsvFoiefvgl7qQNdA=@protonmail.com> (raw)
In-Reply-To: <d8f57dfe176e2537517a1bbb8fd71cac1f5e764f.camel@telenet.be>
On Monday, July 5th, 2021 at 11:15 AM, Maxime Devos <maximedevos@telenet.be> wrote:
> Kaelyn Takata via Guix-patches via schreef op ma 05-07-2021 om 08:43 [+0000]:
>
> > - gnu/packages/xdisorg.scm (libdrm): Update to 2.4.107, and change
> >
> > libpciaccess to a propagated input as the pkg-config for libdrm_intel now
> >
> > includes it in the libs.
> >
> > gnu/packages/xdisorg.scm | 6 +++---
> >
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/gnu/packages/xdisorg.scm b/gnu/packages/xdisorg.scm
> >
> > index d0da2d28d1..1b38149654 100644
> >
> > --- a/gnu/packages/xdisorg.scm
> >
> > +++ b/gnu/packages/xdisorg.scm
> >
> > @@ -638,7 +638,7 @@ rasterisation.")
> >
> > (define-public libdrm
> >
> > (package
> >
> > (name "libdrm")
> >
> > - (version "2.4.104")
> >
> > - (version "2.4.107")
> >
> > (source (origin
> >
> > (method url-fetch)
> >
> > (uri (string-append
> >
> > @@ -646,7 +646,7 @@ rasterisation.")
> >
> > version ".tar.xz"))
> >
> > (sha256
> >
> > (base32
> >
> > - "1jqvx9c23hgwhq109zqj6vg3ng40pcvh3r1k2fn1a424qasxhsnn"))))
> >
> >
> >
> > - "127qf1rzhaf13vdd75a58v5q34617hvangjlfnlkcdh37gqcwm65"))))
> >
> >
> > (build-system meson-build-system)
> >
> > (arguments
> >
> > `(#:configure-flags
> >
> > @@ -663,7 +663,7 @@ rasterisation.")
> >
> > (replace 'check
> >
> > (lambda _
> >
> > (invoke "meson" "test" "--timeout-multiplier" "5"))))))
>
> If you are updating "libdrm" on core-updates anyway,
>
> can you also make the following change (as a separate patch)?:
>
> (replace 'check
>
> (lambda* (#:key tests? #:allow-other-keys)
>
> (when tests?
>
> (invoke "meson" "test" "--timeout-multiplier" 5))))
>
> That should allow "guix build SOMETHING --without-tests=libdrm" to work.
I'm not familiar with the "--without-tests=" flag and mechanism, but would be happy to add a patch for it. I've only recently started using Guix and this is my first patch submission (it's a precursor patch from my attempt to update mesa to 21.1.x); should I email that patch to 49412@debbugs.gnu.org to make it part of the same issue?
Cheers,
Kaelyn
next prev parent reply other threads:[~2021-07-05 15:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 8:43 [bug#49412] [PATCH core-updates] gnu: libdrm: Update to 2.4.107 Kaelyn Takata via Guix-patches via
2021-07-05 15:15 ` Maxime Devos
2021-07-05 15:58 ` Kaelyn via Guix-patches via [this message]
2021-07-06 8:24 ` Maxime Devos
2021-07-05 21:58 ` John Kehayias via Guix-patches via
2021-07-08 3:02 ` John Kehayias via Guix-patches via
2021-07-08 15:43 ` John Kehayias via Guix-patches via
2021-07-13 16:57 ` [bug#49412] [PATCH v2] " Kaelyn Takata via Guix-patches via
2021-07-26 14:19 ` Thiago Jung Bauermann via Guix-patches via
2021-07-31 10:03 ` bug#49412: [PATCH core-updates] " Ludovic Courtès
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='5Pvsg9OZD8vKwdm4EQxqmpNKGC2KiZuZYe_EUcoTjyP7HJwIh_BR3K7AWrE0B4qvbzJE58sQivIwjMr0qXGzc0NI9dKsvFoiefvgl7qQNdA=@protonmail.com' \
--to=guix-patches@gnu.org \
--cc=49412@debbugs.gnu.org \
--cc=kaelyn.alexi@protonmail.com \
--cc=maximedevos@telenet.be \
/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.