Re: [sage-release] Sage 8.7.beta0 released
> On Jan 23, 2019, at 12:47 , Volker Braun wrote:
>
> As always, you can get the latest beta version from the "develop" git branch.
> Alternatively, the self-contained source tarball is at
> http://www.sagemath.org/download-latest.html
Built w/o problems from fresh clones of the develop tree, on three macOS
platforms: 10.11.6 (mid-2014 MBP, Quad-core Core i7), 10.13.6 (2017 iMac Pro,
Xeon W), and 10.14.2 (2017 MBP, Quad-core Core i7). For testing (‘ptestlong’):
10.11.6: all tests passed!
10.13.6: one doctest failed:
sage -t --long --warn-long 72.5 src/sage/libs/singular/polynomial.pyx
See below for the output.
This test passed when run stand-alone.
10.14.2: all tests passed!
Justin
**
File "src/sage/libs/singular/polynomial.pyx", line 184, in
sage.libs.singular.polynomial.singular_polynomial_call
Failed example:
for i in range(30): # long time
n = leak(1)
print("Leaked {} bytes".format(n))
if n == 0:
zeros += 1
if zeros >= 6:
break
else:
zeros = 0
Expected:
Leaked...
Leaked 0 bytes
Leaked 0 bytes
Leaked 0 bytes
Leaked 0 bytes
Leaked 0 bytes
Got:
Leaked 115129450496 bytes
Leaked 327155712 bytes
Leaked 272629760 bytes
Leaked 327155712 bytes
Leaked 327155712 bytes
Leaked 327155712 bytes
Leaked 327155712 bytes
Leaked 343932928 bytes
Leaked 335544320 bytes
Leaked 0 bytes
Leaked 71303168 bytes
Leaked 331350016 bytes
Leaked 331350016 bytes
Leaked 327155712 bytes
Leaked 0 bytes
Leaked 327155712 bytes
Leaked 0 bytes
Leaked 335544320 bytes
Leaked 0 bytes
Leaked 0 bytes
Leaked 318767104 bytes
Leaked 339738624 bytes
Leaked 0 bytes
Leaked 0 bytes
Leaked 0 bytes
Leaked 0 bytes
Leaked 331350016 bytes
Leaked 138412032 bytes
Leaked 327155712 bytes
Leaked 0 bytes
**
1 item had failures:
1 of 12 in sage.libs.singular.polynomial.singular_polynomial_call
[51 tests, 1 failure, 711.16 s]
--
Justin C. Walker, Curmudgeon-At-Large
Institute for the Absorption of Federal Funds
Men are from Earth.
Women are from Earth.
Deal with 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
Under Ubuntu 18.10, I had one transient failure. sage -t --long --warn-long 53.6 src/sage/numerical/linear_tensor_element.pyx # Killed due to abort sage/local/bin/python2 cored. Running the test standalone passed, as did rerunning all tests again. On 1/23/19 2:47 PM, Volker Braun wrote: -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To 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
ok, it's the one being pointed at, makes sense. I've replaced the file. Master right now: files@k8s:~/files/spkg$ sha1sum ./upstream/cryptominisat/cryptominisat-5.6.6.tar.gz 568cd2f528609a31d217e24e381de87e011499d4 ./upstream/cryptominisat/cryptominisat-5.6.6.tar.gz On Thu, Jan 24, 2019 at 1:05 PM Harald Schilly wrote: > Ok, I see, I've removed that file and pushed the timestamp of the master > mirror. I don't know how to get the correct file, so that's all I can do… > > On Thu, Jan 24, 2019 at 12:44 PM Jeroen Demeyer > wrote: > >> 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. >> > -- 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
Ok, I see, I've removed that file and pushed the timestamp of the master mirror. I don't know how to get the correct file, so that's all I can do… On Thu, Jan 24, 2019 at 12:44 PM Jeroen Demeyer wrote: > 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. > -- 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
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
It's really weird that mirrors don't checksum stuff they download and host. Could it be due to an error in setting the mirroring on Sage's side? Just wondering... On Thu, Jan 24, 2019 at 11:21 AM Harald Schilly wrote: > > > > On Thu, Jan 24, 2019 at 8:10 AM Vincent Delecroix <20100.delecr...@gmail.com> > wrote: >> >> And I confirm that the one downloaded from mirrorservice.org >> is broken > > > I've disabled that mirror. Ideally, whatever mechanism is downloading the > files in Sage should blacklist such a mirror when there is an error. Then > start again without that mirror. > > >> >> >> Could that be uploaded again? > > > No, there is only the master server with the main (presumably correct) file. > Mirrors pull from there. > > -- harald > > > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 8.7.beta0 released
On Thu, Jan 24, 2019 at 8:10 AM Vincent Delecroix <20100.delecr...@gmail.com> wrote: > And I confirm that the one downloaded from mirrorservice.org > is broken I've disabled that mirror. Ideally, whatever mechanism is downloading the files in Sage should blacklist such a mirror when there is an error. Then start again without that mirror. > > Could that be uploaded again? > No, there is only the master server with the main (presumably correct) file. Mirrors pull from there. -- harald -- 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
On Thu, Jan 24, 2019 at 11:10 AM Jeroen Demeyer wrote: > > 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? well, ask here: https://github.com/curl/curl they are very reasonable, I once had this: https://github.com/curl/curl/issues/3143 > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
Re: [sage-release] Sage 8.7.beta0 released
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
On Thu, Jan 24, 2019 at 9:19 AM Jeroen Demeyer wrote: > > 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: wget would do it right, but ends up creating a misnamed file 5.6.6.tag.gz curl -O would download html fragment curl -O -L would do the same as wget above does. curl -L -o blah.foo would get the correct file and save it to blah.foo I don't know how to make curl use the correct tarball name for saving. (it also has options like --post302, I don't know whether they are any better) Dima > >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. -- 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
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.7.beta0 released
I do have a valid tarball on my computer
$ sha1sum cryptominisat-5.6.6.tar.gz
568cd2f528609a31d217e24e381de87e011499d4
And I confirm that the one downloaded from mirrorservice.org
is broken
$ sha1sum cryptominisat-5.6.6.tar.gz
0ff5ce55d8e3d199c81c5ebef5abf7f06a47796a
It is a completely broken archive
$ tar tzf cryptominisat-5.6.6.tar.gz
gzip: stdin: not in gzip format
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Could that be uploaded again?
Vincent
Le 23/01/2019 à 21:58, Jeroen Demeyer a écrit :
On 2019-01-23 21:47, Volker Braun wrote:
7aa39995c5 Trac #25480: Upgrade to cryptominisat 5.6.6 (and make it an
optional package again)
There is something wrong with the tarball:
[cryptominisat-5.6.6] Found local metadata for cryptominisat-5.6.6
[cryptominisat-5.6.6] Attempting to download package
cryptominisat-5.6.6.tar.gz from mirrors
[cryptominisat-5.6.6]
http://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/cryptominisat/cryptominisat-5.6.6.tar.gz
[cryptominisat-5.6.6]
[..]
[cryptominisat-5.6.6]
[cryptominisat-5.6.6] Traceback (most recent call last):
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/download/cmdline.py",
line 118, in run_safe
[cryptominisat-5.6.6] run()
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/download/cmdline.py",
line 100, in run
[cryptominisat-5.6.6] app.download_tarball(args.url_or_tarball,
args.destination)
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/download/app.py",
line 43, in download_tarball
[cryptominisat-5.6.6] tarball.download()
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/tarball.py",
line 164, in download
[cryptominisat-5.6.6] raise ChecksumError('checksum does not match')
[cryptominisat-5.6.6] ChecksumError: checksum does not match
[cryptominisat-5.6.6]
[cryptominisat-5.6.6]
[cryptominisat-5.6.6] Error downloading cryptominisat-5.6.6.tar.gz
[cryptominisat-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.7.beta0 released
I accidentally typed in rc0 but then corrected it to beta0, any vestiges of 8.7.rc0 should just be local to your git repo (please delete / ignore) On Wednesday, January 23, 2019 at 9:57:13 PM UTC+1, Jeroen Demeyer wrote: > > On 2019-01-23 21:47, Volker Braun wrote: > > 5389d8dc87 (tag: 8.7.beta0, trac/develop) > > It's also tagged (presumably by mistake) as 8.7.rc0. > -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To 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
On 2019-01-23 21:47, Volker Braun wrote:
7aa39995c5 Trac #25480: Upgrade to cryptominisat 5.6.6 (and make it an
optional package again)
There is something wrong with the tarball:
[cryptominisat-5.6.6] Found local metadata for cryptominisat-5.6.6
[cryptominisat-5.6.6] Attempting to download package
cryptominisat-5.6.6.tar.gz from mirrors
[cryptominisat-5.6.6]
http://www.mirrorservice.org/sites/www.sagemath.org/spkg/upstream/cryptominisat/cryptominisat-5.6.6.tar.gz
[cryptominisat-5.6.6]
[..]
[cryptominisat-5.6.6]
[cryptominisat-5.6.6] Traceback (most recent call last):
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/download/cmdline.py",
line 118, in run_safe
[cryptominisat-5.6.6] run()
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/download/cmdline.py",
line 100, in run
[cryptominisat-5.6.6] app.download_tarball(args.url_or_tarball,
args.destination)
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/download/app.py",
line 43, in download_tarball
[cryptominisat-5.6.6] tarball.download()
[cryptominisat-5.6.6] File
"/home/jdemeyer/sage-patchbot/build/bin/../sage_bootstrap/tarball.py",
line 164, in download
[cryptominisat-5.6.6] raise ChecksumError('checksum does not match')
[cryptominisat-5.6.6] ChecksumError: checksum does not match
[cryptominisat-5.6.6]
[cryptominisat-5.6.6]
[cryptominisat-5.6.6] Error downloading cryptominisat-5.6.6.tar.gz
[cryptominisat-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.7.beta0 released
On 2019-01-23 21:47, Volker Braun wrote: 5389d8dc87 (tag: 8.7.beta0, trac/develop) It's also tagged (presumably by mistake) as 8.7.rc0. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To 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.7.beta0 released
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 5389d8dc87 (tag: 8.7.beta0, trac/develop) Updated SageMath version to 8.7.beta0 36ec29e57d Trac #26969: Misc pip upgrades 79cf5c980d Trac #27023: fix missing :: a4dd7deefc Trac #27020: OpenBLAS 0.3.5 e60f32bb91 Trac #27017: Remove sage.schemes.elliptic_curves.padics from documentation 4fb44bc920 Trac #27014: Deprecate sage.misc.misc.uniq c128368a45 Trac #27013: py3: some care for Hadamard matrices 6521233113 Trac #27010: py3: avoid .vertices() in methods _ford_fulkerson, edge_cut, bounded_outdegree_orientation and gomory_hu_tree 58d9680bbe Trac #27009: py3: avoid sorting vertices and edges in method treewidth 1ad58d2bb9 Trac #27008: py3: avoid .vertices() in method apex_vertices 010e1e893b Trac #27007: py3: avoid .vertices() in planarity.pyx c14dc9c46f Trac #27005: wrong libgap conversion for matrices over QQ['x'] 7123d7504d Trac #27003: _iterator_weight should not sort 48484ef69d Trac #27002: autodoc: use __qualname__ on Python 3 57c5c40661 Trac #26999: 1 optional gurobi doctest failing ee7ed3c076 Trac #26998: py3 fix last 4 failing doctests in combinat/posets 23f806cad2 Trac #26997: 5 internet doctests failing in findstat.py 0698bfb999 Trac #26995: Upgrade to Pynac-0.7.23 619281186a Trac #23222: Add test to EllipticCurve.isogeny() to check for validity of kernel polynomials 4f560b02dc Trac #26988: py3: one tiny fix for isidentifier 90c3b31954 Trac #26985: some work on cluster mutation ee2d9c5657 Trac #26981: fix trac ticket number in deprecation warning 24186b661f Trac #26967: py3: some work on modular/modform_hecketriangle/ 2f73854033 Trac #26958: Inheriting from MPolynomialRing_libsingular crashes sage 319b7ac911 Trac #26943: Giac support for term orders and elimination 537b91840d Trac #26938: IncidenceStructure breaks if points cannot be sorted 37065d12db Trac #26936: WordMorphism: domain/codomain should be sortable if not given cdab354eeb Trac #26933: Subsets_s should support unsortable sets 6a818ec5e1 Trac #26917: py3: some fix in set_partition be09cc219f Trac #26864: Indentation error in Number Field a915a3ab1a Trac #26839: RealLazyField: converting constants in an expression to float cefb74fd8c Trac #26834: pep8 cleaning in vertex_separation.pyx c6125397b3 Trac #26810: Permutations(avoiding=[[1,3,2]]) returns all permutations 52633235e2 Trac #26809: Wrong contains in Permutations avoiding a pattern 33ec2f8202 Trac #26516: Wrong sig_on_count in SharedMeatAxe faab330692 Trac #26361: Glucose SAT solver ce239b2e40 Trac #26183: doctest: tolerance parsing and ellipses 580c25bd1c Trac #26156: 0.0 is printed with too many digits ddfe6f3a20 Trac #25931: changes to partition for k combinat 08166d10a2 Trac #25900: Package libffi 35931ca890 Trac #25865: fast iterator for set partitions with given block sizes 7aa39995c5 Trac #25480: Upgrade to cryptominisat 5.6.6 (and make it an optional package again) 41153919eb Trac #25384: Let `sage --jupyter` call the Jupyter in Sage ec0b3f610b Trac #25147: Add DESTDIR support for boost_cropped a3ee80c6cb Trac #25143: Add DESTDIR support for pari 137ad44b65 Trac #25100: Add DESTDIR support for gfan, lcalc, ratpoints, rubiks, symmetrica d8f5ab4875 Trac #18214: Bug in volume computation of polyhedron 9b3ae6af92 Trac #27024: update sagetex to version 3.2 4a7f20f562 Trac #26966: py3: new doctest failures in homology 3d09a80bb4 Trac #26962: Logarithm of rational numbers is broken d6f2242df4 Trac #26907: Exact division in ℤ[x][y] is broken 6abcb72592 (tag: 8.6, trac/master, sagemath/master) Updated SageMath version to 8.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.
