On 10/12/2013 08:36 AM, Dennis Gregorovic wrote: > On Fri, 2013-10-11 at 19:09 +0200, Miroslav Suchy wrote: >> On 10/11/2013 06:04 PM, Mike McLean wrote: >>> The first thing I opted to tackle was dealing with Koji's uniqueness >>> constraints for NVRs and NVRAs. My approach was to add namespaces for >>> builds. Within a given namespace, NVRs are still required to be unique, >>> but cross-namespaces conflicts are allowed. Additionally, within the >>> NULL namespace any number of conflicts are allowed. >>> >>> Using namespaces allows folks that want NVR uniqueness to just stick >>> with the default namespace, but gives others the option of overlap. >>> >>> I know there are some concerns about the wisdom of allowing NVR overlap >>> at all. If you have cocerns one way or the other, please raise them here. >> >> Speaking for Copr: >> Each new project in Copr, should create new namespace in Koji. So if two >> identical NEVRA from two different namespaces would not raise conflict, >> and two identical NEVRA from one namespace would raise conflict, then it >> is everything I need. >> Well - beside some API for namespaces. I need some API to create >> namespace and some API to assign relation between koji tag and namespace. > > Just to clarify (Mike, correct me if I'm wrong) the uniqueness key is on > NVRA, not NEVRA. We intentionally do not include epoch in the > uniqueness key. Since epoch isn't in the filename, having two RPMs that > only differ by epoch would cause much confusion.
Correct, epoch is not part of the uniqueness constraints, and that will not change. 0:foo-1-1 and 1:foo-1.1 conflict within a namespace -- buildsys mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/buildsys
