I don't believe the numpy rpm should have a "Requires: python-devel" but rather just have "BuildRequires: python-devel"
It's a valid requires with the current packaging see:
With the current packaging it might be a valid requires, doesn't mean its correct. I've created a starting point for a package split here if you/the maintainer wishes to use it as a starting point.
Looks reasonable, but we'll need to make sure that dependent packages, both for Requires and BuildRequires, are set appropriately.
repoquery on F-10 yields:
But I'm not sure how to quickly determine which need f2py and which need numpy.
Suggestions? I mean, I can do it manually if need be, but. . .
Probably the easiest way it to open a bug against each package and get its owner to either update the package if it needs f2py or close the bug as 'NOTABUG'. See 456122 as an example. Then give the package owners a couple week or so to update their packages and push the changes (see the mentioned bug - the changes have long been pushed but still have a number of bugs open).
What's the best way to file bulk bugs?
I have no idea.
(In reply to comment #3)
I did a grep through the runtime scipy codebase and the matplotlib codebase and several scipy .so files reference f2py. I sort of expected that. Let me know when you make the change so I can coordinate the BuildRequires and Requires change for scipy.
I'll just file them individually. It's only 23 packages.
Just discovered python-bugzilla. Looks like it doesn't do Blocks, but I can do that manually.
Thanks to all those that have responded. Given that several haven't and the F11 Final Freeze is only a day away, I'll postpone until afterward, and do this in a new branch for F-12.
Package Change Request
Package Name: numpy
New Branches: F-12
is the form of the provides going to change?
Right now numpy in rawhide provides "f2py" Is that what I should requires to future proof the change? Or is the name of the provides going to change?
Currently numpy Provides f2py. In the new version, numpy-f2py will Provides f2py. Only numpy-f2py will Requires python-devel.
You bring up an interesting point. If all affected packages simply Requires f2py, I can just do the change and close all the bugs.
yep. I have scipy changes ready to commit i just wanted to make sure the form of the provides I need to grab wasn't going to change.
For now I'm just going to BuildRequires and Requires f2py explicitly in scipy. And then the OLPC people will come banging on my door next to figure out how to split up scipy into functional subpackages more effectively.
I assume you meant you would like a early F-11 branch so you could do work in devel that will not go out in F-11? cvs done for that.
You should have a F-11 branch that will go out for F-11, and a devel that will be rawhide that will someday be F-12.
Thanks for both knowing what I really meant and doing it. :)
In CVS. Builds of all sorts are dying in rawide right now, I'll try again tomorrow.
FYI, Peter, I made a slight deviation from your suggested spec. I split out f2py, but didn't make -docs, since the documentation isn't very big.
F-12? I'd still like to see this make F-11. the gnome-python stuff split around F-9 even though there are still dependant packages that aren't closed (see prev example). Also it was only recently that the python-devel dep was actually added as a dep to numpy which would indicate to me most people either don't use f2py, already have the stuff installed, didn't notice it was broken, or don't care :)
On the docs, the only reason I went for the -docs package was because some of the docs were for numpy and some for f2py so it sort of separated it all.
Well, the freeze was supposed to be today, but is being pushed back. The build's not working anyway. If I can get a build for F-12 to work, I'll try it for F-11 and see if it makes it in. If not, it'll go in as an update. If that's not good enough, we can petition for an exception:
Cool. I had my package build in koji as a scratch from mem. I think the freeze is in time for the compose tomorrow morning. Saw a post of fedora-devel to something like that. I think it would be better to get it in if possible so there's some testing time before release, as opposed to straight after release.
My thought process exactly, for N-1 release. We'll see what happens.
Built for F-12/devel and F-11-updates. I'm on the fence about breaking the freeze. Peter, do you have any reason that it would be better to have this in F-11 rather than as an immediate update?
I would like it because it adds quite a bit to the size of the OLPC build which is due to be a F11 Spin. I don't particularly want to have to fork packages for small things like this.
Rel-Eng ticket filed:
This was just approved and tagged into F-11 final. I'll start going through the list of open dependent bugs and trying to determine if any need fp2.
Looks like it's just scipy.
Excellent! Thanks all :-)
I think this is fixed, can it be closed?
I don't see that scipy has been updated. I'll comment on that bug.
All built in rawhide and necessary tag requests submitted.