Il 30/01/2014 22:38, Robert Story ha scritto: > Can we revert these packages to previous versions in the 3.3.2 stable repo > so those of us who want/need to install new hosts in our clusters aren't > dead in the water waiting for 3.3.3?
Hi Robert, I think you can still install 3.3.2 on your clusters with the requirement of adding manually oython-cpopen before trying to install vdsm. About 3.3.3, I think vdsm should really drop dependency on vdsm-python-cpopen: it's a package obsoleted by python-cpopen so there's no point in still requiring it especially if keeping that requirement still break dependency resolution. > > On Thu, 30 Jan 2014 16:26:51 +0100 Sandro wrote: > SB> Il 30/01/2014 16:13, Yaniv Bronheim ha scritto: > SB> > Hey, > SB> > > SB> > we found this yum bug and still struggling with more issuing > SB> > according to the relation between those packages > SB> > > SB> > if we drop vdsm-python-cpopen the requirement in vdsm takes > SB> > python-cpopen instead. in python-cpopen we have the same code base > SB> > and it provides all vdsm-ptyhon-cpopen provides, so shouldn't be any > SB> > issues with dropping it from the repository > SB> > > SB> > is it possible to ship 3.3.3 release that way ? we don't need to > SB> > change the requirement in the code, if python-cpopen 1.3-1 is part of > SB> > the release, it will be taken by vdsm spec (tried with vdsm 4.13.3-2 > SB> > with the available cpopen 1.3-1) > SB> > > SB> > SB> I can't release 3.3.3 that way. > SB> We're keeping rolling releases on stable repository so if I don't > SB> provide 4.13.3-2, previous one will still be available. > > > Robert > > -- > Senior Software Engineer @ Parsons > -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel