Stefanos Harhalakis <v...@v13.gr> writes: > I'm changing the severity of this bug since I believe that it is a huge > issue (with a tiny fix).
I'm sorry that this bug is affecting you, and I'm sorry that it's frustrating! However, setting the bug severity to grave indicates that you believe Puppet should be removed from the upcoming stable release *entirely* if the bug cannot be fixed before the release. I don't think this is appropriate, nor do I think this bug, however serious for your installation, rises to the level of release-critical. The typical Puppet installation uses the Puppet CA, which doesn't have this problem. This makes it an issue that only seriously affects some installations but which does not render the package unusable for other users, which is the definition of important, not grave. I'm going to set the severity back to important, which in no way indicates that I don't think the bug should be fixed, but which does indicate that I think it's reasonable to release Puppet in the upcoming Debian stable release even if this bug is not fixed. (My guess is that the best approach for dealing with this problem will be to use a backported version with a fix once upstream decides how to fix it without reintroducing a security vulnerability.) -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org