Due to the nature of private Qt libraries, which are built within the PySide6 wheel, there is always the risk of them appearing in the Requires / Provides section of the package. We don't want the private libraries to leak to the Requires / Provides sections for several reasons, mainly because it will confuse RPM's dependency resolution, if other packages require Qt6 ibraries. We need to make sure in every release that the Provides / Requires section is not radically different from the following:
Due to the nature of private Qt libraries, which are built within the PySide6 wheel, there is always the risk of them appearing in the Requires / Provides section of the package. We don't want the private libraries to leak to the Requires / Provides sections for several reasons, mainly because it will confuse RPM's dependency resolution, if other packages require Qt6 ibraries. We need to make sure in every release that the Provides / Requires section is not radically different from the following:
Provides
Requires
Having an automated way to check this would be even more preferable.