Re: [galaxy-dev] hg push to remote tool shed fails with abort: authorization failed
Jorrit, Thank you for reporting this issue, I've committed a fix in the default branch at 9077:62bd6fe0e9aa, and it will be updated in stable at our next release. --Dave B. On 3/13/13 18:11:27.000, jorrit poelen wrote: To add some information to my earlier post - It seems that the remote repository is updated, but the commandline returns a confusing abort message. Trying on a private test toolshed, I see the following in the community-webapp.log: 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=capabilities HTTP/1.1 200 130 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=batch HTTP/1.1 200 43 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=branchmap HTTP/1.1 200 48 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=branchmap HTTP/1.1 200 48 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=listkeys HTTP/1.1 200 - - mercurial/proto-1.0 173.11.123.170 - testjorrit [13/Mar/2013:22:08:23 +] POST /repos/testjorrit/testrepo?cmd=unbundle HTTP/1.1 200 - - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:24 +] GET /repos/testjorrit/testrepo?cmd=listkeys HTTP/1.1 200 58 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:24 +] POST /repos/testjorrit/testrepo?cmd=pushkey HTTP/1.1 401 - - mercurial/proto-1.0 Which seems to indicate that most http get/post succeed, but the last one, pushkey, fails to authenticate. I am wondering whether I am the only one seeing this confusing behaviour and what I can do to stop this from happening. thx, -jorrit On Mar 13, 2013, at 2:37 PM, jorrit poelen wrote: Hey y'all, Even through http://wiki.galaxyproject.org/ToolShedRepositoryFeatures#Pushing_changes_to_a_repository_using_hg_from_the_command_line shows a working example of a hg push, I have not been able to push changes to a remote toolshed successfull. Here's an example of an unsuccessful attempt:. $ vi README $ hg commit -m 'bla' -u jorrit $ hg push pushing to http://jor...@testtoolshed.g2.bx.psu.edu/repos/jorrit/obotest searching for changes http authorization required realm: user: jorrit password: abort: authorization failed tried this with hg versions: Mercurial Distributed SCM (version 2.4.2+20130102) and Mercurial Distributed SCM (version 2.0.2) Curious to hear how I can get a hg push to remote repo to work from commandline! -jorrit ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] hg push to remote tool shed fails with abort: authorization failed
Thanks Dave for your super-quick response! Works like a charm. -jorrit On Mar 15, 2013, at 12:16 PM, Dave Bouvier wrote: Jorrit, Thank you for reporting this issue, I've committed a fix in the default branch at 9077:62bd6fe0e9aa, and it will be updated in stable at our next release. --Dave B. On 3/13/13 18:11:27.000, jorrit poelen wrote: To add some information to my earlier post - It seems that the remote repository is updated, but the commandline returns a confusing abort message. Trying on a private test toolshed, I see the following in the community-webapp.log: 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=capabilities HTTP/1.1 200 130 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=batch HTTP/1.1 200 43 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=branchmap HTTP/1.1 200 48 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=branchmap HTTP/1.1 200 48 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=listkeys HTTP/1.1 200 - - mercurial/proto-1.0 173.11.123.170 - testjorrit [13/Mar/2013:22:08:23 +] POST /repos/testjorrit/testrepo?cmd=unbundle HTTP/1.1 200 - - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:24 +] GET /repos/testjorrit/testrepo?cmd=listkeys HTTP/1.1 200 58 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:24 +] POST /repos/testjorrit/testrepo?cmd=pushkey HTTP/1.1 401 - - mercurial/proto-1.0 Which seems to indicate that most http get/post succeed, but the last one, pushkey, fails to authenticate. I am wondering whether I am the only one seeing this confusing behaviour and what I can do to stop this from happening. thx, -jorrit On Mar 13, 2013, at 2:37 PM, jorrit poelen wrote: Hey y'all, Even through http://wiki.galaxyproject.org/ToolShedRepositoryFeatures#Pushing_changes_to_a_repository_using_hg_from_the_command_line shows a working example of a hg push, I have not been able to push changes to a remote toolshed successfull. Here's an example of an unsuccessful attempt:. $ vi README $ hg commit -m 'bla' -u jorrit $ hg push pushing to http://jor...@testtoolshed.g2.bx.psu.edu/repos/jorrit/obotest searching for changes http authorization required realm: user: jorrit password: abort: authorization failed tried this with hg versions: Mercurial Distributed SCM (version 2.4.2+20130102) and Mercurial Distributed SCM (version 2.0.2) Curious to hear how I can get a hg push to remote repo to work from commandline! -jorrit ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
[galaxy-dev] hg push to remote tool shed fails with abort: authorization failed
Hey y'all, Even through http://wiki.galaxyproject.org/ToolShedRepositoryFeatures#Pushing_changes_to_a_repository_using_hg_from_the_command_line shows a working example of a hg push, I have not been able to push changes to a remote toolshed successfull. Here's an example of an unsuccessful attempt:. $ vi README $ hg commit -m 'bla' -u jorrit $ hg push pushing to http://jor...@testtoolshed.g2.bx.psu.edu/repos/jorrit/obotest searching for changes http authorization required realm: user: jorrit password: abort: authorization failed tried this with hg versions: Mercurial Distributed SCM (version 2.4.2+20130102) and Mercurial Distributed SCM (version 2.0.2) Curious to hear how I can get a hg push to remote repo to work from commandline! -jorrit ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
Re: [galaxy-dev] hg push to remote tool shed fails with abort: authorization failed
To add some information to my earlier post - It seems that the remote repository is updated, but the commandline returns a confusing abort message. Trying on a private test toolshed, I see the following in the community-webapp.log: 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=capabilities HTTP/1.1 200 130 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=batch HTTP/1.1 200 43 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=branchmap HTTP/1.1 200 48 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=branchmap HTTP/1.1 200 48 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:19 +] GET /repos/testjorrit/testrepo?cmd=listkeys HTTP/1.1 200 - - mercurial/proto-1.0 173.11.123.170 - testjorrit [13/Mar/2013:22:08:23 +] POST /repos/testjorrit/testrepo?cmd=unbundle HTTP/1.1 200 - - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:24 +] GET /repos/testjorrit/testrepo?cmd=listkeys HTTP/1.1 200 58 - mercurial/proto-1.0 173.11.123.170 - - [13/Mar/2013:22:08:24 +] POST /repos/testjorrit/testrepo?cmd=pushkey HTTP/1.1 401 - - mercurial/proto-1.0 Which seems to indicate that most http get/post succeed, but the last one, pushkey, fails to authenticate. I am wondering whether I am the only one seeing this confusing behaviour and what I can do to stop this from happening. thx, -jorrit On Mar 13, 2013, at 2:37 PM, jorrit poelen wrote: Hey y'all, Even through http://wiki.galaxyproject.org/ToolShedRepositoryFeatures#Pushing_changes_to_a_repository_using_hg_from_the_command_line shows a working example of a hg push, I have not been able to push changes to a remote toolshed successfull. Here's an example of an unsuccessful attempt:. $ vi README $ hg commit -m 'bla' -u jorrit $ hg push pushing to http://jor...@testtoolshed.g2.bx.psu.edu/repos/jorrit/obotest searching for changes http authorization required realm: user: jorrit password: abort: authorization failed tried this with hg versions: Mercurial Distributed SCM (version 2.4.2+20130102) and Mercurial Distributed SCM (version 2.0.2) Curious to hear how I can get a hg push to remote repo to work from commandline! -jorrit ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/ ___ Please keep all replies on the list by using reply all in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
