Re: [Rpm-maint] [rpm-software-management/rpm] BUG: $1 and $2 arguments passed to scriptlets go awry for renamed package upgrades (#474)

Closed #474. -- 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/issues/474#event-1800039344___ Rpm-maint mailing list Rpm-maint@lists.rpm

Re: [Rpm-maint] [rpm-software-management/rpm] BUG: $1 and $2 arguments passed to scriptlets go awry for renamed package upgrades (#474)

No. Scriptlets use $1 in %preun/%postun to determine whether a package is being upgraded or erased: name those two distinct logic paths however you choose. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/r

Re: [Rpm-maint] [rpm-software-management/rpm] BUG: $1 and $2 arguments passed to scriptlets go awry for renamed package upgrades (#474)

You mean erase-while-obsoleting? -- 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/issues/474#issuecomment-407046997___ Rpm-maint mailin

[Rpm-maint] [rpm-software-management/rpm] BUG: $1 and $2 arguments passed to scriptlets go awry for renamed package upgrades (#474)

>From >https://stackoverflow.com/questions/48070042/how-to-detect-upgrade-when-an-rpm-that-obsoletes-another-rpm-is-being-installed The practice of adding a Provides: oldname to satisfy dependencies when renaming a package has unintended consequences for the package count arguments passed to sc