Yeah, traditionally --install is not allowed to erase anything, which (to me at
least) makes sense most of the time. But like you note, with --replacepkgs the
old header will be removed no matter what, so an erase element does seem a sane
thing to do. It's a behavior change that might cause
It's trivial to change the code to also add an erase element for --install if
the NEVRA is the same. (It's actually also what libsolv expects). I didn't do
it because I read in some old thread that you don't like erases with 'rpm
--install'. (The old header will get replaced anyway, so an erase
Just for the record, this also fixes the case where a package with
self-conflict fails with -Uvh --replacepkgs style reinstall
(https://bugzilla.redhat.com/show_bug.cgi?id=1693212)
As expected it doesn't deal with -ivh --replacepkgs in the same case (of
self-conflicts), which is a rather
Thanks for the patch!
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/770#issuecomment-513821424___
Rpm-maint mailing list
Merged #770 into master.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/770#event-2500087756___
Rpm-maint mailing list
