As a user, I can import RPM package which has rich dependencies in *Requires*

[dparalen]

Description

RPM content can have rich/boolean dependencies specified in e.g the Requires field.
The following use cases should nevertheless be all possible with such content:

• a repository can be synchronized with a rich dependency content feed
• rich dependency content can be uploaded into a repository
• pulp-admin shows the Requires field for both the simple- and rich-dependency content
• a repository containing rich dependency content can be copied 🍐
• a repository containing rich dependency content can be published
• a consumer can be fed from a Pulp repository containing rich dependency content
• a consumer, such as dnf, can process rich dependencies expressed in the content

Notes

🪲 https://pulp.plan.io/issues/3339
🪲 https://pulp.plan.io/issues/3715

🍐 Pulp not processing rich dependencies, recursive content copies won't work properly until pulp/pulp_rpm#1122 gets merged.

[rochacbruno]

a consumer can be fed from a Pulp repository containing rich dependency content

We are testing the installation of packages from a Pulp repository having rick/weak dependencies, is that meeting the requirement? can we consider this issue closed?