diff options
| -rw-r--r-- | bitbake/lib/bb/fetch2/__init__.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bitbake/lib/bb/fetch2/__init__.py b/bitbake/lib/bb/fetch2/__init__.py index d099cd1092..a7e84e0dc7 100644 --- a/bitbake/lib/bb/fetch2/__init__.py +++ b/bitbake/lib/bb/fetch2/__init__.py | |||
| @@ -113,7 +113,7 @@ class MissingParameterError(BBFetchException): | |||
| 113 | self.args = (missing, url) | 113 | self.args = (missing, url) |
| 114 | 114 | ||
| 115 | class ParameterError(BBFetchException): | 115 | class ParameterError(BBFetchException): |
| 116 | """Exception raised when a url cannot be proccessed due to invalid parameters.""" | 116 | """Exception raised when a url cannot be processed due to invalid parameters.""" |
| 117 | def __init__(self, message, url): | 117 | def __init__(self, message, url): |
| 118 | msg = "URL: '%s' has invalid parameters. %s" % (url, message) | 118 | msg = "URL: '%s' has invalid parameters. %s" % (url, message) |
| 119 | self.url = url | 119 | self.url = url |
| @@ -182,7 +182,7 @@ class URI(object): | |||
| 182 | Some notes about relative URIs: while it's specified that | 182 | Some notes about relative URIs: while it's specified that |
| 183 | a URI beginning with <scheme>:// should either be directly | 183 | a URI beginning with <scheme>:// should either be directly |
| 184 | followed by a hostname or a /, the old URI handling of the | 184 | followed by a hostname or a /, the old URI handling of the |
| 185 | fetch2 library did not comform to this. Therefore, this URI | 185 | fetch2 library did not conform to this. Therefore, this URI |
| 186 | class has some kludges to make sure that URIs are parsed in | 186 | class has some kludges to make sure that URIs are parsed in |
| 187 | a way comforming to bitbake's current usage. This URI class | 187 | a way comforming to bitbake's current usage. This URI class |
| 188 | supports the following: | 188 | supports the following: |
