[00:00:32] !packages | JustSighDudes [00:00:33] JustSighDudes: Many Linux distributions provide MediaWiki in a packaged format for that distribution. These packages typically contain obsolete and unsupported versions of MediaWiki, also they like to move around files, change the files, and do other batshit insane things. You'll get the best support here if you install MediaWiki directly from one of our tarballs, available at https://www.mediawiki.org/ [00:00:53] Yeah that's what I was worried about [00:01:03] Is there a way to keep it constantly updated? I'm kind of paranoid about security [00:01:27] there /are/ packages, none of them are however endorsed by us the developers [00:02:14] `git pull && php mantenance/update.php` in crontab :P [00:02:46] coae: yes, definitely. [00:04:34] MaxSem: Eh. That + DB backups should suffice for a personal wiki. Thanks. [00:07:03] JustSighDudes, ugh http://packages.ubuntu.com/search?keywords=mediawiki - unsupported version, and even that 2 security releases behind [00:10:46] MaxSem: we still support 1.19 :( [00:11:22] legoktm, EOL this month [00:12:22] oh fantastic [00:12:31] also, ubuntu is *4*, not 2 releases behind [00:12:46] :| [00:13:36] hey csteipp, we've been discussing whether 1.19 is already dead or it has oxygen until may 31:P [00:16:02] 12 days! [00:16:17] No more security releases till 1st June [01:02:23] bd808: if I try using vagrant lxc, will it override my current vagrant setup? [01:02:51] umm... [01:02:54] well... [01:03:12] it will make an lxc container [01:03:40] I woudl recommend playing with it in a new mw-v clone directory [01:04:07] ok [01:04:38] but please play with it and see if it works ok for you [01:04:53] I've been messing about with it on a labs vm some [01:06:30] bd808: and if I figure out the right packages and stuff, it should work on a fedora host right? it doesn't have to be debian/ubuntu? [01:06:58] I *think* it can be made to work on a non-ubuntu host [01:07:24] the host's lxc setup will need to know how to provision a ubuntu 14.04 container [01:07:38] I don't think the plugin takes care of that in any magic way [01:07:51] but there is a base container image we specify [01:08:37] legoktm: most of what I know about it is in https://github.com/wikimedia/mediawiki-vagrant/blob/master/support/README-lxc.md [01:09:43] legoktm: some info at https://github.com/fgrehm/vagrant-lxc/wiki/Usage-on-fedora-hosts as well [01:11:41] ==> default: Box 'Wikimedia/trusty64-puppet-lxc' could not be found. Attempting to find and install... [01:11:43] it's downloading the box now [01:12:15] oh yeah. I had forgotten that I made a custom box image for it [01:12:36] we needed 14.04 + puppet and I couldn't find one [01:13:48] heh. the premade VirtualBox image for testing isn't much help on the configuration -- https://github.com/fgrehm/vagrant-lxc-vbox-hosts/blob/master/provisioning/fedora/configure-bridge.sh [01:47:45] bd808: hmm, I had avoided nfs previously, is it required for lxc? or can I use the same disable option? [01:49:01] * legoktm disables [01:52:51] bd808: http://fpaste.org/223169/14320003/raw/ progress! [01:53:22] cool [01:53:32] so I logged in, ran sudo apt-get update [01:53:33] and then [01:53:39] W: Duplicate sources.list entry http://archive.ubuntu.com/ubuntu/ trusty/multiverse amd64 Packages (/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_trusty_multiverse_binary-amd64_Packages) [01:53:39] W: Duplicate sources.list entry http://security.ubuntu.com/ubuntu/ trusty-security/multiverse amd64 Packages (/var/lib/apt/lists/security.ubuntu.com_ubuntu_dists_trusty-security_multiverse_binary-amd64_Packages) [01:53:39] W: You may want to run apt-get update to correct these problems [01:53:45] legoktm bd808 : vagrant LXC ?! Exciting! [01:54:12] legoktm: ah. Somebody else ran into that too [01:54:34] I think we have puppet rules to setup multiverse [01:54:46] and the image may already have it setup a different way [01:54:55] hmm [01:55:21] JustSighDudes: if you use MediaWiki-Vagrant, `vagrant git-update` is a one-step command that keeps most pieces updated. It's configured for development rather than security [01:55:45] legoktm: look in the /etc/apt/sources.list and see if multiverse is uncommented [01:56:15] that file is just: [01:56:16] deb http://archive.ubuntu.com/ubuntu trusty main restricted universe multiverse [01:56:16] deb http://archive.ubuntu.com/ubuntu trusty-updates main restricted universe multiverse [01:56:16] deb http://security.ubuntu.com/ubuntu trusty-security main restricted universe multiverse [01:56:38] yeah image needs to be fixed [01:56:51] remove the multiverse from each of those [01:57:15] we should probably just puppet our own /etc/apt/sources.list [01:58:33] oh boy, nano isn't installed :( [02:01:44] try pico [02:01:58] I struggled through vim [02:04:53] legoktm: -5 points from Hufflepuff for "I struggled through vim" [02:05:11] legoktm, Yaron: thanks for your help! [02:05:25] Good night, everyone! [02:06:23] coae: np [02:06:58] bd808: I was just going to use cat to override the existing file :P [02:09:11] legoktm: :%s/multiverse$// :wq [02:09:40] I will remember that for next time :P [02:10:15] I'm running into https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-June/009591.html right now, trying to figure out where to disable selinux [02:23:06] mediawiki doesn't have a built-in syntax for repeating decimals? [02:26:08] bd808: so https://lists.linuxcontainers.org/pipermail/lxc-devel/2014-June/009588.html is what I'm seeing right now, I'm going to give up for now and try again when F22 comes out in a few weeks, which will work around https://bugzilla.redhat.com/show_bug.cgi?id=1196915 ... [02:28:28] legoktm: cool. I hope we can get it to work for most folks. It should be way faster than running VirtualBox [02:31:15] o.O wrong channel? [02:32:05] k_sze[work]: we were talking about mediawiki-vagrant :) [02:32:18] ah [02:32:22] k_sze[work]: no sytanx that I'm aware of [02:32:25] syntax* [04:29:38] hello, i add collection extension to my wiki, but now it did not worked. maybe i did not configure right [04:33:35] hello, i add collection extension on my wiki, it is not working fine and had problem in rendering, what should i do? [05:02:58] Hi sasan_. [05:03:05] !debug [05:03:05] For information on debugging (including viewing errors), see http://www.mediawiki.org/wiki/Manual:How_to_debug . A list of related configuration variables is at https://www.mediawiki.org/wiki/Manual:Configuration_settings#Debug.2Flogging [05:31:48] i do not know [06:15:43] it is not shown the error as you told me [06:15:48] could anybody help me? [10:41:37] Hi, I've a mediawiki api question: is there a way to retrieve page extracts + internal wikilinks? I need those links and their precise location (text offset in page extract) [11:32:46] Hi [11:36:38] I want to upgrade from Foswiki to MediaWiki . How can I import my existing Pages? [12:19:09] Hello apergos, will you be at LYON ? [12:19:44] no, sadly not [12:19:48] aw [12:19:49] are you going then? [12:19:52] yup [12:20:24] anyone you work with going? I still want to get these belgian chocolates to you :) [12:21:46] hi yall [12:22:55] I just upgraded from I think was 1.19 to 1.24.2, and the first new internal page I have created and populated with text, is still being shown as a red link... I've tried runJobs.php maintenance script and clearing my browser cache.. this has never happened before... [12:23:58] well after clearing the cache once more AFTER running the job, it's blue.. wow [13:31:17] quick question, does the origin/wmf/1.25wmf## branch get renamed REL1_25 when it's released? [13:31:42] wmat: no, a new branch is created [13:31:50] MatmaRex: ok, thanks [13:31:54] wmat: actually, there is a REL1_25 branch already [13:32:04] patches are being backported to it if necessary [13:34:04] so if I'm tracking master, can I safely switch to REL1_25 on release day? [13:40:08] wmat: what do you mean by "tracking master"? [13:40:25] wmat: REL1_25 is currently behind master by a few hundred commits probably [13:40:57] if you want to upgrade your MediaWiki to 1.25, then yes, you can switch to REL1_25 on release day [13:45:35] MatmaRex, we're started our wiki instance using master-branch (yes, not a good practice). Already filled up. Currently it shows 1.26alpha on version page. What would be the best strategy for migration to some stable branch? Just wait for 1.26 release and upgrade to it? [13:47:30] i don't see any breaking changes on http://www.mediawiki.org/wiki/MediaWiki_1.26, so it could be safe to just upload 1.25 code and run maintenance upgrade scripts? [13:47:55] obviously there is no perfect way, just trying to figure out how to deal with my current situation [13:48:44] MatmaRex: sorry, what I'd meant by "tracking master" is that I maintain my wiki using the Git tracking method, and the wiki is currently pointed at the Master branch of MediaWiki. I haven't done a git pull though since a relase of 1.25alpha (3bb71d9) around 16th of January [13:49:27] MatmaRex: but I've been mandated to keep the wiki at the latest stable release going forward, so when REL1_25 lands, I'm planning to move to that [13:59:01] Nebraskka: 1.26 will be release in about half a year, so there's still plenty of time for something breaking to come up :) [13:59:04] Nebraskka: that's probably a good idea, yes. in the meantime you should probably watch out for security patches for MW 1.25 and apply any [13:59:47] awesome, thanks MatmaRex :) [14:00:03] Nebraskka: you might be also able to switch to 1.25 now. incompatible schema changes are rare. just test it out in non-production environment, if your wiki is mission-critical [14:09:40] wmat: yeah, that sounds sane too [14:09:41] thanks for advice =) [14:09:42] probably what's i'm going to do now [14:09:42] that's what i'm going to do now * [14:34:26] https://en.wikisource.org/w/index.php?title=Page:UK_Traffic_Signs_Manual_-_Chapter_3_Regulatory_Signs._2008_%28Second_Impression_2008%29.pdf/23&action=submit [14:34:39] OK how do I get it to format properly? [14:34:48] A float-right block DOESN'T work [14:48:04] well, it works perfectly fine, it's just that the ambox overrides it [14:52:53] ? [14:53:14] MC8: So it's the ambox that's broken? [14:53:31] https://en.wikisource.org/wiki/Page:UK_Traffic_Signs_Manual_-_Chapter_3_Regulatory_Signs._2008_%28Second_Impression_2008%29.pdf/23 [14:53:45] Here I am trying to add paddign around the block [14:54:11] Again I've overlooked something because when I put the Relevant CSS in the template it ignores it. [14:55:21] When I put the code into a CSS3 test facitly it formats as desired [14:55:34] including the paddign [14:55:36] So [14:55:47] What's causing it NOT to work on Mediawiki? [15:07:55] OK found it [15:08:01] Always a typo [15:08:02] :) [15:08:04] ALWAYS [16:10:23] Hi, wondering if anyone knows about how VisualEditor interacts with tag extensions? Specifically I'm hoping to create a control to display them nicely in VE rather than just as an xml tag that users can easily mess up. It looks like maybe I need to somehow convince Parsoid to make them into an HTML element for me first? [16:12:06] GlennS: hey, you might want to try asking in #mediawiki-visualeditor [16:13:38] ah, thanks [16:13:44] will do [16:19:18] Greetings, James_F [17:18:16] Question, is there an easy way to import a bitbucket wiki (mercurial repo with .md files using markdown) into mediawiki?