12085
Comment: 4t12, normaliz and surfalggeo have reached testing

← Revision 185 as of 20150725 07:28:39 ⇥
11989
Rubiks finally entered debian unstable!

Deletions are marked like this.  Additions are marked like this. 
Line 11:  Line 11: 
* [[http://anonscm.debian.org/gitweb/?p=debianscience/packages/rubiks.git;a=summaryrubiks]] 
Some people within DebianScience would like to package again Sage for Debian. An old version of Sage got packaged long time ago by Tim Abbott, but, because of lack of maintainance, it became totally unusable and was removed from Debian. The status pages (master branch, develop branch) give an overview about package versions in Sage and Debian. If you want to help out, pick one of the open tasks or issues below and get going. Or contact us via the mailing list or in #debianscience on irc.oftc.net.
Steps to get an uptodate Sage standard suite in Debian
Satisfying dependencies that are not yet in Debian unstable
When building Sage against Debian packages as described below, there are still dependencies that cannot yet be satisfied with packages from Debian unstable. This changes frequently. For now the following packages should be installed from git:
singular (use the tag debian/316+dfsg1, Sage will use its own singular but this is needed anyway)
maxima and pari need larger modifications and should be installed from these git repositories. They exist to make experimenting with Sage easier and will not be uploaded to Debian in this form:
maximasage (see 779804)
After installing this version of pari, eclib and lcalc have to be rebuilt against the new version:
Furthermore one has to rebuild the Debian package of cython 0.22 with patches from sage:
ECL has to be patched to fix a doctest:
With these changes the compilation of Sage 6.7 finishes, but building the documentation fails due to our outdated ipython version. To get around this one can uninstall the ipython Debian package. Then Sage will build and use its own version.
Building Sage with Debian packages
We have a git repository (sagemath) to document the steps we currently do to experiment with building Sage against Debian packages. Important elements are the build dependencies of Sage, patches for Sage and a script called "pruner" that uses automake to determine if the necessary packages are installed (see also this mail).
It is recommended to do these steps one by one:
git clone recursive url/to/sagemath.git 
Recursive git clone to also get sage which is included as a git submodule. 
sudo mkbuilddeps install debian/control 
Install build dependencies that are in unstable (requires Debian unstable). 
quilt push a 
Apply patches to Sage. 
debian/rules prune 
Run the pruner script. 
debian/rules build 
Build sage and run the test suite (includes pruning if necessary, but not patching). 
The output of the pruner tells you in the end which dependencies were not found on the machine. These will be downloaded and built in the build step, before Sage itself is built. In the moment the pruner should output something like the following, and it is for now recommended to use these three packages from Sage.
libgap will not come from debian! singular will not come from debian! jmol will not come from debian! 100 system packages will be used
The following commands clean everything up properly.
debian/rules clean 
Clean up after prune and build. 
quilt pop a 
Unapply patches. 
cd sage && git clean dfx 
Clean sage folder (git does not show untracked files from the built due to .gitignore). 
rm rf ~/.local/lib/python2.7/sitepackages/sage* 
Remove sage python library that is installed during the build process. 
Open tasks
Package 
Bug / Link 
Assigned 
Comments 
Packages that need a new maintainer and an upload to Debian: 

jmol 


There is a request for help, see 719330 
libgap 


Can maybe be replaced by a wrapper for GAP. 
pexpect2.0 


(Debian pkg: pythonpexpect): Debian ships version 2.4, but Sage requires version 2.0 (though one of the necessary patches is already in 2.4). Plotting in the notebook is likely to break with newer versions that are in Debian; and >2.0 is reported to be slow. There is a new upstream version so Sage might update, see this sage bug. 

singular 3.1.6 is packaged in debianscience's git and Sage >= 6.2 has also 3.1.6; a package for singular 4.0.1 is in the NEW queue, see 764475. 

Sage components that need a new maintainer and an upload to Debian: 



most dependencies are in Debian now (691509, 703541, 703531, 703533, 703534, 703535, 703536, 787311) The current sagenb package ships a bunch of javascript libraries. It should use at least these Debian packages instead: mathjax, tinymce, jquery, jqueryui, codemirror 

sagetex 



Packages that are (hopefully) not needed: 

cephes 


The Cephes Mathematical Library is only needed for systems where the libc doesn't provide appropriate mathematical functions (cygwin and FreeBSD) and so is not required for Debian. 
iconv 


is part of the libc 

mpir is supposed to be ABIcompatible with gmp. A lot of math packages use gmp and we hope we can have a purely gmp based Sage in Debian. Combining the two will most likely lead to conflicts, using mpir we would need an extra mpir version of many packages. 
Other known or suspected issues
ECL has a strange bug in debian (see 777473).
sage expects to use both ecl and maxima, together, but maxima in debian is using gcl and has no support for ecl ; Snark has fixes for that, but some things (like the above ECL problem) need to clear out before they can be pushed in debian. (see 779804)
pari in sage's latest has a patch and uses a header file which aren't in the debian package, so one currently needs to modify a few things by hand to get going (see 777237)
Information bits that are no issues
Sage upstream would like to get rid of flintqs since some recent versions of flint ship with a quadratic sieve (see this ticket, but it hasn't been done yet). This mail of William Hart tells more about the state of the quadratic sieve code in both flint and flint2. flintqs was uploaded to Debian for the meantime (but blocked in unstable).
New build system for Sage (the distribution)
this is slightly out of date, also, Sage (the community) is not interested in using packages that another distribution provides.
The Sage library is getting an autotools build system in the course of a Google Summer of Code project. With the new build system, it can be built against system libraries. There are tarballs with the code at http://tool.em.cs.unifrankfurt.de/~felix/sage/. (There is also a git repository but the tarballs are recommended). Note that this is work in progress and problems are expected, but we are happy about testers. The transition of this work into Sage is coordinated via a bunch of Sage tickets. We have a Debian package sagelib that currently builds metapackages that help installing the build dependencies of Sage. To test building Sage against Debian packages, one should consult the control file. The dependencies of the metapackage sagelibbuilddepsgit still need special treatment and can't be just installed from Debian.
The following Debian packages should be installed from the git repositories:
For the remaining packages where the Debian package is missing or is missing features required by Sage, it is currently most convenient to use the versions from Sage. This is done by configuring with
../configure \ disableall \ enable{boehm_gc,cython,ecl,flintqs,genus2reduction,maxima,pari,pexpect,pynac,rubiks,sagelib,sagetex,tachyon} \ withgmp
New build system for Sage (the library)
There is some work in progress trying to make sagelib work on top of any software distribution. we use autotools to sort out dependencies, run time paths and provide standard build/installation routines. unlike the first approach, this is heading towards a fork and will likely not play well with the current upstream development process. Experimental tarballs are available at http://tool.em.cs.unifrankfurt.de/~felix/sagelib/, there is no public git repo yet.
Old sagemath package
The old, buggy sagemath Debian package source code is available at http://snapshot.debian.org/package/sagemath/3.0.5dfsg5.1/