Date: Sun, 17 Nov 2019 00:34:12 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 242014] www/jetty8 jettyctl does not work with python3 Message-ID: <bug-242014-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D242014 Bug ID: 242014 Summary: www/jetty8 jettyctl does not work with python3 Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: olgeni@FreeBSD.org Reporter: martin@waschbuesch.de Assignee: olgeni@FreeBSD.org Flags: maintainer-feedback?(olgeni@FreeBSD.org) www/jetty8 comes with a control script (/usr/local/sbin/jettyctl) written in python. The package Makefile does not seem to depend on a specific version of pytho= n, but said control script makes use of python2 syntax. When trying to start jetty, I get: Starting jetty. File "/usr/local/sbin/jettyctl", line 83 executable =3D stat.S_IMODE(finfo) & 0111 ^ SyntaxError: invalid token /usr/local/etc/rc.d/jetty: WARNING: failed to start jetty I do not know much python, but in python3 leading zeros are no longer accep= ted, so I guess an octal bitmask for file permissions would need to be written as 0o0111. However, while doing so will fix the particular error message, the script s= till does not work. Upstream, there is a shell script for starting and stopping jetty. Maybe th= at would be a better approach? If, as may well be, this control script is the = only reason why jetty needs to pull in python as a dependency, using a shell scr= ipt instead sounds like a reasonable thing to do? --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-242014-7788>