From: Brainmue <brainmue@weiller.eu>
To: pgsql-general@lists.postgresql.org
Subject: Re: RHEL repo package crc mismatches
Date: Wed, 03 May 2023 07:33:02 +0000
Message-ID: <db5d0e5dff14e2fc84ba92ae7720e39e@weiller.eu> (raw)
In-Reply-To: <38ec2dac-7c72-5dc7-9af6-020c7e94e051@uvic.ca>
References: <38ec2dac-7c72-5dc7-9af6-020c7e94e051@uvic.ca>
Hello Evan,
we have exactly the same problem and don't feel comfortable with it at the moment either.
We even synchronise several versions and this problem occurs with all of them.
Can anyone confirm that the packages have not been changed inadvertently but only the metadata is
wrong?
Here are the changes with us.
For the pgdg11 RHEL 7 repository:
[MIRROR] ogr_fdw_11-1.1.0-1.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't match.
Calculated: c61d0bb8cdc2c386b57d8968b509f9fe7bf7693b3f86af730128797d087c0caa(sha256) Expected:
a963ae2eb874da055db63953cf0eb0d62e24d16abd6e8d4dab615ba4fadaefd8(sha256)
[MIRROR] ogr_fdw_11-llvmjit-1.1.0-1.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't
match. Calculated: 1be687c8721e7683f7efbfe51b9bd9532f7c7326d344e83e8928667cbc524cd3(sha256)
Expected: 52aa7c905fd802bfea5cf7e89b80b7523b2a16309575cdbe9d68df4179ec1f6b(sha256)
[MIRROR] pg_auto_failover_11-1.6.3-1.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't
match. Calculated: abd1ede633fe8dc7721e1e09783e300c8d5a5e9b226257c67969e2bfbf7ce4f9(sha256)
Expected: 0b29fc748639210c76af4b1870772780ba13a04698886e78514e7fb1baac9781(sha256)
For the pgdg13 RHEL 7 repository:
[MIRROR] ogr_fdw_13-1.1.0-1.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't match.
Calculated: d2ea23dc8b866c09eb620187e40147daae1a60f2a31370a88fd119b08a5f8816(sha256) Expected:
a39bc56ebc34de96321af69f99862819fe36516775cb155f599c839c098a0030(sha256)
[MIRROR] ogr_fdw_13-llvmjit-1.1.0-1.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't
match. Calculated: f2d981ba5ae5e54ac420f881c27eaba3af6b506638feed9f686273272083b479(sha256)
Expected: 5e6baa1e8169da8251f4a3c47c8db0ab4344977c0ed4a8f1042d353a50e4e304(sha256)
[MIRROR] pg_auto_failover_13-1.6.3-1.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't
match. Calculated: 01ce463c8487d52986e347025266167135f0a866c37590c784e7e3e5d8e43817(sha256)
Expected: e35c32a27f5c97596d74fca03e416cb743bf188fdc0dfaf736cc68a20801a5c9(sha256)
For the pgdg14 RHEL 7 repository:
[MIRROR] pg_auto_failover_14-1.6.3-1.rhel7.x86_64.rpm: Downloading successful, but checksum doesn't
match. Calculated: 7b72deadb029a8752717c832cde2e23d87e341037765086d88ac6d96816ebe89(sha256)
Expected: 55de94cebb1967c4f1edb1a0be14246173c05168261a76d141e819f607e83ee3(sha256)
Thank you for checking.
Greetings
Michael
3. Mai 2023 09:00, "Evan Rempel" <erempel@uvic.ca> schrieb:
> 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.
>
> For the pgdg13 RHEL 8 repository
>
> [MIRROR] pg_auto_failover_13-1.6.3-1.rhel8.x86_64.rpm: Downloading successful, but checksum doesn't
> match. Calculated: 5196edcfe1d6af6c0e90ad9a25667613bdfa0731a84fa9a1dbaa7080b4a3caac(sha256)
> Expected: 8d4527c96e9c8a3ff86d75aa85c166899ee895e9522c6720223f0f93b658f8d6(sha256)
>
> [MIRROR] e-maj_13-4.0.1-1.rhel8.x86_64.rpm: Downloading successful, but checksum doesn't match.
> Calculated: f7576cb1cd22303cb3dbb2a86911ad3f9e57afa8472a31f1a6a1f176f708fa1d(sha256) Expected:
> 8c56cacb99771c4f06be2551988e553a70ea5e5459202e12e0e92fdeb7371621(sha256)
>
> For the pgdg12 RHEL 8 repository
>
> [MIRROR] pg_auto_failover_12-llvmjit-1.6.3-1.rhel8.x86_64.rpm: Downloading successful, but checksum
> doesn't match. Calculated: 9bfdaccc3a151fd847bbb5e622a9384648cf963faacd90dc9b31cd433e23a3c0(sha256)
> Expected: aa5e3dc99cabfe22839ed0b9501a0099af139bf8551344a3b198ac048218ceee(sha256)
>
> I think it is just metadata information, but it sounds scary.
>
> Can anyone comment?
>
> --
> Evan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: brainmue@weiller.eu
Subject: Re: RHEL repo package crc mismatches
In-Reply-To: <db5d0e5dff14e2fc84ba92ae7720e39e@weiller.eu>
References: <38ec2dac-7c72-5dc7-9af6-020c7e94e051@uvic.ca> <db5d0e5dff14e2fc84ba92ae7720e39e@weiller.eu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox