| |
@@ -432,8 +432,10 @@
|
| |
def test_fill_in_rpms_list(self):
|
| |
self._add_test_rpm("dhcp-libs-12:4.3.5-5.module_2118aef6.x86_64", "dhcp")
|
| |
self._add_test_rpm("dhcp-libs-12:4.3.5-5.module_2118aef6.i686", "dhcp")
|
| |
+ self._add_test_rpm("dhcp-libs-12:4.3.5-5.module_2118aef6.s390x", "dhcp")
|
| |
self._add_test_rpm("perl-Tangerine-12:4.3.5-5.module_2118aef6.x86_64", "perl-Tangerine")
|
| |
self._add_test_rpm("perl-Tangerine-12:4.3.5-5.module_2118aef6.i686", "perl-Tangerine")
|
| |
+ self._add_test_rpm("perl-Tangerine-12:4.3.5-5.module_2118aef6.s390x", "perl-Tangerine")
|
| |
|
| |
mmd = self.cg.module.mmd()
|
| |
mmd = self.cg._fill_in_rpms_list(mmd, "x86_64")
|
| |
The original Pungi code, on which MBS code is based on, always passed only RPMs
with valid architectures to further decide if their subset should end up in a
final modulemd file.
In MBS, we pass RPMs with all architectures and there was no code to actually filter
out the RPMs which are from architectures which should never end up in a final MMD.
By an lucky accident, the current code was able to filter out multilib architectures, so
for example "i686" did not appear in "x86_64" final MMD. But for example "s390x" RPMs
appeared in the x86_64 final MMD and we had no tests for this scenario...
This commit checks that RPMs for completely different architectures will never
be considered to be included in a final MMD.