Hello Team,
As one of the administrators of the SugarLabs
Facebook page, i was to check on the page today then i got a message
from a team in India wanting to collaborate with Sugar Labs. here is the
discussion between me and the team.
" I
am Bhavna Nagpal a student of IIIT-Delhi which is th
We've seen this message twice now; something wrong with your mail?
http://lists.sugarlabs.org/archive/sugar-devel/2015-June/050455.html
http://lists.sugarlabs.org/archive/sugar-devel/2015-July/050475.html
Are you sure it isn't spam? It looks like a form letter, because it
mentions "company", "br
Yeah, it looks pretty scammy. It references CorprateSocialResponsibility,
engaging with youths and is from Facebook not email - making it look like a
mass campaign not somebody targeting sugarlabs.
Maybe we should just say: SL is a volunteer run, not for profit
organization. We are always delig
Found in spam folder (again).
There are something wrong with the way our mailing lists or servers are
configured?
This is what gmail say about why this mail is considered spam:
https://support.google.com/mail/answer/81126?hl=en#authentication
As a rule, I find emails with links triggered the sp
Hello Sam,
Different people reported an error while building sugar-artwork packages.
The error is caused by this commit [1] which makes GTK a building
requirement for sugar-artwork, but:
a) if GTK version version is really used on building time, then the
approach used in [1] is wrong, because the
>From the tests I have done, I confirmed it is used in building time,
therefore I have reverted the patch until we can determine a better
solution.
On Wed, Jul 1, 2015 at 12:05 PM, Martin Abente <
martin.abente.lah...@gmail.com> wrote:
> Hello Sam,
>
> Different people reported an error while bui
2015-06-30 16:16 GMT-06:00 Martin Abente :
>
> Hello everyone,
>
> I just added one extra UNSTABLE release (0.105.3), basically to ease our
> testing before the final release on next Monday (July 6). If you are
> interested in helping out, the tarballs can be downloaded from:
>
> http://download.
Sam,
I don't have rawhide installed to test, can you try adding rules for the
two new and old ways, like here:
diff --git a/gtk3/theme/gtk-widgets.css.em b/gtk3/theme/gtk-widgets.css.em
index 67e4e48..d14bbfb 100644
--- a/gtk3/theme/gtk-widgets.css.em
+++ b/gtk3/theme/gtk-widgets.css.em
@@ -221,10
But in that case, the file will no be found and will do
https://github.com/sugarlabs/sugar/blob/master/extensions/cpsection/language/model.py#L100
Right?
2015-06-30 18:53 GMT-03:00 Walter Bender :
> FWIW, if the $HOME env. variable is malformed, then there is the
> possibility that neither the
Thanks German,
I also updated packages in [1] our custom archive of Ubuntu.
Refs:
[1]
https://wiki.sugarlabs.org/go/Ubuntu#OLPC_Ubuntu_Sugar_14.04.2_Trusty_LTS
On Wed, Jul 1, 2015 at 1:40 PM, German Ruiz - FundacionZT <
gr...@fundacionzt.org> wrote:
> 2015-06-30 16:16 GMT-06:00 Martin Abente :
If that don't work, should be good test:
diff --git a/gtk3/theme/gtk-widgets.css.em b/gtk3/theme/gtk-widgets.css.em
index 67e4e48..af87900 100644
--- a/gtk3/theme/gtk-widgets.css.em
+++ b/gtk3/theme/gtk-widgets.css.em
@@ -221,9 +221,18 @@ column-header .button:hover:active {
border-width: 0px
2015-07-01 14:48 GMT-04:00 Gonzalo Odiard :
> But in that case, the file will no be found and will do
>
>
> https://github.com/sugarlabs/sugar/blob/master/extensions/cpsection/language/model.py#L100
>
> Right?
>
If the file exists but is, for example, empty, or has malformed data, it
will skip th
Right, in that case have sense the traceback sent by Alejandro.
Filled a ticket http://bugs.sugarlabs.org/ticket/4868 and sent
a pr https://github.com/sugarlabs/sugar/pull/547
2015-07-01 16:25 GMT-03:00 Walter Bender :
>
> 2015-07-01 14:48 GMT-04:00 Gonzalo Odiard :
>
>> But in that case, the f
German,
Did you updated the repodata in the repository?
I have tried do "yum update sugar*" on a xo with your repository installed,
and no package is found to update.
Gonzalo
On Wed, Jul 1, 2015 at 2:40 PM, German Ruiz - FundacionZT <
gr...@fundacionzt.org> wrote:
> 2015-06-30 16:16 GMT-06:00 Ma
2015-07-01 14:14 GMT-06:00 Gonzalo Odiard :
> German,
> Did you updated the repodata in the repository?
> I have tried do "yum update sugar*" on a xo with your repository installed,
> and no package is found to update.
>
> Gonzalo
Yes, it was updated.
Try yum clean all and then yum update sugar*
Hi Samson, this is a copy/pasted form letter, the tipoff is they mention
"company" which means they did not bother spending three clicks to find out
about Sugar Labs.
If their event is legit, we can always ask them if they will assist a
nonprofit like us in attending, with travel, room & board :-)
Sean,
Could you reply?
On Wed, Jul 1, 2015 at 5:53 PM, Sean DALY wrote:
> Hi Samson, this is a copy/pasted form letter, the tipoff is they mention
> "company" which means they did not bother spending three clicks to find out
> about Sugar Labs.
>
> If their event is legit, we can always ask them
in a couple of days ok
On Wed, Jul 1, 2015 at 10:59 PM, Gonzalo Odiard
wrote:
> Sean,
> Could you reply?
>
> On Wed, Jul 1, 2015 at 5:53 PM, Sean DALY wrote:
>
>> Hi Samson, this is a copy/pasted form letter, the tipoff is they mention
>> "company" which means they did not bother spending thre
Thanks, worked.
Anyway, it is strange we need clean before do the update.
On Wed, Jul 1, 2015 at 5:34 PM, German Ruiz - FundacionZT <
gr...@fundacionzt.org> wrote:
> 2015-07-01 14:14 GMT-06:00 Gonzalo Odiard :
> > German,
> > Did you updated the repodata in the repository?
> > I have tried do "y
Hi Guys,
The issue is the metadata_expire=7d setting in the repo file. New updates
under 7 days old will not be seen by the yum client until the metadata
expires and is refreshed from the yum repo. "Yum clean all" comes with a
network cost as all repos' metadata needs to be re-fetched, you could j
On Wed, Jul 01, 2015 at 09:53:03PM -0300, Gonzalo Odiard wrote:
> Anyway, it is strange we need clean before do the update.
Yes, this seems to be a recent feature. Although I don't know how
recent.
I wish it would do a check-if-modified style of HTTP request instead,
in the way that apt does.
P
Thanks. I've added that to the Wiki.
On Wed, Jul 01, 2015 at 08:22:09PM -0500, Jerry Vonau wrote:
> Hi Guys,
>
> The issue is the metadata_expire=7d setting in the repo file. New updates
> under 7 days old will not be seen by the yum client until the metadata
> expires and is refreshed from the
22 matches
Mail list logo
