<p><a href="https://github.com/n3npq" class="user-mention">@n3npq</a> 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.</p>
<p>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?</p>
<p>Thanks</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/rpm-software-management/rpm/issues/270#issuecomment-316898358">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb8085RMoKCE_jIKLxzkUbhpg1prtVEks5sQCZ0gaJpZM4Oeptu">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb801GGhMu6UYloQxaNCNSbjYX9SdIFks5sQCZ0gaJpZM4Oeptu.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/rpm-software-management/rpm/issues/270#issuecomment-316898358"></link>
  <meta itemprop="name" content="View Issue"></meta>
</div>
<meta itemprop="description" content="View this Issue on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rpm-software-management/rpm","title":"rpm-software-management/rpm","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rpm-software-management/rpm"}},"updates":{"snippets":[{"icon":"PERSON","message":"@lucasdemarchi in #270: @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.\r\n\r\nMaybe 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?\r\n\r\nThanks"}],"action":{"name":"View Issue","url":"https://github.com/rpm-software-management/rpm/issues/270#issuecomment-316898358"}}}</script>