Description of problem: An optimization that went into ~3.2.19 was that you could "yum remove X" without updating all of the repositories metadata. However a bug has just been found when releasing 3.2.20 upstream that this means if you have: yum shell <<EOL remove X install X run EOL ...where previous yum versuions would work fine, yum-3.2.19 will now fail on the "install" operation because the repository data isn't setup. The fix is below, and just 2 lines. Version-Release number of selected component (if applicable): yum-3.2.19-10 How reproducible: always Additional info: diff --git a/yum/depsolve.py b/yum/depsolve.py index 25eb0e6..579e7a1 100644 --- a/yum/depsolve.py +++ b/yum/depsolve.py @@ -91,6 +91,8 @@ class Depsolve(object): yet""" if self._tsInfo != None and self._ts != None: + if not remove_only and self._tsInfo.pkgSack is None: + self._tsInfo.setDatabases(self.rpmdb, self.pkgSack) return if not self.conf.installroot:
This bugzilla has Keywords: Regression. Since no regressions are allowed between releases, it is also being proposed as a blocker for this release. Please resolve ASAP.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0176.html