Recently there has been a bug introduced that prevents `guix pull` from actually updating your channels (if using commits, branches or tags, which most people do). Additionally it can also prevent you from reconfiguring, ending up with `Git error: object not found for id (<commit you're currently pulled to>)`. This bug has been present for roughly 11 hours (from Sep 23rd at 9:13 UTC till Sep 23rd 20:23). If you pulled during that time, you're probably affected.
1. How to know if you're affected? The issue has been introduced by `66463356ce` and fixed by `7d1d1d1f7c4`, so you can check if you're between those revisions, if you know how to do that. Apart from that, if you see `guix pull` is repeatedly ending up with the same, old, revision, you're affected. Alternatively you can try evaluating an expression inside of `guix repl` that should pull the channel. `((@ (guix git) latest-repository-commit) ((@ (guix) open-connection)) "https://git.guix.gnu.org/guix.git"; #:ref '(branch . "master"))` Does it show the same commit as in `guix describe`, but you pulled some time ago? Then you're affected. (this will also show the same commit if guix hasn't been updated at all, it should always show the latest revision of master. So this isn't a comprehensive check) 2. How to recover? If you already have multiple generations of guix profile, rollback (`guix pull --roll-back`), then `guix pull` normally. If you don't, you can do `guix time-machine --commit=96d87b4747c63bfce81f8b6ac8eba481f31ed44d -- pull`. This picks up guix from before the change has been introduced, and pulls properly from within it. Regards Rutherther
