RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 608594 - query about lack of EL-6 branch for perl-Module-Find
Summary: query about lack of EL-6 branch for perl-Module-Find
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: perl-Module-Find
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: beta
: ---
Assignee: perl-maint-list
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-28 08:56 UTC by Mark Chappell
Modified: 2010-09-15 06:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-09-15 06:51:26 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Mark Chappell 2010-06-28 08:56:41 UTC
I'm chasing down the dependency tree for RT3 in EL-6, for some reason perl-Module-Find doesn't have an EL-6 branch.

https://koji.fedoraproject.org/koji/getfile?taskID=2273062&name=root.log

Is this because you're not interested in maintaining it any more or is there another reason?  I'm happy to (co)maintain EL branches if this would help.

Comment 1 Mark Chappell 2010-06-28 16:41:24 UTC
More confusingly, it's actually only showing up for x86_64.

Comment 3 RHEL Program Management 2010-06-28 17:02:55 UTC
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.

Comment 5 Matthew Booth 2010-06-30 13:11:41 UTC
Is this bug intended to be against RHEL or EPEL?

Comment 6 Mark Chappell 2010-06-30 15:10:20 UTC
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 ?

Comment 7 Mark Chappell 2010-06-30 15:16:34 UTC
"a" should read, "was this a deliberate exclusion from ppc and i386 in RHEL 6 ?"

Comment 8 Bill Nottingham 2010-06-30 16:17:14 UTC
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.

Comment 9 RHEL Program Management 2010-07-15 14:26:17 UTC
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. **

Comment 10 Marcela Mašláňová 2010-07-19 12:02:29 UTC
I suppose you should sent this request to EPEL list and find out how will be solved these issues.

Comment 11 Mark Chappell 2010-07-19 12:52:17 UTC
(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)

Comment 12 Marcela Mašláňová 2010-07-20 07:09:09 UTC
I suppose someone working more on EPEL was generating a list of packages, which changed. Maybe spot could help?

Comment 13 Mark Chappell 2010-09-14 15:49:58 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.