From 0f0c98535791f16dbe7ff339f6d7ba81048a8072 Mon Sep 17 00:00:00 2001 From: Chris Sosa Date: Thu, 13 Oct 2011 08:29:41 -0700 Subject: [PATCH] Revert "update hooks: add a hook for fixing all pending config updates" This reverts commit dbcbca5139eb83768dad3dc5e4d27e9e89ca3451 Seems like this change broke SSL http://build.chromium.org/i/chromiumos/builders/x86%20generic%20PFQ/builds/1237/steps/BuildBoard/logs/stdio Change-Id: I02b1e46a6032bc48d54e6fb3d9908d3ea5ca489f Reviewed-on: http://gerrit.chromium.org/gerrit/10015 Reviewed-by: Chris Sosa Tested-by: Chris Sosa --- .../12_clean_old_config_files | 24 ------------------- 1 file changed, 24 deletions(-) delete mode 100644 chroot_version_hooks.d/12_clean_old_config_files diff --git a/chroot_version_hooks.d/12_clean_old_config_files b/chroot_version_hooks.d/12_clean_old_config_files deleted file mode 100644 index a0a194bdc9..0000000000 --- a/chroot_version_hooks.d/12_clean_old_config_files +++ /dev/null @@ -1,24 +0,0 @@ -# Copyright (c) 2011 The Chromium OS Authors. All rights reserved. -# Use of this source code is governed by a BSD-style license that can be -# found in the LICENSE file. - -info "Cleaning old configuration files, crosbug.com/13987" - -# The filesystem may be polluted by a lot of pending config file updates -# at this point. By changing CONFIG_PROTECT, several of these have become -# permanently stale, as neither tool considers them updates anymore. - -# First discard all updates in config files that are still protected, as -# governed by the current CONFIG_PROTECT. -# Autodiscard is option "-9" followed by the "YES" confirmation. -info "Discarding bad updates" -printf '%s\nYES\n' -9 | sudo etc-update - -# Overload CONFIG_PROTECT and automerge all possible updates in all sensible -# locations, that is all updates that should've been merged immediately in -# the first place. -# Automerge is the "-5" option. -info "Automerging good updates" -echo "-5" | sudo CONFIG_PROTECT="/etc /usr/share" etc-update - -exit 0