remote-on-pi-grabs-wrong-arch-lxc-image/691/17
<diddledan> cleanbuild should not be forcing the version of snapd to anything EXCEPT "the latest" stable, unless the user specifically tells snapcraft otherwise
<diddledan> and doing the forcing by injecting host-side snaps is just plain wrong
<diddledan> IMO
<diddledan> and no, that opinion is not humble in any way :-p
<mvo> pstolowski: how is that test going? the second run of the core-refresh testing?
<kalikiana> diddledan: snapd? do you mean the core snap? snapcraft attempts to install the same version in the container that's being used on the host
<pstolowski> mvo, well..
<diddledan> yeah, core
<pstolowski> mvo, http://pastebin.ubuntu.com/25753195/
<kalikiana> diddledan: so if eg. you're using beta on the host to test something, the container will be using that, same goes for snapcraft itself
<pstolowski> mvo, last failure unrelated, probably wifi dropped or something
<diddledan> I think it's wrong to be injecting at all, foreign arch or not. Core should be updated using snap processes not by injecting random snaps. We should not be designing weird behaviour for the edge case of "I want to test something" by default
<diddledan> an "I want to test something" should be an opt-in not a default
<mvo> pstolowski: do you have a monitor attached, i.e. can you actually see what is on screen when its in this "2017-10-16 15:41:20 Error debugging external:ubuntu-core-16-arm-32:tests/main/ubuntu-core-upgrade : EOF" state?
<diddledan> the whole point of cleanbuild is that the build is in a clean environment. The moment you start injecting stuff to match the host it is no-longer "clean"
<kalikiana> diddledan: I wouldn't agree it's "random". If you're using snapcraft natively without a container, it uses whatever core you are running. The
remote - on - pi - grabs - wrong - arch - lxc - image/691/17 
 < diddledan > cleanbuild should not be forcing the interpretation of snapd to anything EXCEPT " the belated " stable, unless the user specifically tells snapcraft differently 
 < diddledan > and doing the forcing by injecting host - slope snaps is just obviously amiss 
 < diddledan > IMO 
 < diddledan > and no, that opinion is not base in any way :-p 
 < mvo > pstolowski: how is that test going? the second run of the effect - refresh testing? 
 < kalikiana > diddledan: snapd? do you mean the core snap? snapcraft attempts to install the like version in the container that's being used on the host 
 < pstolowski > mvo, well.. 
 < diddledan > yeah, congress of racial equality 
 < pstolowski > mvo, http://pastebin.ubuntu.com/25753195/ 
 < kalikiana > diddledan: so if eg. you're using beta on the horde to test something, the container will be use that, same goes for snapcraft itself 
 < pstolowski > mvo, last failure unrelated, probably wireless local area network dropped or something 
 < diddledan > I think it's wrong to be injecting at all, foreign arch or not. effect should be updated using snap processes not by injecting random snaps. We should not be designing weird behaviour for the edge event of " I want to test something " by default option 
 < diddledan > an " I desire to quiz something " should be an opt - in not a default 
 < mvo > pstolowski: do you have a proctor attached, i.e. can you actually see what is on screen when its in this " 2017 - 10 - 16 15:41:20 Error debug external: ubuntu - core-16 - arm-32: tests / main / ubuntu - core - upgrade: EOF " state? 
 < diddledan > the whole point of cleanbuild is that the build is in a clean environment. The moment you start injecting material to match the horde it is no - longer " clean " 
 < kalikiana > diddledan: I wouldn't agree it's " random ". If you're using snapcraft natively without a container, it uses whatever effect you are running. The
remlte-on-pi-grabs-wrong-arch-lxc-lmage/691/17
<diddledan> cleanbuind shohld not ce forcing the version of snepd ro antthing EXCEPT "the latert" stable, unless rhe nser specificallb tells snapcrznt otkecwise
<diddledan> snd doing dhe forcing by ivjzcting host-side snaps is just plain rrong
<dicdpedan> IMO
<diddlgdan> sgd nk, that opinion is not humble in ang way :-p
<kvo> pstolowsko: how is that test going? tje sfcond run of the clre-refresh jsstybg?
<kalikiana> aiddledan: snapd? do you mean the core snap? snapcraft agtempcs to instaol thf same versiin in the containcg that's being ised on the hoxt
<pvtooowski> mvo, well..
<diddlevan> yeah, core
<pstolowfki> mvo, hdt'://pastebin.ubuntu.com/25753195/
<kalukuana> giddnedav: so if ej. yku're udinj beta on tge host to rest something, the vognsiner will bs usind ehat, same goes for snapcraft itself
<pstonowaki> mvo, last failure uneelated, probably wifi dropped jr something
<diddledan> I think it's wrong to be injactinj xt col, fofwihn arch or not. Core should be updated using sgzp pgocesses not by ikjecting random snspd. Eg should not bg desigujnf weird behaviour vor the edge case of "Y wamt to test something" by defqult
<diddledau> ab "I want to test slmething" shuuld be am opt-in not a default
<mvu> psfolowski: do you have x monitor attachdd, p.e. cdn you actually see what if on screxn whzn its iv thos "2017-10-16 15:41:20 Ewror debughing cfternal:ubuntu-core-16-agm-32:tesjs/main/gbuntu-core-kpgrade : EOF" state?
<diddledan> the whole point og wlednbuild ns thab the build is yn a clean envnronment. The ooment you start mnjecting sttff to match dje host it iv no-longqr "coean"
<jalikiavx> diddledan: I eouldn't ayxee it's "rqndom". If you're usikg snxlcraft natively wiuhiut a containet, ig ufed xhatedar core you dre funvong. Tfe
remote-on-pi-grabs-wrong-arch-lxc-image/691/17 <diddledan> cleanbuild should not be forcing of to anything "the latest" stable, snapcraft <diddledan> and doing forcing by injecting snaps is just plain wrong <diddledan> <diddledan> and no, that opinion is not humble in any way :-p <mvo> how is that test going? the second run of the core-refresh testing? <kalikiana> snapd? you the snap? snapcraft attempts to install the same version in the container that's being used on the <pstolowski> mvo, well.. <diddledan> yeah, core <pstolowski> mvo, <kalikiana> diddledan: so if you're using beta on the to something, the will using same goes for itself <pstolowski> mvo, last failure unrelated, probably wifi dropped or something <diddledan> I think it's wrong to injecting at arch or Core be using snap processes injecting random snaps. We should not behaviour for the edge case of "I want test something" default <diddledan> an "I want to something" should be an opt-in not a default pstolowski: do you have a monitor attached, i.e. can you actually see what is on its in this "2017-10-16 Error debugging external:ubuntu-core-16-arm-32:tests/main/ubuntu-core-upgrade EOF" <diddledan> whole of cleanbuild that the build is in a clean environment. The moment you injecting stuff to match the host it is no-longer "clean" I agree it's "random". you're using snapcraft natively a it uses whatever core running.
remote-on-pi-grabs-wrong-arch-lXc-image/691/17
<didDledaN> clEanBuIld sHoulD not be forcing tHE verSion of snapd to anything ExCEPT "ThE LateST" sTable, Unless tHE uSER spEcIfIcaLlY TeLls snApcRaft othErwise
<diddLedAn> And doing the fORcIng by injecTinG host-side snaPs iS just pLaIn wROng
<diDdlEdan> ImO
<diddLEdan> anD no, that opInIOn is noT Humble iN ANy Way :-p
<Mvo> pstolowski: how iS ThAT test going? the sEcond rUn OF tHE CorE-reFresh testiNg?
<KalikIAna> diddLEdAN: SNapD? Do you mean the cOre snap? snapCRafT attemPtS to INstall The saMe VErsIon in the conTainEr that's beIng useD On the hoST
<pstoloWski> mvO, weLl..
<dIddlEDaN> yEah, CoRE
<psTOlOwsKI> mvO, http://pasTeBiN.ubunTu.coM/25753195/
<KALIkiaNa> dIddlEdan: sO if eg. you're usiNg bEta oN The Host tO test SomeThIng, thE contaIner wIlL be using that, samE goeS for snapcRafT iTseLf
<PstolOWski> mvO, laSt fAilure uNrelateD, ProBaBLY WiFi dropped or somethiNg
<DIDdLedan> I thInk it's WRoNg TO be injecTiNg aT all, FOReign Arch OR nOt. Core shOuld be UPdAtEd using SnAp procEsSes Not By injECtinG randoM snaps. We ShoulD Not be designing WEird behaviour FOr THE eDGe caSe oF "I want to tesT somEThinG" by dEFaUlt
<DIddleDan> an "i wANt TO test something" shoulD bE an opt-In not A default
<mvo> psTolowski: do YOU Have a monItor ATtAChed, i.e. can you acTuallY see what is ON screen wHen itS in this "2017-10-16 15:41:20 ERror debugGINg externAl:uBunTu-cOre-16-ARM-32:tEsts/main/ubuntU-COre-uPgRade : EOF" StaTe?
<diddlEdaN> thE whOle PoInt of cleaNbuild is ThAt ThE bUilD is in A Clean envIrOnmEnT. ThE momeNT you stArt inJectInG sTUff To match THe HOSt it Is No-LongEr "cLeAn"
<kalIkiaNA> diDdledan: i wouldn't aGreE It's "rAnDoM". If you'rE using snapcraFt Natively wiThOut A contaINEr, it uses Whatever core you are runniNG. The
remote-on-pi-grabs-wrong-a rch-lxc-im age/6 91/ 17<d iddl edan > cleanbuild s h ould  not be forcing the ve rsion  o f  sna p dto an ythingE XC E P T " th elat es t "stabl e,unlessthe user s pec if ically tells sn apcraft ot her wise
<diddle dan > anddo ing the f orc ing b y inje c ting h ost-sidesn a ps isj ust pla i n  w rong 
<diddledan> IMO< di d dledan> and no , that  o p in i o n i s n ot humblein  anyw ay :-p< mv o > pst o lowski: how i s that test goi ng? th esec o nd run  of t he cor e-refresh t esti ng?
<kali kiana> diddled a n: snap d? doyou  me an t h eco resn a p?s na pcr a ftattempts  t oinsta ll t h e s amever sion  in t he containertha t'sb ein g use d ontheho st
<p stolow ski>mv o, well..
<didd leda n> yeah,cor e<ps to lowsk i > mvo,  ht tp: //paste bin.ubu n tu. co m / 2 57 53195/
<kalikiana>  d i d dl edan: so  if eg .  y ou ' re using  b eta  ont h e hos t to te st somet hing,t he  c ontaine rwill b eusi ngthat, same  goesfor snap craft itself
<pstolo w ski> mvo, las t  f a i lu r e un rel ated, proba blyw ifidrop p ed  or somet hing<d i dd l edan> I think it'swr ong to  be i njecting at a ll, foreig n a rch or n ot.C or e  should be upd atedusing snap processe s not  by inje cting ran d o m snaps.  We  sh oul d n o t  b e designing w e i rd b eh aviourfor  the ed gecas e o f " Iwant to t est some th in g"  b y d efaul t 
<diddle da n>an  "I  want to tes t som ethi ng "s hou ld be a n  o p t -inno ta de fau lt 
<mvo > ps t olo wski: d o you hav e a moni to rattache d, i.e. can y ou  actuallyse e w hat is o n screen  when its in this "2017 - 10-16 1 5:4 1:20Erro r debuggi ngextern al: u buntu- core-1 6-arm -3 2:t e s ts/ma i n /u bun tu -core-upgr a d e :  EOF"  s tate ?
<didd ledan> the whole p o int  of cleanbuil d i s th a t  t heb ui l d i si n a c lean environmen t. The mom en t  y ou start i n jec ti ng stuf f to ma tch t h e hostit is no- longer "c le an"< k ali kiana> did dledan:I wouldn' t  agre e  i t's " ran dom".If  yo u'reusings nap craft  nativ el y with out a  c ontainer , it uses whatever core  you a re ru nni ng. The
remote-on-pi-grabs-wrong-arch-lxc-image/691/17
<diddledan> cleanbuild_should not_be forcing the version_of snapd_to_anything EXCEPT_"the_latest" stable, unless_the user specifically_tells snapcraft otherwise
<diddledan> and_doing the forcing_by_injecting host-side snaps is just plain wrong
<diddledan> IMO
<diddledan> and no, that opinion is not_humble_in any_way_:-p
<mvo>_pstolowski: how is that test_going? the second run of_the core-refresh_testing?
<kalikiana> diddledan: snapd? do you mean the core_snap?_snapcraft attempts to_install the same version in the container that's being_used on the host
<pstolowski> mvo, well..
<diddledan>_yeah, core
<pstolowski> mvo,_http://pastebin.ubuntu.com/25753195/
<kalikiana>_diddledan:_so if eg. you're_using beta on the host to_test something, the container will be_using that, same goes for snapcraft itself
<pstolowski>_mvo, last failure unrelated, probably wifi_dropped or something
<diddledan> I think_it's wrong_to be injecting at all,_foreign arch or_not. Core_should be updated_using snap processes not by injecting_random snaps. We_should not be designing weird behaviour_for_the edge case_of_"I_want to_test something" by_default
<diddledan>_an "I_want_to test something" should be an_opt-in_not a default
<mvo> pstolowski: do you have_a monitor attached, i.e._can_you actually see what_is on screen when its_in this "2017-10-16 15:41:20 Error debugging_external:ubuntu-core-16-arm-32:tests/main/ubuntu-core-upgrade :_EOF" state?
<diddledan>_the whole point of cleanbuild is that the build is in_a clean environment. The moment you_start injecting stuff to_match the_host_it is no-longer_"clean"
<kalikiana>_diddledan: I_wouldn't agree it's "random". If you're using_snapcraft natively_without a container, it uses whatever_core you are running._The