IRC Logs for #crux-devel Tuesday, 2018-08-28

*** Workster has quit IRC01:59
*** Workster has joined #crux-devel02:41
frinnstjue I know you are away but: https://secure.ucc.asn.au/hg/dropbear/rev/5d2d1021ca0006:33
frinnsthttp://lists.ucc.gu.uwa.edu.au/pipermail/dropbear/2018q3/002108.html06:33
*** Workster has quit IRC09:30
*** onodera has joined #crux-devel16:01
*** groovy2shoes has quit IRC17:18
jaegermoving bot chat here17:38
jaegerI notice a lot of failed module stuff in the error log17:38
jaegerMaybe those are old, not sure17:40
jaegernot timestamped :/17:40
jaegerInteresting... the bot log shows that it did try to notify for all 4 commits where only 2 showed up17:41
jaeger>>1535474652.21PRIVMSG #crux :[contrib.git/3.4]: docker: updated to version 18.06.1-ce17:41
jaeger>>1535474652.82PRIVMSG #crux :[contrib.git/3.4]: containerd: updated to version 468a54517:42
jaeger>>1535474653.18PRIVMSG #crux :[contrib.git/3.4]: runc: updated to version 69663f017:42
jaeger>>1535474653.72PRIVMSG #crux :[contrib.git/3.4]: go: updated to version 1.1117:42
jaegersame for the two nvidia commits, I see both in the bot's raw log17:46
jaegeralso interesting: all the modules look like this, permissions-wise:17:51
jaeger---------- 1 root root  4041 Nov  5  2016 xkcd.py17:51
jaegerThat seems like something that would have to have been done intentionally17:52
jaegerI don't think that's related, just noticed it17:58
jaegerAnyway, not sure what to think of the missed messages17:59
frinnstyeah I think tek did that when i set it up20:00
frinnstwhen you start it up the log isnt pretty20:00
pedjaRomster, you might want to update contrib/cpuid, 20180519 is the latest version20:07
*** groovy2shoes has joined #crux-devel20:08
*** onodera has quit IRC21:01
*** Workster has joined #crux-devel23:26

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!