Description of problem: Let's get the ball rolling on this one... http://fedoraproject.org/wiki/Features/SysVtoSystemd https://fedoraproject.org/wiki/Packaging:Guidelines:Systemd https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Martin, any objection to my making this change?
Would be great, no objections at all! I just haven't gotten to it yet. So far I have only talked to upstream whether they want systemd support there. The outcome is that for now this should stay downstream.
Cool, one other concern. This requires postgresql-server, and the init script patch assumes that the DB is local. Would it not be better to decouple the two, to both simplify packaging and allow a remote DB?
Yeah, it certainly would. I am not the author of the init script, so I am not sure what the reasoning was. Perhaps there are some hidden problems there.
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
Given that I have left the project and a new individual may or may not continue with systemd integration in the project by submitting new feature following whatever demands FPC and FESCo might have and thus new units in the process I'm closing this and all remaining bugs I had submitted for this particular feature as WONTFIX