[Rpm-maint] [rpm-software-management/rpm] RPM db does not upgrades when upgrading from `4.11.3` to `4.18.2` (Issue #3420)

[Manuel Cano]

**Describe the bug**
Hi team,

I'm working on a Centos 7 Docker container which brings RPM version `4.11.3`. I'm able to cover the required deps and install the `4.18.2` version, but I can not migrate the native rpm db to the installed one and the newer version never knows about the already installed packages.

**To Reproduce**

* Steps to reproduce the behavior:

On a Centos 7 host, install the RPM `4.18.2` with the following command (_having the required deps covered_):

```command
git clone https://github.com/rpm-software-management/rpm.git --branch rpm-4.18.2-release --single-branch && \
    cd rpm && ./autogen.sh && make -j$(nproc) && make install && cd / && rm -rf rpm*
```

Then I try to migrate the installed packages information with the native RPM version as follows:

```command
mkdir -p /usr/local/var/lib/rpm && cp /var/lib/rpm/Packages /usr/local/var/lib/rpm/Packages && \
    /usr/local/bin/rpm --rebuilddb
```

But when querying the installed packages list, it seems to not be updated:
```command
[root at a0607f3a3f16 /]# /usr/local/bin/rpm --version
RPM version 4.18.2
[root at a0607f3a3f16 /]# /usr/local/bin/rpm -qa
```

**Expected behavior**
This procedure has been working for me if the new installed RPM version was the `4.15.1`. With this version the packages list is upgraded and the new version knows the previously installed packages.

Is it expected to not work with the newer mentioned version?

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/3420
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/issues/3420 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20241031/2c5cd852/attachment.html>