On Mon, Jun 6, 2016 at 5:25 AM, William Stein wrote:
> We had tons of discussion on sage-devel about exactly this topic
> recently. One thing is that Chris made
>
> https://github.com/cswiercz/sage_packages
>
> but that seems to have gone nowhere.
>
> I think that **all** development of Sage sho
On 06/07/16 07:28, Jack Dyson wrote:
Hi everyone,
I'd appreciate some help on this: I need to use mixtools on R in sage
for the ER stuff they have. It turns out you need R 3.2.4 or better.
I thought of (a) upgrading the sage internal R or (b) using the system
wide one that I have on sagemath 7.
Yes that's new. Although it is disabled for fat binaries, but there is
no easy way to disable it from outside spkg-install.
Francois
On 06/07/16 08:08, Nathan Dunfield wrote:
I have successfully compiled Sage 7.2, which has an earlier version
of NTL, from source on both 10.8 and 10.9.
>
> I have successfully compiled Sage 7.2, which has an earlier version of
> NTL, from source on both 10.8 and 10.9.
>
Checking the logs for my Sage 7.2 builds, the old NTL version 9.6.2 spkg
did *not* specify the "-march=native" flag on 10.8 and 10.9, unlike the
current spkg for 9.8.1.
Nath
>
> Did you compile sage yourself on the same machine on which you are trying
> to update the NTL package or are using a binary distribution built on >10.9
> ?
>
I was doing a clean Sage build from scratch against the git commit
(715566f4bf9) corresponding to 7.3.beta3. I have successfully co
Did you compile sage yourself on the same machine on which you are trying
to update the NTL package or are using a binary distribution built on >10.9
?
In the latter case, I am pretty sure it is a different manifestation of the
problem from http://trac.sagemath.org/ticket/20563
On Sunday, June
Hi everyone,
I'd appreciate some help on this: I need to use mixtools on R in sage for
the ER stuff they have. It turns out you need R 3.2.4 or better.
I thought of (a) upgrading the sage internal R or (b) using the system wide
one that I have on sagemath 7.2, passing data back and forth from s
Le 06/06/2016 17:17, Ralf Stephan a écrit :
> On Monday, June 6, 2016 at 4:22:02 PM UTC+2, Dima Pasechnik wrote:
>
> Or perhaps someone pulled a full private copy recently?
>
>
> Around end of April, I think, someone better?
>
> ralf@ark:~/sage/.git> find logs/refs/remotes/trac/| wc
> 723
>
> I will setup SSL once the
> domain name is correct (not before tomorrow).
>
>
>
Will you need the old certificate or plan to generate a new one?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop rece
I can confirm Sage 7.3.beta3 builds on OS X 10.11 (El Capitan)
On Sunday, June 5, 2016 at 6:47:29 PM UTC-7, Nathan Dunfield wrote:
>
> On OS X versions 10.8 (Mountain Lion) and 10.9 (Mavricks), the recently
> updated NTL package fails to build with the following error (complete log
> also attach
On 2016-06-06 17:48, Dima Pasechnik wrote:
I don't know how to create a working repo from .git/ alone...
Just checkout something and then "git reset --hard" works.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group a
On Mon, Jun 6, 2016 at 1:21 PM, Eric Gourgoulhon wrote:
>
> Le lundi 6 juin 2016 19:08:44 UTC+2, Thierry (sage-googlesucks@xxx) a écrit
> :
>>
>> Hi,
>>
>> the wiki is back online at University Paris North :
>> http://sagewiki.lipn.univ-paris13.fr/
>>
>
> Thank you very much Thierry!
Thank you!
Le lundi 6 juin 2016 19:08:44 UTC+2, Thierry (sage-googlesucks@xxx) a
écrit :
>
> Hi,
>
> the wiki is back online at University Paris North :
> http://sagewiki.lipn.univ-paris13.fr/
>
>
Thank you very much Thierry!
I've checked it on recently modified pages: the Sage Days 74 ones.
Everything i
Please someone switch the DNS to point to the resurrected sage wiki.
(cc-ing Harald in case he can do it).
Thanks Thierry!
Samuel
Le lundi 6 juin 2016 19:08:44 UTC+2, Thierry (sage-googlesucks@xxx) a
écrit :
>
> Hi,
>
> the wiki is back online at University Paris North :
> http://sagewiki.lip
Hi,
the wiki is back online at University Paris North :
http://sagewiki.lipn.univ-paris13.fr/
It should work with wiki.sagemath.org domain name so please do not
hesitate to switch the DNS to 194.254.163.84. I will setup SSL once the
domain name is correct (not before tomorrow).
Once the data wil
On Monday, June 6, 2016 at 4:13:43 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-06-06 16:44, Dima Pasechnik wrote:
> > And put it somewhere public, e.g. on github.
>
> I have simply tarred up my .git directory at
>
> http://sage.ugent.be/www/jdemeyer/sagetrac-git.tar.bz2
>
I copied it to GCE
IMHO thats not a big deal, some orgs are experimenting with permanently
running datacenters at 90+F...
The best course of action is probably to wait and get the machines back up.
Then slowly move the infrastructure out of UW.
On Monday, June 6, 2016 at 11:27:39 AM UTC-4, Dima Pasechnik wrote:
On Monday, June 6, 2016 at 3:57:41 PM UTC+1, William wrote:
>
> Hello,
>
> The sysadmin just explained what happened -- namely the room has been
> cooking all weekend due to an AC failure: This means that everything
> might -- or might not -- come back in the next few days. There is no
> way
On Monday, June 6, 2016 at 4:22:02 PM UTC+2, Dima Pasechnik wrote:
> Or perhaps someone pulled a full private copy recently?
>
Around end of April, I think, someone better?
ralf@ark:~/sage/.git> find logs/refs/remotes/trac/| wc
72317231 368968
--
You received this message because you a
On 2016-06-06 17:06, William Stein wrote:
And yet you can do anything you want in setup.py... It's not hard to
get around that.q
First of all, those hacks will most likely break setup.py in one way or
another. For example, they might break wheel or "setup.py dist" or whatever.
Second, why sh
On 2016-06-06 16:44, Dima Pasechnik wrote:
And put it somewhere public, e.g. on github.
I have simply tarred up my .git directory at
http://sage.ugent.be/www/jdemeyer/sagetrac-git.tar.bz2
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsu
On Mon, Jun 6, 2016 at 11:01 AM, Jeroen Demeyer wrote:
> On 2016-06-06 16:05, William Stein wrote:
>>
>> Isn't there one canonical one to use now?
>
>
> I guess the "canonical" one is setuptools. But setuptools makes the annoying
> assumption that a Python package is completely self-contained and
On 2016-06-06 16:44, Dima Pasechnik wrote:
And put it somewhere public, e.g. on github.
I don't think I can push 6930 branches to github. After a while, I get
this error:
error: failed to push some refs to 'https://github.com/jdemeyer/sage.git'
error: git-remote-https died of signal 13
--
Y
On 2016-06-06 16:05, William Stein wrote:
Isn't there one canonical one to use now?
I guess the "canonical" one is setuptools. But setuptools makes the
annoying assumption that a Python package is completely self-contained
and that no other software ever needs to use files from that Python
p
Hello,
The sysadmin just explained what happened -- namely the room has been
cooking all weekend due to an AC failure: This means that everything
might -- or might not -- come back in the next few days. There is no
way to know the extent of the damage, if any.
---
"The PDL C28 server room AC un
On 2016-06-06 16:44, Dima Pasechnik wrote:
And put it somewhere public, e.g. on github.
git fetch trac --all
(or perhaps even just 'git fetch trac' would have produced a full backup)
I did "git fetch trac" after the Sage 7.3.beta3 upgrade, so very recently.
--
You received this message becaus
On Monday, June 6, 2016 at 3:30:55 PM UTC+1, Frédéric Chapoton wrote:
>
> I do not think that the patchbots clients have a copy of the full git
> repo. They only pull branches. But they have the branch for 7.3.beta3, at
> least.
>
this one is just here: https://github.com/sagemath/sage/tree/deve
It's a devastating blow. But we will rebuild.
https://imgflip.com/i/15dnsh
On Monday, 6 June 2016 16:32:12 UTC+2, Dima Pasechnik wrote:
>
> Also flint/mpir/nemo sites are down (flint people know this), due to being
> on the same cluster of machines...
>
> On Monday, June 6, 2016 at 3:22:02 PM UT
And put it somewhere public, e.g. on github.
git fetch trac --all
(or perhaps even just 'git fetch trac' would have produced a full backup)
(please excuse my ignorance, I don't know how to make such a recovery repo
quickly - but first we need to find the data...)
Dima
--
You received this me
Also flint/mpir/nemo sites are down (flint people know this), due to being
on the same cluster of machines...
On Monday, June 6, 2016 at 3:22:02 PM UTC+1, Dima Pasechnik wrote:
>
>
>
> On Monday, June 6, 2016 at 2:18:36 PM UTC+1, Jeroen Demeyer wrote:
>>
>> On 2016-06-06 13:09, Thierry wrote:
>>
I do not think that the patchbots clients have a copy of the full git repo.
They only pull branches. But they have the branch for 7.3.beta3, at least.
Frederic
Le lundi 6 juin 2016 16:22:02 UTC+2, Dima Pasechnik a écrit :
>
>
>
> On Monday, June 6, 2016 at 2:18:36 PM UTC+1, Jeroen Demeyer wrote:
On Monday, June 6, 2016 at 2:18:36 PM UTC+1, Jeroen Demeyer wrote:
>
> On 2016-06-06 13:09, Thierry wrote:
> > For the git/trac, i am not sure that it is a good idea to put a 2-weeks
> > backup read/write, because it will be awful to merge with the current
> > state. It is imho much better to
On Monday, June 6, 2016, Jeroen Demeyer wrote:
> On 2016-06-06 05:25, William Stein wrote:
>
>> I think that **all** development of Sage should be done using standard
>> Python packaging.Of course Cython is very well supported using
>> setuptools
>>
>
> or distutils if you prefer that.
Isn'
On 2016-06-06 05:25, William Stein wrote:
I think that **all** development of Sage should be done using standard
Python packaging.Of course Cython is very well supported using
setuptools
or distutils if you prefer that.
--
You received this message because you are subscribed to the Google
On Mon, Jun 6, 2016 at 9:42 AM, Volker Braun wrote:
> The buildbot is gone, too.
>
> I'm also travelling this week and don't have much time to do anything...
>
> Especially for trac with our custom plugins I'd really prefer a docker
> container with a working Dockerfile than a random VM that has b
The buildbot is gone, too.
I'm also travelling this week and don't have much time to do anything...
Especially for trac with our custom plugins I'd really prefer a docker
container with a working Dockerfile than a random VM that has been prodded
by dozens of people over the course of years.
http://patchbot.sagemath.org/ is now also affected, even if it was working
at some point after trac's failure.
Frédéric
Le lundi 6 juin 2016 14:48:47 UTC+2, William a écrit :
>
> I've sent invites to the Google compute engine project to the following
> people.
>
> - Andrew O
> - Dima P
>
On Mon, Jun 06, 2016 at 03:18:33PM +0200, Jeroen Demeyer wrote:
> On 2016-06-06 13:09, Thierry wrote:
> >For the git/trac, i am not sure that it is a good idea to put a 2-weeks
> >backup read/write, because it will be awful to merge with the current
> >state. It is imho much better to have some dow
On Monday, June 6, 2016 at 2:48:47 PM UTC+2, William wrote:
>
> I've sent invites to the Google compute engine project to the following
> people.
>
How do people coordinate usually in this setting? Mail cc? chat? group?
--
You received this message because you are subscribed to the Google Gro
On 2016-06-06 13:09, Thierry wrote:
For the git/trac, i am not sure that it is a good idea to put a 2-weeks
backup read/write, because it will be awful to merge with the current
state. It is imho much better to have some downtime since people can still
work on their local branch.
Sure, but the
Hi,
i am currently working on the wiki (my backup is <2days so there is almost
no lose, and it will be easy to merge the very few changes once we can
access the current sate).
For the git/trac, i am not sure that it is a good idea to put a 2-weeks
backup read/write, because it will be awful to me
and Ralf Stephan.
NOTE: the backups are in /orig on each machine.
On Mon, Jun 6, 2016 at 8:48 AM, William Stein wrote:
> I've sent invites to the Google compute engine project to the following
> people.
>
> - Andrew O
> - Dima P
> - Volker B
> - Erik B
> - Samuel L
>
> On Mon, Jun 6
On Mon, Jun 6, 2016 at 4:29 AM, Erik Bray wrote:
> On Sun, Jun 5, 2016 at 7:27 PM, William Stein wrote:
>> Hi sage devel,
>>
>> According to my monitors trac and wiki are down. I have no idea why. I'm
>> boarding a plane out of town now...
>
> I thought that the Trac site was hosted on Google--
I've sent invites to the Google compute engine project to the following people.
- Andrew O
- Dima P
- Volker B
- Erik B
- Samuel L
On Mon, Jun 6, 2016 at 6:22 AM, Jeroen Demeyer wrote:
> On 2016-06-06 10:33, Erik Bray wrote:
>>
>> I think one of the best things about Sage's development
On Sunday, June 5, 2016 at 11:49:55 PM UTC-5, leif wrote:
>
> Well, GCC accepting '-march=native' doesn't imply the dumb Apple
> assembler accepts all the instructions (here AVX) GCC then emits...
>
If you pass gcc the flag "-Wa,-q", then it will use clang's assembler
rather than the ancient ve
Would it be technically possible to host all these services in different
physical locations (syncronized, of course), and use some kind of load
balancer to handle the falldown of one of them?
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To un
On 2016-06-06 10:33, Erik Bray wrote:
I think one of the best things about Sage's development is that it's
using Trac. GitHub's issue tracker is awful by comparison, especially
for the volume of issues Sage generates.
I agree.
3. Configure trac.sagemath.org and wiki.sagemath.org so they work
On 2016-06-06 10:39, Erik Bray wrote:
But then you have to deal with the usual mess of ensuring that
the __rdiv__ method handles division for those objects.
FYI: __rdiv__ does not exist in Cython (__div__ is always used), so
there is not so much mess.
--
You received this message because you
On Monday, June 6, 2016 at 9:29:58 AM UTC+1, Erik Bray wrote:
>
> On Sun, Jun 5, 2016 at 7:27 PM, William Stein > wrote:
> > Hi sage devel,
> >
> > According to my monitors trac and wiki are down. I have no idea why.
> I'm
> > boarding a plane out of town now...
>
> I thought that the Tr
On Monday, June 6, 2016 at 7:03:42 AM UTC+1, Ralf Stephan wrote:
>
> On Monday, June 6, 2016 at 5:10:16 AM UTC+2, William wrote:
>>
>> There is also a wiki here https://github.com/sagemath/sage/wiki
>> At some point migrate the data on wiki.sagemath.org to github (maybe
>> remove all images if
On Thu, Jun 2, 2016 at 4:22 PM, Jeroen Demeyer wrote:
> On 2016-06-02 15:52, Erik Bray wrote:
>> 2. I know this is probably anathema to mathematicians, but couldn't
>> "1/" be viewed as a two character unary operator meaning reciprocal?
>> :)
>
>
> Sort of, but keep in mind efficiency. Often, taki
On Mon, Jun 6, 2016 at 5:09 AM, William Stein wrote:
> Hi,
>
> Yesterday a machine at UW (the one hosting *.sagenb.org) was attacking
> other computers, so the UW shut it down.
> Today trac, the wiki, and many other machines crashed.
>
> I'm traveling, so can't look into the hardware anytime soon.
On Sun, Jun 5, 2016 at 7:27 PM, William Stein wrote:
> Hi sage devel,
>
> According to my monitors trac and wiki are down. I have no idea why. I'm
> boarding a plane out of town now...
I thought that the Trac site was hosted on Google--at least, that was
the impression Samuel got when he brough
---
ImportError Traceback (most recent call last)
in ()
> 1 load('http://')
2 load('http://')
3
/home/sc_serv/sage/src/sage/structure/sage_object.pyx in
sage.structure.s
54 matches
Mail list logo
