Not sure if this is the right place to bring this up, but attempting to install rpmdevtools on a RHEL 5.3 beta machine fails because of a file conflict - /usr/lib/rpm/check-rpaths-worker is now included as part of rpm-build, and need not be included in rpmdevtools. Fun thing is this is obviously an incompatible change - on RHEL version <= 5.3, it's there, but > 5.3 it's not. Not sure how to handle this in EPEL-land..

I can raise an issue in IT, but not sure where that will go (I'm bcc'ing my TAM and cc'ing John Poelstra on this so maybe they can give me some guidance). This late in the 5.3 game, not sure what can change at this point (or if this has already changed). Agreed that we need something more general than this specific instance though, and something that works for the community - not just those that happen to be large RH customers. We need some sort of visibility as to what's coming in the next point release prior to the public beta, and some sort of input as to those changes in what might be incompatible to EPEL (even internally running repoclosure against new RHEL+EPEL would work IMHO) Enough ranting for tonight :) On 12/15/08, Stephen John Smoogen <smooge(a)gmail.com&gt; wrote: > On Mon, Dec 15, 2008 at 3:07 PM, Jon Stanley <jonstanley(a)gmail.com&gt; wrote: >> Not sure if this is the right place to bring this up, but attempting >> to install rpmdevtools on a RHEL 5.3 beta machine fails because of a >> file conflict - /usr/lib/rpm/check-rpaths-worker is now included as >> part of rpm-build, and need not be included in rpmdevtools. >> >> Fun thing is this is obviously an incompatible change - on RHEL >> version <= 5.3, it's there, but > 5.3 it's not. Not sure how to >> handle this in EPEL-land.. > > Ugh.. file a bug and tell them to fix their crap :)[TM]? On the other > hand, this is one of those things I think we have run into with each > 5.x release. I think we need to work on a more general plan... since > fixing it on our side breaks 5.2 people > > > -- > Stephen J Smoogen. -- BSD/GNU/Linux > How far that little candle throws his beams! So shines a good deed > in a naughty world. = Shakespeare. "The Merchant of Venice" > > _______________________________________________ > epel-devel-list mailing list > epel-devel-list(a)redhat.com > https://www.redhat.com/mailman/listinfo/epel-devel-list

We had a heads up on this quite awhile ago, https://bugzilla.redhat.com/show_bug.cgi?id=466939 there is plans to fix this when RHEL 5.3 is released.

On Fri, 26 Dec 2008 14:52:49 +0200 Ville Skyttä <ville.skytta(a)iki.fi&gt; wrote: > > When these are ready for the EL-5 build, how/when should I do the > build? Just do it when possible, and let the repo masters know that > it shouldn't be pushed anywhere before EL 5.3 is out? Or push it to > testing even before 5.3 is out, and to stable as simultaneously as > possible with 5.3 goes GA? Or should I just tag but hold building it > until ...? Well, it's up to you... I would personally suggest waiting until 5.3 is out, then building and pushing to testing, wait and if all looks ok push to stable.

On Fri, Dec 26, 2008 at 4:44 PM, Ville Skyttä <ville.skytta(a)iki.fi&gt; wrote: > That's what I'd do for a usual less crucial update, but in this case, as > mentioned in bug 466939, having an old rpmdevtools release installed will > break/prevent upgrading to 5.3 if the new one is not available. How about we simply apply the patch that Panu suggested in the current version so the conflict is gone (i.e. identical md5sum between RHEL rpm-build and EPEL rpmdevtools), and wait to push this new version until after 5.3.

What else has changed?