From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Antwane Mason <ad.mason1413@gmail.com>
Cc: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
help-guix@gnu.org
Subject: Re: Udev Rule Not Triggered
Date: Mon, 30 Aug 2021 00:17:32 +0200 [thread overview]
Message-ID: <69153a102313299ebb4ddf8293aea075@tobias.gr> (raw)
In-Reply-To: <CAAztfg+JGwJJtsR_o4H8igeydf=r-ruyT7QneFbqs9G+QFfAVw@mail.gmail.com>
Antwane,
Great that you got it to work! There are some landmines left that I'd
like to point out so they don't bite you later (what? they're
mixed-metaphor cartoon landmines!):
On 2021-08-29 16:01, Antwane Mason wrote:
>> should use string-join instead of string-append
>
> Thanks for the suggestion, but I know that use of string-append is
> correct
> based on example code from
> https://guix.gnu.org/manual/en/html_node/Base-Services.html.
Yes, but *your* use of it isn't. :-) You didn't add any newlines so
everything ends up on one line, which can't work [well].
> (uri
> "https://raw.githubusercontent.com/M0Rf30/https://raw.githubusercontent.com/trustcrypto/trustcrypto.github.io/master/49-onlykey.rules")
> (sha256
> (base32 "1pj9i4hp0d74073x1qqwigd0cyriamg65zmx2j98mi0k66qrhcxa"))
This URL is bogus? It probably works for {you,now} because Guix is
content-addressed and you've previously downloaded a file with that hash
to your store. If it ever gets garbage collected, Guix will be unable
to download again.
I advise against using an external file for such a trivial rule at all,
and simply fixing the string-append until it works (and the actual file
contents look correct).
Kind regards,
T G-R
Sent from a Web browser. Excuse or enjoy my brevity.
next prev parent reply other threads:[~2021-08-29 22:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-29 13:39 Udev Rule Not Triggered Antwane Mason
2021-08-29 13:53 ` pelzflorian (Florian Pelz)
2021-08-29 14:01 ` Antwane Mason
2021-08-29 14:28 ` pelzflorian (Florian Pelz)
2021-08-29 14:42 ` pelzflorian (Florian Pelz)
2021-08-29 15:22 ` Antwane Mason
2021-08-29 15:44 ` Antwane Mason
2021-08-29 17:23 ` pelzflorian (Florian Pelz)
2021-08-29 18:54 ` Antwane Mason
2021-08-29 21:39 ` Antwane Mason
2021-08-29 22:12 ` pelzflorian (Florian Pelz)
2021-08-29 22:17 ` Tobias Geerinckx-Rice [this message]
2021-08-31 21:59 ` Antwane Mason
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=69153a102313299ebb4ddf8293aea075@tobias.gr \
--to=me@tobias.gr \
--cc=ad.mason1413@gmail.com \
--cc=help-guix@gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).