Hi,
this is probably not an actual issue, but it seems that "make build"
trips over some .BACKUP files from a merge (with meld):
https://dl.dropboxusercontent.com/u/83265276/merge-woes.txt
Unfortunately I don't fully remember what I have done that caused
these files. I don't think I ever merged
On 16 December 2013 17:12, Volker Braun wrote:
> I still don't have permissions to copy new upstream tarballs, so you have to
> manually download the tarball and put it into /upstream
OK, that certainly worked.
> . I asked for a more
> sane system on sage.math.users a while ago but nobody with a
I still don't have permissions to copy new upstream tarballs, so you have
to manually download the tarball and put it into /upstream. I asked for a
more sane system on sage.math.users a while ago but nobody with
administrative access did anything.
https://www.kernel.org/pub/software/scm/git/git
On 16 December 2013 17:03, John Cremona wrote:
> WIth a git clone of Sage which ran ok before, after "git pull origin
> master" which takes me to commit
> 68d0a5d1f1852db83b575d3ac93210cb291ad84f, I type "make" and see this:
>
> Attempting to download package git-1.8.4.4
Trying to download
>
WIth a git clone of Sage which ran ok before, after "git pull origin
master" which takes me to commit
68d0a5d1f1852db83b575d3ac93210cb291ad84f, I type "make" and see this:
Attempting to download package git-1.8.4.4
>>> Trying to download
>>> http://www.sagemath.org/packages/upstream//git/git-1.8.
Hell everybody !
This is almost done ! Almost done, because we can't do anything like
that without deprecating stuff for a while (especially when I have no idea
how many people use that), so I created ticket #15521.
This adds deprecation warnings to have everybody explicitly say that
Hi folks,
Here is an interesting interview of Scott Aaronson on philosophy, science,
math and research. The interview ends with the following excerpt which
caught my eye.
Regards,
Ifti
http://intelligence.org/2013/12/13/aaronson/
Q: Which object-level thinking tactics, at roughly this level o
Thanks for the prompt answer.
Eric.
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to
On 12/16/2013 10:50 PM, Eric Gourgoulhon wrote:
You are not totally wrong, although I do not feel very qualified with
the charpoly stuff. So I tried to review the patch: it works well under
Sage 5.10 but fails to install under 5.11 and 5.12, with the following
error message:
sage:
hg_sage.apply(
You are not totally wrong, although I do not feel very qualified with the
charpoly stuff. So I tried to review the patch: it works well under Sage
5.10 but fails to install under 5.11 and 5.12, with the following error
message:
sage:
hg_sage.apply("/home/eric/sage-5.12/trac_local/trac_14403_sy
I would recommend people change their mercurial patches to git branches,
even only if to get their feet wet with git and the "sage -dev" scripts.
But I will merge mercurial tickets, too.
For now it is still possible to use mercurial & sage-5.13 to develop, but
as time passes this will become le
There are various tickets having positive_review which have Mercurial
patches. Will these need to be changed to a git branch before they can
be merged or will the release manager take care of this?
What about Mercurial patches which are currently
needs_work/needs_review? Can these be finished
12 matches
Mail list logo
