On Wed, Mar 30, 2016 at 5:00 PM, Paul Dyer <[email protected]> wrote: > Hi, > > after upgrade to ovirt 3.6, the ovirt-release35 repo remains on the manager > machine (non-hosted engine). There is also a list of rpms from the 3.5 > repo. > > Should the 3.5 repo be removed?
In principle, yes. > What about the rpms from the 3.5 repo? > Should they stay or go? In principle it means that the version from 3.6 is identical to the one you had from 3.5, so yum didn't update them. You can try removing the 3.5 repo, then yum reinstall each package, to make sure. Or just keep them. > > Here is a list of 3.5 repo rpms still installed: > > # yum list installed |grep ovirt-3.5 > ovirt-engine-jboss-as.x86_64 7.1.1-1.el6 @ovirt-3.5 > patternfly1.noarch 1.3.0-1.el6 > @ovirt-3.5-patternfly1-noarch-epel > python-daemon.noarch 1.5.2-1.el6 @ovirt-3.5-epel > python-kitchen.noarch 1.1.1-1.el6 @ovirt-3.5-epel > python-lockfile.noarch 0.8-3.el6 @ovirt-3.5-epel > python-ply.noarch 3.4-4.el6 @ovirt-3.5-epel > python-websockify.noarch 0.6.0-3.el6 @ovirt-3.5-epel > xalan-j2.noarch 2.7.1-8.jbossorg_1.jpp6 > @ovirt-3.5-jpackage-6.0-generic > > Thanks, > Paul > > -- > Paul Dyer, > Mercury Consulting Group, RHCE > 504-302-8750 > > _______________________________________________ > Devel mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/devel -- Didi _______________________________________________ Devel mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/devel
