Date: Thu, 16 Feb 2023 17:13:19 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 268593] lang/execline: execline-cd, execline-umask are not world-executable Message-ID: <bug-268593-7788-iZOuXTp3l9@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-268593-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-268593-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D268593 crest@rlwinm.de changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #240186| |maintainer-approval+ Flags| | --- Comment #7 from crest@rlwinm.de --- Created attachment 240186 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D240186&action= =3Dedit Patch overwriting the problematic permissions via pkg-plist I agree. The update to version 2.9.1.0 alone did not fix the problem. I tra= ced the build process with dwatch execve and failed to quickly identify the culprit. According to execline's package/modes file the executables are supposed to be installed with mode 0755 instead of mode 0600. Running gmake install from the work directory (bypassing staging and packaging) does inst= all them to /usr/local/bin with the expected permissions. I expect it's some annoying interaction between either gmake or execline's install.sh and port staging. For now the best I came up with is to just overwrite the permissio= ns in pkg-plist. --=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-268593-7788-iZOuXTp3l9>