[sage-release] Re: Sage 8.2 released

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

Re: [sage-release] Release process

2018-05-07 17:08 GMT+02:00 Erik Bray: > > On Mon, May 7, 2018 at 4:55 PM, 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

Re: [sage-release] Release process

On Mon, May 7, 2018 at 4:55 PM, Jeroen Demeyer wrote: > (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

[sage-release] Release process

(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

[sage-release] Re: Sage 8.2 released

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

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

On Sat, May 5, 2018 at 10:21 PM, wrote: > On Thursday, April 26, 2018 at 7:11:52 AM UTC-7, Erik Bray wrote: >> >> >> Given such a branch to work in, it becomes less "urgent" to finish a >> release since it no longer needs to block normal development progress. >> Of course, you

[sage-release] Re: Sage 8.2 released

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

[sage-release] Re: Sage 8.2 released

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