Hello, Alexander. У ср, 2025-10-08 у 23:18 +0200, Tomas Volf пише: > Alexander Asteroth <[email protected]> writes: > > > I really love the declarative way of guix system and guix home to > > configure my > > installation. > > Unfortunately it often happens that after a guix pull some package > > (currently > > it's python-autopep8) fails to build. > > Often this package is just some dependency (and I don't even have a > > clue why > > python-autopep8 is needed by which package). > > The problem is now, that due to the transactional manner in wich > > guix > > reconfigure works I get stuck completely. > > I can't even change a dotfile (since it's managed by guix) or > > install a new > > package I need. > > Of course I could do that manually but that would lead to the chaos > > I had before > > using guix home. > > The only solution I see to get my system back to working would be > > to undo the > > guix pull (but is there a way to do that?). > > guix pull --roll-back > > > There must be a better strategy to deal with these situations, like > > excluding > > the failing package and it's dependencies to get updated. > > How do you deal with this situation (since it happens quite often).
I do not use guix home yet, but maybe an inferior could be specified? I have seen an example here: https://codeberg.org/guix/guix/issues/2815 It should allow upgrading the rest of the packages without upgrading the one which cannot be upgraded. Could the requiring package be identified with "guix graph ..."? See: https://lists.gnu.org/archive/html/help-guix/2025-09/msg00020.html I also sometimes use "guix weather ..." to see which of my packages do not have substitutes yet, so are probably failing to build. Maybe, it could be used with guix home too? Roman
signature.asc
Description: This is a digitally signed message part
