On 2022-10-26, Vagrant Cascadian wrote: > On 2022-10-26, zimoun wrote: >> On Wed, 26 Oct 2022 at 09:57, Vagrant Cascadian wrote: >> >>> It is consistently the same errors in the log, though on further looking >>> i discovered a branch in ~/.cache/guix/checkouts/ that had old removed >>> files in it (including wicd.scm/wicd.go) ... *maybe* that was somehow >>> related. I did remove all the evidence, so so if stale checkouts is >>> somehow the issue, it will be hard to reproduce again... oops. ... >>> I did manage again to use an old commit to pull up to a more recent >>> master (a0751e3250dfea7e52468c8090e18c3118d93a60), and see there are new >>> commits now so will try again. Will see. >> >> What is your hackish workflow? You do, >> >> guix pull --commit= && guix pull > > To use the older generations I used: > > /var/guix/profiles/per-user/vagrant/current-guix-138-link/bin/guix pull ... > > >> right? From your recent pull, does this >> >> guix time-machine --commit= -- help >> >> work? where is newer than your current revision. > > Oh yeah, that reminds me to add to the confusion, "guix time-machine > --commit=SOMECOMMIT" worked fine, even where "SOMECOMMIT" didn't > successfully work with guix pull. > > Maybe that's a clue pointing to the crufty .cache directories? Well, after removing ~/.cache/guix/checkouts/ I haven't had the problem again, with several successful pulls. This suggests to me that guix should make sure to not use a dirty checkout to prevent this in the future ... either exporting the guix tree it's working with to a temporary location, or something like running "git clean -dfx" before using the checkout... live well, vagrant