#68935 closed defect (fixed)
py-werkzeug @3.0.1 does not build, subports py31[012]-werkzeug are all OK
Reported by: | snowflake (Dave Evans) | Owned by: | stromnov (Andrey Stromnov) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | base | Version: | 2.8.99 |
Keywords: | Cc: | ||
Port: | py-werkzeug |
Description
py-werkzeug does not build, whereas the sub-ports py310-werkzeug, py311-werkzeug and py312-werkzeug are all OK.
The important error is this:
Error: Failed to build py-werkzeug: can't read "build.cmd": can't read "python.bin": can't read "python.prefix": can't read "python.branch": can't read "python.version": no such variable
Here is the error for py-werkzeug on El Capitan. Sonoma error is the same.
DEBUG: build phase started at Mon Dec 18 08:42:23 GMT 2023 Error: Failed to build py-werkzeug: can't read "build.cmd": can't read "python.bin": can't read "python.prefix": can't read "python.branch": can't read "python.version": no such variable DEBUG: Error code: TCL READ VARNAME DEBUG: Backtrace: can't read "python.version": no such variable DEBUG: while executing DEBUG: "string index ${python.version} 0" DEBUG: ("uplevel" body line 1) DEBUG: invoked from within DEBUG: "uplevel #0 [list set $optionName] [subst -nocommands {[subst {$option_defaults($optionName)}]}]" DEBUG: (procedure "default_check" line 10) DEBUG: invoked from within DEBUG: "default_check python.branch {} read" DEBUG: (read trace on "python.branch") DEBUG: invoked from within DEBUG: "subst {${frameworks_dir}/Python.framework/Versions/${python.branch}}" DEBUG: ("uplevel" body line 1) DEBUG: invoked from within DEBUG: "uplevel #0 [list set $optionName] [subst -nocommands {[subst {$option_defaults($optionName)}]}]" DEBUG: (procedure "default_check" line 10) DEBUG: invoked from within DEBUG: "default_check python.prefix {} read" DEBUG: (read trace on "python.prefix") DEBUG: invoked from within DEBUG: "subst {${python.prefix}/bin/python${python.branch}}" DEBUG: ("uplevel" body line 1) DEBUG: invoked from within DEBUG: "uplevel #0 [list set $optionName] [subst -nocommands {[subst {$option_defaults($optionName)}]}]" DEBUG: (procedure "default_check" line 10) DEBUG: invoked from within DEBUG: "default_check python.bin {} read" DEBUG: (read trace on "python.bin") DEBUG: invoked from within DEBUG: "return "${python.bin} -m build --no-isolation"" DEBUG: (procedure "python_get_defaults" line 13) DEBUG: invoked from within DEBUG: "python_get_defaults build_cmd" DEBUG: ("uplevel" body line 1) DEBUG: invoked from within DEBUG: "uplevel #0 [list set $optionName] [subst -nocommands {[subst {$option_defaults($optionName)}]}]" DEBUG: (procedure "default_check" line 10) DEBUG: invoked from within DEBUG: "default_check build.cmd {} read" DEBUG: (read trace on "build.cmd") DEBUG: invoked from within DEBUG: "if {${build.cmd} eq ""} { DEBUG: error "No build command found" DEBUG: }" DEBUG: (procedure "portbuild::build_start" line 4) DEBUG: invoked from within DEBUG: "[ditem_key $ditem prerun] $targetname"
Change History (5)
comment:1 Changed 11 months ago by snowflake (Dave Evans)
Summary: | py-werkzeug @3.0.1 does not build, subports py3[012]-werkzeug are all OK → py-werkzeug @3.0.1 does not build, subports py31[012]-werkzeug are all OK |
---|
comment:2 Changed 11 months ago by snowflake (Dave Evans)
comment:3 Changed 11 months ago by jmroot (Joshua Root)
Component: | ports → base |
---|
comment:4 Changed 11 months ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:5 Changed 11 months ago by jmroot (Joshua Root)
Note: See
TracTickets for help on using
tickets.
I notice that the buildbot for 10.11 is not reporting errors, so the error I get may be caused by me using port version 2.8.99