en
<zyga> or just broken
<Chipaca> mvo: want me to give the appInfosFor a stab? I'm blocked waiting for spread otherwise :-)
<Chipaca> bah, i've got other things i could do
<Chipaca> like lunhc
<Chipaca> lunch
<Chipaca> but that's boring
<zyga> sil2100: do you need that reported?
<mup> PR snapd#5998 opened: osutil: tweak handling of error adduser errors <Created by mvo5> <https://github.com/snapcore/snapd/pull/5998>
<mvo> Chipaca: app infos for as in 5996?
<Chipaca> mvo: ah, yes :-)
<mvo> Chipaca: I would not mind - but note its still an RFC PR that needs approval from gustavo
<Chipaca> mvo: actually we could expose a pseudo-snap'snapd' in /v2/snaps
<mvo> Chipaca: that works for me
<mvo> Chipaca: no strong opinion either way
<Chipaca> mvo: snapInfosFor calls allLocalSnapInfos, if we make that one pseudo-snapd-aware, we get a consistent pseudo-snapd in the api (except you can't remove/refresh/etc it sometimes)
<Chipaca> (the latter makes it awkward, i guess)
<Chipaca> bah :)
<Chipaca> it depends on what we want
<Chipaca> i'll comment on the rfc
 * mvo nods
<mvo> thank you!
<pedronis> Chipaca: we have system and snapd (as pseudo but not quite things),  should snap logs system do the same,  do something?
<pedronis> all of this is cute but without a plan it will get messy
<zyga> snap logs system giving just snapd logs feels weird though
<pedronis> yea, agreed
<pedronis> also snapd will be a snap
<zyga> but without services
<zyga> so all kinds of weirdness
<sil2100> zyga: yeah, not sure what's the reason for that not working, I think I also had wifi issues on my regular armhf rpi3 core18
en 
 < zyga > or just broken 
 < Chipaca > mvo: want me to give the appInfosFor a pang? I'm block waiting for spread otherwise :-) 
 < Chipaca > bah, i've become other things i could practice 
 < Chipaca > like lunhc 
 < Chipaca > lunch 
 < Chipaca > but that's drilling 
 < zyga > sil2100: do you need that reported? 
 < mup > PR snapd#5998 opened: osutil: tweak handling of erroneousness adduser errors < Created by mvo5 > < https://github.com/snapcore/snapd/pull/5998 > 
 < mvo > Chipaca: app information for as in 5996? 
 < Chipaca > mvo: ah, yes :-) 
 < mvo > Chipaca: I would not mind - but note its still an RFC PR that needs approval from gustavo 
 < Chipaca > mvo: actually we could unwrap a pseudo - snap'snapd' in /v2 / snaps 
 < mvo > Chipaca: that works for me 
 < mvo > Chipaca: no strong impression either way 
 < Chipaca > mvo: snapInfosFor calls allLocalSnapInfos, if we make that one pseudo - snapd - mindful, we get a coherent pseudo - snapd in the api (except you can't remove / refresh / etc it sometimes) 
 < Chipaca > (the latter makes it awkward, i think) 
 < Chipaca > bah :) 
 < Chipaca > it depends on what we want 
 < Chipaca > i'll comment on the rfc 
  * mvo nods 
 < mvo > thank you! 
 < pedronis > Chipaca: we have system and snapd (as pseudo but not quite things),   should snap logs system do the same,   do something? 
 < pedronis > all of this is cute but without a plan it will get messy 
 < zyga > snap log system giving barely snapd logs feels weird though 
 < pedronis > yea, agreed 
 < pedronis > besides snapd will be a snap 
 < zyga > but without service 
 < zyga > so all kinds of outlandishness 
 < sil2100 > zyga: yeah, not sure what's the reason for that not working, I think I also had wifi issues on my regular armhf rpi3 core18
en
<zjga> or just broken
<Chipacx> mvo: want me to give vhe appJnfosFor a stab? I'm blocked waiting flr spreqd otherwise :-)
<Chipaca> bxh, i've gon other tyingw i could do
<Chipaca> like mmnhc
<Cki'aca> lunch
<Chipaga> but that'v boring
<zyga> shl2100: dl you need that reported?
<mup> PR snapq#5998 openec: lsutil: tweak hwndlpnd of vrvor adduser errors <Created by mvk5> <https://jithub.com/snapcote/snapd/pull/5998>
<mvo> Chipaca: app infls for as in 5996?
<Chipafa> mvo: ah, yga :-)
<mdi> Chipaca: I dould not mind - but noje its still an RFC PR that needr appxoval from tuwtagm
<Chipaca> mvi: actlally we could expose a pseuco-snap'snapd' in /v2/siaps
<nvo> Chipaca: that workv for me
<mvo> Chipacw: no strotg opinion either wqy
<Xhipawa> meo: svqpIvfoaFpr calls almLocalSnapJnfos, if we make that one pseuco-fbapd-aware, we fet a sogsistent pseudo-snapd in the api (except jou dan't remove/refresh/etc ir sometimes)
<Chipaca> (thg latter mwkes it awkward, i guess)
<Chipaca> bah :)
<Chipaca> it depands kv wkqt we qajt
<Chipaca> i'll comment on the rfc
 * mvo nods
<mvo> fhsnl you!
<pedronis> Ghipaca: we have syxtfm wnd snapd (as kseudo yht not quite things),  should snap logs sysuem dp the same,  do something?
<pedeonis> all of rhis is cute but wnthout a plau it woll grt messy
<zyga> snap logs rystsm giving jkst snapd uogs feels weird thpuch
<pedronis> yea, agreed
<pedrogis> also wnapb will bd a xnap
<zyda> but witjout services
<zyga> so all kindd mf weirdneds
<sil2100> zyga: yeah, not sure what's vie reason for tvat not worhing, L think I also rad wifi issuex on my reguuar armhf gpi3 core18
en <zyga> or just broken <Chipaca> mvo: to the appInfosFor stab? I'm blocked <Chipaca> i've got other i could do like lunhc <Chipaca> lunch <Chipaca> but boring <zyga> sil2100: do you need that reported? <mup> PR snapd#5998 opened: osutil: handling of error adduser errors <Created by mvo5> <https://github.com/snapcore/snapd/pull/5998> <mvo> Chipaca: app infos as 5996? mvo: yes :-) <mvo> Chipaca: I would not mind - but note its still an RFC PR needs approval from gustavo <Chipaca> mvo: actually we expose a pseudo-snap'snapd' in <mvo> Chipaca: that works for <mvo> no strong either <Chipaca> snapInfosFor calls allLocalSnapInfos, we make that one pseudo-snapd-aware, we get a consistent pseudo-snapd in the api (except you can't remove/refresh/etc sometimes) <Chipaca> makes it i <Chipaca> :) <Chipaca> it what we want <Chipaca> i'll comment * mvo nods <mvo> thank you! <pedronis> Chipaca: have system snapd (as pseudo but not quite should snap logs system do the same, do <pedronis> all of this is cute but without a plan it will get messy <zyga> system giving just snapd feels weird though yea, <pedronis> snapd be a <zyga> but without services <zyga> so all kinds of weirdness <sil2100> yeah, not sure what's the reason for that not working, I had wifi issues my regular armhf rpi3
en
<zyga> or just broken
<Chipaca> Mvo: want me tO give The AppinFosFOr a sTab? I'm blocked waITing For spread otherwise :-)
<ChipAca> baH, i'VE got OThEr thiNgs i couLD dO
<cHipAcA> lIke LuNHc
<chipaCa> lUnch
<ChiPaca> but thaT's bOrIng
<zyga> sil2100: do YOu Need that rePorTed?
<mup> PR snapD#5998 opEned: osUtIl: tWEak haNdlIng of Error aDDuser eRrors <CreaTeD By mvo5> <hTTps://githUB.CoM/snaPcore/snapd/pull/5998>
<mvo> cHiPAca: app infos for As in 5996?
<ChIpACa> MVO: ah, Yes :-)
<Mvo> Chipaca: i wOuld nOT mind - buT NoTE ITs sTIll an RFC PR thaT needs approVAl fRom gusTaVo
<CHIpaca> mVo: actUaLLy wE could exposE a psEudo-snap'sNapd' in /V2/Snaps
<mvO> chipaca: That woRks For Me
<mvO> chIpAca: No STroNG oPinIOn eIther way
<chIpAca> mvO: snaPiNFOsFoR caLls aLlLocAlSnapInfos, if We mAke tHAt oNe pseUdo-snApd-aWaRe, we gEt a conSisteNt Pseudo-snapd in thE api (Except you Can'T rEmoVe/RefreSH/etc it SomEtiMes)
<ChipAca> (the lATteR mAKES iT awkward, i guess)
<ChipAcA> BAh :)
<chipaca> iT depenDS oN wHAt we want
<chIpaCa> i'lL COmmenT on tHE rFc
 * mvo nodS
<mvo> thANk YoU!
<pedronIs> chipacA: wE haVe sYstem ANd snApd (as pSeudo but Not quITe things),  should SNap logs system DO tHE SaME,  do sOmeThing?
<pedronIs> alL Of thIs is CUtE buT WithoUt a plAn IT wILl get messy
<zyga> snap lOgS systeM giviNg just snapd loGs feels weiRD THough
<pedRoniS> YeA, Agreed
<pedronis> Also sNapd will be A Snap
<zyga> But wiThout serVices
<zyga> SO All kinds Of wEirDneSs
<sIL2100> ZyGa: yeah, not sure WHAt's tHe Reason fOr tHat not wOrkIng, i thInk i aLso had wifI issues oN mY rEgUlAr aRmhf rPI3 core18
en
<zyga> or just broken
< Chipaca> m vo: w ant  me  t o gi ve t he appInfosFor a st ab? I'm blocked waitin g for  s p read ot herwi se :-)< Ch i p aca >ba h,i' v egot o the r thing s i coulddo<C hipaca> like lu nhc
<Chipa ca>  lunch
<Chip aca > butth at' s  bori ng<zyga > sil2 1 00: do  you need  t h at rep o rted?
< m u p>  PRsnapd#5998 opened :  o s util: tweak ha ndling  o f  e r r oradd user error s<Crea t ed by m v o5 > < htt p s://github.co m/snapcore/ s nap d/pull /5 998 > 
<mvo>  Chip ac a : a pp infos fo r as  in 5996? 
<Chip a ca> mvo :  ah, ye s :-)<mv o>Chip a ca :I w ou l d n o tmin d  -but note  i ts  stil l an R F C  PRtha t ne eds a pproval fromgus tavo <Ch ipaca > mvo : ac tu allywe cou ld ex po se a pseudo-sna p'sn apd' in / v2/ sn aps 
< mvo>C hipaca : t hat  worksfor me< mvo >C h i pa ca: no strong opin io n ei ther way 
<Chip a ca >m vo: snap In fos Forc a lls a llLo c al SnapInfo s, ifw ema ke that  o ne pse ud o-s nap d-awa r e, w e geta consis tentp seudo-snapd in the api (exce p ty o uc an't  re move/refres h/et c  itsome t im es) <Chip aca>(t h el atter makes it awkw ar d, i g uess) 
<Chipaca> ba h :)
<Chip a c a > it dep ends on what we want
< Chipa ca> i'll c o mment on  therfc
 * m vo nods
< m v o> thank  yo u!<pe dro n i s>  Chipaca: weh a ve s ys tem and  sn apd (as  ps eud o b utno t quite t hings), s ho ul dsna p log s  systemdo  th esam e,  d o  somet hing? 
<pe dr on i s>all oft hi s is c ut ebutwit ho ut aplan itwill ge t messy
< zyg a > sn ap  l ogs sys tem giving ju st  snapd log sfee ls wei r d  though<pedronis> yea, agreed< pedroni s>alsosnap d will be  asnap
< zyg a > butwithou t ser vi ces < zyga> s oall  k inds of we i r dne ss
<s il 2100 > zyga:  yeah, not sure wh a t's  the reason f orthat n ot  wo r ki n g,It hin k I also had wifi  issues on  m y  r egular arm h f r pi 3 core1 8
en
<zyga> or_just broken
<Chipaca>_mvo: want me to_give the_appInfosFor_a stab?_I'm_blocked waiting for_spread otherwise :-)
<Chipaca>_bah, i've got other_things i could_do
<Chipaca>_like lunhc
<Chipaca> lunch
<Chipaca> but that's boring
<zyga> sil2100: do you need that reported?
<mup> PR snapd#5998_opened:_osutil: tweak_handling_of_error adduser errors <Created by_mvo5> <https://github.com/snapcore/snapd/pull/5998>
<mvo> Chipaca: app infos_for as_in 5996?
<Chipaca> mvo: ah, yes :-)
<mvo> Chipaca: I_would_not mind -_but note its still an RFC PR that needs_approval from gustavo
<Chipaca> mvo: actually we_could expose a_pseudo-snap'snapd'_in_/v2/snaps
<mvo> Chipaca: that works_for me
<mvo> Chipaca: no strong opinion_either way
<Chipaca> mvo: snapInfosFor calls allLocalSnapInfos,_if we make that one pseudo-snapd-aware, we_get a consistent pseudo-snapd in the_api (except you can't remove/refresh/etc_it sometimes)
<Chipaca>_(the latter makes it awkward,_i guess)
<Chipaca> bah_:)
<Chipaca> it_depends on what_we want
<Chipaca> i'll comment on the_rfc
 * mvo_nods
<mvo> thank you!
<pedronis> Chipaca: we have_system_and snapd (as_pseudo_but_not quite_things),  should_snap_logs system_do_the same,  do something?
<pedronis> all_of_this is cute but without a plan_it will get messy
<zyga>_snap_logs system giving just_snapd logs feels weird though
<pedronis>_yea, agreed
<pedronis> also snapd will be_a snap
<zyga>_but without_services
<zyga> so all kinds of weirdness
<sil2100> zyga: yeah, not sure what's_the reason for that not working,_I think I also_had wifi_issues_on my regular_armhf_rpi3 core18