Hi,
I'm using yum-priorities in my cobbler-maintained systems in order to have certain packages 'pinned' to a specific version. Now i noticed that the distro repository (the 'core-0' repo) is set to priority=1 by default.
Other than editing /var/www/cobbler/ks_mirror/config/<distr>.repo , is there a better way of changing the priority?
----- "Léon Keijser" keijser@stone-it.com wrote:
Hi,
I'm using yum-priorities in my cobbler-maintained systems in order to have certain packages 'pinned' to a specific version. Now i noticed that the distro repository (the 'core-0' repo) is set to priority=1 by default.
This should not be an issue, if your reposync'ed repositories for RHEL / CentOS (base and updates) are also set to priority=1, you can set this on the repo object.
Jasper
On Thu, 2009-07-09 at 17:33 -0400, Jasper Capel wrote:
This should not be an issue, if your reposync'ed repositories for RHEL / CentOS (base and updates) are also set to priority=1, you can set this on the repo object.
I'm talking about when you do a `cobbler import`, cobbler will automatically create a repository for you in /var/www/cobbler/ks_mirror/<distro>. This repo doesn't show up in `cobbler repo list` so i can't edit it.
And even if i would sync 'base' repositories, i'm still stuck with a 'distro repo' with priority=1.
On 07/09/2009 11:38 PM, Léon Keijser wrote:
On Thu, 2009-07-09 at 17:33 -0400, Jasper Capel wrote:
This should not be an issue, if your reposync'ed repositories for RHEL / CentOS (base and updates) are also set to priority=1, you can set this on the repo object.
I'm talking about when you do a `cobbler import`, cobbler will automatically create a repository for you in /var/www/cobbler/ks_mirror/<distro>. This repo doesn't show up in `cobbler repo list` so i can't edit it.
You're wrong here. This is not a repo. This is an install tree.
Cobbler will make certain directories under that into yum repositories by running createrepo on them.
But yes, there is no repo object to represent these. Adding these were what we were talking about doing, to make it potentially more obvious for people who absolutely must know how things work. Really though, I think "it just works" is suitable and hiding that the install tree has been repo-ized is not as important.
And even if i would sync 'base' repositories, i'm still stuck with a 'distro repo' with priority=1.
This is why I suggested we make a setting for this, if needed, to change the base default...
On Fri, 2009-07-10 at 17:13 -0400, Michael DeHaan wrote:
I'm talking about when you do a `cobbler import`, cobbler will automatically create a repository for you in /var/www/cobbler/ks_mirror/<distro>. This repo doesn't show up in `cobbler repo list` so i can't edit it.
You're wrong here. This is not a repo. This is an install tree.
Ah, thanks for clearing that up.
And even if i would sync 'base' repositories, i'm still stuck with a 'distro repo' with priority=1.
This is why I suggested we make a setting for this, if needed, to change the base default...
Well, the entire point of my post was to ask if it was okay if i edited the files by hand, instead of doing it some other way. I'm fine with editing files, just as long as they don't get overwritten in the future.
Hi,
I'm using yum-priorities in my cobbler-maintained systems in order to have certain packages 'pinned' to a specific version. Now i noticed that the distro repository (the 'core-0' repo) is set to priority=1 by default.
Other than editing /var/www/cobbler/ks_mirror/config/<distr>.repo , is there a better way of changing the priority?
cobbler repo edit --name=foo --priority=number
cobbler@lists.fedorahosted.org