New issue
Advanced search Search tips

Issue 847821 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jan 15
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Fuchsia
Pri: 2
Type: Bug

Blocking:
issue 39240



Sign in to add a comment

third_party/fuchsia-sdk causes tools/licenses.py to fail

Project Member Reported by raphael....@intel.com, May 30 2018

Issue description

licenses.py throws a LicenseError that looks like this when scanning third_party/fuchsia-sdk:

licenses.LicenseError: Errors in third_party/fuchsia-sdk:
 License file not found. Either add a file named LICENSE, import upstream's COPYING if available, or add a 'License File:' line to README.chromium with the appropriate path.
 
Blocking: 39240
Labels: -Pri-3 M-70 Pri-2
Owner: kmarshall@chromium.org
Status: Started (was: Available)
Thanks for reporting this issue; kmarshall@ has just started looking at this.
Status: Verified (was: Fixed)
Status: Assigned (was: Verified)
It still fails here on master (I'm at commit d0852575f8d42bcf45ad26d0c46bda23b025693d):

/data/src/chromium/src % ./tools/licenses.py scan
[...]
third_party/fuchsia-sdk: Errors in third_party/fuchsia-sdk:
 License file not found. Either add a file named LICENSE, import upstream's COPYING if available, or add a 'License File:' line to README.chromium with the appropriate path.                                                                 
[...]

I don't see anything changing third_party/fuchsia-sdk in the commit mentioned in comment #3.
I guess this might be happening when 'fuchsia' isn't in .gclient target_os so we don't run the Fuchsia-specific hooks?
Re #6: We definitely don't have a LICENSE file in there, but neither do we have "License File:" in README.chromium, so where is it picking things up from when target_os="fuchsia" _is_ defined?
Oh, I didn't look very carefully, I just saw something about "generate LICENSE" in kmarshall's cl, so I assumed that was covering it.
Re #8: The CL at #3 creates the overall LICENSE file for the webrunner - the error in #5 is the tool complaining that the SDK license file is missing, I think?
Status: Fixed (was: Assigned)

Sign in to add a comment