Re: [fossil-users] cannot push or commit
At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server:http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received 2011/9/1 Lluís Batlle i Rossell virik...@gmail.com: On Thu, Sep 01, 2011 at 12:23:27PM -0500, Nolan Darilek wrote: Also, to expand even further, Fossil doesn't synchronize users along with the repository, so no need to make your local username/password the same. Just putting that out there, as when I was new I thought there was a shared list of users. You can take the list of users too, running 'fossil configuration pull user'. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Ron Georgia John 13:23 ___ 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] cannot push or commit
On Fri, Sep 02, 2011 at 01:44:51PM -0400, ron georgia wrote: At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server:http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received Ron Georgia John 13:23 You seem to be pushing as an anonymous user who probably doesn't have write permission. You may want to try pushing as a user you've already setup. fossil push http://someusern...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ It should then prompt you for your password, afterwards you can just do fossil push and it will send the correct credentials. -- James Turner ja...@calminferno.net signature.asc Description: Digital signature ___ 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] cannot push or commit
Thanks James (or Jim) - but here is what i get: rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker password for rgeorgia: via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 fossil: server says: 400 Bad Request Total network traffic: 788 bytes sent, 0 bytes received Note I am using a cgi script to point to the ntracker repository, will that have an affect on things? On Fri, Sep 2, 2011 at 1:51 PM, James Turner ja...@calminferno.net wrote: On Fri, Sep 02, 2011 at 01:44:51PM -0400, ron georgia wrote: At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server: http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received Ron Georgia John 13:23 You seem to be pushing as an anonymous user who probably doesn't have write permission. You may want to try pushing as a user you've already setup. fossil push http://someusern...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ It should then prompt you for your password, afterwards you can just do fossil push and it will send the correct credentials. -- James Turner ja...@calminferno.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk5hF60ACgkQrVACqCIZdxhz9gCgrMm/08BOxYEJzg4jIpajxqoD u0sAn0i0eDgCntXTCUUQjB/No7OxeUuI =rVYa -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Ron Georgia John 13:23 ___ 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] cannot push or commit
O! Got it! I removed the proxy. fossil set proxy off. Now i use my local proxy setting. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ password for rgeorgia: Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Received: 455 9 0 0 Sent:4621 17 0 9 waiting for server...Total network traffic: 3309 bytes sent, 0 bytes received EXCELLENT! Next, pushing just one file... we shall see. On Fri, Sep 2, 2011 at 2:04 PM, ron georgia rong1...@gmail.com wrote: Thanks James (or Jim) - but here is what i get: rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push http://rgeor...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker password for rgeorgia: via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 fossil: server says: 400 Bad Request Total network traffic: 788 bytes sent, 0 bytes received Note I am using a cgi script to point to the ntracker repository, will that have an affect on things? On Fri, Sep 2, 2011 at 1:51 PM, James Turner ja...@calminferno.net wrote: On Fri, Sep 02, 2011 at 01:44:51PM -0400, ron georgia wrote: At a complete loss. This is what i get every time, no matter what i do. Perhaps there is some fundamental thing i am not understanding. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil push Server: http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ via proxy: http://proxy.gslb.alcatel-lucent.com:8000 Bytes Cards Artifacts Deltas Sent: 866 17 0 0 Error: not authorized to write Received: 65 1 0 0 Total network traffic: 713 bytes sent, 0 bytes received Ron Georgia John 13:23 You seem to be pushing as an anonymous user who probably doesn't have write permission. You may want to try pushing as a user you've already setup. fossil push http://someusern...@carepo01.us.alcatel-lucent.com/cgi-bin/ntracker/ It should then prompt you for your password, afterwards you can just do fossil push and it will send the correct credentials. -- James Turner ja...@calminferno.net -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAk5hF60ACgkQrVACqCIZdxhz9gCgrMm/08BOxYEJzg4jIpajxqoD u0sAn0i0eDgCntXTCUUQjB/No7OxeUuI =rVYa -END PGP SIGNATURE- ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users -- Ron Georgia John 13:23 -- Ron Georgia John 13:23 ___ 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] cannot push or commit
On Thu, Sep 01, 2011 at 12:53:45PM -0400, Martin S. Weber wrote: Sadly if you clone with http://USER@host/...my.fsl and enter the password in the prompt, it will *not* remember the password (at least last time I tried). You can use USER:PASSWOR@host. Joerg ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
[fossil-users] cannot push or commit
All, I have read through almost all the pertinent Fossil documentation (FAQs included) and scoured the internet looking for help, so now i turn to you with what seems to be a noobe situation. Background: 1.) I install fossil on an OpenBSD (version 4.9) box. 2.) In the /var/www/cgi-bin i have a cgi script that points to a repository. Everything works wonderfully. 3.) I can see the project web page from in Windoz and Linux. from both environments I can clone the repository successfully. 4.) In Linux I add a directory to my local project (I guess it's called adding a branch). 5.) To make sure the user name and passwords are synced I fossil user password USERNAME 6.) Then I fossil commit -m Adding web pages -- this is what I get. rgeorgia@rgeorgia-c1:~/workspace/FOSSIL/ntracker$ fossil commit -m Added web pages Autosync: http://my_server.com/cgi-bin/ntracker via proxy: http://proxy.companty_proxy_server.com:8000/ Bytes Cards Artifacts Deltas Sent: 130 1 0 0 Received: 78 1 0 0 Total network traffic: 322 bytes sent, 0 bytes received New_Version: 2a5783eaf385c7bb3f1ac7630a4bd09f4abb881d Autosync: http://carepo01.us.alcatel-lucent.com/cgi-bin/ntracker via proxy: http://proxy.gslb.alcatel-lucent.com:8000/ Bytes Cards Artifacts Deltas Sent:5509 7 3 1 Error: not authorized to write Received: 111 1 0 0 Total network traffic: 2239 bytes sent, 0 bytes received fossil: Autosync failed Thanks in advance. Oh! Fossil version [79b7902cdd] -- Ron Georgia John 13:23 ___ 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] cannot push or commit
Try setting the autosync URL (fossil remote-url) to http://user@host:port/path. Note the presence of user in the URL. -Martin ___ 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] cannot push or commit
On 09/01/11 12:30, Stephan Beal wrote: On Thu, Sep 1, 2011 at 6:23 PM, Martin S. Webermartin.we...@nist.govmailto:martin.we...@nist.gov wrote: Try setting the autosync URL (fossil remote-url) to http://user@host:port/path. Note the presence of user in the URL. To expand on that a bit: if you clone with: fossil clone http://USER:PASSWORD@host/... my.fsl fossil will remember the authorization info but won't (unlike svn) reveal your password on stdout when shows you the URL later (e.g. via a pull/sync). Sadly if you clone with http://USER@host/...my.fsl and enter the password in the prompt, it will *not* remember the password (at least last time I tried). What I do then afterwards is set the remote-url to the same one again, which triggers me being asked for a password, and *then* it's stored. Not sure whether that's fixed already or not, but it's on my inquiry-list :-) -Martin ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
