yep, i saw the same thing, this happened yesterday about 5pm with a very big changeset that affected the 3rdparty/ directory.
On Sat, May 12, 2012 at 11:03 AM, Alain Bourgeois <[email protected]> wrote: > Here are recent messages on clean install with sqlite : > > “ > Strict Standards: Declaration of MDB2_Driver_sqlite3::_doQuery() should be > compatible with that of MDB2_Driver_Common::_doQuery() in > /shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 909 > > Strict Standards: Declaration of MDB2_Driver_sqlite3::prepare() should be > compatible with that of MDB2_Driver_Common::prepare() in > /shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 909 > > Strict Standards: Declaration of MDB2_Result_sqlite3::fetchRow() should be > compatible with that of MDB2_Result_Common::fetchRow() in > /shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 1035 > Here is a recent problem arrizing on clean install on qglite3 : > “ > Strict Standards: Declaration of MDB2_Statement_sqlite3::execute() should be > compatible with that of MDB2_Statement_Common::execute() in > /shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 1334 > > Strict Standards: Declaration of MDB2_Statement_sqlite3::_execute() should > be compatible with that of MDB2_Statement_Common::_execute() in > /shares/Public/WWW/WWW-pub/master/lib/MDB2/Driver/sqlite3.php on line 1334 > > Strict Standards: Non-static method PEAR::isError() should not be called > statically in /shares/Public/WWW/WWW-pub/master/3rdparty/MDB2.php on line > 381 > > ...... > “ > Alain > > _______________________________________________ > Owncloud mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/owncloud > _______________________________________________ Owncloud mailing list [email protected] https://mail.kde.org/mailman/listinfo/owncloud
