--Sig_/fUwo9BEvqv/Zuzhy3Mjv2Am Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable 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? On Thu, 30 Jan 2014 16:26:51 +0100 Sandro wrote: SB> Il 30/01/2014 16:13, Yaniv Bronheim ha scritto: SB> > Hey,=20 SB> >=20 SB> > we found this yum bug and still struggling with more issuing SB> > according to the relation between those packages=20 SB> >=20 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> >=20 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> >=20 SB>=20 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 --Sig_/fUwo9BEvqv/Zuzhy3Mjv2Am Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlLqxkUACgkQ7/fVLLY1mnheswCgn8iUtI+8ej1p6wFiJJ+2cVoq xckAniQ28R+72D7EE7VsWntZYFPMuSuu =WVqR -----END PGP SIGNATURE----- --Sig_/fUwo9BEvqv/Zuzhy3Mjv2Am--