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

2018-12-20 Thread Sébastien Labbé
On Wednesday, November 28, 2018 at 9:49:53 AM UTC+1, François Bissey wrote: > > That’s interesting. I thought the failures in sage/databases/sql_db.py in > sage-on-gentoo > were due to the use of a newer version of sqlite. But if you see it too > that must be something > more subtle. > > I j

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

2018-11-29 Thread Timo Kaufmann
I've created https://trac.sagemath.org/ticket/26791 for the rpy2 issue, please post there. Am Donnerstag, 29. November 2018 21:54:42 UTC+1 schrieb Timo Kaufmann: > > Probably due to https://trac.sagemath.org/ticket/26596, sorry. Was that a > build using sage's build system (`make -j4 ptestlong`

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

2018-11-29 Thread Timo Kaufmann
Probably due to https://trac.sagemath.org/ticket/26596, sorry. Was that a build using sage's build system (`make -j4 ptestlong` or similar) or the debian package? Am Donnerstag, 29. November 2018 18:39:05 UTC+1 schrieb Emmanuel Charpentier: > > On Debian testing running onCore i5 + 8 GB RAM, I

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

2018-11-29 Thread Emmanuel Charpentier
On Debian testing running onCore i5 + 8 GB RAM, I get three failures in one doctest : -- sage -t --long --warn-long 47.5 src/sage/interfaces/r.py # 3 doctests failed -

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

2018-11-28 Thread François Bissey
This is definitely it. It introduced the doctests in question. I guess I should have provided that extra info. > On 28/11/2018, at 22:11, fchapot...@gmail.com wrote: > > Could be caused by https://trac.sagemath.org/ticket/26702 > > Le mercredi 28 novembre 2018 09:49:53 UTC+1, François Bissey a

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

2018-11-28 Thread fchapoton2
Could be caused by https://trac.sagemath.org/ticket/26702 Le mercredi 28 novembre 2018 09:49:53 UTC+1, François Bissey a écrit : > > That’s interesting. I thought the failures in sage/databases/sql_db.py in > sage-on-gentoo > were due to the use of a newer version of sqlite. But if you see it to

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

2018-11-28 Thread François Bissey
That’s interesting. I thought the failures in sage/databases/sql_db.py in sage-on-gentoo were due to the use of a newer version of sqlite. But if you see it too that must be something more subtle. François > On 28/11/2018, at 21:46, Sébastien Labbé wrote: > > On Ubuntu 16.04, the command >

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

2018-11-28 Thread Sébastien Labbé
On Ubuntu 16.04, the command sage -t --all --optional=sage,optional,external tests the following optional and external doctests: Using --optional=bliss,cbc,ccache,cmake,dot2tex,external,gmpy2,lrslib,memlimit,mpir,normaliz,notedown,pandoc_attributes,pycosat,pynormaliz,python2,rst2ipynb,sage Ext

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

2018-11-27 Thread Eric Gourgoulhon
On Ubuntu 18.04 running on Xeon E5-2623 + 16 GB RAM: - python2: - incremental build (-j16) from 8.5.beta4 OK - all tests from ptestlong passed - python3: - incremental build (-j16) from 8.5.beta4 OK - threejs viewer is now fully functional (at least as functional as with python2);

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

2018-11-26 Thread E. Madison Bray
On Mon, Nov 26, 2018 at 5:37 AM Steven Trogdon wrote: > > On my Gentoo changing the ownership was not sufficient. After changing the > ownership I had to > > git reset --hard HEAD > > which revealed that > > Updating f894105d0d..b36eca1990 > error: The following untracked working tree files would

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

2018-11-25 Thread Steven Trogdon
On my Gentoo changing the ownership was not sufficient. After changing the ownership I had to git reset --hard HEAD which revealed that Updating f894105d0d..b36eca1990 error: The following untracked working tree files would be overwritten by merge: To correct this: git clean -f build/pkgs/ba

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

2018-11-25 Thread Samuel Lelièvre
> As far as I can recall 'git pull' was always done as a normal user. > Note the timestamp on the folders, which predates 8.5.beta4. > And this issue did not manifest itself then. But going forward, > how to correct things? Change to your SAGE_ROOT directory and run this as a normal user $ su

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

2018-11-25 Thread Steven Trogdon
As far as I can recall 'git pull' was always done as a normal user. Note the timestamp on the folders, which predates 8.5.beta4. And this issue did not manifest itself then. But going forward, how to correct things? On Sunday, November 25, 2018 at 8:53:10 PM UTC-6, Samuel Lelievre wrote: > > > >

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

2018-11-25 Thread Samuel Lelievre
Mon 2018-11-26 03:21:58 UTC+1, Steven Trogdon: > > Something rather weird here. I'm unable to complete a pull of the latest > 8.5.beta5 because of > > Updating f894105d0d..b36eca1990 > error: unable to unlink old 'docker/entrypoint.sh': Permission denied > > Now entrypoint.sh is owned by root wh

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

2018-11-25 Thread Steven Trogdon
Something rather weird here. I'm unable to complete a pull of the latest 8.5.beta5 because of Updating f894105d0d..b36eca1990 error: unable to unlink old 'docker/entrypoint.sh': Permission denied Now entrypoint.sh is owned by root which I find strange ls -al docker/entrypoint.sh -rwxr-xr-x 1 ro