This is just a guess about the remote config… First some background…
I have been unable to get the skins to change on my server repo when its running as fossil server <dirname> and connecting through the web to the named repo: http://host:port/repo/ I go to the admin-skins page, but click on the install button for all the different skins doesn’t change anything. meanwhile, back on my cloned repo, I startup the gui using fossil ui and through that webpage, I can change the skins easily on the cloned repo. At some point I think I probably tried to do a push config from the cloned repo back to the server repo, in hopes that I could push the skin there that way. Which didn’t work BTW. Is it possible that when I did a push config, the remote config went with it, thus configuring the server to think it has a remote, which is itself? On May 3, 2016, at 11:58 AM, Richard Hipp <d...@sqlite.org> wrote: > On 5/3/16, Steve Schow <st...@bstage.com> wrote: >> This particular repo is not a clone of another repo. >> And it appears to be trying to sync with itself. > > Huh. I don't know how you got it into that state. > > The solution is probably "fossil remote off". > > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > 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
