[Spacewalk-list] yum-priorities feature in Spacewalk repository management?

[Contant, Olivier]

I'm not having error actually, but I was thinking about this scenario and wondering how it would work by having the same package *different version* in 2 differents repository.  

But the tricky scenario could be a needs for us as well.  We deploy application that may require a previous version of a package. Let say for example a specific version of a lib.

Maybe this issue shouldn't be fixed at the level of the Spacewalk but more at the level of the development team that should maybe embedded with the application the different dependency and bind it locally to the application.

Like : 
/applicationfolder/lib/python_versionx
/applicationfolder/bin/MySQL5.5/
/applicationfolder/bin/PythonX.Y/

And so on .. and rebuild the rpm for those package to install by default in the tree directory of the application ...  Would need a cue about the best practice here.


Regards,



-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Miroslav Suchý
Sent: Thursday, June 02, 2011 12:19 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] yum-priorities feature in Spacewalk repository management?

On 06/02/2011 05:58 PM, Contant, Olivier wrote:
> dependency, let say MySQL 5.5 instead of the MySQL 5.0 available in 
> the base repository for the operating system.
> 
> I created a new repository including the RPM of the internally develop 
> application and added the specific version of dependency package.
> Application repository would have:
> - Application.rpm
> - MySQL 5.5-server.rpm
> - other dependency.rpm ...
> 
> Since I need this system to be registered to its base repository for 
> operating system maintenance and update as well as other useful 
> package that I might need to install on those system for 
> administration,  I get into issue where I have package conflicting in 
> both repository as package exist in both.
> 

I'm puzzled.
If you have in base channel, let say:
 mysql-server-5.0.0
and in child channel
 mysql-server-5.5.12
- which is btw correct and allowed scenario - then yum should prefer that 5.5.12 version. The reverse situation (wanted 5.0, but not 5.5) will be tricky, but your situation should work without problem.

What error you get from yum?

--
Miroslav Suchy
Red Hat Satellite Engineering

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list