Red Hat Bugzilla – Bug 446098
PackageKit interpolates yum config variables when modifying repo files
Last modified: 2008-11-17 12:52:25 EST
When you modify a repo with PackageKit (by using gpk-repo, for instance), it
interpolates all of the yum config variables ($releasever, $basearch, etc) in
the repo file. This isn't a good idea and can lead to some subtle and nasty repo
An example: if you have a repo with a URL like:
If you disable it while $releasever is 8.92, the URL will be rewritten as:
If you then re-enable it once the release has been updated to 9, the repo will
still be unusable - releases/8.92/i386 still doesn't exist.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
All we do is:
repo = self.yumbase.repos.getRepo(repoid)
if enable == 'false':
if not repo.isEnabled():
So we don't parse the strings at all. Re-assigning to yum.
I am testing a fix at the monent, to make repo.disablePersistent() and
repo.enablePersistent() work without merging all the yum config vars.
yum-3.2.17-1.fc9 has been submitted as an update for Fedora 9
yum-3.2.17-2.fc8 has been submitted as an update for Fedora 8
yum-3.2.17-2.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
yum-3.2.18-1.fc8 has been submitted as an update for Fedora 8
yum-3.2.19-1.fc8 has been submitted as an update for Fedora 8.
yum-3.2.19-3.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 447645 has been marked as a duplicate of this bug. ***