Created attachment 586802 [details] backport of reloadConfig() (from master) Description of problem: From a discussion today in #fedora-devel: <Panu> just fyi: using the rpm api for parsing specs has some not-so-obvious [... <Panu> the spec parse can and will affect the global rpm macro "environment" - eg macros defined by the spec will remain there after parsing <Panu> ...and that in turn can and does affect results if you parse more than one spec (or just the same spec more than once) per process lifetime [... snip ...] <Panu> rpm 4.10 exports reloadConfig() function to python that'll reset the configuration, but for older versions the answer is "you dont want to do it" I'm afraid <Panu> mind you, reloadConfig() is something that would be fairly trivial to backport to rpm 4.8 and 4.9 (so rhel-6 and upwards) I'm attaching a patch which applies on top of upstream's rpm-4.8.x branch, as well as on the latest RHEL 6 srpm.
devel_ack, the patch is non-intrusive and useful (for one, its required for parsing several specs within a single process reliably, so kinda related to bug 664427)
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.
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.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0461.html