**** BEGIN LOGGING AT Tue Jun 16 03:06:38 2020 Jun 16 08:37:28 mornin Jun 16 08:38:09 hmm, I am trying -c menunconfig in a screen setup and I can't figure out what package I am missing to get the borders rendered correctly, insted I see @^@^@^@ and stuff like that Jun 16 08:38:32 I installed all sorts of term and ncurses related packages but I seem still to be missing the right one, at the same time I know its possible, I had it working fine on another machine Jun 16 08:38:44 does anyone remember what it may be? Jun 16 13:34:18 Hi, I was trying to setup using INCOMPATIBLE_LICENSE for our images, and ran into a little problem. We use systemd and we're currently using busybox sh, but that is being phased out. If I set INCOMPATIBLE_LICENSE to the value from the manual (as this is the minimum we want to filter out) I can no longer build systemd due to the bash RDEPENDS on systemd-kernel-install and systemd-bash-completion. Both are Jun 16 13:34:24 packages we don't use. Is this really expected behavior? To fail an entire recipe when an unsued package RDEPEND cannot be fulfilled? Jun 16 13:42:04 Jin^eLD: depends on the system and the terminal you are using, sometimes due to locales. Try to set env NCURSES_NO_UTF8_ACS=1 Jun 16 13:46:46 mckoan: I did that, but that, found this suggestion on google but it did not help, so I am almost assuming that I am still missing some package Jun 16 13:47:13 its a new CentOS install and I do no longer have to that older CentOS 7 build server where it was working properly, else I'd just compare Jun 16 14:39:24 Jin^eLD: maybe a missing terminfo file? Jun 16 14:54:55 also thought in that direction and installed a couple, but was not able to figure out which one it could be... Jun 16 14:55:05 actually I am pretty sure it will be some terminfo stuff Jun 16 14:57:35 Jin^eLD: for me it tends to be the "screen" one, as I use it a lot locally for console muxing Jun 16 14:59:07 hmm, if I search for "screen" I do not see any specific terminfo that would come with it? Jun 16 14:59:18 or are you referring to the TERM setting? Jun 16 15:20:15 Jin^eLD: yeah, it sets TERM differently Jun 16 15:21:33 so you are saying your setting is TERM=screen and it works for you? let me try... Jun 16 15:24:09 hmm nope Jun 16 15:24:19 my auto.conf has: TERMCMD='TERM=screen screen -D -m -t "$TERMWINDOWTITLE"' Jun 16 15:25:06 and it looks like this https://snipboard.io/Ev4287.jpg Jun 16 15:25:29 let me try that ncurses variable together with the screen term Jun 16 15:26:35 no, that did not help either.. a mystery :> Jun 16 15:30:25 Jin^eLD: I have TERM=screen.xterm-256color here on my debian buster container setup and menuconfig looks okay Jun 16 15:32:03 Jin^eLD: the only tweak I made in the container image was linking screen.xterm-256color -> screen-256color to make that work Jun 16 15:32:23 still looks the same hmm Jun 16 15:32:33 aha ok let me check Jun 16 15:33:27 Jin^eLD: and I installed screen in the container, it pulled in terminfo bits, iirc Jun 16 15:35:07 I do have those links alreadyhmm Jun 16 15:36:39 I get the feeling that its not using my settings at all Jun 16 15:36:48 I now installed xterm, though itd give me additional terminfos Jun 16 15:36:58 and now, despite my screen line in there, it starts xterms with -c menuconfig Jun 16 15:37:02 which btw looks the same - also broken Jun 16 15:37:26 is TERMCMD in auto.conf the right way to set that? maybe thats my problem Jun 16 15:37:58 and now looking closer: Jun 16 15:38:01 TERMCMD='TERM=screen-256color screen -D -m -t "$TERMWINDOWTITLE"' Jun 16 15:38:04 TERMCMDRUN='${SCREEN_TERMCMD} $SHELLCMDS' Jun 16 15:38:10 I wonder if the first one is supposed to be SCREEN_TERMCMD ) Jun 16 15:39:11 Jin^eLD: I have OE_TERMINAL = "screen" in my site.conf in the tree I tried it in Jun 16 15:39:42 ok let me try that.. changing TERMCMD to SCREEN_TERMCMD did not have any influene Jun 16 15:41:01 ok, then did make a differene - it started menuconfig in screen instead of xterm Jun 16 15:41:15 where exactly did you set TERM then? Jun 16 17:24:03 requet sent to get the ELC slack to let us use irccloud Jun 16 17:25:08 :) Jun 16 17:28:03 Crofton|cloud: slack? Jun 16 17:28:32 Typically LF blindness, use slack for OSS-ELC chat Jun 16 17:31:31 and look slike free version, so chat backlog will go fast Jun 16 17:31:52 heh, they do realize FOSS projects like Mattermost exist, right? Jun 16 17:32:07 But slack is free Jun 16 17:34:49 Crofton|cloud: "free" Jun 16 17:35:09 irccloud app approved Jun 16 17:35:12 less bitching Jun 16 17:35:39 if it just has to be free wrt $, #freenode seems a better choice imo, since it'd educate people wrt using it Jun 16 17:36:22 but the non-ELC attendees probably all use Slack Jun 16 17:37:26 does Slack allow moderators? I could see that being potentially useful Jun 16 17:38:21 I am checking if I can create a yoctoproject channel Jun 16 17:38:33 lol and I am on the matrix now Jun 16 17:44:18 I'm going to guess it does Jun 16 17:53:36 Crofton[m]1: not entirely, free version only allows changing permissions on the #general channel, see https://slack.com/intl/en-ca/help/articles/360004635551-Manage-channel-posting-permissions- Jun 16 17:54:51 Crofton[m]1: and note, it's like IRC, moderators can just ban people. Twitch and Discord moderators can also delete their comments, which does seem like a nice to have Jun 16 17:58:02 Crofton[m]1: ah, I guess an admin on Slack could probably delete messages the same way, doesn't seem workable with the scenario of using the free version, though Jun 16 17:58:35 grr -ETOOMANYBRANCHES Jun 16 17:58:39 analog devices kernel repo Jun 16 18:24:52 oh man, slack... I learned about it at work and I do not think I ever saw such a cumbersome client, especially slack threads are on top of my shitlist :) Jun 16 18:52:28 oh yeah, I lose stuff in threads Jun 16 18:53:04 worst thing is when it openes the thread in a mode where you have to frigging click on each new message to see it Jun 16 18:53:19 "1 reply" *click* **** ENDING LOGGING AT Wed Jun 17 02:59:57 2020