Please don't. It's something that will need to be done before positive
review, but because we're using git, the branch can still be reviewed
(especially because relatively trivial merge conflicts).
Best,
Travis
On Friday, May 16, 2014 8:53:21 PM UTC-7, Ralf Stephan wrote:
>
> And set the ticke
And set the ticket to needs-work, *beg*...
On Friday, May 16, 2014 1:19:08 PM UTC+2, Wilfried Lübbe wrote:
> Recently I had a ticket waiting for review. The branch merged cleanly with
> develop.
>
>
> As the develop branch moved to Sage-6.3.beta1 merge conflicts emerged (pun
> intended ;-): th
Montgomery-Smith, Stephen wrote:
On 05/16/2014 05:38 PM, leif wrote:
Montgomery-Smith, Stephen wrote:
I was building sage-6.2 using FreeBSD. I found out that the subpackage
libm4ri was picking up the system libpng rather than the sage libpng. I
was able to fix it with the following patch:
--
No PKG* variables were set by my system.
pkgconf-0.9.5
http://svnweb.freebsd.org/ports/head/devel/pkgconf/
I looked at the dates on pkg-config in $SAGE_ROOT/local/bin, and it was
created 4 seconds after libm4ri-20130416 was installed.
I did create a ticket, but you can close it if you like.
http
leif wrote:
Montgomery-Smith, Stephen wrote:
I was building sage-6.2 using FreeBSD. I found out that the subpackage
libm4ri was picking up the system libpng rather than the sage libpng.
? We prepend Sage's pkg-config dir to PKG_CONFIG_PATH in sage-env...
Or actually no longer... This is now
Besides which existing PKG* variables were set, it would also be
interesting to know which pkg-config implementation is installed in your
system.
On Friday, May 16, 2014 9:04:08 PM UTC+1, Stephen Montgomery-Smith wrote:
>
> I was building sage-6.2 using FreeBSD. I found out that the subpackag
On 05/16/2014 05:38 PM, leif wrote:
> Montgomery-Smith, Stephen wrote:
>> I was building sage-6.2 using FreeBSD. I found out that the subpackage
>> libm4ri was picking up the system libpng rather than the sage libpng. I
>> was able to fix it with the following patch:
>>
>> --- build/pkgs/libm4ri/
Montgomery-Smith, Stephen wrote:
I was building sage-6.2 using FreeBSD. I found out that the subpackage
libm4ri was picking up the system libpng rather than the sage libpng. I
was able to fix it with the following patch:
--- build/pkgs/libm4ri/spkg-install-orig2014-05-16
18:34:53.0
Consider the following:
sage: from sage.misc.sageinspect import sage_getfile, sage_getsource
sage: sage_getsource(integrate) in open(sage_getfile(integrate),'r').read()
True
This is good: the source actually occurs as a substring in the file
reported to contain the source. We're not so lucky wit
I just booked a room at Hotel Deca with two queen size beds. I would be
happy to have a roommate.
TJ
On Sunday, May 11, 2014 10:35:04 AM UTC-5, Rob Beezer wrote:
>
> There is still some travel funding available, should you wish to attend
> Edu Days 6 in Seattle in June. Contact me off-list as
I was building sage-6.2 using FreeBSD. I found out that the subpackage
libm4ri was picking up the system libpng rather than the sage libpng. I
was able to fix it with the following patch:
--- build/pkgs/libm4ri/spkg-install-orig2014-05-16
18:34:53.0 +
+++ build/pkgs/libm4ri/s
On Fri, May 16, 2014 at 1:35 AM, mmarco wrote:
> What about the days before 19?
Participants will stay at a hotel those days, and we'll be meeting on campus.
>
> El jueves, 15 de mayo de 2014 22:44:32 UTC+2, William escribió:
>>
>> Here's an update on the Sage days in June in Seattle.
>>
>> We w
Hi,
is there any chance to have binaries for Ubuntu 12.04 LTS (32 bit)?
I have an Ubuntu installation with no Internet connectivity and need to run
Sage on it.
Currently, with the binaries for 13.04 I have problems with the Glibc
version (2.17 required, 2.15 available in Ubuntu 12.04).
any help
On 2014-05-16, Jason Grout wrote:
> On 5/15/14, 7:36, Dima Pasechnik wrote:
>> And, by the way, should Sage get a DOI?
>> This looks doable, only one probably needs to be an "Owner" of
>> https://github.com/sagemath/sage
>> and not just "team member".
>>
>
> Interesting. So would this mean that w
>
> If someone is interested in getting numpy-1.8.1/scipy-0.14.0 in sage,
> they can review http://trac.sagemath.org/ticket/16299
I just reviewed it. Thanks for doing this, I recently ran into an annoying
memory leak in numpy 1.7.0, which was fixed in 1.7.1 (and 1.8.1).
Nathan
--
You re
>
> > The optional package ChomP installs cleanly but then does not actually
> > work on Sage 6.1.1 on OS X Mavericks.
>
> Seems this is fixed in Sage 6.2.
>
You're completely right, sorry about that. For some reason, I thought Sage
6.2 was still in beta and so didn't test it there. I tried
It would be great if that worked. I disabled the tmp directory for the
moment and am testing all tickets in the same directory, but that can leave
the tree in a bad state.
Peter
Op vrijdag 16 mei 2014 10:03:01 UTC+1 schreef Ralf Stephan:
>
> Ah I finally found the relevant upstream ticket:
>
On 5/15/14, 7:36, Dima Pasechnik wrote:
And, by the way, should Sage get a DOI?
This looks doable, only one probably needs to be an "Owner" of
https://github.com/sagemath/sage
and not just "team member".
Interesting. So would this mean that we can tell people at
http://wiki.sagemath.org/Publ
Recently I had a ticket waiting for review. The branch merged cleanly with
develop.
As the develop branch moved to Sage-6.3.beta1 merge conflicts emerged (pun
intended ;-): the branch color had changed from green to red. I learned
this more or less by chance.
Would it be possible to reveive an
Ah I finally found the relevant upstream ticket:
https://bitbucket.org/pypa/setuptools/issue/168/ez_setuppy-failing-sporadically-when
which appears resolved with setuptools-3.5.2
Next is testing of a version >= 3.5.2
Regards,
On Thursday, May 15, 2014 9:53:36 AM UTC+2, Ralf Stephan wrote:
>
> It
What about the days before 19?
El jueves, 15 de mayo de 2014 22:44:32 UTC+2, William escribió:
>
> Here's an update on the Sage days in June in Seattle.
>
> We will have a large house near UW June 19 - 30:
>
> http://www.homeaway.com/vacation-rental/p906894
>
>
> On Fri, Apr 4, 2014 at 2:25
21 matches
Mail list logo
