Hi,
I have been under the impression that sage dev scripts are being dropped in
favour of git-trac subcommand for git available from
https://github.com/sagemath/git-trac-command.
HTH,
Kannappan.
On Wed, May 21, 2014 at 12:26 AM, Štěpán Starosta wrote:
> Hi,
>
> I follow the guide (
> http://w
Looks like a bug to me.
On Wednesday, May 21, 2014 2:56:54 AM UTC+8, Štěpán Starosta wrote:
>
> Hi,
>
> I follow the guide (
> http://www.sagemath.org/doc/developer/walk_through.html#starting-without-a-ticket)
>
> to create a new branch without a ticket. The command
>
> sage -dev checkout --bran
On Monday, May 19, 2014 11:52:13 AM UTC+2, Volker Braun wrote:
>
> Since my review request for the urgent bugfix for this:
>
> sage: RLF(0) < oo
> False
>
> has been hijacked by an open-ended discussion about and whether grants
> ought to be acknowledged in the source tree, I'd like to bre
On Friday, May 16, 2014 2:02:41 PM UTC-7, Nils Bruin wrote:
>
> sage: sage_getsource(hyperbolic_triangle) in
> open(sage_getfile(hyperbolic_triangle),'r').read()
> False
>
This is now http://trac.sagemath.org/ticket/16363 with a preliminary
solution.
In the process of writing that, I ran into
Hi!
On 2014-05-20, Jan Keitel wrote:
> git: 'am' is not a git command. See 'git --help'.
> Did you mean one of these?
> br
> ci
> co
> lg
> st
> stat
Recently I had a similar problem, namely Sage's git (i.e. git in a Sage
shell) claiming that "pull" is not a git command. The solutio
Hi there,
I'm posting here instead of opening a ticket right away because I'm not
sure whether the error I'm getting is my fault or not. The scenario is the
following: I import a patch that does not apply cleanly and take care of
the .rej files by hand. After I'm done with that, I tell the dev
Hi,
I follow the guide
(http://www.sagemath.org/doc/developer/walk_through.html#starting-without-a-ticket)
to create a new branch without a ticket. The command
sage -dev checkout --branch my_branch
outputs
*Branch "my_branch" does not exist locally.*
Any ideas what I might be doing wrong? I
On Tue, May 20, 2014 at 4:51 PM, Robert Bradshaw <
rober...@math.washington.edu> wrote:
> > On Mon, May 5, 2014 at 7:10 AM, Ralf Stephan wrote:
>
>> 2. why does patchbot make and test twice per ticket, even with skip-base?
>
> It shouldn't, why are you seeing this?
>
This must have been a mista
On Mon, May 5, 2014 at 7:47 AM, William Stein wrote:
> On Mon, May 5, 2014 at 7:10 AM, Ralf Stephan wrote:
>> Hello,
>> please bear with me and give me a hint why ...
>>
>> 1. isn't make just doing sage -b whenever nothing in
>>lib/ is changed (or any suitable definition of lib)?
>>A coun
Francois Bissey wrote:
Looks to me like your bash has a problem with readline possibly trying to load
Sage's readline
rather than your system one.
Yes, Sage's is still readline 6.2, and that gets installed regardless of
the version the system uses, which here apparently is readline 6.3.
Thi
Hi,
Looks to me like your bash has a problem with readline possibly trying to load
Sage's readline
rather than your system one.
Does "./sage -sh" works?
François
On 20/05/2014, at 17:30, pang wrote:
> Hello:
> sage 6.2 fails to install on arch linux. This is a rolling release, so I
> can't s
Hello:
sage 6.2 fails to install on arch linux. This is a rolling release, so I
can't state the version, but I just updated arch and it fails again. This
distro uses python3 by default.
Found local metadata for sqlite-3.8.4.3
Found local sources at
/home/pang/Escritorio/sa
> I don't care wrt patchbot. ApplyFailed with patchbot is cheap.
> Ah, we could ignore testing tickets that have failed to apply once.
>
> However, as you know, reviewing is a scarce resource, and scaring reviewers
> with a conflicting
> patch is not nice. Also, having a reliable label that shows t
I don't care wrt patchbot. ApplyFailed with patchbot is cheap.
Ah, we could ignore testing tickets that have failed to apply once.
However, as you know, reviewing is a scarce resource, and scaring reviewers
with a conflicting
patch is not nice. Also, having a reliable label that shows the author
c
Hi,
with all the fine changes to docs in 6.2, the web docs are still at 6.1.1.
Can you please update the pages?
Regards,
--
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 em
>
> And set the ticket to needs-work, *beg*...
You also have to consider that setting tickets to needs_work when there is
nobody to review them creates a LOT of (potentially useless) work.
No offense intended, but you set something like 4-5 of my branches to
needs_work yesterday, I fixed the
16 matches
Mail list logo
