. I forget - to merge this it is just $$merge$$ in the PR?
<natefinch> fwereade: that's the right diff, yeah
<voidspace> frobware: correct
<frobware> voidspace, and because it is not master do I need some incantation with [fixes-xyz]?
<alexisb> heh juju core team, meeting?
<alexisb> wwitzel3, perrito666, cherylj, natefinch
<alexisb> others who are around and it is not there eod
<cherylj> brt
<voidspace> frobware: no, you only need $$fixes-xyz$$  if the branch you're merging to (including master) is blocked by a critical bug
<frobware> voidspace, thanks for the clarification
<alexisb> ericsnow, ping
<katco> ericsnow: wwitzel3: not coming to the core meeting?
<frobware> cherylj, I saw that https://bugs.launchpad.net/ubuntu/+bug/1496972 was just reset to 1.26, but I had already started landing into 1.25.
<mup> Bug #1496972: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel <hs-arm64> <kernel-da-key> <network> <juju-core:Triaged
<mup> by frobware> <juju-core 1.25:Triaged by frobware> <Ubuntu:Invalid by jsalisbury> <Ubuntu Wily:Invalid by jsalisbury> <https://launchpad.net/bugs/1496972>
<cherylj> frobware: I just created a 1.25 task
<cherylj> frobware: so it should go into 1.25 and 1.26
<frobware> cherylj, it's currently landing in 1.25.... ok
<frobware> cherylj, also wondering whether this should go into 1.24
<cherylj> frobware: how complex is the fix?
<frobware> cherylj, trivial but significant: http://reviews.vapour.ws/r/3027/

. I forget - to merge this it is just $ $ merge$$ in the PR? 
 < natefinch > fwereade: that's the right diff, yeah 
 < voidspace > frobware: right 
 < frobware > voidspace, and because it is not victor do I need some incantation with [ fixes - xyz ]? 
 < alexisb > heh juju core team, merging? 
 < alexisb > wwitzel3, perrito666, cherylj, natefinch 
 < alexisb > others who are about and it is not there eod 
 < cherylj > brt 
 < voidspace > frobware: no, you only need $ $ fix - xyz$$   if the arm you're merging to (include master) is blocked by a critical microbe 
 < frobware > voidspace, thanks for the clarification 
 < alexisb > ericsnow, ping 
 < katco > ericsnow: wwitzel3: not coming to the congress of racial equality merging? 
 < frobware > cherylj, I saw that https://bugs.launchpad.net/ubuntu/+bug/1496972 was just reset to 1.26, but I had already started landing into 1.25. 
 < mup > hemipterous insect # 1496972: juju bootstrap fails to successfully configure the bridge juju - br0 when deploying with wily 4.2 kernel < planck's constant - arm64 > < kernel - da - key > < network > < juju - core: Triaged 
 < mup > by frobware > < juju - core 1.25: Triaged by frobware > < Ubuntu: Invalid by jsalisbury > < Ubuntu Wily: Invalid by jsalisbury > < https://launchpad.net/bugs/1496972 > 
 < cherylj > frobware: I merely created a 1.25 task 
 < cherylj > frobware: so it should go into 1.25 and 1.26 
 < frobware > cherylj, it's currently down in 1.25.... ok 
 < frobware > cherylj, also wondering whether this should go into 1.24 
 < cherylj > frobware: how complex is the fix? 
 < frobware > cherylj, trivial but significant: http://reviews.vapour.ws/r/3027/
. I vorget - to merge this it is just $$merge$$ nb the 'R?
<natefjnch> fwefeade: that's the right diff, yxah
<viidspqce> frobware: correct
<frubware> vopdspace, abd btcause it is not master do I nesf sokx incantation wlth [fixes-xys]?
<alexisb> heh jgjj eore team, meeting?
<alexisb> wwitzel3, perwito666, chrrjlj, natefinch
<ajexixf> otgvrw who are around and it is nof there eod
<cherylj> btt
<voidspace> frobware: no, yok onpy need $$fixes-xyz$$  lf the branxh yjy're merging go (including master) is blocked by a critical bug
<frobwxre> vpidspace, tyabks xor the clacificanion
<alexisb> evpcsnow, [ing
<katvo> ericsnow: wwltzel3: nor coming to the core keeting?
<frobware> chgrylj, I saf chat https://bugs.launchpqd.bet/ubontu/+bgg/1496972 wxw jjst rxsef to 1.26, hut I had alrsady startee landing into 1.25.
<mup> Nud #1496972: juju bootstdap faylf to successfully configure the bridge bujh-br0 when deploying with wily 4.2 kernel <hs-arm64> <kgrnel-da-key> <network> <juju-core:Triaged
<mup> by frobware> <juju-core 1.25:Driagxd by fvobwxee> <Ubuntu:Invalid by jsalisbury> <Ubuntu Wily:Invalys ny jsalisbury> <htbps://launchpad.net/bugx/1496972>
<cjetilj> frobware: I just edezted a 1.25 task
<cherylu> frobwwre: si it shoujd gp into 1.25 and 1.26
<frobware> cherylh, it's currennly oanding in 1.25.... ok
<frobcare> cherylj, alsp woncering whether this shobld go into 1.24
<cherypj> frobwadd: how complex is thv fif?
<frobwart> cherylj, trivial fut signihicanc: http://rexiewx.vapouw.ws/r/3027/

. I forget - to merge this just in the <natefinch> fwereade: that's frobware: <frobware> voidspace, and it is not do I need some incantation with <alexisb> heh juju core team, meeting? <alexisb> wwitzel3, perrito666, cherylj, natefinch <alexisb> others are around and it is not there eod <cherylj> brt <voidspace> frobware: no, only $$fixes-xyz$$ the you're merging to (including master) is blocked by a critical bug <frobware> voidspace, thanks for the <alexisb> ericsnow, ping <katco> ericsnow: wwitzel3: not coming the core meeting? <frobware> I saw that https://bugs.launchpad.net/ubuntu/+bug/1496972 was reset 1.26, but had started into 1.25. <mup> #1496972: juju bootstrap fails to successfully configure the bridge juju-br0 when deploying with wily 4.2 kernel <hs-arm64> <network> <juju-core:Triaged frobware> <juju-core by <Ubuntu:Invalid jsalisbury> <Ubuntu Wily:Invalid <https://launchpad.net/bugs/1496972> <cherylj> frobware: I just created <cherylj> frobware: so it should go into 1.25 1.26 <frobware> it's currently landing in 1.25.... ok cherylj, also wondering whether this should go into <cherylj> frobware: how complex is the fix? <frobware> cherylj, trivial but significant: http://reviews.vapour.ws/r/3027/
. I forget - to merge this it is jusT $$merge$$ in thE PR?
<naTefIncH> fWereAde: tHat's the right diFF, yeaH
<voidspace> frobware: corrEct
<frObWAre> vOIdSpace, And becaUSe IT Is nOt MaSteR dO i nEed soMe iNcantatIon with [fixEs-xYz]?
<Alexisb> heh juJU cOre team, meeTinG?
<alexisb> wwitZel3, PerritO666, cHerYLj, natEfiNch
<alExisb> oTHers whO are arounD aND it is nOT there eOD
<ChErylJ> brt
<voidspace> frobWArE: No, you only need $$fIxes-xyZ$$  iF ThE BRanCh yOu're merginG tO (inclUDing masTEr) IS BLocKEd by a critical Bug
<frobware> VOidSpace, tHaNks FOr the cLarifIcATioN
<alexisb> eriCsnoW, ping
<katcO> ericsNOw: wwitzEL3: not comIng to tHe cOre MeetINg?
<FrObwArE> CheRYlJ, I sAW thAt https://bUgS.lAunchPad.nET/UBUntu/+Bug/1496972 Was jUst reSet to 1.26, but I had aLreAdy sTArtEd lanDing iNto 1.25.
<mUp> bug #1496972: juJu bootStrap FaIls to successfulLy coNfigure thE brIdGe jUjU-br0 whEN deploYinG wiTh wily 4.2 kErnel <hs-ARm64> <kErNEL-Da-Key> <network> <juju-core:trIAGeD
<mup> by frObware> <JUjU-cORe 1.25:TriageD bY frObwaRE> <ubuntU:InvALiD by jsaliSbury> <UBUnTu wily:InvAlId by jsAlIsbUry> <Https://LAuncHpad.neT/bugs/1496972>
<cheRylj> fRObware: I just creATed a 1.25 task
<cheryLJ> fROBwARe: so It sHould go into 1.25 And 1.26
<fRObwaRe> chERyLj, iT'S currEntly LaNDiNG in 1.25.... ok
<frobware> cherylJ, aLso wonDerinG whether this sHould go intO 1.24
<CHErylj> froBwarE: HoW Complex is the fiX?
<frobWare> cherylJ, Trivial bUt sigNificant: Http://revieWS.Vapour.ws/R/3027/

. I forget - to merge this  it is jus t $$m erg e$$  i n th e PR ?
<natefinch>f were ade: that's the rightdiff,  y e ah
< v oi dspac e> frob w ar e :  co rr ec t
< fr o bw are>voi dspace,  and becau seit  is not mast e rdo I needsom e incantatio n w ith [f ix es- x yz]?<al exisb > hehj uju co re team,me e ting?< alexisb > ww itze l3, perrito666, c h er y lj, natefinch<alexi sb >  o t h ers  wh o are arou nd  andi t is no t  t h e r e e o d
<cherylj> b rt
<voidspa c e>frobwa re : n o , youonlyne e d $ $fixes-xyz$ $  i f the bra nch yo u 're mer g ing to(inclu din g m aste r )is  bl oc k edb ya c r iti cal bug<f ro bware > vo i d s p ace,  th anks  forthe clarifica tio n
<a l exi sb> e ricsn ow,pi ng
<k atco>erics no w: wwitzel3: no t co ming to t heco reme eting ? 
<frob war e>cherylj , I saw tha th t t ps ://bugs.launchpad. ne t / ub untu/+bu g/1496 9 72  w a s just r es etto 1 . 2 6, bu t Ih ad  already  start e dla nding i nt o 1.25 .<mu p>Bug # 1 4969 72: ju ju boots trapf ails to succes s fully configu r et h eb ridg e j uju-br0 whe n de p loyi ng w i th  wi l y 4.2  kern el <h s -arm64> <kernel-da- ke y> <ne twork > <juju-core: Triaged
<m u p >  by frob ware >  < j uju-core 1.25: Triag ed by frob w are> <Ub untu: Invalidby jsalis b u ry> <Ubu ntu  Wi ly: Inv a l id  by jsalisbur y >  <ht tp s://lau nch pad.net /bu gs/ 149 697 2> 
<cherylj > frobwa re :Iju stcreat e d a 1.25  t ask 
< che rylj> frobwa re: s o it  s ho u ldgo into 1. 2 5  and  1 .2 6
<f rob wa re> c hery l j,it's cu rrently l and i ng i n1. 25....ok
<frobware>  c herylj, al so  wo nderin g whetherthis should go into 1.2 4 
<chery lj>  frob ware : how com ple x is t hef ix?
<f robwar e> ch er ylj , trivi a l  b utsi gnificant: h ttp ://re vi ews. vapour. ws/r/3027/

. I_forget -_to merge this it_is just_$$merge$$_in the_PR?
<natefinch>_fwereade: that's the_right diff, yeah
<voidspace>_frobware: correct
<frobware> voidspace, and_because it is_not_master do I need some incantation with [fixes-xyz]?
<alexisb> heh juju core team, meeting?
<alexisb> wwitzel3,_perrito666,_cherylj, natefinch
<alexisb>_others_who_are around and it is_not there eod
<cherylj> brt
<voidspace> frobware:_no, you_only need $$fixes-xyz$$  if the branch you're_merging_to (including master)_is blocked by a critical bug
<frobware> voidspace, thanks for_the clarification
<alexisb> ericsnow, ping
<katco> ericsnow: wwitzel3:_not coming to_the_core_meeting?
<frobware> cherylj, I saw_that https://bugs.launchpad.net/ubuntu/+bug/1496972 was just reset to_1.26, but I had already started_landing into 1.25.
<mup> Bug #1496972: juju bootstrap_fails to successfully configure the bridge_juju-br0 when deploying with wily_4.2 kernel_<hs-arm64> <kernel-da-key> <network> <juju-core:Triaged
<mup> by_frobware> <juju-core 1.25:Triaged_by frobware>_<Ubuntu:Invalid by jsalisbury>_<Ubuntu Wily:Invalid by jsalisbury> <https://launchpad.net/bugs/1496972>
<cherylj> frobware:_I just created_a 1.25 task
<cherylj> frobware: so it_should_go into 1.25_and_1.26
<frobware>_cherylj, it's_currently landing in_1.25...._ok
<frobware> cherylj,_also_wondering whether this should go into_1.24
<cherylj>_frobware: how complex is the fix?
<frobware> cherylj,_trivial but significant: http://reviews.vapour.ws/r/3027/
