unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Brian Cully via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
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 12:54:36 -0400	[thread overview]
Message-ID: <8735h0falg.fsf@ditto.jhoto.spork.org> (raw)
In-Reply-To: <daac9fc191f1c76351c1be1e222f5a1ec5ec66e3.camel@telenet.be>


Maxime Devos <maximedevos@telenet.be> writes:
> 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.

The issue is wide-spread: there are a number of packages that will 
install files who’s names only vary by case. It’s also 
per-package; most work fine, but some will just break 
randomly. Some don’t seem to break until you try to use them, and 
then they yell and complain. This is something I run into often 
enough that it’s familiar to me and know how to fix, but not often 
enough to prevent my surprise when it happens.

Guix can’t fix it, unfortunately. Maybe checking case sensitivity 
would be a worthwhile thing to do, just to warn people, but: I 
don’t know of a good way to check this in a file-system 
independent manner, and I honestly doubt it’s something that 
actually happens that often. I’ve been trucking a ZFS storage pool 
around since I first installed it on macOS about a decade ago, and 
since macOS is case-insensitive, that’s how it was installed (case 
sensitivity causes its own issues there). Short of running Guix on 
Windows or macOS, I don’t see this being a problem.

-bjc




  reply	other threads:[~2022-05-23 17:02 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       ` bug#55583: guix-daemon doesn't cleanly error-out on case-insensitive file systems Maxime Devos
2022-05-23 16:54         ` Brian Cully via Bug reports for GNU Guix [this message]
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

  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=8735h0falg.fsf@ditto.jhoto.spork.org \
    --to=bug-guix@gnu.org \
    --cc=55583@debbugs.gnu.org \
    --cc=bjc@spork.org \
    --cc=maximedevos@telenet.be \
    /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).