From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Streit <simon@netpanic.org>
Cc: 61042-done@debbugs.gnu.org
Subject: bug#61042: [PATCH 0/6] Upgrade spice packages
Date: Sat, 25 Feb 2023 15:06:58 -0500 [thread overview]
Message-ID: <87wn45ecgt.fsf_-_@gmail.com> (raw)
In-Reply-To: <ae85e88ed2ad3b754cbd7e95bee9b29eabd060ee.1675370158.git.simon@netpanic.org> (Simon Streit's message of "Thu, 2 Feb 2023 22:01:00 +0100")
Hi Simon,
Simon Streit <simon@netpanic.org> writes:
> * gnu/packages/spice.scm (virglrenderer): Update to 0.10.4.
> [uri]: Update source uri.
> [build-system] Change to meson-build-system.
> [inputs]: Add python; remove eudev.
> [home-page]: Update url.
> ---
> gnu/packages/spice.scm | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
>
> diff --git a/gnu/packages/spice.scm b/gnu/packages/spice.scm
> index fd0ac077ed..6eb8a4bfc7 100644
> --- a/gnu/packages/spice.scm
> +++ b/gnu/packages/spice.scm
> @@ -85,25 +85,24 @@ (define-public usbredir
> (define-public virglrenderer
> (package
> (name "virglrenderer")
> - (version "0.6.0")
> + (version "0.10.4")
> (source (origin
> (method url-fetch)
> - (uri (string-append
> - "https://www.freedesktop.org/software/virgl/"
> - "virglrenderer-" version ".tar.bz2"))
> - (patches (search-patches "virglrenderer-CVE-2017-6386.patch"))
> + (uri (string-append "https://gitlab.freedesktop.org/virgl/"
> + name "/-/archive/" version "/" name "-" version
> + ".tar.gz"))
We don't use any of the 'archive' github/gitlab links as they point to
tarballs generated on the fly, which may change subtly and invalidate
the hash. I've used git-fetch instead.
> (sha256
> (base32
> - "06kf0q4l52gzx5p63l8850hff8pmhp7xv1hk8zgx2apbw18y6jd5"))))
> - (build-system gnu-build-system)
> + "0522czb3nixkpwjknw3w1ifaj50686a2aj46v4r5cr0zh9cxqgys"))))
> + (build-system meson-build-system)
> (inputs
> - (list libepoxy mesa eudev))
> + (list libepoxy mesa python))
I move python to native-inputs, since no reference to it is kept.
> (native-inputs
> (list pkg-config))
> (synopsis "Virtual 3D GPU library")
> (description "A virtual 3D GPU library that enables a virtualized operating
> system to use the host GPU to accelerate 3D rendering.")
> - (home-page "https://virgil3d.github.io")
> + (home-page "https://gitlab.freedesktop.org/virgl/virglrenderer")
> (license (list license:expat license:bsd-3))))
Thanks for spotting the change of URI, I had missed it in my other
submission also updating spice and friends (sorry for missing that older
submission in the first place!).
Closing.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-02-25 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-24 18:44 [bug#61042] [PATCH 0/6] Upgrade spice packages Simon Streit
2023-01-24 18:48 ` [bug#61042] [PATCH 1/6] gnu: usbredir: Update to 0.13.0 Simon Streit
2023-01-24 18:48 ` [bug#61042] [PATCH 2/6] gnu: virglrenderer: Update to 0.10.4 Simon Streit
2023-01-24 18:48 ` [bug#61042] [PATCH 3/6] gnu: spice-protocol: Update to 0.14.4 Simon Streit
2023-01-24 18:48 ` [bug#61042] [PATCH 4/6] gnu: spice-gtk: Update to 0.41 Simon Streit
2023-01-24 18:48 ` [bug#61042] [PATCH 5/6] gnu: spice: Update to 0.15.1 Simon Streit
2023-01-24 18:48 ` [bug#61042] [PATCH 6/6] gnu: spice-vdagent: Update to 0.22.0 Simon Streit
2023-02-02 21:00 ` [bug#61042] [v2 0/6] Upgrade spice packages Simon Streit
2023-02-02 21:00 ` [bug#61042] [v2 1/6] gnu: usbredir: Update to 0.13.0 Simon Streit
2023-02-02 21:01 ` [bug#61042] [v2 2/6] gnu: virglrenderer: Update to 0.10.4 Simon Streit
2023-02-25 20:06 ` Maxim Cournoyer [this message]
2023-02-02 21:01 ` [bug#61042] [v2 3/6] gnu: spice-protocol: Update to 0.14.4 Simon Streit
2023-02-02 21:01 ` [bug#61042] [v2 4/6] gnu: spice-gtk: Update to 0.41 Simon Streit
2023-02-02 21:01 ` [bug#61042] [v2 5/6] gnu: spice: Update to 0.15.1 Simon Streit
2023-02-02 21:01 ` [bug#61042] [v2 6/6] gnu: spice-vdagent: Update to 0.22.0 Simon Streit
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=87wn45ecgt.fsf_-_@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=61042-done@debbugs.gnu.org \
--cc=simon@netpanic.org \
/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.