Hi Rob, 2012/1/6 Rob Hamerling <[email protected]>
> > There is something wrong with the latest JalPack beta somewhere. I cannot > pinpoint what exactly. These are my observations: > Let's remember there were commits since last jallib-pack generation ! > > I count 871 samples in the Jalpack sample directory, and 1035 in Jallib, > which means unreleased: 1035-871 -> 164. But my TORELEASE analysis says > unreleased samples: 72 + 48 -> 120. So 44 samples missing in Jalpack. > "grep sample" in TORELEASE I used for beta gives 871 samples. It now has 931 samples, on r2903, 912, etc... I guess this is something about not comparing the same revision > > A compare of the sample directories of Jalpack and Jallib shows > that many samples in Jalpack are old: example 10f200_blink.jal 15 nov. > resp. 7 dec., while you created this Jalpack 27 dec. > I'm not surprised with this one. Jallib-pack embeds r2760. Sample was updated on 29 dec, after pack generation. > > I could write a script for a more detailed analysis, but that would be a > waste of time if you can find the cause easily. I'll generate a new beta, note the revision, and keep the logs for the record. Will you check again ? On first/quick analisys I'm pretty sure there's no problem around jallib-pack generation. Cheers, Seb -- You received this message because you are subscribed to the Google Groups "jallib" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
