I posted a patch that changes the code so that it isn't used on OS X
= 10.4. That's in sage-4.1.alpha1.tar already...
William
Thanks, William!
Ryan,
I've got both a MacPPC and a MacIntel running with OS X 10.4.11, so I
think together we could make this work on OS X 10.4, too (OS X 10.3 is
I think I'm not communicating my point very clearly. I'm suggesting
that the release manager have in his patch application script an
automated prepend 'Trac #: ' to the commit message step.
I thought of implementing this but couldn't think of a way to discover
if there was a ticket
Nick Alexander wrote:
I think I'm not communicating my point very clearly. I'm suggesting
that the release manager have in his patch application script an
automated prepend 'Trac #: ' to the commit message step.
I thought of implementing this but couldn't think of a way to discover
Build failed for intel macbook 10.4.11
Should I post the full log somewhere? Here is the tail:
/Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 -c
sage/misc/darwin_memory_usage.c -o
build/temp.macosx-10.3-i386-2.5/sage/misc/darwin_memory_usage.o -w
Is there an -upgrade location to go to?
If the answer is no for the foreseeable future, that's
understandable. Just asking!
- kcrisman
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send
On 25-Jun-09, at 5:10 AM, David Joyner wrote:
Build failed for intel macbook 10.4.11
Should I post the full log somewhere? Here is the tail:
/Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5
-c sage/misc/darwin_memory_usage.c -o build/temp.macosx-10.3-
On 25 Jun., 14:10, David Joyner wdjoy...@gmail.com wrote:
Build failed for intel macbook 10.4.11
Should I post the full log somewhere? Here is the tail:
/Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5 -c
sage/misc/darwin_memory_usage.c -o
Sorry, I forgot to post a location. I will for alpha1, which will drop
shortly.
On Jun 25, 3:39 pm, kcrisman kcris...@gmail.com wrote:
Is there an -upgrade location to go to?
If the answer is no for the foreseeable future, that's
understandable. Just asking!
- kcrisman
Someone please back out patch #6027, and set it to needs work.
It's clearly is the reason for this brokenness, and wasn't tested on
Mac OS X 10.4 at all. As it is stated in its comments.
William is working on this right now, and will post a patch
momentarily.
rlm
On Thu, Jun 25, 2009 at 11:41 AM, Nick Alexanderncalexan...@gmail.com wrote:
On 25-Jun-09, at 5:10 AM, David Joyner wrote:
Build failed for intel macbook 10.4.11
Should I post the full log somewhere? Here is the tail:
/Users/davidjoyner/sagefiles/sage-4.1.alpha0/local/include/python2.5
Unfortunately, I don't have access to a OSX = 10.4 box otherwise I
would have ported this code to those versions when I originally wrote
the code for this patch. If anyone has a machine available with OSX
10.4 or 10.3 I'd be happy to port this code to it.
On Thu, Jun 25, 2009 at 9:47 AM, Robert
On Thu, Jun 25, 2009 at 9:09 PM, David Joynerwdjoy...@gmail.com wrote:
On Thu, Jun 25, 2009 at 11:41 AM, Nick Alexanderncalexan...@gmail.com wrote:
On 25-Jun-09, at 5:10 AM, David Joyner wrote:
Build failed for intel macbook 10.4.11
Should I post the full log somewhere? Here is the tail:
2009/6/24 Robert Miller rlmills...@gmail.com:
6196 mpmath support
5481 devel/doc/output/* should be filtered from the list of files to doctest
6276 atlas-3.8.3.p2 dumps core on Solaris 10 with gcc 4.4.0
4712 Make the doctest timeouts in Sage easily adjustable
5517 cvxopt-0.9.p7: build failure
On Wed, Jun 24, 2009 at 2:04 PM, Robert Millerrlmills...@gmail.com wrote:
This is the first release of the new cycle, and I've agreed to step in
and co-chair the release with Tom. The source tarball and sage.math
binary are available:
The source tarball and sage.math
binary are available:
http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0.tarhttp://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0-s...
If you are involved with one of them, you
are encouraged to try applying the patches to
Robert Miller wrote:
Other easy ways to save release managers time, resulting in more
frequent releases and shorter wait times to get your code merged:
* Please include the trac number in each commit message if possible.
Surely this could be scripted? Just prepend a Trac #: to the
On Wed, Jun 24, 2009 at 5:13 PM, Jason Groutjason-s...@creativetrax.com wrote:
Robert Miller wrote:
Other easy ways to save release managers time, resulting in more
frequent releases and shorter wait times to get your code merged:
* Please include the trac number in each commit message if
Each of the following tickets were rejected by the merge scripts, but
unfortunately the failures are not available at this time (this is due
to human error on my part). If you are involved with one of them, you
are encouraged to try applying the patches to 4.1.alpha0 and see why/
if they
2009/6/24 Robert Miller rlmills...@gmail.com:
This is the first release of the new cycle, and I've agreed to step in
and co-chair the release with Tom. The source tarball and sage.math
binary are available:
http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0.tar
On Wed, Jun 24, 2009 at 8:31 AM, Tom Boothbytomas.boot...@gmail.com wrote:
Each of the following tickets were rejected by the merge scripts, but
unfortunately the failures are not available at this time (this is due
to human error on my part). If you are involved with one of them, you
are
6196
5991
6164
6200
6269
I'm generating reports on these right now and posting them to tickets
as they come.
Ah -- and 6269 almost certainly failed because I applied both patches
on the ticket, not because the second patch was actually bad.
On Jun 24, 5:04 am, Robert Miller rlmills...@gmail.com wrote:
sage -t devel/sage-main/sage/graphs/graph.py # 25 doctests
failed
sage -t devel/sage-main/sage/databases/database.py # 20
doctests failed
sage -t devel/sage-main/sage/geometry/polyhedra.py # 1
doctests
Hi folks,
On Wed, Jun 24, 2009 at 10:04 PM, Robert Millerrlmills...@gmail.com wrote:
This is the first release of the new cycle, and I've agreed to step in
and co-chair the release with Tom. The source tarball and sage.math
binary are available:
SNIP
Here are the tickets merged in Sage
Robert Miller wrote:
This is the first release of the new cycle, and I've agreed to step in
and co-chair the release with Tom. The source tarball and sage.math
binary are available:
http://sage.math.washington.edu/home/rlmill/release/sage-4.1.alpha0.tar
William Stein wrote:
On Wed, Jun 24, 2009 at 5:13 PM, Jason Groutjason-s...@creativetrax.com
wrote:
Robert Miller wrote:
Other easy ways to save release managers time, resulting in more
frequent releases and shorter wait times to get your code merged:
* Please include the trac number in
On Jun 24, 2009, at 8:15 PM, Jason Grout wrote:
William Stein wrote:
On Wed, Jun 24, 2009 at 5:13 PM, Jason Groutjason-
s...@creativetrax.com wrote:
Robert Miller wrote:
Other easy ways to save release managers time, resulting in more
frequent releases and shorter wait times to get your
On Wed, Jun 24, 2009 at 7:55 PM, Dr. David
Kirkbydavid.kir...@onetel.net wrote:
Robert Miller wrote:
This is the first release of the new cycle, and I've agreed to step in
and co-chair the release with Tom. The source tarball and sage.math
binary are available:
27 matches
Mail list logo
