<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Posts on Piotr Orzechowski</title><link>https://orzechowski.tech/posts/</link><description>Recent content in Posts on Piotr Orzechowski</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 28 Oct 2021 00:20:20 +0200</lastBuildDate><atom:link href="https://orzechowski.tech/posts/index.xml" rel="self" type="application/rss+xml"/><item><title>OpenSUSE Tumbleweed and rpmdb error</title><link>https://orzechowski.tech/posts/opensuse-tumbleweed-and-rpmdb-error/</link><pubDate>Sat, 16 May 2020 03:57:42 +0200</pubDate><guid>https://orzechowski.tech/posts/opensuse-tumbleweed-and-rpmdb-error/</guid><description>&lt;h2 id="the-problem"&gt;
 The Problem
 &lt;a class="heading-link" href="#the-problem"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;So yeah, during the last &lt;code&gt;sudo zypper dup&lt;/code&gt; I saw some weird &lt;code&gt;rpm&lt;/code&gt; error (each &lt;code&gt;&amp;lt;num&amp;gt;&lt;/code&gt; was actually a different positive integer):&lt;/p&gt;
&lt;div class="highlight"&gt;&lt;pre tabindex="0" style="color:#e7e9db;background-color:#2f1e2e;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;error: rpmdbNextIterator: skipping h# &amp;lt;num&amp;gt; blob size(-&amp;lt;num&amp;gt;): BAD, &amp;lt;num&amp;gt; + &amp;lt;num&amp;gt; * il(&amp;lt;num&amp;gt;) + dl(-&amp;lt;num&amp;gt;)
&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;As it turned out, this probably means corrupted &lt;code&gt;rpm&lt;/code&gt; database (rpm db).
Well, no luck this time&amp;hellip;&lt;/p&gt;
&lt;p&gt;Both &lt;code&gt;sudo zypper ve&lt;/code&gt; and &lt;code&gt;sudo rpm -qa&lt;/code&gt; did not show anything alarming, though.
But the error was logged.&lt;/p&gt;</description></item></channel></rss>