all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: guix-patches--- via <guix-patches@gnu.org>
To: phodina <phodina@protonmail.com>, 57608@debbugs.gnu.org
Cc: maxim.cournoyer@gmail.com, ludo@gnu.org, maximedevos@telenet.be,
	mail@brendan.scot, leo@famulari.name, kiasoc5@disroot.org,
	marius@gnu.org, h.goebel@crazy-compilers.com
Subject: [bug#57608] Upstreaming KDE Plasma and rest of packages
Date: Mon, 10 Oct 2022 13:03:25 +0000	[thread overview]
Message-ID: <8JP2Q_G5a64hRpHji47IEVTfuacYseEp-Cb4jpA1CL3kr3X9P4-RH7qwefMFO3-IM6awTDWMS079zdeuDKMj4Equ7kP1ewxj4JmLe8TE0ho=@protonmail.com> (raw)
In-Reply-To: <87ilkv67yu.fsf@gmail.com>

It's me again, with a build report of this version of patches.
This time it is very short, because there is no visible change in
state of (plasma-desktop-service-type).

The whole set of changes got built, with one irregularity.
Like previously, gnome-keyring failed in its 'check' phase.
I decided to bisect that after completing the Plasma Desktop on its
own.
I commented out both the Plasma and Gnome declarations
and bisected,
and declared installation of "gnome-keyring" package.
It kept building fine up to the git HEAD.
That was weird, so I tried bisecting the whole
(gnome-desktop-service-type).
This also built fine.
At this point, adding the (plasma-desktop-service-type) was
also fine, and now I have everything built just fine.

The commit used is "a4d236529c260d27998ee48cd969fa52bfd3d62e".

The branch used is "patch/plasma".

I have no idea why the previously failing test suddenly passed.
Should I report this weird behavior as an another issue?




  reply	other threads:[~2022-10-10 13:05 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-06  7:14 [bug#57608] Upstreaming KDE Plasma and rest of packages phodina via Guix-patches via
2022-09-19 17:50 ` phodina via Guix-patches via
2022-09-24 13:12   ` Ludovic Courtès
2022-09-24 13:15   ` Ludovic Courtès
2022-10-02 17:14     ` guix-patches--- via
2022-10-04  6:52       ` phodina via Guix-patches via
2022-10-04 11:07         ` guix-patches--- via
2022-10-04 14:01           ` phodina via Guix-patches via
2022-10-06 12:09             ` phodina via Guix-patches via
2022-10-06 18:29               ` kiasoc5 via Guix-patches via
2022-10-07 12:57                 ` phodina via Guix-patches via
2022-10-07 14:09                   ` Maxim Cournoyer
2022-10-10 13:03                     ` guix-patches--- via [this message]
2022-11-21 21:11               ` Marius Bakke
2022-11-22 10:20                 ` phodina via Guix-patches via
2022-11-22 10:56                   ` Marius Bakke
2022-12-27 21:15                     ` phodina via Guix-patches via
2022-12-28  0:48                       ` Maxim Cournoyer
2022-10-29 11:59 ` Brendan Tildesley
2022-10-29 20:32   ` guix-patches--- via
2022-10-29 23:49     ` Brendan Tildesley
2022-10-31  7:42     ` phodina via Guix-patches via
2023-09-02  4:23 ` bug#57608: " 宋文武 via Guix-patches via

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='8JP2Q_G5a64hRpHji47IEVTfuacYseEp-Cb4jpA1CL3kr3X9P4-RH7qwefMFO3-IM6awTDWMS079zdeuDKMj4Equ7kP1ewxj4JmLe8TE0ho=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=57608@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=kiasoc5@disroot.org \
    --cc=leo@famulari.name \
    --cc=ludo@gnu.org \
    --cc=mail@brendan.scot \
    --cc=marekpasnikowski@protonmail.com \
    --cc=marius@gnu.org \
    --cc=maxim.cournoyer@gmail.com \
    --cc=maximedevos@telenet.be \
    --cc=phodina@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.