From: "Wiktor Żelazny" <wz@freeshell.de>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: ./pre-inst-env guix build dangerous inside an environment?
Date: Thu, 12 Sep 2019 17:45:57 +0200 [thread overview]
Message-ID: <20190912154556.5obvq3u7xeczcpgy@wz.localdomain> (raw)
In-Reply-To: <87tv9ipqo2.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 787 bytes --]
On Wed, Sep 11, 2019 at 09:40:45PM +0200, Ricardo Wurmus wrote:
> I think this failure mode is pretty terrible and I’m really sorry
> that you encountered it.
At least I learned something about Guix workings. The system is back.
This time, I completed 14.2 without a disaster.
> I wonder if the daemon should just abort with an error when it
> encounters an unknown directory. The problem with that is that
> sometimes directories are left behind when the daemon was forcibly
> killed, and we want those to be cleaned up automatically.
rm -i
cp -i
mv -i
from the shell world come to my mind. Or some --dry-run mode.
> (and an environment to provide the required dependencies to work with
> it)
I guess I need to learn more about Guix environments.
WŻ
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 963 bytes --]
prev parent reply other threads:[~2019-09-12 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-10 13:58 ./pre-inst-env guix build dangerous inside an environment? Wiktor Żelazny
2019-09-10 14:37 ` Ricardo Wurmus
2019-09-11 16:18 ` Wiktor Żelazny
2019-09-11 19:40 ` Ricardo Wurmus
2019-09-12 15:45 ` Wiktor Żelazny [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=20190912154556.5obvq3u7xeczcpgy@wz.localdomain \
--to=wz@freeshell.de \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/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.
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).