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

[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 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 ticket #23536...
> Newly created local branch: t/23536/transversal_matroids
> Traceback (most recent call last):
>   File "/U1/accounts/zgersh2/git-trac-command/bin/git-trac", line 18, in 
> 
> cmdline.launch()
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/cmdline.py", line 
> 215, in launch
> app.checkout(args.ticket_or_branch, args.branch_name)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/app.py", line 116, 
> in checkout
> self._checkout_ticket(int(ticket_or_branch), branch_name)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/app.py", line 134, 
> in _checkout_ticket
> self.repo.create(local)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_repository.py", 
> line 145, in create
> self.git.fetch('trac', starting_branch)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_interface.py", 
> line 341, in meth
> return self.execute(git_cmd, *args, **kwds)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_interface.py", 
> line 328, in execute
> popen_stderr=subprocess.PIPE)
>   File "/U1/accounts/zgersh2/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 (1) when 
> executing "git fetch trac develop"
> STDERR: error: garbage at end of loose object 
> '20d0fd3d389aeea9ad4b9b91cfeeab9f03607478'
> STDERR: fatal: loose object 20d0fd3d389aeea9ad4b9b91cfeeab9f03607478 
> (stored in .git/objects/20/d0fd3d389aeea9ad4b9b91cfeeab9f03607478) is 
> corrupt
> STDERR: error: git://trac.sagemath.org/sage.git did not send all 
> necessary objects
> STDERR:
>
> I'm not sure what to do here. Apparently I have to take out some garbage 
> before uploading my changes?
>
> For what it's worth, the branch "t/23536/transveral_matroids" was not 
> actually created, since it doesn't show up when I use "git branch".
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[Zachary Gershkoff]

This error with "garbage at end of loose object" is coming back to plague 
me. I recently tried to upgrade sage by pulling the develop branch, but I 
couldn't.

zgersh2@helmholtz:~/sage$ git checkout develop
Switched to branch 'develop'
zgersh2@helmholtz:~/sage$ git pull
remote: Counting objects: 3375, done.
remote: Compressing objects: 100% (682/682), done.
remote: Total 3375 (delta 2860), reused 3192 (delta 2678), pack-reused 0
Receiving objects: 100% (3375/3375), 790.77 KiB | 247 KiB/s, done.
error: garbage at end of loose object 
'20d0fd3d389aeea9ad4b9b91cfeeab9f03607478'
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, 2017 at 8:01:03 PM UTC-5, Zachary Gershkoff wrote:
>
> 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 ticket #23536...
> Newly created local branch: t/23536/transversal_matroids
> Traceback (most recent call last):
>   File "/U1/accounts/zgersh2/git-trac-command/bin/git-trac", line 18, in 
> 
> cmdline.launch()
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/cmdline.py", line 
> 215, in launch
> app.checkout(args.ticket_or_branch, args.branch_name)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/app.py", line 116, 
> in checkout
> self._checkout_ticket(int(ticket_or_branch), branch_name)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/app.py", line 134, 
> in _checkout_ticket
> self.repo.create(local)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_repository.py", 
> line 145, in create
> self.git.fetch('trac', starting_branch)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_interface.py", 
> line 341, in meth
> return self.execute(git_cmd, *args, **kwds)
>   File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_interface.py", 
> line 328, in execute
> popen_stderr=subprocess.PIPE)
>   File "/U1/accounts/zgersh2/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 (1) when 
> executing "git fetch trac develop"
> STDERR: error: garbage at end of loose object 
> '20d0fd3d389aeea9ad4b9b91cfeeab9f03607478'
> STDERR: fatal: loose object 20d0fd3d389aeea9ad4b9b91cfeeab9f03607478 
> (stored in .git/objects/20/d0fd3d389aeea9ad4b9b91cfeeab9f03607478) is 
> corrupt
> STDERR: error: git://trac.sagemath.org/sage.git did not send all 
> necessary objects
> STDERR:
>
> I'm not sure what to do here. Apparently I have to take out some garbage 
> before uploading my changes?
>
> For what it's worth, the branch "t/23536/transveral_matroids" was not 
> actually created, since it doesn't show up when I use "git branch".
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[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, Dima Pasechnik wrote:
>
>
>
> On Tuesday, July 25, 2017 at 6:15:54 AM UTC+1, Dima Pasechnik wrote:
>>
>> So you want to push the current branch to trac; you have committed local 
>> changes.
>> Show us the output of
>>
>> git status
>>
>> if unsure. Then, in case, 
>> check that track's repo is known as trac. Type 
>>
>> git remote -v
>>
>> In the output you should see the line
>>
>> trac g...@trac.sagemath.org:sage.git (push)
>>
>> Then do
>>
>> git push trac --set-upstream HEAD:u/zgershkoff/transversal_matroids
>>
>> It should succeed, assuming your authentication with trac git is set up 
>> OK,
>> and setting the local branch to follow the remote one (anyway, the latter 
>> is no big deal if you only work on this branch from one local repo).
>>
>> Finally, edit the ticket on trac and put 
>> u/zgershkoff/transversal_matroids into the branch field.
>> Done.
>>
>
> PS. This does not use git-trac, just plain git.
> If you succeeded doing the above, you'd be able to call yourself a git 
> guru. :-)
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

[sage-support] Unable to check out trac tickets

[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 ticket #23536...
Newly created local branch: t/23536/transversal_matroids
Traceback (most recent call last):
  File "/U1/accounts/zgersh2/git-trac-command/bin/git-trac", line 18, in 

cmdline.launch()
  File "/U1/accounts/zgersh2/git-trac-command/git_trac/cmdline.py", line 
215, in launch
app.checkout(args.ticket_or_branch, args.branch_name)
  File "/U1/accounts/zgersh2/git-trac-command/git_trac/app.py", line 116, 
in checkout
self._checkout_ticket(int(ticket_or_branch), branch_name)
  File "/U1/accounts/zgersh2/git-trac-command/git_trac/app.py", line 134, 
in _checkout_ticket
self.repo.create(local)
  File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_repository.py", 
line 145, in create
self.git.fetch('trac', starting_branch)
  File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_interface.py", 
line 341, in meth
return self.execute(git_cmd, *args, **kwds)
  File "/U1/accounts/zgersh2/git-trac-command/git_trac/git_interface.py", 
line 328, in execute
popen_stderr=subprocess.PIPE)
  File "/U1/accounts/zgersh2/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 (1) when 
executing "git fetch trac develop"
STDERR: error: garbage at end of loose object 
'20d0fd3d389aeea9ad4b9b91cfeeab9f03607478'
STDERR: fatal: loose object 20d0fd3d389aeea9ad4b9b91cfeeab9f03607478 
(stored in .git/objects/20/d0fd3d389aeea9ad4b9b91cfeeab9f03607478) is 
corrupt
STDERR: error: git://trac.sagemath.org/sage.git did not send all 
necessary objects
STDERR:

I'm not sure what to do here. Apparently I have to take out some garbage 
before uploading my changes?

For what it's worth, the branch "t/23536/transveral_matroids" was not 
actually created, since it doesn't show up when I use "git branch".

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[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 message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[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,
Zach

On Thursday, June 1, 2017 at 10:41:20 AM UTC-5, Dima Pasechnik wrote:
>
> I would rather (replace my* with right values)
>
> git checkout -b myrebasedstuff develop
> git pull trac u/myuid/mygreatbranch
>
> # assume it all merged fine, then
>
> make doc-clean
> make
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[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 corresponding 
> to the pulled version packages
> will be automatically upgraded, apart from "old style" ones, that are not 
> upgraded any more anyway.
>
> A binary installation cannot be updated using --upgrade at all, I think.
>
> On Saturday, May 13, 2017 at 11:28:31 AM UTC+1, rickhg12hs wrote:
>>
>> Does `sage -upgrade` upgrade the packages as well?
>>
>> If not, what's the most efficient way to upgrade all packages to the 
>> latest release?
>>
>>
>> Is this bullet from Sage Docs 
>>  still 
>> acuurate?
>>
>>
>>- --upgrade [url] – download, build and install standard packages 
>>from given url. If url not given, automatically selects a suitable 
>> mirror. 
>>If url=’ask’, it lets you select the mirror.
>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.

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

[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 
in combinat (not graph theory, where I had been working). I tried rebasing 
the ticket (git rebase -i develop), and I got the following error message


error: could not apply eda38df... Implementing crystal of MV polytopes and 
added plotting.

When you have resolved this problem run "git rebase --continue".
If you would prefer to skip this patch, instead run "git rebase --skip".
To check out the original branch and stop rebasing run "git rebase --abort".
Could not apply eda38df... Implementing crystal of MV polytopes and added 
plotting.


I don't know what to do to let it continue rebasing because I didn't change 
anything relating to crystals or plotting... I just want the documentation 
on my ticket to compile. How can I fix this?

Thanks,
Zach

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.