Learn more about these different git repos.
Other Git URLs
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 unretire perl-Class-Trigger and re-introduce it to EPEL-6 with a zero release number as per the guidance at https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
it is unretired, unblocked imported and built. I hoped to reduce the conflict with RHEL but since it needs to go through bodhi first, a fast build does not help. Please prepare an update for it.
The unblocking of perl-Class-Trigger has resulted in the re-release of the original EPEL-6 package, which was a complete clone of the RHEL-6 package. This is now blocking the release to stable of the re-built package with the "0"-prefixed release tag (bodhi complains about the upgrade path). Can the perl-Class-Trigger-0.13-2.1.el6 package be untagged?
untagged perl-Class-Trigger-0.13-2.1.el6 and perl-Class-Trigger-0.14-2.el6 from dist-6E-epel.
I noticed the package is currently orphaned, please claim it.
Metadata Update from @pghmcfc: - Issue set to the milestone: Fedora 21 Alpha
Login to comment on this ticket.