python-pyspf-2.0.3-1.fc8.src.rpm Failed To Build From Source
Created attachment 300760 [details]
root.log for i386
Created attachment 300761 [details]
build.log for i386
Created attachment 300762 [details]
root.log for x86_64
Created attachment 300763 [details]
build.log for x86_64
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
I am the upstream maintainer of pyspf. It builds on F9 after adding a line for the egg.info (that python2.5 generates) in the spec file. I have built packages for F9 in my private repo for the latest (2.0.5) source. I have signed up with fedoraproject.org, and I'm supposed to email the package owner being trying to update it. I find no email in the info for jafo, so I'm posting here. I'll keep working on how to submit a python-pyspf-2.0.4 for F9, but maybe someone can give me some pointers. I'm an old hand at RPM: started with RPM for AIX, but new to Fedora. There is also an important update for python-pydns (and same egg.info build error).
This package has Failed to Build From Source for many months. Per
http://fedoraproject.org/wiki/FTBFS, this package is now proposed for
removal from the distribution. Please address this FTBFS bug
immediately, or this package will be removed from the distribution
within the next few weeks.
Thank you for your continued contributions to Fedora, and your
commitment to ensuring Fedora packages remain buildable from source
Created attachment 315940 [details]
python-pyspf spec that compiles on Fedora-9
I am still trying to find out the procedure for getting updates in.
Created attachment 315941 [details]
Fixed in rawhide:
Stuart, I suggest that you start the non-responsive maintainer procedure for this maintainer:
Stuart: Are you interested in taking over this, or do you want me to push the new version out?
In case it wasn't clear from Comment #10, I already pushed the new version to rawhide.
Yes, I am interested in taking over. I push out packages on sourceforge and freshmeat, and I am brushing up on the quality control procedures on fedora (like rpmlint). I think the next step is to get a sponsor to become a fedora packager.
Stuart: I'd be happy to look at sponsoring you... do you have any other packages you intend to submit? Or would you be interested in doing some 'pre-reviews' of waiting packages in the review queue to show your understanding of the guidelines?
In addition to pyspf and pydns, which Sean is already handling (did you submit pydns-2.3.3? It has the port randomization everyone wants - although it doesn't affect any know pydns applications), I have pymilter - which lets you write sendmail / postfix milters. The pymilter.spec file also builds 'milter' and 'milter-spf' for --target=noarch. This is likely a naming issue, and I'm not sure if building different packages depending on target is kosher in fedora project. I am slowly learning the ropes.
I believe I remember reading about a place to submit fedora spec files for merciless criticism, but I'll run rpmlint and stuff first.
And yes, I would like a sponsor. I can take over pyspf and pydns if Sean would like to move on. I thank him for getting them into fedora.
I'm afraid I haven't had much attention for keeping up with all the different community projects I've been involved with lately, so I'm running pretty behind.
One thing I want to mention on pymilter is that there seems to be an issue with Fedora 9 on x86_64 in the sendmail package. I don't recall the exact details, but the problem basically was that the sendmail package didn't properly include the milter library under x86_64, which caused pymilter to fail to build. I spent some time trying to get this resolved, but in the end I had to build the library by hand, statically IIRC, and then manually copy that into place and build the pymilter RPM.