[Bug 657604] New: Major mix-up with gcc33 rpms
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c0 Summary: Major mix-up with gcc33 rpms Classification: openSUSE Product: openSUSE 11.3 Version: Final Platform: x86-64 OS/Version: openSUSE 11.3 Status: NEW Severity: Critical Priority: P5 - None Component: Development AssignedTo: pth@novell.com ReportedBy: Joseph.Comfort@asu.edu QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12 Today I updated my rpms through Yast. In addition to the usual repositories, I include the Build Service for gcc. I have both gcc45 and gcc33 installed, and there were updates for these. After the updates, Yast would not restart. There were complaints that GCC_4.2.0 was not found. I rebooted the system, hoping to clear problems. It would not go to level 5, with the same complaint for some process. What I find: The failure relates to /lib64/libgcc_s.so.1 (probably also /lib/libgcc_s.so.1). An rpm -q --whatprovides shows that this is provided by BOTH the libgcc45 and libgcc33 rpms (and 32-bit versions), BUT with very different file sizes. The installed versions are dated Nov 29 and are from libgcc33, not ...45. Checking my other not-updated machines, only the libgcc45 rpm is installed. So the update added a conflicting rpm. On another machine, I downloaded the libgcc45 rpms from the Build Service, and transferred them to my first computer. I wanted to remove the libgcc33 rpm and reinstall the libgcc45 one. However, I could not remove libgcc33 because it is now needed by gcc33-3.3.3-33.6.x86_64. I am basically dead in the water, with project I need to work on over the weekend! Even if the rpms are fixed up, I don't know how I would install them because neither Yast nor zypper will run. It is a serious problem. Reproducible: Always Steps to Reproduce: 1. Have gcc45 and gcc33 installed 2. Setup the repository to the Build Service devel:gcc. 3. Run Yast2, update rpms if updates are available. Actual Results: Yast and zypper are dead. Reboot can not reach level 5. Expected Results: No problems. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c1 --- Comment #1 from Joseph Comfort <Joseph.Comfort@asu.edu> 2010-12-04 19:59:53 UTC --- Update: I was able to restore my system by forcing the reinstallation of libgcc45. I first saved the libgcc_s.so.1 files. They should go somewhere, but I don't know where. Also, I won't update my other computers until this bug is resolved and I am sure there will not be any conflicts. I need gcc33 for g77. I tested a simple case, and it seems to work after the installation above. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c Philipp Thomas <pth@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pth@novell.com AssignedTo|pth@novell.com |rguenther@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
rpm -qp --provides libgcc45-4.5.1_20101116-85.1.x86_64.rpm
rpm -qp --conflicts libgcc45-4.5.1_20101116-85.1.x86_64.rpm
rpm -qp --provides /work/CDs/all/full-head-x86_64/suse/x86_64/libgcc33.rpm
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c2 Richard Guenther <rguenther@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mls@novell.com --- Comment #2 from Richard Guenther <rguenther@novell.com> 2010-12-06 13:20:23 UTC --- Thanks for the report. This means that the suggested approach of using Provides and Conflicts does not work. CCing mls who suggested that. libgcc1 = 4.5.1_20101116-85.1 libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.0)(64bit) libgcc_s.so.1(GCC_3.3)(64bit) libgcc_s.so.1(GCC_3.3.1)(64bit) libgcc_s.so.1(GCC_3.4)(64bit) libgcc_s.so.1(GCC_3.4.2)(64bit) libgcc_s.so.1(GCC_3.4.4)(64bit) libgcc_s.so.1(GCC_4.0.0)(64bit) libgcc_s.so.1(GCC_4.2.0)(64bit) libgcc_s.so.1(GCC_4.3.0)(64bit) libgcc_s.so.1(libgcc_s.so.1)(64bit) libgcc45 = 4.5.1_20101116-85.1 libgcc45(x86-64) = 4.5.1_20101116-85.1 libgcc1 < 4.5.1_20101116-85.1 libgcc = 3.3.3-24.66 libgcc_s.so.1()(64bit) libgcc_s.so.1(GCC_3.0)(64bit) libgcc_s.so.1(GCC_3.3)(64bit) libgcc_s.so.1(GCC_3.3.1)(64bit) libgcc_s.so.1(libgcc_s.so.1)(64bit) libgcc33 = 3.3.3-24.66 libgcc33(x86-64) = 3.3.3-24.66 so somehow the solver installs libgcc33 even though libgcc45 is already installed. Note that I indeed miss a conflict with the libgcc33 package (it doesn't provide libgcc1 but libgcc). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c3 --- Comment #3 from Richard Guenther <rguenther@novell.com> 2010-12-06 13:25:15 UTC --- libgcc33 should be fixed with the next rebuild in devel:gcc. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c4 --- Comment #4 from Joseph Comfort <Joseph.Comfort@asu.edu> 2010-12-06 16:29:37 UTC --- Good. Thank you. I'll watch for it. I just want to be sure that the libgcc33 rpm can be eliminated with the update. I could not remove it because it was required by something else -- gcc33 as I recall. It is not included on my other machines. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c5 Richard Guenther <rguenther@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #5 from Richard Guenther <rguenther@novell.com> 2010-12-06 16:31:02 UTC --- Yes, I also fixed the requires. I'll check that an update from the repo works for me tomorrow (when it finally finished publishing). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c6 --- Comment #6 from Richard Guenther <rguenther@novell.com> 2010-12-08 12:18:27 UTC --- It seems to work for me now, so if you want to re-try ... ;) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c7 --- Comment #7 from Joseph Comfort <Joseph.Comfort@asu.edu> 2010-12-09 19:14:35 UTC --- I successfully updated the rpms. Thanks. Initially, YaST2 showed dependency conflicts. I selected 'do not update libgcc33.' After the updates, I went back and deleted the libgcc33 rpms. These are not on any of my systems. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=657604 https://bugzilla.novell.com/show_bug.cgi?id=657604#c8 Richard Guenther <rguenther@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #8 from Richard Guenther <rguenther@novell.com> 2010-12-10 12:29:12 UTC --- Yep, the conflicts are expected. Closing as fixed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com