From: "Ludovic Courtès" <ludo@gnu.org>
To: Vagrant Cascadian <vagrant@debian.org>
Cc: guix-devel@gnu.org
Subject: Re: Trailing whitespace in /etc/guix/acl
Date: Wed, 03 May 2023 23:02:15 +0200 [thread overview]
Message-ID: <87ttwtw2lk.fsf@gnu.org> (raw)
In-Reply-To: <87y1miro2h.fsf@wireframe> (Vagrant Cascadian's message of "Sun, 23 Apr 2023 19:50:14 -0700")
Hi,
Vagrant Cascadian <vagrant@debian.org> skribis:
> I've noticed there is some trailing whitespace in /etc/guix/acl ... some
> of it comes from the keys in etc/substitutes/ci.guix.gnu.org.pub ... but
> some of it comes from whatever code assembles /etc/guix/acl (or rather,
> whatever the symlink points to in /gnu/store).
>
> I noticed this by trying to add the bordeaux substitute server for the
> Debian package, and swear in the past I was able to do it
> bit-for-bit-identical... but now with the inconsistent whitespace
> differences, while they do not make it impossible, make it needlessly
> more difficult than it needs to be, having to match the extraneous
> whitespace exactly...
>
> I have not figured out where in the code to look for all this stray
> whitespace... maybe someone could take a peek? Maybe the lazy approach
> might be to strip all trailing whitespace from the file after generating
> it?
The “canonical sexps” in /etc/guix/acl are serialized by code in…
Libgcrypt! See (gcrypt pk-crypto) in Guile-Gcrypt.
Good luck! :-)
Ludo’.
prev parent reply other threads:[~2023-05-03 21:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 2:50 Trailing whitespace in /etc/guix/acl Vagrant Cascadian
2023-05-03 21:02 ` 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=87ttwtw2lk.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=vagrant@debian.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 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).