From: Julien Lepiller <julien@lepiller.eu>
To: 57585-close@debbugs.gnu.org
Subject: bug#57585: guix gc removed home config
Date: Sun, 4 Sep 2022 21:17:58 +0200 [thread overview]
Message-ID: <20220904211758.313e13c0@sybil.lepiller.eu> (raw)
In-Reply-To: <20220904203258.697e39dc@sybil.lepiller.eu>
Actually I figured this out:
Generation 16 used an older guix version where guix home added a . at
the end of file names, so my config looked like this:
(simple-service 'xfce4-terminal home-files-service-type
`(("config/xfce4/terminal/terminalrc"
,(local-file
"files/xfce4-terminal/terminalrc"))))
Then, I updated Guix without changing my home configuration, so on
generation 17, guix home created $HOME/config instead of $HOME/.config.
So $HOME/.config/xfce4/terminal/terminalrc (and all other config files)
kept pointing to generation 16's files. After removing the generation
and "guix gc", these files no longer exist, and I'm in trouble :)
So, guix home and guix gc are working as intended, but the change to no
longer adding a "." at the beginning of file names (which makes total
sense) tripped me up.
Le Sun, 4 Sep 2022 20:32:58 +0200,
Julien Lepiller <julien@lepiller.eu> a écrit :
> Hi Guix!
>
> Today I ran "guix home delete-generations" to remove my old home
> generations. It removed generations 0 and 17. I'm on generation 18.
>
> Then I ran "guix gc" and after I noticed I couldn't run a program from
> my window manager (its menu is managed from guix home), I tried to
> look at what was happening. My config files managed by guix home are
> now symlinks that point to non existent store items. Spooky.
>
> Please let me know how I can help diagnose the issue
>
>
>
next prev parent reply other threads:[~2022-09-04 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-04 18:32 bug#57585: guix gc removed home config Julien Lepiller
2022-09-04 19:17 ` Julien Lepiller [this message]
2022-09-05 6:01 ` Andrew Tropin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220904211758.313e13c0@sybil.lepiller.eu \
--to=julien@lepiller.eu \
--cc=57585-close@debbugs.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.