[sage-devel] git trac fails to checkout a remote branch

Trying to test Trac#26791 : charpent@zen-book-flip:/usr/local/sage-8$ git trac checkout 26791 Loading ticket #26791... Checking out Trac #26791 remote branch u/gh-timokau/rpy2-build-typo -> local branch t/26791/rpy2-build-typo... Traceback (most recent ca

Re: [sage-devel] git trac fails to checkout a remote branch

Use plain git. Suppose you're on branch called foo git fetch trac u/gh-timokau/rpy2-build-typo git checkout -b rpy2-build-typo FETCH_HEAD at this point you have created a local branch called rpy2-build-typo which is more or less what trac extension is supposed to do. Test is, and then do git che

Re: [sage-devel] git trac is down ?

On Tuesday, September 12, 2017 at 3:28:06 PM UTC+1, vdelecroix wrote: > > There is already > > git://github.com/sagemath/sage.git > this is not a full mirror of trac's git repo. > > On 12/09/2017 13:26, Dima Pasechnik wrote: > > A mirror on github is up (see another message here), enjoy...

Re: [sage-devel] git trac is down ?

Am 2017-09-12 um 16:28 schrieb Vincent Delecroix: > So it seems that the git server does not longer accept read only requests > without ssh authentication... I confirm that: on one and the same machine: $ LANG=C git fetch git://trac.sagemath.org/sage.git fatal: read error: Connection reset by pee

Re: [sage-devel] git trac is down ?

On 12/09/2017 16:26, Vincent Delecroix wrote: On 12/09/2017 12:58, Daniel Krenn wrote: On 2017-09-12 12:49, Daniel Krenn wrote: On 2017-09-12 12:04, Frédéric Chapoton wrote: I have access failures to the git repo from trac : chapoton@pc-chapoton:~/sage$ git pull trac u/mantepse/fricas_out

Re: [sage-devel] git trac is down ?

There is already git://github.com/sagemath/sage.git On 12/09/2017 13:26, Dima Pasechnik wrote: A mirror on github is up (see another message here), enjoy... https://github.com/dimpase/sagetrac-mirror On Tuesday, September 12, 2017 at 12:05:53 PM UTC+1, Dima Pasechnik wrote: basically same re

Re: [sage-devel] git trac is down ?

On 12/09/2017 12:58, Daniel Krenn wrote: On 2017-09-12 12:49, Daniel Krenn wrote: On 2017-09-12 12:04, Frédéric Chapoton wrote: I have access failures to the git repo from trac : chapoton@pc-chapoton:~/sage$ git pull trac u/mantepse/fricas_output_and_sage_conversion_bug fatal: read error: Co

Re: [sage-devel] git trac is down ?

A mirror on github is up (see another message here), enjoy... https://github.com/dimpase/sagetrac-mirror On Tuesday, September 12, 2017 at 12:05:53 PM UTC+1, Dima Pasechnik wrote: > > basically same remote setup for me, and it still works fine; > We can set up a github mirror, perhaps... > > On T

Re: [sage-devel] git trac is down ?

basically same remote setup for me, and it still works fine; We can set up a github mirror, perhaps... On Tuesday, September 12, 2017 at 11:58:57 AM UTC+1, Daniel Krenn wrote: > > On 2017-09-12 12:49, Daniel Krenn wrote: > > On 2017-09-12 12:04, Frédéric Chapoton wrote: > >> I have access failu

Re: [sage-devel] git trac is down ?

On 2017-09-12 12:49, Daniel Krenn wrote: > On 2017-09-12 12:04, Frédéric Chapoton wrote: >> I have access failures to the git repo from trac : >> >> chapoton@pc-chapoton:~/sage$ git pull trac >> u/mantepse/fricas_output_and_sage_conversion_bug >> fatal: read error: Connexion ré-initialisée par le c

Re: [sage-devel] git trac is down ?

On 2017-09-12 12:04, Frédéric Chapoton wrote: > I have access failures to the git repo from trac : > > chapoton@pc-chapoton:~/sage$ git pull trac > u/mantepse/fricas_output_and_sage_conversion_bug > fatal: read error: Connexion ré-initialisée par le correspondant > > Does anybody else suffers fro

[sage-devel] git trac is down ?

I have access failures to the git repo from trac : chapoton@pc-chapoton:~/sage$ git pull trac u/mantepse/fricas_output_and_sage_conversion_bug fatal: read error: Connexion ré-initialisée par le correspondant Does anybody else suffers from that ? Frederic -- You received this message because y

[sage-devel] git trac try

For those of you like me who didn't know about this, git trac try is a fast way to review tickets without having to build older versions. git trac try automatically merges the current develop branch with only the changes on a ticket into a temporary branch. If you've already built the current d

Re: [sage-devel] git-trac push

On Tuesday, October 18, 2016 at 10:37:24 AM UTC+2, Daniel Krenn wrote: > > It would be nice, if the actual git errors were shown by git-trac. Is > this (easily) possible? > Doing "git-trac --log=DEBUG" probably works. Of course the ideal solution would be for main to catch errors and present a

Re: [sage-devel] git-trac push

On 2016-10-18 08:56, 'Martin R' via sage-devel wrote: > martin@Martin-Laptop:~/sage-develop$ git-trac push 21594 > Pushing to Trac #21594... > Guessed remote branch: u/mantepse/growth_diagrams > Traceback (most recent call last): > ... > raise GitError(result) > git_trac.git_error.GitError It

[sage-devel] git-trac push

git-trac doesn't like me - what have I done wrong? martin@Martin-Laptop:~/sage-develop$ git-trac push 21594 Pushing to Trac #21594... Guessed remote branch: u/mantepse/growth_diagrams Traceback (most recent call last): File "/home/martin/git-trac-command/bin/git-trac", line 18, in cmdline.l

[sage-devel] git trac push error

Hi, I have the following git trac push error: Pushing to Trac #20100... Guessed remote branch: u/jlavauzelle/cyclic_code Traceback (most recent call last): File "/usr/local/bin/git-trac", line 18, in cmdline.launch() File "/usr/local/lib/python2.7/dist-packages/git_trac/cmdline.py", line

Re: [sage-devel] git trac error

> On Aug 14, 2016, at 14:06 , Volker Braun wrote: > > You need the newest git-trac version, presumably you checked out the repo > somewhere. Find it and run "git pull (in the git-trac repo folder) Thanks for that; the updated git-trac did better. Then I ran into this, which perhaps has to do

[sage-devel] git trac error

Hi, all, I admit to being a total novice in the New World of Sage development (post-git). Using OS X, 10.11.6, I attempted just now to “git” the code from a trac ticket (which has every indication of being more-or-less up-to-date, git-wise), and got this in response (on a freshly-built 7.3): %

[sage-devel] "git trac push" can no longer change branch on Trac

With the latest git-trac-command: $ git trac push Pushing to Trac #20868... Guessed remote branch: u/jdemeyer/homfly_doctest_errors The authenticity of host 'trac.sagemath.org (104.197.143.230)' can't be established. ECDSA key fingerprint is 5b:97:c8:74:a6:c4:e4:55:d1:13:8a:84:a3:85:25:6f. Are

[sage-devel] git trac timeout

I am getting timeouts from g...@trac.sagemath.org -- is it just me? John -- 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.

[sage-devel] git trac frustration...

I took a not-so clean Sage-6.5 install, installed git-trac (with no keys or login/password) and tried to check out the code from ticket 17826 (upgrade Ipython). I just get some mysterious errors.How am I supposed to debug this? salvus@devel1dc5:/usr/local/sage/current$ git trac checkout 17826

Re: [sage-devel] 'git trac' instructions for rebasing/merging

On Friday, March 13, 2015 at 6:10:09 PM UTC+1, Jonas Jermann wrote: > > At the moment the git history of sage looks quite messy > and I assume it will get worse, not better. It doesn't get messier over time, its more of a steady state. You either make the history more difficult to understand,

Re: [sage-devel] 'git trac' instructions for rebasing/merging

Hi On 12.03.2015 08:28, Nathann Cohen wrote: Hello everybody, I just noticed that we do not seem to have in our developer's manual instructions about how to rebase/merge a branch when it becomes incompatible with the latest beta. I do not use 'git trac' myself, but it would be cool if anybody

[sage-devel] 'git trac' instructions for rebasing/merging

Hello everybody, I just noticed that we do not seem to have in our developer's manual instructions about how to rebase/merge a branch when it becomes incompatible with the latest beta. I do not use 'git trac' myself, but it would be cool if anybody who does could add such an entry in the develope

[sage-devel] git trac push error

I get the following error and I have no idea what's going wrong: $ git trac push Pushing to Trac #17583... Guessed remote branch: u/jdemeyer/ticket/17583 Traceback (most recent call last): File "/home/jdemeyer/local/bin/git-trac", line 18, in cmdline.launch() File "/home/jdemeyer/local/s

[sage-devel] git trac asking for password

The password prompt is from git, it can't find the ssh key to authenticate and falls back to password. Make sure you have the right ssh key, see the developer manual for details. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe fro

[sage-devel] git trac asking for password

Hello everyone, I have setup the git-trac-enable using the source enable.sh and also have set the username and password using git trac config --user USERNAME --pass ''. It prompts me to give in a password ~/sage$ git trac push 17030 Pushing to Trac #17030... Guessed remote branch: u/a

[sage-devel] git trac log

I get (git-trac-command at 7e8fb34) $ git trac log 16538 Error: release manager has not merged Trac #16538 $ git trac log 16943 Error: release manager has not merged Trac #16943 $ git trac log 16786 Error: release manager has not merged Trac #16786 Actually, #16538 has been merged in 6.4.beta0, #

[sage-devel] git-trac guessing remote branch skips one letter

I was working on krenn@brown:/local/data/krenn/sage/current6$ git branch --contains * article-fsm-in-sage and then wanted to push it on trac by: krenn@brown:/local/data/krenn/sage/current6$ git-trac push 16705 Pushing to Trac #16705... Guessed remote branch: u/dkrenn/rticle-fsm-in-sage

[sage-devel] git trac

Hi Sage Devel, Sage comes with git, but Sage doesn't come with "git trac". Why not? Is it just that nobody got around to including it, or is this on purpose. http://www.sagemath.org/doc/developer/git_trac.html#installing-the-git-trac-command I'm just getting annoyed, due to copying the command

[sage-devel] git-trac trouble

Hi all, I'm trying to follow the developer's guide to set up git-trac. I keep running into the following error, for instance when checking out a ticket or setting up my username and password: Saved trac username. Saved trac password. Trac xmlrpc URL: http://trac.sagemath.org/xmlrpc (anonymo

Re: [sage-devel] "git trac" command

On Thursday, December 26, 2013 5:12:13 PM UTC-8, R. Andrew Ohana wrote: > > 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 >

Re: [sage-devel] "git trac" command

I vote for making this an extension to git, as it makes interacting with trac easier while also allowing developers to learn git if they did not already know it. If we think about the previous development process using mercurial, I am pretty sure that very few people used the sage-wrapped function

Re: [sage-devel] "git trac" command

I've been taking some bits and pieces from the sage -dev scripts, so its not entirely unrelated. Mostly, there is a philosophical difference: The dev scripts implement an alterative UI to git, and the git trac command extends git. The arguments for it aren't exactly new, and boil down to * A lo

Re: [sage-devel] "git trac" command

Yo ! > What's the relation between this and ./sage -dev? Because I don't think we should have this "git trac" command and also "./sage -dev" with lots of overlapping functionality. So I would vote for Jeroen, let me tell you that I *LOVE* the way you rewrite the questions. > [X] Inte

Re: [sage-devel] "git trac" command

On 2013-12-25 21:36, 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 eating my own dog food

Re: [sage-devel] "git trac" command

I agree that it shoud be installed separately, though of course we want to make it easy for people to try it out. But just running "sage -f git_trac" ought to be easy enough, so lets go with that. And the current branch is not set to build by default anyways. So as soon as somebody presses the

Re: [sage-devel] "git trac" command

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

[sage-devel] "git trac" command

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 eating my own dog food for a while now. I think it is now in a