To: pgsql-pkg-yum@lists.postgresql.org
From: Philippe Kueck <a4obmfyynycqcgqmaylaqxi6dzew6gismu@quarantine.de>
Subject: upload of rebuilt packages to the repository
Message-ID: <f4f0c3c3-ae97-6b94-8ca8-824952fb8c83@quarantine.de>
Date: Tue, 6 Mar 2018 13:36:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Precedence: bulk

Hi all,


I've noticed that from time to time PostgreSQL pushes rebuilds of
already existing packages[1] – i.e. same %{name}, %{epoch}, %{version},
%{release} and same filename but different content – into the yum
repository.

Please don't to that.

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. Mirrors that are
using e.g. reposync will create a corrupted file if the former package
was smaller than the updated one by appending additional bytes to the
existing file. If the former package was larger than the updated one,
your the servers will respond with a "416 range not satisfiable".


Best,

Philippe

[1] for example amcheck_next10-1.3-1.rhel7.x86_64 on march 1st