2013/1/17 Vedran Miletić <rivanvx(a)gmail.com>:
2013/1/17 Paulo César Pereira de Andrade
> I followed the procedures at
> and after a reboot, updated my sagemath x86_64 repository.
> I had a few f15 plexus&maven packages that appeared to cause
> upgrade problems as well as ffmpeg-libs, but this was enough
> for me to convert a f17 computer to f18:
> $ sudo yum erase sagemath
> $ sudo yum erase plexus-appserver plexus-runtime-builder
> plexus-maven-plugin maven-shared plexus-xmlrpc ffmpeg-libs
> $ sudo yum update yum
> $ sudo yum clean all
> $ sudo yum --releasever=18 --disableplugin=presto distro-sync
> $ sudo rpm --rebuilddb
> If you previously had a /etc/yum.repos.d/sagemath-f17.repo, please
> now use http://pcpa.fedorapeople.org/sagemath/sagemath-f18.repo
Great stuff. Thank you for your effort.
> There is a Singular update, but the same build should be available
> as an update in a few days
> and I just opened a bug report to update f18 to the same numpy in rawhide
In general, how stable is this? Are there tests to verify this is
This is a bit outdated and was generated from the f17 build:
but most of the failures should still happen.
I ask because I'm planning to mention using sagemath on Fedora as
alternative to Wolfram Mathematica to some people on our university,
and I wouldn't mind using stock sagemath instead of packaged one for
the time being, until packaged one gets wider testing.
For the time being I would suggest using the upstream build, or
something like http://aleph.sagemath.org
My goal is to have the package fully reliable. Right now it is
passing roughly 90% of the tests. Most failures are numerical
noise, but there are some serious issues that need to be fixed.
I'm very grateful for your effort, and having packaged sagemath
definitely make deployment and updates easier in the long term, but
leaving a good initial impression is really important when people are
exposed to free software.