Today I was all day trying to update my development environment,
doing a clone from zero, after was broken with a update.
Looks like the git pull from glib never ends.
Anybody else see that?
My desktop is F18 64bits
Gonzalo
___
Sugar-devel mailing list
I haven't seen that. Post your main.log? Did you try to clone glib manually
to see if that works?
On Friday, 28 June 2013, Gonzalo Odiard wrote:
Today I was all day trying to update my development environment,
doing a clone from zero, after was broken with a update.
Looks like the git pull
Starting again, you can see the log stopping in the same way with automake
I don't know if is a problem with the network here, I am traveling,
but didn't have problems downloading big files.
Thanks for looking at this
Gonzalo
On Fri, Jun 28, 2013 at 3:41 AM, Daniel Narvaez dwnarv...@gmail.com
Please check in which state the automake repo was actually left by this.
For example does git log work on it.
Also try to clone automake manually to see if it's a sugar-build specific
issue or not.
On Friday, 28 June 2013, Gonzalo Odiard wrote:
Starting again, you can see the log stopping in
I've seen something similar travelling in the area you are in, caused
by faulty NAT implementations at internet service providers.
The symptom is that the network connection to the git server stalls,
and the next packet does not arrive. The server has sent the packet,
but the client does not
Finally I've just understood how is orgranized the GCompris project :
- the boards implementations are written in C language, under the
src/boards folder
- the xml definition of the board is defined in boards/
chess_movelearn.xml.in
- the pieces are in the boards/chess
Now I am
Maybe you can obtain more specific info in the gcompris list:
https://lists.sourceforge.net/lists/listinfo/gcompris-devel
Date: Fri, 28 Jun 2013 10:54:18 +0200
From: laurent.bern...@gmail.com
To: gonz...@laptop.org
CC: sugar-devel@lists.sugarlabs.org
Subject: Re: [Sugar-devel] Is PyGame already
Thanks,
I suscribe right now
Regards
2013/6/28 Alan Jhonn Aguiar Schwyn alan...@hotmail.com
Maybe you can obtain more specific info in the gcompris list:
https://lists.sourceforge.net/lists/listinfo/gcompris-devel
--
Date: Fri, 28 Jun 2013 10:54:18 +0200
On Thu, Jun 27, 2013 at 5:44 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
Hello,
this is the first development release of the cycle that will bring us to
0.100.
Highlights:
* Comments box in the journal
* Integration with web services
* Background customization
* Initial support for
Wanted to know if anyone else out there is getting this problem.
I open the journal.
Click one of the recent activities, then sugar terminated abruptly.
After it terminates, this is what i get on my terminal,
http://fpaste.org/21626/37241794/
Did i mess up something in the journal or is it a
Time for the second installment to the XSCE Update.
- Deployments-
1. Bhagmalpur, India - http://bhagmalpur.wordpress.com/ . The update
to XSCE is complete in Bhagmalpur. It will be interesting to see what
Sameer concluded based on the statistics generation system. -- Thanks
Sameer and Anish
2.
Hello again,
Sorry if my question is too obvious : I ask it because I never did it
before.
(I found the GCompris developper wiki and I am reading it).
If I want to improve a GCompris activity, is the best way to clone the
GCompris git repository ? And is the merge request the functionnality
By the way, I expect osbuild clean to be as good as new clone in the
latest sugar-build. So you can do that to avoid fetching all of the sources.
(If you want to be sure absolutely everything is clean you can additionally
git clean -fdx but it should not be necessary. I should stop doing that
On 28 June 2013 12:17, Peter Robinson pbrobin...@gmail.com wrote:
Sugar 0.99.0 is now built in rawhide except sugar-runner which I need
to package up. Latest Browse too. I can probably spin a live image for
those that might be interested in running and testing on F-20 before
the nightly spin
I wish I could see the python code which is triggering this. I cannot
reproduce but it seems unlikely to be something you messed up, it's
probably either a sugar or a glib/pygobject bug.
Can you try this:
Move away ~/.sugar/default
Start sugar
Start the terminal activity
Close it
Click on
You really should ask this on the GCompris mailing list.
On Friday, 28 June 2013, laurent bernabe wrote:
Hello again,
Sorry if my question is too obvious : I ask it because I never did it
before.
(I found the GCompris developper wiki and I am reading it).
If I want to improve a GCompris
Laurent,
There is a Git repo containing all the sample code in the FLOSS Manual.
You can judge for yourself how well PyGame might work for you. I am not a
PyGame expert but in making the examples I thought it worked OK.
There is a guest chapter on making an Activity using HTML and JavaScript
Tried that.
Running terminal activity from journal seems to be fine.
Try this,
Run the pippy activity.
change the title of pippy activity in the activity toobar.
Close it.
Run pippy activity from journal.
When i do that it crashes.
I got the same stuff http://fpaste.org/21715/37243708/
On Fri,
Hello,
I'm doing heavy bug triaging on the sugar components. I want the result to
be a manageable list of issues known to be current, that we can comfortably
show to people that would like to contribute.
Here are a couple of rules I would like to propose
* Use Status = Uncofirmed/New to
Yes! It crashes even if I just over the entry here. I don't have time to
debug it right now but we need to find out which python code is triggering
it.
Can you open a bug about it please? Including these steps and the fpaste.
On 28 June 2013 18:44, suraj ks suraj.gilles...@gmail.com wrote:
Sure.
On Fri, Jun 28, 2013 at 11:06 PM, Daniel Narvaez dwnarv...@gmail.comwrote:
Yes! It crashes even if I just over the entry here. I don't have time to
debug it right now but we need to find out which python code is triggering
it.
Can you open a bug about it please? Including these steps
* Mark a bug as assigned only if you are working on it or will very
shortly. If you change your mind please unassign to give someone else the
opportunity to take it. I don't think we should require people to mark bugs
as assigned though, something optional (it might make more sense if you are
* Don't open obscure todo bugs. If you want it to be in the public tracker
you need to take the time to explain what the change is about. Otherwise
track it yourself :)
For example
http://bugs.sugarlabs.org/ticket/3451
___
Sugar-devel mailing list
Thanks for the update, keep up the great work!
Cheers,
Christoph
On Fri, Jun 28, 2013 at 3:53 PM, David Farning dfarn...@activitycentral.com
wrote:
Time for the second installment to the XSCE Update.
- Deployments-
1. Bhagmalpur, India - http://bhagmalpur.wordpress.com/ . The update
to
Thanks for your answer.
So I'll work on the original GCompris code. For prevision, I had already
cloned the gcompris project on git : i'll simply try to remove this clone.
Regards
2013/6/28 James Simmons nices...@gmail.com
Laurent,
GCompris existed before Sugar did and can be run as a
Thanks for your answer
I'll read the remaining relevant chapters on the floss.
And, as you replied to me in another topic of mine : it is better to
contribute to GCompris in its initial version. So I am going this way.
Regards
2013/6/28 James Simmons nices...@gmail.com
Laurent,
There is a
If obscure, probably had sense to who fill it,
and maintainer at the time.
Should be better ask for more information and status in the same ticket.
I was closing tickets with old milestones in the last weeks.
My criteria was:
* Check if the bug is present in our actual code
* If present, change
Thanks for your answer :
In fact I asked this question as I thought that the best way to improve
GCompris for Sugar was to work directly on Sugar Version hosted in Git
SugarLabs.
But as James Simons pointed me, I should become a Gcompris contributor
instead : which procedure is documented in
On 28 June 2013 23:39, Gonzalo Odiard gonz...@laptop.org wrote:
If obscure, probably had sense to who fill it,
and maintainer at the time.
Should be better ask for more information and status in the same ticket.
It surely made sense at the time, but now it's just adding to the triaging
work
Ok, but in this case, who wrote the ticket is available, and surely will
reply.
In my case, I have closed similar obscure tickets, but without any activity
for 3 or more years :/
Gonzalo
On Fri, Jun 28, 2013 at 6:47 PM, Daniel Narvaez dwnarv...@gmail.com wrote:
On 28 June 2013 23:39, Gonzalo
Sure, in this case I will ask before closing.
On 28 June 2013 23:51, Gonzalo Odiard gonz...@laptop.org wrote:
Ok, but in this case, who wrote the ticket is available, and surely will
reply.
In my case, I have closed similar obscure tickets, but without any activity
for 3 or more years :/
Hello,
we seem to have a pretty old trac version. I'm trying to improve sugar core
bug tracking state and practices and as part of that effort I think it
might make sense to upgrade to 1.0.
Is the only reason we didn't upgrade so far lack of time? Or do we know
about blockers?
Is our trac
32 matches
Mail list logo
