#8861: sagenb-0.8.p1.spkg: broken dependencies, requires internet conn. to build
-------------------------------+--------------------------------------------
Reporter: GeorgSWeber | Owner: GeorgSWeber
Type: defect | Status: needs_review
Priority: blocker | Milestone: sage-4.4.2
Component: build | Keywords:
Author: | Upstream: N/A
Reviewer: Minh Van Nguyen | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Changes (by mvngu):
* reviewer: => Minh Van Nguyen
Old description:
> This was first noted by John Cremona.
> On a computer that is not connected to the internet, the build fails:
> {{{
> Processing sagenb-0.8-py2.6.egg
> removing '/home/john/sage-4.4.1.rc0/local/lib/python2.6/site-
> packages/sagenb-0.8-py2.6.egg'
> (and everything under it)
> creating /home/john/sage-4.4.1.rc0/local/lib/python2.6/site-
> packages/sagenb-0.8-py2.6.egg
> Extracting sagenb-0.8-py2.6.egg to
> /home/john/sage-4.4.1.rc0/local/lib/python2.6/site-packages
> sagenb 0.8 is already the active version in easy-install.pth
> Installing jmol script to /home/john/sage-4.4.1.rc0/local/bin
> Installing sage3d script to /home/john/sage-4.4.1.rc0/local/bin
>
> Installed /home/john/sage-4.4.1.rc0/local/lib/python2.6/site-
> packages/sagenb-0.8-py2.6.egg
> Processing dependencies for sagenb==0.8
> Searching for mechanize<0.2dev
> Reading http://pypi.python.org/simple/mechanize/
> Download error: [Errno -2] Name or service not known -- Some packages
> may not be found!
> Reading http://pypi.python.org/simple/mechanize/
> ...
> }}}
> On a computer with internet connection, one finds in the install.log:
> {{{
> Processing dependencies for zope.testbrowser==3.8.1
> Searching for mechanize<0.2dev
> Reading http://pypi.python.org/simple/mechanize/
> Reading http://wwwsearch.sourceforge.net/mechanize/
> Best match: mechanize 0.1.11
> Downloading
> http://wwwsearch.sourceforge.net/mechanize/src/mechanize-0.1.11.tar.gz
> Processing mechanize-0.1.11.tar.gz
> Running mechanize-0.1.11/setup.py -q bdist_egg --dist-dir /tmp
> /easy_install-XXPn64/mechanize-0.1.11/egg-dist-tmp-fxjRAP
> no previously-included directories found matching 'docs-in-progress'
> Removing mechanize 0.2.0 from easy-install.pth file
> Adding mechanize 0.1.11 to easy-install.pth file
>
> ...
> }}}
> So the solution seems to be pretty easy:
>
> Make a new sagenb-0.8.p2.spkg, by throwing out "mechanize-0.2.0.tar.gz"
> under /src/, adding back the old "mechanize-0.1.11.zip", and finally
> adjusting the corresponding line 6 in the spkg-install file.
New description:
This was first noted by John Cremona.
On a computer that is not connected to the internet, the build fails:
{{{
Processing sagenb-0.8-py2.6.egg
removing '/home/john/sage-4.4.1.rc0/local/lib/python2.6/site-
packages/sagenb-0.8-py2.6.egg'
(and everything under it)
creating /home/john/sage-4.4.1.rc0/local/lib/python2.6/site-
packages/sagenb-0.8-py2.6.egg
Extracting sagenb-0.8-py2.6.egg to
/home/john/sage-4.4.1.rc0/local/lib/python2.6/site-packages
sagenb 0.8 is already the active version in easy-install.pth
Installing jmol script to /home/john/sage-4.4.1.rc0/local/bin
Installing sage3d script to /home/john/sage-4.4.1.rc0/local/bin
Installed /home/john/sage-4.4.1.rc0/local/lib/python2.6/site-
packages/sagenb-0.8-py2.6.egg
Processing dependencies for sagenb==0.8
Searching for mechanize<0.2dev
Reading http://pypi.python.org/simple/mechanize/
Download error: [Errno -2] Name or service not known -- Some packages
may not be found!
Reading http://pypi.python.org/simple/mechanize/
...
}}}
On a computer with internet connection, one finds in the install.log:
{{{
Processing dependencies for zope.testbrowser==3.8.1
Searching for mechanize<0.2dev
Reading http://pypi.python.org/simple/mechanize/
Reading http://wwwsearch.sourceforge.net/mechanize/
Best match: mechanize 0.1.11
Downloading
http://wwwsearch.sourceforge.net/mechanize/src/mechanize-0.1.11.tar.gz
Processing mechanize-0.1.11.tar.gz
Running mechanize-0.1.11/setup.py -q bdist_egg --dist-dir /tmp
/easy_install-XXPn64/mechanize-0.1.11/egg-dist-tmp-fxjRAP
no previously-included directories found matching 'docs-in-progress'
Removing mechanize 0.2.0 from easy-install.pth file
Adding mechanize 0.1.11 to easy-install.pth file
...
}}}
So the solution seems to be pretty easy:
Make a new sagenb-0.8.p2.spkg, by throwing out "mechanize-0.2.0.tar.gz"
under /src/, adding back the old "mechanize-0.1.11.zip", and finally
adjusting the corresponding line 6 in the spkg-install file.
'''Apply this spkg:'''
*
http://sage.math.washington.edu/home/mvngu/spkg/standard/sagenb/sagenb-0.8.p2.spkg
--
Comment:
A trivial point. When uncompressed, Tim's updated spkg has this name:
{{{
#!sh
[mv...@sage sagenb]$ ls
sagenb-0.7.2.spkg sagenb-0.7.5.1.spkg sagenb-0.7.5.2.spkg
sagenb-0.8.p2.spkg
[mv...@sage sagenb]$ tar -jxf sagenb-0.8.p2.spkg
[mv...@sage sagenb]$ ls
sagenb-0.7.2.spkg sagenb-0.7.5.2.spkg sagenb-0.8.p2.spkg
sagenb-0.7.5.1.spkg sagenb-0.8
}}}
Notice the directory name `sagenb-0.8`. It should be `sagenb-0.8.p2`. An
updated package with directory name conforming to the Developer's Guide is
available at
http://sage.math.washington.edu/home/mvngu/spkg/standard/sagenb/sagenb-0.8.p2.spkg
This is essentially Tim's spkg, but I changed the name as per above
instructions, prior to tar gzip2 compressing the updated spkg.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8861#comment:7>
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.
