[sage-support] Documentation won't compile correctly/ can't rebase git branch

2017-06-01 Thread Zachary Gershkoff
I have a ticket where I made some changes to the graph theory package. The documentation wasn't compiling correctly, so I made and remade sage from the develop branch and eventually got it working there. When I switch back to my ticket and try to build the documentation, it says there's an error

[sage-support] Re: Does `sage -upgrade` upgrade the packages as well?

2017-06-01 Thread Zachary Gershkoff
How does one upgrade with git? Is it enough to pull the master or develop branch? On Saturday, May 13, 2017 at 10:11:33 AM UTC-5, Dima Pasechnik wrote: > > IIRC, --upgrade is broken for years already, and should be removed. > If you need to upgrade a source installation, use git; the correspondin

[sage-support] Re: Documentation won't compile correctly/ can't rebase git branch

2017-06-02 Thread Zachary Gershkoff
Dima, I'm not sure why I would make a new local branch. However, I was able to successfully rebase and then build the documentation (and then pull, and then push) after I followed your earlier advice on upgrading sage. I must have broke something before by using the --upgrade option. Thanks, Z

[sage-support] sagemath command line echo has commands I didn't make

2017-06-04 Thread Zachary Gershkoff
After rebuilding and running sage, these three things appeared when I press the up key: sage: trace('print(factor(10))'); print(3+97) sage: print([sys.stdin.isatty(), sys.stdout.isatty()]) sage: 3^33 I have no idea what to make of that. I never typed any of those. -- You received this

[sage-support] Unable to check out trac tickets

2017-07-24 Thread Zachary Gershkoff
I tried to create a new ticket and link it to an existing local branch using git-trac. The trac ticket was created, but attaching a local branch to it failed. I tried checking out the ticket that it created (23536) and this happened: zgersh2@helmholtz:~/sage$ git trac checkout 23536 Loading tic

[sage-support] Re: Unable to check out trac tickets

2017-07-25 Thread Zachary Gershkoff
That worked! I did have uncommitted changes because there was a file I didn't want to commit, but I removed it from the directory. Creating the remote branch the way you said and then setting the branch on the trac ticket manually seemed to work. On Tuesday, July 25, 2017 at 12:24:52 AM UTC-5,

[sage-support] Re: Unable to check out trac tickets

2017-08-02 Thread Zachary Gershkoff
cfeeab9f03607478' fatal: loose object 20d0fd3d389aeea9ad4b9b91cfeeab9f03607478 (stored in .git/objects/20/d0fd3d389aeea9ad4b9b91cfeeab9f03607478) is corrupt fatal: index-pack failed What can I do, short of deleting everything and cloning the entire repository again? On Monday, July 24

[sage-support] Re: Unable to check out trac tickets

2017-08-02 Thread Zachary Gershkoff
I followed the instructions on https://stackoverflow.com/a/18238322 and it seems to be working so far. I lost all my local branches, but I don't mind. On Monday, July 24, 2017 at 8:01:03 PM UTC-5, Zachary Gershkoff wrote: > > I tried to create a new ticket and link it to an existing l