Thanks for identifying the specific checkin.
RPM4 has changed the definition of what is called an "immutable region" in a
signature header.
An "immutable region" is identified with an index/data length as well as a
trailer which duplicates
the same information. The test for an exact_match in the commit has altered the
definition
of an "immutable region" and appears to have introduced an incompatibility.
If you are going to handle Yocto packages built by RPM5 using RPM4 sanely, your
best bet is to back out that specific "exact_match" change. You will be no
worse off than you were before, the test is rather arcane and anal retentive.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/270#issuecomment-316893255
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
