[12:41:47] Hello, I have a question about gerrit [15:05:52] I need to upgrade and migrate a wiki family of 2 wikis to a new server [15:06:20] I tried the upgrade from 1.32.0 to 1.32.1, but it only ran successfully for the test wiki, but not the main wiki [15:07:14] I kinda know the answer to this one, yet I ask to get confirmation: "Would it be non-idiotic to migrate the wikis to the new server and only then try to get the upgrade to run?" [15:08:00] Coz I'm sick and tired of all the companies sabotaging their shit when they notice that I am the customer, so I'd just like to dump the old hosting provider asap [15:20:58] Hi all. I'm looking for legacy release tarballs. I'm upgrading from 1.20. [15:26:34] https://releases.wikimedia.org/mediawiki/ ? [15:26:45] https://www.mediawiki.org/wiki/Download [15:26:47] https://www.mediawiki.org/wiki/Manual:Upgrading [15:27:10] andre__: Thanks! :) [15:27:18] yw [16:18:49] I'm upgrading my database with the web interface upgrade wiki. There is no status or prgress messages. How can I see if it is making progress? [16:58:24] superboot: there should be, I guess it depends on your web server whether it can send the response progressively [16:58:46] in any case, unless your wiki is unusually huge it should take very little time [17:00:11] jubo2: for a point upgrade, the upgrade script should do very little [17:00:35] so it doesn't really matter [17:01:53] superboot: you can try upgrading directly to the current release, it's a bit more risky, but not that much, and a lot simpler [17:02:01] tgr: I did comment out the shared tables in LocalSettings.php and gave the name of the wiki to upgrade as an environment variable and the test wiki upgraded just fine in under a second, but the main wiki did not. This was like 3 weeks ago and I just rolled back the upgrades, because I could not finish the task [17:04:40] jubo2: at a glance the maintenance directory (where the DB patches for the update script are) didn't change at all between 1.32.0/1 [17:10:37] tgr: so.... would indicate that the main wiki is in a somehow broken state (even if it looks fine in browser) [17:10:42] + question mark [17:11:45] that would be my guess [17:12:17] the updater might still do nontrivial work if e.g. a relevant configuration setting has changed [17:12:50] but all changes between .0 and .1 are things that have been intentionally backported, so it's unusual for something like that to happen [17:13:30] do you know what exactly breaks? [20:49:13] Is it possible to delete or hide an account that has made 0 edits? [20:53:40] Okay Why is this throwing a Lintwarning? [20:53:41] https://en.wikisource.org/wiki/Template:Code [20:53:57] When I use Special:ExpandTemplate there is NO error found? [20:54:10] Where is the missing tag please? [21:05:43] maybe in the documentation? [21:15:56] Yes [21:16:00] Where [21:16:01] ? [21:16:22] This solved it https://en.wikisource.org/w/index.php?title=Template%3ACode%2Fdoc&type=revision&diff=9449455&oldid=9447476 [21:16:34] But I can't figure out a logical reason WHY [21:17:28] bug in the tool trying to lint the page? [21:17:43] I'd rather not say that [21:18:14] when it expanded doesn't generate a concern [21:18:31] yes, because of the in there [21:18:56] So why in the Documentation for Code does it break? [21:19:21] Given that the various Nowiki tags SHOULD be escaping out certain seqeunces [21:20:14] Does not actually function like a PRE? [21:20:40] My thinking is that it's getting confused. [21:20:55] and MISmatching sequences [21:21:08] pre brings a lot of extra baggage that nowiki doesn't have (such as monospaced font and preserving whitespace) [21:21:34] Right... So how should the page be repaired without having to use the entities? [21:21:39] In terms of the parser, though, the inner is not parsed, as it shouldn't be. So, the issue is with the linter getting hung up on it [21:21:51] fix the linter bug? [21:22:08] I am still not sure it's a linter bug [21:22:26] Linter is sure it's seen a tag mismatch [21:22:57] but the code in the page is otherwise balanced [21:23:06] Worth a ticket? [21:23:59] Skizzer: As far as I can tell the page is NOTBROKEN [21:24:20] right, because it's not a parser bug [21:24:33] ShakespeareFan00: yeah, i'd say worth a ticket. it's plausible that it doesn't understand that the "inner" in is plain text rahter than a HTML tag [21:24:53] Also why did the entities work? [21:24:58] the parser is doing the right thing (escaping the < > into < > upon parse), but the linter doesn't recognize that things inside of don't get parsed or something similar to that [21:25:10] i honestly wouldn't be able to tell you if you asked me if escapes HTML inside of it. i guess i just learned that it does [21:25:26] The entities are me [21:25:29] I had to go to Special:ExpandTemplates to verify that it did escape them [21:25:30] Manual [21:25:30] perhaps whoever wrote that part of the Linter tool also didn't know [21:25:47] ShakespeareFan00: the parser does indeed automatically escape < and > inside of blocks [21:25:56] the linter likely runs on the pre-parsed wikitext [21:26:08] Ouch [21:26:29] I thought the Linter was running on the RAW output? [21:26:48] remex (aka tidy) has already run on that output, so the linter wouldn't be able to give accurate results [21:27:18] that said, all of this is conjecture on my part [21:27:21] I haven't looked at that code at all [21:27:31] MatmaRex: Do you have some test cases? [21:27:32] just guessing based on observed behavior [21:28:35] ShakespeareFan00: no, i've just heard about the problem from you for the first time :D [21:28:55] I'd very much like to think this is a Linter misdetection [21:29:14] but cannot be certain it's that [21:29:52] What does Linter Actually analyse? [21:30:04] no idea! what linter are we talking about? [21:30:25] Special:LintErorrs [21:30:49] being the Linter that was implemented to find issues with Wiki markup [21:31:23] MatmaRex: Worth a ticket? [21:31:27] As I asked earlier [21:31:51] because I'm still not convinced it's a misdetection [21:32:19] ShakespeareFan00: yes, please. even if it's not a bug, filing a bug is the best way to get someone actually knowledgeable to look into this [21:32:57] filing a ticket* [21:40:17] What I am suprised about is that didn't escape the < > as well [21:41:11] Presumably nowiki is only turning of Mediawiki processing [21:41:20] NOT HTML processing [21:42:07] aka processing [21:43:04] Anyway the escaping solved the problem for the moment [21:55:14] Hmm [21:55:15] https://en.wikisource.org/wiki/Template:Paragraph_break/doc [21:55:27] You think you've solved one problem ans another shows up :( [21:58:15] BTW Which langauges does Pygments/Geshi now support? [22:01:07] Because {{code|}} at Wikisource means syntax highlighting gets enabled for extracts [22:01:09] :) [22:05:15] it supports a lot: http://pygments.org/languages/ [23:05:01] Is it possible to delete or hide an account with 0 edits? [23:05:21] https://en.wikipedia.org/wiki/Wikipedia:FAQ#How_do_I_change_my_username/delete_my_account? [23:05:48] ^ this says "If an account was deleted, all the edits made by the user could not be properly attributed." [23:06:32] However if an account has 0 edits, then there should be no problem with "proper attribution"; so shouldn't it be allowed to be deleted? Thanks [23:07:41] On wikipedia or your own wiki that you’re hosting on your own servers? [23:07:59] If wikipedia, no, accounts won’t be deleted at all regardless of number of edits [23:08:15] If your own server, there’s a removeUnusedAccounts.php maintenance script that you can run which will delete those users [23:09:12] Skizzerz, will this feature of deleting / deactivating accounts ever be added to wikipedia? [23:09:30] for example, https://phabricator.wikimedia.org/T34815 [23:09:32] It’s not a technical restriction, it’s a policy one [23:10:15] ok, what if somebody's privacy and safety is at risk because of the username they used? [23:10:33] you can get it renamed, and the rename log suppressed [23:11:01] excellent, what if you're blocked? do you have to be unblocked and then rename the account? thanks [23:11:25] ask on your talk page? [23:11:33] this is really the wrong channel for this [23:11:47] unable to edit because of block [23:11:51] you could also try #wikipedia-en [23:11:59] thanks