[php-maint] Bug#668252: Bug#668252: /usr/bin/php5: prints out warnings at startup

[Uwe Kleine-König]

On Tue, Apr 10, 2012 at 11:11:55AM +0200, Thijs Kinkhorst wrote:
> > 	$ /usr/bin/php5
> > 	PHP Warning:  PHP Startup: Unable to load dynamic library
> > '/usr/lib/php5/20100525/pdo_sqlite.so' -
> > /usr/lib/php5/20100525/pdo_sqlite.so: cannot open shared object file: No
> > such file or directory in Unknown on line 0
> > 	PHP Warning:  PHP Startup: Unable to load dynamic library
> > '/usr/lib/php5/20100525/sqlite.so' - /usr/lib/php5/20100525/sqlite.so:
> > cannot open shared object file: No such file or directory in Unknown on
> > line 0
> > 	PHP Warning:  PHP Startup: Unable to load dynamic library
> > '/usr/lib/php5/20100525/sqlite3.so' - /usr/lib/php5/20100525/sqlite3.so:
> > cannot open shared object file: No such file or directory in Unknown on
> > line 0
> >
> > This is annoying because /etc/cron.d/php5 generates a mail with the
> > above warnings twice per hour.
> >
> > Ah, I just found the culprit: php5-sqlite (5.3.3-7+squeeze8) was still
> > in the removed state and so provided:
> >
> > 	/etc/php5/conf.d/sqlite.ini
> > 	/etc/php5/conf.d/pdo_sqlite.ini
> > 	/etc/php5/conf.d/sqlite3.ini
> >
> > After purging php5-sqlite the problem seems to be gone.
> 
> I'm not sure I understand your report. Your analysis shows exactly the
> problem, and it's an issue that you can only solve on your local system.
> What do you request from us?
You could make it easier for a user to find the problem. You could show
a dialog during upgrade that these files exist and recommend puring the
package?!

Best regards
Uwe