Bug#605044: (cfengine3) raising severity on 602404 and 605044 to grave
On Fri, Jan 14, 2011 at 02:35:04PM +0100, Julien Cristau wrote: > That doesn't sound grave to me. Just because you have to modify > /etc/init.d/cfengine3 instead of /etc/default/cfengine3 doesn't make the > package unusable, does it? Hi Julien, thanks for your quick answer; I thought this could be a problem because we are shipping /etc/default/cfengine3 and since you have that file, as a user, you expect that once you modify it, then it will work exactly as the other files in /etc/default; basically we are not doing what we are promising to do. As you said, it doesn't make the package unusable but it is a problem for the user; I'm happy to set the severity of this bug back to important if you want and we will leave things as they are on squeeze; the upload is just a 6 lines change though (3 in cfengine3.default and 3 in cfengine3.init) and it is already ready. Let me know your preference and I'll proceed accordingly. Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#605044: (cfengine3) raising severity on 602404 and 605044 to grave
severity 602404 grave severity 605044 grave thanks Hi, I'm raising the severity of those two bugs to grave because, despite being fixed in experimental, they should also be fixed in squeeze, the rationale is that /etc/default/cfengine3 is unusable so the user cannot specify any option to start the daemons. Those are the bugs: 602404 cfengine3 package uses wrongly names variables in /etc/default/cfengine 605044 /etc/init.d/cfengine3: unquoted variables The result of #602404 is that if the user specify what startup opts wants, those will never be used because /etc/init.d/cfengine3 is using other variable names. The result of #605044 is that, once #602404 is fixed, the user still won't be able to add full options because the variables in /etc/init.d/cfengine3 are unquoted so spaces cannot be used. I'm CC'ing debian-release@l.d.o because since I will submit an unblock request for the new package (3.0.5+dfsg-2), they will have some background on the issue. Cheers Antonio -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
