Extras got mad that we put liboil into Core without telling them, and they proceeded to do an FE5 update which overrided our FC5 package. I tried to re-merge their changes into Core, but it fails to build on s390 again. The patch in core needs to be refactored to work with what looks like macro changes. Please fix this in FC-5 and devel, and issue a FC5 update.
I'll have a look at this...
Built, I'll push it into updates-testing later today.
liboil-0.3.8-1.fc5 has been pushed for FC4, which should resolve this issue. If these problems are still present in this version, then please make note of it in this bug report.
(ignore comment 3 which is bogus)
Warren : You should avoid writing things like "got mad". You indeed rebuilt liboil for Core without telling me, the current Extras maintainer. First problem, but nothing major, s*it happens. The other problem is that I didn't notice, and with FC5's release getting closer and liboil 0.3.7 not building cleanly on PPC, I needed to get it rebuilt somehow. After reporting the issue in the liboil bugzilla, I pushed out a package based on the current CVS that fixed the problem (that 0.3.7.1 problem). It is then that people realized that a liboil package had appeared in Extras which was newer than the one in Core. They didn't go mad. They just wanted to understand what happened in order to prevent this problem from happening again, which is the right thing to do. This case is different than the one where someone pushes a package in Core without realizing that it was already available in Extras. You took the spec file from Extras, doing only a small part of what should have been done at that point. After this incident, you deleted the devel CVS branch for liboil in Extras, which again is the right thing to do, but you did not answer to any of the mailing-list messages related to the issue, nor send me a private email about it. Please, next time remember to notify the Extras packager first, then delete the devel Extras branch, and only then import and rebuild the package into Core. This should definitely be a strict policy to be followed when adding packages to Core. Also, I really appreciate quick private explanations, even one-liners. A lot more than reading the first paragraph of this bug report for instance, where you seem to identify yourself as Core and Extras as the guys who went mad... (re-read it, you'll understand I'm sure).
I apologize, this has been a huge oversight on my part. I imported liboil into Core on behalf of the actual owner because some component required it. But at the time I was rushing because I was way too stressed out with too many things going on. I will be more careful to notify people in the proper way in the future.
If things have been taken care of (and I think they have), this bug could probably be closed now...