Awesome, thank you Brian for stepping up! <div><br></div><div>Is something additional required in order to make sure the activity runs properly in SoaS or jhbuild?</div><div><br></div><div>-Wade<br><br><div class="gmail_quote">
On Mon, Jan 26, 2009 at 2:14 PM, Brian Jordan <span dir="ltr"><<a href="mailto:brian@laptop.org">brian@laptop.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="Ih2E3d">On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer <<a href="mailto:simon@schampijer.de">simon@schampijer.de</a>> wrote:<br>
</div><div class="Ih2E3d">> Simon Schampijer wrote:<br>
>> Hi,<br>
>><br>
>> the Sucrose package of Pippy is version 25 - when I last released it<br>
>> back in August. Since then there has been some development going into<br>
>> Pippy (now version 30)<br>
>> <a href="http://dev.laptop.org/git?p=projects/pippy-activity;a=shortlog" target="_blank">http://dev.laptop.org/git?p=projects/pippy-activity;a=shortlog</a><br>
>><br>
>> But none of the maintainers did follow the Sucrose release cycle, even<br>
>> though I sent a reminder<br>
>> <a href="http://lists.laptop.org/pipermail/sugar/2008-November/010021.html" target="_blank">http://lists.laptop.org/pipermail/sugar/2008-November/010021.html</a><br>
>><br>
>> Any, specific reason for that? Pippy has not been moved to<br>
>> <a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a>, as well.<br>
>><br>
>> please indicate clearly:<br>
>> * if you still want to be part of Sucrose (including following the<br>
>> release cycle)<br>
>> * any new maintainer that is willing to do this task if you does not want to<br>
>> * any issues/reasons you have to do so<br>
>><br>
>> Best,<br>
>> Simon<br>
><br>
><br>
> To follow up on this, I mainly want to find a maintainer for Pippy for<br>
> Sucrose. If there is no one willing to do that we drop it, which is ok -<br>
> one can still download the xo etc, I just want a clearer situation.<br>
><br>
</div>Hi,<br>
<br>
I will maintain Pippy for Sucrose, though I may need a bit of hand holding.<br>
<br>
Please let me know if what I did seems correct (esp. step 2):<br>
<br>
1. l got the most recent version of Pippy from git<br>
git-clone git://<a href="http://dev.laptop.org/projects/pippy-activity" target="_blank">dev.laptop.org/projects/pippy-activity</a><br>
cd pippy-activity<br>
<br>
2. ./setup.py gave a bunch of "invalid entry in MANIFEST" errors about<br>
different locales, so I ran:<br>
./setup.py fix_manifest<br>
<br>
3. ./setup.py dist_source<br>
<br>
4. I asked a crank sysadmin to add me to the Sugar group,<br>
And I moved Pippy-30.tar.bz2 to:<br>
<a href="http://dev.laptop.org/pub/sugar/sources/Pippy/Pippy-30.tar.bz2" target="_blank">http://dev.laptop.org/pub/sugar/sources/Pippy/Pippy-30.tar.bz2</a> (805K)<br>
<br>
I will move pippy over to <a href="http://git.sugarlabs.org" target="_blank">git.sugarlabs.org</a> as well.<br>
<br>
Thanks,<br>
Brian<br>
<div class="Ih2E3d"><br>
<br>
> Wade, do you have maybe someone in mind?<br>
><br>
> Cheers,<br>
> Simon<br>
><br>
> _______________________________________________<br>
> Sugar-devel mailing list<br>
> <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a><br>
> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a><br>
><br>
</div>_______________________________________________<br>
Devel mailing list<br>
<a href="mailto:Devel@lists.laptop.org">Devel@lists.laptop.org</a><br>
<a href="http://lists.laptop.org/listinfo/devel" target="_blank">http://lists.laptop.org/listinfo/devel</a><br>
</blockquote></div><br></div>