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

2019-01-24 Thread 'Justin C. Walker' via sage-release
> 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

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

2019-01-24 Thread fchapoton2
I have the same issue with libffi ! Le jeudi 24 janvier 2019 06:08:53 UTC+1, Steven Trogdon a écrit : > > Problem building libffi-3.2.1 on gentoo > > cp: cannot overwrite non-directory > '/64bitdev/storage/sage-git_develop/sage/local/./lib64' with directory >

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

2019-01-24 Thread Sébastien Labbé
I did not run any make test yet, but if I try to create a new notebook in Jupyter I get an error page saying "500 : Internal Server Error" and the error being printed in the terminal says ImportError: No module named defusedxml It is copied below: [I 09:59:24.941 NotebookApp] Creating

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

2019-01-24 Thread 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

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

2019-01-24 Thread Dima Pasechnik
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

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

2019-01-24 Thread Sébastien Labbé
On Thursday, January 24, 2019 at 10:03:07 AM UTC+1, Sébastien Labbé wrote: > > I did not run any make test yet, but if I try to create a new notebook in > Jupyter I get an error page saying "500 : Internal Server Error" and the > error being printed in the terminal says > > ImportError: No

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

2019-01-24 Thread 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

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

2019-01-24 Thread Dima Pasechnik
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

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

2019-01-24 Thread Eric Gourgoulhon
On Ubuntu 18.04 running on Xeon E5-2623 + 16 GB RAM: - python2: - build (-j16) from a fresh git clone OK - all tests from ptestlong passed - python3: - build (-j16) from a fresh git clone OK I confirm that the Jupyter notebook is broken in this release, both with python2 and python3,

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

2019-01-24 Thread 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

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

2019-01-24 Thread Harald Schilly
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

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

2019-01-24 Thread E. Madison Bray
On Thu, Jan 24, 2019 at 9:40 AM wrote: > > I have the same issue with libffi ! I will look into that ASAP. It's a similar / related problem to https://trac.sagemath.org/ticket/26996 but affecting libffi. The install target for libffi might even depend on your compiler's settings, which might

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

2019-01-24 Thread fchapoton2
This libffi warning/failure does not prevent sage to run and work. It prevents my patchbot to work correctly though. Le jeudi 24 janvier 2019 09:40:52 UTC+1, fchap...@gmail.com a écrit : > > I have the same issue with libffi ! > > Le jeudi 24 janvier 2019 06:08:53 UTC+1, Steven Trogdon a écrit :

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

2019-01-24 Thread Dima Pasechnik
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

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

2019-01-24 Thread Harald Schilly
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

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

2019-01-24 Thread fchapoton2
installing libffi-dev on the system and doing ./configure fixed the problem. Thanks ! Le jeudi 24 janvier 2019 13:45:37 UTC+1, E. Madison Bray a écrit : > > On Thu, Jan 24, 2019 at 9:40 AM > wrote: > > > > I have the same issue with libffi ! > > I will look into that ASAP. It's a similar /

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

2019-01-24 Thread Eric Gourgoulhon
Le jeudi 24 janvier 2019 14:12:23 UTC+1, Eric Gourgoulhon a écrit : > > > I confirm that the Jupyter notebook is broken in this release, both with > python2 and python3, as already reported by Sébastien ( > https://groups.google.com/d/msg/sage-release/ULwr6YtMfnY/UpPKqXmxDAAJ), > the error

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

2019-01-24 Thread Andy Howell
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: