We might be having trouble with DKIM: the key might be expired or something.
I'm in Peru and cant even ssh in to check. Perhaps SamP can help with this?
On July 1, 2015 8:38:56 AM GMT-05:00, Gonzalo Odiard godi...@sugarlabs.org
wrote:
Found in spam folder (again).
There are something wrong
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
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
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 Martin
2015-06-30 16:16 GMT-06:00 Martin Abente martin.abente.lah...@gmail.com:
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
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 godi...@sugarlabs.org:
German,
Did you updated the repodata in the repository?
I
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.
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 yum
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
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:
-
10 matches
Mail list logo
