wiki wiki http://www.mediawiki.org/wiki/Download
Created attachment 93988 [details, diff] mediawiki-1.7.1-jobkeyindex-sizeexceeded.patch http://bugzilla.wikimedia.org/show_bug.cgi?id=4445#c7 patch to fix problem
Created attachment 93989 [details, diff] mediawiki.ebuild.diff maintenance/oracle/archive doesn't exist so no need to install it. need epatch for attachment 93988 [details, diff] obviously.
<1.7.1 doesn't seem vulnerable in gentoo to this vulnerability http://sourceforge.net/project/shownotes.php?group_id=34373&release_id=430704 and the $GLOBALS overwrite vulnerability reference http://www.hardened-php.net/advisory_202005.79.html (PHP4 <= 4.4.0 && PHP5 <= 5.0.5)
Ill try to look at this as soon as my system reboots without major glitches. (gcc-4.1.1 and xorg-7.0)
It seems that all of the oracle support is bit rotten and not supported so we could remove all the oracle directory. Was the patch for 1.7.0 or 1.7.1 ?
(In reply to comment #5) > It seems that all of the oracle support is bit rotten and not supported so we > could remove all the oracle directory. Sure > Was the patch for 1.7.0 or 1.7.1 ? 1.7.1
Can you make sure you are using >=mysql-4.1.21 and try the current ebuild for 1.7.1 without a patch for the long key. <mysql-4.1.18 had utf8 conversion troubles and before 4.1.21 had other problems that might be annoying on mediawiki.
(In reply to comment #7) > Can you make sure you are using >=mysql-4.1.21 and try the current ebuild for > 1.7.1 without a patch for the long key. <mysql-4.1.18 had utf8 conversion > troubles and before 4.1.21 had other problems that might be annoying on > mediawiki. I was using mysql-4.1.21 when I first attempted to install mediawiki-1.7.1 (based of emerge.log) and it failed. Redoing it to confirm: spider mediawiki # cp mediawiki-1.6.7.ebuild mediawiki-1.7.1.ebuild spider mediawiki # ebuild mediawiki-1.7.1.ebuild digest >>> Downloading http://mesh.dl.sourceforge.net/sourceforge/wikipedia/mediawiki-1.7.1.tar.gz -..... spider mediawiki # ebuild mediawiki-1.7.1.ebuild merge Disabling noauto in features... merge disables it. (qmerge doesn't) >>> checking ebuild checksums ;-) >>> checking auxfile checksums ;-) >>> checking miscfile checksums ;-) >>> checking mediawiki-1.7.1.tar.gz ;-) * * Using dev-lang/php-5.1.4-r6 ..... >>> Merging www-apps/mediawiki-1.7.1 to / .... .... >>> Safely unmerging already-installed instance... * Removing mediawiki-1.7.1 from /var/www/www.wiki.bob/htdocs * Installed by root on 2006-08-11 21:40:27 spider mediawiki # webapp-config -I -h www.makethemove.bob -d mediawiki mediawiki 1.7.1 * Creating required directories * Linking in required files * This can take several minutes for larger apps * mediawiki-1.7.1 does not install any files from /usr/share/webapps/mediawiki/1.7.1/hostroot/; skipping * Files and directories installed spider mediawiki # cd /var/www/www.makethemove.bob/htdocs/mediawiki/ spider mediawiki # chmod a+w config # mysql --version mysql Ver 14.7 Distrib 4.1.21, for pc-linux-gnu (i686) using readline 5.1 Following install on http://www.makethemove.bob/mediawiki/config generates: Environment checked. You can install MediaWiki. Generating configuration file... Database type: MySQL Loading class: DatabaseMysql Attempting to connect to database server as root...success. Connected to 4.1.21-log Created database wikidb-mtm Creating tables... using MySQL 4 table defs...Query "CREATE TABLE `job` ( job_id int(9) unsigned NOT NULL auto_increment, job_cmd varchar(255) NOT NULL default '', job_namespace int NOT NULL, job_title varchar(255) binary NOT NULL, job_params blob NOT NULL default '', PRIMARY KEY job_id (job_id), KEY (job_cmd, job_namespace, job_title) ) TYPE=InnoDB " failed with error code "Specified key was too long; max key length is 1024 bytes (localhost)". after setting appropriate information -> ^^ failed message. Patch is required. Later versions of mysql have the key limit of 1024 bytes where the earlier versions don't.
OK I feel a bit more comfortable to define the lenght properly than doing it twice, also I noticed that the table for mysql4 and mysql5 are in different files. I have create 2 patches for each cases. Correct me if I am smoking php stuff. If anyone is kind enough to try this new version of mediawiki, 1.7.1, I'd be very pleased. I am not very confident to mark any mediawiki as stable before the minor reach .4 or .5 (experience). Trapni said so in some mail too. I would like to have 1.6.x marked as stable before any 1.7.x If the demand is here, I can mark it testing only if upstream doesn't find any new security bugs during the next 30days. Then I'll mark testing and wait 30 days, then mark stable only if 1.6.x is stable and security issues are OK. The reason behind this is that the documentation is easier to follow during upgrades of 1.5.x -> 1.6.x than 1.5.x -> 1.7.x. Again previous bad experiences I try to avoid to other users. I know gentoo users who need mediawiki + php4, this mean 1.6.x. Ill try to keep Gentoo up to speed after this.
(In reply to comment #9) > OK I feel a bit more comfortable to define the lenght properly than doing it > twice, I'm sure you going to come across people with installation troubles. Hopefully upstream does a patch you can copy off. > also I noticed that the table for mysql4 and mysql5 are in different > files. > I have create 2 patches for each cases. Correct me if I am smoking php > stuff. http://bugzilla.wikimedia.org/show_bug.cgi?id=1322#c19 maybe one more spot for upgrades - I haven't check to see if it applies to 1.7.1 Your doing well Philippe - keeping up with webapps must be really hard.
It worked for me, If I don't hear any complains Ill close this bug tomorrow.
Done many tests, and it works fine for me.
