[sage-release] Re: Sage 8.2 released

2018-05-10 Thread Enrique Artal
Python3, yes. I put the output of gdb below

El jueves, 10 de mayo de 2018, 8:27:56 (UTC+2), Dima Pasechnik escribió:
>
> Well, fire up gdb, look at the place it crashes...
>
> It is python3, right? So it would help to see what F28 does with python3, 
> and why it works outside of sage.
>

   Message: Process 28762 (python) of user 1000 dumped core. 

   Stack trace of thread 28762: 
   #0  0x7fcabcc2cc81 __strlen_avx2 (libc.so.6) 
   #1  0x7fcabd9dd158 do_mkvalue 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #2  0x7fcabd9dda2e va_build_value 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #3  0x7fcabd9ddaee Py_BuildValue 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #4  0x7fcab5e0a801 crypt_crypt_impl 
(_crypt.cpython-36m-x86_64-linux-gnu.so) 
   #5  0x7fcabd925ed5 _PyCFunction_FastCallDict 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #6  0x7fcabd9b1f3f call_function 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #7  0x7fcabd9b564f _PyEval_EvalFrameDefault 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #8  0x7fcabd9b1b3a _PyEval_EvalCodeWithName 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #9  0x7fcabd9b1dd2 fast_function 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #10 0x7fcabd9b564f _PyEval_EvalFrameDefault 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #11 0x7fcabd9b1b3a _PyEval_EvalCodeWithName 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #12 0x7fcabd9b218f PyEval_EvalCodeEx 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #13 0x7fcabd9b21bb PyEval_EvalCode 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #14 0x7fcabd9af19d builtin_exec_impl 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #15 0x7fcabd926085 PyCFunction_Call 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #16 0x7fcabd9b9098 do_call_core 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #17 0x7fcabd9b1b3a _PyEval_EvalCodeWithName 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #18 0x7fcabd9b1dd2 fast_function 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #19 0x7fcabd9b564f _PyEval_EvalFrameDefault 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #20 0x7fcabd9b2139 _PyFunction_FastCall 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #21 0x7fcabd9b564f _PyEval_EvalFrameDefault 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #22 0x7fcabd9b2139 _PyFunction_FastCall 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #23 0x7fcabd9b564f _PyEval_EvalFrameDefault 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #24 0x7fcabd9b2139 _PyFunction_FastCall 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #25 0x7fcabd9b564f _PyEval_EvalFrameDefault 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #26 0x7fcabd9ba77f _PyFunction_FastCall 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #27 0x7fcabd8be76e _PyObject_FastCallDict 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #28 0x7fcabd8bf844 _PyObject_CallMethodIdObjArgs 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #29 0x7fcabd9d4781 PyImport_ImportModuleLevelObject 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #30 0x7fcabd9b9515 import_name 
(/usr/local/sagegit/local/var/tmp/sage/build/python3-3.6.1.p1/src/libpython3.6m.so.1.0)
 

   #31 0x7fcabd9b1b3a 

[sage-release] Re: Sage 8.2 released

2018-05-10 Thread Dima Pasechnik
Well, fire up gdb, look at the place it crashes...

It is python3, right? So it would help to see what F28 does with python3, and 
why it works outside of 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 post to this group, send email to sage-release@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-release.
For more options, visit https://groups.google.com/d/optout.


[sage-release] Re: Sage 8.2 released

2018-05-09 Thread Enrique Artal
An update for the situation with respect to Fedora 28. In case my 
installation, upgraded from previous versions, may have some problems I 
retried in a virtual machine, using gcc-7.2 from sage, and I reached the 
same place: a core dumped when trying to import crypt module in python3, no 
issue with other packages including python2. The same thing happened with 
the develop branch. I guess that the problem is only related to the 
distribution but I am unable to guess how.

El miércoles, 9 de mayo de 2018, 7:50:11 (UTC+2), Enrique Artal escribió:
>
> Thanks! Do you have any clue about why crypt module cannot be loaded?
>
> El miércoles, 9 de mayo de 2018, 0:07:34 (UTC+2), Volker Braun escribió:
>>
>> Binaries are now on the way to the mirrors...
>>
>>

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


[sage-release] Re: Sage 8.2 released

2018-05-08 Thread Enrique Artal
Thanks! Do you have any clue about why crypt module cannot be loaded?

El miércoles, 9 de mayo de 2018, 0:07:34 (UTC+2), Volker Braun escribió:
>
> Binaries are now on the way to the mirrors...
>
>

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


[sage-release] Re: Sage 8.2 released

2018-05-08 Thread Volker Braun
Binaries are now on the way to the mirrors...

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


[sage-release] Re: Sage 8.2 released

2018-05-07 Thread Enrique Artal
I tried it.. I failed the first time because I did not used ./configure and 
gcc package was not used. With ./configure, gcc was loaded, python2 is OK 
but python3 still fails because of crypt module.

El lunes, 7 de mayo de 2018, 16:41:43 (UTC+2), John H Palmieri escribió:
>
> You could try setting the environment variable SAGE_INSTALL_GCC=yes to 
> force Sage to build its own version of gcc. 
>
>
> On Monday, May 7, 2018 at 6:56:53 AM UTC-7, Enrique Artal wrote:
>>
>> I have tried, but there are too many dependences. I will wait for 
>> binaries. I tried to compile on two computers; In one of them python3 was 
>> compiled but python2 failed on both. thanks for the tip, anyway.
>>
>> El lunes, 7 de mayo de 2018, 10:37:56 (UTC+2), Dima Pasechnik escribió:
>>>
>>> You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's 
>>> known to Python people this this does not work...
>>> Can you install gcc-7 and make it the default compiler?
>>>
>>> On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote:

 I was unable to compile it in Fedora 28. I attach the log giles.

 El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió:
>
> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>


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


[sage-release] Re: Sage 8.2 released

2018-05-07 Thread John H Palmieri
You could try setting the environment variable SAGE_INSTALL_GCC=yes to 
force Sage to build its own version of gcc. 


On Monday, May 7, 2018 at 6:56:53 AM UTC-7, Enrique Artal wrote:
>
> I have tried, but there are too many dependences. I will wait for 
> binaries. I tried to compile on two computers; In one of them python3 was 
> compiled but python2 failed on both. thanks for the tip, anyway.
>
> El lunes, 7 de mayo de 2018, 10:37:56 (UTC+2), Dima Pasechnik escribió:
>>
>> You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known 
>> to Python people this this does not work...
>> Can you install gcc-7 and make it the default compiler?
>>
>> On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote:
>>>
>>> I was unable to compile it in Fedora 28. I attach the log giles.
>>>
>>> El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió:

 The "master" git branch has been updated to Sage-8.1. 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.2.rc4

>>>

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


[sage-release] Re: Sage 8.2 released

2018-05-07 Thread Enrique Artal
I have tried, but there are too many dependences. I will wait for binaries. 
I tried to compile on two computers; In one of them python3 was compiled 
but python2 failed on both. thanks for the tip, anyway.

El lunes, 7 de mayo de 2018, 10:37:56 (UTC+2), Dima Pasechnik escribió:
>
> You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known 
> to Python people this this does not work...
> Can you install gcc-7 and make it the default compiler?
>
> On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote:
>>
>> I was unable to compile it in Fedora 28. I attach the log giles.
>>
>> El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió:
>>>
>>> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>>>
>>

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


[sage-release] Re: Sage 8.2 released

2018-05-07 Thread Dima Pasechnik
You're using gcc-8.0.1 - this is not (yet) supported - perhaps it's known 
to Python people this this does not work...
Can you install gcc-7 and make it the default compiler?

On Sunday, May 6, 2018 at 10:21:53 PM UTC+1, Enrique Artal wrote:
>
> I was unable to compile it in Fedora 28. I attach the log giles.
>
> El domingo, 6 de mayo de 2018, 10:56:04 (UTC+2), Volker Braun escribió:
>>
>> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>>
>

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


[sage-release] Re: Sage 8.2 released

2018-05-06 Thread Eric Gourgoulhon
Thank you Volker for the release!

Built like a charm on Ubuntu 16.04 (from a fresh git clone) and make 
ptestlong returned "All tests passed!".

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.
For more options, visit https://groups.google.com/d/optout.


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

2018-05-06 Thread Henri Girard
I use bionic AMD 64 and I compiled sage-8.2 git without any problem (but 
openssl was lacking).



Le 06/05/2018 à 20:30, John H Palmieri a écrit :
Some version of gcc is in the prerequisites for linux, but if the 
existing version is not good enough, Sage will build its own. On OS X, 
Sage builds its own (for now). Also, the Sage gcc package is listed as 
standard, so it should be included in the tarball. The point of the 
tarball being self-contained is that you can download it once and then 
you don't need an internet connection while building Sage.


  John



On Sunday, May 6, 2018 at 10:07:55 AM UTC-7, Emmanuel Charpentier wrote:

gcc is part of the prerequisites listed in README.md

--
Emmanuel Charpentier

Le dimanche 6 mai 2018 17:41:48 UTC+2, John H Palmieri a écrit :

The "self-contained" source tarball is not self-contained: it
(still) does not contains gcc. This has been true for at least
the last several rc releases, as I've reported here before.


On Sunday, May 6, 2018 at 1:56:04 AM UTC-7, Volker Braun wrote:

The "master" git branch has been updated to Sage-8.1. 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.2.rc4

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


[sage-release] Re: Sage 8.2 released

2018-05-06 Thread John H Palmieri
Some version of gcc is in the prerequisites for linux, but if the existing 
version is not good enough, Sage will build its own. On OS X, Sage builds 
its own (for now). Also, the Sage gcc package is listed as standard, so it 
should be included in the tarball. The point of the tarball being 
self-contained is that you can download it once and then you don't need an 
internet connection while building Sage.

  John



On Sunday, May 6, 2018 at 10:07:55 AM UTC-7, Emmanuel Charpentier wrote:
>
> gcc is part of the prerequisites listed in README.md
>
> --
> Emmanuel Charpentier
>
> Le dimanche 6 mai 2018 17:41:48 UTC+2, John H Palmieri a écrit :
>>
>> The "self-contained" source tarball is not self-contained: it (still) 
>> does not contains gcc. This has been true for at least the last several rc 
>> releases, as I've reported here before.
>>
>>
>> On Sunday, May 6, 2018 at 1:56:04 AM UTC-7, Volker Braun wrote:
>>>
>>> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>>>
>>

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


[sage-release] Re: Sage 8.2 released

2018-05-06 Thread Emmanuel Charpentier
FWIW, Starting from a 8.2rc2 tree, 8.2 + #24969 + #24585 builds and passes 
ptestlong with no error whatsoever on Debian testing running on Core i7 + 
16 GB RAM.

HTH,

--
Emmanuel Charpentier


Le dimanche 6 mai 2018 10:56:04 UTC+2, Volker Braun a écrit :
>
> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>

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


[sage-release] Re: Sage 8.2 released

2018-05-06 Thread Emmanuel Charpentier
Neither git nor curl are listed in README.md : are they downloaded an 
compiled on a "virgin" system ? If so, no problem. If not, they should be 
listed in the prerequisites...

--
Emmanuel Charpentier

Le dimanche 6 mai 2018 17:44:31 UTC+2, John H Palmieri a écrit :
>
> It doesn't contain git or curl, either, by the way. I haven't done a 
> systematic check to see whether other packages might be missing.
>
>
> On Sunday, May 6, 2018 at 8:41:48 AM UTC-7, John H Palmieri wrote:
>>
>> The "self-contained" source tarball is not self-contained: it (still) 
>> does not contains gcc. This has been true for at least the last several rc 
>> releases, as I've reported here before.
>>
>>
>> On Sunday, May 6, 2018 at 1:56:04 AM UTC-7, Volker Braun wrote:
>>>
>>> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>>>
>>

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


[sage-release] Re: Sage 8.2 released

2018-05-06 Thread Emmanuel Charpentier
gcc is part of the prerequisites listed in README.md

--
Emmanuel Charpentier

Le dimanche 6 mai 2018 17:41:48 UTC+2, John H Palmieri a écrit :
>
> The "self-contained" source tarball is not self-contained: it (still) does 
> not contains gcc. This has been true for at least the last several rc 
> releases, as I've reported here before.
>
>
> On Sunday, May 6, 2018 at 1:56:04 AM UTC-7, Volker Braun wrote:
>>
>> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>>
>

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


[sage-release] Re: Sage 8.2 released

2018-05-06 Thread John H Palmieri
The "self-contained" source tarball is not self-contained: it (still) does 
not contains gcc. This has been true for at least the last several rc 
releases, as I've reported here before.


On Sunday, May 6, 2018 at 1:56:04 AM UTC-7, Volker Braun wrote:
>
> The "master" git branch has been updated to Sage-8.1. 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.2.rc4
>

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


[sage-release] Re: Sage 8.2 released

2018-05-06 Thread Volker Braun
The "master" git branch has been updated to Sage-8.2, of course

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