 |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | About BLU |
|
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | About BLU |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sun, 10 Feb 2002, Ken Gosier wrote:
> However, if I try to install any one of them, it reports that I already
> have to have one of the others. For instance, trying glibc-common
>
> Similarly for the other two. Question: How do I get the newer rpm's
> installed? The obvious thing to do would be to uninstall all 3 earlier
> rpm's, then install the new 3. But, my guess is:
On Sun, 10 Feb 2002, Brian J. Conway wrote:
> How about 'rpm -Uvh glibc*2.2.4*'?
On Sun, 10 Feb 2002, Mark J. Dulcey wrote:
> Use the --nodeps option to force in the first one in the chain
On Sun, 10 Feb 2002, Ken Gosier wrote:
> Many thanks, I now have glibc-2.2.4 going.
For future reference, I feel (and I'm pretty sure Red Hat agrees) that
the method Brian suggested is "The Right Way." The rpm utility will
accept a list of packages to be installed and resolve dependencies among
them. It might be a little over-cautious, but I prefer to use as few of
the override flags as possible with rpm.
That being said, I don't think there was much of a difference in this
case. The only time it would really become a problem is if you forced in
a conflicting package that broke rpm.
- --
-Matt
We are all so much together and yet we are all dying of loneliness.
-- A. Schweitzer
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE8Z+5lc8/WFSz+GKMRAq3fAKCrv4m2iNMftGDItFr/Hght4O0k6wCdGHAN
dAAkD3Mko4S+Kb8Q9D1XYrY=
=vcPb
-----END PGP SIGNATURE-----
