Results 1 to 4 of 4
Haiii alll, I had gone through a problem in upgrading of apache server. currently i had httpd-2.0.54 and i want it to upgrade to httpd-2.2.0 i think its latest version. ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 05-02-2006 #1
- Join Date
- Mar 2006
Regarding upgradation of apache web server
Haiii alll, I had gone through a problem in upgrading of apache server. currently i had httpd-2.0.54 and i want it to upgrade to httpd-2.2.0 i think its latest version. but when i was upgrading its give huge dependency problems when i was to installl dependencies then its asking for some more dependencies to install it and if i try to install it then its giving error glibc < 2.4 conflicts with glibc-common-2.4-4.i386 when i try to install glibc its asking for glibc-common and when i try for this its giving the above error. If i install with out depending on dependencies using --nodep, i think later it will cause problem.
Can any one help me please.
- 05-02-2006 #2
I dont recommend using the --nodeps option in rpm, you are right in saying that you'll store up problems for yourself later on.
If you are desperate to upgrade, then you'll probably want to remove all the dependent packages and install the latest version of each from source, then install the apache 2.2.x source and build it yourself. It's not a small job, you must have a really pressing reason for using apache 2.2.
- 05-03-2006 #3
- Join Date
- Mar 2006
Thanks for your reply Rox off,
I am planning to upgrade just to keep my server full secure, I think more patches will be added to apache 2.2.x compare to apache 2.0.54. And I think we should keep our server update regularly for all the applications using, So what do u recommend me whether to keep apache 2.0.54 or to upgrade it to 2.2.x. I think even if i upgrade I dont loose my older data in it, can u help whether there is any option of deleting all dependencies of apache quickly.
- 05-03-2006 #4
If you're using a binary-packaged distro, then the distro makers will wrap any security fixes into their updates as vulnerabilities are discovered. Personally, I'd stick with whatever the distro uses, unless I had a particular need for some feature or other that is only available in the latest releases. There is absolutely nothing wrong with Apache 2.0.54, and if security holes are found and patched, you'll get the updates through the regular channels.