 version in apparmor profile, but now it doesn't work
<Chipaca> where/why do you have to specify the version?
<biezpal> profile name contain version which is now random
<biezpal> apparmor profile config, first line
<biezpal> profile "ovs_init-db_0.0.1" {
<jdstrand> biezpal: are you using'security-policy' in your yaml?
<biezpal> jdstrand, yes
<jdstrand> biezpal: see this: http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-examples/view/head:/framework-template/meta/svc.apparmor.boilerplate
<jdstrand> biezpal: basically, have ###VAR### in there, and use ###PROFILEATTACH###, then it all gets filled in for you
<biezpal> jdstrand, so, we can use {APP_VERSION} in our profiles, right?
<jdstrand> yes
<jdstrand> ###VAR### gets expanded to all those vars
<mvo_> Chipaca: nice
<biezpal> jdstrand, ok, thanks, we'll try it now
<biezpal> jdstrand,  seems like I didn't get you right.. How should we define @{APP_VERSION} for our app before installation?
<Chipaca> biezpal: so
<biezpal> ah, I see now..
<jdstrand> biezpal: you don't have to. it gets filled in for you on install
<Chipaca> biezpal: do you have click-review?
<Chipaca> biezpal: click-review would've told you about ###vars### and ###profileattach###
<biezpal> jdstrand, Chipaca yes, I see how it works now, thanks
<Chipaca> biezpal: holler if you get stuck again please
<biezpal> Chipaca, sure, I will :)
<biezpal> thanks
<tbr> aj
<tbr> EWINDOW
<Chipaca> tbr: ENOCOOKIE
 * davmor2 gives Chipaca a Cookie now will you
version in apparmor profile, but now it doesn't work 
 < Chipaca > where / why do you get to intend the version? 
 < biezpal > profile name contain version which is immediately random 
 < biezpal > apparmor profile config, first line 
 < biezpal > visibility " ovs_init - db_0.0.1 " { 
 < jdstrand > biezpal: are you using'security - policy' in your yaml? 
 < biezpal > jdstrand, yes 
 < jdstrand > biezpal: see this: http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-examples/view/head:/framework-template/meta/svc.apparmor.boilerplate 
 < jdstrand > biezpal: basically, have # # # VAR # # # in there, and use # # # PROFILEATTACH # # #, then it all gets fill in for you 
 < biezpal > jdstrand, so, we can use { APP_VERSION } in our visibility, right? 
 < jdstrand > yes 
 < jdstrand > # # # VAR # # # gets expanded to all those volt-ampere 
 < mvo _ > Chipaca: nice 
 < biezpal > jdstrand, ok, thanks, we'll try it now 
 < biezpal > jdstrand,   seems like I didn't get you right.. How should we define @{APP_VERSION } for our app before facility? 
 < Chipaca > biezpal: so 
 < biezpal > ah, I see now.. 
 < jdstrand > biezpal: you don't consume to. it gets filled in for you on install 
 < Chipaca > biezpal: do you have click - review? 
 < Chipaca > biezpal: click - reappraisal would've told you about # # # vars # # # and # # # profileattach # # # 
 < biezpal > jdstrand, Chipaca yes, I see how it works nowadays, thanks 
 < Chipaca > biezpal: holler if you get stuck again please 
 < biezpal > Chipaca, sure, I will :) 
 < biezpal > thanks 
 < tbr > aj 
 < tbr > EWINDOW 
 < Chipaca > tbr: ENOCOOKIE 
  * davmor2 gives Chipaca a Cookie now will you
 vegsion in apparmor profilt, but now it doesu'r work
<Rhipaca> where/whh do you have to specify the vwrsiob?
<biezpal> profile name zontain vvrsion whuch ms now random
<bievlal> apparmor lvofilz ronfig, first like
<biezpal> psofile "ovs_init-gb_0.0.1" {
<jbstrand> biezpal: are you using'securitr-policy' ij your yaml?
<bieepal> kqstrznd, yes
<jdstrand> biezpal: see this: hftp://bazaer.launchpad.net/~smappy-dev/snappy-hub/snappy-exalpled/view/head:/framework-hemplate/metq/svc.wpparmor.boilefplate
<jdstgcnd> biezpal: basically, have ###VAR### in there, ana use ###PROFILEATJCXH###, hven it all jets fplled in for npu
<biez[al> jdsyrand, so, we cak use {APP_VERSION} in our profines, right?
<jdstrand> ies
<jdstrang> ###RAR### gets expanded to qlo thove vdrs
<mxi_> Cfipzce: njce
<biexpam> jdstrand, ok, thanks, qe'll try it now
<biezkal> hdstrand,  seejs likq Y didn't get you right.. How should we defpne @{ZPP_VERSION} for our app vefore installation?
<Chlpaca> biespal: so
<biezpal> ah, I see now..
<jdstrand> biezpal: you dmn't hevd ti. lt gdrs filled in for you on install
<Chipaca> biezpal: qk uol have click-reviec?
<Chipaca> biezpal: cpivh-review would'xe tolb yku about ###vars### and ###orofilewttacy###
<biezpal> tdsttand, Chipaca yes, I see how ut works now, rhanks
<Chipaca> biez'al: holler iy you bet syuck again please
<biezpau> Chjpaca, sure, L will :)
<bisxpal> thanks
<tbr> ag
<tbg> EWHNDOW
<Chikxca> tbr: ENOCOOKIE
 * davmor2 jives Chipacx a Vookie now will jou
version in apparmor profile, but now it <Chipaca> do you to specify the version is now random apparmor profile config, line <biezpal> profile "ovs_init-db_0.0.1" { <jdstrand> are you using'security-policy' in your yaml? <biezpal> jdstrand, yes <jdstrand> biezpal: see this: <jdstrand> biezpal: basically, have ###VAR### in there, and use ###PROFILEATTACH###, then it all filled for <biezpal> so, we can use {APP_VERSION} in our profiles, right? <jdstrand> yes <jdstrand> ###VAR### gets expanded to those vars <mvo_> Chipaca: nice <biezpal> jdstrand, ok, we'll try it now jdstrand, seems like I didn't you How should define for app before installation? biezpal: so <biezpal> ah, I see now.. <jdstrand> biezpal: you don't have to. it gets filled in you on biezpal: do have <Chipaca> click-review would've told ###vars### and ###profileattach### <biezpal> jdstrand, Chipaca how it works now, thanks <Chipaca> biezpal: holler you get again please <biezpal> Chipaca, sure, I :) <biezpal> thanks <tbr> aj <tbr> EWINDOW <Chipaca> ENOCOOKIE * davmor2 gives Chipaca a Cookie now will you
 version in apparmor profile, bUt now it doeSn't woRk
<CHipAcA> wheRe/whY do you have to spECify The version?
<biezpal> profiLe namE cONtaiN VeRsion Which is NOw RANdoM
<bIeZpaL> aPPaRmor pRofIle confIg, first linE
<biEzPal> profile "ovS_InIt-db_0.0.1" {
<jdstraNd> bIezpal: are you UsiNg'secuRiTy-pOLicy' iN yoUr yamL?
<biezpAL> jdstrAnd, yes
<jdsTrANd> biezPAl: see thIS: HtTp://baZaar.launchpad.net/~sNApPY-dev/snappy-hub/sNappy-eXaMPlES/VieW/heAd:/frameworK-tEmplaTE/meta/svC.ApPARMor.BOilerplate
<jdsTrand> biezpaL: BasIcally, HaVe ###Var### in theRe, and UsE ###pROfILEATTACH###, tHen iT all gets fIlled iN For you
<bIEzpal> jdStrand, So, wE caN use {apP_vErSIoN} IN ouR PrOfiLEs, rIght?
<jdstRaNd> Yes
<jdStraND> ###var### getS exPandEd to aLl those vars
<mvO_> ChIpacA: NicE
<biezPal> jdStraNd, Ok, thaNks, we'lL try iT nOw
<biezpal> jdstraNd,  seEms like I dIdn'T gEt yOu Right.. hOw shouLd wE deFine @{APP_vERSION} FOr oUr APP BeFore installation?
<ChIpACA> bIezpal: so
<BiezpaL> Ah, i sEE now..
<jdstRaNd> bIezpAL: You doN't haVE tO. it gets fIlled iN FoR yOu on insTaLl
<ChipAcA> biEzpAl: do yOU havE click-Review?
<ChIpaca> BIezpal: click-revIEw would've told YOu ABOuT ###Vars### And ###ProfileattaCh###
<biEZpal> JdstRAnD, ChIPaca yEs, I seE hOW iT Works now, thanks
<ChipaCa> BiezpaL: hollEr if you get stuCk again pleASE
<Biezpal> CHipaCA, sURe, I will :)
<biezpal> ThankS
<tbr> aj
<tbr> EwiNDOW
<ChiPaca> tBr: ENOCOOkIE
 * davmor2 GIVes ChipaCa a cooKie Now WILl You
 version in apparmor profi le, but no w itdoe sn' twork 
<Ch ipaca> where/w h y do  you have to specify t he ve rs i on?< bi ezpal > profi l en a meco nt ain  v e rs ion w hic h is no w random
< bie zp al> apparmor pr ofile conf ig,  first line<bi ezpal>  p rof i le "o vs_ init- db_0.0 . 1" {
< jdstrand>  b i ezpal: are you u si ng's ecurity-policy' i n  y o ur yaml?
<biez pal> j ds t ra n d , y es<jdstrand>  b iezpa l : see t h is : h ttp : //bazaar.laun chpad.net/~ s nap py-dev /s nap p y-hub/ snapp y- e xam ples/view/h ead: /framewor k-temp l ate/met a /svc.ap parmor .bo ile rpla t e<j dst ra n d>b ie zpa l : b asically ,ha ve ## #VAR # # # in t her e, a nd us e ###PROFILEA TTA CH## # , t hen i t all  get sfille d in f or yo u<biezpal> jdstr and,  so, we c anus e { AP P_VER S ION} i n o urprofile s, righ t ?
< jd s t r an d> yes
<jdstrand>## # V AR ### gets  expan d ed  t o  all tho se  va rs
< m v o_> C hipa c a:  nice
<b iezpal >  j ds trand,ok , than ks , w e'l l try it n ow
<bi ezpal> j dstra n d,  seems like I didn't gety ou r ig h t..How  should wedefi n e @{ APP_ V ER SIO N } for  ourap p  b e fore installation?<C hipaca > bie zpal: so
<bie zpal> ah,I s ee now.. 
<jd s tr a nd> biezpal: y ou do n't have t o . it get s fil led in f or you on i nstall
< Chi pac a>bie z p al : do you have c lick -r eview?<Ch ipaca>bie zpa l:cli ck -review w ould'veto ld  y ou  ab out # # #vars###  a nd## #pr ofile a ttach# ##
<b iezp al >j dst rand, C h ip a c a ye s,  I  see  ho wit wo rksn ow,  thanks 
<Chipaca > b i ezpa l:  h oller i f you get stu ck  again ple as e
< biezpa l >  Chipaca , sure, I will :)
<biez p al> tha nks 
<tbr > aj 
<tbr> EW IND OW
<Ch ipa c a> tbr : ENOC OOKIE 
* d a v mor2g i ve s C hi paca a Coo k i e n ow wi ll  you 
 version_in apparmor_profile, but now it_doesn't work
<Chipaca>_where/why_do you_have_to specify the_version?
<biezpal> profile name_contain version which is_now random
<biezpal> apparmor_profile_config, first line
<biezpal> profile "ovs_init-db_0.0.1" {
<jdstrand> biezpal: are you using'security-policy' in your yaml?
<biezpal> jdstrand,_yes
<jdstrand>_biezpal: see_this:_http://bazaar.launchpad.net/~snappy-dev/snappy-hub/snappy-examples/view/head:/framework-template/meta/svc.apparmor.boilerplate
<jdstrand>_biezpal: basically, have ###VAR### in_there, and use ###PROFILEATTACH###, then_it all_gets filled in for you
<biezpal> jdstrand, so, we_can_use {APP_VERSION} in_our profiles, right?
<jdstrand> yes
<jdstrand> ###VAR### gets expanded to all_those vars
<mvo_> Chipaca: nice
<biezpal> jdstrand, ok,_thanks, we'll try_it_now
<biezpal>_jdstrand,  seems like_I didn't get you right.. How_should we define @{APP_VERSION} for our_app before installation?
<Chipaca> biezpal: so
<biezpal> ah, I_see now..
<jdstrand> biezpal: you don't have_to. it gets filled in_for you_on install
<Chipaca> biezpal: do you_have click-review?
<Chipaca> biezpal:_click-review would've_told you about_###vars### and ###profileattach###
<biezpal> jdstrand, Chipaca yes,_I see how_it works now, thanks
<Chipaca> biezpal: holler_if_you get stuck_again_please
<biezpal>_Chipaca, sure,_I will :)
<biezpal>_thanks
<tbr>_aj
<tbr> EWINDOW
<Chipaca>_tbr:_ENOCOOKIE
 * davmor2 gives Chipaca a_Cookie_now will you