Re: [sage-release] Sage 10.2.beta6 released

[François Bissey]

Yes, I think you are right. I am probably guilty for the fact it is not 
included in this release. I should have hurried up.


On 9/10/23 17:02, Matthias Köppe wrote:
The failure involving setuptools_scm is likely fixed 
by https://github.com/sagemath/sage/pull/36400, which is waiting for review.


On Sunday, October 8, 2023 at 7:47:02 PM UTC-7 furutaka@gmail.com wrote:

A build "Using conda to provide system packages for the Sage
distribution

"
 failed in building setuptools-68.2.2 as before...


2023年10月9日(月) 4:54 Volker Braun :

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




This release drops support for GCC < 8.4 (Debian 10 "Buster")

2f1a76dc24a (tag: 10.2.beta6, github/develop) Updated SageMath
version to 10.2.beta6
46997739f9b gh-36388: fix typographic typos
970fd9f1864 gh-36383: Update flint to 2.9.0, arb to 2.23.0
6d838ba174a gh-36382: `configure --enable-system-site-packages`:
First check all non-site packages
5da52a71923 gh-36381: Python package upgrades cherry-picked from
notebook 7 upgrade PR
726c438330b gh-36378: Add README.md Table of Contents and Links
f1ac6c1c573 gh-36377: clean one test file
d2fa61b433c gh-36376: src/sage/databases/sql_db.py: replace
tmp_dir()
aadad8bf506 gh-36375: src/sage/interfaces/gap_workspace.py:
replace tmp_dir()
bc8d82abede gh-36374: refresh the cython file real_roots (pep8,
range, etc)
16c78cab8ca gh-36373: Enable conda ci for all PRs and remove
experimental label
17f07d5f076 gh-36371: fix remaining W605 warnings in pxi files
d8e55296e17 gh-36369: partial cython-lint cleanup in padics/
0405d07dde8 gh-36367: Simplify experimental all-conda
installation instructions via `pkgs/sage-conf_conda`
1af197b2066 gh-36365: Libgap cubegroup
16aaae1e34d gh-36364: Do not run sage-env more than once, for real.
dfcd25fab60 gh-36363: Fix dependencies of `packaging`, update
`flit_core` to 3.9.0, `pip` to 23.2.1
56533be695f gh-36362: a few more links to errors in the doc
e33c041bd73 gh-36359: a few details in combinat (designs)
afd8d0e8194 gh-36358: CI: Fix the multi-stage build in
ci-linux.yml, fix conda/centos/archlinux system packages
b30cc4b7751 gh-36357: CI: Remove ci-wsl, ci-cygwin-standard
8550060f96a gh-36355: fixing pep8 E275 in rings/ and combinat/
0421fd1745f gh-36352: fix E228 and E225 in coding, crypto,
dynamics, geometry, manifolds, modular
a4017212c20 gh-36348: .github/workflows/build.yml,
doc-build.yml: Fix get_ci_fixes
e1a0794ba97 gh-36344: src/sage/misc/cython.py: replace tmp_dir()
0c63ee37742 gh-36343: src/sage/repl/interpreter.py: replace
tmp_dir()
14c055e0818 gh-36324: src/sage/tests/cmdline.py: replace tmp_dir()
cb0cea09278 gh-36314: add q-Fuss-Catalan numbers
fe963ca5a4d gh-36310: Mod 2 (co)homology as a module over the
Steenrod algebra
119429042c2 gh-36285: add Rémy Oudompheng's implementation of
the BMSS algorithm
7591b1efafc gh-36277: `sage.graphs`: some care with return ...
else statements in `graph.py`, `digraph.py` and `bipartite_graph.py`
71428337f16 gh-36273: `sage.graphs`,
`sage.combinat.{designs,posets}`, `sage.sandpiles`: Update # needs
7c62ef8112b gh-36272: `sage.sets`: Update `# needs`
8ebaeff5496 gh-36261: `sage.rings.padics`: Import fixes
(modularization)
ab6f53b50f2 gh-36161: Upgrade pplpy to 0.8.9
868fefa1289 gh-36123: Upgrade numpy to 1.26.0, setuptools to 68.2.2
fdf30fbb1bc gh-35786: onetbb: Upgrade to 2021.9.0 + GCC13 patch
1738235b962 gh-35546: compute traces of elliptic-curve endomorphisms
bd434dae42a gh-35373: Fix workflow "Build documentation (PDF)"
1ed5b510362 gh-35285: System package information   tox ini   gh
actions for alpine linux
d687f2e7a73 gh-35062: Enable merge_group trigger for merge queues
d5d7c461a11 gh-35008: Implement Covering Arrays
1cf0c13e527 (tag: 10.2.beta5) Updated SageMath version to 10.2.beta5

-- 


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

Re: [sage-release] Sage 10.0 released

[François Bissey]

sage-on-gentoo 10.0 is out sans bliss and meataxe options for now.

On Monday, May 22, 2023 at 8:47:33 AM UTC+12 François Bissey wrote:

>
>
> On 22/05/23 06:14, Matthias Köppe wrote:
> > On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote:
> > 
> > I am preparing the sage-on-gentoo release. I just noticed the file
> > sage/graphs/bliss.pyx
> > is missing from the pypi tarball of sagemath-standard.
> > 
> > 
> > I have a feeling I will find it in the sage-bliss package. However I
> > did
> > not notice that the splitting of sage-bliss was live in the 10.0rc*. Is
> > this a mistake?
> > 
> > 
> > Sorry about this. Two possible courses of action:
> > 1) Prepare a sagemath-standard-10.0.post1 distribution that ships 
> > bliss.pyx (other probably missing files such as mcqd.pyx)
> > 2) Prepare the sagemath-bliss-10.0 etc. packages 
> > (https://github.com/sagemath/sage/issues/34346)
> > 
> > I will work on 2) unless there are good reasons for 1)
> > 
>
> Ok on work on (2), it is just annoying for it to happen post release 
> rather being able to prepare for it prior to it. And you are right it 
> probably affects all the optional stuff, bliss is the one I caught 
> because I include patch for the newer bliss. And patch complained that 
> the file to patch doesn't exist.
>
> François
>

-- 
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/23fcb70f-a4f9-4301-ad8f-0e37249b3300n%40googlegroups.com.

Re: [sage-release] Sage 10.0 released

[François Bissey]

On 22/05/23 06:14, Matthias Köppe wrote:

On Sunday, May 21, 2023 at 3:55:18 AM UTC-7 François Bissey wrote:

I am preparing the sage-on-gentoo release. I just noticed the file
sage/graphs/bliss.pyx
is missing from the pypi tarball of sagemath-standard.


I have a feeling I will find it in the sage-bliss package. However I
did
not notice that the splitting of sage-bliss was live in the 10.0rc*. Is
this a mistake?


Sorry about this. Two possible courses of action:
1) Prepare a sagemath-standard-10.0.post1 distribution that ships 
bliss.pyx (other probably missing files such as mcqd.pyx)
2) Prepare the sagemath-bliss-10.0 etc. packages 
(https://github.com/sagemath/sage/issues/34346)


I will work on 2) unless there are good reasons for 1)



Ok on work on (2), it is just annoying for it to happen post release 
rather being able to prepare for it prior to it. And you are right it 
probably affects all the optional stuff, bliss is the one I caught 
because I include patch for the newer bliss. And patch complained that 
the file to patch doesn't exist.


François

--
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/b5e2d8c4-c6e9-89de-71cc-cc92dd984abe%40gmail.com.

Re: [sage-release] Sage 10.0 released

[François Bissey]

I am preparing the sage-on-gentoo release. I just noticed the file
sage/graphs/bliss.pyx
is missing from the pypi tarball of sagemath-standard.
I have a feeling I will find it in the sage-bliss package. However I did 
not notice that the splitting of sage-bliss was live in the 10.0rc*. Is 
this a mistake?


Cheers,
François

On 21/05/23 11:10, Volker Braun wrote:
The "master" git branch has been updated to Sage-10.0. 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


As you are undoubtedly aware, this version is the first since the 
migration of the development process to github. A big thanks to everyone 
who was involved, we couldn't have done it without you 


6ba0eafc2ca (tag: 10.0, github/develop) Updated SageMath version to 10.0
8476c469588 gh-35460: Update developer guide for workflows on github
4ed2157cd2a gh-35638: build/pkgs/python3/spkg-configure.m4: Add depcheck 
for zlib

9de8c5b1b6c gh-35637: remark that WSL needs a lot of RAM
f2f5863c08a (tag: 10.0.rc3) Updated SageMath version to 10.0.rc3

--
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/48dea2b5-d56c-4191-b1e8-518b03f6aac2n%40googlegroups.com .


--
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/25a10aa1-4ab5-8a18-8007-a72e402d941a%40gmail.com.

Re: [sage-release] Sage 9.8 released

[François Bissey]

Thanks!

On 12/02/23 11:51, Matthias Köppe wrote:

The sdists are now up on PyPI.

On Saturday, February 11, 2023 at 2:43:59 PM UTC-8 Matthias Köppe wrote:

I've created a new PyPI deployment token and made it available to
our repos.
I've started
https://github.com/sagemath/sage/actions/workflows/dist.yml
<https://github.com/sagemath/sage/actions/workflows/dist.yml> manually.


On Saturday, February 11, 2023 at 2:33:12 PM UTC-8 Dima Pasechnik wrote:

On Sat, Feb 11, 2023 at 10:31 PM Matthias Köppe
 wrote:

Neither the "dist.yml" nor the "ci-..." workflows have run
on the push to the 9.8 tag on sagemath/sage.
I'll investigate.


I've also created the GitHub release 9.8 manually. (The tag was
created, the release was not)


On Saturday, February 11, 2023 at 1:54:43 PM UTC-8 François
Bissey wrote:

When will we have packages up on pypi? I now rely on
these for stable
release in sage-on-gentoo.

François

On 12/02/23 02:47, Volker Braun wrote:
 > The "master" git branch has been updated to Sage-9.8.
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
<http://www.sagemath.org/download-latest.html>
 >
 > And as you are undoubtedly aware, the git repository
is now hosted
 > at https://github.com/sagemath/sage
<https://github.com/sagemath/sage>, so update your git
remote.
 >
 > To commemorate the move (and because we are getting
really close to
 > .10), I'm proposing to target Sage version 10 as the
next release.
 >
 > The changes over 9.8.rc0 are mainly housekeeping for
the new repository
 > location.
 >
 > I'll try to finish up merging remaining positively
reviewed trac issues,
 > and then move on to github pull requests.
 >
 > c000c953eb6 (HEAD -> develop, github/master,
github/develop, tag: 9.8)
 > Updated SageMath version to 9.8
 > 104dde9eaa8 Merge pull request #35022 from
tobiasdiez/pr-template-title
 > 17d8a73296f Merge pull request #35018 from
x4/public/35017
 > 6a4667bb5c5 Merge pull request #34983 from
tobiasdiez/add-issue-templates
 > 66b319baffb Merge pull request #35011 from
dimpase/develop
 > 872b32b0c20 Merge pull request #34987 from
mezzarobba/missing_long_time
 > d57804e6dec Merge pull request #34964 from
x4/public/linter-20230206
 > 698001b0e6a remove prohibition, promise details
 > 0c5f7baf6c2 remove trac references, promise details soon
 > 200557e00c3 (tag: 9.8.rc1) Updated SageMath version
to 9.8.rc1
 >
 > --
 > 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
 > <mailto:sage-release...@googlegroups.com>.
 > To view this discussion on the web visit
 >

https://groups.google.com/d/msgid/sage-release/c9f7a210-5377-4cf1-a176-d693fce12c86n%40googlegroups.com 
<https://groups.google.com/d/msgid/sage-release/c9f7a210-5377-4cf1-a176-d693fce12c86n%40googlegroups.com>
 
<https://groups.google.com/d/msgid/sage-release/c9f7a210-5377-4cf1-a176-d693fce12c86n%40googlegroups.com?utm_medium=email_source=footer
 
<https://groups.google.com/d/msgid/sage-release/c9f7a210-5377-4cf1-a176-d693fce12c86n%40googlegroups.com?utm_medium=email_source=footer>>.

-- 
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
   

Re: [sage-release] Sage 9.8 released

[François Bissey]

When will we have packages up on pypi? I now rely on these for stable 
release in sage-on-gentoo.


François

On 12/02/23 02:47, Volker Braun wrote:
The "master" git branch has been updated to Sage-9.8. 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 as you are undoubtedly aware, the git repository is now hosted 
at https://github.com/sagemath/sage, so update your git remote.


To commemorate the move (and because we are getting really close to 
.10), I'm proposing to target Sage version 10 as the next release.


The changes over 9.8.rc0 are mainly housekeeping for the new repository 
location.


I'll try to finish up merging remaining positively reviewed trac issues, 
and then move on to github pull requests.


c000c953eb6 (HEAD -> develop, github/master, github/develop, tag: 9.8) 
Updated SageMath version to 9.8

104dde9eaa8 Merge pull request #35022 from tobiasdiez/pr-template-title
17d8a73296f Merge pull request #35018 from x4/public/35017
6a4667bb5c5 Merge pull request #34983 from tobiasdiez/add-issue-templates
66b319baffb Merge pull request #35011 from dimpase/develop
872b32b0c20 Merge pull request #34987 from mezzarobba/missing_long_time
d57804e6dec Merge pull request #34964 from x4/public/linter-20230206
698001b0e6a remove prohibition, promise details
0c5f7baf6c2 remove trac references, promise details soon
200557e00c3 (tag: 9.8.rc1) Updated SageMath version to 9.8.rc1

--
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/c9f7a210-5377-4cf1-a176-d693fce12c86n%40googlegroups.com .


--
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/d335c81a-3f62-c390-c021-f666a94b6d78%40gmail.com.

Re: [sage-release] Re: Sage 9.8.rc0 released

[François Bissey]

There are at least two different issues that breaks the build of the doc 
for you:


[sagemath_doc_html-none] pkg_resources.DistributionNotFound: The 
'fpylll<=0.5.9,>=0.5.9' distribution was not found and is required by 
sagemath-standard
[sagemath_doc_html-none] Warning: Could not import 
sage.manifolds.differentiable.characteristic_cohomology_class 
/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/venv-python3.10/lib/python3.10/site-packages/scipy/special/_ufuncs.cpython-310-x86_64-linux-gnu.so: 
undefined symbol: dstevr_


It seems that fpylll is not installed (yet?) and that's a bit of an issue.
The second problem is a bit more interesting 'dsterv_` is a fortran 
symbol. It looks like your scipy is missing the lapack package it has 
been compiled against - usually openblas - or that lapack is incomplete 
for some reason or not found in the runtime library path.


François

On 4/02/23 18:35, 'Nasser M. Abbasi' via sage-release wrote:

I get this error on Linux virtual box running

lsb_release -a
LSB Version:    n/a
Distributor ID:    ManjaroLinux
Description:    Manjaro Linux
Release:    22.0.0
Codename:    Sikaris

After extracting the gzip file, these are the commands I did

unset SAGE_ROOT
  unset SAGE_LOCAL
  export GIAC=/usr/local/bin/giac
export MAXIMA=/usr/local/bin/maxima
./configure --with-system-python=no
make

At the end I see

-
sagemath_doc_html-none]   File 
"/home/me/TMP/sage-9.8.rc0/src/sage_docbuild/sphinxbuild.py", line 263, 
in raise_errors

[sagemath_doc_html-none]     raise OSError(self._error)
[sagemath_doc_html-none] OSError: 
/home/me/TMP/sage-9.8.rc0/src/sage/manifolds/chart.py:docstring of 
sage.manifolds.chart.RealChart.plot:104: WARNING: Exception occurred in 
plotting chart-1

[sagemath_doc_html-none]
[sagemath_doc_html-none]     Note: incremental documentation builds 
sometimes cause spurious
[sagemath_doc_html-none]     error messages. To be certain that these 
are real errors, run
[sagemath_doc_html-none]     "make doc-clean doc-uninstall" first and 
try again.
[sagemath_doc_html-none] make[6]: *** [Makefile:28: 
doc-inventory--reference-manifolds] Error 1
[sagemath_doc_html-none] make[5]: *** [Makefile:45: 
doc-inventory-reference] Error 2

make[4]: *** [Makefile:3262: sagemath_doc_html-SAGE_DOCS-no-deps] Error 2
make[3]: *** [Makefile:3262: 
/home/me/TMP/sage-9.8.rc0/local/var/lib/sage/installed/sagemath_doc_html-none] Error 2

make[2]: *** [Makefile:2766: all-start] Error 2
make[2]: Leaving directory '/home/me/TMP/sage-9.8.rc0/build/make'

real    71m30.833s
user    103m7.355s
sys    5m48.306s
***
Error building Sage.

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

It is safe to delete any log files and build directories, but they
contain information that is helpful for debugging build problems.
WARNING: If you now run 'make' again, the build directory of the
same version of the package will, by default, be deleted. Set the
environment variable SAGE_KEEP_BUILT_SPKGS=yes to prevent this.


The following folder  contains 
config.log and install.log files


Thank you
--Nasser






On Friday, February 3, 2023 at 3:40:20 AM UTC-6 Dima Pasechnik wrote:

On Fri, Feb 3, 2023 at 7:33 AM Sébastien Labbé 
wrote:
 >
 >
 >
 > On Thursday, February 2, 2023 at 7:37:27 PM UTC+1
matthia...@gmail.com wrote:
 > On Thursday, February 2, 2023 at 9:30:30 AM UTC-8 Sébastien Labbé
wrote:
 > ./bootstrap: 9: m4: Permission denied
 > make: *** [Makefile:365 : configure] Erreur 1
 >
 > Do you have "." in PATH?
 >
 >
 > No
 >
 > What does "which m4" say?
 >
 >
 > It returns nothing! Thanks for the hint. I found the problem:
when reading the sage README to install sage from scratch on this
new machine, I installed the basic stuff as follows:
 >
 > $ sudo apt install gcc gfortran g++ make m4 perl ranlib tar bc
 > [...]
 > E: Impossible de trouver le paquet ranlib
 >
 > But this returned an error on ranlib and I assumed it had
installed the other packages in the list but no, it did not (gcc,
gfortran, etc. were not installed as well).
 >
 > Is ranlib really needed for sage? Can we remove it from the README?

ranlib is a standard tool, and is used by various build systems. On
Debian it's a part of binutils package.

README is not platform-specific, and it does not tell you to install
*package* called ranlib.
However, we should add there an advice to look for what packages to
install in
build/pkgs/_prereq/distros/
(e.g. for Debian it's in build/pkgs/_prereq/distros/debian.txt)

(Once our GitHub is live in few days, it's a very quick PR to do :-))



 >
 >
 >
 > --
 > You received this message because you are subscribed to the

Re: [sage-release] Re: Sage 9.8.beta7 released

[François Bissey]

It is indeed a known issue with nauty on debian/ubuntu. That's the first 
time someone mentioned it in a while but it is definitely broken.


On 23/01/23 21:28, Antonio Rojas wrote:



El lunes, 23 de enero de 2023 a las 9:07:32 UTC+1, tsc...@ucdavis.edu 
escribió:
I am getting stuck at giac, even after a make distclean (I rebuilt 
9.8.beta6 just to confirm this is a problem with the upgrade and almost 
certainly due to #34857). Sorry for posting the log files; I can't seem 
to include attachments...


This is an underlinking issue in your distro's nauty package. Given that 
upstream nauty doesn't build a shared library, it must be caused by some 
incomplete distro custom patch. Try disabling system nauty.


--
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/dee61127-23cf-4619-bebe-ea17a6cd8817n%40googlegroups.com .


--
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/b390333d-6af3-bc05-99ba-2784319548c2%40gmail.com.

Re: [sage-release] Re: Sage 9.7.rc1 released

[François Bissey]

git checkout tags/9.7.rc0

If I am not mistaken.

On 11/09/22 22:50, Emmanuel Charpentier wrote:

Can it be done by telling |git|(how ?) to use 9.7.rc0 ?



--
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/2aae494f-b41b-60c0-5b05-8dc0feadfece%40gmail.com.

Re: [sage-release] Re: Sage 9.7.rc1 released

[François Bissey]

Which really makes me think that a system update is the cause of the 
problem. Changes are not significant for most people between rc0 and rc1.


Of course that theory could  be checked by checking out rc0 and seeing 
if that builds.


François

On 11/09/22 22:42, Emmanuel Charpentier wrote:

BTW : this has worked perfectly up to and oncluding 9.7.rc0...

Le dimanche 11 septembre 2022 à 12:39:17 UTC+2, Emmanuel Charpentier a 
écrit :


System's ecl, as far as I can tell (its `usr/bin/ecl', which is
system's territory...)

Le dimanche 11 septembre 2022 à 12:27:23 UTC+2, François Bissey a
écrit :

System ECL or sage ECL?

On 11/09/22 22:25, Emmanuel Charpentier wrote:
 > Sage's Maxima (5.45.p0). Debian's maxima is gcl-based, hence
unusable in
 > Sage. Not even installed on this machine.
 >
 > BTW : as far as I know, a system's maxima can't (yet) be used
by Sage...
 >
 > Le dimanche 11 septembre 2022 à 12:17:06 UTC+2, François
Bissey a écrit :
 >
 > That kind of error means the maxima.fas library has not been
built or
 > installed or possibly not installed in the right place. Are
you using
 > the system maxima or was sage's maxima build?
 >
 > François
 >
 > On 11/09/22 22:02, Emmanuel Charpentier wrote:
 > > On Debian testing running on core i7 + 16 GB RAM, the
 > documentatiuon of
 > > `plot3d` doesn't build. This seems to be ultimately related
to :
 > >
 > > ```
 > > [sagemath_doc_html-none] [plot3d   ]   File
 > > "/usr/local/sage-9/src/sage/interfaces/
 > > maxima_lib.py", line 114, in 
 > > [sagemath_doc_html-none] [plot3d   ]     ecl_eval("(require
 > 'maxima)")
 > > [sagemath_doc_html-none] [plot3d   ]   File
"sage/libs/ecl.pyx",
 > line
 > > 1352, in sage
 > > .libs.ecl.ecl_eval
 > > [sagemath_doc_html-none] [plot3d   ]     cpdef EclObject
 > ecl_eval(str s):
 > > [sagemath_doc_html-none] [plot3d   ]   File
"sage/libs/ecl.pyx",
 > line
 > > 1375, in sage
 > > .libs.ecl.ecl_eval
 > > [sagemath_doc_html-none] [plot3d   ]
 > > o=ecl_safe_eval(python_to_ecl(s, True))
 > > [sagemath_doc_html-none] [plot3d   ]   File
"sage/libs/ecl.pyx",
 > line
 > > 321, in sage.
 > > libs.ecl.ecl_safe_eval
 > > [sagemath_doc_html-none] [plot3d   ]     raise
RuntimeError("ECL
 > says:
 > > {}".format(m
 > > essage))
 > > [sagemath_doc_html-none] [plot3d   ] RuntimeError: ECL
says: Module
 > > error: Don't know how to REQUIRE MAXIMA.
 > > [sagemath_doc_html-none] [plot3d   ] Extension error:
 > > [sagemath_doc_html-none] [plot3d   ] Cell raised uncaught
exception:
 > > [sagemath_doc_html-none] [plot3d   ]
 > >
 >

---

 >
 > > [sagemath_doc_html-none] [plot3d   ] RuntimeError
 > >        Traceback (most recent call last)
 > > [sagemath_doc_html-none] [plot3d   ] Input In [37], in  line: 2>()
 > > ```
 > > `install.log` follows as an answer to this answer (Google
Groups
 > > interface will no longer let you attach an arbitrary file
to your
 > posts...).
 > >
 > > Le jeudi 8 septembre 2022 à 01:39:00 UTC+2, Volker Braun a
écrit :
 > >
 > > 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
<http://www.sagemath.org/download-latest.html>
 > <http://www.sagemath.org/download-latest.html
<http://www.sagemath.org/download-latest.html>>
 > > <http://www.sagemath.org/download-latest.html
<http://www.sagemath.org/download-latest.html>
 > <http://www.sagemath.org/download-latest.html
<http://www.sagemath.org/download-latest.html>>>
 > >
 > > 08202bc1ba7 (HEAD -> develop, trac/develop, tag: 9.7.rc1)
Updated
 > > SageMath version to 9.7.rc1
 > > 2e5af062ddd Trac #33833: Make furo sage stan

Re: [sage-release] Re: Sage 9.7.rc1 released

[François Bissey]

System ECL or sage ECL?

On 11/09/22 22:25, Emmanuel Charpentier wrote:
Sage's Maxima (5.45.p0). Debian's maxima is gcl-based, hence unusable in 
Sage. Not even installed on this machine.


BTW : as far as I know, a system's maxima can't (yet) be used by Sage...

Le dimanche 11 septembre 2022 à 12:17:06 UTC+2, François Bissey a écrit :

That kind of error means the maxima.fas library has not been built or
installed or possibly not installed in the right place. Are you using
the system maxima or was sage's maxima build?

François

On 11/09/22 22:02, Emmanuel Charpentier wrote:
 > On Debian testing running on core i7 + 16 GB RAM, the
documentatiuon of
 > `plot3d` doesn't build. This seems to be ultimately related to :
 >
 > ```
 > [sagemath_doc_html-none] [plot3d   ]   File
 > "/usr/local/sage-9/src/sage/interfaces/
 > maxima_lib.py", line 114, in 
 > [sagemath_doc_html-none] [plot3d   ]     ecl_eval("(require
'maxima)")
 > [sagemath_doc_html-none] [plot3d   ]   File "sage/libs/ecl.pyx",
line
 > 1352, in sage
 > .libs.ecl.ecl_eval
 > [sagemath_doc_html-none] [plot3d   ]     cpdef EclObject
ecl_eval(str s):
 > [sagemath_doc_html-none] [plot3d   ]   File "sage/libs/ecl.pyx",
line
 > 1375, in sage
 > .libs.ecl.ecl_eval
 > [sagemath_doc_html-none] [plot3d   ]
 > o=ecl_safe_eval(python_to_ecl(s, True))
 > [sagemath_doc_html-none] [plot3d   ]   File "sage/libs/ecl.pyx",
line
 > 321, in sage.
 > libs.ecl.ecl_safe_eval
 > [sagemath_doc_html-none] [plot3d   ]     raise RuntimeError("ECL
says:
 > {}".format(m
 > essage))
 > [sagemath_doc_html-none] [plot3d   ] RuntimeError: ECL says: Module
 > error: Don't know how to REQUIRE MAXIMA.
 > [sagemath_doc_html-none] [plot3d   ] Extension error:
 > [sagemath_doc_html-none] [plot3d   ] Cell raised uncaught exception:
 > [sagemath_doc_html-none] [plot3d   ]
 >
---

 > [sagemath_doc_html-none] [plot3d   ] RuntimeError
 >        Traceback (most recent call last)
 > [sagemath_doc_html-none] [plot3d   ] Input In [37], in ()
 > ```
 > `install.log` follows as an answer to this answer (Google Groups
 > interface will no longer let you attach an arbitrary file to your
posts...).
 >
 > Le jeudi 8 septembre 2022 à 01:39:00 UTC+2, Volker Braun a écrit :
 >
 > 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
<http://www.sagemath.org/download-latest.html>
 > <http://www.sagemath.org/download-latest.html
<http://www.sagemath.org/download-latest.html>>
 >
 > 08202bc1ba7 (HEAD -> develop, trac/develop, tag: 9.7.rc1) Updated
 > SageMath version to 9.7.rc1
 > 2e5af062ddd Trac #33833: Make furo sage standard doc theme
 > 97dacf88f3c Trac #34450: Standard wheel packages
 > b37ed1cf0cc Trac #34152: Remove remaining dependencies of bootstrap
 > on gettext (AC_LIB_RPATH etc.)
 > cae9ee5177a (tag: 9.7.rc0) Updated SageMath version to 9.7.rc0
 >
 > --
 > 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
 > <mailto:sage-release...@googlegroups.com>.
 > To view this discussion on the web visit
 >

https://groups.google.com/d/msgid/sage-release/ad83f2db-1e14-4a12-9c66-6927529d0f6cn%40googlegroups.com

<https://groups.google.com/d/msgid/sage-release/ad83f2db-1e14-4a12-9c66-6927529d0f6cn%40googlegroups.com>

 >

<https://groups.google.com/d/msgid/sage-release/ad83f2db-1e14-4a12-9c66-6927529d0f6cn%40googlegroups.com?utm_medium=email_source=footer

<https://groups.google.com/d/msgid/sage-release/ad83f2db-1e14-4a12-9c66-6927529d0f6cn%40googlegroups.com?utm_medium=email_source=footer>>.


--
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 
<mailto:sage-release+unsubscr...@googlegroups.com>.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/0a45ec28-9531-4f93-afca-1c92c5a2dbf6n%40googlegroups.com 
<https://groups.google.com/d/msgid/sage-release/0a45ec28-9531-4f93-afca-1c92c5a2dbf6n%40go

Re: [sage-release] Re: Sage 9.7.rc1 released

[François Bissey]

That kind of error means the maxima.fas library has not been built or 
installed or possibly not installed in the right place. Are you using 
the system maxima or was sage's maxima build?


François

On 11/09/22 22:02, Emmanuel Charpentier wrote:
On Debian testing running on core i7 + 16 GB RAM, the documentatiuon of 
`plot3d` doesn't build. This seems to be ultimately related to :


```
[sagemath_doc_html-none] [plot3d   ]   File 
"/usr/local/sage-9/src/sage/interfaces/

maxima_lib.py", line 114, in 
[sagemath_doc_html-none] [plot3d   ]     ecl_eval("(require 'maxima)")
[sagemath_doc_html-none] [plot3d   ]   File "sage/libs/ecl.pyx", line 
1352, in sage

.libs.ecl.ecl_eval
[sagemath_doc_html-none] [plot3d   ]     cpdef EclObject ecl_eval(str s):
[sagemath_doc_html-none] [plot3d   ]   File "sage/libs/ecl.pyx", line 
1375, in sage

.libs.ecl.ecl_eval
[sagemath_doc_html-none] [plot3d   ] 
o=ecl_safe_eval(python_to_ecl(s, True))
[sagemath_doc_html-none] [plot3d   ]   File "sage/libs/ecl.pyx", line 
321, in sage.

libs.ecl.ecl_safe_eval
[sagemath_doc_html-none] [plot3d   ]     raise RuntimeError("ECL says: 
{}".format(m

essage))
[sagemath_doc_html-none] [plot3d   ] RuntimeError: ECL says: Module 
error: Don't know how to REQUIRE MAXIMA.

[sagemath_doc_html-none] [plot3d   ] Extension error:
[sagemath_doc_html-none] [plot3d   ] Cell raised uncaught exception:
[sagemath_doc_html-none] [plot3d   ] 
---
[sagemath_doc_html-none] [plot3d   ] RuntimeError   
        Traceback (most recent call last)

[sagemath_doc_html-none] [plot3d   ] Input In [37], in ()
```
`install.log` follows as an answer to this answer (Google Groups 
interface will no longer let you attach an arbitrary file to your posts...).


Le jeudi 8 septembre 2022 à 01:39:00 UTC+2, Volker Braun a écrit :

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


08202bc1ba7 (HEAD -> develop, trac/develop, tag: 9.7.rc1) Updated
SageMath version to 9.7.rc1
2e5af062ddd Trac #33833: Make furo sage standard doc theme
97dacf88f3c Trac #34450: Standard wheel packages
b37ed1cf0cc Trac #34152: Remove remaining dependencies of bootstrap
on gettext (AC_LIB_RPATH etc.)
cae9ee5177a (tag: 9.7.rc0) Updated SageMath version to 9.7.rc0

--
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/ad83f2db-1e14-4a12-9c66-6927529d0f6cn%40googlegroups.com 
.


--
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/b53e11fd-ccf4-32f6-7788-aa0b96ee2559%40gmail.com.

Re: [sage-release] Sage 9.7.beta3 released

[François Bissey]

Fix at https://trac.sagemath.org/ticket/34037 is ready for review.

> On 21/06/2022, at 13:13, François Bissey  wrote:
> 
> The test was introduced in https://trac.sagemath.org/ticket/25626 and you can 
> see my comment at the end. We need to follow up to make sure the result is 
> tested in a more version independent form.
> 
>> On 21/06/2022, at 13:08, François Bissey  wrote:
>> 
>> I meant to follow up on that. The test has been added in a recent ticket but 
>> the result is different between giac 1.7 and giac 1.9. Both results are 
>> equivalent but the 1.7 is more compact (simplified?). The failure means you 
>> have giac 1.9 installed.
>> 
>>> On 21/06/2022, at 13:05, 'tsc...@ucdavis.edu' via sage-release 
>>>  wrote:
>>> 
>>> I don't know when these errors started to appear, but I am getting the 
>>> following failures:
>>> 
>>> Using 
>>> --optional=4ti2,bliss,coxeter3,debian,e_antic,fricas,gap_packages,latte_int,libsemigroups,lidia,meataxe,normaliz,pip,sage,sage_spkg,tides
>>> Features to be detected: 
>>> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
>>> Doctesting 2 files using 24 threads.
>>> sage -t --warn-long 41.4 
>>> --random-seed=318832280051652493374019680328048210704 
>>> src/sage/calculus/calculus.py
>>> **
>>> File "src/sage/calculus/calculus.py", line 387, in sage.calculus.calculus
>>> Failed example:
>>>   integrate(exp(t)/(t + 1)^2, t, algorithm="giac")
>>> Expected:
>>>   (t*Ei(t + 1) + Ei(t + 1) - e^(t + 1))/(t*e + e)
>>> Got:
>>>   ((t + 1)*(1/(t + 1) - 1)*Ei(-(t + 1)*(1/(t + 1) - 1) + 1) - Ei(-(t + 
>>> 1)*(1/(t + 1) - 1) + 1) + e^(-(t + 1)*(1/(t + 1) - 1) + 1))/((t + 1)*(1/(t 
>>> + 1) - 1)*e - e)
>>> **
>> 
> 

-- 
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/25F4C557-7749-4FC4-97F5-D12D35932ECA%40gmail.com.

Re: [sage-release] Sage 9.7.beta3 released

[François Bissey]

The test was introduced in https://trac.sagemath.org/ticket/25626 and you can 
see my comment at the end. We need to follow up to make sure the result is 
tested in a more version independent form.

> On 21/06/2022, at 13:08, François Bissey  wrote:
> 
> I meant to follow up on that. The test has been added in a recent ticket but 
> the result is different between giac 1.7 and giac 1.9. Both results are 
> equivalent but the 1.7 is more compact (simplified?). The failure means you 
> have giac 1.9 installed.
> 
>> On 21/06/2022, at 13:05, 'tsc...@ucdavis.edu' via sage-release 
>>  wrote:
>> 
>> I don't know when these errors started to appear, but I am getting the 
>> following failures:
>> 
>> Using 
>> --optional=4ti2,bliss,coxeter3,debian,e_antic,fricas,gap_packages,latte_int,libsemigroups,lidia,meataxe,normaliz,pip,sage,sage_spkg,tides
>> Features to be detected: 
>> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
>> Doctesting 2 files using 24 threads.
>> sage -t --warn-long 41.4 
>> --random-seed=318832280051652493374019680328048210704 
>> src/sage/calculus/calculus.py
>> **
>> File "src/sage/calculus/calculus.py", line 387, in sage.calculus.calculus
>> Failed example:
>>integrate(exp(t)/(t + 1)^2, t, algorithm="giac")
>> Expected:
>>(t*Ei(t + 1) + Ei(t + 1) - e^(t + 1))/(t*e + e)
>> Got:
>>((t + 1)*(1/(t + 1) - 1)*Ei(-(t + 1)*(1/(t + 1) - 1) + 1) - Ei(-(t + 
>> 1)*(1/(t + 1) - 1) + 1) + e^(-(t + 1)*(1/(t + 1) - 1) + 1))/((t + 1)*(1/(t + 
>> 1) - 1)*e - e)
>> **
> 

-- 
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/11959F40-9345-46A7-A8E3-27E0A754D00D%40gmail.com.

Re: [sage-release] Sage 9.7.beta3 released

[François Bissey]

I meant to follow up on that. The test has been added in a recent ticket but 
the result is different between giac 1.7 and giac 1.9. Both results are 
equivalent but the 1.7 is more compact (simplified?). The failure means you 
have giac 1.9 installed.

> On 21/06/2022, at 13:05, 'tsc...@ucdavis.edu' via sage-release 
>  wrote:
> 
> I don't know when these errors started to appear, but I am getting the 
> following failures:
> 
> Using 
> --optional=4ti2,bliss,coxeter3,debian,e_antic,fricas,gap_packages,latte_int,libsemigroups,lidia,meataxe,normaliz,pip,sage,sage_spkg,tides
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,gfan,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,msolve,nauty,palp,pandoc,pdf2svg,pdftocairo,phitigra,plantri,polytopes_db,polytopes_db_4d,pynormaliz,python_igraph,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.groups,sage.plot,sage.rings.number_field,sage.rings.padics,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
> Doctesting 2 files using 24 threads.
> sage -t --warn-long 41.4 
> --random-seed=318832280051652493374019680328048210704 
> src/sage/calculus/calculus.py
> **
> File "src/sage/calculus/calculus.py", line 387, in sage.calculus.calculus
> Failed example:
> integrate(exp(t)/(t + 1)^2, t, algorithm="giac")
> Expected:
> (t*Ei(t + 1) + Ei(t + 1) - e^(t + 1))/(t*e + e)
> Got:
> ((t + 1)*(1/(t + 1) - 1)*Ei(-(t + 1)*(1/(t + 1) - 1) + 1) - Ei(-(t + 
> 1)*(1/(t + 1) - 1) + 1) + e^(-(t + 1)*(1/(t + 1) - 1) + 1))/((t + 1)*(1/(t + 
> 1) - 1)*e - e)
> **

-- 
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/5985B9E9-486F-469C-86C6-C9F041AFE69B%40gmail.com.

Re: [sage-release] Sage 9.6 released

[François Bissey]

How long until we have stuff on pypi? That’s when I will pick up the work in 
sage-on-gentoo in the current framework.

Thanks for the release!

> On 16/05/2022, at 10:33, Matthias Köppe  wrote:
> 
> Yay! Thanks a lot, Volker.
> 
> On Sunday, May 15, 2022 at 3:27:40 PM UTC-7 Volker Braun wrote:
> The "master" git branch has been updated to Sage-9.6. 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
> 
> There was no change over 9.6.rc4
> Sage
> 
> -- 
> 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/f8367c34-48c8-4227-b484-a98ced30ad0dn%40googlegroups.com.

-- 
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/19BFB425-F893-47FA-A543-FC6481B473DE%40gmail.com.

Re: [sage-release] Sage 9.6 released

[François Bissey]

I finally pushed 9.6 to master in sage-on-gentoo. An unusually long time 
between actual release and availability for me.
Early testing seems to show we suffer from 
https://trac.sagemath.org/ticket/33304 in a repeatable manner in 9.6 in Gentoo. 
May be we’ll be able to tackle it.

> On 16/05/2022, at 10:27, Volker Braun  wrote:
> 
> The "master" git branch has been updated to Sage-9.6. 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
> 
> There was no change over 9.6.rc4
> Sage
> 
> -- 
> 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/71a2285d-226c-4aac-a804-971a58710ad5n%40googlegroups.com.

-- 
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/914331AF-EA48-472E-910D-4FD158A8573B%40gmail.com.

Re: [sage-release] Sage 9.6.rc3 released

[François Bissey]

That is https://github.com/cschwan/sage-on-gentoo/issues/682

> On 2/05/2022, at 07:04, Matthias Köppe  wrote:
> 
> gentoo: Clean
> - except for (https://github.com/sagemath/sage/runs/6236170009): 
> src/sage/interfaces/giac.py
> 

It means something went wrong when giac was updated on the system in the past 
and the documentation is not pointed to the right place.

Nothing to do with sage itself.

François

-- 
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/59A6CF28-1F36-48DB-9CEF-9B1B701D8DB1%40gmail.com.

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

[François Bissey]

In that particular case, because giac from the system is used, either the 
system giac is missing some dependencies or someone broke their system by 
removing libcliquer without removing nauty itself (which with apt may mean 
giving the wrong answer to a prompt explaining that you are about to break 
something).
Unless the user explicitly broke their system, I’d say it is a bug in that 
distribution. 

> On 28/04/2022, at 08:22, Matthias Köppe  wrote:
> 
> There are some undeclared dependencies - see 
> https://trac.sagemath.org/ticket/31403
> 
> On Wednesday, April 27, 2022 at 12:43:34 PM UTC-7 François Bissey wrote:
> Actually, that means libcliquer is not installed as a dependency of nauty. 
> Those symbols are supposed to be from libcliquer. 
> 
> > On 28/04/2022, at 03:43, Dima Pasechnik  wrote: 
> > 
> > 
> > 
> > On Wed, 27 Apr 2022, 16:26 David Joyner,  wrote: 
> > On Wed, Apr 27, 2022 at 10:44 AM Dima Pasechnik  wrote: 
> > > 
> > > This looks like incompatiblity with system-wide nauty (I assume Sage 
> > > installed its own nauty, right?/ 
> > > 
> > > Can you uninstall the system nauty and try again? 
> > > 
> > 
> > I don't see a system-wide nauty. I installed giac 1.6.0 using 
> > sudo apt install xcas 
> > but 
> > ./config.status --recheck && ./config.status 
> > make 
> > didn't seem to pick it up. 
> > 
> > the system wide giac might come with libnauty, no? Anyway, the following 
> > are errors from you log, and they are about 
> > missing symbols in a copy of libnauty.so 
> > in /usr/lib 
> > 
> > So you do have it there 
> > 
> > 
> > 619 /usr/bin/ld: /usr/lib/gcc/x86_64-linux 
> > -gnu/11/../../../x86_64-linux-gnu/libn 
> > auty.so: undefined reference to `graph 
> > _free@CLIQUER_1' 
> > 620 /usr/bin/ld: /usr/lib/gcc/x86_64-linux 
> > -gnu/11/../../../x86_64-linux-gnu/libn 
> > auty.so: undefined reference to `cliqu 
> > e_unweighted_find_single@CLIQUER_1' 
> > 621 /usr/bin/ld: /usr/lib/gcc/x86_64-linux 
> > -gnu/11/../../../x86_64-linux-gnu/libn 
> > auty.so: undefined reference to `graph 
> > _new@CLIQUER_1' 
> > 
> > 
> > 
> > 
> > 
> > > On Wed, 27 Apr 2022, 14:57 David Joyner,  wrote: 
> > >> 
> > >> Hi: 
> > >> 
> > >> On a Ubuntu 21.10 laptop, I got this: 
> > >> 
> > >> The following package(s) may have failed to build (not necessarily 
> > >> during this run of 'make all-start'): 
> > >> * package: giac-1.6.0.47p3.p0 
> > >> 
> > >> The log file is attached. 
> > >> 
> > >> - David Joyner 
> > >> 
> > >> On Mon, Apr 25, 2022 at 6:48 PM Volker Braun  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 
> > >> > 
> > >> > 67c34fee1d (trac/develop, tag: 9.6.rc2) Updated SageMath version to 
> > >> > 9.6.rc2 
> > >> > 9b2069cf00 Trac #33747: Fix workflow build.yml 
> > >> > b9dce970ea Trac #33746: Upgrade virtualenv, fix missing dependencies 
> > >> > 8b27cf35a9 Trac #33738: Standard package beautifulsoup4 is missing a 
> > >> > dependency 
> > >> > 7950f93e7c Trac #33588: warnings to ignore are not ignored when a 
> > >> > doctest is tagged with # tol 
> > >> > a68c1a Trac #33729: Latex display of integer mod ring is broken 
> > >> > 14be90c7b8 Trac #33724: GH Actions: Use 
> > >> > --enable-download-from-upstream-url in build, doc-build workflows 
> > >> > 4c9e563885 Trac #33722: symengine: Fix install script 
> > >> > f1c3da866a Trac #33694: Developer manual: Remove mention of 
> > >> > SAGE_ROOT/src/module_list.py 
> > >> > fbe3865362 Trac #33672: python3 spkg-configure.m4: Suppress output 
> > >> > 3285e374b4 Trac #33666: Mutable polyhedron (ppl) saves incorrect 
> > >> > Vrepresentation 
> > >> > a00769f3a1 Trac #33648: Update/reorder git instructions in Developer's 
> > >> > Guide 
> > >> > 121b0a8dd6 Trac #33592: do not use temp file with jupyter nb by 
> > >> > default 
> > >> > 781a14a17d Trac #33521: doctesting with pytest fails on system install 
> > >> > of sage 
> &g

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

[François Bissey]

Actually, that means libcliquer is not installed as a dependency of nauty. 
Those symbols are supposed to be from libcliquer.

> On 28/04/2022, at 03:43, Dima Pasechnik  wrote:
> 
> 
> 
> On Wed, 27 Apr 2022, 16:26 David Joyner,  wrote:
> On Wed, Apr 27, 2022 at 10:44 AM Dima Pasechnik  wrote:
> >
> > This looks like incompatiblity with system-wide nauty (I assume Sage 
> > installed its own nauty, right?/
> >
> > Can you uninstall the system nauty and try again?
> >
> 
> I don't see a system-wide nauty. I installed giac 1.6.0 using
> sudo apt install xcas
> but
> ./config.status --recheck && ./config.status
> make
> didn't seem to pick it up.
> 
> the system wide giac might come with libnauty, no? Anyway, the following are 
> errors from you log, and they are about 
> missing symbols in a copy of libnauty.so
> in /usr/lib
> 
> So you do have it there
> 
> 
> 619 /usr/bin/ld: /usr/lib/gcc/x86_64-linux
> -gnu/11/../../../x86_64-linux-gnu/libn
> auty.so: undefined reference to `graph
> _free@CLIQUER_1'  
> 620 /usr/bin/ld: /usr/lib/gcc/x86_64-linux
> -gnu/11/../../../x86_64-linux-gnu/libn
> auty.so: undefined reference to `cliqu
> e_unweighted_find_single@CLIQUER_1'   
> 621 /usr/bin/ld: /usr/lib/gcc/x86_64-linux
> -gnu/11/../../../x86_64-linux-gnu/libn
> auty.so: undefined reference to `graph
> _new@CLIQUER_1'   
> 
> 
> 
> 
> 
> > On Wed, 27 Apr 2022, 14:57 David Joyner,  wrote:
> >>
> >> Hi:
> >>
> >> On a Ubuntu 21.10 laptop, I got this:
> >>
> >> The following package(s) may have failed to build (not necessarily
> >> during this run of 'make all-start'):
> >> * package: giac-1.6.0.47p3.p0
> >>
> >> The log file is attached.
> >>
> >> - David Joyner
> >>
> >> On Mon, Apr 25, 2022 at 6:48 PM Volker Braun  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
> >> >
> >> > 67c34fee1d (trac/develop, tag: 9.6.rc2) Updated SageMath version to 
> >> > 9.6.rc2
> >> > 9b2069cf00 Trac #33747: Fix workflow build.yml
> >> > b9dce970ea Trac #33746: Upgrade virtualenv, fix missing dependencies
> >> > 8b27cf35a9 Trac #33738: Standard package beautifulsoup4 is missing a 
> >> > dependency
> >> > 7950f93e7c Trac #33588: warnings to ignore are not ignored when a 
> >> > doctest is tagged with # tol
> >> > a68c1a Trac #33729: Latex display of integer mod ring is broken
> >> > 14be90c7b8 Trac #33724: GH Actions: Use 
> >> > --enable-download-from-upstream-url in build, doc-build workflows
> >> > 4c9e563885 Trac #33722: symengine: Fix install script
> >> > f1c3da866a Trac #33694: Developer manual: Remove mention of 
> >> > SAGE_ROOT/src/module_list.py
> >> > fbe3865362 Trac #33672: python3 spkg-configure.m4: Suppress output
> >> > 3285e374b4 Trac #33666: Mutable polyhedron (ppl) saves incorrect 
> >> > Vrepresentation
> >> > a00769f3a1 Trac #33648: Update/reorder git instructions in Developer's 
> >> > Guide
> >> > 121b0a8dd6 Trac #33592: do not use temp file with jupyter nb by default
> >> > 781a14a17d Trac #33521: doctesting with pytest fails on system install 
> >> > of sage
> >> > 79dc3dfb7c Trac #33088: More updates for installation and developer 
> >> > guides
> >> > b5a7bd11a3 Trac #33078: Update package info for system python3 on Cygwin
> >> > ad69a5b07b (tag: 9.6.rc1) Updated SageMath version to 9.6.rc1
> >> >
> >> > --
> >> > 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/fbf8ad45-310d-46ce-af60-d1f895f68df8n%40googlegroups.com.
> >>
> >> --
> >> 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/CAEQuuAWzW1LwEqg7NDOcOAAZN-rbnYsirkzdwi2eZD5W0PT8Eg%40mail.gmail.com.
> >
> > --
> > 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/CAAWYfq1Ha8zgvRU_H1dCdy_GLy4%2BJ%2B4QHBV2MHssJYS3gN8DZg%40mail.gmail.com.
> 
> -- 
> 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 

Re: [sage-release] Sage 9.5 released

[François Bissey]

I just remember while downloading one of these tarballs why I prefer the GitHub 
one. It is much smaller since it doesn’t have the “upstream” folder which is 
otherwise irrelevant to my packaging. Downloading one of these for my purpose 
is a waste of bandwidth for me and the users.

> On 31/01/2022, at 11:51, François Bissey  wrote:
> 
> That page is still listing 9.4 and not all mirrors have 9.5 yet. aarnet which 
> would be my closest mirror is not yet updated at the time of writing.
> I guess I’ll wait a few hours. 
> 
>> On 31/01/2022, at 11:48, Thierry  wrote:
>> 
>> You can find it on the mirrors
>> https://www.sagemath.org/download-source.html
> 

-- 
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/D95B9C76-49D2-47D4-811A-BF351AF138BA%40gmail.com.

Re: [sage-release] Sage 9.5.rc0 released

[François Bissey]

That one is because a recent gain is used see 
https://trac.sagemath.org/ticket/31563

> On 11/01/2022, at 06:11, Emmanuel Charpentier  
> wrote:
> 
> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long --warn-long 230.6 
> --random-seed=55945959185617375554737887082041268498 
> src/sage/functions/min_max.py  # 2 doctests failed
> Running doctests with ID 2022-01-10-17-59-37-1c60f093.
> Git branch: develop
> Using 
> --optional=build,debian,debugpy,dot2tex,fricas,gap_packages,libsemigroups,pip,sage,sage_spkg
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,pandoc,pdf2svg,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
> Doctesting 1 file.
> sage -t --long --warn-long 230.6 
> --random-seed=55945959185617375554737887082041268498 
> src/sage/functions/min_max.py
> **
> File "src/sage/functions/min_max.py", line 236, in 
> sage.functions.min_max.MaxSymbolic._evalf_
> Failed example:
> r
> Expected:
> sqrt(2) - cos(1)
> Got:
> 0.873911256505000
> **
> File "src/sage/functions/min_max.py", line 238, in 
> sage.functions.min_max.MaxSymbolic._evalf_
> Failed example:
> r.n()
> Expected:
> 0.873911256504955
> Got:
> 0.873911256505000
> **
> 1 item had failures:
>2 of  11 in sage.functions.min_max.MaxSymbolic._evalf_
> [69 tests, 2 failures, 1.15 s]
> --
> sage -t --long --warn-long 230.6 
> --random-seed=55945959185617375554737887082041268498 
> src/sage/functions/min_max.py  # 2 doctests failed
> --
> Total time for all tests: 1.2 seconds
> cpu time: 1.3 seconds
> cumulative wall time: 1.1 seconds
> Features detected for doctesting: 
> Pytest is not installed, skip checking tests that rely on it.
> 
> Numerical noise ?
> 

-- 
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/0315DA3F-CC81-45D1-B6D2-98D24B01AB21%40gmail.com.

Re: [sage-release] Sage 9.5.rc0 released

[François Bissey]

This is now https://trac.sagemath.org/ticket/33141 - would be nice to get fix 
for 9.5 but it is not exactly critical :)

> On 10/01/2022, at 16:52, François Bissey  wrote:
> 
> It seems that after Trac #32759 I now doctest sage_setup and sage_docbuild in 
> sage-on-gentoo. It was either broken or suppressed voluntarily on my part 
> before. But now those files are doctested here and testing on distro revealed 
> a few things that could be improved.
> 
> $ sage -t --long --random-seed=204418260052577960635697341654995479733 
> /usr/lib/python3.10/site-packages/sage_setup/find.py 
> too many failed tests, not using stored timings
> Running doctests with ID 2022-01-10-16-39-00-700eda06.
> Using --optional=pip,sage
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,pandoc,pdf2svg,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
> Doctesting 1 file.
> sage -t --long --random-seed=204418260052577960635697341654995479733 
> /usr/lib/python3.10/site-packages/sage_setup/find.py
> **
> File "/usr/lib/python3.10/site-packages/sage_setup/find.py", line 243, in 
> sage_setup.find._cythonized_dir
> Failed example:
>_cythonized_dir(SAGE_SRC, editable_install=False)
> Exception raised:
>Traceback (most recent call last):
>  File "/usr/lib/python3.10/site-packages/sage/doctest/forker.py", line 
> 694, in _run
>self.compile_and_execute(example, compiler, test.globs)
>  File "/usr/lib/python3.10/site-packages/sage/doctest/forker.py", line 
> 1088, in compile_and_execute
>exec(compiled, globs)
>  File "", line 1, in 
>_cythonized_dir(SAGE_SRC, editable_install=False)
>  File "/usr/lib/python3.10/site-packages/sage_setup/find.py", line 261, 
> in _cythonized_dir
>return Path(SAGE_ROOT) / "build" / "pkgs" / "sagelib" / "src" / 
> "build" / "cythonized"
>  File "/usr/lib/python3.10/pathlib.py", line 958, in __new__
>self = cls._from_parts(args)
>  File "/usr/lib/python3.10/pathlib.py", line 592, in _from_parts
>drv, root, parts = self._parse_args(args)
>  File "/usr/lib/python3.10/pathlib.py", line 576, in _parse_args
>a = os.fspath(a)
>TypeError: expected str, bytes or os.PathLike object, not NoneType
> **
> File "/usr/lib/python3.10/site-packages/sage_setup/find.py", line 303, in 
> sage_setup.find.find_extra_files
> Failed example:
>extras["sage/ext/interpreters"]
> Expected:
>['.../src/sage/ext/interpreters/wrapper_cdf.pxd', ...wrapper_cdf.h...]
> Got:
>['/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cc.pyx',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cc.pxd',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_py.pyx',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rdf.pxd',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rr.pyx',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rr.pxd',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_el.pxd',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rdf.pyx',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_py.pxd',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_el.pyx',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cdf.pyx',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cdf.pxd',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rr.h',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cc.h',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cdf.h',
> '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_el.h']
> **
> 2 items had failures:
>   1 of   4 in sage_setup.find._cythonized_dir
>   1 of   7 in sage_setup.find.find_extra_files
>[44 tests, 2 failures, 1.08 s]
> --
> sage -t --long --random-seed=2044182600

Re: [sage-release] Sage 9.5.rc0 released

[François Bissey]

It seems that after Trac #32759 I now doctest sage_setup and sage_docbuild in 
sage-on-gentoo. It was either broken or suppressed voluntarily on my part 
before. But now those files are doctested here and testing on distro revealed a 
few things that could be improved.

$ sage -t --long --random-seed=204418260052577960635697341654995479733 
/usr/lib/python3.10/site-packages/sage_setup/find.py 
too many failed tests, not using stored timings
Running doctests with ID 2022-01-10-16-39-00-700eda06.
Using --optional=pip,sage
Features to be detected: 
4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,pandoc,pdf2svg,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,sagemath_doc_html,sphinx,tdlib
Doctesting 1 file.
sage -t --long --random-seed=204418260052577960635697341654995479733 
/usr/lib/python3.10/site-packages/sage_setup/find.py
**
File "/usr/lib/python3.10/site-packages/sage_setup/find.py", line 243, in 
sage_setup.find._cythonized_dir
Failed example:
_cythonized_dir(SAGE_SRC, editable_install=False)
Exception raised:
Traceback (most recent call last):
  File "/usr/lib/python3.10/site-packages/sage/doctest/forker.py", line 
694, in _run
self.compile_and_execute(example, compiler, test.globs)
  File "/usr/lib/python3.10/site-packages/sage/doctest/forker.py", line 
1088, in compile_and_execute
exec(compiled, globs)
  File "", line 1, in 
_cythonized_dir(SAGE_SRC, editable_install=False)
  File "/usr/lib/python3.10/site-packages/sage_setup/find.py", line 261, in 
_cythonized_dir
return Path(SAGE_ROOT) / "build" / "pkgs" / "sagelib" / "src" / "build" 
/ "cythonized"
  File "/usr/lib/python3.10/pathlib.py", line 958, in __new__
self = cls._from_parts(args)
  File "/usr/lib/python3.10/pathlib.py", line 592, in _from_parts
drv, root, parts = self._parse_args(args)
  File "/usr/lib/python3.10/pathlib.py", line 576, in _parse_args
a = os.fspath(a)
TypeError: expected str, bytes or os.PathLike object, not NoneType
**
File "/usr/lib/python3.10/site-packages/sage_setup/find.py", line 303, in 
sage_setup.find.find_extra_files
Failed example:
extras["sage/ext/interpreters"]
Expected:
['.../src/sage/ext/interpreters/wrapper_cdf.pxd', ...wrapper_cdf.h...]
Got:
['/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cc.pyx',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cc.pxd',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_py.pyx',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rdf.pxd',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rr.pyx',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rr.pxd',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_el.pxd',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rdf.pyx',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_py.pxd',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_el.pyx',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cdf.pyx',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cdf.pxd',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_rr.h',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cc.h',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_cdf.h',
 '/usr/lib/python3.10/site-packages/sage/ext/interpreters/wrapper_el.h']
**
2 items had failures:
   1 of   4 in sage_setup.find._cythonized_dir
   1 of   7 in sage_setup.find.find_extra_files
[44 tests, 2 failures, 1.08 s]
--
sage -t --long --random-seed=204418260052577960635697341654995479733 
/usr/lib/python3.10/site-packages/sage_setup/find.py  # 2 doctests failed

The first failure should be made “# optional - build” like the test preceding 
it. There is no reason why one is and not the other as far as I can tell.
The second could be fixed by a slight change in the output. But if it has to 
rely on real source to be present for the test to be meaningful it should again 
be marked “# optional - build”.

$ sage -t --long --random-seed=204418260052577960635697341654995479733 
/usr/lib/python3.10/site-packages/sage_setup/optional_extension.py
too many failed tests, not using stored timings
Running doctests with ID 

Re: [sage-release] Sage 9.5.beta9 released

[François Bissey]

The failures in min_max.py are caused by recent giac. See 
https://trac.sagemath.org/ticket/31563.

> On 25/12/2021, at 09:40, Emmanuel Charpentier  
> wrote:
> 
> FWIW, on Debian testing running on core i7 + 16 GB RAM, ptestlong gives only 
> two (permanent) failures, both new IIRC :
> 
> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long 
> --random-seed=181521996982838512350283316361467808663 
> src/sage/quadratic_forms/binary_qf.py  # 1 doctest failed
> Running doctests with ID 2021-12-24-21-10-49-e0ec083d.
> Git branch: develop
> Using 
> --optional=build,debian,debugpy,dochtml,dot2tex,fricas,gap_packages,libsemigroups,pip,sage,sage_spkg
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,pandoc,pdf2svg,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,tdlib
> Doctesting 1 file.
> sage -t --long --warn-long 228.2 
> --random-seed=181521996982838512350283316361467808663 
> src/sage/quadratic_forms/binary_qf.py
> **
> File "src/sage/quadratic_forms/binary_qf.py", line 1498, in 
> sage.quadratic_forms.binary_qf.BinaryQF.solve_integer
> Failed example:
> xy is None or Q(*xy) == 0
> Expected:
> True
> Got:
> False
> **
> 1 item had failures:
>1 of  12 in sage.quadratic_forms.binary_qf.BinaryQF.solve_integer
> [282 tests, 1 failure, 0.25 s]
> --
> sage -t --long --warn-long 228.2 
> --random-seed=181521996982838512350283316361467808663 
> src/sage/quadratic_forms/binary_qf.py  # 1 doctest failed
> --
> Total time for all tests: 0.3 seconds
> cpu time: 0.2 seconds
> cumulative wall time: 0.3 seconds
> Features detected for doctesting: 
> Pytest is not installed, skip checking tests that rely on it.
> charpent@zen-book-flip:/usr/local/sage-9$ sage -t --long 
> --random-seed=181521996982838512350283316361467808663 
> src/sage/functions/min_max.py  # 2 doctests failed
> Running doctests with ID 2021-12-24-21-11-25-19653f31.
> Git branch: develop
> Using 
> --optional=build,debian,debugpy,dochtml,dot2tex,fricas,gap_packages,libsemigroups,pip,sage,sage_spkg
> Features to be detected: 
> 4ti2,benzene,bliss,buckygen,conway_polynomials,csdp,database_cremona_ellcurve,database_cremona_mini_ellcurve,database_jones_numfield,database_knotinfo,dvipng,ffmpeg,graphviz,imagemagick,jupymake,kenzo,latte_int,lrslib,mcqd,meataxe,pandoc,pdf2svg,plantri,pynormaliz,rubiks,sage.combinat,sage.geometry.polyhedron,sage.graphs,sage.plot,sage.rings.number_field,sage.rings.real_double,sage.symbolic,sage_numerical_backends_coin,tdlib
> Doctesting 1 file.
> sage -t --long --warn-long 228.2 
> --random-seed=181521996982838512350283316361467808663 
> src/sage/functions/min_max.py
> **
> File "src/sage/functions/min_max.py", line 236, in 
> sage.functions.min_max.MaxSymbolic._evalf_
> Failed example:
> r
> Expected:
> sqrt(2) - cos(1)
> Got:
> 0.873911256505000
> **
> File "src/sage/functions/min_max.py", line 238, in 
> sage.functions.min_max.MaxSymbolic._evalf_
> Failed example:
> r.n()
> Expected:
> 0.873911256504955
> Got:
> 0.873911256505000
> **
> 1 item had failures:
>2 of  11 in sage.functions.min_max.MaxSymbolic._evalf_
> [69 tests, 2 failures, 0.84 s]
> --
> sage -t --long --warn-long 228.2 
> --random-seed=181521996982838512350283316361467808663 
> src/sage/functions/min_max.py  # 2 doctests failed
> --
> Total time for all tests: 0.9 seconds
> cpu time: 1.3 seconds
> cumulative wall time: 0.8 seconds
> Features detected for doctesting: 
> Pytest is not installed, skip checking tests that rely on it.
> 
> sage -t --long --random-seed=181521996982838512350283316361467808663 
> src/sage/rings/polynomial/polynomial_zmod_flint.pyx still times out during 
> ptestlong and passes when ran standalone.
> 
> HTH,
> 
> Le vendredi 24 décembre 2021 à 12:48:16 UTC+1, Volker Braun a écrit :
> 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
> 
> 
> c5af19568ca Updated SageMath version to 9.5.beta9
> b879fe3b055 

Re: [sage-release] Sage 9.5.beta4 released

[François Bissey]

I actually observed the second one in sage-on-gentoo but it didn’t persist 
after re-running twice the doctest.
I still have the failure in my logs but cannot reproduce it anymore.

François

> On 21/10/2021, at 19:44, Vincent Delecroix <20100.delecr...@gmail.com> wrote:
> 
> I got two doctest failures on a freshly compiled sage on Debian
> bullseye (see below). The first one looks similar to
> https://trac.sagemath.org/ticket/27477. The second one is
> plausibly dependent on the version of gmp used.
> 
> Best
> Vincent
> 
> sage -t --long --warn-long 40.6 
> --random-seed=162931060078355221068468643985410122317 
> src/sage/rings/integer.pyx
> **
> File "src/sage/rings/integer.pyx", line 3020, in 
> sage.rings.integer.Integer.divisors
> Failed example:
>for i in range(20):  # long time
>try:
>alarm(RDF.random_element(1e-3, 0.5))
>_ = n.divisors()
>cancel_alarm()  # we never get here
>except AlarmInterrupt:
>pass
> Exception raised:
>Traceback (most recent call last):
>  File 
> "/home/debian/sage/local/lib/python3.9/site-packages/sage/doctest/forker.py", 
> line 694, in _run
>self.compile_and_execute(example, compiler, test.globs)
>  File 
> "/home/debian/sage/local/lib/python3.9/site-packages/sage/doctest/forker.py", 
> line 1088, in compile_and_execute
>exec(compiled, globs)
>  File "", line 4, in 
> 
>_ = n.divisors()
>  File "sage/rings/integer.pyx", line 3120, in 
> sage.rings.integer.Integer.divisors 
> (build/cythonized/sage/rings/integer.c:20556)
>sig_on()
>SystemError: calling remove_from_pari_stack() inside sig_on()
> **
> File "src/sage/rings/integer.pyx", line 6434, in 
> sage.rings.integer.Integer._shift_helper
> Failed example:
>try:
>print('Possible error output from gmp')
>1 << (2^60)
>except (MemoryError, OverflowError, RuntimeError):
>pass
>else:
>print("Failed to raise exception")
> Expected:
>Possible error output from gmp...
> Got:
>gmp: overflow in mpz type
>Possible error output from gmp
> **
> 
> 
> Le 20/10/2021 à 12:25, Dima Pasechnik a écrit :
>> mpir removal was not complete, as a result ./bootstrap etc may complain.
>> Fix is here:
>> https://trac.sagemath.org/ticket/32727
>> On Wed, Oct 20, 2021 at 12:07 AM Volker Braun  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
>>> 
>>> 056b8d4e7b (tag: 9.5.beta4, trac/develop) Updated SageMath version to
>>> 9.5.beta4
>>> e8ab458165 Trac #32707: flit_core: Update to 3.4.0; setuptools_scm: Update
>>> to 6.3.2
>>> 18abd75ff8 Trac #32698: Fix up builds without system python3 after #32442
>>> e866070bb9 Trac #32352: Efficient algorithm to compute products in the C'
>>> basis of an Iwahori-Hecke algebra
>>> ab2c01cf28 Trac #32328: Adding post_critical_set
>>> 91184aeb3f Trac #32314: passing a generator to gcd() fails
>>> dc4f1700bc Trac #32266: Enforce normalization in coxeter3-implemented
>>> Coxeter groups
>>> 17c789a5f7 Trac #32258: Adjustments for the 2-adic lseries of elliptic
>>> curves
>>> afa596f16a Trac #32200: Add developer manual section on integer return
>>> values
>>> 64dd2c46d4 Trac #32199: Conjugating Set Runtime Improvement
>>> daaec36f03 Trac #32155: Add is_linearly_independent to projective space
>>> over a ring
>>> 6b1bc6480c Trac #31994: Sigma invariants for P^N, N > 1
>>> 74f3bc75c8 Trac #30477: preparser: implicit multiplication conflicts with
>>> Python's complex literals
>>> 017d1dc75c Trac #17537: The geodetic closure of a graph
>>> 95908b0881 Trac #15219: numerical integral needs an operand for callable
>>> symbolic functions
>>> bf739637a9 Trac #32693: 1 internet failing doctest in
>>> src/sage/calculus/calculus.py
>>> cad17d0e34 Trac #32682: Replace ">> matrix, libs, interfaces, manifolds]
>>> ce1fd8d611 Trac #32675: Partially replace ">> 9a9a62a17e Trac #32646: Update package sqlite to 3.36.0
>>> e0baa96229 Trac #32612: sage.rings.abc.{Real,Complex}{Interval,Ball}Field;
>>> deprecate is_{Real,Complex}IntervalField
>>> 9cbde3ccad Trac #32672: src/setup.py: Don't cythonize everything in src/
>>> e4e87f2419 Trac #14657: set_embedding fails for multigraphs
>>> 913e577deb Trac #32673: src/setup.py: Do not need Cython for sdist or
>>> egg_info
>>> 297f60d39c Trac #32670: use itertools in abstract_tree
>>> 7bba5e0c90 Trac #32668: replace >> ba408efdab Trac #32666: Polyhedron_base.vertex_adjacency_matrix: Do not
>>> use face_lattice
>>> de6b6a1340 Trac #32663: more conversions for Bessel functions
>>> b93313c326 Trac #32662: more conversions for trig and hyperbolic functions
>>> 515cbeaf29 Trac 

Re: [sage-release] Sage 9.4.beta1 released

[François Bissey]

This is now https://trac.sagemath.org/ticket/31921

> On 7/06/2021, at 13:33, François Bissey  wrote:
> 
> Checking how the feature works I think there was a mistake in the addition to 
> sage/features/databases.py
> for knotinfo. It checks for a sage python module presence, which will always 
> be there since it is part of
> sage, when it should have checked for a static file, like for the other 
> databases.

-- 
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/F41BEA41-42A8-4E46-8D0E-D9973A63FC83%40gmail.com.

Re: [sage-release] Sage 9.4.beta1 released

[François Bissey]

Checking how the feature works I think there was a mistake in the addition to 
sage/features/databases.py
for knotinfo. It checks for a sage python module presence, which will always be 
there since it is part of
sage, when it should have checked for a static file, like for the other 
databases.

> On 7/06/2021, at 13:18, François Bissey  wrote:
> 
> I have trouble building the documentation in sage-on-gentoo because of #30352 
> which doesn’t seem to be
> implementing features properly. That error wouldn’t happen on vanilla sage 
> because the build is not done
> in a sandbox and the build system wouldn’t try to write a system location.
> 
> * python3_9: running distutils-r1_run_phase python_compile_all
> /var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/rings/padics/padic_base_leaves.py:1104:
>  DeprecationWarning: invalid escape sequence \Z
>  """
> /var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/rings/padics/padic_base_leaves.py:1139:
>  DeprecationWarning: invalid escape sequence \Q
>  """
> * ACCESS DENIED:  unlinkat: /usr/share/sage/knotinfo
> rm: cannot remove '/usr/share/sage/knotinfo': Permission denied
> * ACCESS DENIED:  mkdir:/usr/share/sage/knotinfo
> Traceback (most recent call last):
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
>  line 420, in demo_version
>self._num_knots =  load(num_knots_file)
>  File "sage/misc/persist.pyx", line 187, in sage.misc.persist.load 
> (/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/cythonized/sage/misc/persist.c:2807)
>with open(filename, 'rb') as fobj:
> FileNotFoundError: [Errno 2] No such file or directory: 
> '/usr/share/sage/knotinfo/num_knots.sobj'
> 
> During handling of the above exception, another exception occurred:
> 
> Traceback (most recent call last):
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/sage_docbuild/__main__.py",
>  line 1, in 
>from sage_docbuild import main
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/sage_docbuild/__init__.py",
>  line 57, in 
>import sage.all
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/all.py",
>  line 215, in 
>from sage.knots.all import *
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/knots/all.py",
>  line 6, in 
>if DatabaseKnotInfo().is_present():
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/features/__init__.py",
>  line 162, in is_present
>res = self._is_present()
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/features/__init__.py",
>  line 823, in _is_present
>importlib.import_module(self.name)
>  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
>return _bootstrap._gcd_import(name[level:], package, level)
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/knots/knotinfo.py",
>  line 239, in 
>from sage.databases.knotinfo_db import KnotInfoColumns, db
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
>  line 815, in 
>dc = db.columns()
>  File "sage/misc/cachefunc.pyx", line 2310, in 
> sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__ 
> (/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/cythonized/sage/misc/cachefunc.c:12918)
>self.cache = f(self._instance)
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
>  line 594, in columns
>column_dict = self.read_column_dict()
>  File "sage/misc/cachefunc.pyx", line 2310, in 
> sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__ 
> (/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/cythonized/sage/misc/cachefunc.c:12918)
>self.cache = f(self._instance)
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
>  line 617, in read_column_dict
>if self.demo_version():
>  File 
> "/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
>  line 422, in demo_version
>self.

Re: [sage-release] Sage 9.4.beta1 released

[François Bissey]

I have trouble building the documentation in sage-on-gentoo because of #30352 
which doesn’t seem to be
implementing features properly. That error wouldn’t happen on vanilla sage 
because the build is not done
in a sandbox and the build system wouldn’t try to write a system location.

* python3_9: running distutils-r1_run_phase python_compile_all
/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/rings/padics/padic_base_leaves.py:1104:
 DeprecationWarning: invalid escape sequence \Z
  """
/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/rings/padics/padic_base_leaves.py:1139:
 DeprecationWarning: invalid escape sequence \Q
  """
 * ACCESS DENIED:  unlinkat: /usr/share/sage/knotinfo
rm: cannot remove '/usr/share/sage/knotinfo': Permission denied
 * ACCESS DENIED:  mkdir:/usr/share/sage/knotinfo
Traceback (most recent call last):
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
 line 420, in demo_version
self._num_knots =  load(num_knots_file)
  File "sage/misc/persist.pyx", line 187, in sage.misc.persist.load 
(/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/cythonized/sage/misc/persist.c:2807)
with open(filename, 'rb') as fobj:
FileNotFoundError: [Errno 2] No such file or directory: 
'/usr/share/sage/knotinfo/num_knots.sobj'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/sage_docbuild/__main__.py",
 line 1, in 
from sage_docbuild import main
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/sage_docbuild/__init__.py",
 line 57, in 
import sage.all
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/all.py",
 line 215, in 
from sage.knots.all import *
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/knots/all.py",
 line 6, in 
if DatabaseKnotInfo().is_present():
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/features/__init__.py",
 line 162, in is_present
res = self._is_present()
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/features/__init__.py",
 line 823, in _is_present
importlib.import_module(self.name)
  File "/usr/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/knots/knotinfo.py",
 line 239, in 
from sage.databases.knotinfo_db import KnotInfoColumns, db
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
 line 815, in 
dc = db.columns()
  File "sage/misc/cachefunc.pyx", line 2310, in 
sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__ 
(/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/cythonized/sage/misc/cachefunc.c:12918)
self.cache = f(self._instance)
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
 line 594, in columns
column_dict = self.read_column_dict()
  File "sage/misc/cachefunc.pyx", line 2310, in 
sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__ 
(/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/cythonized/sage/misc/cachefunc.c:12918)
self.cache = f(self._instance)
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
 line 617, in read_column_dict
if self.demo_version():
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
 line 422, in demo_version
self.reset_filecache()
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/databases/knotinfo_db.py",
 line 391, in reset_filecache
sage_makedirs(sobj_path)
  File 
"/var/tmp/portage/sci-mathematics/sage-/work/sage-/src-python3_9/build/lib/sage/misc/misc.py",
 line 93, in sage_makedirs
os.makedirs(dirname)
  File "/usr/lib/python3.9/os.py", line 225, in makedirs
mkdir(name, mode)
PermissionError: [Errno 13] Permission denied: '/usr/share/sage/knotinfo’

Various bits of sage try to recreate share/knotinfo/num_knots.sobj which isn’t 
installed because I haven’t
packaged it yet. This shouldn’t be an issue since database_knotinfo is still 
optional.
The problem here is that it seems that _feature.is_present() is always true, 
including when it is called
at 
https://github.com/sagemath/sage/blob/develop/src/sage/databases/knotinfo_db.py#L416

I cannot find where it 

Re: [sage-release] Sage 9.3.rc5 released

[François Bissey]

> On 2/05/2021, at 06:57, Dima Pasechnik  wrote:
> 
> I'd rather try gcc 11 instead.

If you want. We already have an issue in compiling fplll
https://github.com/fplll/fplll/issues/462
and sage itself doesn’t compile because of some issue in lcalc
as far as I can see.
https://github.com/cschwan/sage-on-gentoo/issues/634

François

-- 
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/A7626DE4-B786-4EE6-9F16-14005C560DA2%40gmail.com.

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

[François Bissey]

Exactly that, thanks for adding me. I can reliably reproduce it.

> On 9/03/2021, at 09:01, Matthias Köppe  wrote:
> 
> See https://trac.sagemath.org/ticket/30945
> 
> On Monday, March 8, 2021 at 11:52:46 AM UTC-8 François Bissey wrote:
> I have been having a segfault in that file for a while between 9.3.beta7 and 
> 9.3.beta8 
> in sage-on-gentoo when running parallel testing. However the tests run all 
> fine on that 
> file when doing an individual run. There probably can be some kind of race 
> condition 
> when running in parallel. 
> 
> > On 8/03/2021, at 23:27, Thierry Dumont  wrote: 
> > 
> > 1 error: 
> > 
> > sage -t --long --warn-long 89.4 --random-seed=0 
> > src/sage/interfaces/singular.py 
> > Killed due to segmentation fault 
> 
> 
> -- 
> 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/f0a6f03c-cbf4-4a88-8929-8dd453c6c9e7n%40googlegroups.com.

-- 
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/D15EC57E-D116-4393-9240-4A9859C58B38%40gmail.com.

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

[François Bissey]

I have been having a segfault in that file for a while between 9.3.beta7 and 
9.3.beta8
in sage-on-gentoo when running parallel testing. However the tests run all fine 
on that
file when doing an individual run. There probably can be some kind of race 
condition 
when running in parallel.

> On 8/03/2021, at 23:27, Thierry Dumont  wrote:
> 
> 1 error:
> 
> sage -t --long --warn-long 89.4 --random-seed=0 
> src/sage/interfaces/singular.py
>Killed due to segmentation fault

-- 
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/8C42BFC2-3F95-42E3-BDE2-0E44842463ED%40gmail.com.

Re: [sage-release] Sage 9.3.beta3 released

[François Bissey]

It looks like you are missing sqlite3, not on the system or in sage.
You probably have the library but not the executable.

> On 7/12/2020, at 9:50 PM, Clemens Heuberger  wrote:
> 
> 
> I get (Linux Mint 19.3 Tricia):
> 
> $ LANG=C ./sage -t --long --random-seed=0 src/sage/tests/cmdline.py
> Running doctests with ID 2020-12-07-09-45-22-291831e7.
> Using --optional=build,ccache,debian,dochtml,memlimit,pip,sage,sage_spkg
> Doctesting 1 file.
> sage -t --long --warn-long 44.1 --random-seed=0 src/sage/tests/cmdline.py
> **
> File "src/sage/tests/cmdline.py", line 592, in 
> sage.tests.cmdline.test_executable
> Failed example:
>out.startswith("3.")
> Expected:
>True
> Got:
>False
> **
> File "src/sage/tests/cmdline.py", line 594, in 
> sage.tests.cmdline.test_executable
> Failed example:
>err
> Expected:
>''
> Got:
>'/local/cheuberg/local/sage-9.3.beta3/src/bin/sage: line 571: exec: 
> sqlite3: not found\n'
> **
> File "src/sage/tests/cmdline.py", line 596, in 
> sage.tests.cmdline.test_executable
> Failed example:
>ret
> Expected:
>0
> Got:
>127
> **
> 1 item had failures:
>   3 of 231 in sage.tests.cmdline.test_executable
>[230 tests, 3 failures, 26.02 s]
> --
> sage -t --long --warn-long 44.1 --random-seed=0 src/sage/tests/cmdline.py  # 
> 3 doctests failed
> --
> Total time for all tests: 26.1 seconds
>cpu time: 0.3 seconds
>cumulative wall time: 26.0 seconds
> 
> 
> 
> 
> Am 07.12.20 um 00:37 schrieb Volker Braun:
>> 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
>> ca088c9c93 (tag: 9.3.beta3, trac/develop) Updated SageMath version to 
>> 9.3.beta3
>> 3290413be6 Trac #30747: Deprecate sage.misc.package functions 
>> standard_packages, optional_packages, experimental_packages
>> d312143740 Trac #30580: sage_setup: Remove import-time dependency 
>> (`setup_requires`) on `pkgconfig`, `numpy`
>> 52b91c88ce Trac #31012: Modify RandomChordalGraph according a deprecation 
>> warning introduced in Python 3.9
>> 660cac43a2 Trac #30990: flake8 details in parent.pyx
>> 09971a9476 Trac #30986: add module tree_decomposition.pyx
>> a540625234 Trac #30976: incidence_structures.py tries to import 'warn' from 
>> the wrong module
>> 14e3c694a0 Trac #30975: Silence packaging 20.5 deprecation warnings
>> 5fadc42c3b Trac #30963: remove CombinatorialClass in graph_path.py
>> 3fb2f3eab9 Trac #30961: Fix valid input types for NumberField element 
>> constructor
>> e97b79ea1c Trac #30951: tox.ini, build/bin/write-dockerfile.sh: Simplify by 
>> using new options of "sage -package list"
>> 9502bb0cc1 Trac #30921: Fix verbose "epsilon" output in polynomial small 
>> roots
>> 313d0b7c47 Trac #30346: Exception for the unknot in Homfly-PT polynomial
>> 0229ac6fd5 Trac #27921: Script package for checking presence of system 
>> libxml2 (polymake and igraph prerequisite)
>> e3e45a122f Trac #30995: Repair setting of SAGE_NUM_THREADS during build
>> de62cc35da Trac #30903: Fix broken symlink to documentation in the Sage 
>> jupyter kernelspec
>> 4722b13a2b Trac #30891: Normaliz cone from precomputed data has lattice 
>> messed up
>> d40e7902c5 Trac #30579: Clean up sage_setup.library_order
>> c3d9bf77a6 Trac #30965: fix precision in Padé method of power series
>> 768bd5117a Trac #30960: Update/fix top-level makefile target 
>> fast-rebuild-clean (used in Docker build)
>> 169d6aeb7a Trac #30959: almost get rid of "_multiply_basis"
>> 409d545873 Trac #30954: Implement a proper equality check for polyhedron 
>> representation objects
>> 42a76a6037 Trac #30935: Fix IP is none error in doctests
>> 97edd4674e Trac #30929: GH Actions: Update macos test environments
>> 130d7d1199 Trac #30925: Multizeta does not copy its argument
>> f4909e1cb9 Trac #30915: Three.js: Upgrade to r122
>> 66c1a87a12 Trac #30895: Developers' guide: Update "Packaging Third-Party 
>> Code" regarding upstream_url
>> d7b71743c2 Trac #30850: No Future
>> b4c0f6d0c3 Trac #30624: Improve wording and formatting of configure's 
>> recommendation message
>> e7369840f0 Trac #22731: Replace "$SAGE_LOCAL/bin" by more specific variables 
>> to make Sage easier to package, use in venvs
>> 17132a6832 Trac #9407: fixed fields for dirichlet characters and conductors 
>> and dirichlet characters for abelian fields
>> 2e4c869c9f Trac #30958: Remove C99 syntax in 
>> data_structures/bitset_intrinsics.h
>> f844baa06b Trac #30928: Backslash line continuation broken when defining a 
>> callable symbolic 

Re: [sage-release] Sage 9.2.beta14 released

[François Bissey]

This is https://trac.sagemath.org/ticket/30675 as I mentioned to several people 
I am surprised
the fact this was needed was not picked up by the bots. Which version of gcc 
are you using.

> On 1/10/2020, at 10:13 PM, Emmanuel Charpentier 
>  wrote:
> 
> Upgrading from 9.2.beta13 failed : I had successfully installed the optional 
> jupyterlab, and now make insists on installing jupyterlab_widgets2.0.0, which 
> fails as follows :
> 
> cd ../.. && sage-logger -p './sage --docbuild --no-pdf-links all html ' 
> logs/dochtml.log
> [dochtml] Traceback (most recent call last):
> [dochtml]   File "/usr/lib/python3.8/runpy.py", line 185, in 
> _run_module_as_main
> [dochtml] mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
> [dochtml]   File "/usr/lib/python3.8/runpy.py", line 144, in 
> _get_module_details
> [dochtml] return _get_module_details(pkg_main_name, error)
> [dochtml]   File "/usr/lib/python3.8/runpy.py", line 111, in 
> _get_module_details
> [dochtml] __import__(pkg_name)
> [dochtml]   File 
> "/usr/local/sage-9/local/lib/python3.8/site-packages/sage_setup/docbuild/__init__.py",
>  line 58, in 
> [dochtml] import sage.all
> [dochtml]   File 
> "/usr/local/sage-9/local/lib/python3.8/site-packages/sage/all.py", line 129, 
> in 
> [dochtml] from sage.data_structures.all import *
> [dochtml]   File 
> "/usr/local/sage-9/local/lib/python3.8/site-packages/sage/data_structures/all.py",
>  line 3, in 
> [dochtml] from .bitset import Bitset, FrozenBitset
> [dochtml] ImportError: 
> /usr/local/sage-9/local/lib/python3.8/site-packages/sage/data_structures/bitset.cpython-38-x86_64-linux-gnu.so:
>  undefined symbol: _bitset_issubset
> make[3]: *** [Makefile:1887 : doc-html] Erreur 1
> 
> Attempts to uninstall jupyterlab_widgets and jupyterlab, both via 
> sage-spkg-uninstall and sage -pip uninstall... failed : makereinstalls them.
> 
> Being stuck, I’m trying to rebuild from scratch (i. e. aftrer mace distclean. 
> Stay tuned…
> 
> HTH,
> 
> 
> 
> Le jeudi 1 octobre 2020 à 01:22:01 UTC+2, Volker Braun a écrit :
> 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 
> 
> Again, if there is anything that should be merged in this beta cycle then a 
> positively-reviewed patch has to materialize real soon ;-)
> 
> 1da6df404d (tag: 9.2.beta14) Updated SageMath version to 9.2.beta14
> be1a62b3bc Trac #30671: Random failure in src/sage/interfaces/psage.py
> ed7c4a3ee0 Trac #30605: improve cone containment tests
> ad0f8e0a1f Trac #30601: Move bitset.pxi to bitset_base.pxd
> 89bf834ab3 Trac #30597: Define a sparse bitset structure
> c539c2870a Trac #30663: tox.ini: Docker on Mac now needs $HOME too
> 112d9daff1 Trac #30658: conda-forge-ubuntu-standard: Pillow fails to install 
> (follow up)
> 0ef7e3ece8 Trac #30631: fix R on macOS xcode 12
> 6576814c37 Trac #30603: Upgrade readline to 8.0
> aa0a6d7b5f Trac #30546: python3 spkg-configure: Only search for "python3", 
> implement "configure --with-python=/PATH/TO/PYTHON"
> 6969c604ad Trac #30664: Fixup for "Add quiet mode for bootstrap"
> ebf4d9cf63 Trac #30662: Update conda package information, and fix building 
> Sage on conda
> cbd8e5db72 Trac #29061: Upgrade to symmetrica-3.0.1
> 99ab61da02 Trac #30596: Outsource functions in bitset.pxi that can be 
> optimized by intrinsics
> 97802f668d Trac #30595: Remove deprecated sage.libs.ppl
> 9ed2f32d19 Trac #30585: Typo ticket: homogenous -> homogeneous
> 9c205e9694 Trac #30577: remove test file for python3 syntax
> 0b841a75e6 Trac #30575: add maple conversion for hypergeometric functions
> de8e68e534 Trac #30572: Remove indirect typecasts when calling bitset.pxi
> dbd108c10b Trac #30567: remove deprecated things in words
> b4715d1b68 Trac #30563: Use configuration variable MAXIMA instead of 
> hardcoding "maxima"
> 865f3ca815 Trac #30562: Gap downloads from wrong upstream directory
> cd88566df0 Trac #30548: mention that sometimes it is wolfram, not math for 
> Mathematica script
> 7169ec9867 Trac #30547: full flake8 for skew_tableau.py, as an experiment
> 95712fc6ad Trac #30544: spkg-configure, system package info for tox
> 2413f7b665 Trac #30523: polynomial_element.pyx: roots: SR: Fix if determinant 
> is not real
> 28b594bb6e Trac #30486: Prepare doctests for Arb 2.18
> 43089d428d Trac #30337: Graphs: obtain distance-regular graphs from 
> generalised quadrangles
> 82a9e2d091 Trac #29500: Install all Python packages via pip wheel (or 
> setup.py bdist_wheel), store wheels in $SAGE_LOCAL/var/lib/sage/wheels
> 85906ba097 Trac #25119: Fail to integrate sqrt(x^2)/x
> 5bf821488c Trac #15223: Let the `TestSuite` test that the construction of a 
> parent returns the parent
> 501019f5b5 Trac #30610: Fix openblas to build with Xcode 12
> 19be84362c Trac #30576: Python 3.6: Fix locale/encoding issues in docbuild, 
> then re-enable Python 3.6
> af71febd64 Trac 

Re: [sage-release] Sage 9.2.beta14 released

[François Bissey]

This has been around for ages. In fact for as long as nauty has been in sage.
I remember spotting it for the first time in dmesg several years ago.
Because it is mostly silent very little effort has put into fixing that so far,
at least that I know of.

> On 1/10/2020, at 9:20 PM, Eric Gourgoulhon  wrote:
> 
> 1/ Title: nauty-gentourng crashed with SIGSEGV in __libc_start_main()
>  nauty-gentourng is from the Ubuntu package nauty 2.6r10+ds-1ubuntu1
> 

François

-- 
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/F7659316-C046-4FCB-97DD-DF89EEA32C5B%40gmail.com.

Re: [sage-release] Sage 9.2.beta6 released

[François Bissey]

The important bits from that last log
[198/517] creating 
build/temp.macosx-10.14-x86_64-3.7/build/cythonized/sage/libs/arb
clang -Wno-unused-result -Wsign-compare -Wunreachable-code -fno-common -dynamic 
-DNDEBUG -g -fwrapv -O3 -Wall -isysroot 
/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk 
-I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/usr/include 
-I/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk/System/Library/Frameworks/Tk.framework/Versions/8.5/Headers
 -I./sage/libs/arb -I./sage/libs/flint -I./sage/libs/ntl -I./sage/cpython 
-I/opt/s/sage92b6/src -I/opt/s/sage92b6/src/sage/ext 
-I/usr/local/Cellar/python@3.7/3.7.8_1/Frameworks/Python.framework/Versions/3.7/include/python3.7m
 -I/opt/s/sage92b6/local/lib/python3.7/site-packages/numpy/core/include 
-Ibuild/cythonized -I/usr/local/include -I/usr/local/opt/openssl@1.1/include 
-I/usr/local/opt/sqlite/include -I/opt/s/sage92b6/local/include 
-I/usr/local/Cellar/python@3.7/3.7.8_1/Frameworks/Python.framework/Versions/3.7/include/python3.7m
 -c build/cythonized/sage/libs/arb/arith.c -o 
build/temp.macosx-10.14-x86_64-3.7/build/cythonized/sage/libs/arb/arith.o 
-fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c99
In file included from build/cythonized/sage/libs/arb/arith.c:656:
In file included from build/cythonized/sage/libs/arb/arb_wrap.h:14:
In file included from /opt/s/sage92b6/local/include/acb.h:22:
In file included from /opt/s/sage92b6/local/include/arf.h:27:
In file included from /opt/s/sage92b6/local/include/fmpr.h:26:
/opt/s/sage92b6/local/include/fmpz_extras.h:47:1: error: redefinition of 
'fmpz_add_si'
fmpz_add_si(fmpz_t z, const fmpz_t x, slong y)
^
/usr/local/include/flint/fmpz.h:479:18: note: previous definition is here
FMPZ_INLINE void fmpz_add_si(fmpz_t f, const fmpz_t g, slong x)
 ^
In file included from build/cythonized/sage/libs/arb/arith.c:656:
In file included from build/cythonized/sage/libs/arb/arb_wrap.h:14:
In file included from /opt/s/sage92b6/local/include/acb.h:22:
In file included from /opt/s/sage92b6/local/include/arf.h:27:
In file included from /opt/s/sage92b6/local/include/fmpr.h:26:
/opt/s/sage92b6/local/include/fmpz_extras.h:56:1: error: redefinition of 
'fmpz_sub_si'
fmpz_sub_si(fmpz_t z, const fmpz_t x, slong y)
^
/usr/local/include/flint/fmpz.h:487:18: note: previous definition is here
FMPZ_INLINE void fmpz_sub_si(fmpz_t f, const fmpz_t g, slong x)
 ^
2 errors generated.

I would be easier to spot if you were building sagely at j1.

> On 29/07/2020, at 8:28 PM, Samuel Lelievre  wrote:
> 
> 2020-07-26 20:46:10 UTC, Matthias Köppe:
> >
> > From your log:
> >
> > [  4/517] clang -Wno-unused-result [...]
> > -I/opt/s/sage92b6/local/include/singular
> > -I/opt/s/sage92b6/local/include/ -std=c++11
> > In file included from [...]/letterplace_ideal.cpp:675:
> > /usr/local/include/singular/Singular/libsingular.h:15:10:
> > fatal error: 'polys/shiftop.h' file not found
> > #include "polys/shiftop.h"
> > ^
> > In file included from [...]/free_algebra_letterplace.cpp:675:
> > /usr/local/include/singular/Singular/libsingular.h:15:10:
> > fatal error: 'polys/shiftop.h' file not found
> > #include "polys/shiftop.h"
> >  ^
> > In file included from [...]/free_algebra_element_letterplace.cpp:675:
> > /usr/local/include/singular/Singular/libsingular.h:15:10:
> > fatal error: 'polys/shiftop.h' file not found
> > #include "polys/shiftop.h"
> >  ^
> > [...]/finite_dimensional_algebra_element.c:11104:18:
> > warning: unused function
> > '__pyx_pw_4sage_9structure_7element_1parent' [-Wunused-function]
> > static PyObject
> > *__pyx_pw_4sage_9structure_7element_1parent(PyObject *__pyx_self,
> > PyObject *__pyx_v_x) {
> >
> > This appears to be a conflict with a version of Singular
> > that is installed in /usr/local
> 
> 
> 2020-07-26 22:01:03 UTC, Matthias Köppe:
> >
> > This will be addressed in
> > https://trac.sagemath.org/ticket/30227
> 
> 
> 2020-07-28 04:13:48 UTC, Matthias Köppe:
> >
> > Fixed in #30227, please test
> 
> 
> Dear Matthias, thanks for investigating and for the ticket.
> 
> I uninstalled Homebrew's Singular: new failure on sagelib.
> 
> https://www.math.u-psud.fr/~lelievre/sagelogs/slel-sage-9-2-b6-mac-brew-2020-07-27-fail.zip
> 
> I then tried applying ticket 30227, new failure on sagelib.
> 
> https://www.math.u-psud.fr/~lelievre/sagelogs/
> slel-sage-9-2-b6-mac-brew-2020-07-28.zip
> 
> 
> -- 
> 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/dbc12617-0a8f-4104-a016-a24a4e64bc50o%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To 

Re: [sage-release] Sage 9.1.beta1 released

[François Bissey]

> On 23/01/2020, at 9:47 PM, Timo Kaufmann  wrote:
> 
> Am Mittwoch, 22. Januar 2020 19:04:06 UTC+1 schrieb Steven Trogdon:
> Your build may be picking up on the wrong version of pygments. Vanilla Sage 
> uses pygments-2.3.1.p0.
> 
> ./sage -f pygments
> 
> may fix the issue. On my sage-on-gentoo build, which uses a system pygments, 
> I see the same lex literal_block as "python" Warning with pygments-2.5.2. But 
> pygments-2.4.2 is fine.
> 
> I have fixed the pygments issue for nix here: 
> https://github.com/NixOS/nixpkgs/pull/78348
> 
> Only the sphinx patch is strictly necessary to fix the docbuild. Since it 
> doesn't look like sphinx has a python2 maintenance branch, you'll have to 
> patch it if you want this fixed.

Is this backwards compatible with older versions of pygments?
i.e. there won’t be any issues if pygments-2.3.x is used in conjunction with 
patched sphinx-1.8?

François

-- 
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/BE06CF92-AAD7-4C87-AA9E-B4F302FCE89A%40gmail.com.

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

[François Bissey]

Yes. sagenb is no a real optional package even with python2. We overlooked
the test suite when we made some test depending on it just “# py2”.
That was in https://trac.sagemath.org/ticket/28805.
We probably really should have introduced `# sagenb` in insight.
But honestly I don’t care that much about python2 anymore.
In 30 days it will be best efforts at best for python2.

> On 2/12/2019, at 6:50 PM, John H Palmieri  wrote:
> 
> In particular, SageNB is not built with Python 2, but the doctester thinks it 
> should be:
> 

-- 
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/0E399888-BECC-4272-80DE-A3FCB6777940%40gmail.com.

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

[François Bissey]

https://trac.sagemath.org/ticket/28271 broke the building of the pdf doc.
See https://github.com/cschwan/sage-on-gentoo/issues/549
I’ll have a follow up at some point in the next 24hours. The ticket introduced
a unicode “minus” sign at
https://github.com/sagemath/sage/blob/develop/src/sage/graphs/traversals.pyx#L1284


> On 3/09/2019, at 5:53 PM, Henri Girard  wrote:
> 
> Ubuntu 19.10 (+1) beta, AMD 8x 64 bits 16 Go RAM
> 
> Le 26/08/2019 à 08:18, Henri Girard a écrit :
>> Ubuntu 19.10 (+1) beta, AMD 8x 64 bits 16 Go RAM
>> 
>> Compilation ok works fine (from beta 7 to 8)
>> 
>> Le 26/08/2019 à 00:37, Volker Braun a écrit :
>>> 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 
>>> 
>>> It is nearing the end of the 8.9 merge window, so if you want something 
>>> merged then this is your last chance.
>>> 
>>> 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 ;-)
>>> 
>>> 
>>> 4583b4056e (tag: 8.9.beta8, trac/develop) Updated SageMath version to 
>>> 8.9.beta8
>>> 6565e63ee9 Trac #28373: new big bag of typos
>>> 0052843038 Trac #28297: Small optimizations to arithmetic in number fields 
>>> of degree > 2
>>> a9f414a6f8 Trac #28057: Adding precision in computing the generators of the 
>>> period lattice of an elliptic curve.
>>> 40c5efa0c8 Trac #28365: Use something instead of time() to ensure Manifold 
>>> uniqueness in tests
>>> bd8504c9e8 Trac #28335: Cythonize Yen_k_shortest_simple_paths and 
>>> feng_k_shortest_simple_paths
>>> c1d5763dc3 Trac #28147: Remove _derivative from Polynomial_template
>>> ef1517da96 Trac #28056: Sboxes Maintenance
>>> 05bd7671a2 Trac #26098: Implement L-functions using the PARI library
>>> c050128f4a Trac #20755: Bug in solve due to a bug in 
>>> symbolic_expression_from_maxima_string
>>> 2a4bfffc48 Trac #28353: var() with single-element list/tuple crashes with 
>>> unhandled TypeError
>>> 0a45dfc784 Trac #28371: py3: errors with optional package CSDP
>>> 5ab84a6fb3 Trac #28369: Improve progress report in gitlab-ci
>>> a8599952c3 Trac #28367: MR30: Update README.md: -py3 suffix
>>> 56f7684a57 Trac #28346: Use dots instead of precision in polynomial_element
>>> 8edd3f2797 Trac #28201: small cleanup of databases/cremona
>>> 1b7d07b6cc Trac #27573: PRESENT Block Cipher
>>> 5f22d242b6 Trac #28321: py3: rationals can not be initialized from a pair 
>>> of big Python ints
>>> b972100c84 Trac #24494: Deprecate set_planar_positions()
>>> 42eb5103aa Trac #28364: MR29: Update faq-usage.rst
>>> 047992b031 Trac #28361: Implement parameter external_face of layout_planar()
>>> ae73a81a59 Trac #28343: Three.js: Support basic mesh plots
>>> 7e623eddb1 Trac #28116: Cython 0.29.12
>>> 7508513e65 Trac #28108: Py3: ValueError in graph_generators doctests with 
>>> plantri optional package
>>> a98c0ab16f Trac #28347: Add as_integer_ratio() for Integer, Rational, 
>>> RealNumber, RealDoubleElement
>>> 431187f776 Trac #28344: Fix some issues with submanifolds and improve their 
>>> documentation
>>> 7c0d719021 Trac #28342: spkg-configure.m4 for m4ri, m4rie, givaro
>>> 5d6ac68f68 Trac #28228: Semistandard super tableau and standard super 
>>> tableau for superRSK
>>> 7d561d89cf (tag: 8.9.beta7) Updated SageMath version to 8.9.beta7
>>> 
>>> -- 
>>> 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/b1182f0f-112b-4f14-b6b8-6eb94f02e1dc%40googlegroups.com.
> 
> -- 
> 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/95a32695-c787-9ee5-c19b-3baa1d0d9f9d%40gmail.com.

-- 
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/1D9C0737-C450-4CA1-9EA1-0D92D9795D12%40gmail.com.

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

[François Bissey]

Thanks, between that and the source code I know understand what is happening.
The configure script never checked that the flags are supported by the compiler.
Instead it runs some assembly code to identify the cpu ID and infer the 
capabilities
from that information. Actual code using the extensions in question is not 
tested,
and therefore, neither are the flags.

The test code has the following comment

/* find supported instruction set
return value:
0   = 80386 instruction set
1  or above = SSE (XMM) supported by CPU (not testing for O.S. support)
2  or above = SSE2
3  or above = SSE3
4  or above = Supplementary SSE3 (SSSE3)
5  or above = SSE4.1
6  or above = SSE4.2
7  or above = AVX supported by CPU and operating system
8  or above = AVX2
9  or above = AVX512F
10 or above = AVX512VL
11 or above = AVX512BW, AVX512DQ
*/

For your cpu, with gcc-4.8.5 the program returned 12.

> On 6/08/2019, at 5:49 PM, Markus Wageringel  
> wrote:
> 
> 

-- 
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/431F5452-7767-4A41-BF69-499B82E083C8%40gmail.com.

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

[François Bissey]

I meant the config.log of fflas-ffpack not sage’s one.

> On 6/08/2019, at 5:31 PM, Markus Wageringel  
> wrote:
> 
> 

-- 
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/1F5604A9-7841-47A0-816D-135EB0949E9C%40gmail.com.

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

[François Bissey]

Yes I would like to see it. I have looked at what fflas-ffpack does to detect
the stuff but I want a practical output for that case.

> On 6/08/2019, at 10:26 AM, Markus Wageringel  
> wrote:
> 
> It would have been nice to have the config log from when you had the failure.
> 
> Would you still like to have it? I could reproduce it I suppose. 
> 
> -- 
> 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/2804df41-26e7-4820-93e6-35e7cb031bf5%40googlegroups.com.

-- 
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/FF1A7B98-15E2-4EB3-9F22-1848CC66317B%40gmail.com.

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

[François Bissey]

After inspection of configure they are all brand new options I didn’t know 
anything
about. That would have been —disable-{avx512f,avx512dq,avx512vl}. I am still 
shocked 
it enabled them without your compiler supporting it. The logic must be flawed.
In any case we need to add those to the list of disabled options in fat binary 
builds.
It would have been nice to have the config log from when you had the failure.

François 

> On 6/08/2019, at 9:49 AM, Markus Wageringel  
> wrote:
> 
> Thank you for the quick replies. It is the system's default compiler – no 
> idea why it is so old.
> 
> export FFLAS_FFPACK_CONFIGURE="-disable-fma -disable-fma4 -disable-avx 
> -disable-avx2"
> 
> Hm, that did not work, giving still the same error for fflas-ffpack. I assume 
> I would have to disable AVX 512 as well?
> 
> Though, I guess it is better to have it than not. Using gcc 8.3.1 from 
> devtoolset-8 works successfully.
> 
> 
> -- 
> 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/28c5affc-5613-4a0c-8d92-0daf385a982b%40googlegroups.com.

-- 
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/A3E13D64-3F62-451C-BB35-06B980C126B7%40gmail.com.

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

[François Bissey]

But fflas-ffpack detection routines pick it up when they shouldn’t. Technically 
I see that 
as an upstream inbox team problem since they share their detection routines 
over the entire 
givaro/fflas-ffpack/linbox stack.
You may want to try 
export FFLAS_FFPACK_CONFIGURE=“—disable-fma —disable-fma4 —disable-avx 
—disable-avx2”
and then run make again. But you may have to do a similar stop when building 
linbox.

> On 6/08/2019, at 8:22 AM, Dima Pasechnik  wrote:
> 
> You're using gcc version 4.8.5, released in 2015. I guess AVX 512
> didn't exist yet.
> 
> On Mon, Aug 5, 2019 at 11:17 PM Markus Wageringel
>  wrote:
>> 
>> The package fflas_ffpack-2.4.3 added in #26932 fails to compile for me on 
>> CentOS 7.6.1810, due to several errors of this form:
>> 
>> g++: error: unrecognized command line option '-mavx512f'
>> g++: error: unrecognized command line option '-mavx512vl'
>> g++: error: unrecognized command line option '-mavx512dq'
>> 
>> The log file is attached.
>> 
>> --
>> 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/ec04cd37-c65e-411f-886f-5e58a45a89a4%40googlegroups.com.
> 
> -- 
> 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/CAAWYfq3dycsV39S-WW%3DSHXi8nYfWSm7Lv_me9ACoPKBp2Pboxg%40mail.gmail.com.

-- 
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/D9A37166-A79E-4246-88FE-0EE62C7124B3%40gmail.com.

Re: [sage-release] Sage 8..8 released

[François Bissey]

That’s because you changed branch. There is no difference between
the develop branch at 8.8.rc3 and master at 8.8. But when
you switch branch to master you get all the changes between
master at 8.7 and master at 8.8.
Basically to get master at 8.8 you merge develop at 8.8.rc3 into
master at 8.7.

François

> On 27/06/2019, at 8:08 PM, dimp...@gmail.com wrote:
> 
> On Thu, Jun 27, 2019 at 09:10:44AM +0200, henri.gir...@gmail.com wrote:
>> For info ?
>> 
>> As I was in develop I changed to master and make build (I can't build 
>> doc) it says 1400 updates ?
>> 
>> You said no change in 8.8.rc3, why all these then ?
> 
> probably you used a mirror that was not updated yet?
> 
>> 
>> Regards
>> 
>> Henri
>> 
>> 
>> Le 26/06/2019 à 23:19, Volker Braun a écrit :
>>> The "master" git branch has been updated to Sage-8.8. 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
>>> 
>>> There was no change over 8.8.rc3
>>> -- 
>>> 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.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/sage-release/3045b6ac-5941-4979-9f7b-6e03be4a58f6%40googlegroups.com
>>>  
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>> 
>> -- 
>> 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.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/sage-release/1cdbc697-ea0b-05ba-6f2b-f3faec6fc2b7%40gmail.com.
>> For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/20190627080854.GA22505%40hilbert.lan.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/4CC883A2-911A-4A11-8598-EA329956987E%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.rc3 released

[François Bissey]

Print no. But I have users of sage-on-gentoo who have told me that they find it 
handy
and consult it from their phone and stuff.

> On 27/06/2019, at 5:03 AM, Volker Braun  wrote:
> 
> IMHO the main point of the pdf docs is to check that the LaTeX math is valid, 
> nobody is going to download and print the pdf docs (i hope). So no blocker

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/D0FF5136-D8B2-45A5-969D-A6CE7D99A43F%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.rc3 released

[François Bissey]

Unless we are ready to ship 8.8 with broken pdf docs I created
https://trac.sagemath.org/ticket/28059
and marked it as a blocker. Feel free to downgrade the severity
if you think it is appropriate.

François

> On 24/06/2019, at 11:52 PM, Eric Gourgoulhon  wrote:
> 
> On Ubuntu 18.04 running on bi-Xeon E5-2623 (8 cores) + 16 GB RAM:
> 
> - python2: 
> 
>   - incremental build (from 8.8.rc2, with -j16) completed, with Sphinx 
> complaining during the doc build:
>  formatargspec() is now deprecated.  Please use 
> sphinx.util.inspect.Signature instead
> 
>   - all tests from ptestlong passed
> 
> - python3: 
> 
>   - incremental build (from 8.8.rc2, with -j16) completed, with the same 
> Sphinx deprecation warning as with python 2. 
> 
>   - tests from ptest-python3 passed, except for 2 doctests 
> in src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py:
> 
> sage -t --long --warn-long 50.3 
> src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py
> **
> File "src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py", 
> line 1372, in 
> sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function
> Failed example:
> H = HyperellipticCurve(t^5 + a*t)
> Exception raised:
> Traceback (most recent call last):
>   File 
> "/home/eric/sage/py3/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  line 681, in _run
> self.compile_and_execute(example, compiler, test.globs)
>   File 
> "/home/eric/sage/py3/local/lib/python3.7/site-packages/sage/doctest/forker.py",
>  line 1105, in compile_and_execute
> exec(compiled, globs)
>   File " sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function[7]>",
>  line 1, in 
> H = HyperellipticCurve(t**Integer(5) + a*t)
>   File 
> "/home/eric/sage/py3/local/lib/python3.7/site-packages/sage/schemes/hyperelliptic_curves/constructor.py",
>  line 220, in HyperellipticCurve
> raise ValueError("In characteristic 2, argument h (= %s) must be 
> non-zero."%h)
> ValueError: In characteristic 2, argument h (= 0) must be non-zero.
> **
> File "src/sage/schemes/hyperelliptic_curves/hyperelliptic_finite_field.py", 
> line 1373, in 
> sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function
> Failed example:
> H.zeta_function()
> Expected:
> (81*x^4 + 72*x^3 + 32*x^2 + 8*x + 1)/(9*x^2 - 10*x + 1)
> Got:
> (16*x^4 + 8*x^3 + x^2 + 2*x + 1)/(4*x^2 - 5*x + 1)
> **
> 1 item had failures:
>2 of  16 in 
> sage.schemes.hyperelliptic_curves.hyperelliptic_finite_field.HyperellipticCurve_finite_field.zeta_function
> [373 tests, 2 failures, 59.91 s]
> 
> The 2 doctests are passed when run standalone. 
> 
> NB: these are the same errors as with 8.8.rc2 and, IIRC, as with 8.8.rc1. So 
> it seems the errors are reproducible when doctesting with "make 
> ptest-python3". They are not directly related to parallel doctesting though, 
> since 
> 
> ./sage -tp --long --warn-long 50.3 src/sage/schemes/
> 
> yields
> 
> Running doctests with ID 2019-06-24-13-52-38-4df2b045.
> Git branch: develop
> Using --optional=build,dochtml,memlimit,mpir,python2,sage
> Sorting sources by runtime so that slower doctests are run first
> Doctesting 144 files using 8 threads.
> ...
> --
> All tests passed!
> --
> Total time for all tests: 139.5 seconds
> cpu time: 930.2 seconds
> cumulative wall time: 1003.4 seconds
> 
> Eric. 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/aebd284b-ff4a-44a1-8a15-1f7e4816bba1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/96014E89-33AD-43F7-A9D2-0CB9392895C7%40gmail.com.
For more 

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

[François Bissey]

You shouldn't need two copies. It is more like a dependency issue.
sage/matrix/matrix_rational_dense.so (and may be other) should be
re-built during the incremental build but isn’t/aren't. 
Touching the relevant .pyx file and using `./sage -b` should fix it.

> On 20/06/2019, at 12:48 PM, Paul Masson  wrote:
> 
> In an incremental build from beta 7 on macOX Mojave (10.14.5), I'm still 
> encountering a crash-inducing issue with openblas. The relevant part of the 
> crash log is
> 
> ImportError: 
> dlopen(/Users/Masson/Downloads/GitHub/sage/local/lib/python2.7/site-packages/sage/matrix/matrix_rational_dense.so,
>  2): Library not loaded: 
> /Users/Masson/Downloads/GitHub/sage/local/lib/libopenblas_haswellp-r0.3.5.dylib
>   Referenced from: 
> /Users/Masson/Downloads/GitHub/sage/local/lib/python2.7/site-packages/sage/matrix/matrix_rational_dense.so
>   Reason: image not found
> 
> I can work around it by creating a second copy of libopenblas and changing 
> its last digit to 5, but why would I need two copies of the library?
> 
> On Wednesday, June 19, 2019 at 2:54:06 PM UTC-7, Volker Braun 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 
> 
> 
> 8084b69595 (tag: 8.8.rc2, trac/develop) Updated SageMath version to 8.8.rc2
> ab2ee449bb Trac #27961: openblas 0.3.6 vs. OS X on some processors
> 57e1ba71f9 Trac #27950: Replace source activate by conda activate in conda 
> install guide
> 8df690fd2a (tag: 8.8.rc1) Updated SageMath version to 8.8.rc1
> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/d04fa013-2143-4da5-a1c2-9036d1943fa4%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/70759CA1-44D0-409F-90F4-A2A4D95EEFED%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.8.rc0 released

[François Bissey]

As I suspect in the ticket (in which I also left a comment) the fact
that the version 0.3.5 instead of 0.3.6 is mentioned in the trace make
me think this is an incremental build problem.
Something that should have been rebuilt didn’t and that may be because of
the way you performed the incremental build.

François

> On 10/06/2019, at 7:46 AM, John H Palmieri  wrote:
> 
> 
> 
> On Sunday, June 9, 2019 at 12:37:52 PM UTC-7, John H Palmieri wrote:
> I think the problem is with the openblas upgrade, 
> https://trac.sagemath.org/ticket/27847.
> 
> I opened https://trac.sagemath.org/ticket/27961 (not that I know how to fix 
> it...)
> 
> 
> 
> 
> On Sunday, June 9, 2019 at 10:19:27 AM UTC-7, David Coudert wrote:
> crash with both python 2 and python 3 on osX. I attach the crash report with 
> python 3.
> 
> Any help is more than welcome.
> 
> David.
> 
> =
> 
> confetti:sage dcoudert$ ./sage
> ┌┐
> │ SageMath version 8.8.rc0, Release Date: 2019-06-09 │
> │ Using Python 3.7.3. Type "help()" for help.│
> └┘
> ┏┓
> ┃ Warning: this is a prerelease version, and it may be unstable. ┃
> ┗┛
> 
> **
> 
> Oops, Sage crashed. We do our best to make it stable, but...
> 
> A crash report was automatically generated with the following information:
>   - A verbatim copy of the crash traceback.
>   - A copy of your input history during this session.
>   - Data on your current Sage configuration.
> 
> It was left in the file named:
>   '/Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt'
> If you can email this file to the developers, the information in it will help
> them in understanding and correcting the problem.
> 
> You can mail it to: sage-support at sage-s...@googlegroups.com
> with the subject 'Sage Crash Report'.
> 
> If you want to do it now, the following command will work (under Unix):
> mail -s 'Sage Crash Report' sage-s...@googlegroups.com < 
> /Users/dcoudert/.sage/ipython-5.0.0/Sage_crash_report.txt
> 
> In your email, please also include information about:
> - The operating system under which the crash happened: Linux, macOS, Windows,
>   other, and which exact version (for example: Ubuntu 16.04.3, macOS 10.13.2,
>   Windows 10 Pro), and whether it is 32-bit or 64-bit;
> - How Sage was installed: using pip or conda, from GitHub, as part of
>   a Docker container, or other, providing more detail if possible;
> - How to reproduce the crash: what exact sequence of instructions can one
>   input to get the same crash? Ideally, find a minimal yet complete sequence
>   of instructions that yields the crash.
> 
> To ensure accurate tracking of this issue, please file a report about it at:
> http://trac.sagemath.org
> 
> Hit  to quit (your terminal may close):
> c
> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/6cab4410-4a6b-49b9-8346-19e3f0cb3f08%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/89F031E4-6DA4-47DE-BB5F-5A0039AE1569%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.beta6 released

[François Bissey]

There is an actual option for that in the test. But in the current state it has
no effect when the expect interface to gap is selected since ~/.gap is already
ignored.

> On 29/05/2019, at 1:20 AM, E. Madison Bray  wrote:
> 
> The tests should make sure nothing in ~/.gap is ever loaded if at all 
> possible (e.g. update the GAP interfaces to add an option to disable use of 
> ~/.gap` when running the tests, for example)
> 
> On Sat, May 25, 2019, 03:22 François Bissey  wrote:
> We’ll want some kind of follow up. The test will fail if you have something 
> in ~/.gap.
> Not just on sage-on-gentoo.
> The question is whether the pexpect interface should continue starting `gap` 
> with the
> “-r” option or not.
> 
> François
> 
> > On 25/05/2019, at 12:17 PM, Steven Trogdon  wrote:
> > 
> > Found this also first on s-o-g. So should ~/.gap be empty or is a follow-up 
> > to https://trac.sagemath.org/ticket/27681 necessary?
> > On Friday, May 24, 2019 at 7:04:53 PM UTC-5, François Bissey wrote:
> > You have something in ~/.gap. See 
> > https://trac.sagemath.org/ticket/27681#comment:30 
> > 
> > > On 25/05/2019, at 12:02 PM, Steven Trogdon  wrote: 
> > > 
> > > As far as I know this failure started with this beta. 
> > > 
> > > sage -t --long src/sage/tests/gap_packages.py 
> > > ** 
> > > File "src/sage/tests/gap_packages.py", line 137, in 
> > > sage.tests.gap_packages.all_installed_packages 
> > > Failed example: 
> > > all_installed_packages() == all_installed_packages(gap=gap) 
> > > Expected: 
> > > True 
> > > Got: 
> > > False 
> > > ** 
> > > 1 item had failures: 
> > >1 of   4 in sage.tests.gap_packages.all_installed_packages 
> > > [10 tests, 1 failure, 1.04 s] 
> > > 
> > > 
> > > For info: 
> > > 
> > > sage: from sage.tests.gap_packages import all_installed_packages 
> > > sage: all_installed_packages() 
> > > ('AtlasRep', 
> > >  'FactInt', 
> > >  'GAPDoc', 
> > >  'SmallGrp', 
> > >  'alnuth', 
> > >  'atlasrep', 
> > >  'autpgrp', 
> > >  'crisp', 
> > >  'ctbllib', 
> > >  'fga', 
> > >  'irredsol', 
> > >  'laguna', 
> > >  'polenta', 
> > >  'polycyclic', 
> > >  'primgrp', 
> > >  'resclasses', 
> > >  'sophus', 
> > >  'tomlib', 
> > >  'transgrp') 
> > > sage: all_installed_packages(gap=gap) 
> > > ('FactInt', 
> > >  'GAPDoc', 
> > >  'SmallGrp', 
> > >  'alnuth', 
> > >  'atlasrep', 
> > >  'autpgrp', 
> > >  'crisp', 
> > >  'ctbllib', 
> > >  'fga', 
> > >  'irredsol', 
> > >  'laguna', 
> > >  'polenta', 
> > >  'polycyclic', 
> > >  'primgrp', 
> > >  'resclasses', 
> > >  'sophus', 
> > >  'tomlib', 
> > >  'transgrp') 
> > > 
> > > ls ~/.gap/pkg/ 
> > > AtlasRep 
> > > 
> > > 
> > > 
> > > -- 
> > > 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-r...@googlegroups.com. 
> > > To post to this group, send email to sage-r...@googlegroups.com. 
> > > Visit this group at https://groups.google.com/group/sage-release. 
> > > To view this discussion on the web visit 
> > > https://groups.google.com/d/msgid/sage-release/1969b326-0280-430f-8e84-45053acf1b05%40googlegroups.com.
> > >  
> > > For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > 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.
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-release/f8f00f9a-44cf-4a73-8ec1-fd25ccbcd536%40googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> -- 
> You received 

Re: [sage-release] Sage 8.8.beta6 released

[François Bissey]

This is now
https://trac.sagemath.org/ticket/27878

> On 27/05/2019, at 4:57 PM, François Bissey  wrote:
> 
> I have actual data in one of them.
> A little bit of testing show replacing 
> gap_cmd=“gap -r”
> by
> gap_cmd=“gap”
> in interface/gap.py has no side effects on doctesting apart from letting
> the doctest in question pass when ~/.gap is not empty.
> I’ll open a ticket later.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/48E3E102-F715-488B-B53C-B858A2752BA1%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.beta6 released

[François Bissey]

I have actual data in one of them.
A little bit of testing show replacing 
gap_cmd=“gap -r”
by
gap_cmd=“gap”
in interface/gap.py has no side effects on doctesting apart from letting
the doctest in question pass when ~/.gap is not empty.
I’ll open a ticket later.

François

> On 27/05/2019, at 3:05 PM, Steven Trogdon  wrote:
> 
> Yes, the two important folders on vanilla sage are
> 
> ls -al local/share/gap/pkg/atlasrep/data*
> 
> local/share/gap/pkg/atlasrep/datagens:
> total 12
> drwxr-xr-x 2 strogdon math 4096 Mar 30 20:09 .
> drwxr-xr-x 9 strogdon math 4096 Mar 30 20:09 ..
> -rw-r--r-- 1 strogdon math   70 Mar 30 20:05 dummy
> 
> local/share/gap/pkg/atlasrep/dataword:
> total 12
> drwxr-xr-x 2 strogdon math 4096 Mar 30 20:09 .
> drwxr-xr-x 9 strogdon math 4096 Mar 30 20:09 ..
> -rw-r--r-- 1 strogdon math   70 Mar 30 20:05 dummy
> 
> And the contents of dummy, in both folders, is:
> 
> This file is only for causing that the directory is created by `zoo'.
> 
> On Sunday, May 26, 2019 at 5:59:52 PM UTC-5, François Bissey wrote:
> Actually this is a little bit more complicated than what I thought. This test 
> is likely to fail
> on sage-on-gentoo and probably other distro.
> atlasrep is a very naughty gap package that download data from the internet 
> and
> wants to put it in its installation directory. Which is a problem for a 
> system wide install
> where it belongs to root.
> So I adopted some patches from debian to have the data downloaded and stored 
> in
> ~/.gap. So what we see here in ~/.gap is not a package install but the result 
> of
> using atlasrep at any point. It is likely ~/.gap/pkg/AtlasRep will re-appear 
> all by
> itself during doctesting.
> 
> So we really need to improve on this situation.
> 1) does gap need to be run with "-r"
> 2) if it does what do we do about the fact that ~/.gap is skipped when using 
> the pexpect interface.
> 
> Francois
> 
> On Saturday, May 25, 2019 at 1:21:58 PM UTC+12, François Bissey wrote:
> We’ll want some kind of follow up. The test will fail if you have something 
> in ~/.gap. 
> Not just on sage-on-gentoo. 
> The question is whether the pexpect interface should continue starting `gap` 
> with the 
> “-r” option or not. 
> 
> François 
> 
> > On 25/05/2019, at 12:17 PM, Steven Trogdon  wrote: 
> > 
> > Found this also first on s-o-g. So should ~/.gap be empty or is a follow-up 
> > to https://trac.sagemath.org/ticket/27681 necessary? 
> > On Friday, May 24, 2019 at 7:04:53 PM UTC-5, François Bissey wrote: 
> > You have something in ~/.gap. See 
> > https://trac.sagemath.org/ticket/27681#comment:30 
> > 
> > > On 25/05/2019, at 12:02 PM, Steven Trogdon  wrote: 
> > > 
> > > As far as I know this failure started with this beta. 
> > > 
> > > sage -t --long src/sage/tests/gap_packages.py 
> > > ** 
> > > File "src/sage/tests/gap_packages.py", line 137, in 
> > > sage.tests.gap_packages.all_installed_packages 
> > > Failed example: 
> > > all_installed_packages() == all_installed_packages(gap=gap) 
> > > Expected: 
> > > True 
> > > Got: 
> > > False 
> > > ** 
> > > 1 item had failures: 
> > >1 of   4 in sage.tests.gap_packages.all_installed_packages 
> > > [10 tests, 1 failure, 1.04 s] 
> > > 
> > > 
> > > For info: 
> > > 
> > > sage: from sage.tests.gap_packages import all_installed_packages 
> > > sage: all_installed_packages() 
> > > ('AtlasRep', 
> > >  'FactInt', 
> > >  'GAPDoc', 
> > >  'SmallGrp', 
> > >  'alnuth', 
> > >  'atlasrep', 
> > >  'autpgrp', 
> > >  'crisp', 
> > >  'ctbllib', 
> > >  'fga', 
> > >  'irredsol', 
> > >  'laguna', 
> > >  'polenta', 
> > >  'polycyclic', 
> > >  'primgrp', 
> > >  'resclasses', 
> > >  'sophus', 
> > >  'tomlib', 
> > >  'transgrp') 
> > > sage: all_installed_packages(gap=gap) 
> > > ('FactInt', 
> > >  'GAPDoc', 
> > >  'SmallGrp', 
> > >  'alnuth', 
> > >  'atlasrep', 
> > >  'autpgrp', 
> > >  'crisp', 
> > >  'ctbllib', 
> > >  'fga', 
> > >  'irredsol', 
> > >  'laguna', 
> > >  'polenta', 
> > >  'polycyclic', 
> > >  'primgrp', 
> > >  'resclasses', 
> > >  'sophus', 
> > 

Re: [sage-release] Re: Sage 8.8.beta6 released

[François Bissey]

Actually this is a little bit more complicated than what I thought. This 
test is likely to fail
on sage-on-gentoo and probably other distro.
atlasrep is a very naughty gap package that download data from the internet 
and
wants to put it in its installation directory. Which is a problem for a 
system wide install
where it belongs to root.
So I adopted some patches from debian to have the data downloaded and 
stored in
~/.gap. So what we see here in ~/.gap is not a package install but the 
result of
using atlasrep at any point. It is likely ~/.gap/pkg/AtlasRep will 
re-appear all by
itself during doctesting.

So we really need to improve on this situation.
1) does gap need to be run with "-r"
2) if it does what do we do about the fact that ~/.gap is skipped when 
using the pexpect interface.

Francois

On Saturday, May 25, 2019 at 1:21:58 PM UTC+12, François Bissey wrote:
>
> We’ll want some kind of follow up. The test will fail if you have 
> something in ~/.gap. 
> Not just on sage-on-gentoo. 
> The question is whether the pexpect interface should continue starting 
> `gap` with the 
> “-r” option or not. 
>
> François 
>
> > On 25/05/2019, at 12:17 PM, Steven Trogdon  
> wrote: 
> > 
> > Found this also first on s-o-g. So should ~/.gap be empty or is a 
> follow-up to https://trac.sagemath.org/ticket/27681 necessary? 
> > On Friday, May 24, 2019 at 7:04:53 PM UTC-5, François Bissey wrote: 
> > You have something in ~/.gap. See 
> https://trac.sagemath.org/ticket/27681#comment:30 
> > 
> > > On 25/05/2019, at 12:02 PM, Steven Trogdon  
> wrote: 
> > > 
> > > As far as I know this failure started with this beta. 
> > > 
> > > sage -t --long src/sage/tests/gap_packages.py 
> > > ** 
> > > File "src/sage/tests/gap_packages.py", line 137, in 
> sage.tests.gap_packages.all_installed_packages 
> > > Failed example: 
> > > all_installed_packages() == all_installed_packages(gap=gap) 
> > > Expected: 
> > > True 
> > > Got: 
> > > False 
> > > ** 
> > > 1 item had failures: 
> > >1 of   4 in sage.tests.gap_packages.all_installed_packages 
> > > [10 tests, 1 failure, 1.04 s] 
> > > 
> > > 
> > > For info: 
> > > 
> > > sage: from sage.tests.gap_packages import all_installed_packages 
> > > sage: all_installed_packages() 
> > > ('AtlasRep', 
> > >  'FactInt', 
> > >  'GAPDoc', 
> > >  'SmallGrp', 
> > >  'alnuth', 
> > >  'atlasrep', 
> > >  'autpgrp', 
> > >  'crisp', 
> > >  'ctbllib', 
> > >  'fga', 
> > >  'irredsol', 
> > >  'laguna', 
> > >  'polenta', 
> > >  'polycyclic', 
> > >  'primgrp', 
> > >  'resclasses', 
> > >  'sophus', 
> > >  'tomlib', 
> > >  'transgrp') 
> > > sage: all_installed_packages(gap=gap) 
> > > ('FactInt', 
> > >  'GAPDoc', 
> > >  'SmallGrp', 
> > >  'alnuth', 
> > >  'atlasrep', 
> > >  'autpgrp', 
> > >  'crisp', 
> > >  'ctbllib', 
> > >  'fga', 
> > >  'irredsol', 
> > >  'laguna', 
> > >  'polenta', 
> > >  'polycyclic', 
> > >  'primgrp', 
> > >  'resclasses', 
> > >  'sophus', 
> > >  'tomlib', 
> > >  'transgrp') 
> > > 
> > > ls ~/.gap/pkg/ 
> > > AtlasRep 
> > > 
> > > 
> > > 
> > > -- 
> > > 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-r...@googlegroups.com. 
> > > To post to this group, send email to sage-r...@googlegroups.com. 
> > > Visit this group at https://groups.google.com/group/sage-release. 
> > > To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/1969b326-0280-430f-8e84-45053acf1b05%40googlegroups.com.
>  
>
> > > For more options, visit https://groups.google.com/d/optout. 
> > 
> > 
> > -- 
> > 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@googlegroup

Re: [sage-release] Re: Sage 8.8.beta6 released

[François Bissey]

We’ll want some kind of follow up. The test will fail if you have something in 
~/.gap.
Not just on sage-on-gentoo.
The question is whether the pexpect interface should continue starting `gap` 
with the
“-r” option or not.

François

> On 25/05/2019, at 12:17 PM, Steven Trogdon  wrote:
> 
> Found this also first on s-o-g. So should ~/.gap be empty or is a follow-up 
> to https://trac.sagemath.org/ticket/27681 necessary?
> On Friday, May 24, 2019 at 7:04:53 PM UTC-5, François Bissey wrote:
> You have something in ~/.gap. See 
> https://trac.sagemath.org/ticket/27681#comment:30 
> 
> > On 25/05/2019, at 12:02 PM, Steven Trogdon  wrote: 
> > 
> > As far as I know this failure started with this beta. 
> > 
> > sage -t --long src/sage/tests/gap_packages.py 
> > ** 
> > File "src/sage/tests/gap_packages.py", line 137, in 
> > sage.tests.gap_packages.all_installed_packages 
> > Failed example: 
> > all_installed_packages() == all_installed_packages(gap=gap) 
> > Expected: 
> > True 
> > Got: 
> > False 
> > ** 
> > 1 item had failures: 
> >1 of   4 in sage.tests.gap_packages.all_installed_packages 
> > [10 tests, 1 failure, 1.04 s] 
> > 
> > 
> > For info: 
> > 
> > sage: from sage.tests.gap_packages import all_installed_packages 
> > sage: all_installed_packages() 
> > ('AtlasRep', 
> >  'FactInt', 
> >  'GAPDoc', 
> >  'SmallGrp', 
> >  'alnuth', 
> >  'atlasrep', 
> >  'autpgrp', 
> >  'crisp', 
> >  'ctbllib', 
> >  'fga', 
> >  'irredsol', 
> >  'laguna', 
> >  'polenta', 
> >  'polycyclic', 
> >  'primgrp', 
> >  'resclasses', 
> >  'sophus', 
> >  'tomlib', 
> >  'transgrp') 
> > sage: all_installed_packages(gap=gap) 
> > ('FactInt', 
> >  'GAPDoc', 
> >  'SmallGrp', 
> >  'alnuth', 
> >  'atlasrep', 
> >  'autpgrp', 
> >  'crisp', 
> >  'ctbllib', 
> >  'fga', 
> >  'irredsol', 
> >  'laguna', 
> >  'polenta', 
> >  'polycyclic', 
> >  'primgrp', 
> >  'resclasses', 
> >  'sophus', 
> >  'tomlib', 
> >  'transgrp') 
> > 
> > ls ~/.gap/pkg/ 
> > AtlasRep 
> > 
> > 
> > 
> > -- 
> > 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-r...@googlegroups.com. 
> > To post to this group, send email to sage-r...@googlegroups.com. 
> > Visit this group at https://groups.google.com/group/sage-release. 
> > To view this discussion on the web visit 
> > https://groups.google.com/d/msgid/sage-release/1969b326-0280-430f-8e84-45053acf1b05%40googlegroups.com.
> >  
> > For more options, visit https://groups.google.com/d/optout. 
> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/f8f00f9a-44cf-4a73-8ec1-fd25ccbcd536%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/B31F9E94-A1D6-4EFC-A15A-9065C666B7AC%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Re: Sage 8.8.beta6 released

[François Bissey]

You have something in ~/.gap. See 
https://trac.sagemath.org/ticket/27681#comment:30

> On 25/05/2019, at 12:02 PM, Steven Trogdon  wrote:
> 
> As far as I know this failure started with this beta.
> 
> sage -t --long src/sage/tests/gap_packages.py
> **
> File "src/sage/tests/gap_packages.py", line 137, in 
> sage.tests.gap_packages.all_installed_packages
> Failed example:
> all_installed_packages() == all_installed_packages(gap=gap)
> Expected:
> True
> Got:
> False
> **
> 1 item had failures:
>1 of   4 in sage.tests.gap_packages.all_installed_packages
> [10 tests, 1 failure, 1.04 s]
> 
> 
> For info:
> 
> sage: from sage.tests.gap_packages import all_installed_packages
> sage: all_installed_packages()
> ('AtlasRep',
>  'FactInt',
>  'GAPDoc',
>  'SmallGrp',
>  'alnuth',
>  'atlasrep',
>  'autpgrp',
>  'crisp',
>  'ctbllib',
>  'fga',
>  'irredsol',
>  'laguna',
>  'polenta',
>  'polycyclic',
>  'primgrp',
>  'resclasses',
>  'sophus',
>  'tomlib',
>  'transgrp')
> sage: all_installed_packages(gap=gap)
> ('FactInt',
>  'GAPDoc',
>  'SmallGrp',
>  'alnuth',
>  'atlasrep',
>  'autpgrp',
>  'crisp',
>  'ctbllib',
>  'fga',
>  'irredsol',
>  'laguna',
>  'polenta',
>  'polycyclic',
>  'primgrp',
>  'resclasses',
>  'sophus',
>  'tomlib',
>  'transgrp')
> 
> ls ~/.gap/pkg/
> AtlasRep
> 
> 
> 
> -- 
> 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.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-release/1969b326-0280-430f-8e84-45053acf1b05%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-release/9F015792-340D-43B5-82E4-4D44A0D50A75%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-release] Sage 8.5 released

[François Bissey]

Volker, I see you tagged 8.5 in the develop branch on github but the master is 
not updated.

> On 23/12/2018, at 13:19, Volker Braun  wrote:
> 
> The "master" git branch has been updated to Sage-8.5. 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
> 
> There was no change over 8.5.rc1
> 
> 
> -- 
> 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.

-- 
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 8.5.beta5 released

[François Bissey]

This is definitely it. It introduced the doctests in question. I guess
I should have provided that extra info.


> On 28/11/2018, at 22:11, fchapot...@gmail.com wrote:
> 
> Could be caused by https://trac.sagemath.org/ticket/26702
> 
> Le mercredi 28 novembre 2018 09:49:53 UTC+1, François Bissey a écrit :
> That’s interesting. I thought the failures in sage/databases/sql_db.py in 
> sage-on-gentoo 
> were due to the use of a newer version of sqlite. But if you see it too that 
> must be something 
> more subtle. 
> 
> François 
> 
> > On 28/11/2018, at 21:46, Sébastien Labbé  wrote: 
> > 
> > On Ubuntu 16.04, the command 
> > 
> > sage -t --all --optional=sage,optional,external 
> > 
> > tests the following optional and external doctests: 
> > 
> > Using 
> > --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage
> >  
> > External software detected for doctesting: 
> > ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc 
> > 
> > 
> > and gives All tests passed except the following ones: 
> > 
> > -- 
> > sage -t --long src/sage/databases/findstat.py  # 5 doctests failed 
> > sage -t --long src/sage/symbolic/integration/integral.py  # 1 doctest 
> > failed 
> > sage -t --long src/sage/combinat/tutorial.py  # 1 doctest failed 
> > sage -t --long src/sage/symbolic/integration/external.py  # 3 doctests 
> > failed 
> > sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed 
> > sage -t --long src/sage/repl/load.py  # 1 doctest failed 
> > sage -t --long src/sage/misc/persist.pyx  # 2 doctests failed 
> > sage -t --long src/sage/databases/sql_db.py  # 2 doctests failed 
> > -- 
> > 
> > 
> > Follow up at https://trac.sagemath.org/ticket/25536. New failures are 
> > copied below. 
> > 
> > 
> > 
> > sage -t --long src/sage/combinat/tutorial.py 
> > ** 
> > File "src/sage/combinat/tutorial.py", line 224, in sage.combinat.tutorial 
> > Failed example: 
> > oeis([1,1,2,5,14])# optional -- internet 
> > Expected: 
> > 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> > (2n)!/(n!(n+1)!). Also called Segner numbers. 
> > 1: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1. 
> > 2: ... 
> > Got: 
> > 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> > (2n)!/(n!(n+1)!). Also called Segner numbers. 
> > 1: A124302: Number of set partitions with at most 3 blocks; number of 
> > Dyck paths of height at most 4; dimension of space of symmetric polynomials 
> > in 3 noncommuting variables. 
> > 2: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1. 
> > ** 
> > 1 item had failures: 
> >1 of 249 in sage.combinat.tutorial 
> > 5 tests for not implemented functionality not run 
> > 6 not tested tests not run 
> > 0 tests not run because we ran out of time 
> > [248 tests, 1 failure, 24.70 s] 
> > 
> > 
> > sage -t --long src/sage/databases/sql_db.py 
> > ** 
> > File "src/sage/databases/sql_db.py", line 956, in 
> > sage.databases.sql_db.SQLDatabase.__init__ 
> > Failed example: 
> > D.show('simon') 
> > Expected: 
> > graph6   vertices edges 
> >  
> > ?00 
> > @10 
> > A?   20 
> > A_   21 
> > B?   30 
> > BG   31 
> > BW   32 
> > Bw   33 
> > C?   40 
> > C@   41 
> > CB   42 
> > CF   43 
> > CJ   43 
> > CK

Re: [sage-release] Re: Sage 8.5.beta5 released

[François Bissey]

That’s interesting. I thought the failures in sage/databases/sql_db.py in 
sage-on-gentoo
were due to the use of a newer version of sqlite. But if you see it too that 
must be something
more subtle.

François

> On 28/11/2018, at 21:46, Sébastien Labbé  wrote:
> 
> On Ubuntu 16.04, the command 
> 
> sage -t --all --optional=sage,optional,external
> 
> tests the following optional and external doctests:
> 
> Using 
> --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage
> External software detected for doctesting: 
> ffmpeg,graphviz,gurobi,imagemagick,internet,latex,pandoc
> 
> 
> and gives All tests passed except the following ones:
> 
> --
> sage -t --long src/sage/databases/findstat.py  # 5 doctests failed
> sage -t --long src/sage/symbolic/integration/integral.py  # 1 doctest failed
> sage -t --long src/sage/combinat/tutorial.py  # 1 doctest failed
> sage -t --long src/sage/symbolic/integration/external.py  # 3 doctests failed
> sage -t --long src/sage/combinat/designs/ext_rep.py  # 1 doctest failed
> sage -t --long src/sage/repl/load.py  # 1 doctest failed
> sage -t --long src/sage/misc/persist.pyx  # 2 doctests failed
> sage -t --long src/sage/databases/sql_db.py  # 2 doctests failed
> --
> 
> 
> Follow up at https://trac.sagemath.org/ticket/25536. New failures are copied 
> below.
> 
> 
> 
> sage -t --long src/sage/combinat/tutorial.py
> **
> File "src/sage/combinat/tutorial.py", line 224, in sage.combinat.tutorial
> Failed example:
> oeis([1,1,2,5,14])# optional -- internet
> Expected:
> 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> (2n)!/(n!(n+1)!). Also called Segner numbers.
> 1: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1.
> 2: ...
> Got:
> 0: A000108: Catalan numbers: C(n) = binomial(2n,n)/(n+1) = 
> (2n)!/(n!(n+1)!). Also called Segner numbers.
> 1: A124302: Number of set partitions with at most 3 blocks; number of 
> Dyck paths of height at most 4; dimension of space of symmetric polynomials 
> in 3 noncommuting variables.
> 2: A120588: G.f. satisfies: 3*A(x) = 2 + x + A(x)^2, with a(0) = 1.
> **
> 1 item had failures:
>1 of 249 in sage.combinat.tutorial
> 5 tests for not implemented functionality not run
> 6 not tested tests not run
> 0 tests not run because we ran out of time
> [248 tests, 1 failure, 24.70 s]
> 
> 
> sage -t --long src/sage/databases/sql_db.py
> **
> File "src/sage/databases/sql_db.py", line 956, in 
> sage.databases.sql_db.SQLDatabase.__init__
> Failed example:
> D.show('simon')
> Expected:
> graph6   vertices edges
> 
> ?00
> @10
> A?   20
> A_   21
> B?   30
> BG   31
> BW   32
> Bw   33
> C?   40
> C@   41
> CB   42
> CF   43
> CJ   43
> CK   42
> CL   43
> CN   44
> C]   44
> C^   45
> C~   46
> Got:
> graph6   vertices edges   
> 
> ?00   
> @10   
> A?   20   
> A_   21   
> B?   30   
> BG   31   
> BW   32   
> Bw   33   
> C?   40   
> C@   41   
> CB   42   

Re: [sage-release] Re: Sage 8.5.beta0 released

[François Bissey]

I am still on texlive 2017 so it definitely could be an issue.

> On 26/10/2018, at 11:31, John H Palmieri  wrote:
> 
> I've seen it in the graphs portion of the reference manual, in particular the 
> file graph.py. In the error I posted before, it is coming from combinat, in 
> particular combinat/crystals/tensor_product.py:
> 
> .. SEEALSO::
> 
> :mod:`sage.combinat.crystals.crystals` for general help on
> crystals, and in particular plotting and `\LaTeX` output.
> 
> But there are lots of instances in docstrings of the string "`\LaTeX`", and I 
> can't believe that those are new in recent versions of Sage. Could it depend 
> on the version of pdflatex being used? I am seeing this on two different 
> computers, both OS X, one 10.13, one 10.14, both running pdfTeX version 
> 3.14159265-2.6-1.40.19 (TeX Live 2018).
> 
> If I comment out \usepackage{babel} and some lines related to that package, 
> it builds, so it appears to be a conflict with the babel package. My version 
> is "2018/10/16 3.26". I've opened https://trac.sagemath.org/ticket/26558 for 
> this.
> 
>   John
> 
> 
> 
> On Thursday, October 25, 2018 at 2:33:09 PM UTC-7, François Bissey wrote:
> I cannot see that. Which file is affected? 
> 
> François 
> 
> > On 26/10/2018, at 09:34, John H Palmieri  wrote: 
> > 
> > 
> > 
> > On Thursday, October 25, 2018 at 1:30:30 PM UTC-7, John H Palmieri wrote: 
> > PDF docs fail to build for me: 
> > 
> > [docpdf] LaTeX Warning: Command \LaTeX invalid in math mode on input line 
> > 44737. 
> > [docpdf] 
> > [docpdf] 
> > [docpdf] LaTeX Warning: Command \TeX invalid in math mode on input line 
> > 44737. 
> > [docpdf] 
> > [docpdf] ! You can't use `\spacefactor' in math mode. 
> > [docpdf] \@->\spacefactor 
> > [docpdf]  \@m {} 
> > [docpdf] l.44737 ...and in particular plotting and \(\LaTeX 
> > [docpdf]   \) output. 
> > [docpdf] ? 
> > [docpdf] ! Emergency stop. 
> > [docpdf] \@->\spacefactor 
> > [docpdf]  \@m {} 
> > [docpdf] l.44737 ...and in particular plotting and \(\LaTeX 
> > [docpdf]   \) output. 
> > 
> > I'm a little puzzled by this because we have had `\LaTeX` in our source 
> > code for a while, right? Is this causing problems for anyone else? 
> > 
> > $ pdflatex --version 
> > pdfTeX 3.14159265-2.6-1.40.19 (TeX Live 2018) 
> > 
> >   John 
> > 
> > By the way, there was a similar problem 5 years ago: 
> > https://trac.sagemath.org/ticket/16153 
> > 
> >   
> > 
> > 
> > On Saturday, October 20, 2018 at 3:46:52 PM UTC-7, Volker Braun 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 
> > 
> > 
> > a0a5f5992b (tag: 8.5.beta0, trac/develop) Updated SageMath version to 
> > 8.5.beta0 
> > b9222fdd29 Trac #26500: Add is_derangements method to Permutation 
> > 2dd4022b68 Trac #26464: some cleanup in fan.py 
> > db47d3d61b Trac #26461: adding new Catalan semilattices 
> > 4d560d8816 Trac #26415: py3: use sage_getargspec more consistently 
> > f1b425065b Trac #26175: another typo ticket (2018-09) 
> > 6eec37ddd4 Trac #26099: trim lattices 
> > f0981653db Trac #25270: Add option to only run short doctests 
> > 205c4fb1d5 Trac #26502: failing optional internet doctests in 
> > sage/combinat/designs 
> > b0b1578869 Trac #26494: faster f-polynomial and zeta-polynomial for posets 
> > e93130960a Trac #26493: element_pari_ffelt: use PARI clones instead of 
> > deepcopy_to_python_heap() 
> > 2335e0cbf8 Trac #26488: Remove one usage of SAGE_ROOT in doctests 
> > 171909a527 Trac #26486: clean distances_all_pairs.pyx 
> > de42c3e7f9 Trac #26485: clean genus.pyx 
> > ec6372f055 Trac #26484: clean graph_coloring.py 
> > 9978e85d92 Trac #26483: clean graph_database.py 
> > d8fdcc6b40 Trac #26477: remove deprecated stuff in polynomial_element 
> > 2fbf0a8811 Trac #26476: refine the category of Symmetric groups 
> > faafb175f7 Trac #26469: avoid sorting vertex labels in graph_plot.py 
> > f54d861f11 Trac #26431: py3: not sorting vertices on some graph functions 
> > a05841290a Trac #26475: py3: make all tests in manifolds passed 
> > 2b14ffc744 Trac #26473: py3: fix doctests failures of 
> > sage/combinat/words/word_*datatype* 
> > c928023e3d Trac #2646

Re: [sage-release] Re: Sage 8.5.beta0 released

[François Bissey]

I cannot see that. Which file is affected?

François

> On 26/10/2018, at 09:34, John H Palmieri  wrote:
> 
> 
> 
> On Thursday, October 25, 2018 at 1:30:30 PM UTC-7, John H Palmieri wrote:
> PDF docs fail to build for me:
> 
> [docpdf] LaTeX Warning: Command \LaTeX invalid in math mode on input line 
> 44737.
> [docpdf] 
> [docpdf] 
> [docpdf] LaTeX Warning: Command \TeX invalid in math mode on input line 44737.
> [docpdf] 
> [docpdf] ! You can't use `\spacefactor' in math mode.
> [docpdf] \@->\spacefactor 
> [docpdf]  \@m {}
> [docpdf] l.44737 ...and in particular plotting and \(\LaTeX
> [docpdf]   \) output.
> [docpdf] ? 
> [docpdf] ! Emergency stop.
> [docpdf] \@->\spacefactor 
> [docpdf]  \@m {}
> [docpdf] l.44737 ...and in particular plotting and \(\LaTeX
> [docpdf]   \) output.
> 
> I'm a little puzzled by this because we have had `\LaTeX` in our source code 
> for a while, right? Is this causing problems for anyone else?
> 
> $ pdflatex --version
> pdfTeX 3.14159265-2.6-1.40.19 (TeX Live 2018)
> 
>   John
> 
> By the way, there was a similar problem 5 years ago: 
> https://trac.sagemath.org/ticket/16153
> 
>  
> 
> 
> On Saturday, October 20, 2018 at 3:46:52 PM UTC-7, Volker Braun 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
> 
> 
> a0a5f5992b (tag: 8.5.beta0, trac/develop) Updated SageMath version to 
> 8.5.beta0
> b9222fdd29 Trac #26500: Add is_derangements method to Permutation
> 2dd4022b68 Trac #26464: some cleanup in fan.py
> db47d3d61b Trac #26461: adding new Catalan semilattices
> 4d560d8816 Trac #26415: py3: use sage_getargspec more consistently
> f1b425065b Trac #26175: another typo ticket (2018-09)
> 6eec37ddd4 Trac #26099: trim lattices
> f0981653db Trac #25270: Add option to only run short doctests
> 205c4fb1d5 Trac #26502: failing optional internet doctests in 
> sage/combinat/designs
> b0b1578869 Trac #26494: faster f-polynomial and zeta-polynomial for posets
> e93130960a Trac #26493: element_pari_ffelt: use PARI clones instead of 
> deepcopy_to_python_heap()
> 2335e0cbf8 Trac #26488: Remove one usage of SAGE_ROOT in doctests
> 171909a527 Trac #26486: clean distances_all_pairs.pyx
> de42c3e7f9 Trac #26485: clean genus.pyx
> ec6372f055 Trac #26484: clean graph_coloring.py
> 9978e85d92 Trac #26483: clean graph_database.py
> d8fdcc6b40 Trac #26477: remove deprecated stuff in polynomial_element
> 2fbf0a8811 Trac #26476: refine the category of Symmetric groups
> faafb175f7 Trac #26469: avoid sorting vertex labels in graph_plot.py
> f54d861f11 Trac #26431: py3: not sorting vertices on some graph functions
> a05841290a Trac #26475: py3: make all tests in manifolds passed
> 2b14ffc744 Trac #26473: py3: fix doctests failures of 
> sage/combinat/words/word_*datatype*
> c928023e3d Trac #26467: clean hypergraph_generators.py
> 9a0815d6cf Trac #26466: Py3: Fix DeprecationWarning: generator X raised 
> StopIteration
> 0a2e9748fc Trac #26465: remove deprecated stuff in polyhedron/plot
> d5d317fb3d Trac #26463: gen_to_sage: make imports global
> 1f7f4e6d99 Trac #26458: Py3: Fix DeprecationWarning: generator X raised 
> StopIteration for combinat/words
> 91cd66d5ad Trac #26456: remove deprecated zero_element
> 482abec8e9 Trac #26455: remove deprecated call method for symbolic matrices
> 615904148f Trac #26452: cartesian products of MonomialGrowthGroup related to 
> number fields
> 22c1d92fe7 Trac #26448: clean hyperbolicity.pyx
> 75808093e3 Trac #26447: py3: do not sort vertices in static graphs
> f18560e853 Trac #26444: Use maximal cliques iterator for line graph
> 30649e2336 Trac #26439: clean matchpoly.pyx
> dcd7851c62 Trac #26437: clean partial_cube.py
> f936bdfe8c Trac #26436: Force input of affine permutation groups to be 
> elements of ZZ
> 391c379af3 Trac #26435: polytopes.simplex: Add base_ring keyword, allow exact 
> computation with project=True
> 7a3157fe59 Trac #26433: Slowness in generic quo_rem
> 519c614dde Trac #26432: clean graph.py
> 72764911e6 Trac #26430: py3: fix some doctests in combinat/designs
> aba56d7e8e Trac #26428: improve is_weakly_chordal
> 23587340f6 Trac #26427: add doctest to charpoly method of symbolic matrices
> cccd38873b Trac #26424: Bugs in inverses of Yokonuma-Hecke algebras
> bffe63cbde Trac #26419: py3: fix hash for trees
> 88db09e866 Trac #26418: py3: fix int argument check in 
> Matrix_integer_dense.__pow__
> 46217e165c Trac #26417: py3: more robust doctests in one thematic tutorial
> c6fe9ebcc0 Trac #26389: Listing meataxe matrices with zero rows is broken
> 0111e2a65d Trac #23432: Type debugger
> 3d76c5311a Trac #26414: Various fixes to rational_power_parts()
> ce4871d65b Trac #26400: py3 fix all doctests in groups/matrix_gps
> fb09bfa711 Trac #26396: Upgrade to cypari2-1.3.1
> 

Re: [sage-release] Sage 8.4.beta4 released

[François Bissey]

For info he did a couple of hours after my answer to you. So it has been 
available for
about 12 hours now.

> On 8/09/2018, at 07:17, 'Justin C. Walker' via sage-release 
>  wrote:
> 
> 
>> On Sep 6, 2018, at 22:24 , François Bissey  wrote:
>> 
>> No you didn’t. Volker hasn’t pushed on github yet. I am waiting myself to 
>> update the
>> sage-on-gentoo ebuild.
> 
> Good to know.  Thanks!
> 
> Justin
> 
> --
> Justin C. Walker
> Curmudgeon at Large
> Director
> Institute for the Enhancement of the Director's Income
> --
> Build a man a fire and he'll be warm
> for a night.
> Set a man on fire and he'll be warm
> for the rest of his life.
> 
> 
> 
> -- 
> 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.

-- 
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] Sage 8.4.beta4 released

[François Bissey]

No you didn’t. Volker hasn’t pushed on github yet. I am waiting myself to 
update the
sage-on-gentoo ebuild.

François

> On 7/09/2018, at 17:12, 'Justin C. Walker' via sage-release 
>  wrote:
> 
> 
>> On Sep 6, 2018, at 16:24 , Volker Braun  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
> 
> I just cloned from github and did “git checkout develop”.  VERSION.txt says 
>  SageMath version 8.4.beta3, Release Date: 2018-09-02
> 
> Here’s my command sequence.  Did I miss something?
> 
> $ git clone git://github.com/sagemath/sage.git
> Cloning into 'sage'...
> remote: Counting objects: 585449, done.
> remote: Compressing objects: 100% (2/2), done.
> remote: Total 585449 (delta 3), reused 3 (delta 3), pack-reused 585444
> Receiving objects: 100% (585449/585449), 194.36 MiB | 4.45 MiB/s, done.
> Resolving deltas: 100% (456526/456526), done.
> Checking connectivity... done.
> $ mv sage sage-8.4.beta4
> $ cd sage-8.4.beta4
> $ git checkout develop
> Branch develop set up to track remote branch develop from origin.
> Switched to a new branch 'develop'
> $ cat VERSION.txt
> SageMath version 8.4.beta3, Release Date: 2018-09-02
> $ git branch
> * develop
>  master
> $
> 
> 
> --
> Justin C. Walker, Curmudgeon-At-Large
> Institute for the Enhancement of the Director's Income
> 
> When LuteFisk is outlawed,
> Only outlaws will have LuteFisk
> 
> 
> 
> 
> -- 
> 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.

-- 
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] Sage 8.3.beta2 released

[François Bissey]

If the optional package bliss is installed the following doctests fail:
sage -t --long --warn-long 83.4 src/sage/geometry/polyhedron/base.py  # 
4 doctests failed
sage -t --long --warn-long 83.4 src/sage/geometry/lattice_polytope.py  # 
1 doctest failed
sage -t --long --warn-long 83.4 
src/sage/geometry/polyhedron/ppl_lattice_polytope.py  # 5 doctests failed
sage -t --long --warn-long 83.4 
src/sage/geometry/triangulation/point_configuration.py  # 1 doctest failed
sage -t --long --warn-long 83.4 src/sage/geometry/fan_isomorphism.py  # 
1 doctest failed


This is different from the previous series of failures.
Example:
sage -t --long --warn-long 83.6 
src/sage/geometry/triangulation/point_configuration.py

**
File "src/sage/geometry/triangulation/point_configuration.py", line 
1155, in 
sage.geometry.triangulation.point_configuration.PointConfiguration.restricted_automorphism_group

Failed example:
pyramid.restricted_automorphism_group()
Expected:
Permutation Group with generators [(3,5), (2,3)(4,5), (2,4)]
Got:
Permutation Group with generators [(3,5), (2,3)(4,5)]
**
1 item had failures:

Francois

On 19/05/18 08:03, Volker Braun 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


b4a14f9782 (tag: 8.3.beta2) Updated SageMath version to 8.3.beta2
0f91c52fc3 Trac #25102: Allow more digits in some outputs
b3147801b2 Trac #25094: Make GAP doctests less version dependent
a2d1ac71a3 Trac #25093: Use year of release for copyright
4070289aee Trac #25066: Minor typo in pynac.pxd
6c8058f15e Trac #25350: trivial cases of operations in ℤ[x]
a5d8ee3b36 Trac #25331: Pyflakes for posets
6b38080d4e Trac #25303: Random orientation of a graph
94ce399587 Trac #25291: speed up generic polynomials
8b45b1e022 Trac #25279: py3: adapt the atlas-config script
aa2ac3f797 Trac #25265: Compute polynomial discriminant over QQbar
35def48abd Trac #25242: is_polynomial fails when multiple roots
0aecaa99fc Trac #25240: Chebyshev and Lattes maps should be created as 
dynamical systems
51ee5108e4 Trac #25232: Minor simplification of 
PolynomialRing.fraction_field()

2d0d2ae4df Trac #25231: py3: miscellaneous minor fixes to sage.crypto
98b609b283 Trac #25218: Extract roots in NumberField if possible
db3b41b1c0 Trac #25215: py3: minor test fixes for 
sage.tensor.modules.free_module_tensor
5bf743455a Trac #25213: Sort terms in DifferentialForm repr/latex by 
coordinate index

0efa28a027 Trac #25210: Add option to make QQbar / AA print using radicals
c23aacdda4 Trac #25187: py3: misc fixes to sage.typeset
a204596b9f Trac #25180: py3: fixes to sage.dynamics
82a345f8ab Trac #25138: Make some packages order-only dependencies
9382fea6fe Trac #25127: gauss_sum mod1
fdce8e47ee Trac #25126: Factoring disconnected graph
13b921ed9c Trac #25115: more https links and some typos
b8f7802f39 Trac #25073: Add USA map graph
3ad30beb24 Trac #25020: Some updates to use pycygwin
a80afb248b Trac #24783: py3: minor fixes in sage.interfaces
4fe72af573 Trac #25387: Clean up UniqueRepresentations in sage.algebra 
(part 1)

bb38a0b409 Trac #25380: py3: minor fixes towards docbuild
01623e96c0 Trac #25373: Add IPython support for Cython functions
02f281c1c0 Trac #25371: py3: towards docbuild, more details
6eef55a3f8 Trac #25368: py3: towards docbuild, some details
0f896f0357 Trac #25179: New function to get attribute without binding 
and use it instead of __func__

a7905c7071 Trac #25039: Add sdh_install helper function to sage-dist-helpers
40f328aa0b Trac #24975: Improve method binpacking
308d08ffc9 Trac #24760: convert cluster interact to jupyter notebook
705edc0b7b Trac #21162: Row standard tableaux
7357c3aa4e Trac #25323: Feature check for GAP package "prim" is wrong
5cca07b851 Trac #25010: Wrong results for principal_directions in 
ParametrizedSurface3d

02245711f6 Trac #24970: py3: fix sage.tests.cmdline
2953d35508 Trac #24956: py3: miscellaneous minor fixes for 
sage.interfaces.singular
82d89e1abd Trac #25294: Extending valuations in function fields does not 
work
ef697b89b9 Trac #25283: Implement left descent and reduced word for 
colored permutations

25c5e809ab Trac #25274: Clean up cimports in libgap
6ff28fc20a Trac #25204: Upgrade to Python 2.7.15
f079dec4c8 Trac #25197: py3: minor byes/str fixes to sage.matrix
aa5e55aeee Trac #25087: Add DESTDIR support for ppl
c8bf11d065 Trac #24924: Making the bliss canonical form available for 
edge labelled graphs

097ce00d12 Trac #24836: py3: cleanup sage.interfaces.sage0
4dc912cd8c Trac #23851: Fix memoryleak introduced in #11670
f23c4263df Trac #20687: wrong result for is_subword_of
7a93730251 Trac #20564: KleshchevPartitions
bb208e5453 Trac #24938: mpolynomial.lift signals
2e489dbeaf Trac #24891: improve docstring of reflection groups 

Re: [sage-release] Re: Sage 8.3.beta0 released

[François Bissey]

I hadn’t looked at it and didn’t really understand the issue. Also I didn’t 
realise
it was a new ticket from the way you said it - I thought you where adding it to 
a related
gap ticket. So it is all fine.

> On 10/05/2018, at 21:46, Emmanuel Charpentier <emanuel.charpent...@gmail.com> 
> wrote:
> 
> Isn't Trac#25323 good enough ?
> 
> --
> Emmanuel Charpentier
> 
> Le jeudi 10 mai 2018 10:22:06 UTC+2, François Bissey a écrit :
> It is probably an oversight or a corner case in 
> https://trac.sagemath.org/ticket/20382 
> Do open a ticket for that. 
> 
> François 
> 
> > On 10/05/2018, at 20:15, Emmanuel Charpentier <emanuel.c...@gmail.com> 
> > wrote: 
> > 
> > On Debian testing running on cote i7 + 16 GB RAM, make ptestlong gives me 
> > three errors : 
> > 
> > sage -t --long src/sage/rings/padics/padic_lattice_element.py  # Timed out 
> > sage -t --long src/sage/groups/perm_gps/permgroup.py  # 1 doctest failed 
> > sage -t --long src/sage/features/gap.py  # 1 doctest failed 
> > 
> > The first one is transient (i.e. passes when ran standalone), the other two 
> > are permanent (and persist even after "sage -f database_gap", see below) : 
> > 
> > charpent@asus16-ec:/usr/local/sage-8$ sage -t --long 
> > src/sage/groups/perm_gps/permgroup.py 
> > Forcing sage-location, probably because a new package was installed. 
> > Cleaning up, do not interrupt this. 
> > Done cleaning. 
> > too many failed tests, not using stored timings 
> > Running doctests with ID 2018-05-10-10-01-39-e77fca6f. 
> > Git branch: r344_8_3b0 
> > Using 
> > --optional=database_gap,dot2tex,fricas,giacpy_sage,gmpy2,igraph,mpir,python2,python_igraph,sage
> >  
> > Doctesting 1 file. 
> > sage -t --long src/sage/groups/perm_gps/permgroup.py 
> > ** 
> > File "src/sage/groups/perm_gps/permgroup.py", line 1756, in 
> > sage.groups.perm_gps.permgroup.PermutationGroup_generic.group_primitive_id 
> > Failed example: 
> > G.group_primitive_id()# optional - database_gap 
> > Exception raised: 
> > Traceback (most recent call last): 
> >   File 
> > "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/doctest/forker.py",
> >  line 562, in _run 
> > self.compile_and_execute(example, compiler, test.globs) 
> >   File 
> > "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/doctest/forker.py",
> >  line 972, in compile_and_execute 
> > exec(compiled, globs) 
> >   File " > sage.groups.perm_gps.permgroup.PermutationGroup_generic.group_primitive_id[1]>",
> >  line 1, in  
> > G.group_primitive_id()# optional - database_gap 
> >   File 
> > "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/groups/perm_gps/permgroup.py",
> >  line 1775, in group_primitive_id 
> > GapPackage("prim", spkg="database_gap").require() 
> >   File 
> > "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/features/__init__.py",
> >  line 158, in require 
> > raise FeatureNotPresentError(self, presence.reason, 
> > presence.resolution) 
> > FeatureNotPresentError: GAP package prim is not available. 
> > `TestPackageAvailability("prim")` evaluated to `fail` in GAP. 
> > To install GAP package prim you can try to run 'sage -i database_gap'. 
> > ** 
> > 1 item had failures: 
> >1 of   7 in 
> > sage.groups.perm_gps.permgroup.PermutationGroup_generic.group_primitive_id 
> > [832 tests, 1 failure, 9.92 s] 
> > -- 
> > sage -t --long src/sage/groups/perm_gps/permgroup.py  # 1 doctest failed 
> > -- 
> > Total time for all tests: 10.1 seconds 
> > cpu time: 6.6 seconds 
> > cumulative wall time: 9.9 seconds 
> > charpent@asus16-ec:/usr/local/sage-8$ sage -t --long 
> > src/sage/features/gap.py 
> > too many failed tests, not using stored timings 
> > Running doctests with ID 2018-05-10-10-01-58-0245b4d8. 
> > Git branch: r344_8_3b0 
> > Using 
> > --optional=database_gap,dot2tex,fricas,giacpy_sage,gmpy2,igraph,mpir,python2,python_igraph,sage
> >  
> > Doctesting 1 file. 
> > sage -t --long src/sage/features/

Re: [sage-release] Re: Sage 8.3.beta0 released

[François Bissey]

It is probably an oversight or a corner case in 
https://trac.sagemath.org/ticket/20382
Do open a ticket for that.

François

> On 10/05/2018, at 20:15, Emmanuel Charpentier  
> wrote:
> 
> On Debian testing running on cote i7 + 16 GB RAM, make ptestlong gives me 
> three errors :
> 
> sage -t --long src/sage/rings/padics/padic_lattice_element.py  # Timed out
> sage -t --long src/sage/groups/perm_gps/permgroup.py  # 1 doctest failed
> sage -t --long src/sage/features/gap.py  # 1 doctest failed
> 
> The first one is transient (i.e. passes when ran standalone), the other two 
> are permanent (and persist even after "sage -f database_gap", see below) :
> 
> charpent@asus16-ec:/usr/local/sage-8$ sage -t --long 
> src/sage/groups/perm_gps/permgroup.py
> Forcing sage-location, probably because a new package was installed.
> Cleaning up, do not interrupt this.
> Done cleaning.
> too many failed tests, not using stored timings
> Running doctests with ID 2018-05-10-10-01-39-e77fca6f.
> Git branch: r344_8_3b0
> Using 
> --optional=database_gap,dot2tex,fricas,giacpy_sage,gmpy2,igraph,mpir,python2,python_igraph,sage
> Doctesting 1 file.
> sage -t --long src/sage/groups/perm_gps/permgroup.py
> **
> File "src/sage/groups/perm_gps/permgroup.py", line 1756, in 
> sage.groups.perm_gps.permgroup.PermutationGroup_generic.group_primitive_id
> Failed example:
> G.group_primitive_id()# optional - database_gap
> Exception raised:
> Traceback (most recent call last):
>   File 
> "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
> line 562, in _run
> self.compile_and_execute(example, compiler, test.globs)
>   File 
> "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
> line 972, in compile_and_execute
> exec(compiled, globs)
>   File " sage.groups.perm_gps.permgroup.PermutationGroup_generic.group_primitive_id[1]>",
>  line 1, in 
> G.group_primitive_id()# optional - database_gap
>   File 
> "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/groups/perm_gps/permgroup.py",
>  line 1775, in group_primitive_id
> GapPackage("prim", spkg="database_gap").require()
>   File 
> "/usr/local/sage-8/local/lib/python2.7/site-packages/sage/features/__init__.py",
>  line 158, in require
> raise FeatureNotPresentError(self, presence.reason, 
> presence.resolution)
> FeatureNotPresentError: GAP package prim is not available.
> `TestPackageAvailability("prim")` evaluated to `fail` in GAP.
> To install GAP package prim you can try to run 'sage -i database_gap'.
> **
> 1 item had failures:
>1 of   7 in 
> sage.groups.perm_gps.permgroup.PermutationGroup_generic.group_primitive_id
> [832 tests, 1 failure, 9.92 s]
> --
> sage -t --long src/sage/groups/perm_gps/permgroup.py  # 1 doctest failed
> --
> Total time for all tests: 10.1 seconds
> cpu time: 6.6 seconds
> cumulative wall time: 9.9 seconds
> charpent@asus16-ec:/usr/local/sage-8$ sage -t --long src/sage/features/gap.py
> too many failed tests, not using stored timings
> Running doctests with ID 2018-05-10-10-01-58-0245b4d8.
> Git branch: r344_8_3b0
> Using 
> --optional=database_gap,dot2tex,fricas,giacpy_sage,gmpy2,igraph,mpir,python2,python_igraph,sage
> Doctesting 1 file.
> sage -t --long src/sage/features/gap.py
> **
> File "src/sage/features/gap.py", line 41, in 
> sage.features.gap.GapPackage._is_present
> Failed example:
> GapPackage("prim", spkg="database_gap").is_present()  # optional: 
> database_gap
> Expected:
> FeatureTestResult('GAP package prim', True)
> Got:
> FeatureTestResult('GAP package prim', False)
> **
> 1 item had failures:
>1 of   3 in sage.features.gap.GapPackage._is_present
> [12 tests, 1 failure, 0.50 s]
> --
> sage -t --long src/sage/features/gap.py  # 1 doctest failed
> --
> Total time for all tests: 0.5 seconds
> cpu time: 0.5 seconds
> cumulative wall time: 0.5 seconds
> 
> The reinstallation of database_gap does not give error or warning.
> 
> In both cases, the problem seems to be bound to the 'prim' package of GAP.
> 
> Summarily reported againtst database_gap in Trac#25323.
> 
> HTH,
> 
> --
> Emmanuel Charpentier
> 
> Le mercredi 9 mai 2018 20:44:17 UTC+2, Volker Braun a écrit :
> As always, you can get the latest beta version from the "develop" git branch. 
> Alternatively, the self-contained source 

Re: [sage-release] Re: Sage 8.2.rc1 released

[François Bissey]

Would https://trac.sagemath.org/ticket/25026 look helpful? sun.audio missing?

> On 1/04/2018, at 22:40, Emmanuel Charpentier  
> wrote:
> 
> On Debian testing running on Core i7 + 16 GB RAM, builds and passes ptestlong 
> without errors whatsoever.
> 
> However, I get 648 (!) logs of errors related to Java in $SAGE_ROOT (see 
> enclosed tarball). This might be specific to my machine. ATM, I haven't the 
> slightest clue...
> 

-- 
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 8.2.beta8 released

[François Bissey]

> On 15/03/2018, at 04:34, Sébastien Labbé  wrote:
> 
> On Ubuntu 16.04, my first attempt at running make finishes with a problem 
> with giac (undefined reference to `png_set_longjmp_fn')
> 
> The log finishes with:
> 
> ...
> [giac-1.4.9.45.p2] libtool: link: g++ -g -O2 -fno-strict-aliasing 
> -DGIAC_GENERIC_CONSTANTS -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/lib -o 
> .libs/icas icas.o  -L/home/slabbe/GitBox/sage/local/lib ./.libs/libxcas.a 
> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so
>  -lntl -lpari -lreadline -ltermcap -lgsl -lgslcblas -lrt -lpthread -lglpk 
> -ldl -lpng -lm -lmpfi /home/slabbe/GitBox/sage/local/lib/libmpfr.so -lgmp 
> -Wl,-rpath -Wl,/home/slabbe/GitBox/sage/local/lib
> [giac-1.4.9.45.p2] 
> /home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src/.libs/libgiac.so:
>  undefined reference to `png_set_longjmp_fn'
> [giac-1.4.9.45.p2] collect2: error: ld returned 1 exit status
> [giac-1.4.9.45.p2] Makefile:579: recipe for target 'icas' failed
> [giac-1.4.9.45.p2] make[5]: *** [icas] Error 1
> [giac-1.4.9.45.p2] make[5]: Leaving directory 
> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src/src'
> [giac-1.4.9.45.p2] Makefile:404: recipe for target 'all-recursive' failed
> [giac-1.4.9.45.p2] make[4]: *** [all-recursive] Error 1
> [giac-1.4.9.45.p2] make[4]: Leaving directory 
> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
> [giac-1.4.9.45.p2] Makefile:333: recipe for target 'all' failed
> [giac-1.4.9.45.p2] make[3]: *** [all] Error 2
> [giac-1.4.9.45.p2] make[3]: Leaving directory 
> '/home/slabbe/GitBox/sage/local/var/tmp/sage/build/giac-1.4.9.45.p2/src'
> [giac-1.4.9.45.p2] 
> 
> [giac-1.4.9.45.p2] Error building giac-1.4.9.45.p2
> [giac-1.4.9.45.p2] 
> 
> ...
> 
> I did 
> 
> sage -f libpng && make
> 
> which seems to have fixed the error:

Yes that particular one has been seen in the wild before. For some reason
the libpng install got broken and you are missing libpng.so inside sage.
Then the linker tries a system version and if it is not libpng-1.4+ you’ll
get that error because the symbol doesn’t exist before that version.
I would be good to figure out why some install don’t have libpng.so
though, that’s a bit of a mystery.

François

-- 
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] Sage 8.2.beta6 released

[François Bissey]

> On 19/02/2018, at 19:36, Justin C. Walker  wrote:
> 
>> 
>> On Feb 18, 2018, at 12:09 , Volker Braun  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
> 
> Built on macOS 10.11.6 (Quad-core Core i7), from a fresh clone/checkout of 
> develop.
> 
> All tests (‘testlong’) passed!
> 
> Total time dropped from ~2 1/4 hrs to 1 3/4 hrs, thanks to switch to clang!

Not doing a full build of gcc anymore does that for you.
Its hours saved on my laptop.

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

> On 15/02/2018, at 12:21, Justin C. Walker <jus...@mac.com> wrote:
> 
> 
>> On Feb 12, 2018, at 14:45 , François Bissey <frp.bis...@gmail.com> wrote:
>> 
>> Can you test the branch at https://trac.sagemath.org/ticket/24721
>> and see if that helps with this particular machine.
> 
> With François’s help, I rebuilt Sage with #24721 added, and the result built 
> w/o problems (Quad-core Core i7, macOS 10.11.6).  All tests (‘ptestlong’) 
> passed!
> 

Great! Can you positively review #24721, please?
This means that we can support building as far back as
xcode 7 which I think is some achievement.
On the other hand it looks like the recommended minimal
version of clang on linux is 4.0.

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

> On 13/02/2018, at 12:42, Justin C. Walker <jus...@mac.com> wrote:
> 
> 
>> On Feb 12, 2018, at 14:45, François Bissey <frp.bis...@gmail.com> wrote:
>> 
>> Can you test the branch at https://trac.sagemath.org/ticket/24721
>> and see if that helps with this particular machine.
> 
> Sure will.  I have yet to update to Xcode 8.  Should I try the ticket before 
> or after updating?
> 

Before :)

-- 
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] Sage 8.2.beta5 released

[François Bissey]

Can you test the branch at https://trac.sagemath.org/ticket/24721
and see if that helps with this particular machine.

François

> On 10/02/2018, at 19:40, Justin C. Walker <jus...@mac.com> wrote:
> 
> 
>> On Feb 9, 2018, at 19:32 , François Bissey <frp.bis...@gmail.com> wrote:
>> 
>> We didn’t test clang 3.7 which is what your machine is using at OS X 10.11.
>> But I recognised the error as one I got in the same place when I tried a 
>> build
>> with icc on linux. Yes that’s a fun bit I haven’t mentioned yet.
>> You can technically try any compiler that pretends to be gcc - but only 
>> clang 3.8
>> forward have been tested and I haven’t put in place bits for dealing with 
>> icc’s fun
>> issues (over optimisation from icc kills pari).
>> sqlite wants to use some builtins that are in gcc but identifies the 
>> compiler supporting
>> the builtins by a series of pragma. Always risky and a bit porous in this 
>> case.
> 
> Thanks for this.  I have
> 
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin15.6.0
> Thread model: posix
> 
> Is there a fairly straight-forward way to get Apple’s clang at what you're 
> calling 3.8?  
> 
> 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
> 
> 
> 
> 
> -- 
> 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.

-- 
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 8.2.beta5 released

[François Bissey]

Thanks there was exactly what I was after - or almost
CLANG_DEFAULT_RTLIB
which may be needed for https://trac.sagemath.org/ticket/24712

> On 12/02/2018, at 21:22, Ralf Stephan <gtrw...@gmail.com> wrote:
> 
> https://stackoverflow.com/questions/19901128/enable-libc-libcxx-by-default-when-using-clang
> 
> On Mon, Feb 12, 2018 at 9:16 AM François Bissey <frp.bis...@gmail.com> wrote:
> 
> 
> > On 12/02/2018, at 20:06, Ralf Stephan <gtrw...@gmail.com> wrote:
> >
> > Finally here is the recommended set of flags for clang on Linux:
> >
> > export CC="clang"
> > export CXX="clang++"
> > export CLANG_DEFAULT_CXX_STDLIB="libc++"
> >
> 
> Where did you find about this variable? I’d like to know if there are
> other for some other aspects of clang.
> 
> François
> 
> --
> 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.
> 
> -- 
> 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.

-- 
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 8.2.beta5 released

[François Bissey]

> On 12/02/2018, at 20:06, Ralf Stephan  wrote:
> 
> Finally here is the recommended set of flags for clang on Linux:
> 
> export CC="clang"
> export CXX="clang++"
> export CLANG_DEFAULT_CXX_STDLIB="libc++"
> 

Where did you find about this variable? I’d like to know if there are
other for some other aspects of clang.

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

> On 11/02/2018, at 19:57, François Bissey <frp.bis...@gmail.com> wrote:
> 
> 
> 
>> On 10/02/2018, at 12:07, Justin C. Walker <jus...@mac.com> wrote:
>> 
>>> 
>>> On Feb 9, 2018, at 00:25 , Volker Braun <vbraun.n...@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
>> 
>> Yay for using clang!
>> 
>> Built from a fresh clone/checkout of the develop tree.
>> 
>> The build (macOS 10.11.6, MBP Quad-core Core i7) blows chunks on sqlite:
>> 
>> ==
>> libtool: compile:  gcc -DPACKAGE_NAME=\"sqlite\" 
>> -DPACKAGE_TARNAME=\"sqlite\" -DPACKAGE_VERSION=\"3.17.0\" 
>> "-DPACKAGE_STRING=\"sqlite 3.17.0\
>> \"" -DPACKAGE_BUGREPORT=\"http://www.sqlite.org\; -DPACKAGE_URL=\"\" 
>> -DPACKAGE=\"sqlite\" -DVERSION=\"3.17.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_T\
>> YPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
>> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 \
>> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_FDATASYNC=1 
>> -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_D\
>> ECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 
>> -DHAVE_EDITLINE=1 -I. -I/Users/Sage/sage-8.2.beta5/local/include -D_REENTR\
>> ANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_RTREE -g 
>> -O2 -MT sqlite3.lo -MD -MP -MF .deps/sqlite3.Tpo -c sqlite3.c  -fn\
>> o-common -DPIC -o .libs/sqlite3.o
>> sqlite3.c:28836:10: error: use of unknown builtin '__builtin_add_overflow' 
>> [-Wimplicit-function-declaration]
>> return __builtin_add_overflow(*pA, iB, pA);
>>^
>> ==
>> 
>> sqlite log attached.
> 
> 
> Ok figured how that one occurred. Xcode version clang differently from linux.
> sqlite macro evaluate the version with
> #if defined(__clang__) && !defined(_WIN32) && 
> !defined(SQLITE_DISABLE_INTRINSIC)
> # define CLANG_VERSION \
>(__clang_major__*100+__clang_minor__*1000+__clang_patchlevel__)
> 
> with clang 3.8 on linux __clang_major__ is 3 but in Xcode 3.8 it is 8.
> You can imagine that a test designed to figure that you use clang 4 on linux
> will pass with that version of Xcode.
> Anyway it is all the wrong way to figure out if you should use the builtin.
> Using 
> https://www.gnu.org/software/autoconf-archive/ax_gcc_builtin.html#ax_gcc_builtin
> is a way better idea but that means touching quite a bit of sqlite3.c

The latest version of sqlite doesn’t try to identify with version of clang 
support
__builtin_* anymore. I guess they figured out that it was broken.
I also noticed they figured out they needed to do something about icc.
They still do it wrong in my opinion, but upgrading should fix the problem.

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

> On 10/02/2018, at 12:07, Justin C. Walker  wrote:
> 
>> 
>> On Feb 9, 2018, at 00:25 , Volker Braun  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
> 
> Yay for using clang!
> 
> Built from a fresh clone/checkout of the develop tree.
> 
> The build (macOS 10.11.6, MBP Quad-core Core i7) blows chunks on sqlite:
> 
> ==
> libtool: compile:  gcc -DPACKAGE_NAME=\"sqlite\" -DPACKAGE_TARNAME=\"sqlite\" 
> -DPACKAGE_VERSION=\"3.17.0\" "-DPACKAGE_STRING=\"sqlite 3.17.0\
> \"" -DPACKAGE_BUGREPORT=\"http://www.sqlite.org\; -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"sqlite\" -DVERSION=\"3.17.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_T\
> YPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 \
> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_FDATASYNC=1 
> -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_D\
> ECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 
> -DHAVE_EDITLINE=1 -I. -I/Users/Sage/sage-8.2.beta5/local/include -D_REENTR\
> ANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_RTREE -g -O2 
> -MT sqlite3.lo -MD -MP -MF .deps/sqlite3.Tpo -c sqlite3.c  -fn\
> o-common -DPIC -o .libs/sqlite3.o
> sqlite3.c:28836:10: error: use of unknown builtin '__builtin_add_overflow' 
> [-Wimplicit-function-declaration]
>  return __builtin_add_overflow(*pA, iB, pA);
> ^
> ==
> 
> sqlite log attached.


Ok figured how that one occurred. Xcode version clang differently from linux.
sqlite macro evaluate the version with
#if defined(__clang__) && !defined(_WIN32) && !defined(SQLITE_DISABLE_INTRINSIC)
# define CLANG_VERSION \
(__clang_major__*100+__clang_minor__*1000+__clang_patchlevel__)

with clang 3.8 on linux __clang_major__ is 3 but in Xcode 3.8 it is 8.
You can imagine that a test designed to figure that you use clang 4 on linux
will pass with that version of Xcode.
Anyway it is all the wrong way to figure out if you should use the builtin.
Using 
https://www.gnu.org/software/autoconf-archive/ax_gcc_builtin.html#ax_gcc_builtin
is a way better idea but that means touching quite a bit of sqlite3.c

François

-- 
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 8.2.beta5 released

[François Bissey]

> On 11/02/2018, at 10:36, Simon King  wrote:
> 
>> 
>> Ubuntu is probably the most used distro if someone can wipe up some 
>> instructions
>> on what to install that would help greatly.
> 
> Well, so far I was installing clang, clang-dev and libc++abi-dev. The
> latter was in order to get __cxxabi_config.h. However, even after
> installing libc++abi-dev (which according to a duckduckgo search is
> providing the missing header), brial fails to build for the same reason,
> it cannot find __cxxabi_config.h.

It looks like you may have to provide the include path to __cxxabi_config.h.
I don’t know where ubuntu installs it. On Gentoo libcxx is configured at build
time with the right location with the “USE” variable I provided.
So you may have to have
CXX=“clang++ -I/path/to/cxxabi -stdlib=libc++”

François

-- 
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 8.2.beta5 released

[François Bissey]

I am sorry to have cause everyone who wanted to try it on linux so much
grief.
To summarise 
* you need to build from scratch
* clang using libstdc++ from gcc appears to have problems - at the moment
I don’t know if it is just because the gcc in question is too old or that’s
a no go.
* if you switch from clang+libstdc++ to clang+libc++ (or libcxx depending on
your distro) you have to do a distclean as they don’t mix.
* You may need to set CXX to “clang++ --stdlib=libc++” if your distro default
to using libstdc++.

Ubuntu is probably the most used distro if someone can wipe up some instructions
on what to install that would help greatly.

For gentoo setting USE="default-compiler-rt default-libcxx compiler-rt libcxx 
libcxxabi”
should get you something usable with libc++ as the default for clang++.

Can people copy me (fbissey) on bugs they have with clang-5.0 (or even 6.0)
and I’ll look at them.

François

> On 11/02/2018, at 07:52, Simon King  wrote:
> 
> In the failing compilation, we have
> 
> clang++ --stdlib=libc++ [which is what we want]
>... -std=c++11 [which comes from brial]
>... -c BlockDegLexOrder.cc  -fPIC -DPIC -o .libs/BlockDegLexOrder.o
> 
> And the error is then
>/usr/include/c++/v1/cxxabi.h:21:10: fatal error: '__cxxabi_config.h'
>file not found
>#include <__cxxabi_config.h>
> 
> So, it seems (after some duckduckgoing) that I also need to install
>libc++abi-dev
> 
> Hence, I had to install clang, clang-dev, libc++abi-dev so far. These
> things should (if clang is supposed to be a serious option for Sage) be
> mentioned in the documentation, as prerequisites.
> 
> Since I have enough time, I am starting over from scratch (i.e., make
> distclean)
> 
> Regards,
> Simon
> 
> 
> On 2018-02-10, Simon King  wrote:
>> Hi!
>> 
>> After installation of clang-dev, I tried again, but alas, brial failed
>> to build again.
>> 
>> Log is at
>> http://users.minet.uni-jena.de/cohomology/logs/brial-1.0.1.p2.log
>> 
>> So, I am giving up on it for now.
>> 
>> Best regards,
>> Simon
>> 
> 
> -- 
> 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.

-- 
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 8.2.beta5 released

[François Bissey]

> On 11/02/2018, at 00:02, Simon King  wrote:
> 
>> s is what I did now. It is still in the process of building.
> 
> While it was building, I noticed lines such as
>  [python_openid-2.2.5.p0] Found candidate GCC installation:  
> /usr/bin/../lib/gcc/i686-linux-gnu/5.4.0
> 

OK, that’s a curiosity that will have to be investigated.

> Does that mean python_openid will in fact not be build with clang?
> Wouldn't that create a mess?

Depends. Pure C is totally ABI compatible so you can mix
stuff compiled with clang and gcc. C++ is a different beast,
While there is supposed to be some level of ABI compatibility
libstdc++ (GCC) and libcxx (clang) are not interchangeable.
Mixing clang++ and g++ libraries/executables will end up in a 
“total mess".

François

-- 
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 8.2.beta5 released

[François Bissey]

> On 10/02/2018, at 23:49, Simon King <simon.k...@uni-jena.de> wrote:
> 
> Hi François,
> 
> On 2018-02-10, François Bissey <frp.bis...@gmail.com> wrote:
>> I’d recommend to work on a separate clone. It is what I have done
>> on my Gentoo linux box.
> 
> This is what I did now. It is still in the process of building.
> 
> Will the SageMath installation recall that it was installed with clang?
> By that, I mean: What will happen if I do further compilations later,
> either with `sage -b`, `sage -i meataxe` or `make build`? Will all three
> commands automatically use clang? Or would I still need to prepend
> everything with `CC=clang CXX=clang++`?

Sage remembers the compiler it was built with. I saw to that
some times ago as a pre-requisite for clang support.
So once you have configured sage, it will now the compiler it has to
use. And ./sage -i meataxe will just use clang/clang++ if sage
was built with it.

François

-- 
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 8.2.beta5 released

[François Bissey]

> On 10/02/2018, at 22:02, Simon King <simon.k...@uni-jena.de> wrote:
> 
> On 2018-02-10, François Bissey <frp.bis...@gmail.com> wrote:
>> I’d recommend to work on a separate clone. It is what I have done
>> on my Gentoo linux box. I don’t know the state of clang on ubuntu
>> but it is better to have it configured to use libc++ instead of
>> libstdc++ from gcc.
> 
> How? By doing
>  CC=clang CXX=clang++ make -stdlib=libc++
> or what?

It depends on how clang was built and packaged mostly, so hopefully 
just 
CC=clang CXX=clang++ make
is enough.

François

-- 
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 8.2.beta5 released

[François Bissey]

> On 10/02/2018, at 21:25, Simon King  wrote:
> 
> Here are reports that with clang things won't work in different ways
> (e.g., IIUC, segfaults in linbox on openSuse). Does that mean clang is
> buggy resp. not mature enough, or does that mean clang uncovers real
> bugs that are silently ignored by gcc?
> 

Sometimes it uncovers GNUisms. Where you are relying on the behaviour of
the compiler rather than the standard. Bugs, quite possibly, I’d have to
go through the ticket for a memory refresh.
The segfault over linbox I think is because not all installation of clang 
are equal. You can have a full clang with clang’s libc++ for standard c++
library. Or has breed like opensuse where clang use libstdc++ from gcc -
in this case 4.8. I think what’s happening there is that linbox has gone
full c++11 but libstdc++ from gcc-4.8 has only partial support.

> And if I want to give it a try: Currently I have a SageMath installation
> compiled with gcc. Does it suffice to "make clean" before starting
> re-installation of SageMath with clang? Or "make distclean"?

make distclean
definitely.

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

> On 10/02/2018, at 19:40, Justin C. Walker  wrote:
> 
> Thanks for this.  I have
> 
> Apple LLVM version 7.0.2 (clang-700.1.81)
> Target: x86_64-apple-darwin15.6.0
> Thread model: posix
> 
> Is there a fairly straight-forward way to get Apple’s clang at what you're 
> calling 3.8?  

Can you install a newer xcode? Say xcode 8?

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

> On 10/02/2018, at 18:06, kcrisman <kcris...@gmail.com> wrote:
> 
> On Friday, February 9, 2018 at 10:32:49 PM UTC-5, François Bissey wrote:
> We didn’t test clang 3.7 which is what your machine is using at OS X 10.11.
> 
> Would that be the same as this one?  I also have 10.11.
> 
> $ clang --version
> 
> Apple LLVM version 7.3.0 (clang-703.0.31)
> 
> Target: x86_64-apple-darwin15.6.0
> 
> Thread model: posix
> 
> InstalledDir: 
> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
> 

I think so.
 
I know the problem with sqlite, there’s the band aid fix and
then there’s the proper fix which may require a bit of work.

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

We didn’t test clang 3.7 which is what your machine is using at OS X 10.11.
But I recognised the error as one I got in the same place when I tried a build
with icc on linux. Yes that’s a fun bit I haven’t mentioned yet.
You can technically try any compiler that pretends to be gcc - but only clang 
3.8
forward have been tested and I haven’t put in place bits for dealing with icc’s 
fun
issues (over optimisation from icc kills pari).
sqlite wants to use some builtins that are in gcc but identifies the compiler 
supporting
the builtins by a series of pragma. Always risky and a bit porous in this case.

François

> On 10/02/2018, at 12:07, Justin C. Walker  wrote:
> 
> 
>> On Feb 9, 2018, at 00:25 , Volker Braun  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
> 
> Yay for using clang!
> 
> Built from a fresh clone/checkout of the develop tree.
> 
> The build (macOS 10.11.6, MBP Quad-core Core i7) blows chunks on sqlite:
> 
> ==
> libtool: compile:  gcc -DPACKAGE_NAME=\"sqlite\" -DPACKAGE_TARNAME=\"sqlite\" 
> -DPACKAGE_VERSION=\"3.17.0\" "-DPACKAGE_STRING=\"sqlite 3.17.0\
> \"" -DPACKAGE_BUGREPORT=\"http://www.sqlite.org\; -DPACKAGE_URL=\"\" 
> -DPACKAGE=\"sqlite\" -DVERSION=\"3.17.0\" -DSTDC_HEADERS=1 -DHAVE_SYS_T\
> YPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 
> -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 \
> -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DLT_OBJDIR=\".libs/\" -DHAVE_FDATASYNC=1 
> -DHAVE_USLEEP=1 -DHAVE_LOCALTIME_R=1 -DHAVE_GMTIME_R=1 -DHAVE_D\
> ECL_STRERROR_R=1 -DHAVE_STRERROR_R=1 -DHAVE_EDITLINE_READLINE_H=1 
> -DHAVE_EDITLINE=1 -I. -I/Users/Sage/sage-8.2.beta5/local/include -D_REENTR\
> ANT=1 -DSQLITE_THREADSAFE=1 -DSQLITE_ENABLE_FTS3 -DSQLITE_ENABLE_RTREE -g -O2 
> -MT sqlite3.lo -MD -MP -MF .deps/sqlite3.Tpo -c sqlite3.c  -fn\
> o-common -DPIC -o .libs/sqlite3.o
> sqlite3.c:28836:10: error: use of unknown builtin '__builtin_add_overflow' 
> [-Wimplicit-function-declaration]
>  return __builtin_add_overflow(*pA, iB, pA);
> ^
> ==
> 
> sqlite log attached.
> 
> Justin
> 
> -- 
> 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.
> 
> 
> --
> Justin C. Walker
> Director
> Institute for the Enhancement of the Director's Income
> --
> Fame is fleeting, but obscurity
>   just drags on and on.  F
> 
> 
> 
> -- 
> 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.

-- 
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 8.2.beta5 released

[François Bissey]

OK, that’s a slightly different issue. I didn’t think that would be a problem 
but this
package shouldn’t be needed with python3.2+ since it is a backport of 
functionality for
older python. So it would be best not to install it with python3.

> On 10/02/2018, at 05:55, fchapot...@gmail.com wrote:
> 
> I have a build failure in subprocess32 on a python3 build (using export 
> SAGE_PYTHON3=yes)
> 
> 
> [subprocess32-3.2.7] Found local metadata for subprocess32-3.2.7
> [subprocess32-3.2.7] Attempting to download package subprocess32-3.2.7.tar.gz 
> from mirrors
> [subprocess32-3.2.7] 
> http://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/subprocess32/subprocess32-3.2.7.tar.gz
> [subprocess32-3.2.7] 
> [..]
> [subprocess32-3.2.7] subprocess32-3.2.7
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] Setting up build directory for subprocess32-3.2.7
> [subprocess32-3.2.7] Finished extraction
> [subprocess32-3.2.7] No patch files found in ../patches
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] Host system:
> [subprocess32-3.2.7] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu 
> Jan 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] C compiler: gcc
> [subprocess32-3.2.7] C compiler version:
> [subprocess32-3.2.7] Using built-in specs.
> [subprocess32-3.2.7] COLLECT_GCC=gcc
> [subprocess32-3.2.7] 
> COLLECT_LTO_WRAPPER=/home/chapoton/sage3/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
> [subprocess32-3.2.7] Target: x86_64-pc-linux-gnu
> [subprocess32-3.2.7] Configured with: ../src/configure 
> --prefix=/home/chapoton/sage3/local 
> --with-local-prefix=/home/chapoton/sage3/local 
> --with-gmp=/home/chapoton/sage3/local --with-mpfr=/home/chapoton/sage3/local 
> --with-mpc=/home/chapoton/sage3/local --with-system-zlib --disable-multilib 
> --disable-nls --enable-languages=c,c++,fortran --disable-libitm  
> [subprocess32-3.2.7] Thread model: posix
> [subprocess32-3.2.7] gcc version 7.2.0 (GCC) 
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] Installing subprocess32-3.2.7
> [subprocess32-3.2.7] This backport is for Python 2.x only.
> [subprocess32-3.2.7] Error: could not determine package name
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] Error installing subprocess32-3.2.7
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] 
> [subprocess32-3.2.7] real 0m0.131s
> [subprocess32-3.2.7] user 0m0.056s
> [subprocess32-3.2.7] sys  0m0.001s
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] Error installing package subprocess32-3.2.7
> [subprocess32-3.2.7] 
> 
> [subprocess32-3.2.7] Please email sage-devel 
> (http://groups.google.com/group/sage-devel)
> [subprocess32-3.2.7] explaining the problem and including the log file
> [subprocess32-3.2.7]   /home/chapoton/sage3/logs/pkgs/subprocess32-3.2.7.log
> [subprocess32-3.2.7] Describe your computer, operating system, etc.
> [subprocess32-3.2.7] If you want to try to fix the problem yourself, *don't* 
> just cd to
> [subprocess32-3.2.7] 
> /home/chapoton/sage3/local/var/tmp/sage/build/subprocess32-3.2.7 and type 
> 'make' or whatever is appropriate.
> [subprocess32-3.2.7] Instead, the following commands setup all environment 
> variables
> [subprocess32-3.2.7] correctly and load a subshell for you to debug the error:
> [subprocess32-3.2.7]   (cd 
> '/home/chapoton/sage3/local/var/tmp/sage/build/subprocess32-3.2.7' && 
> '/home/chapoton/sage3/sage' --sh)
> [subprocess32-3.2.7] When you are done debugging, you can type "exit" to 
> leave the subshell.
> [subprocess32-3.2.7] 
> 
> Makefile:2950 : la recette pour la cible « 
> /home/chapoton/sage3/local/var/lib/sage/installed/subprocess32-3.2.7 » a 
> échouée
> make[2]: *** 
> [/home/chapoton/sage3/local/var/lib/sage/installed/subprocess32-3.2.7] Erreur 
> 1
> 
> 
> 
> Le vendredi 9 février 2018 09:25:28 UTC+1, Volker Braun a écrit :
> 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
> 
> e6cae6d88d (tag: 8.2.beta5, trac/develop) Updated SageMath version to 
> 8.2.beta5
> 9dd4282d36 Trac #24660: Memory leak in SubgraphSearch
> b9aa268ecd Trac #24639: Enumerating greedy linear extensions
> c795e950c9 Trac #24636: Rivin's test for circumcribability and inscribability
> 

Re: [sage-release] Re: Sage 8.2.beta5 released

[François Bissey]

Actually if you have the autotools packages installed (from the system or sage)
can you try 
autoreconf -i
then re-run configure and see if that fix it. 

> On 10/02/2018, at 00:02, François Bissey <frp.bis...@gmail.com> wrote:
> 
> Which version of ubuntu? We have seen an instance of that problem during 
> review
> but we thought it was fixed. OK, there was something nagging me but it looked 
> fixed on the patchbot.
> 
>> On 9/02/2018, at 23:56, fchapot...@gmail.com wrote:
>> 
>> An incremental build from previous beta fails on gfortran :
>> 
>> [gfortran-7.2.0] Found local metadata for gfortran-7.2.0
>> [gfortran-7.2.0] Using cached file 
>> /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz
>> [gfortran-7.2.0] gfortran-7.2.0
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] Setting up build directory for gfortran-7.2.0
>> [gfortran-7.2.0] Finished extraction
>> [gfortran-7.2.0] No patch files found in ../patches
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] Host system:
>> [gfortran-7.2.0] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 
>> 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] C compiler: gcc
>> [gfortran-7.2.0] C compiler version:
>> [gfortran-7.2.0] Using built-in specs.
>> [gfortran-7.2.0] COLLECT_GCC=gcc
>> [gfortran-7.2.0] 
>> COLLECT_LTO_WRAPPER=/home/chapoton/sage/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
>> [gfortran-7.2.0] Target: x86_64-pc-linux-gnu
>> [gfortran-7.2.0] Configured with: ../src/configure 
>> --prefix=/home/chapoton/sage/local 
>> --with-local-prefix=/home/chapoton/sage/local 
>> --with-gmp=/home/chapoton/sage/local --with-mpfr=/home/chapoton/sage/local 
>> --with-mpc=/home/chapoton/sage/local --with-system-zlib --disable-multilib 
>> --disable-nls --enable-languages=c,c++,fortran --disable-libitm  
>> [gfortran-7.2.0] Thread model: posix
>> [gfortran-7.2.0] gcc version 7.2.0 (GCC) 
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] Error: gcc is already installed
>> [gfortran-7.2.0] 
>> [gfortran-7.2.0] real0m0.003s
>> [gfortran-7.2.0] user0m0.004s
>> [gfortran-7.2.0] sys 0m0.000s
>> [gfortran-7.2.0] 
>> 
>> [gfortran-7.2.0] Error installing package gfortran-7.2.0
>> [gfortran-7.2.0] 
>> 
>> 
>> 
>> Le vendredi 9 février 2018 09:25:28 UTC+1, Volker Braun a écrit :
>> 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
>> 
>> e6cae6d88d (tag: 8.2.beta5, trac/develop) Updated SageMath version to 
>> 8.2.beta5
>> 9dd4282d36 Trac #24660: Memory leak in SubgraphSearch
>> b9aa268ecd Trac #24639: Enumerating greedy linear extensions
>> c795e950c9 Trac #24636: Rivin's test for circumcribability and inscribability
>> d70b6a253a Trac #24629: fix R build on Solaris 11
>> 4f53f24d1f Trac #24628: Build PCRE without JIT if needed
>> 867f4c9761 Trac #24618: fplll fails to build on SunOS
>> 92ac632d04 Trac #24611: Singular fails to build on SunOS
>> ac14d82c6f Trac #24590: bug in inverse_image of module homomorphism
>> 38e8a65eec Trac #24313: py3: fixes to sage.misc.temporary_file
>> b899601826 Trac #24239: Implement soliton cellular automata
>> 7d0ca44142 Trac #24139: Allow baseline to be given as part of ascii_art and 
>> unicode_art
>> 94da5b67c1 Trac #24656: Fix bug in type E bijection from cythonizing 
>> RiggedPartition
>> e8c626f7da Trac #24615: interface libgap floats
>> 9c146ffcb2 Trac #24608: Remove deprecated PowerSeries._floordiv_
>> 6b689d3bfa Trac #23978: Rich comparison for Modules
>> 70c254125d Trac #24634: add .is_polyhedral method to graphs
>> 2d1615636e Trac #24175: Optimizations to generating rigged configurations
>> 7be8a667e9 Trac #24141: Optimizations to Kleber tree
>> 8a2e3ed425 Trac #24035: Normal forms for TorsionQuadraticModules
>> 9b223d74de Trac #24633: Add jump count for a linear extension
>> 0da6392254 Trac #24632: Add is_greedy() to linear extension.
>> e185837226 Trac #24631: Faster jump number for posets
>> 4387613c32 Trac #24619: giac fails to build on SunOS
>> 58fdd676a4 Trac #24516: Cygwin test failures in lseries

Re: [sage-release] Re: Sage 8.2.beta5 released

[François Bissey]

Which version of ubuntu? We have seen an instance of that problem during review
but we thought it was fixed. OK, there was something nagging me but it looked 
fixed on the patchbot.

> On 9/02/2018, at 23:56, fchapot...@gmail.com wrote:
> 
> An incremental build from previous beta fails on gfortran :
> 
> [gfortran-7.2.0] Found local metadata for gfortran-7.2.0
> [gfortran-7.2.0] Using cached file 
> /home/chapoton/sage/upstream/gcc-7.2.0.tar.xz
> [gfortran-7.2.0] gfortran-7.2.0
> [gfortran-7.2.0] 
> [gfortran-7.2.0] Setting up build directory for gfortran-7.2.0
> [gfortran-7.2.0] Finished extraction
> [gfortran-7.2.0] No patch files found in ../patches
> [gfortran-7.2.0] 
> [gfortran-7.2.0] Host system:
> [gfortran-7.2.0] Linux pc-chapoton 4.13.0-32-generic #35-Ubuntu SMP Thu Jan 
> 25 09:13:46 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
> [gfortran-7.2.0] 
> [gfortran-7.2.0] C compiler: gcc
> [gfortran-7.2.0] C compiler version:
> [gfortran-7.2.0] Using built-in specs.
> [gfortran-7.2.0] COLLECT_GCC=gcc
> [gfortran-7.2.0] 
> COLLECT_LTO_WRAPPER=/home/chapoton/sage/local/libexec/gcc/x86_64-pc-linux-gnu/7.2.0/lto-wrapper
> [gfortran-7.2.0] Target: x86_64-pc-linux-gnu
> [gfortran-7.2.0] Configured with: ../src/configure 
> --prefix=/home/chapoton/sage/local 
> --with-local-prefix=/home/chapoton/sage/local 
> --with-gmp=/home/chapoton/sage/local --with-mpfr=/home/chapoton/sage/local 
> --with-mpc=/home/chapoton/sage/local --with-system-zlib --disable-multilib 
> --disable-nls --enable-languages=c,c++,fortran --disable-libitm  
> [gfortran-7.2.0] Thread model: posix
> [gfortran-7.2.0] gcc version 7.2.0 (GCC) 
> [gfortran-7.2.0] 
> [gfortran-7.2.0] Error: gcc is already installed
> [gfortran-7.2.0] 
> [gfortran-7.2.0] real 0m0.003s
> [gfortran-7.2.0] user 0m0.004s
> [gfortran-7.2.0] sys  0m0.000s
> [gfortran-7.2.0] 
> 
> [gfortran-7.2.0] Error installing package gfortran-7.2.0
> [gfortran-7.2.0] 
> 
> 
> 
> Le vendredi 9 février 2018 09:25:28 UTC+1, Volker Braun a écrit :
> 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
> 
> e6cae6d88d (tag: 8.2.beta5, trac/develop) Updated SageMath version to 
> 8.2.beta5
> 9dd4282d36 Trac #24660: Memory leak in SubgraphSearch
> b9aa268ecd Trac #24639: Enumerating greedy linear extensions
> c795e950c9 Trac #24636: Rivin's test for circumcribability and inscribability
> d70b6a253a Trac #24629: fix R build on Solaris 11
> 4f53f24d1f Trac #24628: Build PCRE without JIT if needed
> 867f4c9761 Trac #24618: fplll fails to build on SunOS
> 92ac632d04 Trac #24611: Singular fails to build on SunOS
> ac14d82c6f Trac #24590: bug in inverse_image of module homomorphism
> 38e8a65eec Trac #24313: py3: fixes to sage.misc.temporary_file
> b899601826 Trac #24239: Implement soliton cellular automata
> 7d0ca44142 Trac #24139: Allow baseline to be given as part of ascii_art and 
> unicode_art
> 94da5b67c1 Trac #24656: Fix bug in type E bijection from cythonizing 
> RiggedPartition
> e8c626f7da Trac #24615: interface libgap floats
> 9c146ffcb2 Trac #24608: Remove deprecated PowerSeries._floordiv_
> 6b689d3bfa Trac #23978: Rich comparison for Modules
> 70c254125d Trac #24634: add .is_polyhedral method to graphs
> 2d1615636e Trac #24175: Optimizations to generating rigged configurations
> 7be8a667e9 Trac #24141: Optimizations to Kleber tree
> 8a2e3ed425 Trac #24035: Normal forms for TorsionQuadraticModules
> 9b223d74de Trac #24633: Add jump count for a linear extension
> 0da6392254 Trac #24632: Add is_greedy() to linear extension.
> e185837226 Trac #24631: Faster jump number for posets
> 4387613c32 Trac #24619: giac fails to build on SunOS
> 58fdd676a4 Trac #24516: Cygwin test failures in lseries_ell
> ab3c1c8da7 Trac #24411: Move gamma functions into their own file
> 79f648c706 Trac #23714: GAP matrices
> 295b129a35 Trac #22921: Implementation of shifted tableaux
> c5248314f7 Trac #24625: Some small improvements to polynomial_complex_arb
> d842b25062 Trac #24624: Stop using new_t_POL_from_int_star from cypari2
> 75e3f2960a Trac #24617: Infinite process recursion with Solaris make
> bb2b730403 Trac #24614: Deprecate args of Parent_old.__init__
> 505af6e57c Trac #24613: Remove actions from old coercion model
> b200dbae27 Trac #24610: Change richcmp() to a cpdef inline function
> 2a71f44dae Trac #24607: Add abstract _add_ and _mul_ methods to RingElement
> 6296a31f22 Trac #24606: Forgotten check_error in maxima spkg-install
> f5259142ff Trac #24602: upgrade iconv to 1.15
> e7fe097bf3 Trac #24597: Properly set 

Re: [sage-release] Sage 8.2.beta5 released

[François Bissey]

> On 9/02/2018, at 23:03, Ralf Stephan  wrote:
> 
> So how to use clang on Linux?

CC=clang CXX=clang++ make

Adjust to the peculiarity of your install in terms of PATH and compiler
names.

François

-- 
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] Sage 8.2.beta5 released

[François Bissey]

Note that from this release a fresh build on OS X will use clang.
Building gcc and using it can be triggered with SAGE_INSTALL_GCC=yes
as usual.
Incremental upgrade will continue to use the previously configured compiler.
Feedback on optional packages that are broken by the move appreciated.

François

> On 9/02/2018, at 21:25, Volker Braun  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
> 
> e6cae6d88d (tag: 8.2.beta5, trac/develop) Updated SageMath version to 
> 8.2.beta5
> 9dd4282d36 Trac #24660: Memory leak in SubgraphSearch
> b9aa268ecd Trac #24639: Enumerating greedy linear extensions
> c795e950c9 Trac #24636: Rivin's test for circumcribability and inscribability
> d70b6a253a Trac #24629: fix R build on Solaris 11
> 4f53f24d1f Trac #24628: Build PCRE without JIT if needed
> 867f4c9761 Trac #24618: fplll fails to build on SunOS
> 92ac632d04 Trac #24611: Singular fails to build on SunOS
> ac14d82c6f Trac #24590: bug in inverse_image of module homomorphism
> 38e8a65eec Trac #24313: py3: fixes to sage.misc.temporary_file
> b899601826 Trac #24239: Implement soliton cellular automata
> 7d0ca44142 Trac #24139: Allow baseline to be given as part of ascii_art and 
> unicode_art
> 94da5b67c1 Trac #24656: Fix bug in type E bijection from cythonizing 
> RiggedPartition
> e8c626f7da Trac #24615: interface libgap floats
> 9c146ffcb2 Trac #24608: Remove deprecated PowerSeries._floordiv_
> 6b689d3bfa Trac #23978: Rich comparison for Modules
> 70c254125d Trac #24634: add .is_polyhedral method to graphs
> 2d1615636e Trac #24175: Optimizations to generating rigged configurations
> 7be8a667e9 Trac #24141: Optimizations to Kleber tree
> 8a2e3ed425 Trac #24035: Normal forms for TorsionQuadraticModules
> 9b223d74de Trac #24633: Add jump count for a linear extension
> 0da6392254 Trac #24632: Add is_greedy() to linear extension.
> e185837226 Trac #24631: Faster jump number for posets
> 4387613c32 Trac #24619: giac fails to build on SunOS
> 58fdd676a4 Trac #24516: Cygwin test failures in lseries_ell
> ab3c1c8da7 Trac #24411: Move gamma functions into their own file
> 79f648c706 Trac #23714: GAP matrices
> 295b129a35 Trac #22921: Implementation of shifted tableaux
> c5248314f7 Trac #24625: Some small improvements to polynomial_complex_arb
> d842b25062 Trac #24624: Stop using new_t_POL_from_int_star from cypari2
> 75e3f2960a Trac #24617: Infinite process recursion with Solaris make
> bb2b730403 Trac #24614: Deprecate args of Parent_old.__init__
> 505af6e57c Trac #24613: Remove actions from old coercion model
> b200dbae27 Trac #24610: Change richcmp() to a cpdef inline function
> 2a71f44dae Trac #24607: Add abstract _add_ and _mul_ methods to RingElement
> 6296a31f22 Trac #24606: Forgotten check_error in maxima spkg-install
> f5259142ff Trac #24602: upgrade iconv to 1.15
> e7fe097bf3 Trac #24597: Properly set LD_LIBRARY_PATH in spkg-build for 
> python2/3 on SunOS
> 69951df4c2 Trac #24584: Add the power poset
> 8e3fde343d Trac #24431: Fix coercions and pushout for Laurent series
> f313460743 Trac #24381: New Parent method _convert_method_map
> 9f2efaef78 Trac #24357: Two bugs in NumberField.composite_fields()
> 56c322343a Trac #24223: py3: several string conversion fixes
> b79f27f2c6 Trac #24071: Improve docstring of MPolynomial_libsingular.reduce()
> 950bdd8145 Trac #23696: Update matplotlib to 2.1.0
> 36849d6c3e Trac #22928: Conversion between gmpy2 and sage objects
> 5473d304bb Trac #5574: Implement QQbar^QQ as action
> 129faa0c39 Trac #24599: Internal compiler error when compiling giac-1.4.9.45 
> with gcc-7.2.0
> 07f53b23c4 Trac #24600: another typo ticket
> 52cd6b86d0 Trac #24563: Workaround for small race condition in parallel 
> doctest runner
> 80fecaaf95 Trac #24418: Doctest: bug 
> numerical_approx(2^(450232897/4888643760))
> 919ef40bb8 Trac #21092: Unhandled case in EllipticCurve_from_cubic
> a3ee07f891 Trac #12426: Make Sage build with clang (3.7+) and make it the 
> default on OS X
> ed50684b29 Trac #24517: random failure in sage/geometry/cone.py
> 0a674fd488 (tag: 8.2.beta4) Updated SageMath version to 8.2.beta4
> 
> 
> -- 
> 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.

-- 
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 

Re: [sage-release] Sage 8.2.beta4 released

[François Bissey]

David Coudert got that (on sage-devel I think). Turns out the libpng
install was broken for some reason and was missing libpng.so.
./sage -f libpng
solves this. But you are the second person reporting this which 
makes it suspicious. Is something out there deleting libpng.so?

François

> On 31/01/2018, at 01:34, Erik Bray <erik.m.b...@gmail.com> wrote:
> 
> On Sun, Jan 28, 2018 at 8:17 AM, Ralf Stephan <gtrw...@gmail.com> wrote:
>> This is https://trac.sagemath.org/ticket/24599
>> I'm trying now with the system gcc.
> 
> I don't have this problem on Ubuntu but I am getting:
> 
> [giac-1.4.9.45] libtool: link: g++ -g -O2 -fno-strict-aliasing
> -DGIAC_GENERIC_CONSTANTS -Wl,-rpath
> -Wl,/home/embray/src/sagemath/sage/local/lib -o .libs/icas icas.o
> -L/home/embray/src/sagemath/sage/local/lib ./.libs/libxcas.a
> /home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so
> -lntl -lpari -lreadline -lgsl -lgslcblas -lrt -lpthread -lglpk -ldl
> -lpng -lm -lmpfi /home/embray/src/sagemath/sage/local/lib/libmpfr.so
> -lgmp -Wl,-rpath -Wl,/home/embray/src/sagemath/sage/local/lib
> [giac-1.4.9.45]
> /home/embray/src/sagemath/sage/local/var/tmp/sage/build/giac-1.4.9.45/src/src/.libs/libgiac.so:
> undefined reference to `png_set_longjmp_fn'
> [giac-1.4.9.45] collect2: error: ld returned 1 exit status
> 
> 
> So this has rendered this beta unbuildable for me.
> 
> 
>> On Sun, Jan 28, 2018 at 8:09 AM François Bissey <frp.bis...@gmail.com>
>> wrote:
>>> 
>>> I was going to warn sage-on-gentoo users on this interesting fact that I
>>> experienced
>>> on the experimental branch where I track stuff that Volker merges.
>>> It is probably an issue in giac, but at the end of the day gcc needs to be
>>> rebuilt
>>> after mpfr/mpc. I didn’t think about the problem of what happens when you
>>> use
>>> the host gcc in vanilla sage though.
>>> You may have to build sage’s gcc - or use clang once support is merged :)
>>> 
>>> François
>>> 
>>>> On 28/01/2018, at 20:02, Ralf Stephan <gtrw...@gmail.com> wrote:
>>>> 
>>>> Compiling giac with the gcc installed by Sage (7.2.0) gives an internal
>>>> compiler error:
>>>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>>>> -I.. -I/h
>>>> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>>>> -I/home/ralf/
>>>> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>>>> solve.lo -M
>>>> D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
>>>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I.
>>>> -I.. -I/h
>>>> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include
>>>> -I/home/ralf/
>>>> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT
>>>> derive.lo -
>>>> MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
>>>> init2.c:52: MPFR assertion failed: p >= 2 && p <=
>>>> ((mpfr_prec_t)((mpfr_uprec_t)(
>>>> ~(mpfr_uprec_t)0)>>1))
>>>> modpoly.cc: In function 'std::complex giac::horner_newton(const
>>>> vecteur&
>>>> , const std::complex&, const giac::context*)':
>>>> modpoly.cc:5035:19: internal compiler error: Aborted
>>>>   complex horner_newton(const vecteur & p,const
>>>> std::complex 
>>>> ,GIAC_CONTEXT){
>>>>   ^
>>>> 0xafbc6f crash_signal
>>>>../../src/gcc/toplev.c:337
>>>> 0x7f3e0cfeedd3 mpfr_assert_fail
>>>> 
>>>> /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
>>>> c:305
>>>> 0x7f3e0cfe59c1 mpfr_init2
>>>> 
>>>> /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
>>>> 2
>>>> 0x7f3e0d21b472 mpc_div_zero
>>>> 
>>>> /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:31
>>>> 0x7f3e0d21b472 mpc_div
>>>> 
>>>> /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:257
>>>> 0x77b6b9 do_mpc_arg2(tree_node*, tree_node*, tree_node*, int, int
>>>> (*)(__mpc_stru
>>>> ct*, __mpc_struct const*, __mpc_struct const*, int))
>>>>../../src/gcc/builtins.c:10179
>>>> 0x8afa0a const_binop
>>>>../../src/gcc/fold-const.c:1316
>>>>

Re: [sage-release] Sage 8.2.beta4 released

[François Bissey]

Interesting question and I don’t know. I only know that the failure comes
from mpfr_assert_fail in mpfr-3 code as indicated by your log. 
What else, there was a change of soname which means that there are 
incompatibilities
between mpfr-3 and mpfr-4 and that is probably at play here. 
None of the other standard packages using mpfr trigger an ICE under the same 
condition 
(the only package for which I don’t know for sure is sage itself because you 
have to
rebuild giac first). So I think giac may be using some mpfr construct 
improperly or some
that should be private.

François

> On 28/01/2018, at 20:32, Ralf Stephan  wrote:
> 
> How can an internal compiler error have some other source code as root cause?

-- 
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] Sage 8.2.beta4 released

[François Bissey]

I made some comments in the ticket. In my initial answer I assumed you were
using the host gcc rather than sage’s one. But I wouldn’t be surprised if there
was a problem when using a host gcc compiled against mpfr-3.x. 
This needs to be tested.
While rebuilding gcc get rid of the ICE, I think the root cause of the problem 
is
in giac. It is the only package that gives ICE after mpfr upgrade as far as I 
know.
All the other packages that depend on mpfr in sage don’t give rise to that 
error.

François

> On 28/01/2018, at 20:19, Ralf Stephan <gtrw...@gmail.com> wrote:
> 
> Doesn't this simply make internal gcc a dependency? If so then is it enough 
> to change that for the above ticket?
> 
> On Sun, Jan 28, 2018 at 8:17 AM Ralf Stephan <gtrw...@gmail.com> wrote:
> This is https://trac.sagemath.org/ticket/24599
> I'm trying now with the system gcc.
> 
> On Sun, Jan 28, 2018 at 8:09 AM François Bissey <frp.bis...@gmail.com> wrote:
> I was going to warn sage-on-gentoo users on this interesting fact that I 
> experienced
> on the experimental branch where I track stuff that Volker merges.
> It is probably an issue in giac, but at the end of the day gcc needs to be 
> rebuilt
> after mpfr/mpc. I didn’t think about the problem of what happens when you use
> the host gcc in vanilla sage though.
> You may have to build sage’s gcc - or use clang once support is merged :)
> 
> François
> 
> > On 28/01/2018, at 20:02, Ralf Stephan <gtrw...@gmail.com> wrote:
> >
> > Compiling giac with the gcc installed by Sage (7.2.0) gives an internal 
> > compiler error:
> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I. -I.. 
> > -I/h
> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include 
> > -I/home/ralf/
> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT 
> > solve.lo -M
> > D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
> > libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I. -I.. 
> > -I/h
> > ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include 
> > -I/home/ralf/
> > sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT 
> > derive.lo -
> > MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
> > init2.c:52: MPFR assertion failed: p >= 2 && p <= 
> > ((mpfr_prec_t)((mpfr_uprec_t)(
> > ~(mpfr_uprec_t)0)>>1))
> > modpoly.cc: In function 'std::complex giac::horner_newton(const 
> > vecteur&
> > , const std::complex&, const giac::context*)':
> > modpoly.cc:5035:19: internal compiler error: Aborted
> >complex horner_newton(const vecteur & p,const 
> > std::complex 
> > ,GIAC_CONTEXT){
> >^
> > 0xafbc6f crash_signal
> > ../../src/gcc/toplev.c:337
> > 0x7f3e0cfeedd3 mpfr_assert_fail
> > 
> > /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
> > c:305
> > 0x7f3e0cfe59c1 mpfr_init2
> > 
> > /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
> > 2
> > 0x7f3e0d21b472 mpc_div_zero
> > /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:31
> > 0x7f3e0d21b472 mpc_div
> > /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:257
> > 0x77b6b9 do_mpc_arg2(tree_node*, tree_node*, tree_node*, int, int 
> > (*)(__mpc_stru
> > ct*, __mpc_struct const*, __mpc_struct const*, int))
> > ../../src/gcc/builtins.c:10179
> > 0x8afa0a const_binop
> > ../../src/gcc/fold-const.c:1316
> > 0x8b0c5e const_binop(tree_code, tree_node*, tree_node*, tree_node*)
> > ../../src/gcc/fold-const.c:1565
> > 0xdb4962 gimple_resimplify2(gimple**, code_helper*, tree_node*, 
> > tree_node**, tre
> > e_node* (*)(tree_node*))
> > ../../src/gcc/gimple-match-head.c:132
> > 0xe384b0 gimple_simplify(gimple*, code_helper*, tree_node**, gimple**, 
> > tree_node
> > * (*)(tree_node*), tree_node* (*)(tree_node*))
> > ../../src/gcc/gimple-match-head.c:642
> > 0x8e4306 fold_stmt_1
> > ../../src/gcc/gimple-fold.c:4362
> > 0xbdb5ff execute
> > ../../src/gcc/tree-ssa-forwprop.c:2391
> > Please submit a full bug report,
> > with preprocessed source if appropriate
> >
> > The complete log is attached. System is OpenSuSE 42.3.
> >
> > On Sun, Jan 28, 2018 at 1:08 AM Volker Braun <vbraun.n...@gmail.com> wrote:
> > As always, you can get the latest beta version from the "develop" git 
> > bran

Re: [sage-release] Sage 8.2.beta4 released

[François Bissey]

I was going to warn sage-on-gentoo users on this interesting fact that I 
experienced
on the experimental branch where I track stuff that Volker merges.
It is probably an issue in giac, but at the end of the day gcc needs to be 
rebuilt
after mpfr/mpc. I didn’t think about the problem of what happens when you use
the host gcc in vanilla sage though.
You may have to build sage’s gcc - or use clang once support is merged :)

François

> On 28/01/2018, at 20:02, Ralf Stephan  wrote:
> 
> Compiling giac with the gcc installed by Sage (7.2.0) gives an internal 
> compiler error:
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I. -I.. 
> -I/h
> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include 
> -I/home/ralf/
> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT solve.lo 
> -M
> D -MP -MF .deps/solve.Tpo -c solve.cc  -fPIC -DPIC -o .libs/solve.o
> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -DIN_GIAC -I. -I.. -I. -I.. 
> -I/h
> ome/ralf/sage/local/include -g -O2 -I/home/ralf/sage/local/include 
> -I/home/ralf/
> sage/local/include -fno-strict-aliasing -DGIAC_GENERIC_CONSTANTS -MT 
> derive.lo -
> MD -MP -MF .deps/derive.Tpo -c derive.cc -o derive.o >/dev/null 2>&1
> init2.c:52: MPFR assertion failed: p >= 2 && p <= 
> ((mpfr_prec_t)((mpfr_uprec_t)(
> ~(mpfr_uprec_t)0)>>1))
> modpoly.cc: In function 'std::complex giac::horner_newton(const 
> vecteur&
> , const std::complex&, const giac::context*)':
> modpoly.cc:5035:19: internal compiler error: Aborted
>complex horner_newton(const vecteur & p,const std::complex 
> 
> ,GIAC_CONTEXT){
>^
> 0xafbc6f crash_signal
> ../../src/gcc/toplev.c:337
> 0x7f3e0cfeedd3 mpfr_assert_fail
> 
> /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/mpfr-gmp.
> c:305
> 0x7f3e0cfe59c1 mpfr_init2
> 
> /home/ralf/sage/local/var/tmp/sage/build/mpfr-3.1.5.p0/src/src/init2.c:5
> 2
> 0x7f3e0d21b472 mpc_div_zero
> /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:31
> 0x7f3e0d21b472 mpc_div
> /home/ralf/sage/local/var/tmp/sage/build/mpc-1.1.0/src/src/div.c:257
> 0x77b6b9 do_mpc_arg2(tree_node*, tree_node*, tree_node*, int, int 
> (*)(__mpc_stru
> ct*, __mpc_struct const*, __mpc_struct const*, int))
> ../../src/gcc/builtins.c:10179
> 0x8afa0a const_binop
> ../../src/gcc/fold-const.c:1316
> 0x8b0c5e const_binop(tree_code, tree_node*, tree_node*, tree_node*)
> ../../src/gcc/fold-const.c:1565
> 0xdb4962 gimple_resimplify2(gimple**, code_helper*, tree_node*, tree_node**, 
> tre
> e_node* (*)(tree_node*))
> ../../src/gcc/gimple-match-head.c:132
> 0xe384b0 gimple_simplify(gimple*, code_helper*, tree_node**, gimple**, 
> tree_node
> * (*)(tree_node*), tree_node* (*)(tree_node*))
> ../../src/gcc/gimple-match-head.c:642
> 0x8e4306 fold_stmt_1
> ../../src/gcc/gimple-fold.c:4362
> 0xbdb5ff execute
> ../../src/gcc/tree-ssa-forwprop.c:2391
> Please submit a full bug report,
> with preprocessed source if appropriate
> 
> The complete log is attached. System is OpenSuSE 42.3.
> 
> On Sun, Jan 28, 2018 at 1:08 AM Volker Braun  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
> 
> 0a674fd488 (tag: 8.2.beta4, trac/develop) Updated SageMath version to 
> 8.2.beta4
> 4d966299d9 Trac #24581: more typos
> 59b6f2aff8 Trac #24580: some typos (various)
> 3e3b72af47 Trac #24592: "./sage -f" should clean first before building the 
> toolchain
> e486b8d5b7 Trac #24586: packages whose type is "script" must have executable 
> spkg-install
> dfa00046c8 Trac #24579: Don't install gfortran by default
> 9396336c09 Trac #24570: py3: using the new tags py3 and py2 in some rst files
> d6c9aed908 Trac #24566: BooleanFunction evaluated on Integer computes 
> IndexError wrongly
> cb4e6a68ce Trac #24548: py3: various details
> d54fe681fd Trac #24487: add one example with picture to the doc of list_plot3d
> 7d56dfbec4 Trac #24174: Upgrade giac to 1.4.9-45
> 35188851e1 Trac #23848: py3: some conversions from bytes to utf8
> b5b1e208b4 Trac #22170: plot3d : the option "mesh=True" does not work in 
> Jupyter
> 03a1d71600 Trac #19547: Document  options to hide labels in ToricPloter
> 70e5eae8d3 Trac #2153: [with bundle, needs additional review] Defined Hom 
> parent of group homomorphisms.
> 50e7153e59 Trac #24529: Upgrade some Jupyter packages
> c44a86fc1e Trac #24512: fix plotting of WheelGraph(n) for n<4
> ab59b8df29 Trac #24574: p3  : get rid of __cmp__ for words
> 0d5f9274c1 Trac #24572: py3: some more care for map
> 13585a4c7e Trac #24569: py3 : caring for range again
> 2a38ead995 Trac #24558: exception when creating tensor product
> c4dcef94e0 Trac #24565: small cleanup of abstract tree
> 115b43f467 Trac #23418: put number fields in 

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

[François Bissey]

What about something like PKG_CONFIG_PATH?

> On 10/01/2018, at 11:40, Samuel Lelièvre <samuel.lelie...@gmail.com> wrote:
> 
> Thanks François for spotting that.  I am indeed using Homebrew.
> But before the build I set the PATH to avoid /usr/local:
> 
> $ export PATH='/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin'
> 
> so I'm surprised anything from /usr/local gets picked up.
> 
> Samuel
> 
> 2018-01-09 12:47 GMT-06:00 François Bissey <frp.bis...@gmail.com>:
> It’s picking up an installation of webs in /usr/local
> gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wno-unused 
> -DHAVE_WEBPMUX -I/opt/s/sage-8.2.beta2/local/include/freetype2 
> -I/opt/s/sage-8.2.beta2/local/var/tmp/sage/build/pillow-3.3.0/src/libImaging 
> -I/opt/s/sage-8.2.beta2/local/include -I/opt/local/include -I/opt/X11/include 
> -I/usr/local/include -I/usr/include 
> -I/opt/s/sage-8.2.beta2/local/include/python2.7 -c _webp.c -o 
> build/temp.macosx-10.9-x86_64-2.7/_webp.o
> In file included from _webp.c:9:0:
> /usr/local/include/webp/mux.h:101:13: error: expected '=', ',', ';', 'asm' or 
> '__attribute__' before 'int'
>  WEBP_EXTERN int WebPGetMuxVersion(void);
>  ^~~
> /usr/local/include/webp/mux.h:107:1: error: unknown type name 'WEBP_EXTERN'
>  WEBP_EXTERN WebPMux* WebPNewInternal(int);
>  ^~~
> /usr/local/include/webp/mux.h:107:20: error: expected '=', ',', ';', 'asm' or 
> '__attribute__' before '*' token
>  WEBP_EXTERN WebPMux* WebPNewInternal(int);
> 
> 
> using brew?
> 
> François
> 
> > On 10/01/2018, at 03:08, Samuel Lelièvre <samuel.lelie...@gmail.com> wrote:
> >
> >
> > Under macOS 10.10.5, the build failed on pillow-3.3.0.
> >
> > http://www.math.u-psud.fr/~lelievre/t/install.log
> > http://www.math.u-psud.fr/~lelievre/t/pillow-3.3.0.log
> >
> > --
> > 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.
> 
> --
> 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.
> 
> 
> -- 
> 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.

-- 
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] Sage 8.2.beta2 released

[François Bissey]

It’s picking up an installation of webs in /usr/local
gcc -fno-strict-aliasing -g -O2 -DNDEBUG -g -fwrapv -O3 -Wall -Wno-unused 
-DHAVE_WEBPMUX -I/opt/s/sage-8.2.beta2/local/include/freetype2 
-I/opt/s/sage-8.2.beta2/local/var/tmp/sage/build/pillow-3.3.0/src/libImaging 
-I/opt/s/sage-8.2.beta2/local/include -I/opt/local/include -I/opt/X11/include 
-I/usr/local/include -I/usr/include 
-I/opt/s/sage-8.2.beta2/local/include/python2.7 -c _webp.c -o 
build/temp.macosx-10.9-x86_64-2.7/_webp.o
In file included from _webp.c:9:0:
/usr/local/include/webp/mux.h:101:13: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before 'int'
 WEBP_EXTERN int WebPGetMuxVersion(void);
 ^~~
/usr/local/include/webp/mux.h:107:1: error: unknown type name 'WEBP_EXTERN'
 WEBP_EXTERN WebPMux* WebPNewInternal(int);
 ^~~
/usr/local/include/webp/mux.h:107:20: error: expected '=', ',', ';', 'asm' or 
'__attribute__' before '*' token
 WEBP_EXTERN WebPMux* WebPNewInternal(int);


using brew?

François

> On 10/01/2018, at 03:08, Samuel Lelièvre  wrote:
> 
> 
> Under macOS 10.10.5, the build failed on pillow-3.3.0.
> 
> http://www.math.u-psud.fr/~lelievre/t/install.log
> http://www.math.u-psud.fr/~lelievre/t/pillow-3.3.0.log
> 
> -- 
> 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.

-- 
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] Sage 8.2.beta0 released

[François Bissey]

I am sure I could get it directly from trac. It is just more convenient
from github when you started with a clone from the github repo.
And my live ebuilds also point to Github, I could point the one
that make sense to trac I guess.

François 

> On 14/12/2017, at 22:30, Dima Pasechnik <dimp...@gmail.com> wrote:
> 
> 
> 
> On Wednesday, December 13, 2017 at 11:28:29 PM UTC, François Bissey wrote:
> Can we have an updated develop branch on github? 
> 
> in case, you can pull from here: https://github.com/dimpase/sagetrac-mirror
> 
>  
> François 
> 
> > On 14/12/2017, at 12:03, 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 
> > 
> > 8d9c008a75 (tag: 8.2.beta0, trac/develop) Updated SageMath version to 
> > 8.2.beta0 
> > e78d369799 Trac #24347: make Coxeter matrix groups know when they are 
> > commutative 
> > ac7b04159f Trac #24338: Remove pari_mod finite field implementation 
> > 42faeb8cae Trac #24336: In Cython modules, always *c*import parent 
> > 0bd3ef3112 Trac #24328: New module to implement generic_power 
> > 46ab140520 Trac #24325: manifolds: failing tests in options 
> > 2cbaa17071 Trac #24322: Use new-style GlobalOptions 
> > e71dc43bfb Trac #24318: Conversion failure CBF -> CDF 
> > 34a69e72f9 Trac #24311: fix algdep when it finds a constant polynomial 
> > 0efa5ebb88 Trac #24308: accept polynomial ring to not implement 
> > characteristic for powering 
> > a5321f9d74 Trac #24307: links to github sagetex repo 
> > 48095031fe Trac #24298: Improve Morphism.is_identity() 
> > d1f59e6aeb Trac #24293: Use integer_check_long to implement Integer.__mod__ 
> > d386ef1002 Trac #24287: Issue with vertex cover for graphs with multiple 
> > edges 
> > b5e1445d08 Trac #24285: cleaning reall and complex balls 
> > 637ec22f43 Trac #24282: BooleanFunction.truth_table(format="hex") returns 
> > wrong values 
> > 83527e8e57 Trac #24281: Fix comparison of morphisms 
> > ff624e8e96 Trac #24278: Simplify RingHomset_generic.__call__ 
> > 5670b5d3f1 Trac #24276: Fix categories/examples/semigroups_cython.pyx 
> > 13710a98d6 Trac #24274: Fix bare "except:" statements 
> > b797dd7dc4 Trac #24271: py3: allow flexibility in exception message 
> > formatting in doctests on Python 3 
> > e5cbdd8352 Trac #24270: Fix compiler warnings involving 
> > debug.refine_category_hash_check 
> > a2dce0 Trac #24267: Fix newton_sqrt() method 
> > c79bf6ed78 Trac #24265: py3: fixes to sage.misc.fpickle module 
> > d1f349904c Trac #24248: Fix isinstance(x, int) calls in element.pyx 
> > f027e2d78e Trac #24244: Fast check for C long 
> > 5fb5ca3b3b Trac #24259: Declare Integer.value as array 
> > 61f0cb73b9 Trac #24257: py3: change how remove_unicode_u is applied in the 
> > output checker 
> > d6b21e1d8e Trac #24254: remove is_coercion_cached / is_conversion_cached 
> > methods 
> > 9764031fc8 Trac #24252: Fake Integer interface 
> > 889f394c23 Trac #24251: adapt random interval-posets to python3 
> > 91b2e224dd Trac #24250: py3: do not use mathjax from inside sagenb 
> > 6496ef1f7d Trac #24249: py3: minor care for range 
> > 146e5ebdd7 Trac #24246: Add a Cython compile time constant for 
> > PY_MAJOR_VERSION 
> > 88f2265ba1 Trac #24150: Factory function for famous lattices 
> > e2e850f9ca Trac #22801: SymPy as optional symbolic method for manifolds 
> > 3a516c1f09 Trac #22322: allow sympy algorithm in solve 
> > 03adc63bf5 Trac #24245: Move long.pxd to arith 
> > 778522d712 Trac #24242: Absolute import when importing string 
> > a1c22f12d9 Trac #24240: Upgrade freetype to 2.8.1. 
> > 3ddefacf64 Trac #24236: Structural comparison of expressions 
> > 6dae323315 Trac #24233: py3: replace  > and structure) 
> > d92697baa0 Trac #24232: Simplifications in calculus on manifolds via the 
> > expression tree 
> > 3ed2e7b2d3 Trac #24230: py3: replace  > 4f46f68562 Trac #24229: py3: replace  > 7695b8d5c7 Trac #24227: py3: check for long before check for int in some 
> > pyx files (part 2) 
> > 2fd1201453 Trac #24225: py3: check for long before check for int in some 
> > pyx files 
> > cae490b5f2 Trac #24224: py3: some care for addition of keys() 
> > eac1112a10 Trac #24221: py3: ZZ for large int 
> > 92836ba23f Trac #24220: py3: fixing one bad use of zip 
> > a47a235a5a Trac #24218: py3: get rid of one long in continued fractions 
> > 307076b609 Trac #24215: 

Re: [sage-release] Sage 8.2.beta0 released

[François Bissey]

Can we have an updated develop branch on github?

François

> On 14/12/2017, at 12:03, Volker Braun  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
> 
> 8d9c008a75 (tag: 8.2.beta0, trac/develop) Updated SageMath version to 
> 8.2.beta0
> e78d369799 Trac #24347: make Coxeter matrix groups know when they are 
> commutative
> ac7b04159f Trac #24338: Remove pari_mod finite field implementation
> 42faeb8cae Trac #24336: In Cython modules, always *c*import parent
> 0bd3ef3112 Trac #24328: New module to implement generic_power
> 46ab140520 Trac #24325: manifolds: failing tests in options
> 2cbaa17071 Trac #24322: Use new-style GlobalOptions
> e71dc43bfb Trac #24318: Conversion failure CBF -> CDF
> 34a69e72f9 Trac #24311: fix algdep when it finds a constant polynomial
> 0efa5ebb88 Trac #24308: accept polynomial ring to not implement 
> characteristic for powering
> a5321f9d74 Trac #24307: links to github sagetex repo
> 48095031fe Trac #24298: Improve Morphism.is_identity()
> d1f59e6aeb Trac #24293: Use integer_check_long to implement Integer.__mod__
> d386ef1002 Trac #24287: Issue with vertex cover for graphs with multiple edges
> b5e1445d08 Trac #24285: cleaning reall and complex balls
> 637ec22f43 Trac #24282: BooleanFunction.truth_table(format="hex") returns 
> wrong values
> 83527e8e57 Trac #24281: Fix comparison of morphisms
> ff624e8e96 Trac #24278: Simplify RingHomset_generic.__call__
> 5670b5d3f1 Trac #24276: Fix categories/examples/semigroups_cython.pyx
> 13710a98d6 Trac #24274: Fix bare "except:" statements
> b797dd7dc4 Trac #24271: py3: allow flexibility in exception message 
> formatting in doctests on Python 3
> e5cbdd8352 Trac #24270: Fix compiler warnings involving 
> debug.refine_category_hash_check
> a2dce0 Trac #24267: Fix newton_sqrt() method
> c79bf6ed78 Trac #24265: py3: fixes to sage.misc.fpickle module
> d1f349904c Trac #24248: Fix isinstance(x, int) calls in element.pyx
> f027e2d78e Trac #24244: Fast check for C long
> 5fb5ca3b3b Trac #24259: Declare Integer.value as array
> 61f0cb73b9 Trac #24257: py3: change how remove_unicode_u is applied in the 
> output checker
> d6b21e1d8e Trac #24254: remove is_coercion_cached / is_conversion_cached 
> methods
> 9764031fc8 Trac #24252: Fake Integer interface
> 889f394c23 Trac #24251: adapt random interval-posets to python3
> 91b2e224dd Trac #24250: py3: do not use mathjax from inside sagenb
> 6496ef1f7d Trac #24249: py3: minor care for range
> 146e5ebdd7 Trac #24246: Add a Cython compile time constant for 
> PY_MAJOR_VERSION
> 88f2265ba1 Trac #24150: Factory function for famous lattices
> e2e850f9ca Trac #22801: SymPy as optional symbolic method for manifolds
> 3a516c1f09 Trac #22322: allow sympy algorithm in solve
> 03adc63bf5 Trac #24245: Move long.pxd to arith
> 778522d712 Trac #24242: Absolute import when importing string
> a1c22f12d9 Trac #24240: Upgrade freetype to 2.8.1.
> 3ddefacf64 Trac #24236: Structural comparison of expressions
> 6dae323315 Trac #24233: py3: replace  and structure)
> d92697baa0 Trac #24232: Simplifications in calculus on manifolds via the 
> expression tree
> 3ed2e7b2d3 Trac #24230: py3: replace  4f46f68562 Trac #24229: py3: replace  7695b8d5c7 Trac #24227: py3: check for long before check for int in some pyx 
> files (part 2)
> 2fd1201453 Trac #24225: py3: check for long before check for int in some pyx 
> files
> cae490b5f2 Trac #24224: py3: some care for addition of keys()
> eac1112a10 Trac #24221: py3: ZZ for large int
> 92836ba23f Trac #24220: py3: fixing one bad use of zip
> a47a235a5a Trac #24218: py3: get rid of one long in continued fractions
> 307076b609 Trac #24215: Add HAVE_GMPY2 compile-time constant
> 9a51a033c3 Trac #24208: py3: add some future division imports
> 19e6aa6849 Trac #24181: py3 some corrections for .values()[...] and 
> .keys()[...]
> fe5ee6302b Trac #24205: removed deprecated choose_nk.rank
> 49d49a1d55 Trac #24204: py3: remove some has_key
> 9c06cb14ad Trac #24203: get rid of deprecated zero_element
> 88ee48657d Trac #24202: py3: get rid of some cmp() in the doc of r interface
> b9d56e6d20 Trac #24201: py3: get rid of an hex problem
> 6306edb028 Trac #24200: py3: handle some unbound methods __func__
> 5ec4dd54f2 Trac #24183: Generate eclib includes in a predictable order
> adb11ca67e Trac #24153: Remove unused functions from ccobject.h
> ea8a71ca39 Trac #24015: fix libhomfly on OSX
> 52f7a188fc Trac #24168: Upgrade Jupyter notebook
> f0f3dfba09 Trac #24167: faster Tamari comparison
> b50ba32989 Trac #24162: Fix RealSet.an_element() for unbounded intervals
> bd66e2d633 Trac #24161: Improve speed of Kostka-Foulkes polynomials
> 75bddf67d1 Trac #24160: Improve speed of dominated_partitions
> 51692155b0 Trac #24156: Construction of RealSet from inequality
> ef3bd1ae66 Trac #24155: get rid of one "long"
> 3c011c1266 Trac 

Re: [sage-release] Sage 8.1.rc1 released

[François Bissey]

scipy -> script according to my autocorrect.

> On 19/11/2017, at 08:32, François Bissey <frp.bis...@gmail.com> wrote:
> 
> And it is already a dependency. A build order one, so doc is not
> rebuilt when script changes. Do you need the doc rebuilt on script changes?
> 
> Or considering the conversation before you meant sympy?
> 
> François
> 
>> On 19/11/2017, at 08:30, François Bissey <frp.bis...@gmail.com> wrote:
>> 
>> You would add it there
>> https://github.com/sagemath/sage/blob/develop/build/make/deps#L205
>> 
>>> On 19/11/2017, at 08:28, Dima Pasechnik <dimp...@gmail.com> wrote:
>>> 
>>> so scipy is a missing dependency of docbuilding.
>>> (not sure how to fix this)
>>> 
>>> -- 
>>> 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.
>> 
> 

-- 
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] Sage 8.1.rc1 released

[François Bissey]

And it is already a dependency. A build order one, so doc is not
rebuilt when script changes. Do you need the doc rebuilt on script changes?

Or considering the conversation before you meant sympy?

François

> On 19/11/2017, at 08:30, François Bissey <frp.bis...@gmail.com> wrote:
> 
> You would add it there
> https://github.com/sagemath/sage/blob/develop/build/make/deps#L205
> 
>> On 19/11/2017, at 08:28, Dima Pasechnik <dimp...@gmail.com> wrote:
>> 
>> so scipy is a missing dependency of docbuilding.
>> (not sure how to fix this)
>> 
>> -- 
>> 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.
> 

-- 
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 8.1.rc0 released

[François Bissey]

Define strange behaviours?

> On 16/11/2017, at 18:52, Kwankyu Lee  wrote:
> 
> Hi, 
> 
> Does this release support Xcode 9.1 on mac?
> 
> I built this release with Xcode 9.1, and the Sage built shows strange 
> behaviors. Is this because of Xcode 9.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 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.