Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

[Ivan Andrus]

It looks like ipython is printing invalid (or at least unknown to Emacs) 

I got it to ignore them by setting

(setq ansi-color-drop-regexp
  " 
\\[\\([ABCDsuK]\\|[12][JK]\\|=[0-9]+[hI]\\|[0-9;]*[HfDnC]\\|\\?[0-9]+[hl]\\|J\\)")

There is also a bug in my version of Emacs which causes these eliminated escape 
sequences to mess with the use of the start variable in 
'ansi-color-filter-apply'.  To make a long story short I changed the 
implementation to 

(defun ansi-color-filter-apply (string)
  "Filter out all ANSI control sequences from STRING.

Every call to this function will set and use the buffer-local variable
`ansi-color-context' to save partial escape sequences.  This information
will be used for the next call to `ansi-color-apply'.  Set
`ansi-color-context' to nil if you don't want this.

This function can be added to `comint-preoutput-filter-functions'."
  (let ((start 0) end result)
;; if context was saved and is a string, prepend it
(if (cadr ansi-color-context)
(setq string (concat (cadr ansi-color-context) string)
  ansi-color-context nil))
;; eliminate unrecognized escape sequences
(while (string-match ansi-color-drop-regexp string)
  (setq string
(replace-match "" nil nil string)))
;; find the next escape sequence
(while (setq end (string-match ansi-color-regexp string start))
  (setq result (concat result (substring string start end))
start (match-end 0)))
;; save context, add the remainder of the string to the result
(let (fragment)
  (if (string-match "\033" string start)
  (let ((pos (match-beginning 0)))
(setq fragment (substring string pos)
  result (concat result (substring string start pos
(setq result (concat result (substring string start
  (setq ansi-color-context (if fragment (list nil fragment
result))

and it fixed it for me (I swapped the order of the "eliminate unrecognized 
escape sequences" and "find the next escape sequence".  I have filed a bug on 
it.  

Let me know if that solves the issue.  If so, then maybe we can add a 
workaround to sage-mode or figure out how to get ipython to stop sending the 
control sequences.  If not it would be helpful to know what version of Emacs 
you’re running.

-Ivan

> On Aug 11, 2016, at 3:49 PM, 'Martin R' via sage-devel 
>  wrote:
> 
> This is now https://trac.sagemath.org/ticket/21227
>  
> 
> -- 
> 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 sage-devel@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-devel 
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: broken %attach and %debug ?

[Travis Scrimshaw]

I would really like to have %attach back working.

Best,
Travis


On Friday, August 12, 2016 at 12:50:23 PM UTC-5, Volker Braun wrote:
>
> Presumably attach (or, more generally, using the python inputhook) doesn't 
> work since Ipython 5 now implements its own input handling.
>
>
>
>
> On Friday, August 12, 2016 at 2:22:51 PM UTC+2, Frédéric Chapoton wrote:
>>
>> is this only me, or the recent update to ipython 5.0 has broken severel 
>> things in 7.4.b0 ?
>>
>> it seems that somebody already complained about sage_mode and %lprun (see 
>> https://trac.sagemath.org/ticket/21006)
>>
>> for me, %attach does not seem to reload the files that changed
>>
>> and using %debug doe snot quite work, because the special command r and n 
>> are still mapped to numerical and R interpreter inside the ipbd session
>>
>> Frederic
>>
>

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: checkout from trac

[leif]

leif wrote:
> Bill Page wrote:
>> BTW, is it normal to run 'make' after 'git trac checkout'?
> 
> Sure you should, to make the changes take effect in your Sage
> installation.  (But that's not always necessary, really depends on what
> you pull.  In any case, running 'make' is safe, as when nothing has to
> get rebuilt / updated, 'make' won't do much.)
> 
> But you could have skipped docbuilding in the first place, by running
> 'make build' instead of 'make' (= 'make all').
> 
> 
>> I just did
>> that and 'make' seems to be re-building almost everything.
> 
> Presumably because the branch there is based on some later version of
> Sage than your current is.  (7.4.beta0 vs. 7.3 I guess.)
> 
> 
>> On 13 August 2016 at 17:07, Bill Page  wrote:
>>> Yes indeed it does! Much appreciated.
>>>
>>> On 13 August 2016 at 17:05, Volker Braun  wrote:
 I removed the leading slash from the branch name on that ticket, works now.

 On Saturday, August 13, 2016 at 10:22:55 PM UTC+2, Bill Page wrote:
>
> OK, I thought that might be it (although all I really wanted was
> read-only access), so I ran 'git trac config', see below. But it still
> fails.
>
> I guess it's just not my day ...
> 
> Looks like... ;-)

To avoid further trouble:

You may need (or want) the new FriCAS package from #21209, or at least
the UFFI patch from there, as the current optional FriCAS package in
Sage (1.2.4) won't build with our current version of ECL either.  (But
you may have read that on sage-devel already.)

If you want to install the /new/ version 1.2.7 from #21209, you have to
download it manually (into upstream/) from the link in that ticket's
description, as it's not yet on our server.


-leif


-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: checkout from trac

[leif]

Bill Page wrote:
> BTW, is it normal to run 'make' after 'git trac checkout'?

Sure you should, to make the changes take effect in your Sage
installation.  (But that's not always necessary, really depends on what
you pull.  In any case, running 'make' is safe, as when nothing has to
get rebuilt / updated, 'make' won't do much.)

But you could have skipped docbuilding in the first place, by running
'make build' instead of 'make' (= 'make all').


> I just did
> that and 'make' seems to be re-building almost everything.

Presumably because the branch there is based on some later version of
Sage than your current is.  (7.4.beta0 vs. 7.3 I guess.)


> On 13 August 2016 at 17:07, Bill Page  wrote:
>> Yes indeed it does! Much appreciated.
>>
>> On 13 August 2016 at 17:05, Volker Braun  wrote:
>>> I removed the leading slash from the branch name on that ticket, works now.
>>>
>>> On Saturday, August 13, 2016 at 10:22:55 PM UTC+2, Bill Page wrote:

 OK, I thought that might be it (although all I really wanted was
 read-only access), so I ran 'git trac config', see below. But it still
 fails.

 I guess it's just not my day ...

Looks like... ;-)

Interestingly, trac (and gitolite) did not complain about the (wrong)
leading slash in the Branch field on the ticket; I didn't notice either,
and even unconsciously omitted it when pulling the branch myself... 8-)


-leif


-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: checkout from trac

[Bill Page]

BTW, is it normal to run 'make' after 'git trac checkout'? I just did
that and 'make' seems to be re-building almost everything.

On 13 August 2016 at 17:07, Bill Page  wrote:
> Yes indeed it does! Much appreciated.
>
> On 13 August 2016 at 17:05, Volker Braun  wrote:
>> I removed the leading slash from the branch name on that ticket, works now.
>>
>> On Saturday, August 13, 2016 at 10:22:55 PM UTC+2, Bill Page wrote:
>>>
>>> OK, I thought that might be it (although all I really wanted was
>>> read-only access), so I ran 'git trac config', see below. But it still
>>> fails.
>>>
>>> I guess it's just not my day ...
>>>
>>> On 13 August 2016 at 16:13, Volker Braun  wrote:
>>> > You missed "git trac config"
>>> >

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: checkout from trac

[Bill Page]

Yes indeed it does! Much appreciated.

On 13 August 2016 at 17:05, Volker Braun  wrote:
> I removed the leading slash from the branch name on that ticket, works now.
>
> On Saturday, August 13, 2016 at 10:22:55 PM UTC+2, Bill Page wrote:
>>
>> OK, I thought that might be it (although all I really wanted was
>> read-only access), so I ran 'git trac config', see below. But it still
>> fails.
>>
>> I guess it's just not my day ...
>>
>> On 13 August 2016 at 16:13, Volker Braun  wrote:
>> > You missed "git trac config"
>> >

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: checkout from trac

[Volker Braun]

I removed the leading slash from the branch name on that ticket, works now.

On Saturday, August 13, 2016 at 10:22:55 PM UTC+2, Bill Page wrote:
>
> OK, I thought that might be it (although all I really wanted was 
> read-only access), so I ran 'git trac config', see below. But it still 
> fails. 
>
> I guess it's just not my day ... 
>
> On 13 August 2016 at 16:13, Volker Braun  
> wrote: 
> > You missed "git trac config" 
> > 
>
>
> wspage@sarah ~/sage $ git trac config --user bpage --pass 'xxx' 
> Saved trac username. 
> Saved trac password. 
> Trac xmlrpc URL: 
> https://trac.sagemath.org/xmlrpc (anonymous) 
> https://trac.sagemath.org/login/xmlrpc (authenticated) 
> realm sage.math.washington.edu 
> Username: bpage 
> Password: xxx 
> Retrieving SSH keys... 
> 4096 SHA256:tZKL8qzKXq37V4c0MR7KwpA8OZRjNsXyWama8cN6KOs 
> bill...@newsynthesis.org  (RSA) 
> 2048 SHA256:LKhC6fbZQyINK+kBMbeGjNAJ+FR+4qHmo264OcdBkR0 
> b04b5777e2694c8fa4b8b21dbe1c93c6@compute4-us (RSA) 
> wspage@sarah ~/sage $ git remote -v 
> origingit://github.com/sagemath/sage.git (fetch) 
> origingit://github.com/sagemath/sage.git (push) 
> tracgit://trac.sagemath.org/sage.git (fetch) 
> tracg...@trac.sagemath.org:sage.git (push) 
> wspage@sarah ~/sage $ git trac checkout 21231 
> Loading ticket #21231... 
>
> Checking out Trac #21231 remote branch /u/mantepse/21231 -> local 
> branch t/21231//u/mantepse/21231... 
> Traceback (most recent call last): 
>   File "/home/wspage/git-trac-command/bin/git-trac", line 18, in  
> cmdline.launch() 
>   File "/home/wspage/git-trac-command/git_trac/cmdline.py", line 215, in 
> launch 
> app.checkout(args.ticket_or_branch, args.branch_name) 
>   File "/home/wspage/git-trac-command/git_trac/app.py", line 116, in 
> checkout 
> self._checkout_ticket(int(ticket_or_branch), branch_name) 
>   File "/home/wspage/git-trac-command/git_trac/app.py", line 144, in 
> _checkout_ticket 
> self.repo.checkout_new_branch(ticket.branch, branch) 
>   File "/home/wspage/git-trac-command/git_trac/git_repository.py", 
> line 136, in checkout_new_branch 
> self.git.fetch('trac', remote) 
>   File "/home/wspage/git-trac-command/git_trac/git_interface.py", line 
> 341, in meth 
> return self.execute(git_cmd, *args, **kwds) 
>   File "/home/wspage/git-trac-command/git_trac/git_interface.py", line 
> 328, in execute 
> popen_stderr=subprocess.PIPE) 
>   File "/home/wspage/git-trac-command/git_trac/git_interface.py", line 
> 263, in _run 
> raise GitError(result) 
> git_trac.git_error.GitError: git returned with non-zero exit code 
> (128) when executing "git fetch trac /u/mantepse/21231" 
> STDERR: fatal: Invalid refspec '/u/mantepse/21231' 
>

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: checkout from trac

[Bill Page]

OK, I thought that might be it (although all I really wanted was
read-only access), so I ran 'git trac config', see below. But it still
fails.

I guess it's just not my day ...

On 13 August 2016 at 16:13, Volker Braun  wrote:
> You missed "git trac config"
>


wspage@sarah ~/sage $ git trac config --user bpage --pass 'xxx'
Saved trac username.
Saved trac password.
Trac xmlrpc URL:
https://trac.sagemath.org/xmlrpc (anonymous)
https://trac.sagemath.org/login/xmlrpc (authenticated)
realm sage.math.washington.edu
Username: bpage
Password: xxx
Retrieving SSH keys...
4096 SHA256:tZKL8qzKXq37V4c0MR7KwpA8OZRjNsXyWama8cN6KOs
bill.p...@newsynthesis.org (RSA)
2048 SHA256:LKhC6fbZQyINK+kBMbeGjNAJ+FR+4qHmo264OcdBkR0
b04b5777e2694c8fa4b8b21dbe1c93c6@compute4-us (RSA)
wspage@sarah ~/sage $ git remote -v
origingit://github.com/sagemath/sage.git (fetch)
origingit://github.com/sagemath/sage.git (push)
tracgit://trac.sagemath.org/sage.git (fetch)
tracg...@trac.sagemath.org:sage.git (push)
wspage@sarah ~/sage $ git trac checkout 21231
Loading ticket #21231...

Checking out Trac #21231 remote branch /u/mantepse/21231 -> local
branch t/21231//u/mantepse/21231...
Traceback (most recent call last):
  File "/home/wspage/git-trac-command/bin/git-trac", line 18, in 
cmdline.launch()
  File "/home/wspage/git-trac-command/git_trac/cmdline.py", line 215, in launch
app.checkout(args.ticket_or_branch, args.branch_name)
  File "/home/wspage/git-trac-command/git_trac/app.py", line 116, in checkout
self._checkout_ticket(int(ticket_or_branch), branch_name)
  File "/home/wspage/git-trac-command/git_trac/app.py", line 144, in
_checkout_ticket
self.repo.checkout_new_branch(ticket.branch, branch)
  File "/home/wspage/git-trac-command/git_trac/git_repository.py",
line 136, in checkout_new_branch
self.git.fetch('trac', remote)
  File "/home/wspage/git-trac-command/git_trac/git_interface.py", line
341, in meth
return self.execute(git_cmd, *args, **kwds)
  File "/home/wspage/git-trac-command/git_trac/git_interface.py", line
328, in execute
popen_stderr=subprocess.PIPE)
  File "/home/wspage/git-trac-command/git_trac/git_interface.py", line
263, in _run
raise GitError(result)
git_trac.git_error.GitError: git returned with non-zero exit code
(128) when executing "git fetch trac /u/mantepse/21231"
STDERR: fatal: Invalid refspec '/u/mantepse/21231'

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: checkout from trac

[Volker Braun]

You missed "git trac config"

On Saturday, August 13, 2016 at 8:50:35 PM UTC+2, Bill Page wrote:
>
> :( :{ :[ 
>
> wspage@sarah ~ $ git clone 
> https://github.com/sagemath/git-trac-command.git 
> Cloning into 'git-trac-command'... 
> remote: Counting objects: 776, done. 
> remote: Total 776 (delta 0), reused 0 (delta 0), pack-reused 776 
> Receiving objects: 100% (776/776), 380.53 KiB | 174.00 KiB/s, done. 
> Resolving deltas: 100% (556/556), done. 
> Checking connectivity... done. 
> wspage@sarah ~ $ source git-trac-command/enable.sh 
> Prepending the git-trac command to your search PATH 
> wspage@sarah ~ $ cd sage 
> wspage@sarah ~/sage $ git trac checkout 21231 
> Loading ticket #21231... 
> Checking out Trac #21231 remote branch /u/mantepse/21231 -> local 
> branch t/21231//u/mantepse/21231... 
> Traceback (most recent call last): 
>   File "/home/wspage/git-trac-command/bin/git-trac", line 18, in  
> cmdline.launch() 
>   File "/home/wspage/git-trac-command/git_trac/cmdline.py", line 215, in 
> launch 
> app.checkout(args.ticket_or_branch, args.branch_name) 
>   File "/home/wspage/git-trac-command/git_trac/app.py", line 116, in 
> checkout 
> self._checkout_ticket(int(ticket_or_branch), branch_name) 
>   File "/home/wspage/git-trac-command/git_trac/app.py", line 144, in 
> _checkout_ticket 
> self.repo.checkout_new_branch(ticket.branch, branch) 
>   File "/home/wspage/git-trac-command/git_trac/git_repository.py", 
> line 136, in checkout_new_branch 
> self.git.fetch('trac', remote) 
>   File "/home/wspage/git-trac-command/git_trac/git_interface.py", line 
> 341, in meth 
> return self.execute(git_cmd, *args, **kwds) 
>   File "/home/wspage/git-trac-command/git_trac/git_interface.py", line 
> 328, in execute 
> popen_stderr=subprocess.PIPE) 
>   File "/home/wspage/git-trac-command/git_trac/git_interface.py", line 
> 263, in _run 
> raise GitError(result) 
> git_trac.git_error.GitError: git returned with non-zero exit code 
> (128) when executing "git fetch trac /u/mantepse/21231" 
> STDERR: fatal: Invalid refspec '/u/mantepse/21231' 
>
> ??? 
>
> On 13 August 2016 at 13:37, leif  
> wrote: 
> > Volker Braun wrote: 
> >> http://combinat.sagemath.org/doc/developer/git_trac.html 
> > 
> > [Hello Google,] 
> > 
> > Canonical URLs: ;-) 
> > 
> >  * 
> > 
> http://doc.sagemath.org/html/en/developer/git_trac.html#installing-the-git-trac-command
>  
> > 
> >  * 
> > 
> http://doc.sagemath.org/html/en/developer/git_trac.html#check-out-an-existing-ticket
>  
> > 
> > 
> > -leif 
> > 
> >> In particular check out the sections on "Installing the Git-Trac 
> >> Command" and then "Check out an Existing Ticket" 
> >> 
> >> 
> >> 
> >> On Saturday, August 13, 2016 at 6:55:10 PM UTC+2, Bill Page wrote: 
> >> 
> >> Sorry, I'm still confused. What exactly do I have to do to checkout 
> >> a trac ticket for testing and where is it documented? Google 
> >> searches only seem to mention --dev. 
> >> 
> >> 
> >> On Aug 13, 2016 12:19 PM, "leif"  > 
> >> wrote: 
> >> 
> >> Bill Page wrote: 
> >> > It seems like I am always confused when I try to use 
> sagetrac, 
> >> but I 
> >> > did not expect this: 
> >> > 
> >> > wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231 
> >> > sage-run received unknown option: --dev 
> >> > usage: sage [options] 
> >> > Try 'sage -h' for more information. 
> >> 
> >> The "devscripts" had been deprecated and have now been removed 
> (in 
> >> favour of Volker's "git-trac" command), since 7.0 IIRC. 
> >> 
> >> You can install it independently (outside a Sage installation), 
> >> but it's 
> >> meanwhile also an optional Sage package (named 'git_trac'). 
> >> 
> >> I'd have to dig where it's documented, but 
> >> 
> >> git help trac 
> >> 
> >> should give you an overview (after installation of course). 
> >> 
> >> The source code is on GitHub (vbraun or sagemath, not sure). 
> >> 
> >> 
> >> You can otherwise of course use plain git (cf. "Git the hard 
> way" in 
> >> Sage's Developer Guide). 
> >> 
> >> 
> >> -leif 
> > 
> > 
> > -- 
> > 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+...@googlegroups.com . 
> > To post to this group, send email to sage-...@googlegroups.com 
> . 
> > Visit this group at https://groups.google.com/group/sage-devel. 
> > For more options, visit https://groups.google.com/d/optout. 
>

-- 
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 

Re: [sage-devel] Re: checkout from trac

[Bill Page]

:( :{ :[

wspage@sarah ~ $ git clone https://github.com/sagemath/git-trac-command.git
Cloning into 'git-trac-command'...
remote: Counting objects: 776, done.
remote: Total 776 (delta 0), reused 0 (delta 0), pack-reused 776
Receiving objects: 100% (776/776), 380.53 KiB | 174.00 KiB/s, done.
Resolving deltas: 100% (556/556), done.
Checking connectivity... done.
wspage@sarah ~ $ source git-trac-command/enable.sh
Prepending the git-trac command to your search PATH
wspage@sarah ~ $ cd sage
wspage@sarah ~/sage $ git trac checkout 21231
Loading ticket #21231...
Checking out Trac #21231 remote branch /u/mantepse/21231 -> local
branch t/21231//u/mantepse/21231...
Traceback (most recent call last):
  File "/home/wspage/git-trac-command/bin/git-trac", line 18, in 
cmdline.launch()
  File "/home/wspage/git-trac-command/git_trac/cmdline.py", line 215, in launch
app.checkout(args.ticket_or_branch, args.branch_name)
  File "/home/wspage/git-trac-command/git_trac/app.py", line 116, in checkout
self._checkout_ticket(int(ticket_or_branch), branch_name)
  File "/home/wspage/git-trac-command/git_trac/app.py", line 144, in
_checkout_ticket
self.repo.checkout_new_branch(ticket.branch, branch)
  File "/home/wspage/git-trac-command/git_trac/git_repository.py",
line 136, in checkout_new_branch
self.git.fetch('trac', remote)
  File "/home/wspage/git-trac-command/git_trac/git_interface.py", line
341, in meth
return self.execute(git_cmd, *args, **kwds)
  File "/home/wspage/git-trac-command/git_trac/git_interface.py", line
328, in execute
popen_stderr=subprocess.PIPE)
  File "/home/wspage/git-trac-command/git_trac/git_interface.py", line
263, in _run
raise GitError(result)
git_trac.git_error.GitError: git returned with non-zero exit code
(128) when executing "git fetch trac /u/mantepse/21231"
STDERR: fatal: Invalid refspec '/u/mantepse/21231'

???

On 13 August 2016 at 13:37, leif  wrote:
> Volker Braun wrote:
>> http://combinat.sagemath.org/doc/developer/git_trac.html
>
> [Hello Google,]
>
> Canonical URLs: ;-)
>
>  *
> http://doc.sagemath.org/html/en/developer/git_trac.html#installing-the-git-trac-command
>
>  *
> http://doc.sagemath.org/html/en/developer/git_trac.html#check-out-an-existing-ticket
>
>
> -leif
>
>> In particular check out the sections on "Installing the Git-Trac
>> Command" and then "Check out an Existing Ticket"
>>
>>
>>
>> On Saturday, August 13, 2016 at 6:55:10 PM UTC+2, Bill Page wrote:
>>
>> Sorry, I'm still confused. What exactly do I have to do to checkout
>> a trac ticket for testing and where is it documented? Google
>> searches only seem to mention --dev.
>>
>>
>> On Aug 13, 2016 12:19 PM, "leif" 
>> wrote:
>>
>> Bill Page wrote:
>> > It seems like I am always confused when I try to use sagetrac,
>> but I
>> > did not expect this:
>> >
>> > wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
>> > sage-run received unknown option: --dev
>> > usage: sage [options]
>> > Try 'sage -h' for more information.
>>
>> The "devscripts" had been deprecated and have now been removed (in
>> favour of Volker's "git-trac" command), since 7.0 IIRC.
>>
>> You can install it independently (outside a Sage installation),
>> but it's
>> meanwhile also an optional Sage package (named 'git_trac').
>>
>> I'd have to dig where it's documented, but
>>
>> git help trac
>>
>> should give you an overview (after installation of course).
>>
>> The source code is on GitHub (vbraun or sagemath, not sure).
>>
>>
>> You can otherwise of course use plain git (cf. "Git the hard way" in
>> Sage's Developer Guide).
>>
>>
>> -leif
>
>
> --
> 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 sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: checkout from trac

[leif]

Volker Braun wrote:
> http://combinat.sagemath.org/doc/developer/git_trac.html

[Hello Google,]

Canonical URLs: ;-)

 *
http://doc.sagemath.org/html/en/developer/git_trac.html#installing-the-git-trac-command

 *
http://doc.sagemath.org/html/en/developer/git_trac.html#check-out-an-existing-ticket


-leif

> In particular check out the sections on "Installing the Git-Trac
> Command" and then "Check out an Existing Ticket"
> 
> 
> 
> On Saturday, August 13, 2016 at 6:55:10 PM UTC+2, Bill Page wrote:
> 
> Sorry, I'm still confused. What exactly do I have to do to checkout
> a trac ticket for testing and where is it documented? Google
> searches only seem to mention --dev.
> 
> 
> On Aug 13, 2016 12:19 PM, "leif" 
> wrote:
> 
> Bill Page wrote:
> > It seems like I am always confused when I try to use sagetrac,
> but I
> > did not expect this:
> >
> > wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
> > sage-run received unknown option: --dev
> > usage: sage [options]
> > Try 'sage -h' for more information.
> 
> The "devscripts" had been deprecated and have now been removed (in
> favour of Volker's "git-trac" command), since 7.0 IIRC.
> 
> You can install it independently (outside a Sage installation),
> but it's
> meanwhile also an optional Sage package (named 'git_trac').
> 
> I'd have to dig where it's documented, but
> 
> git help trac
> 
> should give you an overview (after installation of course).
> 
> The source code is on GitHub (vbraun or sagemath, not sure).
> 
> 
> You can otherwise of course use plain git (cf. "Git the hard way" in
> Sage's Developer Guide).
> 
> 
> -leif


-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: checkout from trac

[leif]

leif wrote:
> Bill Page wrote:
>> It seems like I am always confused when I try to use sagetrac, but I
>> did not expect this:
>>
>> wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
>> sage-run received unknown option: --dev
>> usage: sage [options]
>> Try 'sage -h' for more information.
> 
> The "devscripts" had been deprecated and have now been removed (in
> favour of Volker's "git-trac" command), since 7.0 IIRC.

Ooops, deprecated in 7.2, removed in 7.3.


-leif


-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: checkout from trac

[Volker Braun]

http://combinat.sagemath.org/doc/developer/git_trac.html

In particular check out the sections on "Installing the Git-Trac Command" 
and then "Check out an Existing Ticket"



On Saturday, August 13, 2016 at 6:55:10 PM UTC+2, Bill Page wrote:
>
> Sorry, I'm still confused. What exactly do I have to do to checkout a trac 
> ticket for testing and where is it documented? Google searches only seem to 
> mention --dev.
>
> On Aug 13, 2016 12:19 PM, "leif"  wrote:
>
> Bill Page wrote:
> > It seems like I am always confused when I try to use sagetrac, but I
> > did not expect this:
> >
> > wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
> > sage-run received unknown option: --dev
> > usage: sage [options]
> > Try 'sage -h' for more information.
>
> The "devscripts" had been deprecated and have now been removed (in
> favour of Volker's "git-trac" command), since 7.0 IIRC.
>
> You can install it independently (outside a Sage installation), but it's
> meanwhile also an optional Sage package (named 'git_trac').
>
> I'd have to dig where it's documented, but
>
> git help trac
>
> should give you an overview (after installation of course).
>
> The source code is on GitHub (vbraun or sagemath, not sure).
>
>
> You can otherwise of course use plain git (cf. "Git the hard way" in
> Sage's Developer Guide).
>
>
> -leif
>
>
> > What am I doing wrong?
> >
> > I just did
> >
> > wspage@sarah ~ $ git clone git://github.com/sagemath/sage.git
> > wspage@sarah ~ $ cd sage
> > wspage@sarah ~/sage $ make
> >
> > Build completed without errors.
> >
> > wspage@sarah ~/sage $ ./sage
> >
> > seems to work as expected.
>
>
> --
> 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+...@googlegroups.com .
> To post to this group, send email to sage-...@googlegroups.com 
> .
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

Re: [sage-devel] Re: checkout from trac

[Bill Page]

Sorry, I'm still confused. What exactly do I have to do to checkout a trac
ticket for testing and where is it documented? Google searches only seem to
mention --dev.

On Aug 13, 2016 12:19 PM, "leif"  wrote:

Bill Page wrote:
> It seems like I am always confused when I try to use sagetrac, but I
> did not expect this:
>
> wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
> sage-run received unknown option: --dev
> usage: sage [options]
> Try 'sage -h' for more information.

The "devscripts" had been deprecated and have now been removed (in
favour of Volker's "git-trac" command), since 7.0 IIRC.

You can install it independently (outside a Sage installation), but it's
meanwhile also an optional Sage package (named 'git_trac').

I'd have to dig where it's documented, but

git help trac

should give you an overview (after installation of course).

The source code is on GitHub (vbraun or sagemath, not sure).


You can otherwise of course use plain git (cf. "Git the hard way" in
Sage's Developer Guide).


-leif


> What am I doing wrong?
>
> I just did
>
> wspage@sarah ~ $ git clone git://github.com/sagemath/sage.git
> wspage@sarah ~ $ cd sage
> wspage@sarah ~/sage $ make
>
> Build completed without errors.
>
> wspage@sarah ~/sage $ ./sage
>
> seems to work as expected.


--
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: checkout from trac

[leif]

Bill Page wrote:
> It seems like I am always confused when I try to use sagetrac, but I
> did not expect this:
> 
> wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
> sage-run received unknown option: --dev
> usage: sage [options]
> Try 'sage -h' for more information.

The "devscripts" had been deprecated and have now been removed (in
favour of Volker's "git-trac" command), since 7.0 IIRC.

You can install it independently (outside a Sage installation), but it's
meanwhile also an optional Sage package (named 'git_trac').

I'd have to dig where it's documented, but

git help trac

should give you an overview (after installation of course).

The source code is on GitHub (vbraun or sagemath, not sure).


You can otherwise of course use plain git (cf. "Git the hard way" in
Sage's Developer Guide).


-leif


> What am I doing wrong?
> 
> I just did
> 
> wspage@sarah ~ $ git clone git://github.com/sagemath/sage.git
> wspage@sarah ~ $ cd sage
> wspage@sarah ~/sage $ make
> 
> Build completed without errors.
> 
> wspage@sarah ~/sage $ ./sage
> 
> seems to work as expected.


-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] checkout from trac

[Bill Page]

It seems like I am always confused when I try to use sagetrac, but I
did not expect this:

wspage@sarah ~/sage $ ./sage --dev checkout --ticket=21231
sage-run received unknown option: --dev
usage: sage [options]
Try 'sage -h' for more information.

--

What am I doing wrong?

I just did

wspage@sarah ~ $ git clone git://github.com/sagemath/sage.git
wspage@sarah ~ $ cd sage
wspage@sarah ~/sage $ make

Build completed without errors.

wspage@sarah ~/sage $ ./sage

seems to work as expected.

-- 
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 sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.

[sage-devel] Re: Error building after checking out old version.

[leif]

Joseph Hundley wrote:
> Quick update: removing the backslash seems to fix the problem with
> all.py. It was probably a stray character introduced when I went in to
> do some other minor fixes.

Yes.  I didn't say explicitly, but I of course meant "remove it if it's
also in the corresponding file below src/".

The file (just as other *.py files below src/sage/) gets simply copied
to local/lib/.../site-packages/sage/... when you run './sage -b', which
is also invoked by 'make'.  (Actually, src/setup.py does this.)


> Unfortunately, it appears that the merge tool I used (Apple's FileMerge)
> has introduced a bunch of indentation errors in another file. Which is a
> bit too bad. Thankfully the conflicts were minimal and I should be able
> to resolve by hand. 
> 
> And make finally works!  Huzzah!

Not sure what you have planned, but if you push your rebased branch back
to trac, it's probably safer to simply create a new branch (and update
the "Branch" field on the ticket accordingly) rather than doing a
[forced] push to the old branch.  (If anything else went wrong when
rebasing, then others could still retry with the original old branch on
trac.)


-leif


> Thanks for all the help.
> 
> JH
> 
> On Friday, August 12, 2016 at 9:47:03 PM UTC-4, Joseph Hundley wrote:
> 
> Yes, and yes.
> Both 
> /Users/jahundle/sage/local/lib/python2.7/site-packages/sage/categories/all..py
> and $SAGEROOT/src/sage/categories/all.py start with a backslash.
> 
> Using a merge program to compare them confirms that they're identical. 
> 
> On a hunch I decided to
> compare  $SAGEROOT/src/sage/categories/all.py
> with  $SAGEROOT/src/sage/categories/all.py.orig which I would 
> guess is a file created during the merge process. The backslash is
> not there in the "orig." So, maybe it's a stray character introduced
> at that
> stage? Would a typo I'd made during the merge get propogated
> from  $SAGEROOT/src/sage/categories/all.py
> to 
> /Users/jahundle/sage/local/lib/python2.7/site-packages/sage/categories/all.py?
> 
> Thanks for your help.
> 
> Maybe I'll try seeing what deleting that backslash does.
> 
> Joe
> 
> On Friday, August 12, 2016 at 3:45:17 PM UTC-4, leif wrote:
> 
> Joseph Hundley wrote:
> >
> > On Friday, August 12, 2016 at 12:13:08 PM UTC-4, Joseph
> Hundley wrote:
> >
> > [...] I ran
> >
> > git reset --hard HEAD
> > make clean
> > make doc-clean
> >
> > and am now back to a state where make works.
> >
> > hundleymac:sage jahundle$ git status
> >
> > On branch develop
> >
> > Your branch is up-to-date with 'origin/develop'.
> >
> > nothing to commit, working tree clean
> >
> >  
> >
> > Normally speaking, you want to continue working on
> this ticket
> > on the current beta (although 7.4.beta0 is a bit
> > broken, as happens with some betas).
> >
> > That is, you should rebase the branch over 7.4.beta0
> > I.e.,
> > git checkout -b new16821 7.4.beta0
> >
> >
> > fatal: Cannot update paths and switch to branch 'new16821'
> at the
> > same time.
> >
> > Did you intend to checkout '7.4.beta0' which can not be
> resolved as
> > commit?
> >
> >
> > To get around this issue I just did
> >
> > git checkout -b new16821
> >
> > hundleymac:sage jahundle$ git status
> >
> > On branch develop
> >
> > Your branch is up-to-date with 'origin/develop'.
> >
> > nothing to commit, working tree clean
> >
> >
> > git fetch trac public/lie_algebras/classical-16821
> > git merge FETCH_HEAD
> > (the latter may require further actions, be alert...
> >
> >
> > these commands now work.  There were a few files to merge. I
> used git
> > mergetool and the Apple Developer program FileMerge, plus a
> little
> > by-hand editing.
> >
> > make produced
> >
> > 
> >
> > cd ../.. && sage-logger -p './sage --docbuild --no-pdf-links
> all html '
> > logs/dochtml.log
> >
> > [dochtml] Traceback (most recent call last):
> >
> > [dochtml]   
> >
> > [dochtml]   File
> >
> 
> "/Users/jahundle/sage/local/lib/python2.7/site-packages/sage/combinat/free_module.py",
> 
> > line 29, in 
> >
> > [dochtml] from sage.categories.all import Category, Sets,
> > ModulesWithBasis
> >
> >