Hello Devrim, The problem is fixed in most of the repositories I synchronise, but in one I now have a new one. With the package: postgresql13-odbc-13.00.0000-1PGDG.rhel7.x86_64.rpm For the pgdg13 RHEL 7 repository: [MIRROR] postgresql13-odbc-13.00.0000-1PGDG.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 2fa1642932c950ca5597d64a129fc78d2fb3909c898ade5f9bff4db73fb39ae5(sha256) Expected: 9ed5b91c12e072d871314bfa5e8ec991bb312f360f7d1e3af8ece78945931900(sha256) It would be great if you could correct that too. Thank you very much. Greetings Michael 4. Mai 2023 00:23, "Devrim Gündüz" <devrim@xxxxxxxxxx> schrieb: > Hi again, > > On Tue, 2023-05-02 at 12:38 -0700, Evan Rempel wrote: > >> At our site we use reposync to copy the postgresql repositories to a >> local repository. >> >> When doing this on April 28 (and since) I exprience the following >> package checksum matching errors. > > <snip> > > I can confirm that this is caused by signing unsigned packages last > week, but rsync failing to update main server(s). So this is *not* a > security issue. > > However, as a precaution, I removed problematic packages from the > repository. They were too old anyway. I did not want to push updated > checksums for the same packages. > > Please let me know if this solves your problem. > > Again, thanks for the report. > > Regards, > -- > Devrim Gündüz > Open Source Solution Architect, PostgreSQL Major Contributor > Twitter: @DevrimGunduz , @DevrimGunduzTR
