[Sugar-devel] Are we ready for code freeze?

[Gonzalo Odiard]

A few notes about the rpms Jerry shared:

* While is based on 0.100, have a few patches needed by AU,
we didn't have time to upstream.

* The patches are applied on the rpms, to make clear the separation of
the changes.

* specs and patches are here: https://github.com/godiard/au1b_rpms

We don't have the dependencies to support the web part.
I don't know yet if is possible have all (specially webkit) compiled on F18.

Gonzalo


On Mon, Sep 2, 2013 at 9:57 PM, Jerry Vonau <jvonau at shaw.ca> wrote:
> On Mon, 2013-09-02 at 19:37 -0500, Jerry Vonau wrote:
>>
>> On 2 September 2013 19:20, James Cameron <quozl at laptop.org> wrote:
>>         On Mon, Sep 02, 2013 at 09:09:09PM -0300, Manuel Quiñones
>>         wrote:
>>         > 2013/9/2 James Cameron <quozl at laptop.org>:
>>         > > On Mon, Sep 02, 2013 at 04:36:31PM -0300, Manuel Quiñones
>>         wrote:
>>         > >> I agree.  We should delay the hard freeze for 4 weeks and
>>         hope that by
>>         > >> that time we get some testing and bugfixing.
>>         > >
>>         > > How can I test on an XO?
>>         >
>>         > That's the question, James.  We don't have images this
>>         time.  In
>>         > previous releases, we had many periodic builds for testing.
>>          So this
>>         > is something we need to solve as a community.  I hope that
>>         the AU
>>         > deploy could make one soon so we can all test.
>>
>>
>>         Is this new release of Sugar so different it can't even be
>>         retrofitted
>>         onto OLPC OS 13.2.0?  Can we back out those changes only, so
>>         that the
>>         rest of the changes can be tested?
>>
>>
>>
>> We have some rpms that are testable:
>> http://dev.laptop.org/~gonzalo/AU1B/AU1B_4.zip
>>
>>
>> Instalation:
>> * Install the olpc 13.2.0 image
>> http://download.laptop.org/xo-4/os/official/13.2.0-13/32013o4.zd
>>
>>
>> unzip AU1B_2.zip
>
> Opps, make that unzip AU1B_4.zip
>>
>> rpm -Uvh *.rpm
>>
>>
>> Notes:
>> * The modemmanager error happend because now the plan is saved as a
>> integer insted of as a string. To solve it, we need change the initial
>> configuration to do:
>>
>>
>> gconftool-2 --set  /desktop/sugar/network/gsm/plan --type int 2
>>
>>
>>
>> Happy testing,
>>
>>
>> Jerry
>>
>>
>>
>> _______________________________________________
>> Sugar-devel mailing list
>> Sugar-devel at lists.sugarlabs.org
>> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>
> _______________________________________________
> Sugar-devel mailing list
> Sugar-devel at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel