Error installing gcc from Access Client Solutions
Issue #160
resolved
Using the access client solutions installer and gcc fails to install.
http://rpms.sobo.red/ibmi/ppc64/repodata/repomd.xml: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package gcc.noarch 0:6-2 will be installed
--> Processing Dependency: gcc6 = 6.3.0 for package: gcc-6-2.noarch
--> Running transaction check
---> Package gcc6-aix.fat 0:6.3.0-29 will be installed
--> Processing Dependency: gcc6-cpp-aix = 6.3.0-29 for package: gcc6-aix-6.3.0-29.fat
--> Processing Dependency: /QOpenSys/pkgs/lib/libatomic.so.1 for package: gcc6-aix-6.3.0-29.fat
http://rpms.sobo.red/ibmi/ppc64/repodata/e86915da66da7f78fb8226d7cc553a17121ce738f45e440720bfecf27612af01-filelists.sqlite.bz2: [Errno 14] HTTP Error 404 - Not Found
Trying other mirror.
Error: failure: repodata/e86915da66da7f78fb8226d7cc553a17121ce738f45e440720bfecf27612af01-filelists.sqlite.bz2 from sobored: [Errno 256] No more mirrors to try.
Traceback (most recent call last):
File "/QOpenSys/pkgs/bin/yum", line 29, in <module>
yummain.user_main(sys.argv[1:], exit_code=True)
File "/QOpenSys/pkgs/share/yum-cli/yummain.py", line 288, in user_main
errcode = main(args)
File "/QOpenSys/pkgs/share/yum-cli/yummain.py", line 203, in main
if base._depsolving_failed:
AttributeError: 'YumBaseCli' object has no attribute '_depsolving_failed'
Screenshot of acs version info attached.
What I’m trying to do is get a python package installed. Some of the dependencies are looking for gcc…
Any help?
-Jim
Comments (4)
-
-
Also, check
/QOpenSys/etc/yum/repos.d/sobored.repo
(or whatever it may be named) and change the baseurl fromhttp://rpms.sobo.red/ibmi/ppc64
tohttp://rpms.sobo.red/ibmi/
-
reporter Thanks guys, that did the trick!
-
reporter - changed status to resolved
disabled sobored repo and ran install successfully.
- Log in to comment
The error mentions
http://rpms.sobo.red
. This is not an IBM site. You will have to ask the owner of that repository what is wrong. In the mean time, you could disable the repository by editing changing enabled=1 to enabled=0 in its /QOpenSys/etc/yum/repos.d/whatever.repo file.