From: Tom Zander via Guix-patches via <guix-patches@gnu.org>
To: 40791@debbugs.gnu.org, Marius Bakke <mbakke@fastmail.com>
Subject: [bug#40791] Append: KDE upgrade
Date: Sat, 02 May 2020 22:02:06 +0200 [thread overview]
Message-ID: <5410741.DvuYhMxLoT@cherry> (raw)
In-Reply-To: <87imhe2yx2.fsf@devup.no>
The kwayland issue looks like a missing dependency. Likely something that is
an input but not a propagated input up the stack.
A little tricky as I don't see any 'wayland-client' package.
I postponed upgrading kwayland for now so the rest of the kde upgrades can
continue.
Would it be wise to open a new bug for the KDE upgrade, especially since it
can be applied on master?
On zaterdag 2 mei 2020 16:29:13 CEST Marius Bakke wrote:
> Tom via Guix-patches via <guix-patches@gnu.org> writes:
> > I ran the script and fixed several build failures.
> >
> > Notable failure is kwayland in cmake configure step.
> > I have no idea why.
> >
> > Would like some assist there.
>
> I wonder if these KDE updates can be applied on the current master
> branch (without the Qt upgrade)? Does the same error occur then?
>
> If it works on 'master', let's merge this first.
>
> Meanwhile, please adjust the commit message to mention all the changed
> variables, [arguments], etc.
>
> I will have a deeper look in a couple of days. Thanks!
--
Tom Zander
next prev parent reply other threads:[~2020-05-02 20:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 11:05 [bug#40791] Update Qt Tom via Guix-patches via
2020-04-23 18:51 ` [bug#40791] rebased patch Tom via Guix-patches via
2020-04-23 22:23 ` Marius Bakke
2020-04-24 19:09 ` Tom via Guix-patches via
2020-04-24 20:42 ` [bug#40791] todays patch Tom via Guix-patches via
2020-05-02 14:23 ` Marius Bakke
2020-05-17 23:37 ` bug#40791: " Marius Bakke
2020-04-24 22:31 ` [bug#40791] Append: KDE upgrade Tom via Guix-patches via
2020-05-02 14:28 ` Marius Bakke
2020-05-02 14:29 ` Marius Bakke
2020-05-02 20:02 ` Tom Zander via Guix-patches via [this message]
2020-05-17 23:26 ` Marius Bakke
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=5410741.DvuYhMxLoT@cherry \
--to=guix-patches@gnu.org \
--cc=40791@debbugs.gnu.org \
--cc=mbakke@fastmail.com \
--cc=tomz@freedommail.ch \
/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).