The current version of fftw in Fedora is 3.2.1, please update it to 3.2.2. Also, please update fftw in EPEL to 3.2.2. The version in EPEL is currently 3.1.2; the 3.2 series brings significant speedups. According to bug 471772, the fftw 3.2 series is compatible with the 3.1 series, so no other package rebuild should be necessary.
Created attachment 381165 [details] Proposed patch
You can take the EPEL branch of the package if you like, I have no interest in it.
I've committed your patch to the devel/ branch (next time, please use a unified diff so it can be applied), and it's now building for F13. When that succeeds I'll start it for F-12. Thanks!
(In reply to comment #3) > I've committed your patch to the devel/ branch (next time, please use a unified > diff so it can be applied), and it's now building for F13. Whoops, looks like I forgot. But still, there's no problem in applying the patch: $ wget "http://cvs.fedoraproject.org/viewvc/rpms/fftw/devel/fftw.spec?revision=1.27&view=co" -O fftw.spec $ patch fftw.spec fftw.spec.patch results in the patched file. >When that succeeds I'll start it for F-12. > > Thanks! No problem! (In reply to comment #2) > You can take the EPEL branch of the package if you like, I have no interest in > it. OK, I will.
Weird, I guess I'm not familiar enough with patch, sorry. (The 'patch < foo.patch' invocation told me the input was garbage.) Ok, fftw-3.2.2 is build in F-13.
Hmm, 3.1.2 had a %check phase, but new spec files don't have it anymore.. Why?
Don't know.
fftw-3.2.2-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/fftw-3.2.2-1.fc12
OK, pushing 3.2.2-2 in a few minutes with added %check phase and a few other minor cosmetical fixes.
fftw-3.2.2-1.el5 has been submitted as an update for Fedora EPEL 5. http://admin.fedoraproject.org/updates/fftw-3.2.2-1.el5
fftw-3.2.2-1.el4 has been submitted as an update for Fedora EPEL 4. http://admin.fedoraproject.org/updates/fftw-3.2.2-1.el4
I object to the fftw3-> fftw rename here, as (primary) EPEL maintainer.
(In reply to comment #12) > I object to the fftw3-> fftw rename here, as (primary) EPEL maintainer. Conrad asked me to take over the EPEL branch, so I assumed I was given full control over it. If you still want to maintain the EPEL branch (and push the 3.2 branch in it), I will step back. As I stated in the mail and the changelog, the current name does not obey the Package Naming Guidelines. There is no difference in the functionality: "yum install fftw(-devel)" and "yum install fftw3(-devel)" both evaluate to the same thing. So I really don't see the problem: the rpmforge compatibility is still there.
I was already maintainer of the epel branch, Conrad may have just forgotten. :) While the name is strictly out of concordance with the guidelines, if you insist, I'll ask for a new fftw3/ cvs module to be created. But, I think that's beyond what's required here, and would strongly prefer to keep things together in the same fftw/ module. See also, * Tue Jul 10 2007 Rex Dieter <rdieter[AT]fedoraproject.org> 3.1.2-4 - (re)name -> fftw3 (epel-only, for rpmforge compatibility, #246004) For which your change is undoing. rpmforge repo has a long history of providing this as fftw3, and it's developers and users have a strong desire to keep things so. I named this fftw3 with the desire to maximize repo compatibility.
That all said, I *do* welcome comaintainers to help out whereever possible. Thank you for that. :)
(In reply to comment #14) > rpmforge repo has a long history of providing this as fftw3, and it's > developers and users have a strong desire to keep things so. I named this > fftw3 with the desire to maximize repo compatibility. Yes, but that's really going against the guidelines, see http://fedoraproject.org/wiki/Packaging/NamingGuidelines#Spec_file_name Having an Obsoletes: and Provides fftw3(-devel) is not, and it provides a clean upgrade path for rpmforge compatibility. What harm is there *really* about the epel package being called fftw instead of fftw3, when everything written against the fftw3 package names still work as before?
Honestly, there isn't any *real* harm in the rename, but it was done at request of rpmforge's request. Please revisit the rpmforge mailing list flames if you want, else please take my word for it.
Sorry, Rex is correct, I didn't remember he was the EPEL maintainer. As always, pkgdb is the authoritative source :).
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle. Changing version to '13'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
fftw-3.2.2-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.