Re: [fossil-users] fossil push doesn't show up on the server
On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote: What's wrong? What should I do to push my commits? Your answer is in the output of your failed fossil push: Error: not authorized to write -- James Turner ja...@calminferno.net ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil push doesn't show up on the server
James Turner ja...@calminferno.net writes:
On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote:
What's wrong? What should I do to push my commits?
Your answer is in the output of your failed fossil push:
Error: not authorized to write
Why am I not?
I created the remote by copying it with scp from a local repo I was
obviously authorized to modify.
I can login on the remote web with my usual login/password.
I re-cloned the local from the remote.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil push doesn't show up on the server
On Mon, May 7, 2012 at 7:02 PM, Pascal J. Bourguignon p...@informatimago.com wrote: I re-cloned the local from the remote. When you cloned it, did you add username:password to the URL? If not, try cloning with that. It doesn't look like you did because the Server: line does not show your name, like this: stephan@tiny:~/cvs/fossil/cpdo$ f push Server:http://step...@fossil.wanderinghorse.net/repos/cpdo/index.cgi Bytes Cards Artifacts Deltas Sent: 636 12 0 0 Received: 32 1 0 0 Total network traffic: 640 bytes sent, 286 bytes received -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil push doesn't show up on the server
I think this is a good illustration of how noisy output makes it hard for new users to see problems occurring. I would prefer to see most of the sync output suppressed unless a verbose switch is flipped. Most of the time people really only need to know that the sync succeeded or failed. At the very least make the error messages stand out more with an all upper case ERROR: prefix. On Mon, May 7, 2012 at 9:29 AM, James Turner ja...@calminferno.net wrote: On Mon, May 07, 2012 at 06:23:53PM +0200, Pascal J. Bourguignon wrote: What's wrong? What should I do to push my commits? Your answer is in the output of your failed fossil push: Error: not authorized to write -- James Turner ja...@calminferno.net ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil push doesn't show up on the server
Stephan Beal sgb...@googlemail.com writes:
On Mon, May 7, 2012 at 7:02 PM, Pascal J. Bourguignon
p...@informatimago.com wrote:
I re-cloned the local from the remote.
When you cloned it, did you add username:password to the URL? If not,
try cloning with that. It doesn't look like you did because the
Server: line does not show your name, like this:
No, indeed, I did not.
It works better if I clone it adding the user:password to the url.
Thank you.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] fossil push doesn't show up on the server
Matt Welland estifo...@gmail.com writes:
I think this is a good illustration of how noisy output makes it hard
for new users to see problems occurring. I would prefer to see most of
the sync output suppressed unless a verbose switch is flipped. Most
of the time people really only need to know that the sync succeeded or
failed. At the very least make the error messages stand out more with
an all upper case ERROR: prefix.
Definitely.
Also it's better of the error message is last in the output.
And in the case of cloning without a user:password, it might be good to
issue a warning that an anonymous clone has been done.
Alternatively, there could be a way to change the remote user:password
after cloning.
--
__Pascal Bourguignon__ http://www.informatimago.com/
A bad day in () is better than a good day in {}.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
