12:15:54 <neirac> jperkin to use pkgsrc wip in macos do I need to perform additional configurations, or it will just work as the macos/release branch does ?
12:25:28 <jperkin> it should just work, I don't have any modifications for wip on macos
13:16:13 <neirac> jperkin thanks, I'll give it a try.
16:57:05 <nikolam> I see on multiple machines, SmartOS latest , inside global zone,  that pkgin install -y <packagename> still requires to press Y and return to proceed. 
17:01:29 <jperkin> it's "pkgin -y install <packagename>"
17:17:18 <pjustice> `pkgin install -y ...` told me to bark at the moon yesterday.
17:17:31 <pjustice> (However there apparently _is_ a package called asdf, lol.)
17:27:54 <barfield> Is there a simple way to stop the wrapping of text in bash, running in native SmartOS zones?
17:38:39 <barfield> I think that I have seen danmcd: or bahamat: mention setting "export TERM=screen" or something...but that doesn't appear to be working. 
17:39:44 <bahamat> I...have uttered such things in the past, what context are we talking about here?
17:40:15 <barfield> I think...I'm jogging my own memory
17:40:30 <barfield> Trying to remember how to stop bash from borking extra long commands
17:41:06 <bahamat> How is it "borking" extra long commands? And how long is "extra long" here?
17:41:15 <barfield> +40 characters
17:41:21 <barfield> in a non-root shell
17:41:25 <barfield> like psql
17:42:12 <barfield> like `su - postgres; psql` one second, one of my guys is going to get me a real good example
17:43:44 <barfield> Disregard, I think he fixed it lol. Apologies for the false-alarm
17:45:20 <barfield> export TERM=xterm-256color
17:45:20 <barfield> export COLUMNS=148
17:45:20 <barfield> export TERMINFO=/opt/local/share/lib/terminfo
17:45:20 <barfield> 17m
17:45:30 <barfield> Seems like those settings resolved it
17:45:54 <barfield> Thanks again
17:58:02 <nikolam> I have been typing in 'choco' on win to update and that had consequences ;P 
20:51:42 <pjustice> jperkin: Just added a note to #363.  I can remove pkg_install and extract the .tmp.tar to be able to properly reinstall it, but (a) I'm not sure that's truly safe; and (b) I'd like to help kill off the source of this problem.
20:52:56 <jperkin> if you extract the tmp.tar to a temporary directory and then run ./pkg_add inside it
20:53:18 <jperkin> but yeh I really need to just track down where this is coming from and figure out why I don't see it
20:53:45 <pjustice> One of the affected machines today is a new gz that I'm pretty sure I haven't done anything stooopid to.