Rutherther <[email protected]> writes: >> What is the end-user situation when this happen? What is the recovery >> process? Maybe that is worth documenting somewhere, since I suspect >> this may happen again (for justifiable reasons). > > Could you clarify recovery process of what exactly? The end users of Guix > weren't affected by the force push. They were affected by the commit > that was there (couldn't `guix pull` and stopped being affected when > force push happened (now they could `guix pull`). > > It's true that for example if you had the repo cloned, did `git pull` > with a commit that doesn't authenticate, then there is a force push, > afterwards `git pull` won't work anymore. Is this what you mean, is > there more maybe?
Yes, I meant what happens if a user runs 'git pull' in this situation. What the error messages are, and how to recover. In case this happens again, maybe a small example would help. Given that my mirror is still stuck on the broken commit, I can see if I can experiment with what happens and how to recover for future reference. /Simon
signature.asc
Description: PGP signature
