On Sat, 22 Feb 2020 at 10:15, Marco A. <strigiwm@gmail.com> wrote:
Hello,

Sorry to resurrect this old thread but I came across some issues while
attempting to upload the initial configuration for a new chapter
wiki[1].

The new composer commands do look for an entry in wikiversions.json no
matter what, apparently; and refuse to work if they find none. I am
not sure if we want that behaviour, considering that it takes weeks
after the initial configuration gets uploaded for a wiki to be
created, and wikiversions.json changes thrice per week due to the
mediawiki trains.

Why does it take weeks?
 
I used to upload configuration patches without that entry on purpose
so it was easier to rebase once the configuration patch was about to
be merged. I did the trick locally adding a wikiversion.json entry,
running the composer commands but not committing the wikiversions file
later; however that also causes Jenkins to fail as it detects wikis in
all.dblists in all but not in wikiversions.json.

Just add a wikiversions.json line. Rebasing this is pretty trivial whenever someone is actually making the wiki.

In the future, assuming we do go ahead and dispose of InitialiseSettings.php entirely to only have the YAML files, it won't be much hardship to have to rebase for wikiversions.json only.

 
`composer test` also failed due to some weird errors[2] which I'm not
sure are relevant for local testing:
TimelineTest::testTimelineFontFileEexists.

That's because you've not `git submodule update --init`'ed.

 
Also, on the Wikitech guide[3] there's no mention of this new
procedure. We should be updating it I guess.

Updated today. Hope that helps, but I probably missed something, so feel free to shout.


J.
--
James D. Forrester (he/him or they/themself)