You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(Moved from rpminspect/rpminspect#1205 - please let me know if this still isn't the right place to report it.)
https://bugzilla.redhat.com/show_bug.cgi?id=2174300 is a test failure caused by conflicts in tbb-doc.i686 and tbb-doc.x86_64, however that is not a multilib package, so users can never install the i686 package on an x86_64 without downloading it manually (in which case it's their own fault for trying).
If Fedora CI passed the multilib-readiness info down to rpmdeplint then the particular test could be executed only when it makes sense. i.e. when the packages are both rpesent in the multilib repo and are actually available for users to install in parallel.
In this case, the docs package should probably just be noarch, and it wouldn't be an issue, but that's not possible due to spurious differences in the docs when generated on each arch. As a workaround I've made the tbb-docs.i686 conflict with tbb-docs.x86_64 to prevent them being tested for parallel installs.
The text was updated successfully, but these errors were encountered:
(Moved from rpminspect/rpminspect#1205 - please let me know if this still isn't the right place to report it.)
https://bugzilla.redhat.com/show_bug.cgi?id=2174300 is a test failure caused by conflicts in tbb-doc.i686 and tbb-doc.x86_64, however that is not a multilib package, so users can never install the i686 package on an x86_64 without downloading it manually (in which case it's their own fault for trying).
If Fedora CI passed the multilib-readiness info down to rpmdeplint then the particular test could be executed only when it makes sense. i.e. when the packages are both rpesent in the multilib repo and are actually available for users to install in parallel.
In this case, the docs package should probably just be noarch, and it wouldn't be an issue, but that's not possible due to spurious differences in the docs when generated on each arch. As a workaround I've made the tbb-docs.i686 conflict with tbb-docs.x86_64 to prevent them being tested for parallel installs.
The text was updated successfully, but these errors were encountered: