Re: installing mod_ssl on Fedora Core 4 -- complaining about httpd = 2.0.54-10.4

bennett@xxxxxxxxxxxxx writes:


This is a virtual private server hosted by a hosting company, and
SWSoft.com makes virtualization software, so I assume for some reason
they put their binaries on the virtual private server images that
their software creates. I have no idea why they would do this, since

Your first step, then, would be to ask your hosting company if they provide the Apache modules that have been built for the Apache frankenbuild that they plopped on your box.

I would assume that for a virtual host, you can put the same binaries
on it that you would put on normal hardware, so couldn't they have
just used the standard httpd binaries, which would have enabled me to
install mod_ssl with no problem?...

Anyway, I tried what you suggested and got this error:
[root@h122908 ~]# rpm -e httpd httpd-manual
error: Failed dependencies:
httpd-mmn = 20020903 is needed by (installed)
php-5.0.4-10.5.1.swsoft.i386

So you have a frankenbuild of php as well. Congratulations.

httpd-mmn = 20020903 is needed by (installed)
mod_perl-2.0.1-1.fc4.i386
httpd is needed by (installed) hspc-
wwwroot-1.0-18.fc4.swsoft.noarch

Another frankenbuild package. hspc-wwwroot does not ring a bell, that does not look like a Fedora package.

httpd = 2.0.54 is needed by (installed) httpd-
devel-2.0.54-10.4.1.swsoft.i386

You really have a legitimate beef with your hosting company. Rather than giving you a stock Fedora server to play with, they stuff with some frankenpackages. In your specific case, I'd advise you to contact your hosting company, explain to them the situation, and ask them where you can get the Apache modules you need for your own purposes.

Of course, nuking this entire pile of *** is always an option, and in your case that's what I would do. But, I'm probably more comfortable with handling this kind of bull***, and I can fix my own messes. I do this for a living.

So the first thing I would do is investigate what the fsck is this "hspc-wwwroot" deal is all about. My educated guess is that this package is a skeleton that create some directory structure for you. Nothing that can't be replaced, by hand. I'd use "rpm -q -l -v hspc-wwwroot", "rpm -q --scripts hspc-wwwroot", and perhaps some other commands, to understand what this bloody thing does, because that's the first thing to toss out the window with rpm -e.

Then, once that package is nuked from high orbit, I'd compile a list of all the little packages that make up that php frankenpackage, then I'd run "rpm -e httpd httpd-manual httpd-devel php php-/foo/" once (including all php frankensubpackages), just to see what rpm would complain about. I'd want to make sure that no other frankenpackages pop out from under some rock, somewhere. If more "mod*" frankenpackages pop up that _explicitly_ demand a dependency on the "swsoft*" version, they get added to the list. I'll ignore any mod* packages that do not carry a "swsoft" version themselves, and that do not state a dependency on a "swsoft" version of php or httpd, but just a generic version of "httpd", or "php".

Once I have an accurate handle on the scope of the problem, they all go with "rpm -e -f". I'll be reinstalling the Fedora-borg-standard packages of httpd and php, and any mod packages, so I'm not going to worry about stuff that depends on it.

After they're gone, I'd just run "yum install", which should now pull in the standard Fedora version of these packages.

In general, if you're stuck with a server with weird versions of
certain binaries, how would you go about finding binaries compatible
with those to install on top of them, as in this case?

You go back where those weird versions come from, and find the correct packages to install.

What I don't understand is why rpm doesn't just come pre-configured to
pull all new requested binaries from a certain location, so that on a

It does. That's what yum does. Your hosting company should have:

1) Already installed yum for you

2) Configured yum to pull packages from whereever they need to be pulled from, in order to install the compatible software

Actually, your hosting company should've gave you a standard Fedora install, instead of some custom-built stuff. Find out from them exactly why they did that. If they tell you that standard Apache or PHP won't work on their virtual machine, for some reason, and that's why they stuff this non-standard software on it, go somewhere else. You don't need to put up with this nonsense.


Attachment: pgpMXFoPxmdjC.pgp
Description: PGP signature