Re: "emptyenv -c" unsets all environment variables
No problem, waiting for the next update then. Thanks! MMS On Sat, Jan 23, 2021, 18:16 Laurent Bercot wrote: > >Unfortunately, after updating to skalibs-2.10.0.1 (downloaded from > https://skarnet.org/software/skalibs/skalibs-2.10.0.1.tar.gz) and > recompiling execline (statically linked) the problem persists. I also tried > compiling and installing both of them on clean system (no previous versions > of skalibs and execline installed before) and "emptyenv -c" still empties > the whole environment. Perhaps I'm missing something? > > My bad! I lied, skalibs-2.10.0.1 fixes something else. The bugfix > for emptyenv -c is in the execline git master, but I haven't cut a > release yet. Sorry! > I will release versions for execline (and s6, which also has > bugfixes) early next week. > > -- > Laurent > >
Re: "emptyenv -c" unsets all environment variables
Unfortunately, after updating to skalibs-2.10.0.1 (downloaded from https://skarnet.org/software/skalibs/skalibs-2.10.0.1.tar.gz) and recompiling execline (statically linked) the problem persists. I also tried compiling and installing both of them on clean system (no previous versions of skalibs and execline installed before) and "emptyenv -c" still empties the whole environment. Perhaps I'm missing something? My bad! I lied, skalibs-2.10.0.1 fixes something else. The bugfix for emptyenv -c is in the execline git master, but I haven't cut a release yet. Sorry! I will release versions for execline (and s6, which also has bugfixes) early next week. -- Laurent
Re: "emptyenv -c" unsets all environment variables
My apologies for not checking for updates first, I'll actively check for updates before posting here next time :D. Unfortunately, after updating to skalibs-2.10.0.1 (downloaded from https://skarnet.org/software/skalibs/skalibs-2.10.0.1.tar.gz) and recompiling execline (statically linked) the problem persists. I also tried compiling and installing both of them on clean system (no previous versions of skalibs and execline installed before) and "emptyenv -c" still empties the whole environment. Perhaps I'm missing something? On 22 Jan 2021 16.39, Laurent Bercot wrote: I'm using skalibs-2.10.0.0 and execline-2.7.0.0 here in my system. I noticed on my system that "emptyenv -c" unsets all environment variables just like "emptyenv" does. This didn't happen with previous versions of execline and skalibs. Has anyone encountered this too? Already fixed in skalibs-2.10.0.1 ;) (I generally don't make announcements for bugfixes releases, maybe I should.) Also, not related to above, the trap.html documentation page contains some typos: "multisusbstitute" at the second point of the "Notes" section and possibly "will be still be caught" at the "Options" section. Thanks, will fix. -- Laurent
Re: "emptyenv -c" unsets all environment variables
I'm using skalibs-2.10.0.0 and execline-2.7.0.0 here in my system. I noticed on my system that "emptyenv -c" unsets all environment variables just like "emptyenv" does. This didn't happen with previous versions of execline and skalibs. Has anyone encountered this too? Already fixed in skalibs-2.10.0.1 ;) (I generally don't make announcements for bugfixes releases, maybe I should.) Also, not related to above, the trap.html documentation page contains some typos: "multisusbstitute" at the second point of the "Notes" section and possibly "will be still be caught" at the "Options" section. Thanks, will fix. -- Laurent
"emptyenv -c" unsets all environment variables
Hello everyone, I'm using skalibs-2.10.0.0 and execline-2.7.0.0 here in my system. I noticed on my system that "emptyenv -c" unsets all environment variables just like "emptyenv" does. This didn't happen with previous versions of execline and skalibs. Has anyone encountered this too? Also, not related to above, the trap.html documentation page contains some typos: "multisusbstitute" at the second point of the "Notes" section and possibly "will be still be caught" at the "Options" section. Thanks!
