When pushing to the rpms/glib2 dist-git repo, the git hook installed by centpkg is failing with the error "Source file (or tarball) 'glib-2.80.3.tar.xz' wasn't uploaded to the lookaside cache. Push operation was cancelled."

$ git push -f
/usr/lib/python3.12/site-packages/centpkg/__init__.py:95: UserWarning: Unable to determine if this is a fork or not. Proceeding, but you should double check.
  warnings.warn('Unable to determine if this is a fork or not. Proceeding, but you should double check.',
/usr/lib/python3.12/site-packages/centpkg/__init__.py:95: UserWarning: Unable to determine if this is a fork or not. Proceeding, but you should double check.
  warnings.warn('Unable to determine if this is a fork or not. Proceeding, but you should double check.',
Source file (or tarball) 'glib-2.80.3.tar.xz' wasn't uploaded to the lookaside cache. Push operation was cancelled.
Hint: this check (.git/hooks/pre-push script) can be bypassed by adding the argument '--no-verify' argument to the push command.
error: failed to push some refs to 'gitlab.com:TheRealMichaelCatanzaro/centos_rpms_glib2.git 

However, glib-2.80.3.tar.xz is definitely in the lookaside cache and can be built successfully by Zuul and on streamkoji without any issues.

This is a follow-up issue to CS-2147. In that issue, sgallagh@redhat.com investigated and determined the source file in the lookaside cache was corrupted somehow. But in that case, builds were failing because the file was actually corrupt and presumably failed checksum validation. This time is different, because this time builds are proceeding perfectly fine. (Presumably the tarball in lookaside cache matches the expected hash? If not, then we've got a serious supply chain problem, since it shouldn't be possible to build if the source file doesn't match.)