From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 73428@debbugs.gnu.org, julian@flake.de
Cc: Julian Flake <flake@uni-koblenz.de>
Subject: bug#73428: update elogind to 255
Date: Tue, 24 Sep 2024 08:59:02 +0000 [thread overview]
Message-ID: <31D4D07F-F706-4B12-BAE6-56E71EFF21EC@tobias.gr> (raw)
In-Reply-To: <87cykurq2a.fsf@flake.de>
Hi Julian,
On 23 September 2024 21:58:46 UTC, Julian Flake <julian@flake.de> wrote:
>I don't know, how to test this from a local git worktree of guix. I can
>install it from my local worktree into my ~/.guix-profile
However you're installing it from your local checkout should also work for reconfiguring your system, e.g., with ./pre-inst-env.
If it doesn't, you need to make sure that your privilege escalation mechanisb (sudo?) isn't clobbering your environment (guix shell?).
Kind regards,
T G-R
Sent on the go. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2024-09-24 9:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-22 18:50 bug#73428: update elogind to 255 Julian Flake
2024-09-23 21:43 ` bug#73428: [PATCH] elogind update to 252.24 Julian Flake
2024-09-23 21:58 ` bug#73428: update elogind to 255 Julian Flake
2024-09-24 8:59 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2024-09-24 9:02 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2024-09-24 10:34 ` Julian Flake
2024-09-24 19:29 ` Julian Flake
2024-09-24 5:18 ` bug#73428: [PATCH v2 0/2] removed reference to deleted patch Julian Flake
2024-09-24 5:18 ` bug#73428: [PATCH v2 1/2] gnu: elogind update to 252.24 Julian Flake
2024-09-24 5:18 ` bug#73428: [PATCH v2 2/2] gnu: elogind: Remove unneeded rpath patch Julian Flake
2024-09-24 5:37 ` bug#73428: update elogind to 255 Julian Flake
[not found] ` <87bk045089.fsf@gnu.org>
2024-09-30 21:08 ` [bug#73428] " Julian Flake
2024-10-02 0:51 ` Maxim Cournoyer
2024-10-02 5:46 ` Julian Flake
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=31D4D07F-F706-4B12-BAE6-56E71EFF21EC@tobias.gr \
--to=bug-guix@gnu.org \
--cc=73428@debbugs.gnu.org \
--cc=flake@uni-koblenz.de \
--cc=julian@flake.de \
--cc=me@tobias.gr \
/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.