On 2014-08-15, Volker Braun wrote:
> --=_Part_231_1213945713.1408086090167
> Content-Type: text/plain; charset=UTF-8
>
> On Friday, August 15, 2014 6:25:05 AM UTC+1, kcrisman wrote:
>>
>> That's silly, especially because often someone else writes your name and
>> in the deluge of tickets it's
If you want to update your local "master" branch you should do:
git checkout master# switch to your local master branch
git pull --ff-only trac master
On Tuesday, August 12, 2014 1:26:30 PM UTC+1, Andrew wrote:
>
> git pull --ff-only 6.3
> not the recommended way to update the master branch t
Hmm, I have another issue then because, as shown above, the only 6.3 tag
that I am getting is 6.3.beta0 (my list is also alphabetical, it's just
missing all of the other 6.3 tags).
OK, I just fixed my problem with a "git fetch".
*Question*: Is
git pull --ff-only 6.3
not the recommended way t
The tags are in alphabetical order:
$ git tag | tail -15
6.2.rc0
6.2.rc1
6.2.rc2
6.3
6.3.beta0
6.3.beta1
6.3.beta2
6.3.beta3
6.3.beta4
6.3.beta5
6.3.beta6
6.3.beta7
6.3.beta8
6.3.rc0
6.3.rc1
On Tuesday, August 12, 2014 3:17:37 AM UTC+1, Andrew wrote:
>
> I compiled 6.3 happily on my macbook pro
On 12.08.2014 09:34, Jeroen Demeyer wrote:
On 2014-08-11 21:53, John H Palmieri wrote:
I guess they're being installed and the error message is
misleading. A number of packages produce the same error but also install
correctly.
That is indeed the case. There is an "mv" command in sage-spkg whic
On 2014-08-11 21:53, John H Palmieri wrote:
I guess they're being installed and the error message is
misleading. A number of packages produce the same error but also install
correctly.
That is indeed the case. There is an "mv" command in sage-spkg which is
not needed for all packages:
if [ "$U
I compiled 6.3 happily on my macbook pro running macosx 10.9.4.
┌┐
│ Sage Version 6.3, Release Date: 2014-08-10 │
│ Type "notebook()" for the browser-based notebook interface.│
│ Type "help()" for
On Monday, August 11, 2014 10:15:19 AM UTC-7, Volker Braun wrote:
>
> According to the gp manpage the directories should be called galdata/ and
> seadata/... I don't know how to test that they are being found, though.
>
Oh, I see them. I guess they're being installed and the error message is
m
According to the gp manpage the directories should be called galdata/ and
seadata/... I don't know how to test that they are being found, though.
On Monday, August 11, 2014 4:56:56 PM UTC+1, John H Palmieri wrote:
>
> This has probably been an issue for a while, but I hadn't noticed until
> no
On Sunday, August 10, 2014 8:31:01 AM UTC-7, Volker Braun wrote:
>
> Both the "master" and "develop" git branch have been updated to the 6.3
> release.
>
> Source tarball:
> http://boxen.math.washington.edu/home/release/sage-6.3.tar.gz
>
> sha512sum sage-6.3.tar.gz
> 03f8016ddd5029915846be01a6
Oh OK. This is a really old system and I don't have admin rights.
I guess AFM = Adobe Font Metrics, seems like something is wrong with your
system fonts.
On Monday, August 11, 2014 9:55:11 AM UTC+1, P Purkayastha wrote:
>
> File "src/doc/de/tutorial/tour_functions.rst", line 24, in doc.de.tutorial
I guess AFM = Adobe Font Metrics, seems like something is wrong with your
system fonts.
On Monday, August 11, 2014 9:55:11 AM UTC+1, P Purkayastha wrote:
>
> File "src/doc/de/tutorial/tour_functions.rst", line 24, in doc.de.tutorial
> .tour_functions
> Failed example:
> plot(f, 0, 2)
> Expect
On Sunday, August 10, 2014 11:31:01 PM UTC+8, Volker Braun wrote:
>
> Both the "master" and "develop" git branch have been updated to the 6.3
> release.
>
Got some strange doctest failures on "make ptestlong" on this system:
.../src/sage/sage-6.3.server> uname -a
Linux spms-banana 2.6.32-5-amd
13 matches
Mail list logo
