On Wed, Feb 22, 2023 at 1:40 PM Kevin Fenzi <kevin(a)scrye.com> wrote:
The reason it behaves this way is because koji has no concept of 'newer
version' or 'older version'. It has only when a valid build was tagged
into a tag, and pungi operates on that with 'give me the latest tagged
packages in these tags'.
We have compose metadata for every single compose that has succeeded
and failed. In that metadata, we know what NVRs from Koji were pulled
in, and we can reconstitute any historical update push with that data.
We could merge current repos into the newly created one from pungi,
it would be a vast amount of work. It would mean all repodata would need
to be regenerated. That said, it could be done, but no one has had the
cycles to work on it.
Maybe we should just publish into Pulp and have them do that bit for
us automatically. I wouldn't personally be comfortable with that until
Pulp is available in Fedora for people to easily deploy, but I know
the COPR folks are investigating it for their tooling. And the
AlmaLinux folks use Pulp for their system for similar reasons.
Pulp is designed to handle super-huge repositories like that.
真実はいつも一つ！/ Always, there's only one truth!