Bug 825145 - Please backport the reloadConfig() method from rpm 4.10's Python API
Please backport the reloadConfig() method from rpm 4.10's Python API
Product: Fedora
Classification: Fedora
Component: rpm (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Fedora Packaging Toolset Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-05-25 04:41 EDT by Mathieu Bridon
Modified: 2013-08-01 03:56 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-08-01 03:55:50 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
backport of reloadConfig() (from master) (1.52 KB, patch)
2012-05-25 04:41 EDT, Mathieu Bridon
no flags Details | Diff

  None (edit)
Description Mathieu Bridon 2012-05-25 04:41:54 EDT
Created attachment 586801 [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- branch, as well as on the Fedora 16 and Fedora 17 package.

This bug is about Fedora 17, but I'd love to have it in Fedora 16 as well, do you want a separate bug report?
Comment 1 Mathieu Bridon 2012-06-26 06:05:44 EDT
Comment 2 Fedora End Of Life 2013-07-03 22:17:12 EDT
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2013-08-01 03:56:00 EDT
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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