On Thu, Dec 19, 2013 at 11:48:43AM +0100, Harald Schilly wrote:
> Do you think this as a marker flag or something more elaborate?
> Because, well, to make this nice, I assume one has to pick a few
> tickets and write one larger piece for all of them, including some
> additional context, etc. I don'
Yes, the "sage -upgrade" should just pull changes to the source repo and
then rebuild. Will end up in precisely the same place as where you started
it.
On Thursday, December 19, 2013 8:46:10 PM UTC, Justin C. Walker wrote:
>
>
> On Dec 19, 2013, at 07:02 , Volker Braun wrote:
>
> > I'm please
On Dec 19, 2013, at 07:02 , Volker Braun wrote:
> I'm pleased to announce the release of the first beta version. I've been
> working on merging the backlog of git tickets, though there is more to come.
>
> If you are using git, note that the "master" branch is from now on frozen
> to the sage-
On 19 December 2013 15:02, Volker Braun wrote:
> I'm pleased to announce the release of the first beta version. I've been
> working on merging the backlog of git tickets, though there is more to come.
>
> If you are using git, note that the "master" branch is from now on frozen to
> the sage-6.0 t
I'm pleased to announce the release of the first beta version. I've been
working on merging the backlog of git tickets, though there is more to come.
If you are using git, note that the "master" branch is from now on frozen
to the sage-6.0 tree until 6.1 is finished. If you want to follow the be
2013/12/19 Jeroen Demeyer
> On 2013-12-19 15:08, Marco Streng wrote:
>
>> New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
>> after downloading and extracting the tarball and typing "make", I get
>> the following problem (both sage 5.13 and sage 6.0).
>>
>> sed: /usr/includ
On 2013-12-19 15:08, Marco Streng wrote:
New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
after downloading and extracting the tarball and typing "make", I get
the following problem (both sage 5.13 and sage 6.0).
sed: /usr/include/sys/cdefs.h: No such file or directory
Thi
New machine, new problem. On a mac recently upgraded from 10.8 to 10.9,
after downloading and extracting the tarball and typing "make", I get the
following problem (both sage 5.13 and sage 6.0).
sed: /usr/include/sys/cdefs.h: No such file or directory
Marco
-
Found package gcc-4.7.3.p1
2013/12/19 Jean-Pierre Flori
> Looks like
> https://groups.google.com/d/msg/sage-release/PXtNIE_5V-4/2Upi4LoaWbIJ
> Maybe you added the path to old Sage binaries in your path?
>
I did. Then fixed that, rebooted, and downloaded fresh tarballs and am
still compiling... (but the conway polynomials
On 2013-12-19 12:38, Volker Braun wrote:
the 5.13 binary tarballs are in the sage subfolder.
I deleted this, since it's no longer needed.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails
Binary tarballs are now available at
http://boxen.math.washington.edu/home/buildbot/binaries/
The buildbot has undergone some serious reconfiguration in the switch to
git, so it is possible that there are regressions. In particular, I don't
have a mac to test the dmg's on. Feel free to try them
On Thursday, December 19, 2013 8:15:53 AM UTC, Meier wrote:
>
> I tried 5.13 and it is running on my 80486DX
>
That is awesome! :)
--
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
Looks like
https://groups.google.com/d/msg/sage-release/PXtNIE_5V-4/2Upi4LoaWbIJ
Maybe you added the path to old Sage binaries in your path?
On Thursday, December 19, 2013 10:59:16 AM UTC+1, Marco Streng wrote:
>
> Any idea what this could be or how I could find out?
>
> Thanks!
> Marco
>
>
> 201
On Thu, Dec 19, 2013 at 11:38 AM, Nicolas M. Thiery
wrote:
> With that, we can
> just stick to our usual tools to write collaboratively the
> announcement for the important tickets.
Do you think this as a marker flag or something more elaborate?
Because, well, to make this nice, I assume one has
On Wed, Dec 18, 2013 at 03:41:45PM +0100, Harald Schilly wrote:
> in the spirit of "dogfeeding" us our own stuff, we could start to
> collaborate at cloud.sagemath.org. everyone who wants to do this, drop
> me an email.
>
> http://en.wikipedia.org/wiki/Dogfooding
>
> > Could
> > people who've be
Any idea what this could be or how I could find out?
Thanks!
Marco
2013/12/19 Jeroen Demeyer
> On 2013-12-19 09:12, Marco Streng wrote:
>
>> I tried 5.13.rc0 and it had the same problem. Is that different from 5.13?
>>
> No, it's the same.
>
>
> --
> You received this message because you are s
On 2013-12-19 09:12, Marco Streng wrote:
I tried 5.13.rc0 and it had the same problem. Is that different from 5.13?
No, it's the same.
--
You received this message because you are subscribed to the Google Groups
"sage-release" group.
To unsubscribe from this group and stop receiving emails fro
I tried 5.13 and it is running on my 80486DX
On Thu, Dec 19, 2013 at 5:12 AM, Marco Streng wrote:
> I tried 5.13.rc0 and it had the same problem. Is that different from 5.13?
>
>
> 2013/12/19 Jeroen Demeyer
>
>> On 2013-12-19 09:03, Marco Streng wrote:
>>
>>> Is this supposed to build on 10.9?
I tried 5.13.rc0 and it had the same problem. Is that different from 5.13?
2013/12/19 Jeroen Demeyer
> On 2013-12-19 09:03, Marco Streng wrote:
>
>> Is this supposed to build on 10.9?
>>
> Yes, it is supposed to work. Did you try Sage 5.13?
>
>
> --
> You received this message because you are s
On 2013-12-19 09:03, Marco Streng wrote:
Is this supposed to build on 10.9?
Yes, it is supposed to work. Did you try Sage 5.13?
--
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, s
2013/12/17 Justin C. Walker
> Cloned from github. Build completed w/o problems, and all tests
> ('ptestlong') passed on two OS X systems: 10.6.8 (dual 6-core Xeons) and
> 10.9.1 (quad core Core i7).
>
Is this supposed to build on 10.9? That did not work for me.
Recently upgraded my Mac from 1
21 matches
Mail list logo
