On 2014-03-05, Dima Pasechnik <[email protected]> wrote: > On 2014-03-05, Nathann Cohen <[email protected]> wrote: >> Helloooooooo !! >> >>> suppose I previosuly had beta2 installed from the tarball. What is the >>> git way to get the update? >>> >>> Would 'git pull' followed by 'make' be enough? >> >> Yep. First make sure that your current branch is actually the beta2 >> release (and not some ticket's branch, or something you are working >> on), and then "git pull". And make, which is not always necessary >> (when spkg were updated if I make no mistake). >> >> If something happens, then it works. If you get an error message, share it >> :-D > > something has happened, surely, but at the end I still see beta2 > banner, even though git log says that the latest commit is > > commit ccab9854bf85180a261d71a8adc103d4c1f26342 > Author: Volker Braun <[email protected]> > Date: Mon Mar 3 16:05:18 2014 +0100 > > Updated Sage version to 6.2.beta3 > > and one can see that the banner is updated by this commit. > Well, sage-banner in src/bin/ is different from the one in local/bin/; > the latter stays on beta2. > > How are the scripts in local/bin updated? note that at the Sage prompt I get sage: version() 'Sage Version 6.2.beta3, Release Date: 2014-03-03'
i.e. indeed it looks like whatever script is meant to update local/bin scripts is not invoked by make. (it does not get invoked by sage -b or by sage -sync-build, either) > > > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/groups/opt_out.
