From: "宋文武 via Guix-patches via" <guix-patches@gnu.org>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>
Cc: iyzsong@member.fsf.org, 75025-done@debbugs.gnu.org,
amorenompls@gmail.com, Zhu Zihao <all_but_last@163.com>
Subject: bug#75025: [PATCH] gnu: xfce4-power-manager: Fix guix system build caused by 2e6adef5a6.
Date: Tue, 24 Dec 2024 13:12:32 +0800 [thread overview]
Message-ID: <871pxxhdfj.fsf@envs.net> (raw)
In-Reply-To: <87a5cnyz8f.fsf@envs.net> ("宋文武"'s message of "Mon, 23 Dec 2024 09:17:20 +0800")
宋文武 <iyzsong@envs.net> writes:
> Rostislav Svoboda <rostislav.svoboda@gmail.com> writes:
>
>> * gnu/packages/xfce.scm (xfce4-power-manager): Fix guix system build problem
>> introduced by 2e6adef5a6. The `guix system build` fails with 'In procedure
>> opendir: No such file or directory' for
>> /gnu/store/70x83bfg3hqvsvhfrk5fw4m57wm6sb73-xfce4-power-manager-4.20.0.
>
> Hello, I didn't meet this error, also it build successful on CI:
> https://ci.guix.gnu.org/build/7464641/details
>
> Indeed it missing polkit and panel plugin support, so I send an updated patch
> to add them.
>
> Thanks.
I had pushed the patch to add polkit and xfce-panel to inputs, but i
don't think it's the reason for the failed build you reported, which
maybe like filesystem (hardware) or parallel build issues (unlikely)...
Close this now, feel free to report again if it still fails.
prev parent reply other threads:[~2024-12-24 5:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-22 14:58 [bug#75025] [PATCH] gnu: xfce4-power-manager: Fix guix system build caused by 2e6adef5a6 Rostislav Svoboda
2024-12-23 1:13 ` [bug#75025] [PATCH] gnu: xfce4-power-manager: Enable polkit and panel plugin iyzsong--- via Guix-patches via
2024-12-23 1:17 ` [bug#75025] [PATCH] gnu: xfce4-power-manager: Fix guix system build caused by 2e6adef5a6 宋文武 via Guix-patches via
2024-12-24 5:12 ` 宋文武 via Guix-patches via [this message]
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=871pxxhdfj.fsf@envs.net \
--to=guix-patches@gnu.org \
--cc=75025-done@debbugs.gnu.org \
--cc=all_but_last@163.com \
--cc=amorenompls@gmail.com \
--cc=iyzsong@envs.net \
--cc=iyzsong@member.fsf.org \
--cc=rostislav.svoboda@gmail.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 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).