@n3npq thanks for looking into this. This rpm may be the only one I'll have to
deal with and I can regenerate it using rpm4 reasonably easy. However I thought
it was important to notify upstream since when other distros update they may
face similar problems since they don't have much control over what .rpm users
are going to install.
Maybe an option to rpm to allow it to continue even if the "exact_match" test
fails? Or changing this to be a warning rather than an error since it causes
compatibility issues?
Thanks
--
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-316898358
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
