Koji and spec file with not the most up-to-date version of a package

Dennis Gilmore dennis at ausil.us
Wed Oct 28 14:14:34 UTC 2015


On Wednesday, October 28, 2015 02:51:45 PM Sebastien Moretti wrote:
> >> Hi
> >> 
> >> We use Koji and have an issue with some packages (let say B)
> >> requiring a particular version of another package (A = 1.2 ) which
> >> has a more up-to-date version (A = 1.2 & A = 1.5).
> >> e.g.
> >> Name:            B
> >> BuildRequires:   A = 1.2
> >> 
> >> In that case, Koji builds fail:
> >> DEBUG util.py:388:  Error: Package: B-3.4.2-4.el6.x86_64 (build)
> >> DEBUG util.py:388:             Requires: A = 1.2
> >> DEBUG util.py:388:             Available: A = 1.5-1.x86_64 (build)
> >> DEBUG util.py:388:                 A = 1.5
> >> 
> >> 
> >> 
> >> Is there a way to avoid that behavior?
> >> When no version is specified, use the most up-to-date, when a
> >> particular version is required, use that one.
> > 
> > koji repos can contain only single build of a package, that's by design
> > 
> > 		Dan
> 
> But if I try
> 	yum info A
> it will return A-1.5
> 
> If I try
> 	yum info A-1.2
> it will return A-1.2
> 
> So both should be in the repos, right?

no koji only has the last tagged version of a package in its repos. if you 
need multiple versions of something you will need to manage that in the 
packaging.  having a12 a15 etc packages

Dennis

Dennis


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.fedoraproject.org/pipermail/buildsys/attachments/20151028/df78b7e5/attachment.sig>


More information about the buildsys mailing list