#8861: sagenb-0.8.p1.spkg: broken dependencies, requires internet conn. to build
-----------------------------------------------+----------------------------
Reporter: GeorgSWeber | Owner: GeorgSWeber
Type: defect | Status: positive_review
Priority: blocker | Milestone: sage-4.4.2
Component: build | Keywords:
Author: Tim Dumol | Upstream: N/A
Reviewer: Minh Van Nguyen, Georg S. Weber | Merged:
Work_issues: |
-----------------------------------------------+----------------------------
Changes (by newvalueoldvalue):
* status: needs_review => positive_review
* reviewer: Minh Van Nguyen => Minh Van Nguyen, Georg S. Weber
* author: => Tim Dumol
Comment:
OK, using the (slightly altered) version that Minh posted from Tim's p2
spkg, I found out the following:[[BR]]
* this spkg solves the original problem, i.e. does not need an internet
connection to build (I tested this "on top" of a full sage-4.4.1 build,
forcing sagenb to be rebuilt)[[BR]]
* all sagenb doctests still pass[[BR]]
* the notebook starts up and passes some smoke tests[[BR]]
* the mercurial repository is clean, and the spkg is based upon the
previous version 0.8.p1 (i.e. the last patch applied by Mike Hansen for
some t2 issue IIRC should be still in)[[BR]]
* the changes made look sane (esp. about "== 0.1.11" w.r.t. the mechanize
version)[[BR]]
* the one reviewer comment about testing has been incorporated into the
SPKG.txt[[BR]]
I now understand the sagenb spkg better, i.e. that the file "spkg-install"
is being generated, and that the dependencies under src/ are being
downloaded during a standard generation of some new version of this spkg.
So the discrepancy that crept in my goofed attempt just cannot occur this
way. What I disliked, is that this did lead also to the following updates
of certain dependencies in between sagenb-0.8.p1.spkg and
sagenb-0.8.p2.spkg:[[BR]]
* zope.event-3.4.1.tar.gz --> zope.event-3.5.0-1.tar.gz[[BR]]
* zope.i18nmessageid-3.5.1.tar.gz --> zope.i18nmessageid-3.5.2.zip[[BR]]
* zope.interface-3.5.3.tar.gz --> zope.interface-3.6.1.tar.gz[[BR]]
* zope.schema-3.6.1.tar.gz --> zope.schema-3.6.3.zip[[BR]]
Personally, in the light of my other findings and tests above, I do not
consider this as critical, assuming that sagenb does not use any "bleeding
edge" functionality of the above four zope packages, that would be
affected by these updates. If somebody thinks I'm wrong here, then please
feel free to switch the status back to "needs_work".
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8861#comment:9>
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.
