Releasing Sage 6.0

[Volker Braun]

Sage 6.0 

A.k.a. "Today is a good day to die", the credo of release engineering...

This is the first official release for Sage 6, which from now on will use git and a single unified repository.

Source tarball: http://boxen.math.washington.edu/home/vbraun/src/sage-6.0.tar.gz

Binary tarballs (is anybody using these?) will follow when they are done.

If you use git, you can do

    git clone git://github.com/sagemath/sage.git

    cd sage

    make

* The master branch will stay at 6.0 until 6.1 is released

* The develop branch will soon move on to 6.1.beta0

 

[Simon King]

Hi Volker,

On 2013-12-18, Volker Braun <vbrau...@gmail.com> wrote:
> This is the first official release for Sage 6, which from now on will use
> git and a single unified repository.

Congratulation!

> * The master branch will stay at 6.0 until 6.1 is released
> * The develop branch will soon move on to 6.1.beta0

Does this mean that for doing development work on trac, one should
henceforth do "git checkout trac develop" rather than "git checkout trac
master" (or whatever git command is used), or are you just talking about
the master branch of the github repository? Will the trac master stay at
6.0 as well?

Best regards,
Simon

[Nathann Cohen]

Yooooooooooooooooo !!

> A.k.a. "Today is a good day to die", the credo of release engineering...

Gosh ! This release is gloomier than usual :-P

Nathann

[Volker Braun]

On Wednesday, December 18, 2013 11:09:36 AM UTC, Simon King wrote:

> * The master branch will stay at 6.0 until 6.1 is released
> * The develop branch will soon move on to 6.1.beta0
Does this mean that for doing development work on trac, one should
henceforth do "git checkout trac develop" rather than "git checkout trac
master"

Just as with the old workflow, you could develop against the most recent beta or the most recent release. It depends a bit on how cutting-edge you dare to be, and how sweeping the changes on your ticket are.

Will the trac master stay at 6.0 as well?

The trac master is the same as the github master, and the trac develop branch is the same as the github develop branch. They are just 1:1 mirrored on github.

 

Best regards,
Simon

[Jaap Spies]

Sorry to disturb your day. Please don't die.

I upgraded to Fedora 20, but building sage-6.0 resulted in:
Error building Sage.

The following package(s) may have failed to build:

package: atlas-3.10.1.p7
log file: /home/jaap/downloads/sage-6.0/logs/pkgs/atlas-3.10.1.p7.log
build directory: /home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/atlas-3.10.1.p7

package: git-1.8.4.4
log file: /home/jaap/downloads/sage-6.0/logs/pkgs/git-1.8.4.4.log
build directory: /home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/git-1.8.4.4

The build directory may contain configuration files and other potentially
helpful information. WARNING: if you now run 'make' again, the build
directory will, by default, be deleted. Set the environment variable
SAGE_KEEP_BUILT_SPKGS to 'yes' to prevent this.

make: *** [build] Error 1

What can I do?

Cheers, Jaap

--
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...@googlegroups.com.
To post to this group, send email to sage-r...@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/groups/opt_out.

[Volker Braun]

I updated to Fedora 20 this morning and Sage built for me. Can you post the logs?

[Jaap Spies]

Please, tell me more exact what you want to see. I'm rusty in building Sage!

Jaap

[Harald Schilly]

On Wed, Dec 18, 2013 at 10:49 PM, Jaap Spies <jaap...@gmail.com> wrote:
> Please, tell me more exact what you want to see. I'm rusty in building Sage!

The error message mentions log files for both packages, i.e.

log file: /home/jaap/downloads/sage-6.0/
logs/pkgs/atlas-3.10.1.p7.log
and
log file: /home/jaap/downloads/sage-6.0/
logs/pkgs/git-1.8.4.4.log

At the bottom of both, there will be some information why building them failed.

Harald

[Jaap Spies]

Thanks Harald.

Thread model: posix
gcc version 4.7.3 (GCC)
/home/jaap/downloads/sage-6.0/local/bin/gcc -V 2>&1  >> bin/INSTALL_LOG/ERROR.LOG
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
make[7]: [error_report] Error 1 (ignored)
/home/jaap/downloads/sage-6.0/local/bin/gcc --version 2>&1  >> bin/INSTALL_LOG/ERROR.LOG
tar cf error_x86SSE264SSE2.tar Make.inc bin/INSTALL_LOG/*
bzip2 error_x86SSE264SSE2.tar
make[7]: Leaving directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/atlas-3.10.1.p7/src/ATLAS-build'
make[6]: Leaving directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/atlas-3.10.1.p7/src/ATLAS-build'
make[5]: Leaving directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/atlas-3.10.1.p7/src/ATLAS-build/bin'
Error report error_<ARCH>.tgz has been created in your top-level ATLAS
directory.  Be sure to include this file in any help request.
cat: ../../CONFIG/error.txt: No such file or directory
cat: ../../CONFIG/error.txt: No such file or directory


BEGIN STAGE 1-0-0: SYSTEM PROBE/AUX COMPILE at 22:12
make[4]: *** [build] Error 255
make[4]: Leaving directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/atlas-3.10.1.p7/src/ATLAS-build'
make[3]: *** [build] Error 2
make[3]: Leaving directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/atlas-3.10.1.p7/src/ATLAS-build'
------------------------------------------------------------
  File "./spkg-install", line 512, in <module>
    assert_success(rc, bad='Failed to build ATLAS.', good='Finished building ATLAS core.')
  File "./spkg-install", line 58, in assert_success
    traceback.print_stack(file=sys.stdout)
------------------------------------------------------------
Error:  Failed to build ATLAS.

real    1m0.981s
user    0m44.588s
sys     0m2.489s
************************************************************************
Error installing package atlas-3.10.1.p7
************************************************************************

make[4]: Entering directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/git-1.8.4.4/src/perl'
/usr/bin/perl Makefile.PL PREFIX='/home/jaap/downloads/sage-6.0/local' INSTALL_BASE='' --localedir='/home/jaap/downloads/sage-6.0/local/share/locale'
Can't locate ExtUtils/MakeMaker.pm in @INC (you may need to install the ExtUtils::MakeMaker module) (@INC contains: /usr/local/lib64/perl5 /usr/local/share/perl5 /usr/lib64/perl5/vendor_perl /usr/share/perl5/vendor_perl /usr/lib64/perl5 /usr/share/perl5 .) at Makefile.PL line 3.
BEGIN failed--compilation aborted at Makefile.PL line 3.
make[4]: *** [perl.mak] Error 2
make[4]: Leaving directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/git-1.8.4.4/src/perl'
make[3]: *** [perl/perl.mak] Error 2
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory `/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/git-1.8.4.4/src'
Error building git.

real    1m5.124s
user    0m57.644s
sys     0m4.480s
************************************************************************
Error installing package git-1.8.4.4
************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file
  /home/jaap/downloads/sage-6.0/logs/pkgs/git-1.8.4.4.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/git-1.8.4.4 and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/home/jaap/downloads/sage-6.0/local/var/tmp/sage/build/git-1.8.4.4' && '/home/jaap/downloads/sage-6.0/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************

Cheers,

Jaap

[Robert Bradshaw]

Yay! Congrats and thank you.

[Volker Braun]

For the git problem you need to "yum install perl-ExtUtils-MakeMaker".

For the atlas problem I need the whole log. One alternative is to install the system atlas ("yum install atlas-devel") and build with SAGE_ATLAS_LIB=/usr/lib64/atlas

[Jaap Spies]

My goodness! How should I have known this!

Jaap

[John H Palmieri]

On Wednesday, December 18, 2013 3:05:13 PM UTC-8, Volker Braun wrote:

For the git problem you need to "yum install perl-ExtUtils-MakeMaker".

For the atlas problem I need the whole log. One alternative is to install the system atlas ("yum install atlas-devel") and build with SAGE_ATLAS_LIB=/usr/lib64/atlas

For the ATLAS problem, it looks like it's using Sage's gcc. On a typical Linux machine, shouldn't it be using the system gcc? What does "gcc --version" return?


 

[Jaap Spies]

[jaap@vrede sage-6.0]$ gcc --version
gcc (GCC) 4.8.2 20131212 (Red Hat 4.8.2-7)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

[jaap@vrede sage-6.0]$

[Jaap Spies]

----------------------------------------------------------------------
All tests passed!
----------------------------------------------------------------------
Total time for all tests: 1036.7 seconds
    cpu time: 6876.2 seconds
    cumulative wall time: 7838.4 seconds

On Thu, Dec 19, 2013 at 12:05 AM, Volker Braun <vbrau...@gmail.com> wrote:

[Marco Streng]

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 in spkg/standard/gcc-4.7.3.p1.spkg
gcc-4.7.3.p1
====================================================
Extracting package /Users/tcstreng/sagebuilds/sage-5.13/spkg/standard/gcc-4.7.3.p1.spkg
-rw-r--r--@ 1 tcstreng  staff  37520975 Dec 11 12:05 /Users/tcstreng/sagebuilds/sage-5.13/spkg/standard/gcc-4.7.3.p1.spkg
Finished extraction
****************************************************
Host system:
Darwin dhcp-70.math.leidenuniv.nl 13.0.0 Darwin Kernel Version 13.0.0: Thu Sep 19 22:22:27 PDT 2013; root:xnu-2422.1.72~6/RELEASE_X86_64 x86_64
****************************************************
C compiler: /usr/bin/clang
C compiler version:
Apple LLVM version 5.0 (clang-500.2.79) (based on LLVM 3.3svn)
Target: x86_64-apple-darwin13.0.0
Thread model: posix
****************************************************
sed: /usr/include/sys/cdefs.h: No such file or directory

real    0m0.012s
user    0m0.007s
sys    0m0.007s
************************************************************************
Error installing package gcc-4.7.3.p1

************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the relevant part of the log file

  /Users/tcstreng/sagebuilds/sage-5.13/logs/pkgs/gcc-4.7.3.p1.log

Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to

/Users/tcstreng/sagebuilds/sage-5.13/spkg/build/gcc-4.7.3.p1 and type 'make' or whatever is appropriate.

Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:

  (cd '/Users/tcstreng/sagebuilds/sage-5.13/spkg/build/gcc-4.7.3.p1' && '/Users/tcstreng/sagebuilds/sage-5.13/sage' --sh)

When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************

2013/12/18 Volker Braun <vbrau...@gmail.com>

--

[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/include/sys/cdefs.h: No such file or directory

This is an XCode installation problem. That file needs to exist before
you can build Sage.

Perhaps have a look at http://trac.sagemath.org/ticket/15319

[Marco Streng]

2013/12/19 Jeroen Demeyer <jdem...@cage.ugent.be>

Thanks!

 

--
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+unsubscribe@googlegroups.com.

[Marco Streng]

Built succesfully on OSX 10.9.1 (well, on 1 of the 2 machines). But sage -t -a gives:

sage -t src/sage/interfaces/sage0.py  # 4 doctests failed
sage -t src/sage/structure/sage_object.pyx  # 3 doctests failed
sage -t src/sage/doctest/forker.py  # 2 doctests failed
sage -t src/sage/misc/ascii_art.py  # 3 doctests failed
sage -t src/sage/misc/interpreter.py  # 1 doctest failed
sage -t src/sage/interacts/debugger.py  # 1 doctest failed
sage -t src/sage/misc/attached_files.py  # 3 doctests failed
sage -t src/sage/misc/sage_extension.py  # 11 doctests failed
sage -t src/sage/misc/inputhook.pyx  # 4 doctests failed
sage -t src/sage/misc/displayhook.py  # 6 doctests failed

All but one related to printing of characters, e.g. "<CSI-0;31m><CSI-0m>[ " instead of "[ ".

The exception is:

File "src/sage/interfaces/sage0.py", line 375, in sage.interfaces.sage0.Sage._contains
Failed example:
    sage0._contains('2', 'QQ')
Expected:
    True
Got:
    False

2013/12/19 Marco Streng <marco....@gmail.com>

[Volker Braun]

Did Apple break isatty or whats going on?

2013/12/19 Marco Streng <marco....@gmail.com>

To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.

[Emmanuel Charpentier]

Le mercredi 18 décembre 2013 12:00:39 UTC+1, Volker Braun a écrit :
> Sage 6.0 
>
>
> A.k.a. "Today is a good day to die", the credo of release engineering...
>
>
> This is the first official release for Sage 6, which from now on will use git and a single unified repository.
>
>
>
> Source tarball: http://boxen.math.washington.edu/home/vbraun/src/sage-6.0.tar.gz
>
>
> Binary tarballs (is anybody using these?) will follow when they are done.
>
>
> If you use git, you can do
>
>
>     git clone git://github.com/sagemath/sage.git
>     cd sage
>     make

Is there an http:// or https:// address to reach (i.e. git whatever) sage ? My workplace's firewall locks the git port :-((. I could be bothered to create an ssh tunnel, but then I would have to edit the sage git scripts.

Alternatively, are you aware of some local proxy tool that would allow this ? Socks comes to mind, but seems a bit heavyweight for the task...

--
Emmanuel Charpentier

[Harald Schilly]

On Fri, Dec 20, 2013 at 9:16 PM, Emmanuel Charpentier
<emanuel.c...@gmail.com> wrote:
> Is there an http:// or https:// address to reach (i.e. git whatever) sage ?

Here is the website:
https://github.com/sagemath/sage

bottom right, click on the "https", gives you
https://github.com/sagemath/sage.git

(You can also download a tarball with everything inside for a given
tag or branch identifyer, e.g.:
https://github.com/sagemath/sage/archive/6.0.zip )

Harald

[Vince]

I had the same problem with git-1.8.4.4. This is running on CentOS (which is a ridiculous pain for someone who doesn't really know what they're doing...).

I tried running the command Volker suggested: `yum install perl-ExtUtils-MakeMaker`

I get the following error:

Loaded plugins: security

Repository epel is listed more than once in the configuration

Setting up Install Process

No package perl-ExtUtils-MakeMaker available.

Nothing to do

I've obviously made some mistake with epel somewhere... I realise I'm probably not sharing enough (and that this isn't technically a Sage problem) here but thought I'd just blinding ask as I've already spent a fair amount of time trying to figure this out using my google-foo... If anyone has any idea that'd be appreciated. In the meantime I've just moved us back to a previous version of Sage which was running fine (note that this actually built something that just didn't seem to have a working version of scipy)...

Thanks,

Vince

[kcrisman]

If you use git, you can do

    git clone git://github.com/sagemath/sage.git

    cd sage

    make

http://sagemath.org/doc/installation/source.html has no mention of this as an alternate path to enlightenment.

Also, is there a way to do this but not have the folder created called "sage"?  (E.g. "my_sage_folder"?)  Perhaps it is some option for git clone - that could be added to any help on the doc. 

[Harald Schilly]

On Thu, Jan 23, 2014 at 10:53 PM, kcrisman <kcri...@gmail.com> wrote:
> Also, is there a way to do this but not have the folder created called
> "sage"? (E.g. "my_sage_folder"?) Perhaps it is some option for git clone -
> that could be added to any help on the doc.

That's quite straight forward:

git clone git://github.com/sagemath/sage.git my_sage_folder

:-)

Harald