unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tomas Volf <~@wolfsden.cz>
To: guix-devel@gnu.org
Subject: The `channels' field of `operating-system' record
Date: Sun, 7 Apr 2024 18:05:57 +0200	[thread overview]
Message-ID: <ZhLEZRLgYSlknetc@ws> (raw)

[-- Attachment #1: Type: text/plain, Size: 2993 bytes --]

Hello,

yesterday I had to debug a really weird problem.  I had a extra-special-file in
my system configuration used to create /etc/guix/channels.scm, but it was not
working, the channels file contained something completely else then I put into
it.  In particular, this sequence in the configuration:

    (extra-special-file "/etc/guix/channels.scm" file/channels.scm)
    (extra-special-file "/etc/guix/xxx" file/channels.scm)
    (extra-special-file "/etc/guix/yyy" file/channels.scm)

Produced this on the file system:

    channels.scm -> /gnu/store/icw828kvva25ns9p0y0np7lp3c7xl0n6-channels.scm
    xxx -> /gnu/store/w3gip7zqrqxbp8kaplq6kia85i5c4fh8-channels.scm
    yyy -> /gnu/store/w3gip7zqrqxbp8kaplq6kia85i5c4fh8-channels.scm

Notice that, despite being created by the exact same code, the store items
differs.

After ~2 hours of digging I realized this is caused by the changes in
883e69cdfd226c8f40b6e3b76ce0740b59857de6.

I see couple of issues here (in no particular order, questions prefixed with Q):

* My configuration file just *silently* stopped working.

That is not great for obvious reasons.

* There is no news entry

I did not realize it stopped working for some time (but it explains few weird
issues I had lately) until I tried to install completely new system where I
actually went to check it works as expected.

* Broken default behavior.

Currently, out of the box, extra-special-file with "/etc/guix/channels.scm" just
does not do anything.  No error, no warning.  That is pretty unexpected.

* There is no terse way to turn it off

Currently my configuration contains this:

      (modify-services %base-services
        (guix-service-type
         config => (guix-configuration
                    (inherit config)
                    (channels #f))))

That is 5 lines instead of single token %base-services just to restore the
original non-broken behavior.  Would be nice to have guix-extension for this
turning it into 2 lines.

* Q: Is there an easy way to fill (channels)?

After I learned that (channels) is a thing, I wanted to use it, but did not find
any simple way how to do so.  My channels are in channels.scm produced by `guix
describe --format=channels', and I do not see any simple way to pass the content
of that file into (channels).  No, it does not accept (local-file).  I tried
just (read)-ing it, but that too does not work.

I could steal the code from scripts/pull.scm, but that cannot be the intended
way, right?  So how should I do this?  What procedure did I failed to find?

* Q: Is the default value right?

Currently it defaults to %default-channels, which causes all this magic.  Would
it not be better to default to #f, so that it would do nothing magical out of
the box and would be backwards compatible?  You could still turn it on by
(Somehow?  See above.) providing desired value.



Have a nice day,
Tomas Volf

--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2024-04-07 16:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-07 16:05 Tomas Volf [this message]
2024-04-10 15:17 ` The `channels' field of `operating-system' record Ludovic Courtès
2024-04-15 22:04   ` Tomas Volf
2024-04-19 20:10     ` Ludovic Courtès
2024-05-08 23:16   ` Tomas Volf
  -- strict thread matches above, loose matches on Subject: below --
2024-04-09  4:06 Nathan Dehnel
2024-04-09  4:16 ` Marek Paśnikowski
2024-04-09 12:28   ` Tomas Volf
2024-04-09 12:29 ` Tomas Volf
2024-04-09 12:33 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.

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=ZhLEZRLgYSlknetc@ws \
    --to=~@wolfsden.cz \
    --cc=guix-devel@gnu.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).