New apache 1.3.28 for SuSE 8.2 and mod_php4 problem
Hi, There is a new rpm package for Apache 1.3.28 in suse-people apt-get repository. The problem here is it requires to uninstall mod-php4 package to upgrade apache. I'm afraid it will disable all embebed php4 scripting. Do you know whether this package is now included into mod-php-core? Is it a bug in packaging? Thanks. Guillermo. -- Guillermo Ballester Valor registered linux user #117181 gbv@oxixares.com Ogijares, Granada SPAIN
On Sat, Aug 09, 2003 at 10:48:05AM +0200, Guillermo Ballester Valor wrote:
There is a new rpm package for Apache 1.3.28 in suse-people apt-get repository.
The problem here is it requires to uninstall mod-php4 package to upgrade apache. I'm afraid it will disable all embebed php4 scripting. Do you know whether this package is now included into mod-php-core? Is it a bug in packaging?
You have two options: - don't install the 1.3.28 package, I'm nearly 100% sure that you do not need it. - install 1.3.28 and ignore/override the dependency of mod_php4 on 1.3.27. I'm nearly 100% sure that they'll work together. Peter
Hi, On Saturday 09 August 2003 17:43, poeml@cmdline.net wrote:
You have two options: - don't install the 1.3.28 package, I'm nearly 100% sure that you do not need it.
This is the one I picked at the moment, I suposse SuSE people will correct this unspected dependency. Then I will upgrade, there few small bugs fixed in new version.
- install 1.3.28 and ignore/override the dependency of mod_php4 on 1.3.27. I'm nearly 100% sure that they'll work together.
Peter
Guillermo -- Guillermo Ballester Valor registered linux user #117181 gbv@oxixares.com Ogijares, Granada SPAIN
On Sat, Aug 09, 2003 at 06:02:24PM +0200, Guillermo Ballester Valor wrote:
On Saturday 09 August 2003 17:43, poeml@cmdline.net wrote:
You have two options: - don't install the 1.3.28 package, I'm nearly 100% sure that you do not need it.
This is the one I picked at the moment, I suposse SuSE people will correct this unspected dependency. Then I will upgrade, there few small bugs fixed in new version.
It is a misunderstanding that this is something that calls for correction. The packages are not supported, and provided as is (mainly for testing purposes). If you are truly concerned about a particular bug that might have been fixed in 1.3.28, just go ahead and use the package. You should not have any problem with mod_php4. If you do find a problem, please let me know. Peter
On Saturday 09 August 2003 21:59, poeml@cmdline.net wrote:
It is a misunderstanding that this is something that calls for correction. The packages are not supported, and provided as is (mainly for testing purposes).
If you are truly concerned about a particular bug that might have been fixed in 1.3.28, just go ahead and use the package. You should not have any problem with mod_php4. If you do find a problem, please let me know.
Sorry if somebody has missinterpreted my words. Is my fault and my poor english :(. I know that these packages are unsupported, I've also built some rpm packages to be build as is. My aim when writing to the list is because I thought there was something wrong in the dependencies easy to fix, and just I wanted to point at this problem. Guillermo -- Guillermo Ballester Valor registered linux user #117181 gbv@oxixares.com Ogijares, Granada SPAIN
On Sun, Aug 10, 2003 at 12:09:19AM +0200, Guillermo Ballester Valor wrote:
[...] My aim when writing to the list is because I thought there was something wrong in the dependencies easy to fix, and just I wanted to point at this problem.
Then I was really misunderstanding you. I thought you were waiting for a fix. Thanks for pointing it out! To explain the matter, the package dependency on the apache package that exists in the mod_php4 package is too picky, it depends on the major module magic number as well as on the minor one. A dependency on the major number should actually suffice, but this is an attemt to play safe. PHP is a very complex module, and normally apache is not updated to a higher version within a given distribution. For apache2, I have made the dependency a bit looser, because apache2 has an inbuilt sanity check for loading of modules that do not match the major module magic number anyway. That's why I said you _can_ use the package. I beleive it's not worth the trouble rebuilding the PHP (and others) packages, just to have packages that install 100% cleanly. I basically know that it works. I can promise you that _if_ I had doubts about it I _would_ rebuild the packages, see if it helps, and investigate further. Peter
On Sunday 10 August 2003 23:18, poeml@cmdline.net wrote:
On Sun, Aug 10, 2003 at 12:09:19AM +0200, Guillermo Ballester Valor wrote:
[...] My aim when writing to the list is because I thought there was something wrong in the dependencies easy to fix, and just I wanted to point at this problem.
Then I was really misunderstanding you. I thought you were waiting for a fix. Thanks for pointing it out!
To explain the matter, the package dependency on the apache package that exists in the mod_php4 package is too picky, it depends on the major module magic number as well as on the minor one. A dependency on the major number should actually suffice, but this is an attemt to play safe. PHP is a very complex module, and normally apache is not updated to a higher version within a given distribution. For apache2, I have made the dependency a bit looser, because apache2 has an inbuilt sanity check for loading of modules that do not match the major module magic number anyway.
I've installed the src.rpms for apache and mod_php4 this morning. Then I read the specs files. They are really complicated. In a non production PC I installed apache-1.3.28 with apt-get and it worked, but at the cost of losing mod_php4. I couldn't install mod_php4 in anyway I tried, the magic number module dependency appeared .
That's why I said you _can_ use the package. I beleive it's not worth the trouble rebuilding the PHP (and others) packages, just to have packages that install 100% cleanly. I basically know that it works. I can promise you that _if_ I had doubts about it I _would_ rebuild the packages, see if it helps, and investigate further.
I'm pretty sure of this ;-). Regards Guillermo -- Guillermo Ballester Valor registered linux user #117181 gbv@oxixares.com Ogijares, Granada SPAIN
On Sat, Aug 09, 2003 at 06:02:24PM +0200, Guillermo Ballester Valor wrote:
On Saturday 09 August 2003 17:43, poeml@cmdline.net wrote:
You have two options: - don't install the 1.3.28 package, I'm nearly 100% sure that you do not need it.
This is the one I picked at the moment, I suposse SuSE people will correct this unspected dependency. Then I will upgrade, there few small bugs fixed in new version.
I rebuilt the package with more pleasing dependencies. BTW, 1.3.28 introduced a bug (zombie processes when using CGI+suexec), but it is fixed in the rebuilt package. Peter
participants (2)
-
Guillermo Ballester Valor -
poeml＠cmdline.net