I recently moved away from apt, becuase I could not make it work with multiple x86_64, because there are many duplicate packages from both rchitectures that get installed, and I could not make apt-get work.
Someone suggested that I try yum, which does work, but I am having a heck of a time managing multiple repositories.
It was easy with apt, being able to pin priorities to repositories and packages, but I cannot make yum work as nicely with pinning. I can exclude and such but most of the time it does not work.
I wish I could go back to apt while using x86_64.
If anyone has got any tips for either getting apt to work with multiple architectures, or pinning with yum please let me know.
On 6/13/05, Robin Mordasiewicz robin@bullseye.tv wrote:
Someone suggested that I try yum, which does work, but I am having a heck of a time managing multiple repositories.
It was easy with apt, being able to pin priorities to repositories and packages, but I cannot make yum work as nicely with pinning. I can exclude and such but most of the time it does not work.
You can see from http://www.google.com/search?hl=en&lr=&q=+site:lists.dulug.duke.edu+... that this is a subject that comes up frequently on the yum lists. I would recommend you read through some of those posts to get some ideas.
Also, the exclude option in the yum.conf (man yum.conf for more details) and the enablerepo and disablerepo may be precisely what you need.
Some of these features may require a newer version of yum than you have (you didn't say CentOS3 or 4) but you can always pull out yum from cvs if the feature you need is released later.
Greg
On Mon, 13 Jun 2005, Greg Knaddison wrote:
On 6/13/05, Robin Mordasiewicz robin@bullseye.tv wrote:
Someone suggested that I try yum, which does work, but I am having a heck of a time managing multiple repositories.
It was easy with apt, being able to pin priorities to repositories and packages, but I cannot make yum work as nicely with pinning. I can exclude and such but most of the time it does not work.
You can see from http://www.google.com/search?hl=en&lr=&q=+site:lists.dulug.duke.edu+... that this is a subject that comes up frequently on the yum lists. I would recommend you read through some of those posts to get some ideas.
Also, the exclude option in the yum.conf (man yum.conf for more details) and the enablerepo and disablerepo may be precisely what you need.
Some of these features may require a newer version of yum than you have (you didn't say CentOS3 or 4) but you can always pull out yum from cvs if the feature you need is released later.
ok, thanks. I have played around a bit and it seems that I can narrow it down to certain repositories causing more problems. It seems that DAG and Dries repositories work flawlessly, but atrpms causes alot of conflicts. The kde-redhat repo is only causing one small conflict, but if I choose not to install kde at kickstart time it works ok.
On 6/13/05, Robin Mordasiewicz robin@bullseye.tv wrote:
ok, thanks. I have played around a bit and it seems that I can narrow it down to certain repositories causing more problems. It seems that DAG and Dries repositories work flawlessly, but atrpms causes alot of conflicts. The kde-redhat repo is only causing one small conflict, but if I choose not to install kde at kickstart time it works ok.
Oh, um, yeah, that.
http://dag.wieers.com/home-made/apt/FAQ.php#D2
What do you need from atrpms that you want to keep it enabled all the time?
Greg
On Mon, 13 Jun 2005, Greg Knaddison wrote:
On 6/13/05, Robin Mordasiewicz robin@bullseye.tv wrote:
ok, thanks. I have played around a bit and it seems that I can narrow it down to certain repositories causing more problems. It seems that DAG and Dries repositories work flawlessly, but atrpms causes alot of conflicts. The kde-redhat repo is only causing one small conflict, but if I choose not to install kde at kickstart time it works ok.
Oh, um, yeah, that. http://dag.wieers.com/home-made/apt/FAQ.php#D2 What do you need from atrpms that you want to keep it enabled all the time?
well I do not need it to be enabled all the time but I am building a setup where I mirror the rep, and kickstart my client machines. I do not want to have to go changing the clients. When I get nearer to production I will take a snapshot of the various reps and then just locally fix the conflicts. I will only update my master yum server with tested changes, but all my clients will have the reps enabled for when I do make changes to the local mirror.
-
Greg Knaddison -
Robin Mordasiewicz