On Sat, Jun 07, 2003 at 02:26:49PM -0500, David Summers wrote:
> On Sat, 7 Jun 2003, Max Bowsher wrote:
> > Maury Hammel wrote:
> > > Hello all:
> > >
> > > I'm still trying to get all the pieces of Subversion installed on Red Hat
> > 9
> > > using the RPMs. I have managed to get all of the packages installed
> > except for
> > > httpd-2.0.45-0.2.i386.rpm and mod_ssl-2.0.45-0.2.i386.rpm. Both report
> > failed
> > > dependencies:
> > >
> > > # rpm -Uh httpd-2.0.45-0.2.i386.rpm
> > > error: Failed dependencies:
> > > httpd-mmn = 20020628 is needed by (installed) mod_perl-1.99_07-5
> > > httpd-mmn = 20020628 is needed by (installed) mod_python-3.0.1-3
> > > httpd-mmn = 20020628 is needed by (installed) php-4.2.2-17
> > > httpd-mmn = 20020628 is needed by (installed) mod_ssl-2.0.40-21.3
> > > libapr.so.0 is needed by (installed) mod_perl-1.99_07-5
> > > libaprutil.so.0 is needed by (installed) mod_perl-1.99_07-5
> > > # rpm -ivh mod_ssl-2.0.45-0.2.i386.rpm
> > > error: Failed dependencies:
> > > httpd-mmn = 20021106 is needed by mod_ssl-2.0.45-0.2
> > >
> > > I'm not sure why httpd-mmn is not found, because it appears to be a part
> > of the
> > > previous versions of httpd I've installed, and the two libapr* files are
> > sitting
> > > in /usr/lib, so I'm at a loss.
> > >
> > > Can someone point me in the right direction to get these things installed?
> >
> > The failiures from your "rpm -U httpd..." command aren't missing items.
> > RPM is telling you that your currently installed mod_perl, mod_python, php
> > and mod_ssl packages are bound to a particular version of apache. Either get
> > compatible versions of mod_perl, mod_python, php and mod_ssl from where you
> > got your httpd-2.0.45 rpm, or uninstall those packages first.
>
> Uh, yeah...what he said. :-)
>
> I haven't tried recompiling all the packages that depend on httpd but
> theoretically all you have to do is rebuild them so they depend on
> httpd-2.0.45.
That should be the case. The stuff Maury is having problems with are built
against 2.0.40, which should be source-compat with the new 2.0.45.
If you get packages built against 2.0.44 or later, then you're totally set.
From there on, Apache httpd is binary compatible. If some RPM is stupid and
won't let you install a newer Apache because the dump RPM has a dep against,
say, 2.0.45 only, then you can just force the installation of the new httpd.
It won't break the bad RPM.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jun 8 00:32:38 2003