latest sagemath package

[Ondrej Certik]

Hi,

where is the latest 3.0.5dfsg-1 package? I'd like to compile it myself
and test it, before it gets through NEW.

Ondrej

[Timothy G Abbott]

There's a copy at
<http://web.mit.edu/sage/export/new/sagemath_3.0.5dfsg-1.dsc>

-Tim Abbott

[Ondrej Certik]

On Mon, Aug 25, 2008 at 1:03 AM, Timothy G Abbott <tab...@mit.edu> wrote:
>
> There's a copy at
> <http://web.mit.edu/sage/export/new/sagemath_3.0.5dfsg-1.dsc>

Thanks. It failed to build for me though:

make[2]: Entering directory `/home/ondra/debian/sagemath-3.0.5dfsg/spkg'
base/bzip2-1.0.4-install 2>&1
Decompressing bzip2

gzip: ../base/bzip2-1.0.4.tar.gz: unexpected end of file
tar: This does not look like a tar archive
tar: Error exit delayed from previous errors
base/bzip2-1.0.4-install: line 36: cd: bzip2-1.0.4: No such file or directory
make[3]: Entering directory `/home/ondra/debian/sagemath-3.0.5dfsg/spkg/build'
make[3]: *** No targets specified and no makefile found. Stop.
make[3]: Leaving directory `/home/ondra/debian/sagemath-3.0.5dfsg/spkg/build'
Error building bzip2
make[2]: *** [installed/bzip2-1.0.4] Error 1
make[2]: Leaving directory `/home/ondra/debian/sagemath-3.0.5dfsg/spkg'
[...]
mv: cannot stat `usr/lib/python2.5': No such file or directory
make: *** [binary-post-install/sagemath] Error 1
dpkg-buildpackage: failure: fakeroot debian/rules binary gave error
exit status 2

But I haven't tried in pbuilder, so I may have some messed up system.

Ondrej

[Timothy G Abbott]

I assume you're using debuild to build the package? That is what I would
expect to happen if you ran "make" instead...

-Tim Abbott

[Ondrej Certik]

On Mon, Aug 25, 2008 at 5:39 AM, Timothy G Abbott <tab...@mit.edu> wrote:
>
> I assume you're using debuild to build the package? That is what I would
> expect to happen if you ran "make" instead...

I run dpkg-buildpackage.

Ondrej

[Timothy G Abbott]

On Mon, 25 Aug 2008, Ondrej Certik wrote:

Close enough (debuild is a pretty thin wrapper around dpkg-buildpackage).

Well, if you didn't accidentally run "make" instead of something that
executes debian/rules when trying to build my package, I'd appreciate
seeing a full build log so I can debug this.

-Tim Abbott

[Ondrej Certik]

I built it in freshly updated pbuilder with sid and it still fails on
i386. Full build log attached.

Ondrej

P.S. It works on amd64.

[Ondrej Certik]

> Ondrej
>
> P.S. It works on amd64.

By works I meant it builds. I installed it on amd64 and it segfaults:

$ sage
----------------------------------------------------------------------
| SAGE Version 3.0.5, Release Date: 2008-07-11 |
| Type notebook() for the GUI, and license() for information. |
----------------------------------------------------------------------

------------------------------------------------------------
Unhandled SIGSEGV: A segmentation fault occured in SAGE.
This probably occured because a *compiled* component
of SAGE has a bug in it (typically accessing invalid memory)
or is not properly wrapped with _sig_on, _sig_off.
You might want to run SAGE under gdb with 'sage -gdb' to debug this.
SAGE will now terminate (sorry).
------------------------------------------------------------

Here is a stacktrace:

#0 0x00002b74cf20b070 in strlen () from /lib/libc.so.6
No symbol table info available.
#1 0x0000000000455e4b in PyString_FromString ()
No symbol table info available.
#2 0x00002b74e4951a43 in initmulti_polynomial_libsingular ()
from /usr/lib/python2.5/site-packages/sage/rings/polynomial/multi_polynomial_libsingular.so
No symbol table info available.
#3 0x00000000004ab207 in _PyImport_LoadDynamicModule ()
No symbol table info available.
#4 0x00000000004a9764 in ?? ()
No symbol table info available.
#5 0x00000000004a99fc in ?? ()
No symbol table info available.
#6 0x00000000004aa0a1 in ?? ()
No symbol table info available.
#7 0x00000000004aa40f in PyImport_ImportModuleLevel ()
No symbol table info available.
#8 0x000000000048ad39 in ?? ()
No symbol table info available.
#9 0x00000000004187b3 in PyObject_Call ()
No symbol table info available.
#10 0x000000000048b222 in PyEval_CallObjectWithKeywords ()

Looks like a bug in libsingular, no?

ii libsingular-3-0-4-3
3-0-4-3.dfsg-2 Library for commutative algebra, shared
libr

Ondrej

[Timothy G Abbott]

Hmm. Well, the piece of code that isn't working is probably this:

(cd spkg && ./install installed/dir-0.1)
(cd spkg && touch installed/`./standard/newest_version -base bzip2`)

in the debian/stamp-sage-build target, as that is what is supposed to
prevent it from trying to install the (deleted) bzip2 spkg.

Any ideas on why the behavior of that code would vary between our
environments? It works for me on i386 (I've not tested amd64 recently).

-Tim Abbott

[Ondrej Certik]

On Mon, Aug 25, 2008 at 11:44 PM, Timothy G Abbott <tab...@mit.edu> wrote:
>
> Hmm. Well, the piece of code that isn't working is probably this:
>
> (cd spkg && ./install installed/dir-0.1)
> (cd spkg && touch installed/`./standard/newest_version -base bzip2`)
>
> in the debian/stamp-sage-build target, as that is what is supposed to
> prevent it from trying to install the (deleted) bzip2 spkg.
>
> Any ideas on why the behavior of that code would vary between our
> environments? It works for me on i386 (I've not tested amd64 recently).

Have you tested this in pbuilder with sid? This is really weird if it
behaves differently in pbuilder.

Ondrej

[Timothy G Abbott]

Not since July 20 :). But trying again today, it built fine.

-Tim Abbott

[Ondrej Certik]

Ok, if it builds for you in (updated) pbuilder, I suggest we simply
wait until it gets to sid. If it builds for you, it may build on
buildds.

Ondrej