From: "Ludovic Courtès" <ludo@gnu.org>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>
Cc: 58084@debbugs.gnu.org
Subject: bug#58084: guix deploy fails, leaving the newly installed system generation active
Date: Thu, 29 Sep 2022 16:47:15 +0200 [thread overview]
Message-ID: <87zgei9r0s.fsf@gnu.org> (raw)
In-Reply-To: <87a66myqlg.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 26 Sep 2022 13:48:11 -0400")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> skribis:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
> [...]
>
>>> … which is fine, except that there was already a pre-existing
>>> /etc/modprobe.d directory (coming from openSuSE, the distro that was
>>> initially installed on this machine), which caused this activation code
>>> to break:
>>
>> Oh wow! Should we be extra careful and always rm files before linking to
>> their location? Or define our own 'symlink' procedure that'd take care
>> of it? That's not very elegant but better than obscure crashes like
>> this.
>
> I just had a better idea: fail and report that an unexpected file was
> found there, leaving the user to inspect it and choose a proper action.
Yeah, that’d be nice. It’s really a corner case that you’ll only hit
when installing on a non-empty file system, but gracefully handling it
would be nice for sure.
Ludo’.
prev parent reply other threads:[~2022-09-29 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 2:37 bug#58084: guix deploy fails, leaving the newly installed system generation active Maxim Cournoyer
2022-09-26 15:39 ` Ludovic Courtès
2022-09-26 17:46 ` Maxim Cournoyer
2022-09-26 17:48 ` Maxim Cournoyer
2022-09-29 14:47 ` Ludovic Courtès [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=87zgei9r0s.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=58084@debbugs.gnu.org \
--cc=maxim.cournoyer@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).