jgart <jg...@dismail.de> writes: > On Thu, 14 Apr 2022 09:05:29 -0700 Vagrant Cascadian <vagr...@debian.org> > wrote: >> Rolling back to an older generation and then moving forward basically >> would be a successfull (hopefully just accidental) attack changing the >> commit history! Rolling back to an older generation isn't much different >> than just blindly allowing to move forward to a different branch... > > That's a very good point that I only just thought of now after doing it ;() > >> Is it possible that one of your channels actually had the exact same >> commit in it, but then forked off in different directions? > > I don't have any other channel that is mirroring GNU Guix upstream. > >> It is rather unsettling to not know what happened... > > Yes, it is. I agree. > > Others have reported this issue on irc at #guix. > > See the logs. > > I think they just blindly used --allow-downgrades while I blindly rolled back > and forward > > Hopefully we find out what happened. > > all best, > > jgart
It should be possible to use the git reflog to find out what your previous git history state was. It would be a good idea if you could push the "suspect" branch up somewhere where it can be examined, I'd think?
