>
>
> gcc should be contained in the source tarball. This is fallout from the 
> build system changes. Fix needs review at 
>
>
What about the blank line with no failed packages?  Clearly a package 
failed.  So somehow whatever mechanism causes the package to be listed (I 
used to know what that is, but in the new build system I don't) is not 
working if a package is not even downloaded.  But that is still a failure 
in that package - OR there should be some separate message saying that 
there is a connectivity problem.  Because the final message isn't the 
connectivity message, it's the message about Sage not building, and even

SyntaxError: unexpected EOF while parsing

isn't exactly something that screams "you have a bad proxy setting", which 
is what turned out to be the case for me.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

Reply via email to