On Saturday 27 September 2003 04:43 pm, Scott Paul Robertson wrote:
> did urpmi kernel-source, after downloading, it gives an error message:
> -installing /var/cache/urpmi/rpms/kernel-source-2.4.21-0.25mdk.i586.rpm
> -
> -Installation failed:
> - glibc-devel is needed by kernel-source-2.4.21-0.25mdk
> - ncurses-devel is needed by kernel-source-2.4.21-0.25mdk
> - gcc is needed by kernel-source-2.4.21-0.25mdk
> i try to urpmi these, and it gives a "no package named..." error, manually
> getting the rpms and trying to install fails saying they already are.
> Now what?
You've got several options.
1) You can install the rpms you already manually got using the --nodeps
option, which can lead to complications, but which has also worked out fine
for me. I think this situation might be especially safe since your rpm
database seems to think you've already got these packages. The only question
is whether the version numbers match (one of the eternal rpm headaches, but
usually not that bad). If it were me, since I'm often paranoid, I would rpm
-q the packages that are already there before you rpm -Uvh --nodeps the new
ones just to know which ones were there in case you brake something. (And if
you're trying rpm -i, try rpm -U before you go to --nodeps.
rpm {-U|--upgrade} [install-options] PACKAGE_FILE ...
This upgrades or installs the package currently installed to a newer
version. This is the same as install, except all other version(s) of
the package are removed after the new package is installed.
(from rpm man page)
You also have nothing to lose by rpm -ivh --nodeps kernel-source, since if it
doesn't work the rpm system makes removing them a cinch. (is that how you
spell "cinch?")
2) If you haven't already done this, go to
http://plf.zarb.org/~nanardon/urpmiweb.php
It does an easy urpmi config for you that will help you add lots of cool urpmi
sources so you will almost never have to search for any packages ever again.
Then you could try urpmi'ing the ones you need again, or even the
kernel-source and hope it autodetects the others. As long as you didn't tell
it to delete the kernel-source rpm from /var/cache/urpmi after the failed
install you won't have to redownload it so you can play around trying
different methods all you want without wasting time.
3) There's always rpm --rebuild, which supposedly rebuilds the rpm database.
It's always worth a try, though I can't say it's ever really done much for
me. Barring that, you can try
http://www.informatimago.com/linux/rpm-rebuilddb, which recommends a method
that the author claims does a USEFUL rebuild of the rpm database.
You could also, if you're insane, try ripping out all the rpms down to the
level of the offending ones and starting over from there, but those are
pretty low level ones, and I wouldn't advise that. If nothing else works,
you could use the Mandrake boot cd to try an install repair. Sometimes it
catches things you wouldn't think of.
Good luck.
-James Nickerson
_______________________________________________
newbies mailing list
[EMAIL PROTECTED]
http://phantom.byu.edu/cgi-bin/mailman/listinfo/newbies
