Bug 608594
Summary: | query about lack of EL-6 branch for perl-Module-Find | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Mark Chappell <tremble> |
Component: | perl-Module-Find | Assignee: | perl-maint-list |
Status: | CLOSED NOTABUG | QA Contact: | BaseOS QE - Apps <qe-baseos-apps> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 6.0 | CC: | mbooth, notting, tcallawa, tremble |
Target Milestone: | beta | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-15 06:51:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mark Chappell
2010-06-28 08:56:41 UTC
More confusingly, it's actually only showing up for x86_64. This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux major release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Major release. This request is not yet committed for inclusion. Is this bug intended to be against RHEL or EPEL? Initially it was filed against the EPEL5 branch of perl-Module-Find I was confused as to why it hadn't branched from EPEL-5 into EPEL-6. Then I found that the reason it didn't branch was because RHEL-6 includes perl-Module-Find.noarch but ONLY in the x86_64 repositories. Because it's a noarch package we wouldn't generally branch it for EPEL since it's in RHEL. a) was this deliberate from ppc and i386 in RHEL 6 ? b) any chance it could be added to the ppc/i386 branches ? "a" should read, "was this a deliberate exclusion from ppc and i386 in RHEL 6 ?" perl-Module-Find is a build requirement of one of the only-on-x86_64 virt tools... it's essentially an implementation detail. It's intentional that it's only on the platform where it's required. Now, we do need to find a good solution as to how to handle this between RHEL and EPEL. That's still being worked on. This issue has been proposed when we are only considering blocker issues in the current Red Hat Enterprise Linux release. It has been denied for the current Red Hat Enterprise Linux release. ** If you would still like this issue considered for the current release, ask your support representative to file as a blocker on your behalf. Otherwise ask that it be considered for the next Red Hat Enterprise Linux release. ** I suppose you should sent this request to EPEL list and find out how will be solved these issues. (In reply to comment #10) > I suppose you should sent this request to EPEL list and find out how will be > solved these issues. EPEL are basically just going to rebuild the RHEL-6 SRPMS. Are you aware of any mechanism available for monitoring Red Hat releases for *only* certain packages, rather than all Errata? (So we can put through the appropriate rebuilds) I suppose someone working more on EPEL was generating a list of packages, which changed. Maybe spot could help? We've now generated some scripts for keeping an eye on EPEL pkgs vs RHEL pkgs so I'm happy for you to close off this ticket. |