checking if it worked that way
<tomwardill> is it just a case of exit(1) from the hook?
<Chipaca> tomwardill: yep
<tomwardill> excellent, thanks.
<Chipaca> at least that's what the integration test uses :-)
<sil2100> sergiusens: anyway, we weren't looking at core16 recently yet
<sil2100> sergiusens: so I guess it
<sil2100> argh, I guess it
<sil2100> (keyboard errors)
<sil2100> I guess it'll still take a bit
<sil2100> Since you mentioned it now, I'm doing an image test build to see what's the current state
<mup> PR snapd#6003 opened: cmd/snap: block 'snap help <cmd> --all' <Simple ð> <Created by chipaca> <https://github.com/snapcore/snapd/pull/6003>
<Chipaca> hmm, hmm, snap refresh --offline
<pedronis> Chipaca: what would that do ?
<Chipaca> pedronis: remember apt-zip?
<pedronis> no
<Chipaca> https://wiki.debian.org/AptZip
<pedronis> I see
<Chipaca> pedronis: context is a person in the forum in 'the heart of africa' (says their profile), 3rd world with intermittent energy and connectivity, wanting to only talk to the store once and get everything for multiple devices
<Chipaca> pedronis: I tagged you in one of the topics on this, there's a second (linked to that one)
<Chipaca> anyway, i'm off for a bit
<mup> PR snapd#6004 opened: cmd/snap-confine: reduce verbosity of debug and error messages <Created by zyga> <https://github.com/snapcore/snapd/pull/6004>
<jdstrand> mvo: I think this is what sergiusens may have been reporting. it looks like my 5981, 5989 and 6002 PRs are 'stuck'. 'Details' show all green for 5981, shows spread at 6 minutes for 5989 (did that restart?) and show nothing started for 6002
<jdstrand> mvo: let me know if I should do something
<zyga> dpkg-deb: error: <compress> from tar -cf subprocess was killed by signal (Illegal instruction), core dumped
<zyga> that's a new error
<mup> PR snapd#5992 closed: release: merge 2.35.5 changes into the 2.36 branch <Created by mvo5> <Merged by zyga> <https://github.com/snapcore/snapd/pull/5992>
<mvo> jdstrand: sorry for the slow reply - "stuck> not sure w