 it unpack the right lib/modules? I suspect it will and this means something is missing here :(
<mvo> Chipaca: i.e. somewhere what we did is not what snappy did
 * mvo really lunches first
<olli> gm
<Chipaca> mvo: indeed, that worked perfectly
<Chipaca> doing over with strace
<mvo> Chipaca: yeah, lets figure out what it execve()s :/
<sergiusens> morning
<Chipaca> olli: sergiusens: mo'in
 * sergiusens has a nasty cold since yesterday
<Chipaca> so does the uk
<Chipaca> they're calling it "autumn"
<sergiusens> Chipaca, it snowed in the Altas Cumbres yesterday!
<sergiusens> we are enjoying spring ;-)
<Chipaca> wow, slightly late this year
<Chipaca> usually it's september it snows :)
<Chipaca> whaaaa
<Chipaca> ok, lots of trace files :)
<Chipaca> hah, well, that's something that went wrong
<Chipaca> /tmp/trace.1080:execve("/usr/bin/system-image-cli", ["system-image-cli", "--progress", "json", "-C", "/etc/system-image/config.d"], [/* 23 vars */]) = 0
<Chipaca> and that happens if it can't read the one in /writable/cache
<Chipaca> $ ls -l /writable/cache/system/etc/system-image/config.d/00_default.ini
<Chipaca> lrwxrwxrwx 1 root root 13 Oct 13 11:04 /writable/cache/system/etc/system-image/config.d/00_default.ini -> ../client.ini
<Chipaca> puzzled, now
<ogra_> why ?
<ogra_> the old s-i-cli used /etc/system-image/client.ini by default, the new one uses the files under /etc/system-image/config.d/
<Chipaca> i think this is related to a bug barry already fixed
<Chipaca> with system-image not really requiring config to work
<Chipaca> but we still treat it like it does
<Chipaca> and system-image used to crash with a symlink, but he fixed taht
<Chipaca> ogra_: in any case, it's doing the wrong update and getting into trouble
 * olli waves at Chipaca
<Chipaca> i'm not sure when using the wrong config for system image is the right thing, but this isn't one of those times :)
<ogra_> well, whats inside that client.ini  ?
<ogra_> it should point to the new image
<Chipaca> it's not there ^
<Chipaca> broken symlink
<ogra_> ah !
<ogra_