how should I upgrade httpd server if no rpm source has the latest package
Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
how should I upgrade httpd server if no rpm source has the latest package
Hi,
As we all know, there's always bug for any software(include httpd). For example, to fix bug CVE-2011-3348, we should install/upgrade httpd to version 2.2.21.
Now on my server, httpd version is 2.2.15. When using yum list|grep httpd, I can see this 2.2.15 is now the latest version, which means yum update httpd won't upgrade httpd.
What should I do about this? Should I download the source package(.tar.gz one) and transform it into a rpm package and then use rpm -Uvh to upgrade it?(And how to transform it?)
Thanks very much!
PS:
I know there's a software management system called spacewalk which can install one update to several servers at one time, I'm thinking whether we should transform the source package to rpm one in order to take the advantage of spacewalk.
If you know what you are doing, or are willing to take the time to learn then you can download the source and configure / compile whatever version of apache you want. There are plenty of how-to's around, Google Is Your Friend!
If you're not confident about configuring / compiling packages then you might want to consider waiting until your upstream distro releases an RPM.
If you know what you are doing, or are willing to take the time to learn then you can download the source and configure / compile whatever version of apache you want. There are plenty of how-to's around, Google Is Your Friend!
If you're not confident about configuring / compiling packages then you might want to consider waiting until your upstream distro releases an RPM.
Thanks.
I know we can just download/compile httpd etc using their source packages, but I think rpm one can be more convenient for software management.
Maybe everything has it's pros and cons.
For example, to fix bug CVE-2011-3348, we should install/upgrade httpd to version 2.2.21. Now on my server, httpd version is 2.2.15. When using yum list|grep httpd, I can see this 2.2.15 is now the latest version, which means yum update httpd won't upgrade httpd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.