On Thu, Jun 20, 2013 at 1:56 PM, Matthias Runge <mrunge@redhat.com> wrote:

On 20/06/13 13:50, Sandro "red" Mathys wrote:
> Great, thanks for the quick reply and the quick fix. Still thinking
> yum priorities are bad and should be removed completely from RDO
> (RHOS is a different story) but if only directly openstack related
> packages remain in the repo, it shouldn't matter anyway. -- Sandro
>
Why do you think priorities are bad?

Because they are patronizing the user, relatively hard to overcome and situations where they seem necessary should be avoided in general.

They give us the freedom to
directly steer combinations of packages, thus as overriding packages
from elsewhere.

As written in the first post in this thread: since RDO strives to always be (equal to or more likely) ahead of RHEL and EPEL, such an override should never be necessary. And overriding "packages from _elsewhere_" should not be considered necessary as no other repos are (nor should they be) supported.

Please keep in mind, this won't happen that often, but still there might
be cases where this is desired.

Like in what case? When will RDO ever want an older version of something than what is in RHEL / EPEL?

The only thing I can possibly come up with right now are the kernel and other tools where new networking stuff (netns, maybe more) was enabled ahead of time but I sure hope those changes make it back into RHEL with the next kernel update there. Or if not, that new RHEL kernels are again re-built with those patches for RDO as well to avoid security holes.

-- Sandro