CLOBBER
author Gregory Szorc <gps@mozilla.com>
Thu, 01 Sep 2016 15:38:30 -0700
changeset 313084 d31f5e1edb53ced0cfd71d6692354713e40615be
parent 312802 a46f0e32289bb8975eef7f87d14cbd71c9c10582
child 313598 869a5b6dae7834e2d33e92486b5fd9629f6c3000
permissions -rw-r--r--
Bug 1298947 - Pin hg.mozilla.org fingerprint; r=dustin We just upgraded our run-time environment to Mercurial 3.9. 3.9 features a new [hostsecurity] config section and allows certificate fingerprints to be defined using SHA-256 hashes (not just SHA-1). A TaskCluster secret with the Mercurial 3.9 fingerprint format has been added. This commit takes advantage of it. MozReview-Commit-ID: 5NwJl9zOse2

# To trigger a clobber replace ALL of the textual description below,
# giving a bug number and a one line description of why a clobber is
# required. Modifying this file will make configure check that a
# clobber has been performed before the build can continue.
#
# MERGE NOTE: When merging two branches that require a CLOBBER, you should
#             merge both CLOBBER descriptions, to ensure that users on
#             both branches correctly see the clobber warning.
#
#                  O   <-- Users coming from both parents need to Clobber
#               /     \
#          O               O
#          |               |
#          O <-- Clobber   O  <-- Clobber
#
# Note: The description below will be part of the error message shown to users.
#
# Modifying this file will now automatically clobber the buildbot machines \o/
#

# Are you updating CLOBBER because you think it's needed for your WebIDL
# changes to stick? As of bug 928195, this shouldn't be necessary! Please
# don't change CLOBBER for WebIDL changes any more.

Bug 1287426 - Clobber required because of Linux Chromium sandbox file moves.