problem installing glibc-2.3.2-4.80.i686, glibc-common-2.3.2-4.80.8.i386.rpm
Red HatThis forum is for the discussion of Red Hat Linux.
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.
and Firefox 1.0 does run now (amazingly)... but, I cannot upgrade glibc-2.2 to 2.3.2 due to failed dependency on glibc-common, and I cannot install glibc-common. Here's what I get:
Code:
# rpm -ivh glibc-common-2.3.2-4.80.8.i386.rpm --force --nodeps
Preparing... ########################################### [100%]
1:glibc-common ########################################### [100%]
error: unpacking of archive failed on file /usr/lib/locale: cpio: unlink failed - Operation not permitted
I've searched high and low for a similar error to no avail. PLEASE don't tell me to upgrade my os to fedora, I'm not ready to do that yet. Does this have something to do with missing language settings, etc?
why are yiou forcing the install?? if you have a circular dependency then just install them at teh same time, on the same command line. you should have a really good reason for using those RPM options.
Distribution: $ uname -snrvmo Linux martianpackets 3.13.0-29-generic #53-Ubuntu SMP Jun 4 2014 x86_64 GNU/Linux
Posts: 13
Original Poster
Rep:
Quote:
Originally posted by acid_kewpie why are yiou forcing the install?? if you have a circular dependency then just install them at teh same time, on the same command line.
I didn't try that -- it is a circular dependency.
OK dammit: I tried installing them both on the same line as suggested.
Code:
# rpm -Fvh glibc-2.3.2-4.80.8.i686.rpm glibc-common-2.3.2-4.80.8.i386.rpm
error: Failed dependencies:
glibc-common = 2.3.2-4.80.8 is needed by glibc-2.3.2-4.80.8
nada. I tried swapping the order of the file names on the cmd line as well. Whutup with that?
Quote:
you should have a really good reason for using those RPM options.
My reasoning was that if I could force one of the packages, then the other would go. I admit it was risky but what the hell -- I got the RedHat 8 cd sitting right here, if I have to reinstall I can do that. This dumb circular dependency is a kludge.
Distribution: $ uname -snrvmo Linux martianpackets 3.13.0-29-generic #53-Ubuntu SMP Jun 4 2014 x86_64 GNU/Linux
Posts: 13
Original Poster
Rep:
Quote:
Originally posted by perfect_circle well try this:
rpm -Fhv glibc*
I'm pretty sure i did it this way.
That's what I did in the first place. I do have
glibc-debug-2.3.2-4.80.8
installed, so I wonder if this is satisfying the need for glibc-2.3.2-4.80.8? In any case, I haven't encountered any problems yet. I'm going to attempt to install Thunderbird which I believe requires the same glibc version.
Still the question remains:
How do I get glibc-2.3.2-4.80.8 and glibc-common-2.3.2-4.80.8 installed? Again a query of my glibc rpms gives:
I downloaded glibc-common-2.3.2-4.80.8, glibc-devel-2.3.2-4.80.8 and glibc-2.3.2-4.80.8 all separately. Then followed perfect_circle's advice and typed rpm -Fhv glibc* it all went well and upgraded the glibc. Firefox has installed fine afterwards. Thanks everyone!
I have had the same frustrating problem with the circular dependency. Tried just about everything. The solution is what perfect circle has posted.
Do this:
I am on RHEL4 and am facing a similar problem with the glibc and glibc-common circular dependencies. I have glibc-2.3.4-2.25.i686 and glibc-common-2.3.4-2.25.i386 installed, and I want to downgrade to glibc-2.3.2-95.39.i386 and glibc-common-2.3.2-95.39.i386.
When I ran the rpm -Fvh glibc* in my directory that contained the rpms I want to downgrade to, I get this:
warning: glibc-2.3.2-95.39.i386.rpm: V3 DSA signature: NOKEY, key ID db42a60e
Running the rpm -Fvh glibc* command didn't do anything, as I verified by doing an rpm -qa | grep glibc, it still showed the 2.3.4 versions as installed. I also tried listing out the rpms all on the same line but that output the same warning and did nothing.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.