Under certain circumstances, an attempt to use the RepoStorage API may have failed with an AttributeError. With this update, this error has been fixed, and the RepoStorage API can now be used as expected.

Description of problem:
Pulp uses RepoStorage to accumulate repos and their package sacks outside of YumBase. Due to this certain attributes aren't set (which are set in yumBase) that RepoStorage assumes they are present. The error we see is:
AttributeError: DepSolver instance has no attribute '_override_sigchecks'
James already fixed this in fedora rawhide. Patch needs to be backported.

Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Previously, the Pulp application used the RepoStorage API directly outside of the YumBase class, therefore certain attributes were not set as expected. As a consequence, users experienced attributes errors when using the Pulp server to manage their software repositories. With this update, RepoStorage has been modified to include the condition that verifies and sets these attributes. These attributes errors occur no more when using Pulp.

Technical note updated. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Diffed Contents:
@@ -1 +1 @@
-Previously, the Pulp application used the RepoStorage API directly outside of the YumBase class, therefore certain attributes were not set as expected. As a consequence, users experienced attributes errors when using the Pulp server to manage their software repositories. With this update, RepoStorage has been modified to include the condition that verifies and sets these attributes. These attributes errors occur no more when using Pulp.+Under certain circumstances, an attempt to use the RepoStorage API may have failed with an AttributeError. With this update, this error has been fixed, and the RepoStorage API can now be used as expected.

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-2011-1702.html

Note

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