#5842 Please unblock some EPEL-6 packages
Closed: Fixed None Opened 10 years ago by pghmcfc.

Some perl modules that replaced EPEL-6 were introduced in a recent EL-6 point release, and the EPEL-6 packages were retired. However, the new packages were not made available in EL-6 for ppc64 and this has resulted in broken dependencies for other packages in EPEL-6 for ppc64.

In particular, I would like to un-retire perl-Class-Accessor and perl-Class-Data-Inheritable and re-introduce them to EPEL-6 with a zero release number as per the guidance at https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages


Please unretire them first in pkgdb with an SCM admin request as described here:
http://fedoraproject.org/wiki/Package_SCM_admin_requests

I misunderstood that unretirement had to occur before unblocking, unretired.

I've now claimed the packages again in pkgdb, thanks. Can they now be unblocked?

Unblocked with:
{{{koji unblock-pkg dist-6E-epel perl-Class-Data-Inheritable perl-Class-Accessor}}}

New problem: the builds for these packages are now ready to be pushed to stable, but when I try to mark them as stable, I get this:
{{{
Broken update path: perl-Class-Accessor-0.31-6.1.el6 is already released, and is newer than perl-Class-Accessor-0.31-0.6.1.el6
}}}
There was previously a perl-Class-Accessor-0.31-6.1.el6 package in EPEL-6 but that was retired because the package was in RHEL-6. However, it's not available on all architectures, so I followed the EPEL guidelines and created a clone of the RHEL package but with a "0." release prefix to provide the package on ppc64. It looks now that the existence of the original (retired) EPEL package is blocking this new one (same for perl-Class-Data-Inheritable); what can be done about that?

Currently you need to edit the update, select stable as request and save the update to push it to stable (I just did it).

Metadata Update from @pghmcfc:
- Issue set to the milestone: Fedora 21 Alpha

7 years ago

Login to comment on this ticket.

Metadata