No subject

JSON library internally to resolve these issues. (named PSON for namespace
reasons)

--00504502af8b2931800475e7092f
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Wed, Oct 14, 2009 at 6:15 AM, Micah A=
nderson <span dir=3D"ltr">&lt;<a href=3D"mailto:micah at riseup.net">micah at ris=
eup.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D=
"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
* Nigel Kersten &lt;<a href=3D"mailto:nigel at explanatorygap.net">nigel at expla=
natorygap.net</a>&gt; [2009-10-14 08:39-0400]:<br>
<div class=3D"im">&gt; On Wed, Oct 14, 2009 at 5:30 AM, Micah Anderson &lt;=
<a href=3D"mailto:micah at riseup.net">micah at riseup.net</a>&gt; wrote:<br>
&gt;<br>
&gt; &gt; * Andrew Pollock &lt;<a href=3D"mailto:apollock at debian.org">apoll=
ock at debian.org</a>&gt; [2009-09-26 17:55-0400]:<br>
&gt; &gt; &gt; On Sat, Sep 26, 2009 at 11:48:21AM -0400, Micah Anderson wro=
te:<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; I&#39;m really glad this got sorted out, I haven&#39;t =
tried to go through the<br>
&gt; &gt; &gt; &gt; same steps you have yet, so my brain isn&#39;t fully wr=
apped around how<br>
&gt; &gt; this<br>
&gt; &gt; &gt; &gt; works, or why. I&#39;m afraid that when I do need to do=
 this, I will have<br>
&gt; &gt; to<br>
&gt; &gt; &gt; &gt; dig through the mailing list archives and try to recons=
truct the steps<br>
&gt; &gt; &gt; &gt; based on what folks reported here... it might be better=
 if we<br>
&gt; &gt; maintained<br>
&gt; &gt; &gt; &gt; a page to preserve these details, maybe on <a href=3D"h=
ttp://wiki.debian.org" target=3D"_blank">wiki.debian.org</a>?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Yes, we should definitely maintain some documentation, eithe=
r on the Wiki<br>
&gt; &gt; or<br>
&gt; &gt; &gt; on the Alioth project page.<br>
&gt; &gt;<br>
&gt; &gt; This was a minor digression into the need for documentation of th=
e git<br>
&gt; &gt; procedures of the package, I&#39;m sorry if it distracted from th=
e main<br>
&gt; &gt; point, which was getting 0.25 uploaded.<br>
&gt; &gt;<br>
&gt; &gt; What, if anything, are we waiting on at this point?<br>
&gt; &gt;<br>
&gt;<br>
&gt; 0.25.1, which will be very very soon, within days.<br>
<br>
</div>Sounds reasonable.<br>
<div class=3D"im"><br>
&gt; There was a potential data corruption bug that I was very concerned ab=
out in<br>
&gt; 0.25.0, but it&#39;s looking like that&#39;s actually doing more corre=
ct erb<br>
&gt; template evaluation than 0.24.x was.<br>
<br>
</div>Do you have a reference to this? if its not an actual bug, I&#39;m go=
ing to<br>
want to check my templates before I corrupt things :) In fact, it might<br>
be worth adding to NEWS?<br></blockquote></div><br><div>The bug history is =
a little confusing, but it gets clearer towards the end.</div><div><br></di=
v><div><a href=3D"http://projects.reductivelabs.com/issues/2615">http://pro=
jects.reductivelabs.com/issues/2615</a></div>
<div><br></div><div>There are a bunch of other associated bugs, but it turn=
s out that the problem has to do with bugs in serialization libraries or di=
fferences between versions.</div><div><br></div><div>From my understanding,=
 0.25.1 is where Puppet is planning to ship it&#39;s own JSON library inter=
nally to resolve these issues. (named PSON for namespace reasons)</div>
<div><br></div><div><br></div>

--00504502af8b2931800475e7092f--