From: Giacomo via Bug reports for GNU Guix <bug-guix@gnu.org>
To: janneke@gnu.org, 68848@debbugs.gnu.org
Cc: ludo@gnu.org, sarg@sarg.org.ru, 60521@debbugs.gnu.org
Subject: bug#68848: New home-dotfiles-service-type creates extra toplevel directories
Date: Wed, 31 Jan 2024 13:31:52 +0100 [thread overview]
Message-ID: <D29097E8-217F-491E-8BD4-6FD15C1F162E@autistici.org> (raw)
In-Reply-To: <87cythy9wq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1196 bytes --]
Hi Janneke, thank you for the report. I already pointed out this at https://issues.guix.gnu.org/60521 . there was a fix that was removed by a misunderstanding on the requirements of the service since the code contradicts documentation as you pointed out . It should be pretty easy to apply the fix from 60521.
Thank you
Giacomo
Il 31 gennaio 2024 13:17:25 CET, Janneke Nieuwenhuizen <janneke@gnu.org> ha scritto:
>Hi,
>
>When I follow the documentation, and have
>
> dotfiles/guix/.config/guix/channels.scm
>
>that shows suing tree -a ./dotfiles
>
> dotfiles
> └── guix
> └── .config
> └── guix
> └── channels.scm
>
>similar to the documentaion, and using
>
> (service home-dotfiles-service-type
> (home-dotfiles-configuration
> (directories (list "./dotfiles"))))
>
>creates
>
> ~/guix/.config/guix/channels.scm
>
>an extra toplevel `guix" directory!
>
>What gives?
>
>Greetings,
>Janneke
>
>--
>Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
>Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
[-- Attachment #2: Type: text/html, Size: 1433 bytes --]
prev parent reply other threads:[~2024-01-31 12:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-31 12:17 bug#68848: New home-dotfiles-service-type creates extra toplevel directories Janneke Nieuwenhuizen
2024-01-31 12:31 ` Giacomo via Bug reports for GNU Guix [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=D29097E8-217F-491E-8BD4-6FD15C1F162E@autistici.org \
--to=bug-guix@gnu.org \
--cc=60521@debbugs.gnu.org \
--cc=68848@debbugs.gnu.org \
--cc=goodoldpaul@autistici.org \
--cc=janneke@gnu.org \
--cc=ludo@gnu.org \
--cc=sarg@sarg.org.ru \
/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).