Hello maintainers,
the Copr project is in the process of implementing the PULP storage
backend (RPM repo management technology):
https://github.com/fedora-copr/copr/issues/2533
We expect that this change will be slow and incremental (we will not move
all projects to PULP at once) and that it is going to be almost an 1:1
replacement. See that tracker link above if you want more info.
There's one technical detail/change that seems to be clear right now and
is worth announcing in advance - the way we handle the duplicate NEVRAs in
the same repos is going to change (a bit). Before or after the switch,
Copr simply allows you to build packages with the same/duplicate NEVRAs
into the same repository. There's no reason to fail the build process.
The current (old) behavior though is that Copr keeps all the duplicates in
the RPM repository - and DNF is confused (when asked to install one of
such duplicate NEVRAs, it picks one of them by random, or by package ID,
or it is DNF version specific behavior, or - I don't really now). Project
administrators can then come anytime later and decide which particular
build ID they want to keep, and delete the rest of the duplicate builds.
So the confusion can be resolved pretty easily.
The new (with PULP) behavior will be that the newer duplicates
will override the previous - this is on one hand good, because DNF
is not confused - always sees the latest "duplicate" NEVRA to install.
But on the other hand this also means that, when the latest NEVRA build is
removed, Copr will drop the NEVRA from the metadata (it will not present
the older builds).
This is just a headsup for you, feel free to comment here or ideally in
the corresponding Copr issue
https://github.com/fedora-copr/copr/issues/3262
Thank you, and happy building!
P.S. When you build only for the purpose of building (to check there's no
FTBFS) you are not affected. If you bump Release regularly (you should),
you won't be affected.
Pavel
