[Rpm-maint] [rpm-software-management/rpm] rpm core in rpm.daily (Issue #2612)

[Panu Matilainen]

Yes, the system as a whole cannot be considered working normally during (major) upgrades.

I don't remember offhand whether there was a soname bump between those versions but it doesn't take anything more exotic than that. Berkeley DB (which still was the default in 4.15) has it's own notorious quirks between versions, but degraded to read-only support (if built in at all) in 4.17 so that's not going to work in any case without arranging for some kind of rpmdb migration.

It's the responsibility of distro maker to run major upgrades in a suitably isolated environment and arrange any database migrations etc as necessary.

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

Message ID: <rpm-software-management/rpm/issues/2612/1676767474 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20230813/44d9ba98/attachment.html>