I hadn’t ran across that page prior. When I was on the https://github.com/spacewalkproject/spacewalk/wiki/HowToInstallNightly page, the upgrade link goes to https://github.com/spacewalkproject/spacewalk/wiki/HowToUpgrade instead of the link you sent below.
After I ran the rpm removal command and disabled the jpackage repository complete, the upgrade kicked off AOK. Thanks! Jeffrey From: <[email protected]> on behalf of Eric Herget <[email protected]> Reply-To: "[email protected]" <[email protected]> Date: Friday, August 11, 2017 at 13:52 To: "[email protected]" <[email protected]> Subject: Re: [Spacewalk-list] upgrade of 2.6 to 2.7-nightly fails on RHEL/CentOS 6 I had responded to Jeffrey directly when I meant to reply to the list so others could benefit... There is a HowToUpgradeNightly document on the wiki here - https://github.com/spacewalkproject/spacewalk/wiki/HowToUpgradeNightly Spacewalk Nightly (and the upcoming 2.7 release) no longer uses the jpackage repo. There is a step in the upgrade process to remove some of the packages that come from the jpackage repo (those with ".jpp5") if you are running on RHEL6. I did the upgrade process the other day and I ended up removing all the packages that had come from the jpackage repo. Also note, the upgrade process requires versionlock of quartz if you are running on Fedora. Eric On 08/11/2017 12:28 PM, Miller, Jeffrey L wrote: I’m not sure where to send this so I figured to the list would be a good idea. I saw rumblings of a release soon, and I was testing the upgrade of a Spacewalk 2.6 server to 2.7-nightly on both RHEL 6 and CentOS 6 VMs; however, I encountered the following error on dependency checking from a yum upgrade command: ---> Package spacewalk-java.noarch 0:2.7.108-1.el6 will be obsoleting --> Processing Dependency: jakarta-commons-logging < 1.1 for package: spacewalk-java-2.7.108-1.el6.noarch --> Finished Dependency Resolution Error: Package: jakarta-commons-logging-mvn-2.7.12-1.sw.noarch (group_spacewalkproject-epel6-addons) Requires: jakarta-commons-logging = 1.0.4 Installed: jakarta-commons-logging-1.1-8.jpp5.noarch (@jpackage-generic) jakarta-commons-logging = 1.1-8.jpp5 Available: jakarta-commons-logging-1.0.4-10.el6.noarch (base) jakarta-commons-logging = 1.0.4-10.el6 Error: Package: spacewalk-java-2.7.108-1.el6.noarch (spacewalk-nightly) Requires: jakarta-commons-logging < 1.1 Installed: jakarta-commons-logging-1.1-8.jpp5.noarch (@jpackage-generic) jakarta-commons-logging = 1.1-8.jpp5 Available: jakarta-commons-logging-1.0.4-10.el6.noarch (base) jakarta-commons-logging = 1.0.4-10.el6 You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest I believe the error is coming from the requirements specified in the spec file for spacewalk-java on GitHub (https://github.com/spacewalkproject/spacewalk/blob/master/java/spacewalk-java.spec), line 127 reads: “Requires: jakarta-commons-logging < 1.1”. The package version for jakarta-commons-logging on a Spacewalk 2.6 install on CentOS 6 is jakarta-commons-logging-1.1-8.jpp5.noarch. In other words, 1.1 < 1.1 fails the yum dependency check, and yum cannot downgrade to 1.0.4 since 1.1 is required for other components. Jeffrey ============================================= Jeffrey Miller Senior Systems Administrator The University of Iowa ITS – Research Services 19 Lindquist Center South Iowa City, IA 52242-1727 (319) 467-1636 ============================================= _______________________________________________ Spacewalk-list mailing list [email protected]<mailto:[email protected]> https://www.redhat.com/mailman/listinfo/spacewalk-list -- Eric Herget | Senior Software Engineer Red Hat Satellite
_______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
