Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etDeW-0002Tc-Ku for pgsql-pkg-yum@arkaria.postgresql.org; Tue, 06 Mar 2018 14:33:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1etDeV-0008Kf-Ah for pgsql-pkg-yum@arkaria.postgresql.org; Tue, 06 Mar 2018 14:33:15 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etDeV-0008KV-2X for pgsql-pkg-yum@lists.postgresql.org; Tue, 06 Mar 2018 14:33:15 +0000 Received: from ns5.gunduz.org ([107.170.136.15] helo=ns1.gunduz.org) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1etDeR-0000ku-Kl for pgsql-pkg-yum@lists.postgresql.org; Tue, 06 Mar 2018 14:33:13 +0000 Received: from asus-laptop04.gunduz.org (unknown [88.98.205.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ns1.gunduz.org (Postfix) with ESMTPSA id 3563D3FD09; Tue, 6 Mar 2018 14:33:08 +0000 (UTC) Message-ID: <1520346786.5655.20.camel@gunduz.org> Subject: Re: upload of rebuilt packages to the repository From: Devrim =?ISO-8859-1?Q?G=FCnd=FCz?= To: Philippe Kueck , pgsql-pkg-yum@lists.postgresql.org Date: Tue, 06 Mar 2018 14:33:06 +0000 In-Reply-To: References: Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-g6xqfImSlF1CpmfU/Kjn" X-Mailer: Evolution 3.26.5 (3.26.5-1.fc27) Mime-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --=-g6xqfImSlF1CpmfU/Kjn Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, On Tue, 2018-03-06 at 13:36 +0100, Philippe Kueck wrote: > I've noticed that from time to time PostgreSQL pushes rebuilds of > already existing packages[1] =E2=80=93 i.e. same %{name}, %{epoch}, %{ver= sion}, > %{release} and same filename but different content =E2=80=93 into the yum > repository. >=20 > Please don't to that. Err, we *never* do so. Can you please give me an example? > If the existing package is buggy or corrupt, just increase %{release} > and push the new package to the repo. > Otherwise yum and mirrors might not handle it correctly. With cached > metadata, yum will complain about checksum mismatches. When we add/update a new package, the metadata is updated, so if the cached version (on OS side) does not match, you get this message. That is the only reason for this issue (and it is not an issue, IMHO) Regards, --=20 Devrim G=C3=BCnd=C3=BCz EnterpriseDB: https://www.enterprisedb.com PostgreSQL Consultant, Red Hat Certified Engineer Twitter: @DevrimGunduz , @DevrimGunduzTR --=-g6xqfImSlF1CpmfU/Kjn Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEH8GKHNUOKtDEiyD22MM9/pLPbrUFAlqepqIACgkQ2MM9/pLP brWimA/9FqMQxH1PAPfIq1MacYMaiDYsP8C7aV1UwsWjg7k+weRVkOs9RvIAoRqx ZXuZdOBblBhRNxt7qApTDCmyCw3j1jo5lPFa2TUHz8jB1xT0oAF5Hp2S+FmtwXC4 5bPxy01oOK/ewtf3vJtxHN9Aeew+Gbn+NjBgMrnrJEH7Bgzyy7xq55Sy4bLAnCF5 eNGls8szAbFyg1KPJOg1ZTVjrSU1BUAyE5vGq/Abo/qjh50fO0R0NVI+MNqfa7VW Od/gk5N2G90nTSM+CSunrF4Zcdwmry0mAYP2TVU2IBkb8K5dKey/jymgbiHvJ+J5 cFXoZRdXvw5BWmdZ+R+GyIxP/GzYKMfn6mXxmHsl0EyBVkB0y4uAf6oD0asMKQUN UTppRZ5u2qAp4nC6003iYfvtL2k+6LYWVnJL2vpVSml91wCaBS508eGQHmLQ7uj2 EVaw6G3LgtbNfS9pBtkDw1XWvUR+3bBFaoHQ+KK+OfW0mwq3xePNTeVhU95c/ZrO Mp1OdS+WPvqALPzrzJ9UQ42/YMI9Z9lDG3yVExUuqbrElV/hAiAINN6w5M93UyFN RM/5mtoyhatumBX2AArsd0FyZZxVCiCQFdcF3Mjl6dEwZTu4mEsUUcLsFaeNPa/H kqzfnvYWu3fl1/ESjSOpMcrHHqmvfCrEHelUl6Met8HidMkGjy8= =qPQn -----END PGP SIGNATURE----- --=-g6xqfImSlF1CpmfU/Kjn--