On Sun, Dec 19, 2010 at 17:16:46 +, Chris Butler wrote:
> If it's any use, I ran a quick "git bisect" on the upstream source, and
> discovered the commit which seems to have fixed the problem:
>
> https://github.com/flori/json/commit/dd06e48aa414674f52e81f9cdc7836b6456c04f8
>
> However, this
On Sun, Dec 19, 2010 at 03:39:22PM +, Adam D. Barratt wrote:
> On Sun, 2010-12-19 at 14:53 +, Chris Butler wrote:
> > On Sun, Nov 14, 2010 at 08:33:01PM -0700, Joshua Timberman wrote:
> > > The JSON gem has a history of issues, and while it seems that 1.1.9 may
> > > otherwise be stable, it
On Sun, 2010-12-19 at 14:53 +, Chris Butler wrote:
> On Sun, Nov 14, 2010 at 08:33:01PM -0700, Joshua Timberman wrote:
> > The JSON gem has a history of issues, and while it seems that 1.1.9 may
> > otherwise be stable, it is a year old and has a lot of improvements. So
> > far I have not seen
Apologies for the delay; I forgot to subscribe to the bug and therefore
missed your response.
On Sat, Nov 13, 2010 at 04:27:51PM -0700, Joshua Timberman wrote:
> Ohai is required for Chef. Is this a localization issue that can be fixed
> upstream in Ohai?
Well chef was not in lenny either, and h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello Chris!
Ohai is required for Chef. Is this a localization issue that can be fixed
upstream in Ohai?
Or is it in fact a bug in older version of JSON available in Debian? This is
the first I've heard of the issue with Ohai.
-BEGIN PGP SIGNAT
5 matches
Mail list logo
