If I recall, when I originally setup the git-trac server, I included a hook
that would reject/warn any introduction of new trailing whitespace. I
believe this was a compromise made after a long discussion at a Sage days
-- there were a lot of concerns at the time about the effort required to
rebase
On Tue, Apr 12, 2016 at 12:50 PM, kcrisman wrote:
> It doesn't mean that the normal visible
>> public API of Sage changes
>> at all. Why do you think otherwise?
>>
>
> Well, reading this thread made me think that. Because I don't see how we
> enforce all those "other pieces" working nicely to
On Wed, Jan 20, 2016 at 5:27 PM, William Stein wrote:
> Hi,
>
> I thought about this some more today: I personally have zero interest
> or time for personally running wiki.sagemath.org anymore. It's just
> been coasting for the last year or two. The moment some spammer takes
> it over, the UW w
At this point it all of sage's dependencies build with python 3, so if you
do the following
SAGE_PYTHON3=yes make
it will fail building some cython module in the sage library.
On Sat, Nov 14, 2015 at 7:45 PM, Nathan Dunfield
wrote:
> can someone summarize the status on making SageMath Pyth
You are using the read only git url, you need to use the ssh url to be able
to push. You can either add a new remote:
git remote add trac g...@trac.sagemath.org:sage.git
or modify your current remote:
git remote set-url origin g...@trac.sagemath.org:sage.git
On Mon, Sep 21, 2015 at 7:1
I just updated the project with some excel + csv files with a much more
indepth inventory.
Also, concerning ansible -- this is what I used when working on things this
summer (see https://github.com/ohanar/sagemath.org). I found that when you
use any well supported plugin, using ansible was very pl
As William mentioned, I don't really have the time to work on administering
the cluster, but I would be happy to part of the initial discussions (e.g
what I was planning on doing if I had the time, why I chose centos,
in-depth inventory of hardware, etc).
--
You received this message because you
Sage.math points to wstein.org (as per an earlier request by William). As
far as I'm aware, he is the only one with credentials to that system, I
certainly don't have access.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this
Everybody was warned that things would go down back in April, so you should
have dealt with it awhile ago (but apparently didn't).
We can easily setup a redirect on the VM that hosts wstein.org (which is
where sage.math.washington.edu redirects to) if you find a place to host
your site. If your si
On Mon, Aug 24, 2015 at 6:25 AM, kcrisman wrote:
>
>>> trac and wiki accounts used to be linked (same username, same password).
>>> I
>>> changed my password on trac and it worked, but i can not use it on the
>>> wiki. Unfortunately, i am travelling and i do not have access to my
>>> previous pas
On Sat, Aug 22, 2015 at 10:07 PM, William Stein wrote:
> On Sat, Aug 22, 2015 at 8:55 PM, R. Andrew Ohana
> wrote:
> >
> >
> > On Sat, Aug 22, 2015 at 4:22 AM, Thierry <
> sage-googlesu...@lma.metelu.net>
> > wrote:
> >>
> >> Hi,
> >
On Sat, Aug 22, 2015 at 4:22 AM, Thierry
wrote:
> Hi,
>
> trac and wiki accounts used to be linked (same username, same password). I
> changed my password on trac and it worked, but i can not use it on the
> wiki. Unfortunately, i am travelling and i do not have access to my
> previous password.
Password reset on our trac instance doesn't work (and I have looked into it
a few times and haven't been able to figure out why it is broken).
I can create a temporary password for you manually and send it to you (at
which point you should be able to change your password from your user
preferences
There was a cron job setup for cleaning /tmp, but I just looked and it
seems like it was disabled... I re-enabled it and manually cleaned it at
the same time.
On Sun, Aug 16, 2015 at 6:48 AM, Vincent Delecroix <
20100.delecr...@gmail.com> wrote:
> Hello,
>
> Again...
>
> """
> Trac detected an in
This should now be resolved.
On Sun, Aug 16, 2015 at 6:10 PM, Kwankyu Lee wrote:
> I looked into this thread because I have the same issue with the following
> ticket.
>
> http://trac.sagemath.org/ticket/18807
>
> Anyway, your ticket URL seems to have no problem :-)
>
> --
> You received this me
On Aug 1, 2015 13:21, "Michael Orlitzky" wrote:
>
> On 07/31/2015 07:51 PM, Andrey Novoseltsev wrote:
> > Hello,
> >
> > While working on http://trac.sagemath.org/ticket/18613 I ran into the
> > following problem:
>
> Argh, the trac notifications still aren't fixed. Can someone please add
> a reve
Trac's ip address changed on Saturday, which that might have broken
something with the email signature. I'll take a look later today.
On Jul 20, 2015 10:27, "Benjamin Hackl" wrote:
> Our mail system alters the subject (probably since today; wasn't like that
> last Thursday) like this:
>
> ***
Most of these sites should now be back up. The patchbot still needs a
little bit of setup (from Robert and Frederic), so it will be down until
they have a chance to look at it.
On Sat, Jul 18, 2015 at 9:26 AM, William Stein wrote:
>
>
> On Friday, July 17, 2015, R. Andrew Oha
Small update, we will be starting at around 8 AM PST tomorrow.
On Sat, Jul 11, 2015 at 18:40 R. Andrew Ohana
wrote:
> Due to lack of funding (as previously mentioned by William), the servers
> that are currently hosting a number of the sagemath sites will need to be
> relocate
On Sun, Jul 12, 2015 at 6:02 AM, Jeroen Demeyer
wrote:
> On 2015-07-12 03:40, R. Andrew Ohana wrote:
>
>> In addition, boxen.math.washington.edu
>> <http://boxen.math.washington.edu> will finally be going offline, and
>> due to lack of space won'
Due to lack of funding (as previously mentioned by William), the servers
that are currently hosting a number of the sagemath sites will need to be
relocated. We are currently planning on doing this next Saturday (i.e.
Saturday July 18), exactly when and for exactly how long is not quite
clear, but
On Sat, Jun 13, 2015 at 5:21 AM, 'Martin Albrecht' via sage-devel <
sage-devel@googlegroups.com> wrote:
> Hi all,
>
> On Saturday 13 Jun 2015 10:41:15 Francois Bissey wrote:
> > I think Andrew has already done quite a bit of the porting to autotools
> and
> > some python 3 fixes. But neither he or
On Fri, Jun 12, 2015 at 5:34 AM, 'Martin Albrecht' via sage-devel <
sage-devel@googlegroups.com> wrote:
> Hi,
>
> so, the Singular team *wants* to keep PolyBoRi alive, but it's currently
> not
> clear if and when they *can* devote resources to it. This will be clarified
> over the next few months
On Thu, Jun 11, 2015 at 2:42 PM, Alexander Dreyer <
jan.alexander.dre...@gmail.com> wrote:
> From my point of view a fork - or better call it sequel - would be the
> best.
>
> Unfortunately, all original developers like me went to industrial
> positions, which are completely unrelated to PolyBoRi
On Wed, Jun 10, 2015 at 6:40 PM, François Bissey <
francois.bis...@canterbury.ac.nz> wrote:
> Hi all,
>
> over at http://trac.sagemath.org/ticket/18437 we have
> some heated debate about what to do about polybori.
>
> Let me summarize the situation.
> * at this moment polybori is dead upstream
> *
If you want to know exactly how it is currently working, it is this one line
https://github.com/sagemath/sage_trac_plugin/blob/dddc41b60a7620ebe0e224973497d83c719d9cd9/sage_trac/git_merger.py#L92
(the rest of that function deals with trivial merges, and writing
unreferenced objects back to trac's
On Tue, May 26, 2015 at 11:53 AM, kcrisman wrote:
>
>
>
>> In the interest of reducing the work required for supporting Python 3,
>> unless there is some champion out there who wants to do the hard work
>> making sagenb work with Python 3, the sage notebook will not be joining the
>> rest of sage
In the interest of reducing the work required for supporting Python 3,
unless there is some champion out there who wants to do the hard work
making sagenb work with Python 3, the sage notebook will not be joining the
rest of sage with Python 3.
So, with that said, is there anyone interested in por
On Mon, May 18, 2015 at 9:29 AM, William Stein wrote:
> On Mon, May 18, 2015 at 8:37 AM, Thierry
> wrote:
> > Hi,
> >
> > On Mon, May 18, 2015 at 01:49:22AM -0700, Harald Schilly wrote:
> >> > Is Sage living in a state of emergency ?
> >>
> >> Yes
> >
> > OK, so we should just breathe, give more
Ok, hopefully it is fixed now. It looks like it is a bug in git (at least
the version that is on the trac server), see [1].
[1]
http://git.661346.n2.nabble.com/Problems-with-stale-keep-files-on-git-server-td6226633.html
On Wed, Apr 15, 2015 at 1:02 PM, R. Andrew Ohana
wrote:
> There is s
There is some permissions issue with the git repository. Working on it...
On Wed, Apr 15, 2015 at 12:28 PM, Dima Pasechnik wrote:
> /tmp or some other filesystem ran out of space?
>
>
> On Wednesday, 15 April 2015 20:09:54 UTC+1, vdelecroix wrote:
>>
>> contamination...
>>
>> http://trac.sagemat
Homebrew tries to avoid exposing headers and libraries for packages that
are already bundled with OS X or have "alternatives" on OS X (e.g. readline
vs libedit) by installing such packages into what they call Cellars. At
least in my personal experience, this has been successful, however I've
instal
On Thu, Jan 8, 2015 at 5:38 PM, kcrisman wrote:
> All our dependencies have proper support for Python 3,
>>
>
> What about 17 and 18 at http://trac.sagemath.org/ticket/15530?
>
Yes, you are right. I had forgotten about those when I posted this. 17
(scons) only exists because of 18 (polybori) and
As an alternative to the Bug Days William mentioned, we could hold a
workshop focused on porting Sage to Python 3 (this has apparently been a
frequent request for SMC).
All our dependencies have proper support for Python 3, so the main effort
at this point in time is porting the Sage library. A lo
The buildbot was having some issues and was reporting everything as a
failure. I disabled it until I get a moment to fix it.
On Tue, Oct 21, 2014 at 1:18 PM, Frédéric Chapoton
wrote:
> Hello,
>
> it seems that the bots have disappeared. Both the buildbot (was top left)
> and the patchbot (top ri
On Sat, Oct 4, 2014 at 2:49 AM, Jonas Jermann wrote:
> Hi
>
> On 04.10.2014 11:18, Ralf Stephan wrote:
>
>> On Saturday, October 4, 2014 12:09:19 AM UTC+2, Jonas Jermann wrote:
>>
>>
>> --
>> sage -t src/sage/crypto/mq/s
On Fri, Oct 3, 2014 at 8:12 AM, Nils Bruin wrote:
> Dear buildboteers,
>
> The new buildbot interface is wonderful. However, on #17065 we ran into an
> issue that "needs work" tickets do not display the buildbot link. That's
> inconvenient in the following scenario:
> 1. Author gets a ticket to
Ok, it should be fixed now. I disabled version control since we shouldn't
be using it anymore (finger's crossed that doesn't break something else
that I missed).
On Mon, Sep 15, 2014 at 12:26 AM, Jeroen Demeyer
wrote:
> The "Search" box on the Trac webpage is broken: any kind of search (for
> ex
.google.com/forum/#!searchin/sage-trac-account/volker%7Csort:date/sage-trac-account/15Wk1fL2XBI/4eM2GZrMQZgJ
> ).
>
Yup, I'm aware. This may or may not have been fixed. If it is still broken,
I don't know how to fix it (seems to be a bug with the plugin).
>
>
>
> Le samed
Ok, I'm done updating. Let me know if I broke anything.
On Fri, Aug 29, 2014 at 7:38 PM, R. Andrew Ohana
wrote:
> I'm about to update the trac server with some bug fixes + the initial
> buildbot support I mentioned in
> https://groups.google.com/forum/#!topic/sage-devel/z
I'm about to update the trac server with some bug fixes + the initial
buildbot support I mentioned in
https://groups.google.com/forum/#!topic/sage-devel/zYpEM7W-7cQ, so trac
will not be reliable for the next little bit. I'll post back here when I'm
done.
--
Andrew
--
You received this message b
Hi Aly,
So it looks like you cloned the git-trac-command repository under your sage
directory and tried to add it (probably accidentally) in this commit:
http://git.sagemath.org/sage.git/commit/?h=u/aly.deines/ticket/13568&id=87d42644c5909a3c3d02881cbe15f8581a39097a
.
Git won't add other git repo
The first version that had 10.9 support was 5.13, although it should be as
simple as applying the patches and spkgs at [1] and [2] to get it to work
on 5.11.
Before any of this, you should work from a clean set of sage sources.
[1] http://trac.sagemath.org/15433
[2] http://trac.sagemath.org/15937
bump.
In case anyone has actual feedback. I will try to roll out these changes
sometime next week.
On Sat, Jun 28, 2014 at 7:03 PM, R. Andrew Ohana
wrote:
> Hi all,
>
> I've been working on setting up an instance of buildbot for the eventual
> replacement of patchbot. It doe
Hi all,
I've been working on setting up an instance of buildbot for the eventual
replacement of patchbot. It doesn't have all the features of patchbot yet,
so for the moment being it is an addition, not a replace.
If you would like to try it out, I have setup a sandbox trac server at
http://trac-
Some observations from this change:
1) The "From Internet" button in the +New tab is right now a complete lie,
and gives un-user friendly error messages. Either you should remove this
button (for now), or somehow make it bypass the whitelist.
2) You cannot ssh out (nor use any services that rely o
Yeah, I also found some morphisms in the polynomial ring code, but like the
QQ <-> ZZ code, it seemed dated (and hence might not follow recommended
practices).
As for sage.algebras.*, I didn't really see anything other than Boolean
return values.
On Fri, Jun 6, 2014 at 9:21 AM, Vincent Delecroix
Ok, follow up question. Is there much documentation on morphisms, or am I
just blind and missing it?
At least as far as I can tell, the documentation on the coercion seems to
recommend implementing morphisms for _coerce_map_from_, but in the toy
examples, only boolean return values are used (which
Hi,
Reading through the documentation (from the latest beta) on the coercion
framework and category framework, it isn't exactly clear to me what the
recommended way to implement a new Parent/Element pair as part of the Sage
ecosystem.
For instance, what is the recommended class I should inherit f
On Sat, May 17, 2014 at 2:27 PM, leif wrote:
> R. Andrew Ohana wrote:
>
>> Well it is a bit different than other changes, since nothing actually
>> changes in the ticket itself (which would prompt a notification). Rather
>> the plugin is just a special render for the br
Well it is a bit different than other changes, since nothing actually
changes in the ticket itself (which would prompt a notification). Rather
the plugin is just a special render for the branch field, so the merge is
not actually checked until someone actually loads the page for the first
time (res
On Thu, May 1, 2014 at 9:30 AM, leif wrote:
> Travis Scrimshaw wrote:
>
>> That happens when you've started making a comment (or any other change
>> to the ticket) as part of the preview.
>>
>
> Hardly related, but is it intentional that trac meanwhile also colors (and
> even strikes!) trac user
On Mon, Apr 28, 2014 at 2:03 PM, Jean-Baptiste Priez wrote:
> Hello,
>
> I would like to know what is the new line which is equivalent to
>
> %load_ext sage.misc.sage_extension
>>
>
> with sage 6.2?
>
%load_ext sage
should now work.
>
> The ticket #16050 (I think...) moved some code so...
>
>
The symbolic link exists for the sole reason that previously you could not
install sagenb as a standard python package (it cared deeply about its
location in the SAGE_ROOT); this was necessary for getting sagenb to
initially work on the git version of Sage. The symbolic link was made (as a
hack) be
On Fri, Apr 4, 2014 at 3:19 AM, Volker Braun wrote:
> What happened to the plan of migrating to another wiki (was it gollum?).
> Just curious ...
>
Got busy with school...
Some work still needed to be done since gollum doesn't scale well with
large repositories (both in number of commits and in
On Fri, Apr 4, 2014 at 3:27 AM, Volker Braun wrote:
> On Friday, April 4, 2014 1:55:40 AM UTC+1, R. Andrew Ohana wrote:
>>
>> I'm a bit confused at what you are saying. I agree that the act of
>> cleaning up the imports is essentially impossible right now due to the
On Thu, Apr 3, 2014 at 3:49 PM, Volker Braun wrote:
>
> Simplifying the import process would definitely be nice. We should have
> some mechanism enforce a somewhat linear order, e.g. by introducing
> barriers where you are only allowed to (module-level) import stuff that
> finished importing befo
Personally I would find it incredibly useful to be able to use Sage as a
Python Library. While this is technically possible at the moment (by doing
"import sage.all" and when done making sure to run "sage.all.quit_sage"),
it isn't very useful, since you still have to import everything in Sage
when
Sorry, bit late to this (mainly got reminded by the 10.4 support thread).
For Solaris support, what about setting up an x86_64 Solaris VM as a
buildbot? This doesn't deal with the issue of SPARC support, but at least
it would make sure that we continued to test against Solaris.
On Wed, Mar 19, 2
On Sun, Mar 23, 2014 at 4:50 PM, William Stein wrote:
> On Sun, Mar 23, 2014 at 4:31 PM, R. Andrew Ohana
> wrote:
> >
> > On Sun, Mar 23, 2014 at 3:36 PM, William Stein wrote:
> >>
> >> Hi,
> >>
> >> In Sage 0.0 - 5.12, I could create a
On Sun, Mar 23, 2014 at 3:36 PM, William Stein wrote:
> Hi,
>
> In Sage 0.0 - 5.12, I could create a file foo.sage and type
>
> sage: load foo.sage # or %load foo.sage
>
> and evaluate its contents. In sage-6.2(beta) I get some interactive
> script loaded, that makes me evaluate the contents
On Sun, Mar 9, 2014 at 9:39 PM, William Stein wrote:
> On Sun, Mar 9, 2014 at 8:53 PM, R. Andrew Ohana
> wrote:
> > This doesn't at least look to be a regression, so much as a long term
> bug.
>
> Do you mean it isn't a regression *resulting from the git
> re
This doesn't at least look to be a regression, so much as a long term bug.
The offending path has always been a subpath of SAGE_ROOT since sage was
initially checked into a repository (it was SAGE_ROOT/data/extcode/octave
before). My guess is that if you are only experiencing issues with recent
ver
On Mon, Mar 3, 2014 at 3:04 AM, Volker Braun wrote:
> There was some attempt to replace it with Jenkins at SD56, but I don't
> know how how far that progressed. Since the changeset information is now
> easily accessible through git it would make sense to replace it with a more
> run-of-the-mill c
On Fri, Feb 14, 2014 at 4:25 PM, Travis Scrimshaw wrote:
> Hey Andrew,
>Thanks for fixing that. However I'm afraid I have another problem. On
> http://trac.sagemath.org/ticket/15822, it's already showing the branch as
> being merged when it clearly has not.
>
Both branches that you put there
On Tue, Feb 11, 2014 at 4:28 PM, Travis Scrimshaw wrote:
> Hey Andrew,
>I inputed the wrong branch on http://trac.sagemath.org/ticket/15668and
> then trac would not load the page. I worked around this by uploading a
> branch with the typo, but the issue with trac is still there.
>
Ok, this s
Hi Everyone,
I just pushed out an update to our trac plugin. The main change is that
merged branches now have links for the merge into develop (i.e. the merge
commit), as well as the list of commits that were merged. There were some
other minor changes + bug fixes, and a significant bit of code re
On Fri, Feb 7, 2014 at 3:25 PM, Francois Bissey <
francois.bis...@canterbury.ac.nz> wrote:
> Truth to be told I would feel better if someone was fixing all (or at
> least some of) the cython warnings we currently
> have before trying anything new.
>
Almost certainly not possible unless you rewrit
On Feb 7, 2014 3:27 AM, "Volker Braun" wrote:
>
> Its better to do smaller chunks. And I highly doubt that 2to3 will be
able to deal with the whole Sage library, Cython and all.
Cython should be less of an issue since it produces c code that can be
compiled against python 2 and 3. Obviously certa
On Sat, Feb 1, 2014 at 10:36 PM, William Stein wrote:
> Hi,
>
> I just wanted to raise awareness (and apologize) that the
> re-organization of the layout of Sage broke so many optional spkg's.
> In case people run into similar problems, here's what I'm doing to
> workaround this mess for sage-6.2
On Thu, Jan 23, 2014 at 5:22 PM, kcrisman wrote:
>
>>> By including another parameter "&id2=..." or perhaps "&h=..." or
>> "&b=..." it should be possible to specify the state relative to which you
>> want to see the diff. It should in principle be possible to paste in the
>> hash of the #15107 co
I'm a fan of gentoo's package manager specification (PMS) [1], however the
only package manager that is fully compliant is portage, which I don't
think is appropriate for sage. In particular:
1. It requires a noticeably bigger bootstrapping of the world. Lmonade
reduces this to only ~20 more packa
Well, I did fix it, but the trac server was still pulling up the old one
sometimes. I've noticed it does this sometimes unless you restart the
apache server, so I did that.
On Mon, Jan 6, 2014 at 6:12 AM, Travis Scrimshaw wrote:
> See http://trac.sagemath.org/ticket/15637.
>
>
> On Monday, Janu
Ok, I just deployed the rewritten sage plugin, and removed all usage of the
trac git plugin. There are bound to be a few bugs, but hopefully trac will
be much faster now.
On Fri, Jan 3, 2014 at 10:26 AM, Nathann Cohen wrote:
> Yooo !
>
> > Don't thank me yet, you must have just had good luck
27;m planning on
working on this today.
>
> Nathann
>
>
> On Wednesday, January 1, 2014 12:10:34 PM UTC+1, R. Andrew Ohana wrote:
>
>> I think the main culprit is the git trac plugin (as it seems to have
>> gotten much much worse in the last couple weeks as we have fina
Please try again. This should now be fixed.
On Wed, Jan 1, 2014 at 12:29 PM, Jean-Pierre Flori wrote:
> I'm getting an error:
> *Trac detected an internal error:*
>
> IOError: [Errno 13] Permission denied:
> u'/home/www-data/gitolite/keydir/03/jpflori.pub'
>
>
> Did I do something wrong?
>
> Be
I think the main culprit is the git trac plugin (as it seems to have gotten
much much worse in the last couple weeks as we have finally made the
changeover). One of my goals at Sage Days 56 is to completely remove our
usage of this plugin.
On Wed, Jan 1, 2014 at 2:43 AM, Nathann Cohen wrote:
> A
On Mon, Dec 30, 2013 at 3:28 PM, Robert Bradshaw <
rober...@math.washington.edu> wrote:
> For performance reasons, the patchbot always installs ccache. However,
> this shouldn't fail...
>
This line in the log looks suspicious:
tee: /tmp/tmp4Y_0j9-sage-git-temp-11630/logs/install.log: No such fil
On Mon, Dec 30, 2013 at 1:04 PM, William Stein wrote:
> On Mon, Dec 30, 2013 at 12:47 PM, Nils Bruin wrote:
> > On Monday, December 30, 2013 12:35:37 PM UTC-8, R. Andrew Ohana wrote:
> >>
> >> Moreover, I don't think we have to force the switch, it should be
&g
On Mon, Dec 30, 2013 at 10:14 AM, William Stein wrote:
> This discussion on Hacker News is relevant to "The Annual Sage on
> Python 3 Thread"
>
>https://news.ycombinator.com/item?id=6985207
>
>http://alexgaynor.net/2013/dec/30/about-python-3/
>
> 1. Argument against switching now:
>
> One
On Wed, Dec 25, 2013 at 12:36 PM, Volker Braun wrote:
I've been working on a "git trac" subcommand to complement the git suite
> with trac integration instead of the separate UI that the sage -dev scripts
> present. This project is the basis for my release management scripts, so I
> have been eati
I disagree with the sentiment that we should make python package X a
standard package because it is useful for Y. At that rate, every
(compatibly licensed) mathematics and science python package will be a
standard part of sage. Because pycrypto is not truly a dependency of the
sage library (i.e. us
Ok, the issue should hopefully be fixed now.
On Fri, Dec 20, 2013 at 7:41 AM, John Cremona wrote:
> I have a variation: I successfully pushed a new commit to #15554, then
> went onto trac to enter the commit hash manually, but get the error
> message
>
Although in your case, you haven't actuall
Yes, sorry. I'll try to look into this sometime this weekend.
On Fri, Dec 20, 2013 at 5:23 PM, Volker Braun wrote:
> Its a bug in our trac plugin. I'm pretty sure Andrew will fix it when he
> has some time ;-)
>
>
>
>
> On Saturday, December 21, 2013 12:25:07 AM UTC, John H Palmieri wrote:
>>
>
d elect to make it an optional package.
On Wed, Dec 11, 2013 at 3:48 PM, Dan Drake wrote:
> On Wed, 11 Dec 2013 at 02:53AM -0800, R. Andrew Ohana wrote:
> > But this time with a report!
> >
> > Broken spkgs:
> >
> > sagetex (maybe?)
>
> Why the "maybe&
The problem was the commit messages that had non-ascii characters were not
being properly decoded as utf8 (in this case there was a zero-width space
in one of the commit messages).
On Sun, Dec 15, 2013 at 3:01 PM, Jeroen Demeyer wrote:
> On 2013-12-15 23:49, Volker Braun wrote:
>
>> Did you just
But this time with a report!
Broken spkgs:
PIL
setuptools (really distribute)
sympy
pycrypto
pynac
rpy2
pexpect
gdmodule
sqlalchemy
networkx
mpmath
zn_poly
sagenb
sagetex (maybe?)
scons
(almost certainly polybori -- it depends on scons)
and a number of others that use python 2 spkg-install scrip
They don't supply a Fortran compiler, which we need. Also as of Xcode 5
they no longer supply gcc (the gcc in PATH is actually clang) and some
packages we include depend explicitly on having gcc as our c compiler.
If anything we need our own compiler now more than before, and this
situation doesn'
FYI, this is up for review now.
On Sun, Nov 17, 2013 at 11:51 PM, R. Andrew Ohana wrote:
> I've opened #15433 to trac porting to 10.9.
>
>
> On Sat, Nov 16, 2013 at 10:18 PM, R. Andrew Ohana
> wrote:
>
>> Ok, I've successfully built a fully working copy o
I've uploaded a binary to
http://boxen.math.washington.edu/home/ohanar/builds/sage-5.13.beta3-x86_64-Darwin.dmg--
no promises it will work for you.
On Sun, Nov 17, 2013 at 11:51 PM, R. Andrew Ohana wrote:
> I've opened #15433 to trac porting to 10.9.
>
>
> On Sat, Nov 1
I've opened #15433 to trac porting to 10.9.
On Sat, Nov 16, 2013 at 10:18 PM, R. Andrew Ohana wrote:
> Ok, I've successfully built a fully working copy of sage on 10.9 (i.e.
> passes all
> doctests with 3 exceptions, see below).
>
> polybori: I stopped experiencing th
On Sat, Nov 16, 2013 at 10:08 PM, Robert Bradshaw wrote:
> On Sat, Nov 16, 2013 at 9:10 AM, Volker Braun
> wrote:
> > Can somebody remind me of the status of the cython compiler cache?
>
> Discussion at http://trac.sagemath.org/ticket/13031 , but it may have
> been fixed since then.
>
I'm pretty
Ok, I've successfully built a fully working copy of sage on 10.9 (i.e.
passes all
doctests with 3 exceptions, see below).
polybori: I stopped experiencing the issue others are having (and still
have not
been able to figure out what resolved it for me)
scipy: This seems like more or less the same
Has anyone else been looking into this?
Where I've gotten:
scipy:
easy fix, just add "-D__ACCELERATE__" to CPPFLAGS
polybori:
this is a phantom bug that I can no longer reproduce (and I don't know
what changed in my environment)
r:
seems less like an issue with r, than with sqlite -- in p
There could also be an issue with the digital signature if the public key
did not get transferred to the new and configuration.
On Oct 19, 2013 11:18 AM, "Volker Braun" wrote:
> I get the following from spamassasin:
>
> X-Spam-hits: BAYES_00 -1.9, MISSING_HEADERS 1.021, RDNS_NONE 0.793,
> REPLYT
On Mon, Oct 7, 2013 at 1:44 PM, Volker Braun wrote:
> Do you know where in the library the large cremona database is used?
> Grepping for cremona.db doesn't find anything.
>
It is at sage.databases.cremona, although everything in the library should
be already be up to date (e.g. the small cremon
I'm trying to review #7539 which aims to include the small primesieve
library in Sage, but I'm not quite up to date on what the current policy is
on including new SPKGs. I thought at one point it was decided that all new
SPKGs needed to be optional for a period before becoming standard, however
the
This was reported upstream and is reported to be fixed. I'll see about
pulling in the latest source and updating trac.
On Sun, Jul 21, 2013 at 2:35 PM, Jeroen Demeyer wrote:
> On 07/21/2013 11:14 PM, Jeroen Demeyer wrote:
>
>> I must admit that I haven't read the whole thread about the new Trac,
Ok, trac has been updated. Please let me know if you continue to experience
this issue.
On Sun, Jul 21, 2013 at 2:43 PM, R. Andrew Ohana wrote:
> This was reported upstream and is reported to be fixed. I'll see about
> pulling in the latest source and updating trac.
>
>
>
Yup, this is again the issue of needing more space on the trac server. I
cleared out some more stuff while we continue to wait to get some more disk
space on the system.
On Sun, Jul 21, 2013 at 7:41 AM, Travis Scrimshaw wrote:
> Hey Andrew,
>Somethings wrong with the new trac server:
>
> Ope
1 - 100 of 205 matches
Mail list logo
