Subject: bug#76660: current guix pull doesn't authenticate

From: Leo Famulari <[email-masked]>
Date: Sun, 2 Mar 2025 13:50:43 -0500

On Sat, Mar 01, 2025 at 11:37:40AM -0500, Jack Hill wrote:
> guix pull: error: aborting update of channel 'guix' to commit 6ca7b07a251739dfaefa639e74c01e3013c9454c, which is not a descendant of f13f0769688493271f43f31a016957355dbecb30
> hint: This could indicate that the channel has been tampered with and is trying to force a
> roll-back, preventing you from getting the latest updates.  If you think this is not the
> case, explicitly allow non-forward updates.

I successfully pulled from the latest commit on the 'master' branch:

------
$ guix package -p ~/.config/guix/current -l
[...]
Generation 242	Mar 02 2025 13:45:23	(current)
 + nonguix	45bde19	out	/gnu/store/ahqhr9qbhq9w83fl3yif8qy5vfkhay7c-nonguix
 + guix   	56a374a	out	/gnu/store/lfwph6c7099c0f5dzfpffg1qm93va5iv-guix-56a374aa7
 - nonguix	87c5b72	out	/gnu/store/1kbmg93s0sc3ic01pql1jic6nr8mzkhi-nonguix
 - guix   	55a5181	out	/gnu/store/vc2sn17c6g7ww4akd7p9dcfby6zykr81-guix-55a5181e7
------

This commit is a descendant of both of the commits from your error
message.

And `guix git authenticate` succeeds from 56a374a as well.

So what's going on?