Hi,
Florent Georges <[email protected]> writes: > Thank you, Rutherther! I ran the following: > >> sudo guix gc --verify=contents,repair > reading the store... > checking path existence... > checking hashes... So this is all? That would mean there is no corruption and then I do not really know how the error can be occurring tbh. > > I tried again "guix package -l" after, but I still get the same error. I would expect nothing else, since even if there was corruption, it is not fixable as user profiles are not substitutable. > > I have no idea what you mean by "you will probably have to switch to > earlier generation, and remove the one affected by the corruption" Guix package uses generations, every time you install something new generation is created. You can manage them with `guix package` --list-generations, --delete-generations, --switch-generations. > > On the other hand, since I know exactly the list of 10-ish packages I have > installed using Guix, it might be easier to delete/uninstall Guix > completely. Then install it fresh again. Any specific things to be > careful with if I chose that path? This is an excessive reaction as the issue is only in your user's profiles, so there should be no reason to get rid of guix completely. You can just remove stuff under /var/guix/profiles/per-user/$USER. That way you reset your user's profiles state. Or you should actually be able to remove just /var/guix/profiles/per-user/$USER/guix-profile*, leaving current-guix untouched (current-guix is the profile you get from guix pull), if you don't have problems with pull, you don't have to remove that one. Nope, no specific things to be careful about, if you decide to nuke Guix, make sure to nuke both /var/guix and /gnu/store (or if you just use guix-install.sh --uninstall it will do it for you). As long as you remove everything, it is fine. What would be problematic is if you left one without the other. Rutherther > > ju, > > -- > Florent Georges > H2O Consulting > http://h2o.consulting/ > > > > > On Sun, 31 Aug 2025 at 18:22, Rutherther <[email protected]> wrote: > >> >> Hi Florent, >> >> Florent Georges <[email protected]> writes: >> >> > Hi, >> > >> > After a reboot (a crash of my machine running Ubuntu, actually,) I get an >> > error with Guix, about an unsupported manifest format. For instance: >> > >> >> guix package -l >> > Generation 1 Jul 14 2022 17:24:46 >> > emacs 27.2 out /gnu/store/6ahsf2ja6qyg19skggjxxpf9xx6ybxi1-emacs-27.2 >> > >> > Generation 2 Jul 14 2022 19:33:27 >> > + glibc-utf8-locales 2.31 out >> > /gnu/store/rgydar9dfvflqqz2irgh7njj34amaxc6-glibc-utf8-locales-2.31 >> > >> > Generation 3 Jul 14 2022 19:37:02 >> > guix package: error: unsupported manifest format >> > >> > Any idea what could be wrong? >> >> Yes, especially if your machine crashed, this is probably a file >> corruption. You can try running `guix gc --verify=contents,repair` >> to find corrupted files in store and repair them if possible (they have >> to be substitutable) >> >> If your profile's manifest is broken, that's unfortunate as you cannot >> really substitute that. So you will probably have to switch to earlier >> generation, and remove the one affected by the corruption, then you >> should be fine. >> >> Rutherther >> >> > >> > -- >> > Florent Georges >> > H2O Consulting >> > http://h2o.consulting/ >>
