On Dec 26, 2017, at 4:22 PM, Olivier Mascia <[email protected]> wrote:
>
> I have no issues or difficulties with fossil commands themselves and know how
> to, for instance, clone and properly open sqlite repository
Oh, I thought you were seeing this with your own new repository.
Now that I know what to test, I see it, too:
fossil-native-2.4 clone https://sqlite.org/cgi/src x.x
mkdir x
cd x
fossil-native-2.4 open ../x.x
fossil-native-2.4 ui
This is with fossil-native-2.4.exe being the binary from fossil-scm.org,
so-named to differentiate it from the fossil.exe binary I actually use here. :)
The problem is due to the improvements to skinning. When you initially clone
the repository, you get a copy of the remote skin configuration, but it will
only work if you have a version of Fossil as of about a month ago, when all of
this changed.
What you’re doing to fix it is override the skin that sqlite.org gave you with
a configuration that works correctly with your local fossil.exe.
Until drh ships Fossil 2.5, you’ll have to either stick with that workaround or
build your own fossil.exe against the trunk code.
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
