On Wed, 16 Oct 2019 at 03:53, Fabian Arrotin arrfab@centos.org wrote:
It seems EPEL doesn't use a repoclosure test when pushing from testing to stable. Let me just take one simple example : I recently asked a pkg to be built for epel 8 (see https://bugzilla.redhat.com/show_bug.cgi?id=1755787)
Sadly repoclosure would only work for EPEL-6 and 7 . I think it stopped working after some changes were made to rpm after Fedora 21 or so.. [Try running repoclosure on CentOS-8:
package: systemd-udev-239-13.el8.x86_64 from BaseOS unresolved deps: systemd(x86-64) = 239-13.el8 package: systemd-udev-239-13.el8_0.3.i686 from BaseOS unresolved deps: systemd(x86-32) = 239-13.el8_0.3 package: systemd-udev-239-13.el8_0.3.x86_64 from BaseOS unresolved deps: systemd(x86-64) = 239-13.el8_0.3 package: valgrind-devel-1:3.14.0-9.el8.i686 from AppStream unresolved deps: valgrind = 1:3.14.0-9.el8 package: valgrind-devel-1:3.14.0-9.el8.x86_64 from AppStream unresolved deps: valgrind = 1:3.14.0-9.el8
... it goes on and on.]
Stephen (smooge) would probably be able to comment if that would be possible for Epel to have some gating from -testing to stable (like a simple repoclosure test) to see if packages pushed to stable can be installable (and so satisfied deps in stable repo too)
A new repoclosure tool would need to be written, then integrating it with I think bodhi would be needed.