Packages on S3 Mirror of RPM repository changed GPG keys
Incident Report for Tideways
We performed a large migration of the RPM repository yesterday and in the process activated a mirror script to synchronize the new RPM repository to the old location to make the migration smooth for existing installations. In the process we realized that our mirroring script has a bug where adding the old GPG key invalidates the checksums stored in the metadata files. As such your downloads of the old YUM repository will fail with this error:

[Errno -1] Package does not match intended download.

You can workaround this by changing to the new repository directly, modify the `/etc/yum.repos.d/tideways.repo` to point the baseurl to:

Additionally import the new GPG Key:

rpm --import

We are working on fixing the mirror script to generate the right metadata to avoid this error within the day.

**Edit August 26th, 11:35** We have pushed the RPM repository to S3 again with the old publishing mechanism to restore it to the original state, signed with the old GPG Key. The installation should now work again so that we can working on fixing the mirror script without pressure.
Posted Aug 25, 2020 - 02:00 CEST