To get the latest betas you should be tracking the "develop" branch (from
trac or github, they are the same).
You can issue something like:
"""
git checkout -b develop trac/develop
"""
to make a local copy of it and directly swith to it.
On Wednesday, April 30, 2014 4:30:44 PM UTC+2, Andrew wrote:
>
> OK, so the singular version seems to be in
>
> $SAGE_ROOT/build/pkgs/singular/package-version.txt
>
> and it is indeed set to 3.1.5.p9. Updating this by hand to 3.1.6.p1 and
> then re-making gave a checksum error on
>
> upstream/singular-3.1.6.p1
>
> Deleting this and then re-making still gives a checksum error so I'm
> guessing that the heck sum that it is being compared against is for
> 3.1.5.p6.
>
> I'm guessing that I have somehow tied git up in knots?
> Andrew
>
> On Thursday, 1 May 2014 00:22:31 UTC+10, Andrew wrote:
>>
>> On Wednesday, 30 April 2014 20:48:01 UTC+10, Volker Braun wrote:
>>>
>>> On Wednesday, April 30, 2014 9:50:27 AM UTC+1, Andrew wrote:
>>>>
>>>> singular-3.1.5.p9
>>>>>
>>>>
>>> Sage-6.2.rc0 uses Singular 3.1.6.p1, you are building an old branch
>>> (possibly older than when we fixed the OSX 10.9 build). Are you sure you
>>> didn't accidentally check out 6.2.beta0? Check "git log"
>>>
>>> Strange. In $SAGE_ROOT/upstream I have both
>> singular-3.1.5.tar.bz2
>> singular-3.1.6.tar.bz2
>> I jut tried deleting 3.1.5 and remaking....and make downloaded 3.1.5
>> again giving the messages
>> ...
>> /usr/local/src/sage/build/pipestatus "sage-spkg ${SAGE_SPKG_OPTS}
>> singular-3.1.5.p9 2>&1" "tee -a
>> /usr/local/src/sage/logs/pkgs/singular-3.1.5.p9.log"
>> Found local metadata for singular-3.1.5.p9
>> Attempting to download package singular-3.1.5.p9
>> >>> Trying to download
>> http://www.sagemath.org/packages/upstream/singular/singular-3.1.5.tar.bz2
>> [............................................................]
>> Checksum: b4834021a4b44f43806cca2561ec942dc2185c17 vs
>> b4834021a4b44f43806cca2561ec942dc2185c17
>> singular-3.1.5.p9
>> ....
>>
>> Does anyone know where the 'local metadata for singular 3.1.5.p9" can be
>> found?
>>
>> Possibly there is also something wrong my how I have configured git. From
>> $SAGE_ROOT I'm using:
>>
>> git remote -v
>> trac g...@trac.sagemath.org:sage.git (fetch)
>> trac g...@trac.sagemath.org:sage.git (push)
>>
>> git status -b
>> On branch master
>> Your branch is up-to-date with 'trac/master'.
>>
>> My $SAGE_ROOT/.git/config contains, among other things, the following:
>>
>> [core]
>> repositoryformatversion = 0
>> filemode = true
>> bare = false
>> logallrefupdates = true
>> ignorecase = true
>> precomposeunicode = false
>> [remote "trac"]
>> url = g...@trac.sagemath.org:sage.git
>> fetch = +refs/heads/*:refs/remotes/trac/*
>> [branch "master"]
>> remote = trac
>> merge = refs/heads/master
>>
>> Is there anything obviously wrong here?
>>
>> Andrew
>>
>>
>>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
