- From: Joshua Timberman <
>
- To:
- Subject: [chef] Re: Re: bluepill error uninitialized constant Daemonization (NameError)
- Date: Sat, 18 Feb 2012 15:03:46 -0700
- Authentication-results: mr.google.com; spf=pass (google.com: domain of
designates 10.182.37.99 as permitted sender)
On Sat, Feb 18, 2012 at 6:15 AM, Akzhan Abdulin
<
>
wrote:
>
This is problem that refs bluepill/131, bluepill/132, bluepill/136 (Author
>
of Daemons gem have changed undocumented API that was used by bluepill).
>
>
Should be worarounded by bluepill 0.56 that restricts using of daemons gem.
Per the daemons gem author:
Date: 2012-02-17 12:31
Sender: Thomas Uehlinger
While the Daemonize module was never part of daemons' API (for
example no documentation refers to it), I agree that the change
of name was unnecessary. Therefore I had immediately reverted
that change and released 1.1.8. bluepill should therefore work
without problems with 1.1.8. After now also having yanked 1.1.7,
I don't see a reason to bump to 1.2 as there are now no breaking
gems in 1.1.*.
Via its tracker:
http://rubyforge.org/tracker/index.php?func=detail&aid=29516&group_id=524&atid=2084
I posted this to the bluepill issue as well.
--
Opscode, Inc
Joshua Timberman, Technical Program Manager
IRC, Skype, Twitter, Github: jtimberman
Archive powered by MHonArc 2.6.16.