From: Kaelyn Takata via Guix-patches via <guix-patches@gnu.org>
To: 57914@debbugs.gnu.org
Cc: Kaelyn Takata <kaelyn.alexi@protonmail.com>
Subject: [bug#57914] [PATCH 0/2] Update weston to 10.0.02
Date: Sun, 18 Sep 2022 18:02:17 +0000 [thread overview]
Message-ID: <cover.1663523777.git.kaelyn.alexi@protonmail.com> (raw)
These two patches update weston to 10.0.2, which also fixes the build of
weston with the updated vulkan-headers on the update-vulkan-headers-staging
branch. The newer weston required a newer version of wayland-protocols,
pipewire 0.3 instead of 0.2 in the inputs, and Python 3 added to the native
inputs. I've successfully built both packages on the
update-vulkan-headers-staging and on master, along all of the packages
reported by `./pre-inst-env guix refresh -l wayland-protocols`.
Kaelyn Takata (2):
gnu: wayland-protocols: Update to 1.26.
gnu: weston: Update to 10.0.2.
gnu/packages/freedesktop.scm | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
base-commit: ce3b51a4c6bef22e35ca04a945917510627fc3a7
--
2.37.3
next reply other threads:[~2022-09-18 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-18 18:02 Kaelyn Takata via Guix-patches via [this message]
2022-09-18 18:16 ` [bug#57914] [PATCH 1/2] gnu: wayland-protocols: Update to 1.26 Kaelyn Takata via Guix-patches via
2022-09-18 18:59 ` Maxime Devos
2022-09-18 19:29 ` Kaelyn via Guix-patches via
2022-09-18 18:16 ` [bug#57914] [PATCH 2/2] gnu: weston: Update to 10.0.2 Kaelyn Takata via Guix-patches via
2022-09-18 19:34 ` [bug#57914] [PATCH v2 0/1] Update weston " Kaelyn Takata via Guix-patches via
2022-09-18 19:34 ` [bug#57914] [PATCH v2 1/1] gnu: weston: Update " Kaelyn Takata via Guix-patches via
2022-10-08 8:10 ` bug#57914: [PATCH 0/2] Update weston to 10.0.02 Ricardo Wurmus
2022-10-08 11:34 ` [bug#57914] " dan
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=cover.1663523777.git.kaelyn.alexi@protonmail.com \
--to=guix-patches@gnu.org \
--cc=57914@debbugs.gnu.org \
--cc=kaelyn.alexi@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.