On Tue, Apr 25, 2017 at 04:08:00PM -0400, Dennis Gregorovic wrote:
On 04/24/2017 09:25 AM, Ralph Bean wrote:
> On Mon, Apr 24, 2017 at 01:51:39PM +0200, Stanislav Ochotnicky wrote:
>> This is the first stab and what the mbs CG metadata output might look like:
> Just to clarify - in the "build" entry here, this is a build of the
> "nginx module". The "version" (which is 1) and the
"release" (which is
> 2) are in koji terms, not MBS terms.
> The mapping between MBS and koji terms should look something like:
> MBS -> Koji
> name -> name
> stream -> version
> version -> release
> The only kicker I can see at the moment is the datatype of stream(MBS)
> versus version(Koji). The MBS stream is a string (master, or f26, or
> whatever). The Koji version... does it have to be an integer?
Is there potential for nvr conflict? For example if you have a nginx-1-2 RPM and a
It is possible, but highly unlikely.
You would have to have:
- A traditional rpm with a 'release' like 201704250000 (unlikely)
- A module with a streamname like '1' (unlikely).
You're more likely to hit the second one, where the module streamname
might be "2.2", suggesting that the module is following the "2.2"
update stream of some major package. To get an NVR conflict, you
would need to hit both scenarios, though.