FS#72462 - [qt5-webengine] python3 related build error
Attached to Project:
Arch Linux
Opened by Rijnder (rien333) - Monday, 18 October 2021, 13:43 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 05 January 2022, 09:22 GMT
Opened by Rijnder (rien333) - Monday, 18 October 2021, 13:43 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 05 January 2022, 09:22 GMT
|
Details
Description:
When I use `makepkg` to build the current PKGBUILD, I get the following error in the build process: ``` [4899/23910] /usr/bin/python ../../../../qtwebengine/src/3rdparty/chromium/third_party/dawn/generator/dawn_json_generator.py --dawn-json ../../../../qtwebengine/src/3rdparty/chromium/third_party/dawn/dawn.json --wire-json ../../../../qtwebengine/src/3rdparty/chromium/third_party/dawn/dawn_wire.json --targets dawn_headers --template-dir /tmp/makepkg/qt5-webengine/src/qtwebengine/src/3rdparty/chromium/third_party/dawn/generator/templates --jinja2-path /tmp/makepkg/qt5-webengine/src/qtwebengine/src/3rdparty/chromium/third_party/jinja2 --output-json-tarball gen/third_party/dawn/dawn_headers_gen.json_tarball --depfile gen/third_party/dawn/dawn_headers_gen.json_tarball.d --expected-outputs-file gen/third_party/dawn/dawn_headers_gen.expected_outputs --allowed-output-dirs-file gen/third_party/dawn/dawn_headers_gen.allowed_output_dirs FAILED: gen/third_party/dawn/dawn_headers_gen.json_tarball /usr/bin/python ../../../../qtwebengine/src/3rdparty/chromium/third_party/dawn/generator/dawn_json_generator.py --dawn-json ../../../../qtwebengine/src/3rdparty/chromium/third_party/dawn/dawn.json --wire-json ../../../../qtwebengine/src/3rdparty/chromium/third_party/dawn/dawn_wire.json --targets dawn_headers --template-dir /tmp/makepkg/qt5-webengine/src/qtwebengine/src/3rdparty/chromium/third_party/dawn/generator/templates --jinja2-path /tmp/makepkg/qt5-webengine/src/qtwebengine/src/3rdparty/chromium/third_party/jinja2 --output-json-tarball gen/third_party/dawn/dawn_headers_gen.json_tarball --depfile gen/third_party/dawn/dawn_headers_gen.json_tarball.d --expected-outputs-file gen/third_party/dawn/dawn_headers_gen.expected_outputs --allowed-output-dirs-file gen/third_party/dawn/dawn_headers_gen.allowed_output_dirs Traceback (most recent call last): File "/tmp/makepkg/qt5-webengine/src/build/src/core/release/../../../../qtwebengine/src/3rdparty/chromium/third_party/dawn/generator/dawn_json_generator.py", line 816, in <module> sys.exit(run_generator(MultiGeneratorFromDawnJSON())) File "/tmp/makepkg/qt5-webengine/src/qtwebengine/src/3rdparty/chromium/third_party/dawn/generator/generator_lib.py", line 290, in run_generator dependencies += _compute_python_dependencies(args.root_dir) File "/tmp/makepkg/qt5-webengine/src/qtwebengine/src/3rdparty/chromium/third_party/dawn/generator/generator_lib.py", line 204, in _compute_python_dependencies path = os.path.abspath(path) File "/usr/lib/python3.9/posixpath.py", line 375, in abspath path = os.fspath(path) TypeError: expected str, bytes or os.PathLike object, not NoneType ``` I'm guessing this is somehow related to dropping the python2 make dependency. Additional info: * package version(s) 5.15.6-4 and 5.15.6-5 * config and/or log files etc. See above for the error. * link to upstream bug report, if any Steps to reproduce: 1. `yay -G qt5-webengine` 2. `cd` into the folder 3. `makepkg -si` |
This task depends upon
Closed by Antonio Rojas (arojas)
Wednesday, 05 January 2022, 09:22 GMT
Reason for closing: Fixed
Additional comments about closing: in svn
Wednesday, 05 January 2022, 09:22 GMT
Reason for closing: Fixed
Additional comments about closing: in svn
Comment by Rijnder (rien333) -
Monday, 18 October 2021, 15:06 GMT
Comment by Rijnder (rien333) -
Wednesday, 05 January 2022, 09:22 GMT
Comment by Antonio Rojas (arojas) -
Wednesday, 05 January 2022, 09:22 GMT
I can confirm that when removing the patches that allow for the
removal of python2 from makedeps, the build proceeds without
errors.
- Field changed: Percent Complete (100% → 0%)
Seeing this again. I think the current
qt5-webengine-chromium-python3.patch somehow reintroduced the
error.
oops, sorry