anyone with osx 10.4 intel please test this for dvd

1 view
Skip to first unread message

Joshua Kantor

unread,
Jan 6, 2008, 1:08:50 AM1/6/08
to sage-devel
Hello. for the dvd we are including a dmg file. There was some
problems with the initial version of this. I believe the following is
working,
but if anyone else could test that following the instructions works
fine on their system that would be appreciated. Again this is osx 10.4
intel

http://sage.math.washington.edu/home/jkantor/sage-2.9.2-osx10.4-intel-i386-Darwin.dmg

David Roe

unread,
Jan 6, 2008, 8:35:51 AM1/6/08
to sage-...@googlegroups.com
It worked for me.
David

David Joyner

unread,
Jan 6, 2008, 11:39:55 AM1/6/08
to sage-...@googlegroups.com
I got the error: :the following disk images failed to mount"...
Could be a corrupted download?


On Jan 6, 2008 1:08 AM, Joshua Kantor <kant...@gmail.com> wrote:
>

Justin C. Walker

unread,
Jan 6, 2008, 2:48:39 PM1/6/08
to sage-...@googlegroups.com

Tried this on Mac OS X, 10.4.11, on a Dual Quad Xeon system. I think
it's a success, but there are a few nits. The details:

The DMG mounted successfully, and I dragged the 'sage' folder to a
local disk.

Starting 'sage' in the copied directory gave me the 'may have moved'
message, and then startup completed without a peep.

I ran "make test" (with -j6) in this directory, and this was the
final output:

All tests passed!
Total time for all tests: 2339.3 seconds

However, the ".tex" tests actually all failed. The log file doesn't
show all the details, so I'm including them here. In addition, there
were a batch of dependency warnings. I'm not sure whether they point
to a problem. 'test.log' is at "sage.math.washington.edu:~justin/
logs/dmg-test.log".

Justin

cd spkg && ./install all 2>&1 | tee -a ../install.log
ls: bzip2-*-install: No such file or directory
ls: dir-*-install: No such file or directory
ls: prereq-*-install: No such file or directory
standard/deps:39: warning: overriding commands for target `installed/'
standard/deps:36: warning: ignoring old commands for target `installed/'
standard/deps:42: warning: overriding commands for target `installed/'
standard/deps:39: warning: ignoring old commands for target `installed/'
standard/deps:157: warning: overriding commands for target `installed/'
standard/deps:42: warning: ignoring old commands for target `installed/'
make[1]: Circular installed/python-2.5.1.p10 <- installed/ dependency
dropped.
make[1]: Circular installed/python-2.5.1.p10 <- installed/ dependency
dropped.
make[1]: Circular installed/python-2.5.1.p10 <- installed/ dependency
dropped.
make[1]: Circular installed/zlib-1.2.3.p2 <- installed/ dependency
dropped.
make[1]: Circular installed/zlib-1.2.3.p2 <- installed/ dependency
dropped.
make[1]: Circular installed/zlib-1.2.3.p2 <- installed/ dependency
dropped.
make[1]: Circular installed/termcap-1.3.1 <- installed/ dependency
dropped.
make[1]: Circular installed/termcap-1.3.1 <- installed/ dependency
dropped.
make[1]: Circular installed/termcap-1.3.1 <- installed/ dependency
dropped.
make[1]: Circular installed/readline-5.2 <- installed/ dependency
dropped.
make[1]: Circular installed/readline-5.2 <- installed/ dependency
dropped.
make[1]: Circular installed/readline-5.2 <- installed/ dependency
dropped.
make[1]: Circular installed/libpng-1.2.22.p3 <- installed/ dependency
dropped.
make[1]: Circular installed/libpng-1.2.22.p3 <- installed/ dependency
dropped.
make[1]: Circular installed/libpng-1.2.22.p3 <- installed/ dependency
dropped.
make[1]: Circular installed/ <- installed/ dependency dropped.
make[1]: Circular installed/ <- installed/ dependency dropped.
make[1]: Circular installed/ <- installed/ dependency dropped.
make[1]: Nothing to be done for `all'.

real 0m0.008s
user 0m0.003s
sys 0m0.004s
To install gap, gp, singular, etc., scripts
in a standard bin directory, start sage and
type something like
sage: install_scripts('/usr/local/bin')
at the SAGE command prompt.

SAGE build/upgrade complete!
. local/bin/sage-env && sage-maketest
/tmp/sage/local/bin/sage-maketest: line 4: /tmp/sage/tmp/test.log: No
such file or directory
/tmp/sage/local/bin/sage-maketest: line 5: /tmp/sage/tmp/test.log: No
such file or directory
tee: /tmp/sage/tmp/test.log: No such file or directory
tmp directory doesn't exist - creating ...
dsage-trial tmp directory doesn't exist - creating ...
This script will run the unit tests for DSage
Running 40 tests.
sage.dsage.database.tests.test_clientdb
ClientDatabaseTestCase

testadd_user ... [
OK]

testdel_user ... [
OK]

testset_enabled ... [
OK]

testupdate_login_time ... [
OK]
sage.dsage.database.tests.test_job
JobTestCase

testcreate_job ... [
OK]

testjobCreationTime ... [
OK]

testjobFailures ... [
OK]

testjobFile ... [
OK]

testjobFinishTime ... [
OK]

testjobKilled ... [
OK]

testjobResult ... [
OK]

testjobStatus ... [
OK]

testjobUpdateTime ... [
OK]

testjob_id ... [
OK]
sage.dsage.database.tests.test_jobdb
JobDatabaseSQLiteTestCase

testcreate_jdict ... [
OK]

testget_job ... [
OK]

testget_job_by_id ... [
OK]

testget_killed_jobs_list ... [
OK]

testhas_job ... [
OK]

teststore_job ... [
OK]
sage.dsage.server.tests.test_server
DSageServerTestCase

testget_active_clients_list ... [
OK]

testget_active_jobs ... [
OK]

testget_all_jobs ... [
OK]

testget_job ... [
OK]

testget_job_by_id ... [
OK]

testget_job_result_by_id ... [
OK]

testget_jobs_by_username ... [
OK]

testget_killed_jobs_list ... [
OK]

testjob_done ... [
OK]

testjob_failed ... [
OK]

testkill_job ... [
OK]

testsubmit_job ... [
OK]
sage.dsage.twisted.tests.test_pubkeyauth
PublicKeyCredentialsCheckerTest

testBadLogin3 ... [
OK]

testLogin ... [
OK]
sage.dsage.twisted.tests.test_remote
ClientRemoteCallsTest

testremoteSubmitBadJob ... [
OK]

testremoteSubmitJob ... [
OK]
MonitorRemoteCallsTest

testget_killed_jobs_list ... [
OK]

testremote_get_job ... [
OK]

testremote_job_done ... [
OK]

testremote_job_failed ... [
OK]

------------------------------------------------------------------------
-------
Ran 40 tests in 5.332s

PASSED (successes=40)
Testing of examples currently not implemented.
Testing SAGE documentation
Testing SAGE tutorial
/tmp/sage/local/bin/sage-maketest: line 18: cd: /tmp/sage/devel/doc/
tut: No such file or directory
ERROR: File ./tut.tex is missing
exit code: 1

----------------------------------------------------------------------
The following tests failed:


./tut.tex
Total time for all tests: 0.0 seconds
Testing SAGE programming guide
/tmp/sage/local/bin/sage-maketest: line 22: cd: /tmp/sage/devel/doc/
prog: No such file or directory
ERROR: File ./prog.tex is missing
exit code: 1

----------------------------------------------------------------------
The following tests failed:


./prog.tex
Total time for all tests: 0.0 seconds
Testing SAGE constructions guide
/tmp/sage/local/bin/sage-maketest: line 26: cd: /tmp/sage/devel/doc/
const: No such file or directory
ERROR: File ./const.tex is missing
exit code: 1

----------------------------------------------------------------------
The following tests failed:


./const.tex
Total time for all tests: 0.0 seconds

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk
--------

Joshua Kantor

unread,
Jan 6, 2008, 3:25:24 PM1/6/08
to sage-devel
David, can you test the md5sum of the downloaded .dmg file.
At the terminal
md5 <file name>

mabshoff

unread,
Jan 6, 2008, 3:42:34 PM1/6/08
to sage-devel


On Jan 6, 8:48 pm, "Justin C. Walker" <jus...@mac.com> wrote:
> On Jan 5, 2008, at 22:08 , Joshua Kantor wrote:
>
>
>
> > Hello. for the dvd we are including a dmg file. There was some
> > problems with the initial version of this. I believe the following is
> > working,
> > but if anyone else could test that following the instructions works
> > fine on their system that would be appreciated. Again this is osx 10.4
> > intel
>
> >http://sage.math.washington.edu/home/jkantor/sage-2.9.2-osx10.4-
> > intel-i386-Darwin.dmg
>
> Tried this on Mac OS X, 10.4.11, on a Dual Quad Xeon system. I think
> it's a success, but there are a few nits. The details:
>
> The DMG mounted successfully, and I dragged the 'sage' folder to a
> local disk.

That might be the problem since dragging the folder breaks symlinks.
Can you try again with "cp -R -P" - there should be some Readme in the
folder that has installations instructions.

> Starting 'sage' in the copied directory gave me the 'may have moved'
> message, and then startup completed without a peep.
>
> I ran "make test" (with -j6) in this directory, and this was the
> final output:
>
> All tests passed!
> Total time for all tests: 2339.3 seconds
>
> However, the ".tex" tests actually all failed. The log file doesn't
> show all the details, so I'm including them here. In addition, there
> were a batch of dependency warnings. I'm not sure whether they point
> to a problem. 'test.log' is at "sage.math.washington.edu:~justin/
> logs/dmg-test.log".
>
> Justin

Cheers,

Michael

<SNIP>

> --
> Justin C. Walker, Curmudgeon-At-Large
> Institute for the Enhancement of the Director's Income
> --------
> When LuteFisk is outlawed,
> Only outlaws will have LuteFisk

+1 - think of the children :)

> --------

Justin C. Walker

unread,
Jan 6, 2008, 5:00:10 PM1/6/08
to sage-...@googlegroups.com

On Jan 6, 2008, at 12:25 , Joshua Kantor wrote:

>
> David, can you test the md5sum of the downloaded .dmg file.
> At the terminal
> md5 <file name>

FWIW, I get:

MD5 (/SandBox/DownLoads/sage-2.9.2-osx10.4-intel-i386-Darwin.dmg) =
7bdaf64293d8136aa0d59c89b894ca79

Justin

--
Justin C. Walker, Curmudgeon-At-Large, Director


Institute for the Enhancement of the Director's Income
--------

The path of least resistance:
it's not just for electricity any more.
--------

Justin C. Walker

unread,
Jan 6, 2008, 5:27:49 PM1/6/08
to sage-...@googlegroups.com

On Jan 6, 2008, at 12:42 , mabshoff wrote:

>
>
>
> On Jan 6, 8:48 pm, "Justin C. Walker" <jus...@mac.com> wrote:
>> On Jan 5, 2008, at 22:08 , Joshua Kantor wrote:
>>
>>
>>
>>> Hello. for the dvd we are including a dmg file. There was some
>>> problems with the initial version of this. I believe the
>>> following is
>>> working,
>>> but if anyone else could test that following the instructions works
>>> fine on their system that would be appreciated. Again this is osx
>>> 10.4
>>> intel
>>
>>> http://sage.math.washington.edu/home/jkantor/sage-2.9.2-osx10.4-
>>> intel-i386-Darwin.dmg
>>
>> Tried this on Mac OS X, 10.4.11, on a Dual Quad Xeon system. I think
>> it's a success, but there are a few nits. The details:
>>
>> The DMG mounted successfully, and I dragged the 'sage' folder to a
>> local disk.
>
> That might be the problem since dragging the folder breaks symlinks.
> Can you try again with "cp -R -P" - there should be some Readme in the
> folder that has installations instructions.

I know that was a problem, but Josh asked us to 'follow the
instructions', so, following instructions, I followed the instructions.

However, I have now followed your instructions (to use "cp -R -
P ..."), and I find that the results are the same (no differences
between what I reported earlier and this time).

:-}

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Enhancement of the Director's Income
--------
When LuteFisk is outlawed,
Only outlaws will have LuteFisk

--------

David Roe

unread,
Jan 6, 2008, 5:36:24 PM1/6/08
to sage-...@googlegroups.com
> David, can you test the md5sum of the downloaded .dmg file.
> At the terminal
> md5 <file name>

FWIW, I get:

MD5 (/SandBox/DownLoads/sage-2.9.2-osx10.4-intel-i386-Darwin.dmg) =
7bdaf64293d8136aa0d59c89b894ca79

I get the same:

MD5 (sage-2.9.2-osx10.4-intel-i386-Darwin.dmg) = 7bdaf64293d8136aa0d59c89b894ca79

For reference I used the finder to move the sage folder to Applications rather than the command line.
David

Joshua Kantor

unread,
Jan 6, 2008, 6:19:03 PM1/6/08
to sage-devel
I wanted to check that moving via finder work. So thats good.

The tex issue may be because I created the binary dist from another
binary dist.
I was mostly worried about moving via finder because that did not work
in the initial version.

I have no idea why david joyner couldn't mount it, hopefully his md5
doesn't agree with yours which are correct.


Josh

Justin C. Walker

unread,
Jan 6, 2008, 7:17:18 PM1/6/08
to sage-...@googlegroups.com

On Jan 6, 2008, at 15:19 , Joshua Kantor wrote:

>
> I wanted to check that moving via finder work. So thats good.
>
> The tex issue may be because I created the binary dist from another
> binary dist.
> I was mostly worried about moving via finder because that did not work
> in the initial version.
>
> I have no idea why david joyner couldn't mount it, hopefully his md5
> doesn't agree with yours which are correct.

It does look like you nailed the 'move by Finder' problem.

Are the "dependency" problems ("warning: overriding" and "dependency
dropped") and "ls" failures just cosmetic?

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------
If it weren't for carbon-14, I wouldn't date at all.
-----------


William Stein

unread,
Jan 7, 2008, 12:06:03 AM1/7/08
to sage-...@googlegroups.com
On Jan 6, 2008 4:17 PM, Justin C. Walker <jus...@mac.com> wrote:
>
>
> On Jan 6, 2008, at 15:19 , Joshua Kantor wrote:
>
> >
> > I wanted to check that moving via finder work. So thats good.
> >
> > The tex issue may be because I created the binary dist from another
> > binary dist.

The binary distribution doesn't contain the devel/doc-main directory
at present, hence the doctests on those files will fail since they aren't
there. The doctest failure above from your email hints at this:

"Testing SAGE tutorial
/tmp/sage/local/bin/sage-maketest: line 18: cd: /tmp/sage/devel/doc/
tut: No such file or directory
ERROR: File ./tut.tex is missing
exit code: 1"


Options:
(1) Add the pure tex files into bdist, or
(2) Add all of doc-main to bdist (we include sage-main)
(3) Remove testing the tex files from "make check" for bdist.

What do you guys think? I like (2).

William


> > I was mostly worried about moving via finder because that did not work
> > in the initial version.
> >
> > I have no idea why david joyner couldn't mount it, hopefully his md5
> > doesn't agree with yours which are correct.
>
> It does look like you nailed the 'move by Finder' problem.
>
> Are the "dependency" problems ("warning: overriding" and "dependency
> dropped") and "ls" failures just cosmetic?
>
> Justin
>
> --
> Justin C. Walker, Curmudgeon at Large
> Institute for the Absorption of Federal Funds
> -----------
> If it weren't for carbon-14, I wouldn't date at all.
> -----------
>
>
>
>
> >
>

--
William Stein
Associate Professor of Mathematics
University of Washington
http://wstein.org

Justin C. Walker

unread,
Jan 7, 2008, 12:52:08 AM1/7/08
to sage-...@googlegroups.com

On Jan 6, 2008, at 21:06 , William Stein wrote:

>
> On Jan 6, 2008 4:17 PM, Justin C. Walker <jus...@mac.com> wrote:
>>
>>
>> On Jan 6, 2008, at 15:19 , Joshua Kantor wrote:
>>
>>>
>>> I wanted to check that moving via finder work. So thats good.
>>>
>>> The tex issue may be because I created the binary dist from another
>>> binary dist.
>
> The binary distribution doesn't contain the devel/doc-main directory
> at present, hence the doctests on those files will fail since they
> aren't
> there. The doctest failure above from your email hints at this:
>
> "Testing SAGE tutorial
> /tmp/sage/local/bin/sage-maketest: line 18: cd: /tmp/sage/devel/doc/
> tut: No such file or directory
> ERROR: File ./tut.tex is missing
> exit code: 1"

I saw that, but wasn't sure whether those directories were
deliberately, or accidentally, missing :-}

> Options:
> (1) Add the pure tex files into bdist, or
> (2) Add all of doc-main to bdist (we include sage-main)
> (3) Remove testing the tex files from "make check" for bdist.
>
> What do you guys think? I like (2).

It costs a mere 80MB or so, right? How critical is that size
difference?

I'd think it a good idea to include at least the primary doc set, or
maybe just the html set...

Justin

--
They said it couldn't be done, but sometimes,
it doesn't work out that way.
- Casey Stengel
--

William Stein

unread,
Jan 7, 2008, 1:08:50 AM1/7/08
to sage-...@googlegroups.com

The html documentation is included. It is in SAGE_ROOT/doc/

However, I think the tex files are not in there.

-- Wiliam

Justin C. Walker

unread,
Jan 7, 2008, 1:44:45 AM1/7/08
to sage-...@googlegroups.com

On Jan 6, 2008, at 22:08 , William Stein wrote:
> On Jan 6, 2008 9:52 PM, Justin C. Walker <jus...@mac.com> wrote:
>> On Jan 6, 2008, at 21:06 , William Stein wrote:
[snip]

>>> Options:
>>> (1) Add the pure tex files into bdist, or
>>> (2) Add all of doc-main to bdist (we include sage-main)
>>> (3) Remove testing the tex files from "make check" for bdist.
>>>
>>> What do you guys think? I like (2).
>>
>> It costs a mere 80MB or so, right? How critical is that size
>> difference?
>>
>> I'd think it a good idea to include at least the primary doc set, or
>> maybe just the html set...
>
> The html documentation is included. It is in SAGE_ROOT/doc/
>
> However, I think the tex files are not in there.

Neither the tex/pdf nor the html doc appear to be in the .dmg's I
downloaded. 'sage-bdist' certainly *looks* like it should copy it,
but there is no 'html' in $SAGE_ROOT.

Here's what I see:

$ ls
COPYING.txt examples
matplotlibrc test.log
README.txt install.log
sage tmp
data ipython sage-2.9.1.txt
devel local sage-README-osx.txt
example.sage makefile spkg

$ find . -name html
./local/LIB/r/doc/html
./local/LIB/r/src/gnuwin32/fixed/html
./local/share/maxima/5.13.0/doc/html
./local/share/maxima/5.13.0/xmaxima/html
./local/share/moin/htdocs/applets/FCKeditor/_samples/html

Justin

--
Justin C. Walker, Curmudgeon at Large
Institute for the Absorption of Federal Funds
-----------

I'm beginning to like the cut of his jibberish.
-----------

William Stein

unread,
Jan 7, 2008, 4:01:31 AM1/7/08
to sage-...@googlegroups.com

OK, then this is definitely a bug, unless Josh messed something
up in making the dmg. I've made this trac 1708:

http://trac.sagemath.org/sage_trac/ticket/1708

Joshua Kantor

unread,
Jan 7, 2008, 4:11:56 AM1/7/08
to sage-devel
Even in the original dmg that I used to make my dmg, there were no tex
files.
In devel there was only sage and sage-main, no doc and doc-main.


Josh

Justin C. Walker

unread,
Jan 7, 2008, 4:40:11 AM1/7/08
to sage-...@googlegroups.com

On Jan 7, 2008, at 01:01 , William Stein wrote:

>
> On Jan 6, 2008 10:44 PM, Justin C. Walker <jus...@mac.com> wrote:

[snip]


>> Neither the tex/pdf nor the html doc appear to be in the .dmg's I
>> downloaded. 'sage-bdist' certainly *looks* like it should copy it,
>> but there is no 'html' in $SAGE_ROOT.

[snip]


> OK, then this is definitely a bug, unless Josh messed something
> up in making the dmg. I've made this trac 1708:
>
> http://trac.sagemath.org/sage_trac/ticket/1708

I just did a '-bdist' of a "full-build" install of 2.9.2.

The result has the doc directory, but there is no "html" directory in
$SAGE_LOCAL of the built 'bdist'.

Not sure what that means...

Justin

--
Justin C. Walker, Curmudgeon-At-Large


Institute for the Absorption of Federal Funds
--------

If you're not confused,
You're not paying attention
--------

Reply all
Reply to author
Forward
0 new messages