Hello all!
I've recently started using the priorities plugin as part of my best practices. It's very effective, and prevents nasty things from happening (like atrpms upgrading python and disabling yum.)
I'm wondering if there's a simple and elegant way to allow package-name-based exclusions. For example: For my mysql cluster, I'd prefer to have the latest mysql and mysql-server packages which I can get from utterramblings (Thanks Jason!), however, to do so while using the priorities plugin, I'd need to make that repo an equal priority with base, so that it'll upgrade.
I've worked around the problem by creating a duplicate repo with the exceptions as an includepkg and a priority equal to that of base, but it seems less than elegant, and I know it results in double the internet traffic for the repo mirror, which is less than friendly.
Does anyone know if there's a more elegant way to deal with this issue, or might this be an appropriate feature request for the plugin developer?
Sincerely,
Jacob Leaver Sr. System Administrator ReachONE Internet
On Wed, May 07, 2008 at 07:54:11AM -0700, jleaver+centos@reachone.com enlightened us:
I've recently started using the priorities plugin as part of my best practices. It's very effective, and prevents nasty things from happening (like atrpms upgrading python and disabling yum.)
I'm wondering if there's a simple and elegant way to allow package-name-based exclusions. For example: For my mysql cluster, I'd prefer to have the latest mysql and mysql-server packages which I can get from utterramblings (Thanks Jason!), however, to do so while using the priorities plugin, I'd need to make that repo an equal priority with base, so that it'll upgrade.
I've worked around the problem by creating a duplicate repo with the exceptions as an includepkg and a priority equal to that of base, but it seems less than elegant, and I know it results in double the internet traffic for the repo mirror, which is less than friendly.
Does anyone know if there's a more elegant way to deal with this issue, or might this be an appropriate feature request for the plugin developer?
Why not just exclude mysql from the base and updates repos of your distro? If they are not there, they don't need protected/prioritized and the other repo will win.
Matt
Matt Hyclak wrote:
On Wed, May 07, 2008 at 07:54:11AM -0700, jleaver+centos@reachone.com enlightened us:
I've recently started using the priorities plugin as part of my best practices. It's very effective, and prevents nasty things from happening (like atrpms upgrading python and disabling yum.)
I'm wondering if there's a simple and elegant way to allow package-name-based exclusions. For example: For my mysql cluster, I'd prefer to have the latest mysql and mysql-server packages which I can get from utterramblings (Thanks Jason!), however, to do so while using the priorities plugin, I'd need to make that repo an equal priority with base, so that it'll upgrade.
I've worked around the problem by creating a duplicate repo with the exceptions as an includepkg and a priority equal to that of base, but it seems less than elegant, and I know it results in double the internet traffic for the repo mirror, which is less than friendly.
Does anyone know if there's a more elegant way to deal with this issue, or might this be an appropriate feature request for the plugin developer?
Why not just exclude mysql from the base and updates repos of your distro? If they are not there, they don't need protected/prioritized and the other repo will win.
Matt
Hahahaha! That's awesome, I was so busy looking at it from one angle, I never considered the other. That'll work nicely, thanks.
Jacob
On Wed, May 07, 2008 at 07:54:11AM -0700, jleaver+centos@reachone.com wrote:
I've recently started using the priorities plugin as part of my best practices. It's very effective, and prevents nasty things from happening (like atrpms upgrading python and disabling yum.)
When did ATrpms replace python and I didn't notice?
Axel Thimm wrote:
On Wed, May 07, 2008 at 07:54:11AM -0700, jleaver+centos@reachone.com wrote:
I've recently started using the priorities plugin as part of my best practices. It's very effective, and prevents nasty things from happening (like atrpms upgrading python and disabling yum.)
When did ATrpms replace python and I didn't notice?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Er... I don't have exact dates, it was last year, and a rash of my servers all figured they oughtta get new python, yum, and rpms from the atrpms repo. Only, they botched it, and I had to manually downgrade. Not sure why. Sorry, no intention to bash atrpms! I use the repo extensively for your lovely amavisd-new & friends stack, cpan rpms, and other stuffs. I should have been less general.
Sincerely,
Jacob
On Wed, May 07, 2008 at 10:38:55AM -0700, jleaver+centos@reachone.com wrote:
Axel Thimm wrote:
On Wed, May 07, 2008 at 07:54:11AM -0700, jleaver+centos@reachone.com wrote:
I've recently started using the priorities plugin as part of my best practices. It's very effective, and prevents nasty things from happening (like atrpms upgrading python and disabling yum.)
When did ATrpms replace python and I didn't notice?
Er... I don't have exact dates, it was last year, and a rash of my servers all figured they oughtta get new python, yum, and rpms from the atrpms repo. Only, they botched it, and I had to manually downgrade. Not sure why. Sorry, no intention to bash atrpms! I use the repo extensively for your lovely amavisd-new & friends stack, cpan rpms, and other stuffs. I should have been less general.
Well my question was rhetorical - ATrpms never replaced python packages. Furthermore there have never been amavisd-new and friends on ATrpms ever, so maybe you are confusing ATrpms and another repo?
-
Axel Thimm -
jleaver+centos＠reachone.com -
Matt Hyclak