[DRE-maint] Bug#778303: chef: Memory leak
Antonio Terceiro
terceiro at debian.org
Sun Feb 22 02:16:26 UTC 2015
Hello Piotr,
On Fri, Feb 13, 2015 at 03:56:38PM +0100, Piotr Pańczyk wrote:
> Hello Antonio,
>
> On 13.02.2015 14:29, Antonio Terceiro wrote:
> >Would you by any chance be able to identify the upstream commit that
> >introduced the fix? If so, I can try backporting that and releasing a
> >stable update.
> I think this is it:
> https://github.com/chef/chef/pull/291
I was looking at this, and there a few issues:
- that commit does not apply clean on the wheezy chef tree.
- there are are a few other commits in the upstream history related to
the forking behaviour, so I think there were a few issues with this
it. I have the the impression that it is too risky to pull this into a
stable branch, and I won't have to spare cycles to handle the breakage
that will probably come.
- I only use chef-solo, so testing this would a little difficult for me.
--
Antonio Terceiro <terceiro at debian.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-ruby-extras-maintainers/attachments/20150221/be8c8b74/attachment.sig>
More information about the Pkg-ruby-extras-maintainers
mailing list