[00:06:13] seems like you are using CentralAuth? > Yep, I'm using CA [00:07:10] So, the best option is remove CA? [03:44:39] yeah, if you have multiple wikis just use WSOAuth, disable local login/account creation and rely on the central ID of the user being the same on all wikis. [11:18:29] So, I tried upgrading an inactive wiki from 1.35 to 1.35.1 with the instructions I have written for myself on how to upgrade a minor revision. I do have instructions on how to upgrade a major revision (git clone clean and move the LocalSettings.php and necessary directories with 'cp -Rp'). Should I try the major revision route? [11:21:41] the problem I had could have been to do with something having gone slightly wrong in the history or it could have been to do with the extensions being fetched being written for master, not 1_35 [11:29:16] yeah... running this again it ends in the same way. 'git submodule update --init --recursive' in extensions/ pulls tons of [new branch] called 'wmf/1.36.0-wmf.X', where the X is an integer. And then it ends aborting the task because it appears to git that manual changes have been made to something called "guzzlehttp" This is not right is it? [11:32:07] info: This particular wiki appears to have been installed with git since 1.31. Before that I did tarballs [11:38:00] I'ma revert that back to working state and look at another inactive wiki. It looks like I gonna need to do the long route I have documented for major revision upgrade [11:38:58] jukeboh: you're talking us about *your* written instructions that we don't know about :) [11:39:08] !upgrade [11:39:08] http://www.mediawiki.org/wiki/Manual:Upgrading [11:39:14] This is what we know about [11:40:10] Vulpix: yeah, and the long route is that one, done with git. The short route for minor revision upgrades would utilize git to get the freshest code and extensions for 1.35.1 in-place [11:41:44] when downloading from git, you also need to run composer. Maybe that's what you're missing? [11:42:09] composer dependencies may change even on minor version upgrades [11:45:22] at which stage should I run 'composer update --no-dev'? before or after 'git submodule update --init --recursive' ? Sorry if I'm being a little clueless, everyone can't be the texiest person in the world [11:46:29] This was the source of my method to upgrade minor revisions that worked ok for a while, but now won't work: https://www.mediawiki.org/wiki/Download_from_Git#Keeping_up_to_date perhaps this is not up-to-dtae [11:54:23] the changes in the vendor folder are stopping 'git submodule update --init --recursive' from working. Can I move the vendor folder away and recreate it? [12:03:29] composer update 100% after git, or git'll complain. [12:03:57] yeah. after moving the 'vendor'-folder and recreating it with 'composer update --no-dev' resolved the issue [12:04:40] so I managed to upgrade in place with 'git pull' + ' [12:05:37] 'git pull https://gerrit.wikimedia.org/r/mediawiki/core.git REL1_35' + 'git submodule update --init --recursive' in /extensions/ + 'composer update --no-dev' in the /mediawiki/ + 'php maintenance/update.php'. Does this sound about right? [12:06:01] lemme repeat it on another wiki [12:08:46] I'm just thinking does the /vendor/-folder contain something that should be manually copied over to the one generated by 'composer update --no-dev' [12:25:51] If someone could check if my minor revision upgrade method described in 13 lines in here: https://paste.debian.net/1180174/ is correct or may cause some problems. Previously I did not need to move the vendor-folder away and recreate it. Do I need to edit something in the vendor-folder generated by 'composer update --no-dev' ? [13:21:59] All other wikis upgraded just fine but the test wiki in a wiki family of 2 members I cannot get to work. The testwiki has an installation of https://www.mediawiki.org/wiki/Wikibase/Installation [13:24:15] The current instructions say to require "monolog/monolog": "~2.0.2" in composer.local.json, but that causes a version mismatch problem as follows: "The requested package monolog/monolog ~2.0.2 exists as monolog/monolog[1.25.5] but these are rejected by your constraint." [13:38:34] I ran 'composer why-not monolog/monolog 2.0.2' in extensions/Wikibase and it says "wikibase/wikibase dev-REL1_35 requires monolog/monolog (^2.2)" [13:38:59] I'm on Debian10. What to do? [13:46:05] After a dirty random-guessing hack the test wiki with the wikibase seems upgraded [13:47:25] I put '"require": { "monolog/monolog": "~2.2.0"}' into composer.local.json and after that the composer and the update will run [14:40:47] Hi, When I write templates I don't want them to add new lines to the page which uses them, So I am ending with writing a comment for every line, such: https://pastebin.com/C0uQxZHN, There is any way to avoid this?:) [14:42:09] without the comma: https://pastebin.com/C0uQxZHN [17:27:21] hi, I think I found a mistake in the documentation of the mediawiki shibboleth extension in the readme.hd file on gerrit mediawiki [17:28:04] Near group mapping: https://github.com/wikimedia/mediawiki-extensions-Shibboleth [17:28:35] I think wgSimpleSAMLphp_GroupMap should be $wgShibboleth_GroupMap like on https://www.mediawiki.org/wiki/Extension:Shibboleth [17:35:03] tgr|away, before using WSOAuth I've ConfirmAccount, so will be deactivated [17:35:10] with CA? [17:36:59] c u m [17:37:56] wtf [17:44:44] Dear Democrats, [17:44:49] I will now eat a cheesecake. [17:53:12] oh sorry [17:53:16] wrong irc chan [18:06:07] c:hey Im serious it was a mistake [20:35:47] hey i have a backup of an old wiki and ive started a new wiki and my users didn't import correctly - all the pages are there, but not the users [20:36:17] in the revision histories, for example, the old users' names are just black text, not links to user pages [20:36:42] is there a way to re-import just the users? [20:37:06] (and how do i handle the fact that some of my old users have created new accounts with the same name..(!)) [20:37:54] why didn't they import? [20:37:59] what sort of backup did you have? [20:39:36] I have no idea why they didnt import unfortunately lol - the backup was an export of the old one - I used the mediawiki instructions page - I think I did a 'mysqldump' ? [20:40:06] is there a user table in the file? [20:40:33] yes, i've imported the wiki again under a different name and I can see all the old accounts [20:41:15] (not sure if that's what you meant - and the new one has a user table as well, but only with users who have created accounts since I remade it) [20:42:51] if it worked again for a different import... [20:43:30] is there a way to extract just the user data and import just that? the important part is their contributions/edits - my users really want to see what they've worked on [20:43:48] edit/contribution data doesn;t seem to be in the user table [20:44:19] the user table is just a list of users [20:45:23] can I merge two wikis in a way that won't overwrite new content? [20:47:06] Possibly, but it depends what you've dnoe [20:47:21] If you've created new user accounts on the new wiki, you're probably going to cause a renumbering [20:48:13] the old one has about 65,000 pages, and the new one has all that same content, plus whatever users have done since the new one went up (which was only a couple weeks ago, so not TOO much if it's lost - but obv they don't want to lose that work) [20:51:04] or - to solve it from the other direction - is there a way to export just the pages created/changed since, say, christmas, and import that into the functional, re-import that I did? [21:36:20] so I'm looking for, or looking to know where to ask, is the wikipedia network/server info published anywhere? I am hoping to convince my security department that we don't need to be SO secretive about our network/server layouts & ips... and I found this https://meta.wikimedia.org/wiki/Wikimedia_servers which at the very least has network [21:36:21] diagrams... [21:38:44] ofbeaton, likely on https://wikitech.wikimedia.org/ (but not sure what "server info" is supposed to mean) [21:38:58] might be a question for #wikimedia-tech as this channel is about MediaWiki mostly [21:40:30] ofbeaton: my general opinion is that security by obscurity is not great practice [21:44:57] https://github.com/wikimedia/operations-dns/blob/master/templates/10.in-addr.arpa [21:45:01] Depends what you're looking for ;) [21:45:07] https://github.com/wikimedia/puppet [21:45:20] But we make nearly everything but secrets/passwords/etc public [21:51:04] jaysan: Apparently you should be able to export pages from the api using recent changes as a generator: https://www.mediawiki.org/wiki/Special:ApiSandbox#action=query&format=json&prop=info&export=1&exportnowrap=1&generator=recentchanges&grcstart=2021-01-08T21%3A44%3A33.000Z&grcend=2021-01-08T18%3A44%3A33.000Z [21:51:26] This may export only the latest revision of each page, though [21:52:53] @Reedy thank you. that's what I was looking for. so wikimedia does not consider internal hostnames as secrets right? that's what the DNS entries look like to me... [21:53:04] We don't [22:46:07] Anyone know who made the AD authentication extensions? [22:46:17] I am having a horrible time setting up LDAPS. [22:46:34] LDAP works just fine, LDAPS refuses to be consistant. [22:46:44] at first it worked only 50% of the time. [22:46:57] Now it's like 90% of the time, but it still fails every 10th or so try. [22:53:51] which extension are you using? [22:53:57] Extension:LDAPAuthentication2 ? [23:02:19] Hmm. [23:02:22] Let me check. [23:02:25] Sorry for the late reply. [23:03:10] LDAPAuthentication2 [23:03:45] I am using PluggableAuth, LDAPProvider, LDAPAuthentication2, LDAPAuthorization, LDAPUserInfo, and LDAPGroups. [23:03:57] And Auth_remoteuser [23:13:58] I get this: [X-jm4uxVFWLjvfcqFzxLLwAAAMg] /index.php?title=Special:PluggableAuthLogin MWException from line 168 of /var/www/html/extensions/LDAPProvider/src/Client.php: Could not bind to LDAP: (-1) Can't contact LDAP server [23:14:17] But it's only sometimes. [23:14:21] Other times it works just fine.