bug#53581: closed ([PATCH 1/8] gnu: libdrm: Update to 2.4.109.)

[GNU bug Tracking System]

Your message dated Wed, 22 Jun 2022 12:41:23 +0200
with message-id <87edzh3rqk.fsf_-_@gnu.org>
and subject line Re: bug#53581: [PATCH 1/8] gnu: libdrm: Update to 2.4.109.
has caused the debbugs.gnu.org bug report #53581,
regarding [PATCH 1/8] gnu: libdrm: Update to 2.4.109.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
53581: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=53581
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: [PATCH 1/8] gnu: libdrm: Update to 2.4.109. Date: Thu, 27 Jan 2022 11:43:13 +0000

Hi,

here is a patch set to update the sway window manager to latest version 1.7.

Since it updates wayland packages and libdrm is there a way how to test all the packages which are effected?

Currently I list the affected packages like this:

./pre-inst-env guix refresh --list-dependent <UPDATED PACKAGES>

I can use sed to remove the versions and also remove guix-minimal from the list

sed "s/@[-\.a-zA-Z0-9]* / /g" | sed "s/guix-minimal//g"

Finally I call the build itself

xargs ./pre-inst-env guix build

Since it touches lots of packages I expect it will go to core-updates, right? Should I mark the patches somehow (next time)?

There is package xf86-video-freedreno, but it also fails to build without the patches and by quick check the last commit is ~5yrs old.

Also should I test all the packages to build? I stopped at ungoogled-chromium as that requires a lot of resources and time.

----

Petr

0001-gnu-libdrm-Update-to-2.4.109.patch
Description: Text Data

0002-gnu-wayland-Update-to-1.20.0.patch
Description: Text Data

0006-gnu-cagebreak-Update-to-1.8.3.patch
Description: Text Data

0003-gnu-wayland-protocols-Update-to-1.24.patch
Description: Text Data

0005-gnu-sway-Update-to-1.7.patch
Description: Text Data

0008-gnu-hikari-Update-to-2.3.3.patch
Description: Text Data

0004-gnu-wlroots-Update-to-0.15.0.patch
Description: Text Data

0007-gnu-dwl-Update-to-0.2.2.patch
Description: Text Data

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#53581: [PATCH 1/8] gnu: libdrm: Update to 2.4.109.
>
>
>
>
> Date: 
>
> Wed, 22 Jun 2022 12:41:23 +0200
>
>
>
>
> User-agent: 
>
> Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux)
>
>
>
>
> 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’.
>
>
> --- End Message ---