[sage-devel] Re: Git repository should have Sage versions as branches not tags

Samuel, there are a couple pull requests from the middle of 2015 that never became Trac tickets. The bot appears to have stopped creating tickets before then. There are open pull requests from the end of 2014 that became part of Sage 6.4. The bot does not appear to close pull requests on

[sage-devel] Re: sage -b fail

Jeroen Demeyer wrote: > On 2016-07-18 14:48, 'Paul Mercat' via sage-devel wrote: >> But this command doesn't work even if I don't make any change in the >> source code. > > Note that changing git branches counts as changing source code. So > I bet that you *did* make changes to the Sage source

Re: [sage-devel] sage -b fail

On 2016-07-18 14:48, 'Paul Mercat' via sage-devel wrote: But this command doesn't work even if I don't make any change in the source code. Note that changing git branches counts as changing source code. So I bet that you *did* make changes to the Sage source code since the last time you ran

Re: [sage-devel] Re: sage -b fail

On 18 July 2016 at 14:26, leif wrote: > John Cremona wrote: >> I have a similar problem, on a machine which has successfully built >> Sage in the past. Version 7.2 (literally commit f76401f). >> >> The last few commainds in history are >> >> make distclean >> ../configure

[sage-devel] Re: sage -b fail

leif wrote: > John Cremona wrote: >> I have a similar problem, on a machine which has successfully built >> Sage in the past. Version 7.2 (literally commit f76401f). >> >> The last few commainds in history are >> >> make distclean >> ../configure >> make >> make >> >> but each of the last two

[sage-devel] Re: sage -b fail

John Cremona wrote: > I have a similar problem, on a machine which has successfully built > Sage in the past. Version 7.2 (literally commit f76401f). > > The last few commainds in history are > > make distclean > ../configure > make > make > > but each of the last two make's ends with the

Re: [sage-devel] sage -b fail

I have a similar problem, on a machine which has successfully built Sage in the past. Version 7.2 (literally commit f76401f). The last few commainds in history are make distclean ./configure make make but each of the last two make's ends with the following, also mentioning

Re: [sage-devel] sage -b fail

I can not reproduce your problem with 7.3.beta7 (downloaded from Sage's git/trac server). That said, if you make some modifications of Sage source code, you can just do 'make' afterwards. Ciao, Thierry On Mon, Jul 18, 2016 at 05:48:39AM -0700, 'Paul Mercat' via sage-devel wrote: > Yes, I

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

On Mon, Jul 18, 2016 at 12:46 PM, Thierry wrote: > Hi, > > On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote: > [...] >> Additionally, I think we should allow issues (without code) to be >> posted on GitHub, and have an easy way to convert a GitHub issue

Re: [sage-devel] sage -b fail

Yes, I successfully ran 'make'. But I need to run 'sage -b' because I want to modify some things in the source code. But this command doesn't work even if I don't make any change in the source code. Ciao Paul Le lundi 18 juillet 2016 13:24:41 UTC+2, Thierry (sage-googlesucks@xxx) a écrit : >

Re: [sage-devel] sage -b fail

Hi, On Mon, Jul 18, 2016 at 03:48:47AM -0700, 'Paul Mercat' via sage-devel wrote: > Hi ! > > I just installed the last developpement version of sage with > git clone git://github.com/sagemath/sage.git > and it compiles correctly on my Ubuntu 16.04 computer. Do you mean that at this point you

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

Hi, On Mon, Jul 18, 2016 at 12:17:48PM +0200, Erik Bray wrote: [...] > Additionally, I think we should allow issues (without code) to be > posted on GitHub, and have an easy way to convert a GitHub issue to a > Trac ticket. I don't think it should be done for all issues, but > rather use GitHub

[sage-devel] sage -b fail

Hi ! I just installed the last developpement version of sage with git clone git://github.com/sagemath/sage.git and it compiles correctly on my Ubuntu 16.04 computer. But after that the command "./sage -b" fail with the following error : ... qflllTraceback (most recent call last): File "", line

Re: [sage-devel] Re: Git repository should have Sage versions as branches not tags

On Mon, Jul 18, 2016 at 10:12 AM, Samuel Lelievre wrote: > There is a bot (called sageb0t) that turns pull requests on GitHub into trac > tickets. > > It might be that the bot also closes pull requests when the corresponding > tickets > have been closed on trac and a

[sage-devel] Indicate hidden output in Sage worksheet

Hello, the output in a Sage worksheet can be hidden. - *Hide/Show Output:* Click on the left side of output to toggle between hidden, shown with word wrap, and shown without word wrap. It is however not indicated in which state the output sell currently is. I repeatedly ran into the

[sage-devel] Re: Git repository should have Sage versions as branches not tags

There is a bot (called sageb0t) that turns pull requests on GitHub into trac tickets. It might be that the bot also closes pull requests when the corresponding tickets have been closed on trac and a new public release of Sage happens (github pull requests are typically against the master