Re: issue with sudo-1.8.23

2018-05-04 Thread Walter Schwarzenfeld
It was not good worded. It was changed upstream to /run (the timestamp does not survive system reboot). But it is now set (see Makefile) CONFIGURE_ARGS+=--with-rundir=/var/run/sudo and that is what you want. ___ freebsd-ports@freebsd.org mailing

Re: issue with sudo-1.8.23

2018-05-04 Thread Lars Engels
On Fri, May 04, 2018 at 07:56:10AM +0200, Lars Engels wrote: > On Thu, May 03, 2018 at 09:15:14PM +0200, Walter Schwarzenfeld wrote: > > In this version /var/run/sudo is changed to /run/sudo. If /var/run/sudo > > in the pkg-plist causes the problem if a directory /run exists. > > > > But solved,

Re: issue with sudo-1.8.23

2018-05-04 Thread Lars Engels
On Thu, May 03, 2018 at 09:15:14PM +0200, Walter Schwarzenfeld wrote: > In this version /var/run/sudo is changed to /run/sudo. If /var/run/sudo > in the pkg-plist causes the problem if a directory /run exists. > > But solved, fixed by maintainer. Can we please revert this to /var/run? /run is

Re: issue with sudo-1.8.23

2018-05-03 Thread Walter Schwarzenfeld
In this version /var/run/sudo is changed to /run/sudo. If /var/run/sudo in the pkg-plist causes the problem if a directory /run exists. But solved, fixed by maintainer. ___ freebsd-ports@freebsd.org mailing list

issue with sudo-1.8.23

2018-05-03 Thread Walter Schwarzenfeld
following issue: ===>  Installing for sudo-1.8.23 ===>   Registering installation for sudo-1.8.23 pkg-static: lstat(/ram/usr/ports/security/sudo/work/stage/var/run/sudo/): No such file or directory *** Error code 74 Stop. make[2]: stopped in /usr/ports/security/sudo *** Error code 1