Proposal for dropping packages from ovirt rpm repositories
alonbl at redhat.com
Wed Jan 22 10:00:17 UTC 2014
----- Original Message -----
> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
> To: "arch" <arch at ovirt.org>, "infra" <infra at ovirt.org>
> Cc: "Kiril Nesenko" <knesenko at redhat.com>, "Ohad Basan" <obasan at redhat.com>
> Sent: Wednesday, January 22, 2014 11:40:33 AM
> Subject: Proposal for dropping packages from ovirt rpm repositories
> I think that having the same package on different repositories must be
> The last python-cpopen-1.3 release broke repository closure of ovirt-stable
> which provides a vdsm release still requiring vdsm-python-cpopen.
> I think that since vdsm and other packages are delivered in Fedora
> repositories we should not deliver them in ovirt repositories.
> An example is:
> python-cpopen affects both Fedora and oVirt repositories, hitting 2 different
> but other packages are handled as vdsm.
> So i suggest to keep just .tar.gz files on ovirt site for allowing fedora
> packagers to build referencing the source tarball and drop at all any
> package already provided by Fedora from ovirt site.
> Comments as always are welcome.
We should build pre-release as fedora will wait for release, and we might depend on pre-release for our own pre-releases right?
Also, if we are not the ones that control the fedora packaging, then we probably need to provide even release until fedora adds to their repo.
Maybe these components should go into different non ovirt repositories that can be easily disabled? even one per such package?
If this is the only example and it is quite static, then no need to invest any resource... just remove it.
More information about the Infra