{"action":"closed","issue":{"url":"https://api.github.com/repos/rpm-software-management/rpm/issues/474","repository_url":"https://api.github.com/repos/rpm-software-management/rpm","labels_url":"https://api.github.com/repos/rpm-software-management/rpm/issues/474/labels{/name}","comments_url":"https://api.github.com/repos/rpm-software-management/rpm/issues/474/comments","events_url":"https://api.github.com/repos/rpm-software-management/rpm/issues/474/events","html_url":"https://github.com/rpm-software-management/rpm/issues/474","id":343576594,"node_id":"MDU6SXNzdWUzNDM1NzY1OTQ=","number":474,"title":"BUG: $1 and $2 arguments passed to scriptlets go awry for renamed package upgrades","user":{"login":"n3npq","id":643926,"node_id":"MDQ6VXNlcjY0MzkyNg==","avatar_url":"https://avatars3.githubusercontent.com/u/643926?v=4","gravatar_id":"","url":"https://api.github.com/users/n3npq","html_url":"https://github.com/n3npq","followers_url":"https://api.github.com/users/n3npq/followers","following_url":"https://api.github.com/users/n3npq/following{/other_user}","gists_url":"https://api.github.com/users/n3npq/gists{/gist_id}","starred_url":"https://api.github.com/users/n3npq/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/n3npq/subscriptions","organizations_url":"https://api.github.com/users/n3npq/orgs","repos_url":"https://api.github.com/users/n3npq/repos","events_url":"https://api.github.com/users/n3npq/events{/privacy}","received_events_url":"https://api.github.com/users/n3npq/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-07-23T10:30:56Z","updated_at":"2018-08-21T12:41:26Z","closed_at":"2018-08-21T12:41:26Z","author_association":"CONTRIBUTOR","body":"From https://stackoverflow.com/questions/48070042/how-to-detect-upgrade-when-an-rpm-that-obsoletes-another-rpm-is-being-installed\r\n\r\nThe practice of adding a Provides: oldname to satisfy dependencies when renaming a package has unintended consequences for the package count arguments passed to scriptlets: the count is based on the package N, not the Provides: oldname.\r\n\r\nRather than trying to detect package renaming -- a rather rare event -- and adjust the arguments passed to scriptlets, I'd suggest that the better fix would be to devise a means to differentiate between erase-while-upgrading and erase-while-removing that is by far the most common need to test package counts.\r\n"}}
{"actor":{"display_login":"n3npq"}}