unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: phodina <phodina@protonmail.com>
Cc: "53581@debbugs.gnu.org" <53581-done@debbugs.gnu.org>
Subject: bug#53581: [PATCH 1/8] gnu: libdrm: Update to 2.4.109.
Date: Wed, 22 Jun 2022 12:41:23 +0200	[thread overview]
Message-ID: <87edzh3rqk.fsf_-_@gnu.org> (raw)
In-Reply-To: <87o7ym60qr.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 21 Jun 2022 07:31:40 +0200")

Hi,

Ludovic Courtès <ludo@gnu.org> skribis:

> phodina <phodina@protonmail.com> skribis:
>
>> could somebody have a look at the patches?
>
> It all LGTM.
>
>> FIY: I will test them on the latest core-updates as some time has pasted but recently openssl (both the 1.x.x and 3.x.x) is failing due to expired certs so I'm waiting for 21.6.2022 as the new release with fixes should come and then I'll also rebase these patches.
>
> Same here: I was going to test them and then stumbled upon that OpenSSL
> test failure.  I’ll see if we can update it or workaround the issue.

Done:

  https://issues.guix.gnu.org/56137

I pushed the whole series as a589049e141588ebcf4079116e378d60b779f6b4 on
‘core-updates’.  Note that not everything had been built by the time I
pushed, so please keep an eye on it and let me know if anything’s amiss.

Thanks and apologies for the delay!

Ludo’.




      reply	other threads:[~2022-06-22 10:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-27 11:43 [bug#53581] [PATCH 1/8] gnu: libdrm: Update to 2.4.109 phodina via Guix-patches via
     [not found] ` <handler.53581.B.164328381823472.ack@debbugs.gnu.org>
2022-04-17  2:26   ` [bug#53581] Acknowledgement ([PATCH 1/8] gnu: libdrm: Update to 2.4.109.) phodina via Guix-patches via
2022-06-20 18:42 ` [bug#53581] Ping phodina via Guix-patches via
2022-06-21  5:31   ` Ludovic Courtès
2022-06-22 10:41     ` Ludovic Courtès [this message]

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=87edzh3rqk.fsf_-_@gnu.org \
    --to=ludo@gnu.org \
    --cc=53581-done@debbugs.gnu.org \
    --cc=phodina@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).