Opened 11 years ago
Closed 10 years ago
#67 closed defect (fixed)
Yum/Rpm stopped working
Reported by: | guzzi | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | rpm | Version: | |
Severity: | Keywords: | ||
Cc: |
Description
I have a problem similar to the ome in (closed) ticket 66
Yum gives the following error (no entries in popuplog):
F:\>yum
There was a problem importing one of the Python modules
required to run yum. The error leading to this problem was:
dlopen rc=87 extra=°
Please install a package which provides this module, or
verify that the module is installed correctly.
It's possible that the above module doesn't match the
current version of Python, which is:
2.6.5 (r265:79063, Jun 5 2013, 16:43:40)
[GCC 4.4.6]
If you cannot solve this problem yourself, please go to
the yum faq at:
When I run RPM from the commandline an error is generated in popuplog:
01-18-2014 15:48:35 SYS3175 PID 00bc TID 0001 Slot 00f3
F:\USR\BIN\RPM.EXE
c0000005
1c894ce0
P1=00000002 P2=1de31b80 P3=XXXXXXXX P4=XXXXXXXX
EAX=00000001 EBX=114907b0 ECX=1de31b80 EDX=11490760
ESI=00000000 EDI=00000000
DS=0053 DSACC=f0f3 DSLIM=ffffffff
ES=0053 ESACC=f0f3 ESLIM=ffffffff
FS=150b FSACC=00f3 FSLIM=00000030
GS=0000 GSACC= GSLIM=
CS:EIP=005b:1c894ce0 CSACC=f0df CSLIM=ffffffff
SS:ESP=0053:0012ff74 SSACC=f0f3 SSLIM=ffffffff
EBP=0012ffa0 FLG=00010203
GCC473.DLL 0001:00004ce0
David McKenna sent me the current RPM version of GCC473.dll, so I am assuming that the problem is not actually caused by GCC473.dll
Change History (12)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
I removed the bootstrap package after installing yum/rpm. If I want to reinstall it, it will overwrite the current unix tree. What is the best way to proceed? Backup the tree, reinstall bootstrap package and then copy the tree back overwriting the stuff put in by the bootstrap package?
comment:3 by , 11 years ago
Reinstalling the bootstrap package will not overwrite your existing tree, bootstrap is going into %TMP%. I suggest to use boostrap 1.4 and manually adjust PATH and BEGINLIBPATH in the console window.
comment:5 by , 11 years ago
I installed the 1.4 zip package and used yum remove libcc473. This removed the gcc473 package and it's dependencies, o.a. yum. As a result yum couldn't find the module yum anymore...
I gave up and used a backup....
When I try to install libgcc473 now, I get an error no package libgcc473 available. I do see one in the exp rep which I have in my config.
comment:7 by , 11 years ago
I tried that, but it didn't work. My mistake, I used the boostrap console from a different drive.
2 problems remain after reinstalling:
1)
Installing:
libgcc i386 4.4.4-1 netlabs-rel 39 k
will lead to this error:
Transaction Check Error:
file /@unixroot/usr/lib/gcc444.dll from install of libgcc-4.4.4-1.i386 confli
ts with file from package libgcc444-4.5.2-2.oc00.i386
2) libgcc473 will not install, probably because it is in the pentium4 repo and incompatible with i386. Shouldn't there be an i386 version too?
comment:8 by , 11 years ago
The bootstrap code should work also from a different drive, please open a different ticket if you can reproduce.
you need to install only one of libgcc-4.4.4-1.i386 and libgcc-4.4.4-1.i386. I wonder how you got both installed.
Regarding libgcc473, it is only in the experimental tree and only for pentium4. i386 will get only in the release tree. Which CPU do you have?
comment:9 by , 11 years ago
I will open a ticket when I find time to reproduce. I tried twic, so I'm fairly sur it will reproduce.
As regards libgcc4.4.1, I installed yum, did a yum update and that is all. Tried several times with all gcc libs uninstalled, always that same result.
CPU is a Core 2 Quad
comment:10 by , 11 years ago
I will check which files are in those packages. the 4.5.2 package has been added to fulfill some other packages, one of them is redundant.
With Core2 you can install pentium4 packages. Please add a platform file as in wiki instructions.
comment:12 by , 10 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
we assume this is fixed, If not please either reopen this ticket, or open a new one.
This is because of broken gcc473.dll shipped in the past. Now you probably have two dlls requiring it, one requires the broken dll, the other the correct one. You need to identify which upgrade broke your system (last one most probably), then you need to downgrade it. Add the the bootstrap package to your path/libpath to have a working RPM recovery console.