Commit a4d3e026 authored by Marius Gedminas's avatar Marius Gedminas

Typo: occured -> occurred.

parent f91c9626
......@@ -501,7 +501,7 @@ Bugs Fixed
- 92891: bootstrap crashes with recipe option in buildout section.
- 113085: Buildout exited with a zero exist status when internal errors
occured.
occurred.
1.0.0b23 (2007-03-19)
......
......@@ -189,7 +189,7 @@ else: # Windows prefers this, apparently; otherwise we would prefer subprocess
if exitcode != 0:
sys.stdout.flush()
sys.stderr.flush()
print ("An error occured when trying to install zc.buildout. "
print ("An error occurred when trying to install zc.buildout. "
"Look above this message for any errors that "
"were output by easy_install.")
sys.exit(exitcode)
......
......@@ -1502,7 +1502,7 @@ def _error(*message):
sys.exit(1)
_internal_error_template = """
An internal error occured due to a bug in either zc.buildout or in a
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
"""
......
......@@ -463,7 +463,7 @@ leave previously created paths in place:
While:
Installing data-dir.
<BLANKLINE>
An internal error occured due to a bug in either zc.buildout or in a
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
...
......@@ -495,7 +495,7 @@ If we fix the typo:
While:
Installing data-dir.
<BLANKLINE>
An internal error occured due to a bug in either zc.buildout or in a
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
...
......@@ -572,7 +572,7 @@ When we rerun the buildout:
While:
Installing data-dir.
<BLANKLINE>
An internal error occured due to a bug in either zc.buildout or in a
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
...
......@@ -653,7 +653,7 @@ directories will be created:
While:
Installing data-dir.
<BLANKLINE>
An internal error occured due to a bug in either zc.buildout or in a
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
...
......
......@@ -5,7 +5,7 @@ Buildouts can be pretty complex. When things go wrong, it isn't
always obvious why. Errors can occur due to problems in user input or
due to bugs in zc.buildout or recipes. When an error occurs, Python's
post-mortem debugger can be used to inspect the state of the buildout
or recipe code were there error occured. To enable this, use the -D
or recipe code were there error occurred. To enable this, use the -D
option to the buildout. Let's create a recipe that has a bug:
>>> mkdir(sample_buildout, 'recipes')
......
......@@ -529,7 +529,7 @@ class Installer:
if exit_code:
logger.error(
"An error occured when trying to install %s. "
"An error occurred when trying to install %s. "
"Look above this message for any errors that "
"were output by easy_install.",
dist)
......
......@@ -383,7 +383,7 @@ Error: Couldn't download 'http://localhost/base.cfg' in offline mode.
While:
Installing.
Checking for upgrades.
An internal error occured ...
An internal error occurred ...
ValueError: install_from_cache set to true with no download cache
......
......@@ -1442,7 +1442,7 @@ def internal_errors():
Getting section data-dir.
Initializing part data-dir.
<BLANKLINE>
An internal error occured due to a bug in either zc.buildout or in a
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
...
......@@ -2546,7 +2546,7 @@ if sys.version_info > (2, 4):
Initializing section x.
Loading zc.buildout recipe entry zc.buildout.testexit:default.
<BLANKLINE>
An internal error occured due to a bug in either zc.buildout or in a
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used:
Traceback (most recent call last):
...
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment