On Tue, Mar 6, 2012 at 4:39 PM, Nicolas Chauvet <kwizart(a)gmail.com&gt; wrote: https://bugzilla.rpmfusion.org/show_bug.cgi?id=1712#c17 I wouldn't consolidate the versions. F16 would stay 0.3.8 and F17+ would stay 0.4.0. It would just be a SysV -> systemd transition. Richard

On Tue, Mar 6, 2012 at 4:45 PM, Nicolas Chauvet <kwizart(a)gmail.com&gt; wrote: I wonder sometimes if it's your goal to be unhelpful in as few words as possible. Do you go out of your way to be this acidic or does it just come naturally? It's not my intention to start an argument here, but ignoring your comments is becoming increasingly difficult. If you want to run everything by yourself then just tell me so I can get all of my packages assigned to you. If not, I suggest you at least try to take the path of a teacher instead of looking down on everyone who doesn't know as much as you. Since I'm not getting paid for this, I'm definitely not getting paid enough to put up with this shit. Back to the subject at hand, the bug is that for some reason the LSB entry in the SysV file says there should be a PID file but I can not find where, if at all, in the akmods script it's created. Sure I could just remove the PID entry but since this is F16 we're talking about I thought it would be nice to use a native systemd service file since I'm not sure what issues the SysV compatibility can cause in this type of service, which is not a daemon. Richard