Re: [Users] Problem with python-cpopen dependency on f19 AIO stable
Hi, was this resolved for EL 6.5? I'm currently planning to roll out EL 6.5 Nodes and would like to know how to circumvent this issue if it is still present? Am 05.12.2013 12:13, schrieb Martijn Grendelman: > I have the same issue on a CentOS node after updating it to 6.5: > >> Resolving Dependencies >> --> Running transaction check >> ---> Package python-cpopen.x86_64 0:1.2.3-4.el6 will be obsoleted >> ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.el6 will be obsoleting >> --> Finished Dependency Resolution >> >> Dependencies Resolved >> >> >> Package Arch >> Version Repository >> Size >> >> Installing: >> vdsm-python-cpopenx86_64 >> 4.13.0-11.el6ovirt-stable 19 >> k >> replacing python-cpopen.x86_64 1.2.3-4.el6 >> >> Transaction Summary >> >> Install 1 Package(s) >> >> Total download size: 19 k >> Is this ok [y/N]: y > > On a subsequent run of 'yum update', python-cpopen will replace > vdsm-python-cpopen, and so on. > > Vinzenz Feenstra schreef op 5-12-2013 8:34: >> Forwading to vdsm-devel >> >> On 12/04/2013 08:59 AM, Gianluca Cecchi wrote: >>> Hello, >>> since yesterday evening I have this sort of dependency problem with updates >>> >>> yum update >>> say >>> >>> Resolving Dependencies >>> --> Running transaction check >>> ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting >>> ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted >>> --> Finished Dependency Resolution >>> >>> Dependencies Resolved >>> >>> = >>> Package Arch Version >>> Repository Size >>> = >>> Installing: >>> python-cpopenx86_64 >>> 1.2.3-4.fc19updates 19 k >>> replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19 >>> >>> Transaction Summary >>> = >>> Install 1 Package >>> >>> If I go ahead and run yum update again I have: >>> >>> Dependencies Resolved >>> >>> = >>> PackageArch Version >>> RepositorySize >>> = >>> Installing: >>> vdsm-python-cpopen x86_64 >>> 4.13.0-11.fc19 ovirt-stable 20 k >>> replacing python-cpopen.x86_64 1.2.3-4.fc19 >>> >>> Transaction Summary >>> = >>> Install 1 Package >>> >>> and so again in a loop >>> >>> Gianluca -- Mit freundlichen Grüßen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +49-5772-293-100 F: +49-5772-293-333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Re: [Users] Problem with python-cpopen dependency on f19 AIO stable
I have the same issue on a CentOS node after updating it to 6.5: > Resolving Dependencies > --> Running transaction check > ---> Package python-cpopen.x86_64 0:1.2.3-4.el6 will be obsoleted > ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.el6 will be obsoleting > --> Finished Dependency Resolution > > Dependencies Resolved > > > Package Arch > Version Repository Size > > Installing: > vdsm-python-cpopenx86_64 > 4.13.0-11.el6ovirt-stable 19 k > replacing python-cpopen.x86_64 1.2.3-4.el6 > > Transaction Summary > > Install 1 Package(s) > > Total download size: 19 k > Is this ok [y/N]: y On a subsequent run of 'yum update', python-cpopen will replace vdsm-python-cpopen, and so on. Cheers, Martijn. Vinzenz Feenstra schreef op 5-12-2013 8:34: > Forwading to vdsm-devel > > On 12/04/2013 08:59 AM, Gianluca Cecchi wrote: >> Hello, >> since yesterday evening I have this sort of dependency problem with updates >> >> yum update >> say >> >> Resolving Dependencies >> --> Running transaction check >> ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting >> ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted >> --> Finished Dependency Resolution >> >> Dependencies Resolved >> >> = >> Package Arch Version >> Repository Size >> = >> Installing: >> python-cpopenx86_64 >> 1.2.3-4.fc19updates 19 k >> replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19 >> >> Transaction Summary >> = >> Install 1 Package >> >> If I go ahead and run yum update again I have: >> >> Dependencies Resolved >> >> = >> PackageArch Version >> RepositorySize >> = >> Installing: >> vdsm-python-cpopen x86_64 >> 4.13.0-11.fc19 ovirt-stable 20 k >> replacing python-cpopen.x86_64 1.2.3-4.fc19 >> >> Transaction Summary >> = >> Install 1 Package >> >> and so again in a loop >> >> Gianluca >> ___ >> Users mailing list >> Users@ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users > > ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Problem with python-cpopen dependency on f19 AIO stable
Forwading to vdsm-devel On 12/04/2013 08:59 AM, Gianluca Cecchi wrote: Hello, since yesterday evening I have this sort of dependency problem with updates yum update say Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted --> Finished Dependency Resolution Dependencies Resolved = Package Arch Version Repository Size = Installing: python-cpopenx86_64 1.2.3-4.fc19updates 19 k replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19 Transaction Summary = Install 1 Package If I go ahead and run yum update again I have: Dependencies Resolved = PackageArch Version RepositorySize = Installing: vdsm-python-cpopen x86_64 4.13.0-11.fc19 ovirt-stable 20 k replacing python-cpopen.x86_64 1.2.3-4.fc19 Transaction Summary = Install 1 Package and so again in a loop Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users -- Regards, Vinzenz Feenstra | Senior Software Engineer RedHat Engineering Virtualization R & D Phone: +420 532 294 625 IRC: vfeenstr or evilissimo Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
[Users] Problem with python-cpopen dependency on f19 AIO stable
Hello, since yesterday evening I have this sort of dependency problem with updates yum update say Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-4.fc19 will be obsoleting ---> Package vdsm-python-cpopen.x86_64 0:4.13.0-11.fc19 will be obsoleted --> Finished Dependency Resolution Dependencies Resolved = Package Arch Version Repository Size = Installing: python-cpopenx86_64 1.2.3-4.fc19updates 19 k replacing vdsm-python-cpopen.x86_64 4.13.0-11.fc19 Transaction Summary = Install 1 Package If I go ahead and run yum update again I have: Dependencies Resolved = PackageArch Version RepositorySize = Installing: vdsm-python-cpopen x86_64 4.13.0-11.fc19 ovirt-stable 20 k replacing python-cpopen.x86_64 1.2.3-4.fc19 Transaction Summary = Install 1 Package and so again in a loop Gianluca ___ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
