Proposal for dropping packages from ovirt rpm repositories
Hi, I think that having the same package on different repositories must be avoided. 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: https://bugzilla.redhat.com/show_bug.cgi?id=1056470 https://bugzilla.redhat.com/show_bug.cgi?id=1056464 python-cpopen affects both Fedora and oVirt repositories, hitting 2 different products. 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. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
----- Original Message -----
From: "Sandro Bonazzola" <sbonazzo@redhat.com> To: "arch" <arch@ovirt.org>, "infra" <infra@ovirt.org> Cc: "Kiril Nesenko" <knesenko@redhat.com>, "Ohad Basan" <obasan@redhat.com> Sent: Wednesday, January 22, 2014 11:40:33 AM Subject: Proposal for dropping packages from ovirt rpm repositories
Hi, I think that having the same package on different repositories must be avoided.
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: https://bugzilla.redhat.com/show_bug.cgi?id=1056470 https://bugzilla.redhat.com/show_bug.cgi?id=1056464
python-cpopen affects both Fedora and oVirt repositories, hitting 2 different products. 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. Alon
On Wed, Jan 22, 2014 at 10:40:33AM +0100, Sandro Bonazzola wrote:
Hi, I think that having the same package on different repositories must be avoided.
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: https://bugzilla.redhat.com/show_bug.cgi?id=1056470 https://bugzilla.redhat.com/show_bug.cgi?id=1056464
python-cpopen affects both Fedora and oVirt repositories, hitting 2 different products. 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.
Only problem with this is that epel would not agree to ship the el6 build of rpm - we'd need to carry it on our own. Dan.
Il 22/01/2014 14:57, Dan Kenigsberg ha scritto:
On Wed, Jan 22, 2014 at 10:40:33AM +0100, Sandro Bonazzola wrote:
Hi, I think that having the same package on different repositories must be avoided.
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: https://bugzilla.redhat.com/show_bug.cgi?id=1056470 https://bugzilla.redhat.com/show_bug.cgi?id=1056464
python-cpopen affects both Fedora and oVirt repositories, hitting 2 different products. 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.
Only problem with this is that epel would not agree to ship the el6 build of rpm - we'd need to carry it on our own.
with epel we won't have duplicates in different repos
Dan.
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (3)
-
Alon Bar-Lev -
Dan Kenigsberg -
Sandro Bonazzola