IRC Logs for #crux-devel Friday, 2012-08-17

*** Romster has quit IRC00:40
*** Romster has joined #crux-devel00:41
*** mike_k has joined #crux-devel02:00
frinnstso teK_ what needs changing before im off for the weekend? I dont have access to the server from home08:37
frinnstmaybe i should fix that btw..08:37
teK_I have to rethink the process due to the uid-preserving-problem so get home I'll let you know as soon as I know08:38
*** mike_k has quit IRC08:56
*** mike_k has joined #crux-devel08:57
frinnstjust a sudo should be doable, no?08:58
frinnstanyways, i've fixed access from home now too08:58
jaegerI think he didn't want to allow sudo access to rsync08:59
jaegerwhich is understandable if you don't trust people not to do something like "rsync /dev/null /etc/passwd" or whatever09:00
frinnstyeah that does sound like something tek would do sooner or later09:00
teK_the difference is that I'd do it _without_ malice09:02
jaegerhehe, indeed09:02
teK_they sentenced pussy riot09:03
*** horrorStruck has quit IRC09:06
*** horrorStruck has joined #crux-devel09:07
jaegerwow... udisks2 can't even be compiled without upgrading kernel headers to 3.3 or something09:09
jaegerI was thinking that might be an automount solution with gvfs/mate-vfs but won't be able to test it without upgrading glibc or installing 2.8/3.0, heh09:15
jaegerwe're already on kernel 3.5.2 now? jesus09:21
*** horrorSt1uck has joined #crux-devel09:22
*** horrorStruck has quit IRC09:25
*** horrorSt1uck is now known as horrorStruck10:10
*** joe9 has joined #crux-devel12:14
*** joe9 has quit IRC13:04
*** mike_k has quit IRC14:21
*** jaeger23 has quit IRC17:29
*** jaeger- has joined #crux-devel17:29
*** acrux has quit IRC18:08
*** acrux has joined #crux-devel18:10
*** jaeger- has quit IRC18:48
*** jaeger23 has joined #crux-devel18:48
*** jaeger23 has quit IRC18:57
*** jaeger23 has joined #crux-devel20:23
*** mavrick61 has quit IRC21:23
*** mavrick61 has joined #crux-devel21:24
jaegerfrinnst: have you messed with the new toolchain yet on x64? I'm getting dbm build issues with pythoon21:58
jaegerpython, too21:58
prologicwhat's the build error?23:28
jaegerIt's a footprint mismatch caused by *** WARNING: renaming "dbm" since importing it failed: build/lib.linux-x86_64-2.7/ undefined symbol: dbm_nextkey23:32
jaegerMISSING   -rwxr-xr-x      root/root       usr/lib/python2.7/lib-dynload/_bsddb.so23:32
jaegerMISSING   -rwxr-xr-x      root/root       usr/lib/python2.7/lib-dynload/dbm.so23:32
jaegerNEW       -rwxr-xr-x      root/root       usr/lib/python2.7/lib-dynload/dbm_failed.so23:32
jaegerblarg, hardware error spotted!23:41
jaegertons of errors in memtest23:41
jaeger(unrelated to the python thing, just stress testing another box)23:41

Generated by 2.11.0 by Marius Gedminas - find it at!