https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237952
Kubilay Kocak <ko...@freebsd.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|mail/notmuch: port still |mail/notmuch: port still
|has build dependency |has build dependency
|python27 |python27 (transitive, via
| |devel/talloc)
Assignee|ports-b...@freebsd.org |ko...@freebsd.org
Resolution|--- |FIXED
Keywords|needs-qa |
See Also| |https://bugzilla.samba.org/
| |show_bug.cgi?id=13504
Status|Open |Closed
Flags| |maintainer-feedback?(timur@
| |FreeBSD.org)
--- Comment #5 from Kubilay Kocak <ko...@freebsd.org> ---
Fixing the exception syntax throughout the bundled waf results in further
errors:
os.chmod:
File "./buildtools/wafsamba/wafsamba.py", line 801
os.chmod(installed_location, 0755)
^
SyntaxError: invalid token
and after fixing that:
NameError: name 'xrange' is not defined (function removed from Python 3)
I stopped my 'quick fix investigation' at this point.
Suffice it to say:
1) devel/talloc uses :2.7 because the bundled waf bundled is (very) old,
pre-Python 3 support, and only supports 2.x.
The options from here are, in no specific order:
a) Port/fix the bundled waf script to work with python 3.x
b) Ask/get talloc upstream to upgrade their bundled waf version
This may already be occurring:
https://bugzilla.samba.org/show_bug.cgi?id=13504
c) In the meantime, get devel/talloc port to expose a PYTHON option that is
disabled by default (might impact other samba ports?). This may be an
incomplete solution, and still has a *build* dependency on Python 2.7, but
removes the *runtime* requirement for it.
d) Investigate/Get notmuch to not use talloc. I don't know if its compulsory,
or an optional/swappable backend
IMO,
(a) is too much (and duplicate) work, and has a high QA and maintenance
overhead.
(b) is worth adding your support to.
(c) is worth exploring with samba port maintainer (not as a bug), as a backup
for, and in the meantime to (b)
(d) is worth investigating
Once we have the answers to (c) and (d), we can consider resolution for this
issue. If they bear no fruit, this will likely need to be closed "Not A Bug",
"Works As Intended" or "Not Accepted" as necessary
Either way I'm happy to be the coordindator on resolution for this
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
