Opened 9 years ago
Closed 9 years ago
#160 closed defect (fixed)
Error message when starting YUM: execv failed, rc =-1 No such file or directory
Reported by: | Einar Lygre | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | yum | Version: | |
Severity: | highest | Keywords: | |
Cc: |
Description
[E:\]yum
execv failed, rc=-1
execv: No such file or directory
It does not matter what command I use after YUM
I'm running eCS 2.2 beta II
Change History (13)
follow-up: 4 comment:1 by , 9 years ago
follow-up: 6 comment:3 by , 9 years ago
more questions:
- did it ever run
- if yes what did you change right before it stopped running
- did you delete something
- did you move around path entries in config.sys
- did you install python from somewhere and not using the rpm one
comment:4 by , 9 years ago
Replying to diver:
it's always the case with such error messages:
which rpm version does one run?
To be honest: I don't know, but (all?) RPM files in e:\usr\.. is dated 2015\02\25. I think they are from the version that came with eCS 2.2 beta II
comment:5 by , 9 years ago
Replying to diver:
the output of "yum list rpm*" is needed btw
Well, the result is:
[E:\]yum list rpm*
execv failed, rc=-1
execv: No such file or directory
comment:6 by , 9 years ago
Replying to diver:
more questions:
- did it ever run
- if yes what did you change right before it stopped running
- did you delete something
- did you move around path entries in config.sys
- did you install python from somewhere and not using the rpm one
Q1: Probably not, but I can't remember the error messages I got. I remember that because of the problems I tried to install the software (rpm-yum-bootstrap-1_3.wpi or rpm-yum-bootstrap-1_5-p4.wpi). It didn't work so I uninstalled it again. That is the situation today.
Q2: Change what? Answer is probably NO.
Q3: Of course! With all the different versions of *.dlls spread around, that is the only way to fix things. But I don't think I did this for RPM/YUM.
Q4: Yes. Scribus is depending on Python27.dll and it has to be in the libpath - according to the ReadMe file. I have installed new versions of Scribus, and that might have been one of the first installations after eCS 2.2 beta II.
follow-up: 8 comment:7 by , 9 years ago
so it looks like you screwed your installation when you installed the other python.
eCS 2.2 installs a rpm/yum already. when you after that fiddle around it gets hard to fix it.
If you didn't install anything with rpm at all so far, I recommend you to delete everything in \usr and either reinstall the bootstrap 1.5 or use the ANPM.
But for sure take care, that you remove the Paul's python first. Scribus works again, as soon as all rpm/yum staff also works.
comment:8 by , 9 years ago
Replying to diver:
so it looks like you screwed your installation when you installed the other python.
eCS 2.2 installs a rpm/yum already. when you after that fiddle around it gets hard to fix it.
If you didn't install anything with rpm at all so far, I recommend you to delete everything in \usr and either reinstall the bootstrap 1.5 or use the ANPM.
But for sure take care, that you remove the Paul's python first. Scribus works again, as soon as all rpm/yum staff also works.
What is ANPM?
comment:10 by , 9 years ago
Arca Noae Package Manager may be downloaded from this link.
Be sure to read the support wiki, as there are a number of things you should know which might impact your particular setup.
comment:11 by , 9 years ago
hmm 2 month of no updates from the reporter. We can't help when we don't get the input.
comment:12 by , 9 years ago
Sorry about not answering.
I immediately installed ANPM and followed your instructions and the result was success. It seems that everything is OK now.
Thank you very much.
comment:13 by , 9 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
it's always the case with such error messages:
which rpm version does one run?