From acab2f7c338f245baa7e5d9dca57476d12d863bf Mon Sep 17 00:00:00 2001 From: Brett Smith Date: Fri, 26 Feb 2016 18:20:41 -0500 Subject: [PATCH] 8371: Rails postrm only fires after removing last RPM. This prevents removing the package files when the postrm script is called for the old version of a package after doing an upgrade. RPM post- scripts are called with $1 as the number of versions of the package currently installed on the system. 0 means the last version has been removed. We only want to remove files in that case. --- jenkins/rails-package-scripts/postrm.sh | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/jenkins/rails-package-scripts/postrm.sh b/jenkins/rails-package-scripts/postrm.sh index 8c45d2f8ce..2d63f0b9e8 100644 --- a/jenkins/rails-package-scripts/postrm.sh +++ b/jenkins/rails-package-scripts/postrm.sh @@ -14,7 +14,7 @@ purge () { if [ "$1" = 'purge' ]; then # This is a debian-based system and purge was requested purge -elif [ "$1" = "0" ] || [ "$1" = "1" ] || [ "$1" = "2" ]; then +elif [ "$1" = "0" ]; then # This is an rpm-based system, no guarantees are made, always purge # Apparently yum doesn't actually remember what it installed. # Clean those files up here, then purge. -- 2.30.2