On 2021/03/16 11:40, Andrei Borzenkov wrote:
And what exactly is not clear in this message? That my entire rpm database had been wiped and needed restoration from a user-backup to recover from suse-upgrade damage, again. Most users wouldn't have such a backup, so for most users, that would be an entire wipe.
It's one reason why most of my scripts/programs take me so long these days, as 75-80% of the script is checking for error conditions and telling whoever is running the program (often me) how to fix it, cuz I don't remember every little detail when something breaks years later. Now I don't know what I should do about this, since something will likely try to upgrade it again and will likely mess it up again. Why did rpm have to change locations and source dialects and compression encoding? (all at the same time, from my perspective).
Mon Nov 20 14:50:53 UTC 2017 - mpluskal@suse.com
- Move update alternatives database to new location
Warning: rpm-4.14.1-lp151.13.10.x86_64.rpm %posttrans script failed (returned 1) Problem occured during or after installation or removal of packages: Failed to cache rpm database (1). Please see the above error message for a hint. ----------------
Speaking of weird error messages
Tried to install rpm from leap 15.1... Rats; yeah, have backups won't travel much...