Russ Allbery <r...@debian.org> writes: > The problem is mildly obscure (many Puppet manifests, including very > complex and non-trivial ones, will never trigger this error condition) > and absolutely does not warrant removing the package from testing. In > fact, I'm tempted to downgrade it to important again, although if > there is a tested upstream fix, I'd be in favor of applying it for > wheezy.
There is now an upstream fix for this issue at https://github.com/puppetlabs/puppet/commit/e94732b, which has been accepted and merged into the puppet 2.7.x branch. 4 of the 5 commits in the merge apply to 2.7.18, while the final one fixes a test in 2.7.20. The commit that actually fixes the bug is at https://github.com/puppetlabs/puppet/commit/1b0e812ad9e33b3cc148fac30a28490f60f40c63, while the other 3 rewrites the unit tests. The patches apply, and the tests run fine. All that remains is to see it actually work in practice, before I upload 2.7.18-4, and ask for a freeze exemption. -- Stig Sandbeck Mathisen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
