Story #3847
Updated by milan over 6 years ago
Pulp lacks resolving of "RPM weak forward dependency":http://rpm.org/user_doc/dependencies.html @Recommends@ during content association in case of e.g recursively copying RPMs between repositories, which by default is respected by @dnf@ A content gap might therefore be induced on a consumer machine when installing from a repository containing just the recursive-copy calculated dependencies of an RPM unit. This isn't a breaking change as "by definition, weak dependencies missing don't cause an unit to break":https://fedoraproject.org/wiki/Packaging:WeakDependencies#Weak_dependencies repositories. The very weak/hint weak @Suggests@ field is out of scope as hints are by default not processed by @dnf@. Bot well as bot the weak and very weak/hint weak backward fields: @Supplements@ and @Enhances@ are out of scope too. @Enhances@, respectively. h3. Implementation * the "RPM model":https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/db/models.py#L743,#L772 needs to track the following "forward" weak dependency field @Recommends@ * the "primary XML repo metadata parsing code":https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/importers/yum/repomd/primary.py has to be updated in order to populate the @Recommends@ field h3. Notes * the RPM content upload code needn't be updated as it "reuses the XML parsing code":https://github.com/pulp/pulp_rpm/blob/2-master/plugins/pulp_rpm/plugins/importers/yum/upload.py#L375,#L384 * the backwards dependencies needn't be processed because the Pulp workflow is closer to a repo closure calculation than to an actual content installation * the processing of the @Recommends@ field is going to be "handled thru @libsolv@":https://github.com/pulp/pulp_rpm/pull/1122/files#diff-cfe0bb646220ae499249edd39626a096R232 once that PR lands
.