<sebboh>Looks like the initial install from the USB image didn't populate the store as I would have expected. I'm downloading and building things that I downloaded and built yesterday. **I think.** I don't actually know the steps that guix goes through to install a package, or reconfigure an OS.
<mark_weaver>fwiw, one workaround for this awkwardness on single-user machines is to make ~root/.config/guix/latest a symlink pointing to ~USER/.config/guix/latest
<sebboh>I use sudo exclusively (or, I will if I can ever complete this reconfigure) and I never even look in /root. Occasionally when it is time to migrate a machine, I look in there, and I find tons of little application-generated files, all of which clearly somehow got that $HOME instead of /home/hobbes. Now, there is some command line option for sudo that affects this.. and I might occasionally invoke sudo incorrectly. But whatever, if I
<sebboh>I think the balance between this thing being a unix and having it be centered around a functional package manager has broke--that is, it has tipped to both side simultaneously.
<sebboh>Don't worry, I'm here to help. 1. all requests for resources (source, bins, package lists, whatever) go through localhost:1234 which caches. That will solve a lot of re-download-cause-wrong-user issues.
<sebboh>2. any build/work/expensive operation gets *uploaded* to localhost:1234, too. For the same reason.
<sebboh>3. Some facility can show an operator what packages are installed and at what scope-level each is installed. (This may exist, pardon me.)
<fps>sebboh: there is such a thing: the list of packages in the operating-system call in your config
<sebboh>I just installed a few packages, but they didn't make it to my config. Which brings me to 4. an operator can ask the running system to emit a config, and it will somehow magically know the difference between a default value and values the user has tainted, whether it happened from config.scm or later from guix package ... et al.
<sebboh>fps, I'm praying? I don't even know who the devs are.
<sebboh>I can't remember what the other thing is. Have a great weekend~!
<fps>about 1. unless you explicitly GC stuff that was downloaded won;t be downloaded again
<fps>if you have a package in the operating-system and a user guix package -i's the exact same package he _should_ just get a symlink to the same place in the store
<fps>about 2. unless you explicitly GC, the result of a derivation will not get removed, so if another user requests the same derivation they should again just get a symlink in their profile to the same place in the store
<fps>about 3. i wonder if the result of the operating-system call is serialized explicitly somewhere among the system generations in /var/guix
<rekado>XFCE4 needs policykit / consolekit. The "Suspend", "Shutdown", "Restart", "Switch user" fields in the panel are only active when it can get a positive answer on DBus to questions like "CanRestart".
<rekado>you can run "dbus-monitor --session" and then add "Action Buttons" to the panel to see these dbus requests and their answers.
<rekado>the destination is org.xfce.SessionManager, so if we wanted to fix this we would have to change the session manager code.
<civodul>Steap: sorry, i don't understand what failed
<civodul>coreutils and dmd (provides halt & reboot) are installed by default
<civodul>i can think of 3 ways this can happen: (1) remount /gnu/store read-write and explicitly remove the things, and (2) overwrite /var/guix/db/db.sqlite and run 'guix gc', or (3) install Guix with a different localstatedir and run 'guix gc' with that Guix
<mark_weaver>does this qcow2 image contain just a single filesystem, or does it contain a partition map with multiple partitions?
<mark_weaver>(my question may show my ignorance of VMs; I confess I almost never use them myself)
<mark_weaver>if this happened to me on my bare metal system, I would boot from the USB installer
<Steap>it has an ext4 partition + a swap partition
<mark_weaver>it may be that someone with more experience with VMs should be helping you here. what does one normally do when the root partition of a VM is corrupted? how does one do the equivalent of booting a rescue system that has access to that corrupted partition?
<mark_weaver>Steap: did you try booting into an earlier generation of the system? is there a GRUB menu that you have access to while booting this VM?
<mark_weaver>it would be nice if our initrd emergency REPL were easier to use, and that's something we can work on, but honestly it hasn't been high on our priority list because I don't think this kind of problem has ever happened any of us before. we've always been able to boot into an earlier generation of the system.
<mark_weaver>well, since you're the VM guy, I ask again: what does one normally do when the root partition of a VM is corrupted? how does one do the equivalent of booting a rescue system that has access to that corrupted partition?
<mark_weaver>because I, as a bare-metal guy, know exactly what I would do in this case: I would simply boot the USB installer.
<mark_weaver>Steap: well, my conclusion from this is the same as if you had said "I ran 'tar xf icecat-xxx.tar.xz' and now my whole system is fubared". your filesystem got corrupted somehow. it's the only explanation of why simply adding new files to the filesystem would cause long-existing files to suddenly disappear.
<rekado>hmm, I spoke too soon. The shutdown and restart buttons are no longer disabled, but they don't actually do what their labels say. XFCE ends but it immediately respawns and the user ends up at the slim login screen.
<rekado>how can I view the logs on vt1? Are they stored somewhere?