|
Home > Archive > Debian Developers > August 2004 > php4 requires to reinstall all php extensions (mass bugreport)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
php4 requires to reinstall all php extensions (mass bugreport)
|
|
| Artur R. Czechowski 2004-08-20, 2:52 am |
| Hello,
I would like to submit a bugreport to all php4 extensions.
Latest php4 (4:4.3.8-5) has introduced new SAPI: cli. All previously
installed php extensions are not added to /etc/php4/cli/php.ini.
What should be a proper solution for above problem? Well prepared
config/postinst scripts could detect new SAPI automagically. But is still
requires extensions to be reinstalled. I suggest a simple sollution: just
bump up version number for all packages containing php extensions to hint
users to update those packages.
This problem affects only sarge and sid users - php4 had changed a lot
since woody (zendapi,phpapi) and all php4 extensions shall be upgraded to
meet dependency requirements.
Cheers
Artur
--
Dzisiaj odbywał się tylko pojedynek Pigułki z naleśnikiem, którego upolowała
i próbowała zabić; przez długi czas wydawało sie, że naleśnikwygra, ale
w końcu Pigułka go zamordowała i zjadła. Wy nie wiecie, jak taki naleśnik
potrafi sie z nienacka rzucić kotowi do gardła ;) /Gadzinka/
| |
| Jeroen van Wolffelaar 2004-08-20, 7:50 am |
| On Fri, Aug 20, 2004 at 09:41:15AM +0200, Artur R. Czechowski wrote:
> Hello,
> I would like to submit a bugreport to all php4 extensions.
>
> Latest php4 (4:4.3.8-5) has introduced new SAPI: cli. All previously
> installed php extensions are not added to /etc/php4/cli/php.ini.
>=20
> What should be a proper solution for above problem? Well prepared
> config/postinst scripts could detect new SAPI automagically. But is still
> requires extensions to be reinstalled. I suggest a simple sollution: just
> bump up version number for all packages containing php extensions to hint
> users to update those packages.
Well, bumping version number doesn't help. Extensions only change
php.inis on upgrade and dpkg-reconfigure, and php4-cli (or any other
newly installed SAPI) doesn't know how to trigger reconfigures of all
php extensions.
Adam Conrad, php maintainer, says this is a known bug, it's a bug in the
php4 package and no the extensions (a proper way to deal with this
should be designed), and it won't be fixed before sarge is released.
By the way, some extensions simply don't support the CLI SAPI yet at
all (php4-interbase for example), which is IMHO something that should be
fixed.
> This problem affects only sarge and sid users - php4 had changed a lot
> since woody (zendapi,phpapi) and all php4 extensions shall be upgraded to
> meet dependency requirements.
This problem _also_ affects woody -> sarge upgrades, upgrading
extensions simply doesn't solve the problem.
If a mass bug filing highly related to a certain package (php4 in this
case), cc'ing those maintainers is usually a good idea.
--Jeroen
--=20
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl
| |
| Artur R. Czechowski 2004-08-22, 6:11 pm |
| On Fri, Aug 20, 2004 at 10:35:49AM +0200, Jeroen van Wolffelaar wrote:
> Well, bumping version number doesn't help.
Erm...
> Extensions only change php.inis on upgrade and dpkg-reconfigure,
.... you just say that bumping version number _does_ help.
> and php4-cli (or any other newly installed SAPI) doesn't know how to
> trigger reconfigures of all php extensions.
But extensions know (or could know) it itselfs.
There could be a magic to detect SAPI's, like:
for SAPI in `find /etc/php4/ -type d -maxdepth 1 -mindepth 1 | sed -e's#.*/##'`
or hardcoded values.
In first case uploading package to archive with increased debian revision
would be sufficient. In the second one maintainer should add cli as a valid
SAPI in config/postinst script.
> Adam Conrad, php maintainer, says this is a known bug, it's a bug in the
> php4 package and no the extensions (a proper way to deal with this
> should be designed), and it won't be fixed before sarge is released.
Well, I think that Adam is too selfcritical  I wouldn't call it a bug.
There is rather a lack of policy and tools to maintain dependencies between
webservers, php and php extensions. It just requires some additional work
from extensions' maintainers. Like in this case.
I agree that the lack of policy and tools is not a sufficient reason to hold
a sarge release, but the case I mentioned in my initial mail shall be
considered as one.
> By the way, some extensions simply don't support the CLI SAPI yet at
> all (php4-interbase for example), which is IMHO something that should be
> fixed.
I agree.
> This problem _also_ affects woody -> sarge upgrades, upgrading
> extensions simply doesn't solve the problem.
I cannot agree. Due to dependencies order of actions during update will look
like this:
php4 unpacked (creating /etc/php4/apache dir)
php4-cli unpacked (creating /etc/php4/cli dir)
php-extensions unpacked
[...]
php4 set
php4-cli set
php-extensions set (using existing directories in /etc/php4 to detect SAPIs)
What's wrong with this scheme?
> If a mass bug filing highly related to a certain package (php4 in this
> case), cc'ing those maintainers is usually a good idea.
I'll drop the note to them and ask to focus on this thread in private mail.
Cheers
Artur
--
http://www.ralphm.net/world
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Artur R. Czechowski 2004-08-22, 6:11 pm |
| On Fri, Aug 20, 2004 at 10:35:49AM +0200, Jeroen van Wolffelaar wrote:
> If a mass bug filing highly related to a certain package (php4 in this
> case), cc'ing those maintainers is usually a good idea.
Maintainers of following packages has been informed by email:
- php-imlib
- php4-dbase
- php4-gd2
- php4-idn
- php4-imagick
- php4-interbase
- php4-mcrypt
- php4-pgsql
- php4-rrdtool
- php4-spplus
- php4-sqlite
- php4-tclink
I expect them joining to the thread.
Cheers
Artur
--
"Znamy siebie na tyle, na ile nas wypróbowano"
/Gustaw Herling Grudziński "Inny świat"/
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Adam Conrad 2004-08-22, 6:11 pm |
| Artur R. Czechowski wrote:
>
> I suggest a simple sollution: just bump up version number for all
> packages containing php extensions to hint users to update those
packages.
This won't work. If you intall an extension, then a new SAPI, the new
SAPI won't get detected, as the extension has already been configured.
Conversely, if you install a new SAPI, then upgrade your extensions,
because there's already a php.ini installed for that SAPI, the debconf
value will get set to "don't add", and it won't act.
The only way to solve this is either to make the SAPIs smarter (won't
happen before Sarge releases), or force everyone to run dpkg-reconfigure
on all their extensions, making them see all the questions again. Also,
not going to happen.
Your "bump version numbers" solution achieves nothing. Please, please,
PLEASE don't suggest this to maintainers, it'll just produce more
package churn, with 0 actual useful effect.
.... Adam
| |
| Artur R. Czechowski 2004-08-22, 6:11 pm |
| Hello,
Adam and I discussed this case more on #debian-devel.
We agreed that bumping version number could or couldn't work - it depends
on user's configuration. Moreover, in most cases it wont work. So this
sollution should be considered as useless.
There is workaround for this problem. After upgrading php, users should run
dpkg-reconfigure for all installed php extensions.
EOT
Cheers
Artur
--
Ciągnie się jak backup nad ranem
/z pamiętnika administratora/
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Martin Schulze 2004-08-24, 7:07 pm |
| Artur R. Czechowski wrote:
> Hello,
> Adam and I discussed this case more on #debian-devel.
>
> We agreed that bumping version number could or couldn't work - it depends
> on user's configuration. Moreover, in most cases it wont work. So this
> sollution should be considered as useless.
>
> There is workaround for this problem. After upgrading php, users should run
> dpkg-reconfigure for all installed php extensions.
Could you write a verbose text, including all affected packages by name,
for the release-notes for sarge? This problem may be worth to be included
in that document.
I don't know off-hand if that document already exists yet (maybe in the
d-i svn space) but it will probably be created at some stage, and this
may be worth to get added.
Regards,
Joey
--
Beware of bugs in the above code; I have only proved it correct,
not tried it. -- Donald E. Knuth
Please always Cc to me when replying to me on the lists.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
| |
| Martin Schulze 2004-08-24, 7:07 pm |
| Artur R. Czechowski wrote:
> Hello,
> I would like to submit a bugreport to all php4 extensions.
>
> Latest php4 (4:4.3.8-5) has introduced new SAPI: cli. All previously
> installed php extensions are not added to /etc/php4/cli/php.ini.
Just to get this right, the problem only affects php4-cli (the commandline
interface for php4) and results in the extensions not being available off
hand for it.
The problem does not affect the php4 and php4-cgi packages.
Regards,
Joey
--
Beware of bugs in the above code; I have only proved it correct,
not tried it. -- Donald E. Knuth
Please always Cc to me when replying to me on the lists.
--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
|
|
|
|
|