From: Maxime Devos <maximedevos@telenet.be>
To: Brian Cully <bjc@spork.org>
Cc: 55583@debbugs.gnu.org
Subject: bug#55583: guix-daemon doesn't cleanly error-out on case-insensitive file systems.
Date: Mon, 23 May 2022 16:25:50 +0200 [thread overview]
Message-ID: <daac9fc191f1c76351c1be1e222f5a1ec5ec66e3.camel@telenet.be> (raw)
In-Reply-To: <87bkvoflmr.fsf@ditto.jhoto.spork.org>
[-- Attachment #1: Type: text/plain, Size: 695 bytes --]
retitle 55583 guix-daemon doesn't cleanly error-out on case-sensitive file systems.
thanks
Brian Cully schreef op ma 23-05-2022 om 09:00 [-0400]:
This bug was caused by having my Guix filesystem mounted on a
case-insensitive file system. Re-running pull within the Docker
container mounted on a case-sensitive file system works correctly.
This bug can be closed. Sorry for the noise.
-bjc
Not sure how a case-insensitivity would cause this, but I think we
can keep this open -- wouldn't it be better if "guix-daemon" just says
‘nope, case-sensitivity is required (*), not continuing)?
(*) For reproducible builds, and apparently for substitution.
Greetings,
Maxime
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2022-05-23 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-22 20:09 bug#55583: nar-error on pull Brian Cully via Bug reports for GNU Guix
2022-05-22 21:09 ` Maxime Devos
2022-05-22 21:12 ` Maxime Devos
2022-05-22 23:06 ` Brian Cully via Bug reports for GNU Guix
2022-05-23 13:00 ` Brian Cully via Bug reports for GNU Guix
2022-05-23 14:25 ` Maxime Devos [this message]
2022-05-23 16:54 ` bug#55583: guix-daemon doesn't cleanly error-out on case-insensitive file systems Brian Cully via Bug reports for GNU Guix
2022-05-23 17:19 ` Maxime Devos
2022-05-24 22:54 ` Brian Cully via Bug reports for GNU Guix
2022-06-13 7:46 ` bug#55583: Maxime Devos
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=daac9fc191f1c76351c1be1e222f5a1ec5ec66e3.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=55583@debbugs.gnu.org \
--cc=bjc@spork.org \
/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.