diskimage-builder/diskimage_builder/elements/ubuntu/pre-install.d/00-remove-apt-xapian-index

#!/bin/bash

if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then
    set -x
fi
set -eu
set -o pipefail

# This package is broken and causes real issues on update:
# https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1227420
apt-get --yes remove apt-xapian-index || :
/bin/bash all the things. Since we are using bash syntax in some of the element fragments, we should make sure we use bash for all of them, so that things don't break on systems where /bin/sh != /bin/bash. Change-Id: If2f043c57aa4e1492b7f9839213ef6123f683612 2013-11-07 04:25:34 +00:00			`#!/bin/bash`
set -e all the things Using set -e in all of our scripts will prevent some subtle bugs from slipping in, and will allow us to enforce use of set -e with tooling. This change also adds -u and set -o pipefail in the less complex scripts where it is unlikely to cause problems. A follow-up change will enable those options in the complex scripts so that if it breaks something it can be reverted easily. Change-Id: I0ad358ccb98da7277a0ee2e9ce8fda98438675eb 2014-03-29 03:28:22 +00:00
Standarise tracing for scripts There is a wide variety of tracing options through the various shell scripts. Some use "set -eux", others explicity set xtrace and others do nothing. There is a "-x" option to bin/disk-image-create but it doesn't flow down to the many scripts it calls. This adds a global integer variable set by disk-image-create DIB_DEBUG_TRACE. All scripts have a stanza added to detect this and turn on tracing. Any other tracing methods are rolled into this. So the standard header is --- if [ "${DIB_DEBUG_TRACE:-0}" -gt 0 ]; then set -x fi set -eu set -o pipefail --- Multiple -x options can be specified to dib-create-image, which increases the value of DIB_DEBUG_TRACE. If script authors feel their script should only trace at higher levels, they should modify the "-gt" value. If they feel it should trace by default, they can modify the default value also. Changes to pachset 16 : scripts which currently trace themselves by default have retained this behaviour with DIB_DEBUG_TRACE defaulting to "1". This was done by running [1] on patch set 15. See the thread beginning at [2] dib-lint is also updated to look for the variable being matched. [1] https://gist.github.com/ianw/71bbda9e6acc74ccd0fd [2] http://lists.openstack.org/pipermail/openstack-dev/2014-November/051575.html Change-Id: I6c5a962260741dcf6f89da9a33b96372a719b7b0 2014-09-04 04:56:29 +00:00			`if [ ${DIB_DEBUG_TRACE:-0} -gt 0 ]; then`
			`set -x`
			`fi`
set -e all the things Using set -e in all of our scripts will prevent some subtle bugs from slipping in, and will allow us to enforce use of set -e with tooling. This change also adds -u and set -o pipefail in the less complex scripts where it is unlikely to cause problems. A follow-up change will enable those options in the complex scripts so that if it breaks something it can be reverted easily. Change-Id: I0ad358ccb98da7277a0ee2e9ce8fda98438675eb 2014-03-29 03:28:22 +00:00			`set -eu`
			`set -o pipefail`

Remove apt-xapian-index from ubuntu cloud images This package recently caused us some very large headaches when it was updated for a security issue. It is completely unnecessary and should be removed. Note that we have recommended that it be removed from the cloud images in launchpad bug #1227425. fixes bug #1227420 Change-Id: Ic0d4efa7b44c46271d19576f5191c9421d07c015 2013-09-19 00:22:59 +00:00			`# This package is broken and causes real issues on update:`
			`# https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1227420`
Do not prompt on removal of apt-xapian-index from ubuntu cloud images Change-Id: I49582a0c51aafcda6c0ad7911c291d58bb6c52a6 2013-09-19 20:35:31 +00:00			`apt-get --yes remove apt-xapian-index \|\| :`