CLOBBER
author Nathan Froyd <froydnj@gmail.com>
Tue, 09 Aug 2016 18:10:19 -0400
changeset 308834 c8be3efb34863ed1b532536c3cc77ad46340d497
parent 308431 8ee6f2eb8b349a351f6f76585eb85e0ec2b5c475
child 309495 2d707c2b52b5a2a63da551959d255795337b9880
permissions -rw-r--r--
Bug 1290957 - ensure MOZ_AUTOMATION builds require a cargo with --frozen support; r=chmanchester We want to ensure that our automation builds don't pull in libraries from crates.io, and we need --frozen support in cargo to do that. If we don't have that support, we shouldn't build.

# 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 1291229 - clobber due to changes in generated code (bug 1182840)