From: Marius Bakke <mbakke@fastmail.com>
To: "Rutger Helling" <rhelling@mykolab.com>,
"Ludovic Courtès" <ludo@gnu.org>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Conflict resolution (gtk, wayland)
Date: Tue, 22 May 2018 17:55:49 +0200 [thread overview]
Message-ID: <87603ffzwa.fsf@fastmail.com> (raw)
In-Reply-To: <20180522094223.16f0a370@mykolab.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
Rutger Helling <rhelling@mykolab.com> writes:
> I've created a patch to update Mesa on staging, along with removing
> wayland-egl from it. I can confirm I can still start GNOME on Wayland
> manually after rebuilding with this patch.
Excellent, thanks!
> Should I apply this to staging now? It's been two weeks since the last
> commit to staging, and a merge doesn't seem to be happening anytime
> soon.
Hydra is currently busy with 'core-updates'. In the mean time, please
queue up patches on 'staging' so we can start it as soon as core-updates
is merged. The patch LGTM!
> On an unpleasant side-note, certain things are completely broken on
> GNOME on Wayland with staging. Menus and buttons don't work anymore. I
> suspect this is because our mutter and gnome-shell packages are too old
> (3.24.x instead of 3.28.x).
Does GNOME on Wayland work on current 'master'? The only real
difference on staging (apart from this patch) is GTK+ 3.22.30, which is
fairly uneventful:
https://ftp.acc.umu.se/pub/gnome/sources/gtk+/3.22/gtk+-3.22.30.news
But perhaps they removed some other interfaces when adding xdg-shell
support?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2018-05-22 15:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-10 10:58 Conflict resolution (gtk, wayland) Pierre Neidhardt
2018-05-14 9:23 ` Ludovic Courtès
2018-05-14 10:40 ` Rutger Helling
2018-05-17 14:13 ` Ludovic Courtès
2018-05-22 7:42 ` Rutger Helling
2018-05-22 15:55 ` Marius Bakke [this message]
2018-05-22 16:22 ` Rutger Helling
2018-06-01 11:30 ` Rutger Helling
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=87603ffzwa.fsf@fastmail.com \
--to=mbakke@fastmail.com \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=rhelling@mykolab.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.
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).