Sage 8.9.beta9 released

263 views
Skip to first unread message

Volker Braun

unread,
Sep 2, 2019, 7:22:40 PM9/2/19
to sage-release
As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html 


bdf4b23d74 (trac/develop, tag: 8.9.beta9) Updated SageMath version to 8.9.beta9
c631202c12 Trac #28411: refresh the prompt in the installation guide
45482b13f0 Trac #28387: Implement function that returns the balanced digit representation of an integer
4454ffec0d Trac #28384: py2: UnicodeDecodeError in doctest framework exception handling
0c8192c3de Trac #28366: Lattice precision timing test fails on Windows 7 due to low-ish clock resolution
5e1b351a89 Trac #28274: EnumeratedFamily should use integers as keys
ec9715bb88 Trac #28172: Profile of a Finite Permutation Group
dcf58df8b5 Trac #28154: SciPy: patch for missing coding lines in some source files
82d75fd335 Trac #27917: Standardize doctest headers
04d5aab185 Trac #25817: RuntimeError: Encountered operator mismatch in maxima-to-sr translation, integrate
45314bcbcf Trac #23639: Strange errors with roots() of polynomials over polynomial rings
f29cee985f Trac #28419: new pyflakes miscellanous cleanup
77bddf472a Trac #28417: removed deprecated stuff in integer_mod
c565a3aa0a Trac #28412: upgrade Pynac to 0.7.26
2e47b34ab8 Trac #28408: fixing a few invalid escape sequences
877d26294b Trac #28407: py3: fix quantum_group_gap and graph_latex
3db8be3dc0 Trac #28399: remove deprecated things in integer.pyx
6a837c5ea6 Trac #27818: Meet-subsemilattice for lattices
2920f66a0e Trac #27798: Add `backend` option to associahedron and flow polytope
98f3199887 Trac #27587: Follow up to #25680: Fix tempfile handling in doctests
0719be21c2 Trac #27473: Matrix inversion fails over a Laurent series ring
842a3dcd41 Trac #27444: Expose multithreaded fflas-ffpack features
cee95e6b38 Trac #28404: Sign of hypergeometric motives is sometimes wrong
af8bf5ead8 Trac #28400: fixing a few roles
1cdf4955c6 Trac #28398: _richcmp_ for quaternion algebra elements
abb2397287 Trac #28397: fix some wrong doctests that were not run
2465a9e494 Trac #28396: faster Möbius matrix for Hasse diagrams
4b4b5bf81b Trac #28395: Bug in is_weil_polynomial
77466c5716 Trac #28393: add self-tests for polymake
a7f0a353e5 Trac #28391: dependencies file for jupymake
e7a3ec0d98 Trac #28377: polymake interface broken with "non-standard" quadratic fields
a535670711 Trac #28339: Random failure in src/sage/interfaces/expect.py
f34f77e4da Trac #28271: Implement LexM traversal
304feb1626 Trac #28229: Generalized shifted prime tableau
e570374675 Trac #27689: Implement is_pyramid, is_bipyramid, is_prism for polytopes
addde7bcc7 Trac #28380: bump up the version of givaro in spkg-configure.m4
8f1c30f031 Trac #28403: py3: crypto/block_cipher/present.py doctest failures
0ae7ffa669 Trac #25727: Prevent giac from giving localized output
109c1bd6c1 Trac #28060: Extensions of finite fields embeddings: we have inverse image but `inverse_image` throws `NotImplemented`
0c5c45c0cf Trac #27937: Fix for functorial construction of monoid algebras
fee35bf412 Trac #27851: Convert sqrt(D) to UCF
3b7ef2c62c Trac #27831: Small fix for is_symmetric for matrices over CDF
8f76f4d242 Trac #27760: Generalized Permutohedra and type H4 4-uniform polytopes
67de66d92d Trac #27096: Bug in Buchberger algorithm over Tate algebra
6b8839d39f Trac #25823: maxima segfaults on integral computation
4583b4056e (tag: 8.9.beta8, trac/develop) Updated SageMath version to 8.9.beta8

Emmanuel Charpentier

unread,
Sep 3, 2019, 8:35:35 AM9/3/19
to sage-release
On Debian testing running on core i5 + 8 GB RAM, upgrading a Python 3-based Sage 8.9.beta8 to beta9 gives me one permanent failure of prest-python3, already multireported:

charpent@p-202-021:/usr/local/sage-python3$ sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx
too many failed tests, not using stored timings
Running doctests with ID 2019-09-03-14-30-52-f99cf583.
Git branch: develop
Using --optional=build,dochtml,dot2tex,fricas,giacpy_sage,memlimit,python2,sage
Doctesting 1 file.
sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx
**********************************************************************
File "src/sage/rings/polynomial/polynomial_rational_flint.pyx", line 2055, in sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
Failed example:
    G = f.galois_group(); G
Expected:
    Transitive group number 5 of degree 4
Got:
    Exception (FLINT memory_manager). Unable to allocate memory.
    Transitive group number 5 of degree 4
**********************************************************************
1 item had failures:
   1 of  16 in sage.rings.polynomial.polynomial_rational_flint.Polynomial_rational_flint.galois_group
    [397 tests, 1 failure, 3.32 s]
----------------------------------------------------------------------
sage -t --long src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 1 doctest failed
----------------------------------------------------------------------
Total time for all tests: 3.4 seconds
    cpu time: 3.3 seconds
    cumulative wall time: 3.3 seconds

HTH,

Emmanuel Charpentier

unread,
Sep 3, 2019, 11:14:49 AM9/3/19
to sage-release
On another maciine (Debian testing running on core i7 + 16 GB RAM), upgrading a Python 3-based Sage 8.9.beta8 to beta9 gives me the same permanent failure of prest-python3, pl;us another (also already reported):

charpent@zen-book-flip:/usr/local/sage-P3-2$ sage -t --long --warn-long 157.5 src/sage/graphs/strongly_regular_db.pyx
Running doctests with ID 2019-09-03-17-05-16-9c475f15.
Git branch: develop
Using --optional=build,dochtml,dot2tex,fricas,gap_packages,giacpy_sage,libsemigroups,memlimit,python2,sage
Doctesting 1 file.
sage -t --long --warn-long 157.5 src/sage/graphs/strongly_regular_db.pyx
**********************************************************************
File "src/sage/graphs/strongly_regular_db.pyx", line 2324, in sage.graphs.strongly_regular_db.SRG_280_135_70_60
Failed example:
    g=SRG_280_135_70_60()                  # long time # optional - gap_packages
Exception raised:
    Traceback (most recent call last):
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/gap.py", line 763, in _eval_line
        raise RuntimeError("%s produced error output\n%s\n   executing %s"%(self, error,line))
    RuntimeError: Gap produced error output
    Error, Record Element: <rec> must be a record (not a boolean or fail)

       executing \$sage1:=AtlasGenerators("J2",2).generators;;

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/expect.py", line 1471, in __init__
        self._name = parent._create(value, name=name)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/interface.py", line 491, in _create
        self.set(name, value)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/gap.py", line 1421, in set
        self._eval_line(cmd, allow_use_file=True)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/gap.py", line 797, in _eval_line
        raise RuntimeError(exc)
    RuntimeError: Gap produced error output
    Error, Record Element: <rec> must be a record (not a boolean or fail)

       executing \$sage1:=AtlasGenerators("J2",2).generators;;

    During handling of the above exception, another exception occurred:

    Traceback (most recent call last):
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 681, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 1123, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.graphs.strongly_regular_db.SRG_280_135_70_60[1]>", line 1, in <module>
        g=SRG_280_135_70_60()                  # long time # optional - gap_packages
      File "sage/graphs/strongly_regular_db.pyx", line 2335, in sage.graphs.strongly_regular_db.SRG_280_135_70_60 (build/cythonized/sage/graphs/strongly_regular_db.c:34133)
        J2    = PermutationGroup(gap('AtlasGenerators("J2",2).generators'))
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/interface.py", line 288, in __call__
        return cls(self, x, name=name)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/expect.py", line 1476, in __init__
        raise_(TypeError, TypeError(*x.args), sys.exc_info()[2])
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/six.py", line 692, in reraise
        raise value.with_traceback(tb)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/expect.py", line 1471, in __init__
        self._name = parent._create(value, name=name)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/interface.py", line 491, in _create
        self.set(name, value)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/gap.py", line 1421, in set
        self._eval_line(cmd, allow_use_file=True)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/interfaces/gap.py", line 797, in _eval_line
        raise RuntimeError(exc)
    TypeError: Gap produced error output
    Error, Record Element: <rec> must be a record (not a boolean or fail)

       executing \$sage1:=AtlasGenerators("J2",2).generators;;
**********************************************************************
File "src/sage/graphs/strongly_regular_db.pyx", line 2325, in sage.graphs.strongly_regular_db.SRG_280_135_70_60
Failed example:
    g.is_strongly_regular(parameters=True) # long time # optional - gap_packages
Exception raised:
    Traceback (most recent call last):
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 681, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 1123, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.graphs.strongly_regular_db.SRG_280_135_70_60[2]>", line 1, in <module>
        g.is_strongly_regular(parameters=True) # long time # optional - gap_packages
    NameError: name 'g' is not defined
**********************************************************************
File "src/sage/graphs/strongly_regular_db.pyx", line 2451, in sage.graphs.strongly_regular_db.SRG_416_100_36_20
Failed example:
    g = SRG_416_100_36_20()                # optional - gap_packages # long time
Exception raised:
    Traceback (most recent call last):
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 681, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 1123, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.graphs.strongly_regular_db.SRG_416_100_36_20[1]>", line 1, in <module>
        g = SRG_416_100_36_20()                # optional - gap_packages # long time
      File "sage/graphs/strongly_regular_db.pyx", line 2461, in sage.graphs.strongly_regular_db.SRG_416_100_36_20 (build/cythonized/sage/graphs/strongly_regular_db.c:36293)
        h.add_edges(g.Orbit([1,5],libgap.OnSets))
      File "sage/libs/gap/element.pyx", line 2669, in sage.libs.gap.element.GapElement_MethodProxy.__call__ (build/cythonized/sage/libs/gap/element.c:20251)
        return GapElement_Function.__call__(self, * ([self.first_argument] + list(args)))
      File "sage/libs/gap/element.pyx", line 2517, in sage.libs.gap.element.GapElement_Function.__call__ (build/cythonized/sage/libs/gap/element.c:19264)
        sig_on()
    sage.libs.gap.util.GAPError: Error, no method found! Error, no 1st choice method found for `GeneratorsOfMagmaWithInverses' on 1 arguments
    The 1st argument is 'fail' which might point to an earlier problem
**********************************************************************
File "src/sage/graphs/strongly_regular_db.pyx", line 2452, in sage.graphs.strongly_regular_db.SRG_416_100_36_20
Failed example:
    g.is_strongly_regular(parameters=True) # optional - gap_packages # long time
Exception raised:
    Traceback (most recent call last):
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 681, in _run
        self.compile_and_execute(example, compiler, test.globs)
      File "/usr/local/sage-P3-2/local/lib/python3.7/site-packages/sage/doctest/forker.py", line 1123, in compile_and_execute
        exec(compiled, globs)
      File "<doctest sage.graphs.strongly_regular_db.SRG_416_100_36_20[2]>", line 1, in <module>
        g.is_strongly_regular(parameters=True) # optional - gap_packages # long time
    NameError: name 'g' is not defined
**********************************************************************
2 items had failures:
   2 of   4 in sage.graphs.strongly_regular_db.SRG_280_135_70_60
   2 of   4 in sage.graphs.strongly_regular_db.SRG_416_100_36_20
    [334 tests, 4 failures, 282.80 s]
----------------------------------------------------------------------
sage -t --long --warn-long 157.5 src/sage/graphs/strongly_regular_db.pyx  # 4 doctests failed
----------------------------------------------------------------------
Total time for all tests: 282.9 seconds
    cpu time: 22.1 seconds
    cumulative wall time: 282.8 seconds

HTH,

John H Palmieri

unread,
Sep 3, 2019, 6:58:30 PM9/3/19
to sage-release
With a Python 3 build on OS X, I get a sporadic failure in numerical/linear_tensor_element.pyx — it fails not every time, but at least half the time. As far as I can tell, this is due to #27587 (that is, I get failures with 8.9.beta8 + that ticket, but not with 8.9.beta8), but I don't understand why.

$ ./sage -t src/sage/numerical/linear_tensor_element.pyx
too many failed tests, not using stored timings
Running doctests with ID 2019-09-03-15-54-33-30edf809.
Git branch: develop
Using --optional=build,dochtml,python2,sage
Doctesting 1 file.
glp_free: memory allocation error
Error detected in file env/alloc.c at line 72
------------------------------------------------------------------------
0   signals.cpython-37m-darwin.so       0x00000001026c50ba print_backtrace + 58
...
  [snip]
...
56  libsystem_pthread.dylib             0x00007fff667b940d thread_start + 13
------------------------------------------------------------------------
Unhandled SIGABRT: An abort() occurred.
This probably occurred because a *compiled* module has a bug
in it and is not properly wrapped with sig_on(), sig_off().
Python will now terminate.
------------------------------------------------------------------------
sage -t src/sage/numerical/linear_tensor_element.pyx
    Killed due to abort
**********************************************************************
Tests run before process (pid=20158) failed:
sage: mip.<x> = MixedIntegerLinearProgram('ppl')   # base ring is QQ ## line 6 ##
sage: lt = x[0] * vector([3,4]) + 1;   lt ## line 7 ##
(1, 1) + (3, 4)*x_0
...
  [snip]
...
sage: len(list(d)) ## line 467 ##
2
sage: sig_on_count() # check sig_on/off pairings (virtual doctest) ## line 469 ##
0

**********************************************************************
----------------------------------------------------------------------
sage -t src/sage/numerical/linear_tensor_element.pyx  # Killed due to abort
----------------------------------------------------------------------

Sébastien Labbé

unread,
Sep 4, 2019, 3:14:02 AM9/4/19
to sage-release
Running ptestlong with few optional + external packages including

Using --optional=awali,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage

I obtain:

----------------------------------------------------------------------
sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
sage -t --long src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed
----------------------------------------------------------------------
External software detected for doctesting: ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc

Repeating failed tests, I obtain:

----------------------------------------------------------------------
sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed
sage -t --long src/sage/databases/oeis.py  # 1 doctest failed
sage -t --long src/sage/databases/findstat.py  # 8 doctests failed
----------------------------------------------------------------------
External software detected for doctesting: internet

The oeis one is copied below (ticket has still to be created). Other failures can be followed at https://trac.sagemath.org/ticket/25536


sage -t --long src/sage/databases/oeis.py
**********************************************************************
File "src/sage/databases/oeis.py", line 90, in sage.databases.oeis
Failed example:
    p.cross_references(fetch=True)                # optional -- internet
Expected:
    0: A000798: Number of different quasi-orders (or topologies, or transitive digraphs) with n labeled elements.
    1: A001035: Number of partially ordered sets ("posets") with n labeled elements (or labeled acyclic transitive digraphs).
    2: A001930: Number of topologies, or transitive digraphs with n unlabeled nodes.
    3: A006057: Number of topologies on n labeled points satisfying axioms T_0-T_4.
    4: A079263: Number of constrained mixed models with n factors.
    5: A079265: Number of antisymmetric transitive binary relations on n unlabeled points.
    6: A263859: Triangle read by rows: T(n,k) (n>=1, k>=0) is the number of posets with n elements and rank k (or depth k+1).
Got:
     0: A000798: Number of different quasi-orders (or topologies, or transitive digraphs) with n labeled elements.
     1: A001035: Number of partially ordered sets ("posets") with n labeled elements (or labeled acyclic transitive digraphs).
     2: A001930: Number of topologies, or transitive digraphs with n unlabeled nodes.
     3: A006057: Number of topologies on n labeled points satisfying axioms T_0-T_4.
     4: A079263: Number of constrained mixed models with n factors.
     5: A079265: Number of antisymmetric transitive binary relations on n unlabeled points.
     6: A263859: Triangle read by rows: T(n,k) (n>=1, k>=0) is the number of posets with n elements and rank k (or depth k+1).
     7: A316978: Number of factorizations of n into factors > 1 with no equivalent primes.
     8: A319559: Number of non-isomorphic T_0 set systems of weight n.
     9: A326939: Number of T_0 sets of subsets of {1..n} that cover all n vertices.
    10: A326943: Number of T_0 sets of subsets of {1..n} that cover all n vertices and are closed under intersection.
    11: A326944: Number of T_0 sets of subsets of {1..n} that cover all n vertices, contain {}, and are closed under intersection.
    12: A326947: BII-numbers of T_0 set-systems.

**********************************************************************
1 item had failures:
   1 of  26 in sage.databases.oeis
    5 webbrowser tests not run
    0 tests not run because we ran out of time
    [266 tests, 1 failure, 62.87 s]

E. Madison Bray

unread,
Sep 4, 2019, 5:30:41 AM9/4/19
to sage-r...@googlegroups.com
Although it might be a little late, at this point, if we want to make
sure it's well-enough tested, I think we should try to include the
following in 8.9 final:

https://trac.sagemath.org/ticket/28356

As discussed when the first version of this code was added, it's
actually reasonably robust and might happen to fix other docbuild
hanging issues that have been reported (or at least the one we do know
the cause of; I don't know if there are other causes). Everyone who's
tested this has built the docs successfully with it, and the code
itself is generally well-reviewed.

OTOH I can't promise there are *no* bugs--just not any I have found yet.
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/81faec30-03eb-4a66-b110-6417607004a7%40googlegroups.com.

Dima Pasechnik

unread,
Sep 4, 2019, 5:35:10 AM9/4/19
to sage-release
On Wed, Sep 4, 2019 at 10:30 AM E. Madison Bray <erik....@gmail.com> wrote:
>
> Although it might be a little late, at this point, if we want to make
> sure it's well-enough tested, I think we should try to include the
> following in 8.9 final:
>
> https://trac.sagemath.org/ticket/28356

yes please, and also two other (and much smaller) bug-fixing tickets related to
configure with external packages,
https://trac.sagemath.org/ticket/28401
and
https://trac.sagemath.org/ticket/28405
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAOTD34YVLBe_NjBF%2Bk1NqHhTQUzxU-uWVvt%2BJ0aofk-QFTH%3Dkg%40mail.gmail.com.

Eric Gourgoulhon

unread,
Sep 4, 2019, 10:11:49 AM9/4/19
to sage-release
On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM:

- python2:

  - incremental build (from 8.9.beta8, with -j16) OK
  - all tests from ptestlong passed

- python3:

  - incremental build (from 8.9.beta8, with -j16) OK

  - tests from ptest-python3 passed, except for
    - 1 permanent failure in
       src/sage/rings/polynomial/polynomial_rational_flint.pyx
       this is the error tracked at https://trac.sagemath.org/ticket/28334
    - 1 transient (i.e. passed when run standalone) failure in
       src/sage/interfaces/psage.py
       (cf. the attached log)

   - tests from ptestlong passed, except for a rather short list now:

----------------------------------------------------------------------
sage -t --long --warn-long 53.7 src/sage/combinat/root_system/weyl_group.py  # 7 doctests failed
sage -t --long --warn-long 53.7 src/sage/libs/eclib/interface.py  # 1 doctest failed
sage -t --long --warn-long 53.7 src/sage/rings/polynomial/polynomial_rational_flint.pyx  # 1 doctest failed
sage -t --long --warn-long 53.7 src/sage/repl/attach.py  # 4 doctests failed
sage -t --long --warn-long 53.7 src/sage/libs/singular/function.pyx  # 1 doctest failed
sage -t --long --warn-long 53.7 src/sage/numerical/backends/generic_backend.pyx  # 2 doctests failed
----------------------------------------------------------------------

      The failed docstests are those tracked at https://trac.sagemath.org/ticket/28298
      The last three ones, which are denoted respectively by (J), (H) and (I) in #28298, are passed when run standalone.
      The other ones (i.e. the first three lines in the above list) are permanent on this computer.

Eric.


error_psage.log

Justin C. Walker

unread,
Sep 4, 2019, 5:37:13 PM9/4/19
to 'Justin C. Walker' via sage-release


> On Sep 2, 2019, at 16:22 , Volker Braun <vbrau...@gmail.com> wrote:
>
> As always, you can get the latest beta version from the "develop" git branch. Alternatively, the self-contained source tarball is at http://www.sagemath.org/download-latest.html

And again:

As with 8.9-b6, 8.9-b7, and -b8, the build, from a fresh clone of the develop branch, worked w/o problems, on three macOS systems: 10.11.6 (mid-2015 MBP, Quad-core i7), 10.13.6 (2017 iMac Pro, 18-core Xeon W), and 10.14.6 (2017 MBP, Quad-core Core i7).

Testing (‘ptestlong’):
- all tests passed on 10.11.6 and 10.14.6
- test failures in one file on 10.13.6:
1 item had failures:
----------------------------------------------------------------------
sage -t --long --warn-long 71.5 src/sage/libs/singular/polynomial.pyx # 1 doctest failed
———————————————————————————————————

For 8.9-b6, the test failed twice when run by itself.
For 8.9-b7, the test passed twice when run by itself.
For 8.9-b8, the test failed twice when run by itself.
Again this time, 8.9-b9, the test failed twice when run by itself.

Justin

--
Justin C. Walker, Curmudgeon-At-Large
Director
Institute for the Enhancement of the Director's Income
--------
"Weaseling out of things is what separates us from the animals.
Well, except the weasel."
- Homer J Simpson
--------


E. Madison Bray

unread,
Sep 6, 2019, 5:36:53 AM9/6/19
to sage-r...@googlegroups.com
Consistently getting a test failure on Cygwin related to some oddity in GAP:

sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py
**********************************************************************
File "src/sage/tests/cmdline.py", line 535, in
sage.tests.cmdline.test_executable
Failed example:
out
Expected:
'120\n'
Got:
"you can 'quit;' to quit to outer loop, or\nyou can 'return;' to continue\n"
**********************************************************************
File "src/sage/tests/cmdline.py", line 537, in
sage.tests.cmdline.test_executable
Failed example:
err.replace('gap: halving pool size.', '').strip()
Expected:
''
Got:
'Error, <str> must not contain \'\\\' or \':\' at
/home/embray/src/sagemath/sage/local/share/gap/lib/files.gi:53 called
from\nfunc( C[i] ) at
/home/embray/src/sagemath/sage/local/share/gap/lib/coll.gi:665 called
from\nList( GAPInfo.DirectoriesSystemPrograms, Directory \n ) at
/home/embray/src/sagemath/sage/local/share/gap/lib/files.gd:420 called
from\n<function "DirectoriesSystemPrograms">( <arguments> )\n called
from read-eval loop at
/home/embray/src/sagemath/sage/local/share/gap/pkg/alnuth-3.1.1/defs.g:10\nbrk>
120\nbrk>'
**********************************************************************
1 item had failures:
2 of 251 in sage.tests.cmdline.test_executable
[250 tests, 2 failures, 273.09 s]
----------------------------------------------------------------------
sage -t --long --warn-long 109.3 src/sage/tests/cmdline.py # 2 doctests failed
----------------------------------------------------------------------

Can't be sure yet that it isn't just a weird, localized issue in my
installation. Will investigate.

On Tue, Sep 3, 2019 at 1:22 AM Volker Braun <vbrau...@gmail.com> wrote:
>

E. Madison Bray

unread,
Sep 6, 2019, 6:13:07 AM9/6/19
to sage-r...@googlegroups.com
Yes, that's all it was. I had a PATH entry with a \ in it, thanks to
conda still being a bit buggy on Cygwin :) Conversely, I don't think
GAP should blow up in this case either. So, two issues to file....
\o/

Dima Pasechnik

unread,
Sep 6, 2019, 6:26:57 AM9/6/19
to sage-release
as I am now (and till March 2020) officially working for St. Andrews,
I'll lookng forward to GAP issues, please CC me there :-)

Dima
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAOTD34ZPU-mguVfhOucxc2NeNAzGxUaZ-iLP0O%2Bqj8BCB2NMmg%40mail.gmail.com.

Mariel Supina

unread,
Sep 10, 2019, 8:36:45 AM9/10/19
to sage-release
On Debian stretch, I get a compilation error making sage 8.9.beta9. The problem is in the package "cypari", the relevant log is attached:

Found local metadata for cypari-2.1.1
Attempting to download package cypari2-2.1.1.tar.gz from mirrors
https://mirror.koddos.net/sagemath/spkg/upstream/cypari/cypari2-2.1.1.tar.gz
[......................................................................]
cypari-2.1.1
====================================================
Setting up build directory for cypari-2.1.1
Finished extraction
Applying patches from ../patches...
Applying ../patches/trashcan.patch
patching file cypari2/gen.pxd
patching file cypari2/gen.pyx
Hunk #1 succeeded at 141 (offset 6 lines).
patching file cypari2/pari_instance.pyx
****************************************************
Host system:
Linux ural 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u4 (2019-07-19) x86_64 GNU/Linux
****************************************************
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18+deb9u1' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
****************************************************
Package 'cypari' is currently not installed
No legacy uninstaller found for 'cypari'; nothing to do
Installing cypari-2.1.1
Installing package cypari2 using pip2
Ignoring indexes: https://pypi.org/simple
Created temporary directory: /tmp/pip-ephem-wheel-cache-EMVpJz
Created temporary directory: /tmp/pip-req-tracker-wfmzIV
Created requirements tracker '/tmp/pip-req-tracker-wfmzIV'
Created temporary directory: /tmp/pip-install-HkyCL2
Processing /srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src
  Created temporary directory: /tmp/pip-req-build-MoH_HZ
  Added file:///srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src to build tracker '/tmp/pip-req-tracker-wfmzIV'
  Running setup.py (path:/tmp/pip-req-build-MoH_HZ/setup.py) egg_info for package from file:///srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src
    Running command python setup.py egg_info
    running egg_info
    creating pip-egg-info/cypari2.egg-info
    writing requirements to pip-egg-info/cypari2.egg-info/requires.txt
    writing pip-egg-info/cypari2.egg-info/PKG-INFO
    writing top-level names to pip-egg-info/cypari2.egg-info/top_level.txt
    writing dependency_links to pip-egg-info/cypari2.egg-info/dependency_links.txt
    writing manifest file 'pip-egg-info/cypari2.egg-info/SOURCES.txt'
    error: [Errno 2] No such file or directory: '/usr/share/pari/pari.desc'
Cleaning up...
  Removing source in /tmp/pip-req-build-MoH_HZ
Removed file:///srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src from build tracker '/tmp/pip-req-tracker-wfmzIV'
Removed build tracker '/tmp/pip-req-tracker-wfmzIV'
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-req-build-MoH_HZ/
Exception information:

Traceback (most recent call last):
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/cli/base_command.py", line 143, in main
    status = self.run(options, args)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/commands/install.py", line 318, in run
    resolver.resolve(requirement_set)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 102, in resolve
    self._resolve_one(requirement_set, req)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 256, in _resolve_one
    abstract_dist = self._get_abstract_dist_for(req_to_install)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 209, in _get_abstract_dist_for
    self.require_hashes
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/operations/prepare.py", line 298, in prepare_linked_requirement
    abstract_dist.prep_for_dist(finder, self.build_isolation)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/operations/prepare.py", line 126, in prep_for_dist
    self.req.run_egg_info()
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/req/req_install.py", line 473, in run_egg_info
    command_desc='python setup.py egg_info')
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/utils/misc.py", line 705, in call_subprocess
    % (command_desc, proc.returncode, cwd))
InstallationError: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-req-build-MoH_HZ/
Error: installing with pip2 failed
********************************************************************************
Error installing cypari-2.1.1
********************************************************************************

real    0m1.345s
user    0m1.088s
sys    0m0.184s
************************************************************************
Error installing package cypari-2.1.1
************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /srv/public/shared/sage/logs/pkgs/cypari-2.1.1.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1 and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1' && '/srv/public/shared/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************
Found local metadata for cypari-2.1.1
Using cached file /srv/public/shared/sage/upstream/cypari2-2.1.1.tar.gz
cypari-2.1.1
====================================================
Setting up build directory for cypari-2.1.1
Finished extraction
Applying patches from ../patches...
Applying ../patches/trashcan.patch
patching file cypari2/gen.pxd
patching file cypari2/gen.pyx
Hunk #1 succeeded at 141 (offset 6 lines).
patching file cypari2/pari_instance.pyx
****************************************************
Host system:
Linux ural 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u4 (2019-07-19) x86_64 GNU/Linux
****************************************************
C compiler: gcc
C compiler version:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.3.0-18+deb9u1' --with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs --enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre --enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64 --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64 --with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --with-target-system-zlib --enable-objc-gc=auto --enable-multiarch --with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
****************************************************
Package 'cypari' is currently not installed
No legacy uninstaller found for 'cypari'; nothing to do
Installing cypari-2.1.1
Installing package cypari2 using pip2
Ignoring indexes: https://pypi.org/simple
Created temporary directory: /tmp/pip-ephem-wheel-cache-4L98l9
Created temporary directory: /tmp/pip-req-tracker-mosN7y
Created requirements tracker '/tmp/pip-req-tracker-mosN7y'
Created temporary directory: /tmp/pip-install-AHSkDU
Processing /srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src
  Created temporary directory: /tmp/pip-req-build-eMwGZT
  Added file:///srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src to build tracker '/tmp/pip-req-tracker-mosN7y'
  Running setup.py (path:/tmp/pip-req-build-eMwGZT/setup.py) egg_info for package from file:///srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src
    Running command python setup.py egg_info
    running egg_info
    creating pip-egg-info/cypari2.egg-info
    writing requirements to pip-egg-info/cypari2.egg-info/requires.txt
    writing pip-egg-info/cypari2.egg-info/PKG-INFO
    writing top-level names to pip-egg-info/cypari2.egg-info/top_level.txt
    writing dependency_links to pip-egg-info/cypari2.egg-info/dependency_links.txt
    writing manifest file 'pip-egg-info/cypari2.egg-info/SOURCES.txt'
    error: [Errno 2] No such file or directory: '/usr/share/pari/pari.desc'
Cleaning up...
  Removing source in /tmp/pip-req-build-eMwGZT
Removed file:///srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1/src from build tracker '/tmp/pip-req-tracker-mosN7y'
Removed build tracker '/tmp/pip-req-tracker-mosN7y'
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-req-build-eMwGZT/
Exception information:

Traceback (most recent call last):
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/cli/base_command.py", line 143, in main
    status = self.run(options, args)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/commands/install.py", line 318, in run
    resolver.resolve(requirement_set)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 102, in resolve
    self._resolve_one(requirement_set, req)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 256, in _resolve_one
    abstract_dist = self._get_abstract_dist_for(req_to_install)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/resolve.py", line 209, in _get_abstract_dist_for
    self.require_hashes
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/operations/prepare.py", line 298, in prepare_linked_requirement
    abstract_dist.prep_for_dist(finder, self.build_isolation)
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/operations/prepare.py", line 126, in prep_for_dist
    self.req.run_egg_info()
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/req/req_install.py", line 473, in run_egg_info
    command_desc='python setup.py egg_info')
  File "/srv/public/shared/sage/local/lib/python2.7/site-packages/pip/_internal/utils/misc.py", line 705, in call_subprocess
    % (command_desc, proc.returncode, cwd))
InstallationError: Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-req-build-eMwGZT/
Error: installing with pip2 failed
********************************************************************************
Error installing cypari-2.1.1
********************************************************************************

real    0m1.313s
user    0m1.084s
sys    0m0.176s
************************************************************************
Error installing package cypari-2.1.1
************************************************************************
Please email sage-devel (http://groups.google.com/group/sage-devel)
explaining the problem and including the log file
  /srv/public/shared/sage/logs/pkgs/cypari-2.1.1.log
Describe your computer, operating system, etc.
If you want to try to fix the problem yourself, *don't* just cd to
/srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1 and type 'make' or whatever is appropriate.
Instead, the following commands setup all environment variables
correctly and load a subshell for you to debug the error:
  (cd '/srv/public/shared/sage/local/var/tmp/sage/build/cypari-2.1.1' && '/srv/public/shared/sage/sage' --sh)
When you are done debugging, you can type "exit" to leave the subshell.
************************************************************************

Dima Pasechnik

unread,
Sep 10, 2019, 8:51:27 AM9/10/19
to sage-release
On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
<mariel...@berkeley.edu> wrote:
>
> On Debian stretch, I get a compilation error making sage 8.9.beta9. The problem is in the package "cypari", the relevant log is attached:

Are you upgrading? Building from scratch?

The interesting line is

error: [Errno 2] No such file or directory: '/usr/share/pari/pari.desc'

This appears to be related to
https://trac.sagemath.org/ticket/28242
Perhaps it ought to be improved.

It looks like you're trying to use a system installation of Pari/GP, rather
than build Sage's Pari. What parts of Pari (Pari-related packages?)
do you have on your Debian system?

Anyhow, Pari in Stretch is too old, but you should be able to use the
one from backports:

https://packages.debian.org/stretch-backports/libpari-dev

Thanks
Dima
> --
> You received this message because you are subscribed to the Google Groups "sage-release" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/78651b01-df14-4f2f-826c-d7de01833101%40googlegroups.com.

Mariel Supina

unread,
Sep 10, 2019, 9:16:00 AM9/10/19
to sage-release
Hi,


On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote:
On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
<mariel...@berkeley.edu> wrote:
>
> On Debian stretch, I get a compilation error making sage 8.9.beta9. The problem is in the package "cypari", the relevant log is attached:

Are you upgrading? Building from scratch?

I am building from scratch with python3.
 

The interesting line is

error: [Errno 2] No such file or directory: '/usr/share/pari/pari.desc'

This appears to be related to
https://trac.sagemath.org/ticket/28242
Perhaps it ought to be improved.

The compilation used to work fine on the machines, so that could be it?
 

It looks like you're trying to use a system installation of Pari/GP, rather
than build Sage's Pari. What parts of Pari (Pari-related packages?)
do you have on your Debian system?

The computer on which I try to compile is maintained by my department's IT, so I am not completely aware of all the packages that might or might not be installed.

How can I figure out which pari (and which packages) are installed?
 

Anyhow, Pari in Stretch is too old, but you should be able to use the
one from backports:

https://packages.debian.org/stretch-backports/libpari-dev

I am afraid that I do not have the rights to install libpari systemwide. Hmm.
 
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-r...@googlegroups.com.

Dima Pasechnik

unread,
Sep 10, 2019, 9:32:12 AM9/10/19
to sage-release
On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina
<mariel...@berkeley.edu> wrote:
>
> Hi,
>
> On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote:
>>
>> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
>> <mariel...@berkeley.edu> wrote:
>> >
>> > On Debian stretch, I get a compilation error making sage 8.9.beta9. The problem is in the package "cypari", the relevant log is attached:
>>
>> Are you upgrading? Building from scratch?
>
>
> I am building from scratch with python3.
>

could you post the output of ./configure --with-python=3 ?
(I guess that's what you ran before starting to build)

In case you don't know how, run
./configure --with-python=3 >/tmp/foo

and post the resulting /tmp/foo file

Thanks.

I suspect you have a broken in a interesting way system-wide
installation of pari/gp...

---------------

you can build and use Sage's pari e.g. by
doing

make pari

and then doing

make
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/71e7386e-a8bf-4a26-b446-706c65f0a91a%40googlegroups.com.

Dima Pasechnik

unread,
Sep 10, 2019, 9:53:06 AM9/10/19
to sage-release
On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina
<mariel...@berkeley.edu> wrote:
>
> Hi,
>
> On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote:
>>
>> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
>> <mariel...@berkeley.edu> wrote:
>> >
>> > On Debian stretch, I get a compilation error making sage 8.9.beta9. The problem is in the package "cypari", the relevant log is attached:
>>
>> Are you upgrading? Building from scratch?
>
>
> I am building from scratch with python3.
>
>>
>>
>> The interesting line is
>>
>> error: [Errno 2] No such file or directory: '/usr/share/pari/pari.desc'
>>
>> This appears to be related to
>> https://trac.sagemath.org/ticket/28242
>> Perhaps it ought to be improved.
>
>
> The compilation used to work fine on the machines, so that could be it?
>
>>
>>
>> It looks like you're trying to use a system installation of Pari/GP, rather
>> than build Sage's Pari. What parts of Pari (Pari-related packages?)
>> do you have on your Debian system?
>
>
> The computer on which I try to compile is maintained by my department's IT, so I am not completely aware of all the packages that might or might not be installed.
>
> How can I figure out which pari (and which packages) are installed?

what is the output of

gp --version

and of

echo 'default(datadir)' | gp -qf

And what is the output of

which gp

Thanks.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/71e7386e-a8bf-4a26-b446-706c65f0a91a%40googlegroups.com.

Mariel Supina

unread,
Sep 10, 2019, 10:07:24 AM9/10/19
to sage-release
I have attached the output of ./configure --with-python=3.

On Tuesday, September 10, 2019 at 3:53:06 PM UTC+2, Dima Pasechnik wrote:
On Tue, Sep 10, 2019 at 2:16 PM Mariel Supina
<mariel...@berkeley.edu> wrote:
>
> Hi,
>
> On Tuesday, September 10, 2019 at 2:51:27 PM UTC+2, Dima Pasechnik wrote:
>>
>> On Tue, Sep 10, 2019 at 1:36 PM Mariel Supina
>> <mariel...@berkeley.edu> wrote:
>> >
>> > On Debian stretch, I get a compilation error making sage 8.9.beta9. The problem is in the package "cypari", the relevant log is attached:
>>
>> Are you upgrading? Building from scratch?
>
>
> I am building from scratch with python3.
>
>>
>>
>> The interesting line is
>>
>> error: [Errno 2] No such file or directory: '/usr/share/pari/pari.desc'
>>
>> This appears to be related to
>> https://trac.sagemath.org/ticket/28242
>> Perhaps it ought to be improved.
>
>
> The compilation used to work fine on the machines, so that could be it?
>
>>
>>
>> It looks like you're trying to use a system installation of Pari/GP, rather
>> than build Sage's Pari. What parts of Pari (Pari-related packages?)
>> do you have on your Debian system?
>
>
> The computer on which I try to compile is maintained by my department's IT, so I am not completely aware of all the packages that might or might not be installed.
>
> How can I figure out which pari (and which packages) are installed?

what is the output of

  gp --version

                  GP/PARI CALCULATOR Version 2.9.1 (released)
          amd64 running linux (x86-64/GMP-6.1.1 kernel) 64-bit version
       compiled: Dec  1 2016, gcc version 6.2.1 20161124 (Debian 6.2.1-5)
                           threading engine: pthread
                (readline v7.0 disabled, extended help enabled)

 

and of

  echo 'default(datadir)' | gp -qf

"/usr/share/pari"
 

And what is the output of

  which gp

/usr/bin/gp
 
foo

Dima Pasechnik

unread,
Sep 10, 2019, 11:50:53 AM9/10/19
to sage-release
Thanks. OK, I see that you're supposed to be building Pari, anyway,
amd then the rest should have worked. Strange.

To make sure bulding Pari worked, could you do the following:
In the directory you're building Sage, run

./sage --gp --version

and post the output. Also, please post the output of

echo 'default(datadir)' | ./sage --gp -qf

Also, at the same directory, start Sage's Python by typing

./sage --python

and at the Python's prompt, type the following 2 commands:

from distutils.spawn import find_executable
find_executable("gp")

and post the output.

In the same directory, run

ls -l local/share/pari/pari.desc

and post the output.


-------------------------------------

finally, please post the output of

ls -l /usr/share/pari/pari.desc

Thanks.

On Tue, Sep 10, 2019 at 3:07 PM Mariel Supina
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/eb8f707d-4dc1-489b-9b32-a7d2dfc7011f%40googlegroups.com.

Mariel Supina

unread,
Sep 10, 2019, 12:30:41 PM9/10/19
to sage-release


On Tuesday, September 10, 2019 at 5:50:53 PM UTC+2, Dima Pasechnik wrote:
Thanks. OK, I see that you're supposed to be building Pari, anyway,
amd then the rest should have worked. Strange.

To make sure bulding Pari worked, could you do the following:
In the directory you're building Sage,  run

  ./sage --gp --version

and post the output.

                   GP/PARI CALCULATOR Version 2.11.1 (released)
           amd64 running linux (x86-64/GMP-6.1.2 kernel) 64-bit version
    compiled: Sep 10 2019, gcc version 6.3.0 20170516 (Debian 6.3.0-18+deb9u1)
                             threading engine: single
                (readline not compiled in, extended help enabled)

 
Also, please post the output of

  echo 'default(datadir)' | ./sage --gp -qf

 "/srv/public/shared/sage/local/share/pari"


Also, at the same directory, start Sage's Python by typing

  ./sage --python

and at the Python's prompt, type the following 2 commands:

  from distutils.spawn import find_executable
  find_executable("gp")

and post the output.

'/srv/public/shared/sage/local/bin/gp'
 

In the same directory, run

  ls -l local/share/pari/pari.desc

and post the output.



-rw-r--r-- 1 mjsupina ag_discgeom 1425197 Sep 10 14:55 local/share/pari/pari.desc
 
-------------------------------------

finally, please post the output of

  ls -l /usr/share/pari/pari.desc


ls: Zugriff auf '/usr/share/pari/pari.desc' nicht möglich: Datei oder Verzeichnis nicht gefunden

(Translation to English:
ls: Unable to access '/usr/share/pari/pari.desc': file or directory not found)
 

Dima Pasechnik

unread,
Sep 10, 2019, 1:16:23 PM9/10/19
to sage-release, Vincent Delecroix, jeroen.k...@gmail.com, sage-devel
On Tue, Sep 10, 2019 at 5:30 PM Mariel Supina
<mariel...@berkeley.edu> wrote:
>
> On Tuesday, September 10, 2019 at 5:50:53 PM UTC+2, Dima Pasechnik wrote:
>>
>> Thanks. OK, I see that you're supposed to be building Pari, anyway,
>> amd then the rest should have worked. Strange.
>>
>> To make sure bulding Pari worked, could you do the following:
>> In the directory you're building Sage,

as you are building in /srv/public/shared/sage/ everything appears to
be in order.

Something is telling cypari to ignore the Pari/GP already installed in
/srv/public/shared/sage/local/
and to use the system Pari/GP, which is not only incompatible, but broken
(as /usr/share/pari/pari.desc is a part of the package, but it's missing) too.
On the other hand I checked how cypari discovers the Pari/GP installation, and
it appears it should work as expected.

I cc the main authors of cypari package.

Are you setting any environment variables by hand? No pre-set SAGE_ROOT?
Or perhaps something
that you get by default, and this breaks things?

Could you post the output of

set
Vielen dank, ich weiss es auch ohne deine ueberzetsung ;-)

Could it be that German locale is breaking something? I don't know...

Dima
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/c8c72666-0ab0-4e70-9271-6e2083d37dec%40googlegroups.com.

Mariel Supina

unread,
Sep 11, 2019, 5:49:10 AM9/11/19
to sage-release
Attached is the output of

set
foo1

Dima Pasechnik

unread,
Sep 11, 2019, 6:18:37 AM9/11/19
to sage-release
OK, thanks, let's do more debugging of cypari:

cd /srv/public/shared/sage/upstream
tar xf cypari2-2.1.1.tar.gz
cd cypari2-2.1.1/

now, start Sage's Python:

../../sage -python

and at its prompt, do

import autogen
autogen.pari_share()

Post the result of the last 3 commands.

Similarly, staying at this directory, start system's Python

python

and at its prompt, do

import autogen
autogen.pari_share()

Post the result of the last 3 commands.

---------------
I suspect that cypari invokes system's Python rather than Sage's
Python at this point.

To check this, let us try putting Sage's Python 1st in the PATH and
re-run the installation of Cypari. Thus, try the following:

cd /srv/public/shared/sage/
PATH=/srv/public/shared/sage/bin:$PATH ./sage -i cypari

and tell us whether this worked or not...

Thanks.
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/744517bd-2b7c-4132-9f0c-fbefa2d0b738%40googlegroups.com.

Mariel Supina

unread,
Sep 11, 2019, 11:08:59 AM9/11/19
to sage-release


On Wednesday, September 11, 2019 at 12:18:37 PM UTC+2, Dima Pasechnik wrote:
OK, thanks, let's do more debugging of cypari:

   cd /srv/public/shared/sage/upstream
   tar xf  cypari2-2.1.1.tar.gz
   cd cypari2-2.1.1/

now, start Sage's Python:

   ../../sage -python

and at its prompt, do

   import autogen
   autogen.pari_share()  

Post the result of the last 3 commands.

'/srv/public/shared/sage/local/share/pari'
 

Similarly, staying at this directory, start system's Python

    python

and at its prompt, do

   import autogen
   autogen.pari_share()

Post the result of the last 3 commands.

'/usr/share/pari'
 

---------------
I suspect that cypari invokes system's Python rather than Sage's
Python at this point.

To check this, let us try putting Sage's Python 1st in the PATH and
re-run the installation of Cypari. Thus, try the following:

    cd /srv/public/shared/sage/
    PATH=/srv/public/shared/sage/bin:$PATH ./sage -i cypari

and tell us whether this worked or not...

This worked!
 

Dima Pasechnik

unread,
Sep 11, 2019, 11:41:47 AM9/11/19
to sage-release
On Wed, Sep 11, 2019 at 4:09 PM Mariel Supina
<mariel...@berkeley.edu> wrote:
>
>
>
> On Wednesday, September 11, 2019 at 12:18:37 PM UTC+2, Dima Pasechnik wrote:
>>
>> OK, thanks, let's do more debugging of cypari:
>>
>> cd /srv/public/shared/sage/upstream
>> tar xf cypari2-2.1.1.tar.gz
>> cd cypari2-2.1.1/
>>
>> now, start Sage's Python:
>>
>> ../../sage -python
>>
>> and at its prompt, do
>>
>> import autogen
>> autogen.pari_share()
>>
>>
>> Post the result of the last 3 commands.
>
>
> '/srv/public/shared/sage/local/share/pari'
>
>>
>>
>> Similarly, staying at this directory, start system's Python
>>
>> python
>>
>> and at its prompt, do
>>
>> import autogen
>> autogen.pari_share()
>>
>> Post the result of the last 3 commands.
>
>
> '/usr/share/pari'
>
>>
>>
ok, this is all as expected.

>> ---------------
>> I suspect that cypari invokes system's Python rather than Sage's
>> Python at this point.
>>
>> To check this, let us try putting Sage's Python 1st in the PATH and
>> re-run the installation of Cypari. Thus, try the following:
>>
>> cd /srv/public/shared/sage/
>> PATH=/srv/public/shared/sage/bin:$PATH ./sage -i cypari
>>
>> and tell us whether this worked or not...
>
>
> This worked!
OK, good. At least from this point on you should be able to continue
building, just by
typing

make

The remaining question is whether the problem is reproducible.
That is, what happens if you try to re-install cypari wthout the PATH
hack, i.e. just by

./sage -f cypari

Does this work? If yes, then the problem (which in this case would be
that the installation of Pari/GP was not ready at the point building
of cypai kicked in) is gone, more or less.

If it doesn't then it's a problem I cannot really pin down to anything
in particular, and it appears very limited in scope, i.e. I can't
reproduce it on other machines...
Anyway,

PATH=/srv/public/shared/sage/bin:$PATH ./sage -i cypari

should allow you to proceed.

HTH
Dima
> To unsubscribe from this group and stop receiving emails from it, send an email to sage-release...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/a9a0d305-db4c-4c51-a94b-78b16e8d962d%40googlegroups.com.

John H Palmieri

unread,
Sep 12, 2019, 3:16:16 PM9/12/19
to sage-release


On Friday, September 6, 2019 at 3:13:07 AM UTC-7, E. Madison Bray wrote:

I see this failure if I have a PATH entry with a space in it, as in "/Users/palmieri/path\ with\ space/". GAP should be able to handle this, I think.

Mariel Supina

unread,
Sep 16, 2019, 6:02:30 AM9/16/19
to sage-release
Hello Dima,

Sorry for taking awhile to respond -- I have been away from my work computer. Re-installing cypari as you suggested did work. The problem appears to be fixed. Thank you very much for all of your help!

Best,
Mariel
Reply all
Reply to author
Forward
0 new messages