<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 30, 2014 at 11:32 PM, Dan Kenigsberg <span dir="ltr"><<a href="mailto:danken@redhat.com" target="_blank">danken@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Wed, Apr 30, 2014 at 07:57:32PM +0200, Vinzenz Feenstra wrote:<br>
><br>
> Due to some confusion around how alternatives worked, I screwed up the<br>
> list of packages here. I've updated it below. I'll give it a few<br>
> more days before filing the actual bugs.<br>
><br>
> On Wed, Apr 23, 2014 at 4:59 PM, Andrew Lutomirski <<a href="mailto:luto@mit.edu">luto@mit.edu</a>> wrote:<br>
> > Hi everyone-<br>
> ><br>
> > This is a notice in accordance with the mass bug filing procedure.<br>
> ><br>
> > A number of packages install systemd units and enable them<br>
> > automatically. They should not. Please update these packages to use the<br>
> > macroized scriptlet<br>
> > (<a href="https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd" target="_blank">https://fedoraproject.org/wiki/Packaging:ScriptletSnippets#Systemd</a>).<br>
> ><br>
> > If your package has an exception from FESCo permitting it to enable<br>
> > itself, please make sure that the service in question is listed in the<br>
> > appropriate preset file.<br>
> ><br>
> > There is a general exception described here:<br>
> ><br>
> > <a href="https://fedoraproject.org/wiki/Starting_services_by_default" target="_blank">https://fedoraproject.org/wiki/Starting_services_by_default</a><br>
> ><br>
> > If your package falls under the general exception, then it is possible<br>
> > that no change is required. Nevertheless, if you are relying on the<br>
> > exception, please make sure that your rpm scripts are sensible. The<br>
> > exception is:<br>
> ><br>
> > In addition, any service which does not remain persistent on the<br>
> > system (aka, it "runs once then goes away"), does not listen to<br>
> > incoming connections during initialization, and does not require<br>
> > configuration to be functional may be enabled by default (but is not<br>
> > required to do so). An example of "runs once then goes away" service<br>
> > is iptables.<br>
> ><br>
> > Given that this issue can affect Fedora 20 users who install your<br>
> > package as a dependency, these bugs should be fixed in Fedora 20 and<br>
> > Rawhide.<br>
> ><br>
> > The tracker bug is here:<br>
> ><br>
> > <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1090684" target="_blank">https://bugzilla.redhat.com/show_bug.cgi?id=1090684</a><br>
> ><br>
> > I created it early because three of the bugs are pre-existing. Next<br>
> > week, I'll file bugs against the packages below. If you fix your<br>
> > package in the mean time, please let me know.<br>
> ><br>
> > After three weeks, provenpackagers may step in and fix these issues.<br>
> ><br>
<br>
</div></div>Vinzenz, I suppose that your main point is this part of the list<br>
<br>
> vdsm<br></blockquote><div><br></div><div>Yes sorry for not being more specific, I forwarded that from on my mobile and did think it's to important to forget about ;-)</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Douglas/Yaniv - can infra take care of this?<br>
</blockquote></div><br></div></div>