Closing.
--
Sent from my p≡p for Android.
Well, I wondered myself , and I was palning to test when I arrive home today.
But here is my take:
1. Premise: The system configuration is declarative. The declarative state
should be obeyed all times by the system
2. Implication: running a guix pull (or any other form of update) as any user
sh
On 2018-06-20 23:35, l...@gnu.org wrote:
> Hello swedebugia,
..snip
> ~/.config/guix/current is created by the new ‘guix pull’. So when
> coming from 0.14, you actually need to run it twice: the first run will
> give you the new ‘guix pull’, and the second run will actually run the
> new code
Hello swedebugia,
swedebugia skribis:
> Steps to reproduce:
> Install 0.14
> Init system with user a
> Login root
> Guix pull
> Make sure it has right paths to .config/guix/current
> Reconfigure with new user b
> Reboot
> Login user b
>
> When logging in slim? populates the dot-files and a .gui
Hi
Steps to reproduce:
Install 0.14
Init system with user a
Login root
Guix pull
Make sure it has right paths to .config/guix/current
Reconfigure with new user b
Reboot
Login user b
When logging in slim? populates the dot-files and a .guix-profile is created
with path to old guix. No .config/gu
