<p>If you are hitting this problem "Hundreds. Of. Times. A. Day.", then there is a<br>
mismatch between what you are expecting, and what is actually implemented in RPM.</p>
<p>While I am not responsible (or able to even submit an acceptable patch to rpm.org, sigh),<br>
I can certainly diagnose your problems, and suggest better/alternative usage for RPM.</p>
<p>I can also <em>easily</em> back port the core fix to the problem reported here, implemented years ago @rpm5.org:</p>
<ul>
<li>when DB_RUNRECOVERY is returned opening a BDB dbenv, then do the recovery by setting a flag, and repeating the open one time, thereby running recovery.</li>
</ul>
<p>That takes care of the majority of "automated" problems. Other problems exist if using NETSNMP+RPM, or if using GDB+RPM, usage cases that RPM rpmdb wasn't ever really<br>
designed for.</p>
<p>Again, I can easily generate the patch for @rpm.org code: just no patch I submit from<br>
@rpm5.org will <em>EVER</em> be acceptable @rpm.org AFAIK (and there are many public statements to<br>
that effect from @rpm.org and @redhat.com devels).</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/232#issuecomment-308304796">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb807U4nLs3C31CfeFmpPAeQUxLW3ADks5sD0qTgaJpZM4NzFoB">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb808Fy11s4UTnZBCYn8qc2uAsEu78uks5sD0qTgaJpZM4NzFoB.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/232#issuecomment-308304796"></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":"@n3npq in #232: If you are hitting this problem \"Hundreds. Of. Times. A. Day.\", then there is a\r\nmismatch between what you are expecting, and what is actually implemented in RPM.\r\n\r\nWhile I am not responsible (or able to even submit an acceptable patch to rpm.org, sigh),\r\nI can certainly diagnose your problems, and suggest better/alternative usage for RPM.\r\n\r\nI can also *easily* back port the core fix to the problem reported here, implemented years ago @rpm5.org:\r\n\r\n* when DB_RUNRECOVERY is returned opening a BDB dbenv, then do the recovery by setting a flag, and repeating the open one time, thereby running recovery.\r\n\r\nThat takes care of the majority of \"automated\" problems. Other problems exist if using NETSNMP+RPM, or if using GDB+RPM, usage cases that RPM rpmdb wasn't ever really\r\ndesigned for.\r\n\r\nAgain, I can easily generate the patch for @rpm.org code: just no patch I submit from\r\n@rpm5.org will *EVER* be acceptable @rpm.org AFAIK (and there are many public statements to\r\nthat effect from @rpm.org and @redhat.com devels)."}],"action":{"name":"View Issue","url":"https://github.com/rpm-software-management/rpm/issues/232#issuecomment-308304796"}}}</script>