New `rclone` package in OnDemand 4.0 RHEL8 repo not signed

Get Help
1

Hello,

The new rclone-1.74.0 package in the 4.0 repo for Red Hat 8 isn’t signed

# yum update rclone
Updating Subscription Management repositories.
Last metadata expiration check: 1:35:07 ago on Tue 05 May 2026 03:40:31 AM EDT.
Dependencies resolved.
========================================================================================================================
 Package                   Architecture              Version                      Repository                       Size
========================================================================================================================
Upgrading:
 rclone                    x86_64                    1.74.0-1                     ondemand-web                     28 M

Transaction Summary
========================================================================================================================
Upgrade  1 Package

Total download size: 28 M
Is this ok [y/N]: y
Downloading Packages:
rclone-v1.74.0-linux-amd64.rpm                                                          6.9 MB/s |  28 MB     00:04    
------------------------------------------------------------------------------------------------------------------------
Total                                                                                   6.9 MB/s |  28 MB     00:04     
Package rclone-v1.74.0-linux-amd64.rpm is not signed
The downloaded packages were saved in cache until the next successful transaction.
You can remove cached packages by executing 'yum clean packages'.
Error: GPG check FAILED

I suspect other copies in the other repo’s are similar. Under our security guidelines, we can’t install a non-signed RPM. Would appreciate it if someone on the OnDemand team responsible for managing the repo would sign with RPM with the OnDemand key.

Thanks!

2

Same problem here, the affected repository is https://yum.osc.edu/ondemand/4.0/web/el8/x86_64/ but I can’t exclude that there could be more.

3

This should have been fixed this morning. Can you try again and let us know?

4

It was not working when I wrote the previous comment, but it now works.
Thank you for addressing this!

5

Glad to hear its working now - sorry for the troubles, Mattia and Brad.

6

Working for me as well. Thanks!