Hide Forgot
Description of problem: I'm unable to install rhts-devel from the new beaker repo due to unsatisfied dependencies. Version-Release number of selected component (if applicable): rhts-devel.noarch 0:4.38-1.el5 How reproducible: always Steps to Reproduce: https://engineering.redhat.com/trac/rhat/wiki/BeakerUserGuide on a stablesystem 1. rpm -e rhts-release 2. wget -O /etc/yum.repos.d/beaker.repo http://beaker-stage.app.eng.bos.redhat.com/beaker-prod/beaker-RedHatEnterpriseLinux.repo 3. yum install rhts-devel Actual results: .qa.[root@ppcp-5s-m1 tps]# yum install rhts-devel Loaded plugins: aliases, changelog, downloadonly, fastestmirror, filter-data, keys, kmod, list-data, protect-packages, protectbase, rhnplugin, security, tmprepo, : verify, versionlock Loading mirror speeds from cached hostfile Skipping filters plugin, no data 0 packages excluded due to repository protections Reading version lock configuration Setting up Install Process Resolving Dependencies Skipping filters plugin, no data --> Running transaction check ---> Package rhts-devel.noarch 0:4.38-1.el5 set to be updated --> Processing Dependency: beaker-client for package: rhts-devel --> Running transaction check ---> Package beaker-client.noarch 0:0.6.12-1.git.22.d828891.el5 set to be updated --> Processing Dependency: beaker = 0.6.12-1.git.22.d828891.el5 for package: beaker-client --> Processing Dependency: kobo-client >= 0.3 for package: beaker-client --> Processing Dependency: python-lxml for package: beaker-client --> Processing Dependency: python-krbV for package: beaker-client --> Running transaction check ---> Package beaker.noarch 0:0.6.12-1.git.22.d828891.el5 set to be updated ---> Package beaker-client.noarch 0:0.6.12-1.git.22.d828891.el5 set to be updated --> Processing Dependency: python-lxml for package: beaker-client --> Processing Dependency: python-krbV for package: beaker-client ---> Package kobo-client.noarch 0:0.3.4-1.el5 set to be updated --> Processing Dependency: kobo = 0.3.4-1.el5 for package: kobo-client --> Processing Dependency: python-simplejson for package: kobo-client --> Running transaction check ---> Package beaker-client.noarch 0:0.6.12-1.git.22.d828891.el5 set to be updated --> Processing Dependency: python-lxml for package: beaker-client --> Processing Dependency: python-krbV for package: beaker-client ---> Package kobo.noarch 0:0.3.4-1.el5 set to be updated --> Processing Dependency: python-hashlib for package: kobo ---> Package python-simplejson.ppc 0:2.0.9-8.el5 set to be updated --> Finished Dependency Resolution beaker-client-0.6.12-1.git.22.d828891.el5.noarch from beaker has depsolving problems --> Missing Dependency: python-lxml is needed by package beaker-client-0.6.12-1.git.22.d828891.el5.noarch (beaker) kobo-0.3.4-1.el5.noarch from beaker has depsolving problems --> Missing Dependency: python-hashlib is needed by package kobo-0.3.4-1.el5.noarch (beaker) beaker-client-0.6.12-1.git.22.d828891.el5.noarch from beaker has depsolving problems --> Missing Dependency: python-krbV is needed by package beaker-client-0.6.12-1.git.22.d828891.el5.noarch (beaker) Error: Missing Dependency: python-lxml is needed by package beaker-client-0.6.12-1.git.22.d828891.el5.noarch (beaker) Error: Missing Dependency: python-hashlib is needed by package kobo-0.3.4-1.el5.noarch (beaker) Error: Missing Dependency: python-krbV is needed by package beaker-client-0.6.12-1.git.22.d828891.el5.noarch (beaker) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest Expected results: the package rhts-devel gets installed Additional info: .qa.[root@ppcp-5s-m1 tps]# tps-yum-show-channels beaker rhel-ppc-server-5 rhel-ppc-server-cluster-5 rhel-ppc-server-cluster-storage-5 rhel-ppc-server-fastrack-5 rhel-ppc-server-hts-5 rhel-ppc-server-supplementary-5
Is there a reason you need rhts-devel on ppc? We assumed that the client would only be needed on i386 and x86_64 so thats all we built the repo for. oh wait. I'm remembering back the irc session now. So tps requires rhts-rh-devel. Can You tell me why tps require rhts-rh-devel? We do build rhts-test-env for all arches in the harness repo.
(In reply to comment #1) > Is there a reason you need rhts-devel on ppc? We assumed that the client would > only be needed on i386 and x86_64 so thats all we built the repo for. > > oh wait. I'm remembering back the irc session now. So tps requires > rhts-rh-devel. Can You tell me why tps require rhts-rh-devel? We do build > rhts-test-env for all arches in the harness repo. it is not TPS itself but a tool called tps-rhts which serves to run tests (from cvs) I'm not sure what and why exactly is needed - CCing ohudlick as the author if he can provide more info the tool should run on full set of architectures, to be able to run tests on all of them (um, I guess it is not just because of the tool, but the tests themselves need the rhts packages even if you run them manually via "make run" or runtest.sh)
(In reply to comment #2) > it is not TPS itself but a tool called tps-rhts which serves to run tests (from > cvs) > > I'm not sure what and why exactly is needed - CCing ohudlick as the author if > he can provide more info > > the tool should run on full set of architectures, to be able to run tests on > all of them (um, I guess it is not just because of the tool, but the tests > themselves need the rhts packages even if you run them manually via "make run" > or runtest.sh) It could be that tps-rhts just has the wrong requirement since make run is satisfied via rhts-test-env and that *is* available for every architecture.
(In reply to comment #3) > It could be that tps-rhts just has the wrong requirement since make run is > satisfied via rhts-test-env and that *is* available for every architecture. Ondro, please could you explain why rhts-devel is required by the script? wouldn't rhts-test-env be sufficient then?
closing. If you feel the dependencies are still messed up then re-open.