From 25005ff22c9f845ffffa682a903b0c0b8f76e28d Mon Sep 17 00:00:00 2001 From: Chris Koeritz Date: Fri, 3 Nov 2017 00:06:59 -0400 Subject: [PATCH] attempting to fix naive system updater the updater running from cron kept getting jammed up, with multiple possibly running at the same time. this seems to be due to questions about using existing or new config files. a fix suggested on internet says that dpkg needs to be told not to do that, and to just use the existing ones. --- scripts/system/naive_system_updater.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/scripts/system/naive_system_updater.sh b/scripts/system/naive_system_updater.sh index dbad94fb..08cd5266 100644 --- a/scripts/system/naive_system_updater.sh +++ b/scripts/system/naive_system_updater.sh @@ -3,7 +3,8 @@ source "$FEISTY_MEOW_SCRIPTS/core/launch_feisty_meow.sh" sudo apt-get update -y check_result "problem while doing 'apt-get update'" -sudo apt-get dist-upgrade -y +# new magic to tell dpkg to go with existing config files. let's see if it works! +sudo apt-get dist-upgrade -y -o Dpkg::Options::="--force-confold" check_result "problem while doing 'apt-get dist-upgrade'" -- 2.34.1