Andy Bradford wrote: > Thus said Will Parsons on Thu, 07 Aug 2014 00:53:53 -0000: > >> Since I wasn't transmitting any sensitive data anyway, I answered yes, >> and then got: >> >> Error: not authorized to write >> >> Is there something wrong with the way I'm trying to authenticate? > > I see you used -B for HTTP_AUTH. I don't know, but does chiselap > actually require HTTP_AUTH? At any rate, it won't be used unless > required, however, I suspect you are missing the actual Fossil username > somewhere and this is why Fossil is telling you that you are not > authorized to write. Without a Fossil username, you get the default set > of permissions which does not include the permission to write to the > repository.
I don't understand - what I represented by <uname> in the command *is* my chiselapp user name. To be clear, in my original local repository, I had a superuser "name1". I created the chiselapp user as "name2". Looking at the repository on chiselapp, I see two superusers, "name1" and name2". "name2" is what I represented by <uname> in the command I indicated. I assume I would have to supply my chiselapp name and password in the command line somehow, and if not by the -B option, then how? > You had: > >> fossil push https://chiselapp.com/user/<uname>/repository/<reponame> -B >> '<uname>:<passwd>' > > Maybe you should try something like the following instead: > > fossil push https://un...@chiselapp.com/user/<uname>/repository/<reponame> Now I'm really confused - what does that have to do with the chiselapp repository? (At any rate, I did try it and got connection refused.) -- Will _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
