gecko-dev/python
Aniket Kadam 3cad808ba6 Bug 1460355 - Fix: Change how the packages are sent to the sdkmanager to install, avoid missing argument. r=nalexander
The argument --package_file was removed in the latest sdkmanager by Google's Android. But the docs for it say
packages can also be sent by putting them in quotes and calling the sdk manager with them as individual args.
So now instead of sending the file directly with the --package_file argument, the package names are read from
the file and the sdk manager is called with them as individual args.
Historically this has been thought of as a bug that happens with the wrong version of the JDK, but this can be
reproduced with just java 1.8.0_181 and the most up to date version of sdkmanager currently 26.1.1
Important note, the mach bootstrap command downloads an older version of the sdk and this bug is not present in
the older version.
Since the way of updating packages I'm proposiing to use is backwards compatible, there shouldn't be any problem
in any version of the sdkamanger.
This is a simpler fix than trying the --package_file argument, particularly because it would involve capturing
output (to detect this particular bug) that's also supposed to be shown to the user because this also happens
when the user is supposed to be interacting with the install.

MozReview-Commit-ID: L7VhCVKJNIf
***
Formatting changes to satisfy the linter.

--HG--
extra : rebase_source : f67d2cb85a4136eb8ad5c3053f5436a8870ab528
2018-07-24 20:06:21 +05:30
..
devtools/migrate-l10n
docs Backed out 3 changesets (bug 1346026) for Bugzilla linting 2018-05-23 19:42:13 +03:00
l10n/fluent_migrations bug 1478343, update existing fluent migrations to 0.6 AST, r=stas 2018-07-25 16:49:30 +02:00
mach Bug 1475058 - Send SIGINT when interrupting interactive in mach before sending SIGKILL. r=mshal 2018-07-12 11:50:48 -07:00
mozboot Bug 1460355 - Fix: Change how the packages are sent to the sdkmanager to install, avoid missing argument. r=nalexander 2018-07-24 20:06:21 +05:30
mozbuild Bug 1474442 - mach command to analyze files in build graph r=chmanchester,mshal 2018-07-25 14:06:51 -04:00
mozlint Bug 1471620 - Skip python-tests locally that don't run with python 3 in CI r=davehunt 2018-06-27 11:10:02 -04:00
mozrelease Bug 1471620 - Skip python-tests locally that don't run with python 3 in CI r=davehunt 2018-06-27 11:10:02 -04:00
mozterm Bug 1471171 - Indicate that mozterm is universal and works on any version of Python; r=emorley 2018-07-02 12:03:10 +01:00
mozversioncontrol Bug 1472177 - Run mozversioncontrol tests under python 3 r=gps 2018-07-24 21:21:46 +00:00
safety Bug 1476003 Update python virtual environment for |mach python-safety| r=davehunt 2018-07-16 15:36:50 +00:00
mach_commands.py Bug 1476390 - [python-test] Default number of processes to multiprocessing.cpu_count() r=davehunt 2018-07-18 16:15:48 +00:00
moz.build Bug 1469872 - update bugzilla products and components in moz.build files: devtools. r=nalexander 2018-06-20 21:34:40 +03:00
README

This directory contains common Python code.

The basic rule is that if Python code is cross-module (that's "module" in the
Mozilla meaning - as in "module ownership") and is MPL-compatible, it should
go here.

What should not go here:

* Vendored python modules (use third_party/python instead)
* Python that is not MPL-compatible (see other-licenses/)
* Python that has good reason to remain close to its "owning" (Mozilla)
  module (e.g. it is only being consumed from there).

Historical information can be found at
https://bugzilla.mozilla.org/show_bug.cgi?id=775243
https://bugzilla.mozilla.org/show_bug.cgi?id=1346025