python-numeric in EPEL5 newer then in RHEL5
I have retired the EL5 branch following the procedure here,
by marking it as dead.package and retiring the branch:
Here is the rel-eng ticket:
Hopefully this will be pushed through soon. Sorry for the
confusion, I got broken dep messages for missing python-numeric
in RHEL/EPEL 6, and I assumed that it was also missing in
RHEL/EPEL 5. I should have checked a bit more.
Ideally bodhi would detect such a situation and prevent things
being pushed. Also it's not super easy to find whether a
package is or is not in RHEL. There's no equivalent of
PackageDB, you have to nose around the SRPM directories,
which seems somewhat suboptimal.
> On Tue, 2011-02-01 at 13:24 -0700, Kevin Fenzi wrote:
> > On Mon, 31 Jan 2011 10:14:23 +0200
> > David Juran <email@example.com> wrote:
> > > Hello.
> > >
> > > Just noticed that python-numeric-24.2 got pushed to EPEL5.
> > > python-numeric (-23.7) is already present in RHEL5 so I believe
> > > the
> > > epel version should (somehow) be un-pushed.
> > I added a note about this to:
> > https://bugzilla.redhat.com/show_bug.cgi?id=664399
> > Hopefully the maintainer will dead.package it and get it blocked.
> > If they don't, I can do so in a while...
> I think it's better done ASAP since any subscriber of RHEL that pulls
> this update will need to take manual steps to revert the process.
> Also, one the dead.package is in place, we probably should send out
> something on epel-announce describing the steps how to get back to a
> supported configuration.
> David Juran
> Sr. Consultant
> Red Hat
epel-devel-list mailing list