Wikimedia Bugzilla is closed!

Didn't recognize it in what way? Is it just not seeing PHP's mysql support? Is it in fact properly installed?

it didn't see the support.  I assume it is "properly installed" since switching to 1.18 works.  But there maybe be more interesting things going on here.  I installed the php5-sqlite port and it didn't see that one.

<whine>Also, fbsd isn't as user-friendly as linux so it could be that I've done something wrong..</whine>

So.... any directions on how to reproduce, such as the version of FreeBSD and how PHP and MySQL were installed?

(In reply to comment #3)
> So.... any directions on how to reproduce, such as the version of FreeBSD and
> how PHP and MySQL were installed?

MySQL and PHP were installed from cvsup'd ports.  Note I didn't try to install the server, I was running this on a virtual machine on my laptop and was just going to use the mysql server on my laptop for more testing.

$ uname -r
7.3-RELEASE

$ mysql --version
mysql  Ver 14.14 Distrib 5.5.17, for FreeBSD7.3 (amd64) using  5.2

$ php --info | grep mysql
mysql
Client API version => mysqlnd 5.0.8-dev - 20102224 - $Revision: 310735 $
mysql.allow_local_infile => On => On
mysql.allow_persistent => On => On
mysql.connect_timeout => 60 => 60
mysql.default_host => no value => no value
mysql.default_password => no value => no value
mysql.default_port => no value => no value
mysql.default_socket => no value => no value
mysql.default_user => no value => no value
mysql.max_links => Unlimited => Unlimited
mysql.max_persistent => Unlimited => Unlimited
mysql.trace_mode => Off => Off
mysqli
Client API library version => mysqlnd 5.0.8-dev - 20102224 - $Revision: 310735 $
mysqli.allow_local_infile => On => On
mysqli.allow_persistent => On => On
mysqli.default_host => no value => no value
mysqli.default_port => 3306 => 3306
mysqli.default_pw => no value => no value
mysqli.default_socket => no value => no value
mysqli.default_user => no value => no value
mysqli.max_links => Unlimited => Unlimited
mysqli.max_persistent => Unlimited => Unlimited
mysqli.reconnect => Off => Off
mysqlnd
mysqlnd => enabled
Version => mysqlnd 5.0.8-dev - 20102224 - $Revision: 310735 $

$ php -v
PHP 5.3.8 with Suhosin-Patch (cli) (built: Oct 22 2011 14:43:33) 
Copyright (c) 1997-2011 The PHP Group
Zend Engine v2.3.0, Copyright (c) 1998-2011 Zend Technologies

$ svn info
...
URL: http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3
...
Revision: 100516

$ svn info
...
URL: http://svn.wikimedia.org/svnroot/mediawiki/branches/wmf/1.18wmf1
...
Revision: 100522

Errm... That freebsd looks to be older than the legacy version..

8.2 is in production

(In reply to comment #5)
> 8.2 is in production

I hates fbsd... now to figure out an easy way to upgrade. :P

http://www.freebsd.org/releases/8.2R/announce.html

FreeBSD Update

The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[01234]-RELEASE, 8.[01]-RELEASE, 8.2-BETA1, or 8.2-RC[123] can upgrade as follows:

# freebsd-update upgrade -r 8.2-RELEASE
During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.

# freebsd-update install
The system must be rebooted with the newly installed kernel before continuing.

# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new userland components:

# freebsd-update install
At this point, users of systems being upgraded from FreeBSD 7.4-RELEASE or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries.

After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries:

# freebsd-update install
Finally, reboot into 8.2-RELEASE:

# shutdown -r now

Having said that though, they're presumably from ports as the php version it's reasonably up to date..

Still, starting from a proper release isn't a bad idea ;)

I may hates fbsd, but I loves Reedy! tyvm!

You've got php-mysql 5.0.x, but you're running mysql 5.5.x. May be No Big Deal, but looks suspicious.

(In reply to comment #10)
> You've got php-mysql 5.0.x, but you're running mysql 5.5.x. May be No Big Deal,
> but looks suspicious.

Indeed, it shouldn't be an issue (I remember Domas saying so after someone was worried about the phpMyAdmin error in that case), but it is a fairly different version

ok, I've gone through the pain upgrading and the problem has gone away. Pfffft!