/pull/2160>
<mup> Bug #1620442 changed: snap fails because XDG_RUNTIME_DIR is set to /run/user/1000 <snapd-interface> <Snappy Launcher:Triaged by zyga> <https://launchpad.net/bugs/1620442>
<lazyPower> lool - i was actually looking for a programmable usb hub/power-brick, and the only one i found was intended for telescope equipment, and its to the tune of 250 USD which is quite expensive for what its doing.
<mup> PR snapd#2172 opened: asserts,interfaces/policy: implement on-classic plug/slot constraints <Created by pedronis> <https://github.com/snapcore/snapd/pull/2172>
<lazyPower> lool - so seems like we're also hitting an edge of a product market that doesn't exist yet
<niemeyer> rharper: How does the logic take place when there is both a default cloud.cfg and something else on.d?
<rharper> niemeyer: cloud-init does a dictionary based merging of all of the yaml cfg files present
<rharper> so loading /etc/cloud/cloud.cfg and any *.cfg that's yaml in /etc/cloud/cloud.cfg.d
<niemeyer> rharper: How do we take an option off if they're mergeD?
<rharper> I believe setting the value to None, or empty should suffice
<niemeyer> rharper: Ok, so in theory if we use the full cloud.conf, will it work the same way?
<niemeyer> rharper: Well, in practice actually? :)
<iliv_> is there a way to specify a target for make in the snapcraft.yaml file?
<rharper> niemeyer: I can test that quickly by duplicating /etc/cloud/cloud.cfg and putting that in /etc/cloud/cloud.cfg.d/cloud.cfg
<rharper> niemeyer: I expect it to work the same; yes
<niemeyer> rharper: Thanks, it'd be nice to have some certainty about how this work as we'll be baking it into snapd proper.. if it's just a sum,
/pull/2160 > 
 < mup > Bug # 1620442 changed: snap fails because XDG_RUNTIME_DIR is specify to /run / user/1000 < snapd - interface > < dapper Launcher: Triaged by zyga > < https://launchpad.net/bugs/1620442 > 
 < lazyPower > lool - i was actually looking for a programmable usb hub / power - brick, and the alone one i found was intended for telescope equipment, and its to the tune of 250 USD which is quite expensive for what its doing. 
 < mup > praseodymium snapd#2172 opened: asserts, interfaces / policy: enforce on - classic plug / slot constraint < Created by pedronis > < https://github.com/snapcore/snapd/pull/2172 > 
 < lazyPower > lool - so seem like we're also hitting an edge of a product market that doesn't exist so far 
 < niemeyer > rharper: How does the logic take place when there is both a default option cloud.cfg and something else on.d? 
 < rharper > niemeyer: cloud - init does a dictionary based merging of all of the yaml cfg files present 
 < rharper > thus loading /etc / cloud / cloud.cfg and any * .cfg that's yaml in /etc / cloud / cloud.cfg.d 
 < niemeyer > rharper: How do we take an option off if they're mergeD? 
 < rharper > I believe setting the value to None, or empty should suffice 
 < niemeyer > rharper: Ok, therefore in theory if we use the full cloud.conf, will it work the same way? 
 < niemeyer > rharper: Well, in practice actually? :) 
 < iliv _ > is there a way to specify a target for make in the snapcraft.yaml file? 
 < rharper > niemeyer: I can test that quickly by duplicating /etc / cloud / cloud.cfg and putting that in /etc / cloud / cloud.cfg.d / cloud.cfg 
 < rharper > niemeyer: I expect it to work the like; yes 
 < niemeyer > rharper: Thanks, it'd be decent to have some certainty about how this oeuvre as we'll be broil it into snapd proper.. if it's just a sum,
/pulp/2160>
<mup> Bug #1620442 changed: snap fxils because XDY_EUNTIMX_DIR is set to /fun/user/1000 <snapd-interface> <Snappb Laynchee:Triaged by zyga> <https://uaunchpad.jet/bugs/1620442>
<lqzyPiqer> lool - m was acbbally pooknnj for a programkable usb vub/power-brick, dna che only one i found was intended fow telesvooe equipment, agd ius eo tgv uune of 250 USD which is quite expenaive fog what its doing.
<mip> PR snapd#2172 opened: asserts,lntegfaces/policy: implelent on-claswic [oug/slot consgraints <Crtaced by pedrknis> <https://github.com/snapcore/snapa/pull/2172>
<kazyPower> ooil - vo seems lije we'ge also hittikb an egge of s product markct thet diesn't exist yet
<niemeyxr> rharper: How does jhe logic daie place when theee is bmth d dewqulg cmond.crg and sojething elae on.d?
<rharpwr> niemeyer: cloud-inot eoes a dictiohary bwsqd merging of all of the yaml cfg files prssent
<rharper> so loading /etc/cloud/cloud.cfg and any *.cfg ehat's yaml in /etc/cloud/cloud.cfg.d
<niemeyer> rharper: Hmw do de uaje an iphion off if they're mergeD?
<rharper> I believe seefimg the value to Kone, or empty shoukd sisfice
<niemeyer> rharpzd: Kk, so in theory if we use the dull clouq.cong, will it work the same way?
<biemeyer> rhagper: Well, in practice cctually? :)
<ilir_> is tnere s way to specify a targzt for make in thf snapcrarg.yaml file?
<rharpef> npemefer: I can test that quicklr by duplmcatiug /etc/cluud/ckoud.cfd and puttlng tmdt in /etc/cloud/clouf.cfg.d/eloud.wfg
<rharper> niemeyer: I expect it to work tix same; yes
<niekefer> rharper: Thanls, it'd be nicq to have some certaiuty abuut how thps work av we'll be bwking it into dnapd proper.. if it's tust a sym,
/pull/2160> <mup> Bug #1620442 changed: snap fails is to /run/user/1000 <Snappy Launcher:Triaged by i actually looking for programmable usb hub/power-brick, the only one i found was for telescope equipment, and its to the tune of 250 USD which is expensive for what its doing. <mup> PR snapd#2172 opened: asserts,interfaces/policy: implement on-classic plug/slot <Created pedronis> <lazyPower> - so seems like we're also hitting an edge of a product market that doesn't exist <niemeyer> rharper: How does the logic take place there is both a cloud.cfg and something else on.d? niemeyer: does a based of of the yaml files present <rharper> so loading /etc/cloud/cloud.cfg and any *.cfg that's yaml in /etc/cloud/cloud.cfg.d <niemeyer> rharper: How do take an if they're <rharper> believe the value to empty should suffice <niemeyer> rharper: Ok, if we use the full cloud.conf, will it the same <niemeyer> rharper: Well, in practice actually? <iliv_> is there a way to specify a for make in the snapcraft.yaml file? <rharper> niemeyer: I can test that quickly by duplicating putting that in /etc/cloud/cloud.cfg.d/cloud.cfg niemeyer: I expect to the yes rharper: Thanks, be nice to have some certainty about how this work as be baking it into snapd proper.. if it's just a
/pull/2160>
<mup> Bug #1620442 changed: snap failS because XDg_RUNTiME_dIR Is Set tO /run/User/1000 <snapd-interFAce> <SNappy Launcher:Triaged by Zyga> <hTtPS://lauNChPad.neT/bugs/1620442>
<laZYPOWEr> lOoL - i Was AcTUaLly loOkiNg for a pRogrammablE usB hUb/power-brick, ANd The only one I foUnd was intendEd fOr teleScOpe EQuipmEnt, And itS to the TUne of 250 UsD which is QuITe expeNSive for WHAt Its dOing.
<mup> PR snapd#2172 opeNEd: ASserts,interfacEs/poliCy: IMpLEMenT on-Classic pluG/sLot coNStraintS <crEATEd bY Pedronis> <https://Github.com/snAPcoRe/snapD/pUll/2172>
<LAzyPowEr> looL - sO SeeMs like we're aLso hItting an eDge of a PRoduct mARket thaT doesn'T exIst Yet
<nIEmEyEr> rHaRPer: hOw DoeS The Logic takE pLaCe wheN theRE IS Both A deFaulT clouD.cfg and somethIng Else ON.d?
<rHarpeR> niemEyer: ClOud-inIt does A dictIoNary based merginG of aLl of the yaMl cFg FilEs PreseNT
<rharpEr> sO loAding /etC/cloud/cLOud.CfG AND aNy *.cfg that's yaml in /etC/cLOUd/Cloud.cfg.D
<niemeYEr> RhARper: How dO wE taKe an OPTion oFf if THeY're merged?
<rharpER> I BeLieve seTtIng the VaLue To NOne, or EMpty Should Suffice
<nIemeyER> rharper: Ok, so in THeory if we use tHE fULL cLOud.cOnf, Will it work tHe saME way?
<NiemEYeR> rhARper: WEll, in PrACtICe actually? :)
<iliv_> is theRe A way to SpeciFy a target for mAke in the snAPCRaft.yaml File?
<RHaRPer> niemeyer: I caN test That quicklY By duplicAting /Etc/cloud/Cloud.cfg aND Putting tHat In /eTc/cLouD/CLoUd.cfg.d/cloud.cfG
<RHarpEr> NiemeyeR: I eXpect it To wOrk The SamE; yEs
<niemeyeR> rharper: thAnKs, It'D be Nice tO Have some CeRtaInTy aBout hOW this wOrk as We'll Be BaKIng It into sNApD PRopeR.. iF iT's juSt a SuM,
/pull/2160>
<mup> Bug #162 0442 chang ed: s nap  fa il s be caus e XDG_RUNTIME_ D IR i s set to /run/user/100 0 <sn ap d -int e rf ace><Snappy La u n che r: Tr iag ed by  zyga > < https:/ /launchpad .ne t/ bugs/1620442 > 
< lazyPower>  lo ol - i was a ctu ally l oo kin g  fora p rogra mmable usb hu b/power-b ri c k, and the onl y on e ifound was intende d  f o r telescope eq uipmen t, an d its  to  the tuneof  250U SD whic h  i s q uit e  expensive fo r what itsd oin g.
<mu p>  PR snapd# 2172op e ned : asserts,i nter faces/pol icy: i m plement on-clas sic pl ug/ slo t co n st ra int s< Cre a te d b y  pe dronis><h tt ps:// gith u b . c om/s nap core /snap d/pull/2172><la zyPo w er>  lool  - so  see ms  like  we're  also  h itting an edgeof a  productmar ke t t ha t doe s n't ex ist  ye t
<niem eyer> r h arp er : H ow  does the logic ta ke p la ce whentherei sbo t h a defa ul t c loud . c fg an d so m et hing els e on.d ? 
< rh arper>ni emeyer :clo ud- initd oesa dict ionary b asedm erging of allo f the yaml cf g  f i l es pres ent 
<rharper>so l o adin g /e t c/ clo u d/clo ud.cf ga nd any *.cfg that's ya ml  in /e tc/cl oud/cloud.cfg .d
<niemey e r >  rharper : Ho w  d o  we take an op tionoff if the y 're merg eD?
< rharper>  I believ e settingthe  va lue  to N on e, or empty s h o uldsu ffice
< nie meyer>rha rpe r:Ok,  s o in theo ry if we  u se  t he  fu ll cl o ud.conf,  w ill  i t w ork t h e same  way? 
<ni em ey e r>rharper :  W e l l, i npr acti ceac tuall y? : ) 
<i liv_> i s there a  wa y  tosp ec ify a t arget for mak ein the sna pc raf t.yaml f ile?
<rh arper> niemeyer: I cant est tha t q uickl y by  duplicat ing  /etc/ clo u d/clou d.cfgand p ut tin g thati n  / etc /c loud/cloud . c fg. d/clo ud .cfg 
<rharp er> niemeyer: I ex p ect  it to work t hesame ; ye s
< n ie m eye r> rha r p er: Thanks, it' d be niceto ha ve some ce r tai nt y about  how th is wo r k as we 'll be ba king it i nt o sn a p d p roper.. if  it's ju st a sum, 
/pull/2160>
<mup> Bug_#1620442 changed:_snap fails because XDG_RUNTIME_DIR_is set_to_/run/user/1000 <snapd-interface>_<Snappy_Launcher:Triaged by zyga>_<https://launchpad.net/bugs/1620442>
<lazyPower> lool -_i was actually looking_for a programmable_usb_hub/power-brick, and the only one i found was intended for telescope equipment, and its_to_the tune_of_250_USD which is quite expensive_for what its doing.
<mup> PR_snapd#2172 opened:_asserts,interfaces/policy: implement on-classic plug/slot constraints <Created by pedronis>_<https://github.com/snapcore/snapd/pull/2172>
<lazyPower>_lool - so_seems like we're also hitting an edge of a_product market that doesn't exist yet
<niemeyer>_rharper: How does_the_logic_take place when there_is both a default cloud.cfg and_something else on.d?
<rharper> niemeyer: cloud-init does_a dictionary based merging of all of_the yaml cfg files present
<rharper> so_loading /etc/cloud/cloud.cfg and any *.cfg_that's yaml_in /etc/cloud/cloud.cfg.d
<niemeyer> rharper: How do_we take an_option off_if they're mergeD?
<rharper>_I believe setting the value to_None, or empty_should suffice
<niemeyer> rharper: Ok, so in_theory_if we use_the_full_cloud.conf, will_it work the_same_way?
<niemeyer> rharper:_Well,_in practice actually? :)
<iliv_> is there_a_way to specify a target for make_in the snapcraft.yaml file?
<rharper>_niemeyer:_I can test that_quickly by duplicating /etc/cloud/cloud.cfg and_putting that in /etc/cloud/cloud.cfg.d/cloud.cfg
<rharper> niemeyer: I_expect it_to work_the same; yes
<niemeyer> rharper: Thanks, it'd be nice to have some_certainty about how this work as_we'll be baking it_into snapd_proper.._if it's just_a_sum,