01:00 <isd> Jacob Weisz: know anything about composer? I am trying to update the mediawiki package and hitting errors from this strange php package manager that I am unfamiliar with.

01:02 <isd> I dumped the error in the commit message: https://github.com/zenhack/mediawiki-sandstorm/commit/17ed462384e3e80f256d040add0494ef2b7253eb

01:02 <isd> My best guess is that we're pulling in a version of composer that is too new for mediawiki or something, but I'm unfamiliar with the relevant tooling

01:09 <ocdtrekkie> I haven't ever used composer. I understand it is the PHP version of like an npm thing but I basically write all vanilla PHP.

01:12 <isd> drat.

01:13 <isd> The update does not seem like it's going to be too bad overall though. Yay for apps that were pretty mature even when sandstorm was new?

01:14 <isd> Most of Jason's patches applied cleanly, only a couple exceptions, some of which may just be obsolete.

01:17 <ocdtrekkie> I'm a big DokuWiki fan now, personally, but it'll be nice to bring that package up... six years.

01:25 <isd> My housemates wanted something with a wysiwyg editor

01:26 <ocdtrekkie> Ah yeah, that's where your WordPress and MediaWiki classics shine

02:23 <isd> Looks like the version of mediawiki in the app store is so old that the migration scripts don't even support it anymore.

02:24 <isd> (sidestepped the composer issue; you can get the deps just by pulling in submodules)

02:38 <ocdtrekkie> Just going to publish as a new package then?

02:39 <isd> Maybe. I don't have any old grains to migrate.

02:39 <isd> The alternative would be to stash a copy of 1.27 in the grain for the purposes of intermediate upgrade. That sounds complicated.

02:55 <ocdtrekkie> Yeah without even anecdata on the matter that might be a lot of work for a single grain somewhere.

02:55 <ocdtrekkie> If you are considering the effort maybe ask the dev list if anyone needs upgrading.

03:20 <isd> Looks like they re-did how user auth works internally, the sandstorm auth integration is bitrotten.

11:15 <TimMc> It would be interesting if Sandstorm could support intermediate upgrades by having a package declare its min previous version.

11:16 <TimMc> Then you could publish an intermediate package and then the newest package.

12:24 <ocdtrekkie> We have an open issue for that.

12:25 <ocdtrekkie> Actually the package definition even had a field for it, it just never was implemented.

21:39 <isd> I suppose I could do that anyway, and just tell anyone who wants to upgrade an ancient grain that they'll need to futz with the versions...

21:41 <isd> But yes, that would be useful. It's a bit fiddly to implement though, because you need to be able to tell if the upgrade actually took; if you upgrade a grain, never launch it, and then upgrade it again, then the logic for the first upgrade never runs.

21:41 <isd> So we'd have to define a way for grains to tell sandstorm what there "data version" is or such. All this is on the issue iirc.

21:42 <isd> I'm not sure I care enough to do it either way, but I think I will ping the mailing list to see if anyone actually has old grains that they care about.

22:14 <ocdtrekkie> Another possible resource is asking Kenton to check the data from servers which opt in to sharing usage data.

22:50 <isd> kentonv: ^

22:50 <isd> Any insights into how much use mediawiki gets?

22:51 <kentonv> I shut down the dashboard a while back, though I think the data is still being collected in a grain on Alpha, but I'm not entirely sure how to access it

22:57 <isd> Don't worry about it then.