Description of problem: From bug 654047 (see comment 12): ''' The spec should have fixed these other problems: * Use %global for the top-level definitions instead of %define * Package should require php >= 5.2 as noted in its Drupal .info file -- although that's automatically met in Fedora it's not necessarily met elsewhere (e.g. EL-5). * Package should require drupal6-ctools * Package should require drupal6-job_scheduler (not available in Rawhide or F14, also not packaged as far as I know) I'm reopening this bug since I can't remember how we deal with packages that have been reviewed and added to git prematurely. ''' This package now exists in a broken fashion in Rawhide, and should not be built or pushed elsewhere until these problems are fixed. Specifically, the job_scheduler module is required for this package, and will need to be packaged, reviewed and accepted for this one to be properly fixed.
Oh yes, I have forgotten. I have just submitted the job_scheduler package. https://bugzilla.redhat.com/show_bug.cgi?id=659005
The job_scheduler review is now approved in bug 659005.
drupal6-feeds-1.0-0.2.beta10.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/drupal6-feeds-1.0-0.2.beta10.fc14
Update has moved because of editing: https://admin.fedoraproject.org/updates/drupal6-feeds-1.0-0.4.beta10.fc14
drupal6-feeds-1.0-0.4.beta10.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update drupal6-feeds'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/drupal6-feeds-1.0-0.4.beta10.fc14
Is this getting pushed to stable at some point, so we can close this last bug against our tracker?
I think this is stable, I am going to push it into stable repository. We can close this because Feeds is working flawlessly our testing/staging instance.
Great. Once the package gets pushed to stable, the bug will be closed by the updates system automatically, no need to worry about it. Thanks Peter!