#8664: Upgrade Sage's MPIR spkg to version 2.1.3
-------------------------------------------------------------------------------+
Reporter: was
| Owner: GeorgSWeber
Type: enhancement
| Status: positive_review
Priority: major
| Milestone: sage-4.6.2
Component: packages
| Resolution:
Keywords: GMP ECM execstack Fedora 14 extension module library dependencies
| Author: Mike Hansen, Leif Leonhardy
Upstream: N/A
| Reviewer: Leif Leonhardy, Dmitrii Pasechnik
Merged:
| Work_issues:
-------------------------------------------------------------------------------+
Comment(by leif):
Replying to [comment:36 jdemeyer]:
> Replying to [comment:33 leif]:
> > * Download the [http://trac.sagemath.org/sage_trac/raw-
attachment/ticket/8664/trac_8664-fix_extmod_deps_for_MPIR_generically-
sagelib.patch patch to the Sage library]. '''Do not yet apply the
patch.''' (We first rebuild / reinstall dependent spkgs, of which the Sage
library is one, so the patched version could get overwritten.)
>
> Please explain. When can {{{setup.py}}} be overwritten? This patched-
files-being-overwritten-thing has bitten me already several times.
A problem with `SAGE_UPGRADING` (whose "external" use is inofficial
anyway) is that if the Sage library gets reinstalled because some of its
dependencies got rebuilt (which is the typical case), Sage unconditionally
switches back to the `main` branch without any warning, so previously
applied patches to a clone take no longer effect (though they are still
there, but no longer in the afterwards current branch, `sage-main`). It
took me some time to realize that (or in fact track down weird errors
caused by this)... ;-)
The Sage library's `spkg-install` should at least issue a warning when it
switches the current branch; perhaps there should be some option to avoid
this, since it is IMHO convenient to do e.g. `env SAGE_UPGRADING=yes make
ptestlong` rather than patching the `main` branch or first building a new
source distribution to build from scratch (or a new patched Sage library
spkg to be installed).
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8664#comment:93>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
