Bug 680661

Summary: [patch] Add option to enable/disable the createrepo command in local.py
Product: Red Hat Enterprise Linux 6 Reporter: Alexander Todorov <atodorov>
Component: yum-utilsAssignee: Valentina Mukhamedzhanova <vmukhame>
Status: CLOSED WONTFIX QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0CC: jzeleny, ksrot, rvokal, tcallawa, tlavigne
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-25 14:07:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 680662    
Attachments:
Description Flags
enable/disable createrepo if desired none

Description Alexander Todorov 2011-02-26 19:42:29 UTC
Created attachment 481181 [details]
enable/disable createrepo if desired

Description of problem:
This patch against latest git code adds a second 'enabled' parameter under the [createrepo] section. If false (true by default) the _rebuild() function will return immediately. 

This can be useful on a large local repository where metadata is generated via cron when the system is not in use or idle. Currently metadata is regenerated whenever new RPMs are downloaded.

Comment 1 James Antill 2011-03-22 21:23:07 UTC
As it's an internal only RFE atm. ... moving to 6.2.

Comment 5 James Antill 2012-06-26 19:35:48 UTC
 Might call it something other than enabled. Also not upstream, but it doesn't seem like a terrible feature (and it's simple).

Comment 6 RHEL Program Management 2012-07-10 06:48:12 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 7 RHEL Program Management 2012-07-11 02:12:03 UTC
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 8 RHEL Program Management 2012-09-07 05:21:10 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 11 RHEL Program Management 2013-10-14 01:09:46 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 13 Valentina Mukhamedzhanova 2016-07-25 14:07:24 UTC
Red Hat Enterprise Linux version 6 is entering the Production 2 phase of its lifetime and this bug doesn't meet the criteria for it, i.e. only high severity issues will be fixed. Please see https://access.redhat.com/support/policy/updates/errata/ for further information.

Please feel free to open this request against Red Hat Enterprise Linux 7.