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

[Jeroen Demeyer]

On 2019-01-24 12:20, Harald Schilly wrote:

there is only the master server with the main (presumably correct)
file.


It's NOT correct in this case (see the other posts in this thread). The 
file genuinely has to be uploaded again to the master server.


And probably there is nothing wrong with that specific mirror, please 
unblock it.


--
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.7.beta0 released

[Jeroen Demeyer]

On 2019-01-24 10:44, Dima Pasechnik wrote:

curl -O  would download html fragment


Crazy stuff. What's the rationale for *not* following the Location 
header by default?


--
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.7.beta0 released

[Jeroen Demeyer]

More precisely, the "tarball" is just this HTML fragment:

You are being href="https://codeload.github.com/msoos/cryptominisat/tar.gz/5.6.6;>redirected.


I don't know how the release manager downloaded that tarball, as the 
link on Trac #25480 is correctly responding with a 302 which any decent 
downloader should automatically follow:


  HTTP/1.1 302 Found
  Date: Thu, 24 Jan 2019 09:14:59 GMT
  Content-Type: text/html; charset=utf-8
  Transfer-Encoding: chunked
  Server: GitHub.com
  Status: 302 Found
  Vary: X-PJAX
  Location: https://codeload.github.com/msoos/cryptominisat/tar.gz/5.6.6

--
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.6.rc1 released

[Jeroen Demeyer]

On 2019-01-14 17:40, Dima Pasechnik wrote:

I am getting a Heisenbug:

sage -t --long src/sage/geometry/polyhedron/library.py
**
File "src/sage/geometry/polyhedron/library.py", line 398, in
sage.geometry.polyhedron.library.Polytopes.icosahedron
Failed example:
 ico.volume()
Exception raised:
 Traceback (most recent call last):
   File 
"/home/dimpase/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 671, in _run
 self.compile_and_execute(example, compiler, test.globs)
   File 
"/home/dimpase/sage/local/lib/python2.7/site-packages/sage/doctest/forker.py",
line 1086, in compile_and_execute
 exec(compiled, globs)
   File "", line 1,
in 
 ico.volume()
   File "sage/misc/cachefunc.pyx", line 1952, in
sage.misc.cachefunc.CachedMethodCaller.__call__
(build/cythonized/sage/misc/cachefunc.c:10324)
 w = self._instance_call(*args, **kwds)
   File "sage/misc/cachefunc.pyx", line 1828, in
sage.misc.cachefunc.CachedMethodCaller._instance_call
(build/cythonized/sage/misc/cachefunc.c:9809)
 return self.f(self._instance, *args, **kwds)
   File 
"/home/dimpase/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/base.py",
line 5039, in volume
 triangulation = self.triangulate(engine=engine, **kwds)
   File 
"/home/dimpase/sage/local/lib/python2.7/site-packages/sage/geometry/polyhedron/base.py",
line 2837, in triangulate
 return pc.triangulate()
   File 
"/home/dimpase/sage/local/lib/python2.7/site-packages/sage/geometry/triangulation/point_configuration.py",
line 1092, in triangulate
 return self.placing_triangulation()
   File 
"/home/dimpase/sage/local/lib/python2.7/site-packages/sage/geometry/triangulation/point_configuration.py",
line 2055, in placing_triangulation
 for facet in facets_of_simplex(simplex):
   File 
"/home/dimpase/sage/local/lib/python2.7/site-packages/sage/geometry/triangulation/point_configuration.py",
line 1994, in facets_of_simplex
 normals = span.inverse().columns()
   File "sage/matrix/matrix2.pyx", line 8857, in
sage.matrix.matrix2.Matrix.inverse
(build/cythonized/sage/matrix/matrix2.c:66081)
 return ~self
   File "sage/matrix/matrix_double_dense.pyx", line 466, in
sage.matrix.matrix_double_dense.Matrix_double_dense.__invert__
(build/cythonized/sage/matrix/matrix_double_dense.c:5933)
 raise ZeroDivisionError("input matrix must be nonsingular")
 ZeroDivisionError: input matrix must be nonsingular

Perhaps the underlying triangulation code uses some randomisation,
getting bad triangulations in this case.


Related? https://trac.sagemath.org/ticket/18214

--
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.rc1 released

[Jeroen Demeyer]

On 2018-12-20 20:41, Emmanuel Charpentier wrote:

This
 seems
to wreck out release plans...


If the problem already existed in the *released* version 8.4, it 
shouldn't make anything worse to release 8.5 with the same bug as 8.4.


If instead it worked in 8.4 but not in 8.5.rc1, I would suggest a 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.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2018-10-07 21:32, Volker Braun wrote:

I've seen this sometimes when running out of memory (docbuild gets stuck
instead of erroring out)


This is just general suckiness of multiprocessing.Pool

I have a long-standing plan to extract the multiprocess code from the 
doctesting framework and use that in other place like the docbuilder too.


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

[Jeroen Demeyer]

On 2018-09-11 12:29, Erik Bray wrote:

It's not very important.


It's not very important for Sage. However, PARI (which displays the 
warning) doesn't know that. What PARI sees is somebody asking for a 
certain PARI stack size. PARI fails to allocate that much space and 
allocates less space instead (knowing that users typically ask for more 
memory than needed). However, for users who do know how much memory they 
need, the warning would actually be fatal. And the problem with the PARI 
stack is that its size is fixed once and for all when PARI starts.


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

[Jeroen Demeyer]

On 2018-09-11 11:08, Erik Bray wrote:

On Cygwin `make ptestlong` with 4 processes gave me a few random
failures.  I have a lot of browser tabs open so I'm getting a lot of
spurious

  ***   Warning: not enough memory, new PARI stack 8545042432

warnings as the cause for most of the random failures.


Can you give an example of such a failure? Does it happen only after 
forking? And how much RAM does that machine have?


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Sage 8.3 release notes

[Jeroen Demeyer]

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.
Sage 8.3 was released on 3 August 2018. It is available in
source and binary form from:

  * http://www.sagemath.org/download.html

Sage (http://www.sagemath.org/) is developed by volunteers and combines
over 90 open source packages. For instructions about installing Sage, see

  * http://doc.sagemath.org/html/en/installation/index.html

The following page lists the platforms on which Sage should work:

  * http://wiki.sagemath.org/SupportedPlatforms

If you have any questions and/or problems, please report them to any of
these Google groups:

  * sage-support: http://groups.google.com/group/sage-support
  * sage-devel: http://groups.google.com/group/sage-devel

You can also drop by in #sagemath on freenode or post your questions
at http://ask.sagemath.org/

The following 104 people contributed to this release. Of those, 19 made
their first contribution to Sage:

  - Aaron Lauve
  - Alex J. Best
  - Aly Deines
  - Andrew Mathas
  - Andrey Novoseltsev
  - Anna Haensch
  - Armin Straub
  - Ben Hutz
  - Ben Salisbury
  - Bianca Thompson
  - Brent Baccala [first contribution]
  - Bruce Westbury
  - Bruno Grenet
  - Carlos Mafra [first contribution]
  - Christian Stump
  - Clement Pernet
  - Craig Citro
  - Daniel Georg Holzfeind
  - Daniel Krenn
  - Darij Grinberg
  - David Coudert
  - David Loeffler
  - David Lubicz [first contribution]
  - David Roe
  - Dima Pasechnik
  - Emmanuel Charpentier
  - Enrique Artal [first contribution]
  - Eran Assaf [first contribution]
  - Eric Gourgoulhon
  - Erik Bray
  - Florent Hivert
  - Florentin Jaffredo [first contribution]
  - Franco Saliola
  - François Bissey
  - Friedrich Wiemer
  - Frédéric Chapoton
  - Gonzalo Tornaría
  - Jean-Philippe Labbé
  - Jeroen Demeyer
  - Jeroen Sijsling
  - Johan Rosenkilde
  - John Cremona
  - John Palmieri
  - Jonathan Hanke
  - Jori Mäntysalo
  - Joseph Lupo [first contribution]
  - Julian Rüth
  - Justin Walker
  - Kenji Hashimoto
  - Kiran Kedlaya
  - Kwankyu Lee
  - Luis Felipe Tabera
  - Marc Masdeu
  - Marc Mezzarobba
  - Marcelo Forets
  - Maria Francis [first contribution]
  - Mark Bell
  - Martin Albrecht
  - Martin Rubey
  - Matthew Lancellotti [first contribution]
  - Matthias Goerner
  - Matthias Koeppe
  - Meghana M Reddy [first contribution]
  - Michalis Neururer [first contribution]
  - Miguel Marco
  - Mike Zabrocki
  - Moritz Firsching
  - Nicolas M. Thiéry
  - Nicolás Sirolli
  - Nils Bruin
  - Paolo Menegatti
  - Pascal Giorgi [first contribution]
  - Paul Zimmermann
  - Peleg Michaeli
  - Peter Bruin
  - Raghukul Raman [first contribution]
  - Ralf Stephan
  - Romain Lebreton [first contribution]
  - Rusydi H. Makarim
  - Sai Harsh [first contribution]
  - Samuel Lelièvre
  - Sebastian Oehms
  - Simon Brandhorst
  - Simon King
  - Stefan Wewers
  - Stephan Ehlen
  - Sébastien Labbé
  - Theo Douvropoulos [first contribution]
  - Thierry Monteil
  - Timo Kaufmann [first contribution]
  - Tom Roby
  - Tomer Bauer
  - Tondomker Sai Harsh [first contribution]
  - Travis Scrimshaw
  - Vincent Delecroix
  - Vincent Klein
  - Vincent Neiger [first contribution]
  - Volker Braun
  - Vít Tuček
  - Xavier Caruso
  - Ximin Luo
  - Yuan Zhou
  - Zach Gershkoff
  - Élise Vandomme

* Release manager: Volker Braun.

* We closed 520 tickets in this release.

Merged in sage-8.3.beta0:

#7589: Frédéric Chapoton: bug in coercion and cyclotomic fields [Reviewed by 
Travis Scrimshaw]
#10577: Jonathan Hanke, Frédéric Chapoton: Deepcopy fails on vectorspaces over 
GF(2) with inner_product_matrix specified [Reviewed by Simon Brandhorst]
#15729: Yuan Zhou: Graphics3d with fractional opacity will not save image 
[Reviewed by Jean-Philippe Labbé]
#16823: Travis Scrimshaw: Implement the free Lie algebra [Reviewed by Darij 
Grinberg]
#17340: Frédéric Chapoton: can't plot immutable graphs [Reviewed by David 
Coudert]
#19270: Sébastien Labbé: Matrix_integer_sparse object has no attribute 'gap' 
[Reviewed by Travis Scrimshaw]
#19506: Travis Scrimshaw: Implement cellular algebras [Reviewed by Andrew 
Mathas]
#20382: Julian Rüth, Jeroen Demeyer: Replace is_package_installed with Features 
[Reviewed by Nicolas M. Thiéry, François Bissey, Julian Rüth]
#21022: Jeroen Demeyer: version information in sage.__version__ [Reviewed by 
Mark Bell]
#22243: Julian Rüth: Make doctests not depend on the boost version [Reviewed by 
François Bissey]
#22572: Jean-Philippe Labbé, Vincent Delecroix: Add a thematic tutorial on the 
polyhedron class [Reviewed by Moritz Firsching]
#22604: Jeroen Demeyer: autodoc unforking again [Reviewed by

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

[Jeroen Demeyer]

On 2018-08-28 11:34, Erik Bray wrote:

I did get one strange failure I have never seen before:

sage -t --long --warn-long 304.2 src/sage/parallel/map_reduce.py
**
File "src/sage/parallel/map_reduce.py", line 281, in sage.parallel.map_reduce
Failed example:
 st = pstats.Stats(prof+'0')
Expected nothing
Got:
 Exception AssertionError: AssertionError('TripleDictEraser: key
match but no weakref match',) in

ignored
**


Is it reproducible?

--
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.4.beta0 released

[Jeroen Demeyer]

On 2018-08-06 16:22, Eric Gourgoulhon wrote:

Removing Mathematica from that computer (thanks to Sage, I have no
longer any need for it  ;-))


So that test did a very good job! :-)

--
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.4.beta0 released

[Jeroen Demeyer]

On 2018-08-05 21:08, bryan gin-ge chen wrote:

[sagelib-8.4.beta0] [156/483] gcc -fno-strict-aliasing -g -O2 -DNDEBUG
-g -fwrapv -O3 -Wall -Wno-unused
-I/Applications/SageMath/local/lib/python2.7/site-packages/cysignals
-I/Applications/SageMath/local/include
-I/Applications/SageMath/local/include/python2.7
-I/Applications/SageMath/local/lib/python2.7/site-packages/numpy/core/include
-I/Applications/SageMath/src -I/Applications/SageMath/src/sage/ext
-Ibuild/cythonized -I/Applications/SageMath/local/include/python2.7 -c
build/cythonized/sage/libs/braiding.cpp -o
build/temp.macosx-10.9-x86_64-2.7/build/cythonized/sage/libs/braiding.o
-fno-strict-aliasing -DCYTHON_CLINE_IN_TRACEBACK=1 -std=c++11
[sagelib-8.4.beta0] build/cythonized/sage/libs/braiding.cpp:1310:10:
fatal error: 'braiding.h' file not found
[sagelib-8.4.beta0] #include "braiding.h"
[sagelib-8.4.beta0]  ^~~~
[sagelib-8.4.beta0] 1 error generated.


I opened https://trac.sagemath.org/ticket/26007 for 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.

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

[Jeroen Demeyer]

Thanks for the quick beta!

--
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.3.beta2 released

[Jeroen Demeyer]

On 2018-05-18 22:28, Sébastien Labbé wrote:

The first run of make gave the following error with gfan:


This is because of the ticket fixing the Python builds (not the upgrade 
to 2.7.15). Simply trying the build again ("make" or whatever) should 
fix it.


--
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.3.beta1 released

[Jeroen Demeyer]

On 2018-05-16 17:26, Erik Bray wrote:

I'm not sure, but I think this might be pip-related.  I think Jeroen
mentioned something about this to me a couple weeks ago.  Is it
possible you upgraded the pip in your Sage install?


Indeed, I guess you are using pip 10 by accident.

It might be a good idea to upgrade the pip in Sage and fix this issue.

--
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: Release process

[Jeroen Demeyer]

On 2018-05-16 12:44, Vincent Delecroix wrote:

- "integration" is intended to be used by bots only to check whether
a given positively reviewed ticket is worth a merge. It has no
reason to be used by any human.


The issue is that it may be accidentally used by a human by mistake.

--
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: Release process

[Jeroen Demeyer]

On 2018-05-16 11:26, Vincent Delecroix wrote:

It can be smarter than a hash, e.g. 8.3.beta2018-05-16. And we can
afford a daily release at GMT 00:00.


If you want to automate it anyway, you could instead automatically 
release a new "beta" whenever develop is updated.


--
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: Release process

[Jeroen Demeyer]

On 2018-05-16 10:30, Vincent Delecroix wrote:

And I agree: there should be two branches whatever
they are called. Let's go for "develop + integration" (that were
"integration" + "TMP" in my previous e-mail).


In that case, I fully agree with your previous e-mail!


As a consequence, we would abandon beta releases


Why? I like the idea of betas because it makes it easy to name things. I 
can say "I rebased this on top of 8.3.beta1" and everybody understands 
what I mean. On the other hand, "I rebased this on top of 
6fc1e20c666283a301b4ff3f855013de8d206b35" is not so clear.


--
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: Release process

[Jeroen Demeyer]

On 2018-05-16 10:23, Vincent Delecroix wrote:

TMP is public! People should just not base their work on as it is
likely to be abandoned. On the other hand, people should be encouraged
to base their work on "integration" and not on "latest beta".


It seems that you're thinking that there are 3 branches (develop, 
integration and TMP) while in reality there are only two (develop and TMP).


--
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: Release process

[Jeroen Demeyer]

On 2018-05-16 10:06, Vincent Delecroix wrote:

On 15/05/2018 17:07, Volker Braun wrote:

The integration branch is going to have its history rewritten regularly.


Why is that? Shouldn't the process be simply

   1. create a branch TMP = "integration branch" + "merged positive
 review ticket"
   2. if merge fails: move back ticket to needs work and go back to 1
   3. if any test fails: move back ticket to needs work and go back to 1
   4. set the integration branch to TMP and go back to 1


The integration branch *is* TMP. Otherwise you are just shifting the 
problem from "integration branch" to TMP and people will complain that 
TMP should be publicly accessible.


IMHO the workflow should be:

1. create a branch integration = develop + some selection of positive 
review tickets

2. if merge fails: move back ticket to needs work and go back to 1
3. if any test fails: move back ticket to needs work and go back to 1
4. set develop to integration and go back to 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.

Re: [sage-release] Re: Release process

[Jeroen Demeyer]

On 2018-05-15 15:40, Emmanuel Charpentier wrote:

Therefore, I think that contributing to Sage should not *require* a
sophisticated understanding of the finer points of git care and feeding...


Of course not. I don't think that anybody here proposed that.

--
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: Release process

[Jeroen Demeyer]

On 2018-05-15 14:35, Erik Bray wrote:

I'm not convinced that's a real problem.  This is what I meant by "yes
its contents may change and shift rapidly, but for a sophisticated
developer who just wants to peek in on the release process this is not
a problem".


I agree that it's not a problem for the "sophisticated developer" who 
knows what he is doing. But the more you advertise this secret branch, 
the larger chance there is of abuse by non-sophisticated developers who 
have no clue. I believe that this is the point that Maarten was trying 
to make.


--
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.3.beta0 released

[Jeroen Demeyer]

On 2018-05-11 10:41, Dima Pasechnik wrote:

I really don't get how #20382
was ever positively reviewed.


I guess we were mostly focusing on the technical aspects of the Feature 
check framework and not so much on the individual checks.


--
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.3.beta0 released

[Jeroen Demeyer]

On 2018-05-09 22:21, Volker Braun wrote:

Open one on trac if there is not one already.


+1

A ticket on Trac is much more visible than a mailing list post.

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] Release process

[Jeroen Demeyer]

(starting a new thread for the discussion about the current very slow 
pace of merging tickets)


On 2018-05-07 16:28, Erik Bray wrote:

If it's not clear, shall I write up some more formal documentation for
my proposed process?


To be honest, I think it's not very meaningful to do that without 
consulting the release manager. I mean, you can write up all the 
documentation that you want; in the end, it's the release manager who 
decides what happens.


I do agree that there is a problem though. We are close to 200 
positively reviewed tickets just sitting there. And my fear of conflicts 
is certainly holding me back to do further Sage development for the 
moment (luckily, I had PEP 575 and the Cernay workshop to keep myself busy).


So Volker, what's your opinion on 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.

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

[Jeroen Demeyer]

On 2018-04-26 11:16, fchapot...@gmail.com wrote:

I am
really worried by the 161 positive-reviewed tickets that have been
accumulating


+1

There have been releases with less tickets than that.

--
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.rc3 released

[Jeroen Demeyer]

On 2018-04-20 01:23, John H Palmieri wrote:

objc[46054]: +[__NSPlaceholderDate initialize] may have been in progress
in another thread when fork() was called.


Googling for this error messages shows that we are not alone:

https://blog.phusion.nl/2017/10/13/why-ruby-app-servers-break-on-macos-high-sierra-and-what-can-be-done-about-it/

--
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.rc1 released

[Jeroen Demeyer]

On 2018-04-02 18:18, Samuel Lelièvre wrote:

I would also like to advocate getting the following tickets in Sage 8.2:


I nominate https://trac.sagemath.org/ticket/25047

It's really trivial but convenient for Python 3 development.

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

[Jeroen Demeyer]

The Sage banner is broken:
https://trac.sagemath.org/ticket/25056

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

[Jeroen Demeyer]

On 2018-03-14 19:02, Erik Bray wrote:

two Integers' mpz_t structs' _mp_d
member (the array of limbs) is being set to the same memory address.


You really mean two different Integer objects with the same _mp_d (as 
opposed to the same Integer object being used mistakenly in two 
different places).


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

[Jeroen Demeyer]

On 2018-03-14 19:02, Erik Bray wrote:

I see now--less likely a bug with MPIR/GMP itself, and more likely a
bug with Sage's fast_tp_new stuff for Integer.


I don't know whether it will fix that bug or not, but there is a 
long-standing ticket to improve those hacks at


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

--
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.beta7 released

[Jeroen Demeyer]

Thanks! I opened https://trac.sagemath.org/ticket/24963

--
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.beta7 released

[Jeroen Demeyer]

On 2018-03-13 10:02, John Cremona wrote:

I had a couple of failures on a ubuntu machine where the previous beta
was fine, both complaining about permissions of files in /tmp.


Logs please.

--
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.beta6 released

[Jeroen Demeyer]

See https://trac.sagemath.org/ticket/24827

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

[Jeroen Demeyer]

On 2018-02-09 17:55, fchapot...@gmail.com wrote:

I have a build failure in subprocess32 on a python3 build (using export
SAGE_PYTHON3=yes)


Fixed in https://trac.sagemath.org/ticket/24650

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

[Jeroen Demeyer]

On 2018-02-09 12:02, François Bissey wrote:

We have seen an instance of that problem during review
but we thought it was fixed.


That was a different issue. While the error message was the same, the 
underlying reason was different.


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

[Jeroen Demeyer]

I think I understand why this might happen:
https://trac.sagemath.org/ticket/24694

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

[Jeroen Demeyer]

On 2018-02-09 11:56, fchapot...@gmail.com wrote:

An incremental build from previous beta fails on gfortran :


Please do

touch configure.ac && make build

and send me the full output.

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

[Jeroen Demeyer]

I created 2 blocker tickets for problems reported by some patchbots:

- #24376: Upgrade notedown
- #24378: Doctest failures related to sympy

--
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.rc4 released

[Jeroen Demeyer]

On 2017-12-04 19:18, Emmanuel Charpentier wrote:

I already reported

(twice

!) that 8.1.rc(whatever) won't build without Trac#24121


If you find that ticket so important, why didn't you change its priority 
to "blocker"? I see that this was done very recently, but if you had 
done that from the beginning, it would already have been merged.


--
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.rc4 released

[Jeroen Demeyer]

On 2017-12-04 14:35, Erik Bray wrote:

I don't see why.  What's the harm in merging a couple working branches?


The first rc version of Sage 8.1 is now almost 1 month ago. We don't 
want to delay the release of 8.1 forever.


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

[Jeroen Demeyer]

On 2017-11-18 04:47, kcrisman wrote:

So maybe that is part of the issue.  How could that be happening?


Maybe you have more than 1 version of Sage installed?

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

[Jeroen Demeyer]

On 2017-11-17 14:51, Kwankyu Lee wrote:

This (building the documentation is no longer
the last step) sounds a big change to me. I wonder when that change was
made.


In Sage 6.8, see https://trac.sagemath.org/ticket/18710

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

[Jeroen Demeyer]

On 2017-11-17 02:05, Kwankyu Lee wrote:

There was an error in building doc.


There you have it! The build didn't succeed.

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

[Jeroen Demeyer]

On 2017-11-16 07:38, Kwankyu Lee wrote:

I get the following just after "make",


Sorry to ask a silly question, but are you sure that

(1) You actually ran "make"
(2) That run of "make" succeeded without errors

It seems that sympy simply wasn't built. I am not aware of any bug in 
the build system (especially not specific to OS X) which could cause that.


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

[Jeroen Demeyer]

Could this be
https://github.com/cython/cython/issues/1375

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

[Jeroen Demeyer]

On 2017-10-18 18:09, Erik Bray wrote:

Thanks, but no need--I think I see the issue.  If you happen to be
somewhere on the path of the cythonized file, then the "File" string
Cython produces ends up being relative to your current directory


I remember seeing this bug 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.1.beta8 released

[Jeroen Demeyer]

Just to be clear: is this the *only* failure or are you seeing several 
similar failures (if so: please show them all).


--
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.beta7 released

[Jeroen Demeyer]

On 2017-10-04 09:09, Emmanuel Charpentier wrote:

On Debianbtesting running on core i7 + 16 GB RAM, passes ptestlong with
one transient failure :
--
sage -t --long src/sage/schemes/elliptic_curves/sha_tate.py  # 1 doctest
failed
--
This tet passes when ran standalone.


Also: which optional packages were installed? In particular, was 
database_cremona installed?


--
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.beta7 released

[Jeroen Demeyer]

Was it the test from https://trac.sagemath.org/ticket/23962 which failed?

--
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.beta4 released

[Jeroen Demeyer]

On 2017-09-11 18:40, Maarten Derickx wrote:

Was there already a ticket created for the failing elliptic curves test?


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

I'm guessing it has to do with optional packages since also the sage4 
patchbot is one with a lot of optional packages.


--
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.beta4 released

[Jeroen Demeyer]

On 2017-09-06 14:31, François Bissey wrote:

Hum… Several things at once there. First you had an upgrade-downgrade
of glpk 4.63 as discussed in the glpk upgrade ticket which didn’t
quite make in the beta (last minute rejection) see
https://trac.sagemath.org/ticket/23596
The other two seem to be linked to a separate ticket about verbosity of glpk.
I don’t have that ticket number right now.


That is #20876. But the reason why it causes patchbot failures is still 
the same as discussed in #23596: the downgrade to GLPK-4.60 from #20876 
broke the way as the downgrade from #23596.


--
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.beta4 released

[Jeroen Demeyer]

On 2017-09-06 14:24, Daniel Krenn wrote:

Two patchbots rk02-math and sardonis failed their test of 8.1.beta4 in

sage -t --long src/sage/numerical/backends/glpk_backend.pyx  # 3
doctests failed
sage -t --long src/sage/numerical/backends/generic_backend.pyx  # 1
doctest failed
sage -t --long src/sage/numerical/backends/glpk_exact_backend.pyx  # 1
doctest failed


This is https://trac.sagemath.org/ticket/23596#comment:4

--
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.beta4 released

[Jeroen Demeyer]

On 2017-09-06 01:55, Vincent Delecroix wrote:

sage -t --long --warn-long 74.4
src/sage/schemes/elliptic_curves/ell_number_field.py  # 18 doctests failed


It seems that you are the only one with this problem. Do you have a 
custom version of some package (say, PARI/GP) installed?


--
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.beta2 released

[Jeroen Demeyer]

On 2017-08-16 03:07, richar...@lozestech.com wrote:

Failed example:
 E.cremona_label()
Expected:
 Traceback (most recent call last):
 ...
 RuntimeError: Cremona label not known for Elliptic Curve defined by
y^2 + y = x^3 - 79*x + 342 over Rational Field.
Got:
 '19047851a1'
**


This should be fixed by https://trac.sagemath.org/ticket/23609

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

[Jeroen Demeyer]

On 2017-07-02 10:38, Sébastien Labbé wrote:

See
https://trac.sagemath.org/ticket/15585
for the first one.


Which is possibly fixed by https://trac.sagemath.org/ticket/22462 (needs 
review).


--
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.0.beta9 released

[Jeroen Demeyer]

zlib breakage: https://trac.sagemath.org/ticket/23122

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

[Jeroen Demeyer]

OK, I didn't realise that math-readline was a Python script from Sage.

I created https://trac.sagemath.org/ticket/23112 to track this issue.

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

[Jeroen Demeyer]

On 2017-05-30 23:51, John H Palmieri wrote:

I'm getting intermittent timeouts from src/sage/doctest/external.py, and
in particular the "has_mathematica()" test. This is a new (but
underpowered) computer and it does not have mathematica installed. If I run

$ sage --sh
$ math-readline

then 19 out of 20 times, it fails immediately


Define "fails immediately". The fact that it only "fails immediately" 19 
out of 20 times means that the "fails immediately" is somehow non-trivial.


--
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.0.beta1 released

[Jeroen Demeyer]

On 2017-04-08 14:23, Eric Gourgoulhon wrote:

make ptestlong created
an empty directory "home" in SAGE_ROOT


That's an old issue. I never investigated where that "home" came from.


as well as two files:
__home_eric__sage_temp_manifold_6686_dir_R1ZgOC_src_pyx.cpp
__home_eric__sage_temp_manifold_6686_dir_R1ZgOC_src_pyx.html


See https://trac.sagemath.org/ticket/22788

--
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.0.beta0 released

[Jeroen Demeyer]

On 2017-04-04 18:41, Eric Gourgoulhon wrote:

What could explain the difference?


That's a very good question indeed...

I'm afraid we need some web expert here.

--
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.0.beta0 released

[Jeroen Demeyer]

I would like in particular feedback on the "Take me to the new 
Sage/Jupyter notebook" button in ExportSageNB.


When clicking that button, do you get

(A) a directory listing of the current directory
(B) a login screen where you are asked for a token

You should get (A) but under certain unknown circumstances, one can get 
(B) instead.


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

[Jeroen Demeyer]

[lrslib-062+autotools-2017-03-03] Attempting to download package 
lrslib-062+autotools-2017-03-03.tar.gz from mirrors

[...]
[lrslib-062+autotools-2017-03-03] 
[xx]
[lrslib-062+autotools-2017-03-03] ERROR [transfer|run:135]: [Errno 404] 
Not Found: 
'//sagepad.org/spkg/upstream/lrslib/lrslib-062+autotools-2017-03-03.tar.gz'

[lrslib-062+autotools-2017-03-03] Traceback (most recent call last):
[lrslib-062+autotools-2017-03-03]   File 
"/home/patchbot/sage-patchbot/build/bin/sage-download-file", line 28, in 


[lrslib-062+autotools-2017-03-03] run_safe()
[lrslib-062+autotools-2017-03-03]   File 
"/home/patchbot/sage-patchbot/build/bin/../sage_bootstrap/download/cmdline.py", 
line 118, in run_safe

[lrslib-062+autotools-2017-03-03] run()
[lrslib-062+autotools-2017-03-03]   File 
"/home/patchbot/sage-patchbot/build/bin/../sage_bootstrap/download/cmdline.py", 
line 100, in run
[lrslib-062+autotools-2017-03-03] 
app.download_tarball(args.url_or_tarball, args.destination)
[lrslib-062+autotools-2017-03-03]   File 
"/home/patchbot/sage-patchbot/build/bin/../sage_bootstrap/download/app.py", 
line 43, in download_tarball

[lrslib-062+autotools-2017-03-03] tarball.download()
[lrslib-062+autotools-2017-03-03]   File 
"/home/patchbot/sage-patchbot/build/bin/../sage_bootstrap/tarball.py", 
line 161, in download
[lrslib-062+autotools-2017-03-03] raise 
FileNotMirroredError('tarball does not exist on mirror network')
[lrslib-062+autotools-2017-03-03] 
sage_bootstrap.tarball.FileNotMirroredError: tarball does not exist on 
mirror network
make[2]: *** 
[/home/patchbot/sage-patchbot/local/var/lib/sage/installed/lrslib-062+autotools-2017-03-03] 
Error 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.

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

[Jeroen Demeyer]

On 2017-02-26 19:49, Volker Braun wrote:

0dff673 Trac #22177: Implement SVG plotting in pari_jupyter


This tarball is not mirrored:

[pari_jupyter-1.2.2] ERROR [transfer|run:135]: [Errno 404] Not Found: 
'//sagepad.org/spkg/upstream/pari_jupyter/pari_jupyter-1.2.2.tar.bz2'

[pari_jupyter-1.2.2] Traceback (most recent call last):
[pari_jupyter-1.2.2]   File 
"/usr/local/src/sage-git/build/bin/sage-download-file", line 28, in 

[pari_jupyter-1.2.2] run_safe()
[pari_jupyter-1.2.2]   File 
"/usr/local/src/sage-git/build/bin/../sage_bootstrap/download/cmdline.py", 
line 118, in run_safe

[pari_jupyter-1.2.2] run()
[pari_jupyter-1.2.2]   File 
"/usr/local/src/sage-git/build/bin/../sage_bootstrap/download/cmdline.py", 
line 100, in run
[pari_jupyter-1.2.2] app.download_tarball(args.url_or_tarball, 
args.destination)
[pari_jupyter-1.2.2]   File 
"/usr/local/src/sage-git/build/bin/../sage_bootstrap/download/app.py", 
line 43, in download_tarball

[pari_jupyter-1.2.2] tarball.download()
[pari_jupyter-1.2.2]   File 
"/usr/local/src/sage-git/build/bin/../sage_bootstrap/tarball.py", line 
161, in download
[pari_jupyter-1.2.2] raise FileNotMirroredError('tarball does not 
exist on mirror network')
[pari_jupyter-1.2.2] sage_bootstrap.tarball.FileNotMirroredError: 
tarball does not exist on mirror network


--
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: Why is gcc built?

[Jeroen Demeyer]

On 2017-02-24 10:31, Erik Bray wrote:

On Thu, Feb 23, 2017 at 5:26 PM, Dima Pasechnik  wrote:

one can still have something like:
--with-everything  # build everything
--with-everythingneeded # build missing
etc...
to encode the most usual cases.


Yes, I think this goes without saying.


And why should --with-everythingneeded *not* be the default?

--
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: Why is gcc built?

[Jeroen Demeyer]

Sorry, but I do not like your idea. I don't feel like being forced to run

./configure --with-gcc --with-zlib --with-mpir --with-r --with-glpk 
--with-git --with-ppl --with-pari --with-libgap ... # 80 packages more


just because I don't have those packages on my system.

--
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 7.6.beta4 released

[Jeroen Demeyer]

This is a bug in Pynac, see
* https://trac.sagemath.org/ticket/22421
* https://github.com/pynac/pynac/issues/231

On 2017-02-22 08:16, Jeroen Demeyer wrote:

sage -t --long src/sage/symbolic/expression.pyx
**
File "src/sage/symbolic/expression.pyx", line 9627, in
sage.symbolic.expression.Expression.to_gamma
Failed example:
 binomial(m,n).to_gamma()
Expected:
 gamma(m + 1)/(gamma(m - n + 1)*gamma(n + 1))
Got:
 binomial(m, n)
**


--
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: Why is gcc built?

[Jeroen Demeyer]

Looks fine to me...

On 2017-02-22 18:31, Simon King wrote:

configure:5266: checking for gfortran
configure:5282: found /usr/bin/gfortran
configure:5293: result: gfortran
configure:5319: checking for Fortran compiler version
configure:5328: gfortran --version >&5
GNU Fortran (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Copyright (C) 2015 Free Software Foundation, Inc.

GNU Fortran comes with NO WARRANTY, to the extent permitted by law.
You may redistribute copies of GNU Fortran
under the terms of the GNU General Public License.
For more information about these matters, see the file named COPYING


--
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: Why is gcc built?

[Jeroen Demeyer]

On 2017-02-22 16:50, Simon King wrote:

In other words, I still don't see why gcc should be rebuilt (unless the
developer's manual needs update).


Can you post the config.log file?

--
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: Why is gcc built?

[Jeroen Demeyer]

On 2017-02-22 16:50, Simon King wrote:

So, it seems that the problem lies in Fortran compiler, right? But I did do
   sudo apt-get install gcc-fortran
following the advice of the manual.


To verify, run

gfortran --version

--
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: Why is gcc built?

[Jeroen Demeyer]

On 2017-02-22 14:50, Simon King wrote:

Hi Jeroen,

On 2017-02-22, Jeroen Demeyer <jdeme...@cage.ugent.be> wrote:

The reason that I asked you to run ./configure is just to answer the
*why* question.


Since I am not patient enough to wait till the build has finished:
Shouldn't the reason be visible in install.log?


No: ./configure is run *before* that log file is created.

--
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 7.6.beta4 released

[Jeroen Demeyer]

On sage4, I get one failure:

sage -t --long src/sage/symbolic/expression.pyx
**
File "src/sage/symbolic/expression.pyx", line 9627, in 
sage.symbolic.expression.Expression.to_gamma

Failed example:
binomial(m,n).to_gamma()
Expected:
gamma(m + 1)/(gamma(m - n + 1)*gamma(n + 1))
Got:
binomial(m, n)
**

I have not tested each beta on this machine, so I cannot be sure that 
this problem got introduced in 7.6.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.

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

[Jeroen Demeyer]

On 2017-02-13 14:32, Sébastien Labbé wrote:

On Ubuntu 16.06, make ptestlong with MAKE="make j6" had one failing test
which I can not reproduce:


See https://trac.sagemath.org/ticket/15585

--
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 7.6.beta3 released

[Jeroen Demeyer]

sage -t src/sage/modular/pollack_stevens/padic_lseries.py
**
File "src/sage/modular/pollack_stevens/padic_lseries.py", line 199, in 
sage.modular.pollack_stevens.padic_lseries.pAdicLseries.__ne__

Failed example:
L != L
Exception raised:
Traceback (most recent call last):
  File 
"/usr/local/src/sage-config/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
line 498, in _run

self.compile_and_execute(example, compiler, test.globs)
  File 
"/usr/local/src/sage-config/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
line 861, in compile_and_execute

exec(compiled, globs)
  File "sage.modular.pollack_stevens.padic_lseries.pAdicLseries.__ne__[1]>", 
line 1, in 

L != L
NameError: name 'L' is not defined
**

See https://trac.sagemath.org/ticket/22334

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2017-02-04 10:34, Jean-Philippe Labbé wrote:

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


Logs please... ignore the "python" thing, it's most likely not the 
reason for the failure.


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2017-01-24 13:09, John Cremona wrote:

OK, I am doing that and then make and make ptestlong, and we'll see
what happens no, same errors.


Minor comment: if you are going to run "make ptestlong" anyway, there is 
no point in running "make" separately. In other words, "make && make 
ptestlong" is equivalent to "make ptestlong" (with the latter also being 
faster).


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2017-01-24 10:54, John Cremona wrote:

Quite possibly.  If I use pip to install something and it tells me
that my pip os out of date I usually obey instructions and update it.
Should I not have done?


Depends. If you want all doctests to pass: no, you should not have done 
that.



And what should I do to fix this (apart from make clean; make)?


I guess you could try re-installing pip using "./sage -f pip"

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

This is 3 doctest runs concatenated. I will just look at the last one 
(if you remember for next time: better just post the log of one run).


Those issues are because of pip. Did you manually upgrade pip in that 
installation?


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2017-01-23 17:50, John Cremona wrote:

ptestlong.log available on request.


Yes please.

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

[Jeroen Demeyer]

On 2016-12-23 01:35, Francois Bissey wrote:

Follow up. Working on a ticket.


Just did that: https://trac.sagemath.org/ticket/22094

I don't know how to reproduce 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.

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

[Jeroen Demeyer]

On 2016-12-20 12:02, Daniel Krenn wrote:

Fails for me on Linux Mint 17.3, built from repo from scratch as well.


If you know how to reproduce this: please report at
https://trac.sagemath.org/ticket/22094

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-12-10 13:54, Dima Pasechnik wrote:

Aren't we trying to separate build space from source?


Yes, we are in the process of doing that. Although this is about 
auto-generated sources, so it's not necessarily wrong to put those in 
the sources.


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-11-26 07:38, Peleg Michaeli wrote:

I have a similar error:


Not similar. Please try again with

$ make doc-clean
# make

--
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 7.5.beta3 released

[Jeroen Demeyer]

On 2016-11-19 13:16, 'Bill Hart' via sage-release wrote:

I vaguely remember Bill Allombert saying something about changing Pari
so that it just adds more stack when needed, rather than requiring a
huge block allocated up front.


It's true that PARI uses a small stack by default and that it increases 
stack size when needed. But it still needs to *allocate* the large stack 
up front.



Or are we talking about virtual memory,
or a different definition of enormous?


We are talking about *virtual* memory indeed.

--
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 7.5.beta3 released

[Jeroen Demeyer]

On 2016-11-19 10:27, John Cremona wrote:

It seems strange to me that pari would need to allocate an
enormous amount of memory as Sage starts up.


Maybe strange, but it is a feature because of the way the PARI stack works.

--
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: cannot build 7.5.b3 (twice)

[Jeroen Demeyer]

On 2016-11-19 08:53, fchapot...@gmail.com wrote:

Le samedi 19 novembre 2016 00:36:58 UTC+1, Volker Braun a écrit :

What are the permissions on your src/ directory?




It seems to be 775. I do not think I have changed anything about that recently.


This should fix it:

chmod 0755 src

--
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 7.5.beta3 released

[Jeroen Demeyer]

On 2016-11-18 20:58, John Cremona wrote:

   ***   Warning: not enough memory, new stack 69618196480

-- what's that about (the last line)?


It means that PARI failed to allocate the requested amount of memory.

--
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 7.5.beta3 released

[Jeroen Demeyer]

On 2016-11-18 10:06, John Cremona wrote:

Build failure on ubuntu, based on a successful build of the previous
beta and following "git pull trac develop":

Error building Sage.

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

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

* documentation: dochtml
   log file: /home/jec/sage/logs/pkgs/../dochtml.log


I'm certainly used to dochtml failing but python?  The log file is
embarrassingly short:


Red herring. As others said, this was almost certainly an old file still 
lingering in logs/pkgs. Note the phrase "not necessarily

during this run of 'make all'" above.

--
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 7.5.beta1 released

[Jeroen Demeyer]

On 2016-11-07 11:43, Emmanuel Charpentier wrote:

and read the logs I've attached.


It's a long thread with many posts of you, I am getting lost. Can you 
please reboot the discussion at #21812? And attach a log file showing 
why you think that #21812 does not work.


--
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 7.5.beta1 released

[Jeroen Demeyer]

On 2016-11-07 08:31, Emmanuel Charpentier wrote:

Well, a serial recompilation with pip 8.x works (see enclosed logs).


That test failure is #15585 which is totally unrelated to pip.

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

[sage-release] database_cremona_ellcurve-20161017 is not mirrored

[Jeroen Demeyer]

Please mirror
http://homepages.warwick.ac.uk/~masgaj/ftp/database_cremona_ellcurve-20161017.tar.bz2
(see https://trac.sagemath.org/ticket/21715)

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-11-02 21:12, William Stein wrote:

Jereon - is this script the thing you want from
disk.math.washington.edu?


Yes.


Is that the only copy?


Yes. I never copied it because I didn't think I would be running it 
forever...



If so, next time
I'm on campus I can turn that machine on and get the script...


Sure. I don't remember exactly where it is stored, I should see some "ls 
-l" of my home directory.


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-11-02 13:26, Dima Pasechnik wrote:

My point is that cysignals is essentially a part of the Sage's build system.


No, it's not. It's a package just like numpy or mpfr is a package.


Imagine you would need to declare a dependence on python in every
package that uses python...


We actually do that and nobody ever complained about that.

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-11-02 10:16, Dima Pasechnik wrote:

I would rather treat cysignals as a part of Python suite, and make sure
they are built together with Python
a sort of "codependency" - let's say Python is codependent on cysignals
if they are to be built right after Python.
Surely there are more examples like this that can simplify our
dependencies graph.


-1 because I don't see the point, what is so special about cysignals? It 
will only complicate the build system.


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-11-02 09:37, Dima Pasechnik wrote:

build failure at fpylll due to undeclared dependency on cysignals


This is https://trac.sagemath.org/ticket/21795


somehow, cygsignals should be built before any cython module


The usual "dependencies" files can handle that. Why should cysignals be 
treated differently from other dependencies?


--
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 7.5.beta0 released

[Jeroen Demeyer]

On 2016-10-21 16:11, Jeroen Demeyer wrote:

It consistently shows up while running doctests, but not in an
interactive Sage session. I have no idea what is going on.


OK, got it. This problem happens whenever gmpy2 (a package I have been 
playing with recently but which is not in Sage) is imported because it 
changes the GMP/MPIR memory allocation functions.


It turns out that the doctester imports sympy to "Disable SymPy terminal 
width detection", which imports mpmath, which imports gmpy2.


--
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 7.5.beta0 released

[Jeroen Demeyer]

I have a very strange problem:

sage -t src/sage/ext/memory.pyx
**
File "src/sage/ext/memory.pyx", line 9, in sage.ext.memory
Failed example:
2^(2^63-2)
Expected:
Traceback (most recent call last):
...
MemoryError: failed to allocate 1152921504606847008 bytes
Got:
Fatal Python error: Insufficient memory
Traceback (most recent call last):
  File 
"/usr/local/src/sage-git/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
line 498, in _run

self.compile_and_execute(example, compiler, test.globs)
  File 
"/usr/local/src/sage-git/local/lib/python2.7/site-packages/sage/doctest/forker.py", 
line 861, in compile_and_execute

exec(compiled, globs)
  File "", line 1, in 
Integer(2)**(Integer(2)**Integer(63)-Integer(2))
  File "sage/rings/integer.pyx", line 2047, in 
sage.rings.integer.Integer.__pow__ 
(build/cythonized/sage/rings/integer.c:13702)

sig_on()
  File "src/cysignals/signals.pyx", line 102, in 
cysignals.signals.sig_raise_exception (build/src/cysignals/signals.c:1273)

RuntimeError: Aborted
**

It consistently shows up while running doctests, but not in an 
interactive Sage session. I have no idea what is going on.


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-10-19 20:00, Emmanuel Charpentier wrote:

After upodating my "develop" branch to 7.4 and merging it with my local
branch (was 7.4beta6, and contained trac#20523 (R.3.3.1), trac#21231
(enhancemens to fricas interface) and trac#21622 (pari/perl)), I get a
bunch of compilation problems :


1. Obvious question: does sage-7.4 by itself work? Maybe the "merging" 
that you did introduced problems.


2. If 7.4 does not work: log files please.

--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

On 2016-10-16 20:20, 'Martin R' via sage-release wrote:

It seems that this made openblas build, thank you.

However: the build takes so long that it makes me wonder.  Is it
possible that it takes much longer to build this release candidate than
some beta before?


The build of *what* takes so long? The openblas build? Of an incremental 
Sage build? Of a complete from-scratch Sage build?


--
You received this message because you are subscribed to the Google Groups 
"sage-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-release+unsubscr...@googlegroups.com.
To post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.

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

[Jeroen Demeyer]

I created https://trac.sagemath.org/ticket/21689

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