On May 13, 2014, at 08:34 , Volker Braun wrote:
> Get it from the updated "develop" git branch or the source tarball
> at http://boxen.math.washington.edu/home/release/sage-6.3.beta1.tar.gz
Built 6.3-beta1 (both 10.6.8, Dual 6-core Xeons and 10.9.2, Quad core Core i7)
and ran a 'ptestlong' tes
On May 10, 2014, at 13:33 , Volker Braun wrote:
> Get the updated the "develop" branch for the latest Sage beta version.
Built 6.3-beta0 (both 10.6.8, Dual 6-core Xeons and 10.9.2, Quad core Core i7)
From Lief's tarball, and ran a 'ptestlong' test. All tests passed.
Justin
--
Justin C. Walk
On May 6, 2014, at 08:39 , Volker Braun wrote:
> Now both the "master" and the "develop" git branch have been updated to the
> new release. A more detailed changelog and binary packages will be posted
> later. Source tarball (Harald: please mirror):
>
> http://boxen.math.washington.edu/home/re
Hi John,
On 2014-05-13, John H Palmieri wrote:
> In git's 'configure' script, it says:
>
> libexecdir='${exec_prefix}/libexec'
>
> and on the few platforms to which I have access, I see libexec, not lib.
> What platform are you using?
openSuse 12.3
> Do you have any environment variables s
Simon King wrote:
Anyway. Worse is: The tests in sage.dev fail as before. And it seems to
be because of the "git" that comes with sage: When I use the system git,
then of course "git pull" works. But in a sage shell, I get:
(sage-sh) king@linux-etl7:sage$ git pull
git: 'pull' ist kein Git-Komman
In git's 'configure' script, it says:
libexecdir='${exec_prefix}/libexec'
and on the few platforms to which I have access, I see libexec, not lib.
What platform are you using? Do you have any environment variables set
which could be interfering with this?
John
On Tuesday, May 13, 2014
Hi again,
On 2014-05-13, Simon King wrote:
> Anyway, this was with 6.3.beta0, and I now retry with beta1.
Frankly I am disappointed about the current quality of doc-building.
After pulling, "make" fails with
Note: incremental documentation builds sometimes cause spurious
error messages. To be c
http://trac.sagemath.org/ticket/16350
but is the git install right or sage-env?
Followup at the ticket page...
On Tue, May 13, 2014 at 6:01 PM, Ralf Stephan wrote:
> No sage -f git:
> execdir=$(cd '/home/ralf/sage/local/lib/git-core' && pwd) && \
>
> lib not libexec
>
>
> On Tue, May 13, 2014
No sage -f git:
execdir=$(cd '/home/ralf/sage/local/lib/git-core' && pwd) && \
lib not libexec
On Tue, May 13, 2014 at 5:59 PM, John H Palmieri wrote:
>
>
> On Tuesday, May 13, 2014 8:50:47 AM UTC-7, Ralf Stephan wrote:
>>
>> GIT_EXEC_PATH=/home/ralf/sage/local/libexec/git-core
>> but git is in
On Tuesday, May 13, 2014 8:50:47 AM UTC-7, Ralf Stephan wrote:
>
> GIT_EXEC_PATH=/home/ralf/sage/local/libexec/git-core
> but git is in local/bin/?
>
local/libexec/git-core should contain many executables (like
"git-checkout", "git-clone", etc.) which get run when you do a command like
"git ch
GIT_EXEC_PATH=/home/ralf/sage/local/libexec/git-core
but git is in local/bin/?
On Tue, May 13, 2014 at 5:46 PM, Simon King wrote:
> Hi Volker,
>
> On 2014-05-13, Volker Braun wrote:
> > Get it from the updated "develop" git branch or the source tarball
>
> You mean I shall now pull from trac?
Hi Ralf,
On 2014-05-13, Ralf Stephan wrote:
> GIT_EXEC_PATH=/home/ralf/sage/local/libexec/git-core
> but git is in local/bin/?
king@linux-etl7:~/Sage/git/sage> which git
/usr/bin/git
sage-sh) king@linux-etl7:sage$ which git
/home/king/Sage/git/sage/local/bin/git
Anyway, this was with 6.3.beta0,
Hi Volker,
On 2014-05-13, Volker Braun wrote:
> Get it from the updated "develop" git branch or the source tarball
You mean I shall now pull from trac?
Anyway, with commit fa885d90d609c8311d8fa52deac1340cd558b5a9 I get, for
example:
ralf@ark:~/sage> ls -l local/libexec/git-core
ls: cannot access local/libexec/git-core: No such file or directory
On Tue, May 13, 2014 at 5:27 PM, Peter Bruin wrote:
> These look a lot like the failures I got after moving my Sage
> installation, and which were fixed by #15901, but that ticket
That's what I call a Combinatorial Designs Release :-P
Helll YEAH
Nathann
P.S. : Thaaanks Volker ! ;-)
On 13 May 2014 17:34, Volker Braun wrote:
> Get it from the updated "develop" git branch or the source tarball at
> http
Get it from the updated "develop" git branch or the source tarball
at http://boxen.math.washington.edu/home/release/sage-6.3.beta1.tar.gz
Mini-changelog:
36af814 Trac #16265: transducers.weight: new common transducer
bbc23e1 Trac #15099: Implement numeric evaluation of zetaderiv
cf5d0ef Trac #16
These look a lot like the failures I got after moving my Sage installation,
and which were fixed by #15901, but that ticket was merged in 6.3.beta0...
Peter
Op dinsdag 13 mei 2014 16:12:44 UTC+1 schreef Simon King:
>
> Hi Releasers,
>
> On 2014-05-11, Ralf Stephan > wrote:
> > I get doctest f
It works on the buildbot which errors do you get?
On Tuesday, May 13, 2014 4:12:44 PM UTC+1, Simon King wrote:
>
> Hi Releasers,
>
> On 2014-05-11, Ralf Stephan > wrote:
> > I get doctest failures in dev/sagedev.py that go away when I switch to
> > master and make, but won't go away in dev
Hi Releasers,
On 2014-05-11, Ralf Stephan wrote:
> I get doctest failures in dev/sagedev.py that go away when I switch to
> master and make, but won't go away in develop with make (at least not
> always 8-/).
Just for the record, testing dev/sagedev.py with the sage-6.3.beta0
branch results in
Am 2014-05-13 10:01, schrieb Volker Braun:
> Are you volunteering to write the announcement? ;-)
No ;)
--
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 sage-rele
Are you volunteering to write the announcement? ;-)
On Tuesday, May 13, 2014 8:26:05 AM UTC+1, Daniel Krenn wrote:
>
> Is there a reason, why there is still no official announcement (e.g. in
> sage-announce) of Sage 6.2?
>
>
--
You received this message because you are subscribed to the Google
Am 2014-05-06 17:39, schrieb Volker Braun:
> Now both the "master" and the "develop" git branch have been updated to
> the new release. A more detailed changelog and binary packages will be
> posted later. Source tarball (Harald: please mirror):
Is there a reason, why there is still no official an
22 matches
Mail list logo
