[sage-release] Re: reporting on Sage.9.0.beta4

2019-11-06 Thread Jean-Philippe Labbé
The base_QQ.py errors are likely to be linked to

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

It should be easily fixed, I created ticket: 

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

for that.

Le mardi 5 novembre 2019 21:02:44 UTC+1, Sébastien Labbé a écrit :
>
> I am reporting on the following release from 3 days ago (I am creating a 
> new thread since it has not been created yet).
>
> ┌┐
> │ SageMath version 9.0.beta4, Release Date: 2019-11-02   │
> │ Using Python 2.7.15. Type "help()" for help.   │
> └┘
>
> Running tests with optional + external packages, I get:
>
> Using 
> --optional=awali,cbc,ccache,cryptominisat,dot2tex,e_antic,external,glucose,memlimit,normaliz,notedown,openssl,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage
> --
> sage -t --long src/sage/databases/findstat.py  # 52 doctests failed
> sage -t --long src/sage/symbolic/integration/external.py  # 1 doctest 
> failed
> sage -t --long src/sage/geometry/polyhedron/base_QQ.py  # 3 doctests failed
> --
> External software detected for doctesting: 
> ffmpeg,graphviz,imagemagick,internet,latex,pandoc
>
> Rerunning failed tests, I get:
>
> --
> sage -t --long src/sage/geometry/polyhedron/base_QQ.py  # 3 doctests failed
> sage -t --long src/sage/databases/findstat.py  # 62 doctests failed
> --
> External software detected for doctesting: internet
>
> The transient error is:
>
> sage -t --long src/sage/symbolic/integration/external.py
> **
> File "src/sage/symbolic/integration/external.py", line 247, in 
> sage.symbolic.integration.external.parse_moutput_from_json
> Failed example:
> sorted(L) # optional 
> internet
> Expected:
> [u'-Cos[x]', u'{{x == Pi C[1], Element[C[1], Integers]}}']
> Got:
> [{u'val': u'-Cos[x]'}, {u'val': u'{{x == Pi C[1], Element[C[1], 
> Integers]}}'}]
> **
> 1 item had failures:
>1 of  10 in sage.symbolic.integration.external.parse_moutput_from_json
> 8 fricas tests not run
> 0 tests not run because we ran out of time
> [36 tests, 1 failure, 21.01 s]
>
> It seems the following 3 tests are missing the latte optional tag:
>
> sage -t --long src/sage/geometry/polyhedron/base_QQ.py
> **
> File "src/sage/geometry/polyhedron/base_QQ.py", line 483, in 
> sage.geometry.polyhedron.base_QQ.Polyhedron_QQ.?
> Failed example:
> ts.integral_points_count()# optional - pynormaliz
> Exception raised:
> Traceback (most recent call last):
>   File 
> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>  
> line 681, in _run
> self.compile_and_execute(example, compiler, test.globs)
>   File 
> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>  
> line 1123, in compile_and_execute
> exec(compiled, globs)
>   File " sage.geometry.polyhedron.base_QQ.Polyhedron_QQ.?[13]>", line 1, in 
> ts.integral_points_count()# optional - pynormaliz
>   File 
> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/base_QQ.py",
>  
> line 218, in integral_points_count
> **kwds)
>   File 
> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/interfaces/latte.py",
>  
> line 116, in count
> Latte().require()
>   File 
> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/features/__init__.py",
>  
> line 158, in require
> raise FeatureNotPresentError(self, presence.reason, 
> presence.resolution)
> FeatureNotPresentError: LattE is not available.
> Executable 'count' not found on PATH.
> To install count you can try to run 'sage -i latte_int'.
> Further installation instructions might be available at 
> https://www.math.ucdavis.edu/~latte/software.php.
> **
> File "src/sage/geometry/polyhedron/base_QQ.py", line 515, in 
> sage.geometry.polyhedron.base_QQ.Polyhedron_QQ.?
> Failed example:
> 
> simplex.ehrhart_polynomial()  
>   
> # optional - pynormaliz
> Exception raised:
> Traceback (most recent call last):
>   File 
> "/home/slabbe/GitBox/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
>  
> line 681, in _run
> self.compile_and_execute(exam

[sage-release] Re: Sage 8.9.beta8 released

2019-08-27 Thread Jean-Philippe Labbé
Guten Tag,

Le lundi 26 août 2019 00:37:50 UTC+2, Volker Braun a écrit :

> I'm inclined to name the next version 9.0. In particular, we now have 
> Python 3 support that, while not perfect, is at least usable so we should 
> mark that with a new major version. Also point-9 is a natural place to 
> switch. If you want to voice your opinion on that issue: now is the time ;-)
>
 
+1

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/c0294fc9-581e-41ef-8031-ac28d6a830eb%40googlegroups.com.


[sage-release] Re: Sage 8.3 release notes

2018-10-08 Thread Jean-Philippe Labbé
This is great material to use for an introductory talk on Sage.

Thank you very much!

Le jeudi 6 septembre 2018 16:08:55 UTC+2, Jeroen Demeyer a écrit :
>
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 7.6.beta2 released

2017-02-06 Thread Jean-Philippe Labbé
Everything looks normal in the "install.log" file. I made a circular search 
with the keyword "error" in that file and did not find anything I could 
report. My install.log has more than 4M lines, any pointer on which log I 
should look at? Nothing to report in the start.log.

There is nothing to report excepted this "python" error, for which I copied 
the whole log file.

Sage seems to be working without trouble though, so it seems not to be a 
big deal(!?).

I will most likely recompile soon, with the Sagedays84 coming up. If the 
error persists, I will make a follow-up.

Thanks a lot for your time,

Le samedi 4 février 2017 15:12:23 UTC+1, Jeroen Demeyer a écrit :
>
> On 2017-02-04 10:34, Jean-Philippe Labbé wrote: 
> > Before that it was building the doc, and before that installing the 
> > jupyter client. 
>
> Logs please... ignore the "python" thing, it's most likely not the 
> reason for the failure. 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-release] Re: Sage 7.6.beta2 released

2017-02-04 Thread Jean-Philippe Labbé
Hi,

I get:


Error building Sage.

The following package(s) may have failed to build (not necessarily 
during this run of 'make all'): 

* package: python 
log file: /sage/logs/pkgs/python.log 
build directory: /sage/local/var/tmp/sage/build/python
=

Before that it was building the doc, and before that installing the jupyter 
client.

I did not run the all the test yet, but sage seems to run without problems 
so far.

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 7.6.beta2 released

2017-02-03 Thread Jean-Philippe Labbé
Hi,

Just compiled the latest version. First time that I get this error 
compiling Sage:

The following package(s) may have failed to build (not necessarily during 
this run of 'make all'):

* package: python
 log file: sage/logs/pkgs/python.log 

Here is the content of the log:

Attempting to download package python 
>>> Checking online list of optional packages. 
>>> Checking online list of experimental packages. 
>>> Checking online list of huge packages. 
Error: could not find a package matching python 
Try 'sage --package list' to see the available packages 
Did you mean: cython, ipython, python2, python3, pathpy? 
Attempting to download package python 
>>> Checking online list of optional packages. 
>>> Checking online list of experimental packages. 
>>> Checking online list of huge packages. 
Error: could not find a package matching python 
Try 'sage --package list' to see the available packages 
Did you mean: cython, ipython, python2, python3, pathpy?

Would a make dist-clean do the thing?

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 7.4.rc2 released

2016-10-17 Thread Jean-Philippe Labbé
Oh!

Okay, so according 
to http://doc.sagemath.org/html/en/installation/source.html#section-macprereqs, 
we again need to type:

xcode-select --install

in the terminal after the installation of XCode.

Compiling again.

Le lundi 17 octobre 2016 21:18:36 UTC+2, Jean-Philippe Labbé a écrit :
>
> Hi,
>
> I got an error compiling gcc-4.9.3.p1 on the branch "develop" on a MacBook 
> Pro 2,4GHz Intel Core 2 Duo with a fresh install of OS 10.12.
>
> For this first run, I forgot to type MAKE="make -j2" so it compiled using 
> only 1 core. I don't know it this can influence.
>
> I got the error:
>
> [gcc-4.9.3.p1] The directory that should contain system headers does not 
> exist: 
> [gcc-4.9.3.p1] /usr/include 
> [gcc-4.9.3.p1] make[6]: *** [stmp-fixinc] Error 1 
> [gcc-4.9.3.p1] make[5]: *** [all-stage1-gcc] Error 2 
> [gcc-4.9.3.p1] make[4]: *** [stage1-bubble] Error 2 
> [gcc-4.9.3.p1] make[3]: *** [all] Error 2 
> [gcc-4.9.3.p1] 
> [gcc-4.9.3.p1] real 15m13.328s 
> [gcc-4.9.3.p1] user 8m31.598s 
> [gcc-4.9.3.p1] sys 2m44.787s 
> [gcc-4.9.3.p1] 
>  
> [gcc-4.9.3.p1] Error installing package gcc-4.9.3.p1 
> [gcc-4.9.3.p1] 
> 
>

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 7.4.rc2 released

2016-10-17 Thread Jean-Philippe Labbé
Hi,

I got an error compiling gcc-4.9.3.p1 on the branch "develop" on a MacBook 
Pro 2,4GHz Intel Core 2 Duo with a fresh install of OS 10.12.

For this first run, I forgot to type MAKE="make -j2" so it compiled using 
only 1 core. I don't know it this can influence.

I got the error:

[gcc-4.9.3.p1] The directory that should contain system headers does not 
exist: 
[gcc-4.9.3.p1] /usr/include 
[gcc-4.9.3.p1] make[6]: *** [stmp-fixinc] Error 1 
[gcc-4.9.3.p1] make[5]: *** [all-stage1-gcc] Error 2 
[gcc-4.9.3.p1] make[4]: *** [stage1-bubble] Error 2 
[gcc-4.9.3.p1] make[3]: *** [all] Error 2 
[gcc-4.9.3.p1] 
[gcc-4.9.3.p1] real 15m13.328s 
[gcc-4.9.3.p1] user 8m31.598s 
[gcc-4.9.3.p1] sys 2m44.787s 
[gcc-4.9.3.p1] 
 
[gcc-4.9.3.p1] Error installing package gcc-4.9.3.p1 
[gcc-4.9.3.p1] 


-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 7.0 released

2016-03-07 Thread Jean-Philippe Labbé
A colleague has a error in the compilation of Sage 7.0:

"Error installing package mpc-1.0.3.p0" here is a part of the log file:



dyld: lazy symbol binding failed: Symbol not found: _openat

  Referenced from: /Applications/Sage/sage-7.0/local/bin/patch

  Expected in: /usr/lib/libSystem.B.dylib


dyld: Symbol not found: _openat

  Referenced from: /Applications/Sage/sage-7.0/local/bin/patch

  Expected in: /usr/lib/libSystem.B.dylib


./spkg-install: line 13: 87768 Trace/BPT trap: 5   patch -p1 < "$patch"

Error applying '../patches/mpc_mul_faster.patch'

His computer is a MacBook Air 1.8Ghz Intel Core i5, 8GB RAM OS 10.9.5

-- 
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+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.