Fix bug in package-listing start script

Change af89ef784234e7b89984d5b2995fc6d29b6d8c34 introduced a bug where
we don't make sure that the package-listing.sh script is executable
before calling it during system startup. This means that we are no
longer currently producing the needed listing start file for instances
to be able to diff against to give us a view of package changes.

Change-Id: Iea2f0b07cdf10f7819072bcb00596bdeda4665df
Signed-off-by: Andrew Grimberg <agrimberg@linuxfoundation.org>

diff --git a/jenkins-init-scripts/package-listing.sh b/jenkins-init-scripts/package-listing.sh
index 93a2e74..b2c9784 100755 (executable)
--- a/jenkins-init-scripts/package-listing.sh
+++ b/jenkins-init-scripts/package-listing.sh
@@ -16,4 +16,6 @@
 
 jjb_init_scripts="$(dirname "$0")/../shell"
 
+# Make sure that the package listing script is executable
+chmod +x "$jjb_init_scripts/package-listing.sh"
 "$jjb_init_scripts/package-listing.sh"