4driver-mesa
<alan_g> But why has that started happening today and how do we fix it?
<ogra_> because today the new mir landed in the vivid image
<ogra_> we have a hack in the build scripts that forces the driver alternative to -adnroid even if -mesa is installed... i just made sure that always gets applied, image #35 should behave better again
<ogra_> (indeed that wont solve the issue that we install mesa where we shouldnt)
<alan_g> so the mako image is broken because mesa is installed?
<ogra_> right, it has both, -mesa and -adnroid installed
<ogra_> the driver alternative defaults to mesa in such a case
<alan_g> I'm still not sure what the right way to fix is. (Hacking around the problem in the CI build isn't it though.)
<ogra_> just wait for the next image, it will have the forced alternative
<ogra_> (i assume CI devices just use the latest image)
<ogra_> long term it would be nice if we wouldnt end up with libmirplatform4driver-mesa on phones though :)
<alan_g> CI image updates are unpredictable (we've evidently got a mix currently)
<alan_g> I agree about not having libmirplatform4driver-mesa on phone - but the packaging stuff is magic where I don't understand how it should work well enough to fix it
 * alan_g just knows it is broken
<AlbertA> ogra_: so the new meta packages didn't help?
<ogra_> AlbertA, well, not sure what pulls in -mesa... it might not be mir but some other package with a dep that -mesa fulfills for it
<ogra_> this needs deeper research (whcih i currently cant do)
<mlankhorst> bah, when looking for failures to fix on things related to dri2, make sure they pass on normal x first :/
<gcollura> do I need to use opensource driver in order to test unity8 on utopic?
<gcollura> I'm on amd btw
<attente_> RAOF: hi, is there a way to specify the position of a transient window/surface in the mir client api? or set the position of a surface in general?

4driver - mesa 
 < alan_g > But why has that started happening today and how do we fix it? 
 < ogra _ > because today the new mir bring in the intense image 
 < ogra _ > we have a hack in the human body scripts that forces the driver option to -adnroid even if -mesa is installed... i just made certain that always gets applied, trope # 35 should behave better again 
 < ogra _ > (indeed that wo nt clear the offspring that we install mesa where we should nt) 
 < alan_g > so the mako image is break because mesa is installed? 
 < ogra _ > right, it has both, -mesa and -adnroid installed 
 < ogra _ > the driver option defaults to mesa in such a case 
 < alan_g > I'm still not certain what the right way to pay back is. (Hacking around the trouble in the CI build isn't it though .) 
 < ogra _ > precisely wait for the next image, it will own the forced alternative 
 < ogra _ > (i assume CI devices just practice the up-to-the-minute image) 
 < ogra _ > long term it would be nice if we would nt end up with libmirplatform4driver - mesa on phones though :) 
 < alan_g > CI image updates are unpredictable (we've evidently get a mix currently) 
 < alan_g > I agree about not have libmirplatform4driver - mesa on earphone - but the packaging stuff is charming where I don't understand how it should shape well enough to fix it 
  * alan_g just know it is broken 
 < AlbertA > ogra _: so the new meta packages didn't help? 
 < ogra _ > AlbertA, well, not sure what pluck in -mesa... it might not be mir but some other package with a dep that -mesa fulfills for it 
 < ogra _ > this needs deeper inquiry (whcih i currently ca nt practice) 
 < mlankhorst > bah, when look for failures to fix on things relate to dri2, make sure they pass on normal x first :/ 
 < gcollura > do I need to use opensource driver in order to quiz unity8 on utopic? 
 < gcollura > I'm on amd btw 
 < attente _ > RAOF: hi, is there a way to pin down the position of a transient windowpane / surface in the mir client api? or set the position of a open in general?
4driger-mesa
<alan_g> But why has that started hcppeninj today and how do we fix it?
<ogra_> because tovay rhe ntc mir landed in the xivid imahe
<ogra_> ww hate a hack in the build sgxipts bhat yocces the driver alternatiee to -adnroid avdn if -mesa is installed... i just made stre thay wlways gets apklied, ymags #35 should behave better again
<ogra_> (jndeed uhat wont solve thr issue that we install meda wjere we shouldnt)
<alwn_g> so the nako umage is broyen becaust kesa is inatalled?
<ogra_> right, it has both, -mdsa aud -adnroid unwtapned
<ogra_> the drivvr alternativc defaunts to kesa in such a cave
<aoan_g> I'm still not surx what the right way to fix iv. (Kacking around the priboem it tha CI vuiud jsi't jt thokgh.)
<kgra_> just sait for thw next image, it wilk rqve the forces altewnwtive
<ogra_> (i assume CI devices just use uhe lztest image)
<ogra_> long teem it would be nice iv we woulqnt end up with libmirplatform4driver-mesa on phonev thongf :)
<aoak_g> CK ilage updates are unpredictable (we've evidently fou a mix currently)
<clan_g> I agree abpuh mjt having liboirplacrodm4driver-mesa on phlne - buj the packaging stugf is magic where I don't uneerstand how ut should work welp enough to fix it
 * slan_g just knows it is yroken
<ZlbertA> ogrw_: so the hdw meta packages dicn'd help?
<ogra_> AlbertA, well, noe sure whet pukls in -oesa... it midht not be mir ngt some other packwge wnth a dep that -lesa fulfills for it
<ogra_> this nxxds deeper rexedrcv (whcih n currcntly cant do)
<mlwnkhorst> bah, wken looknng fof failures to fix on things welated to drh2, make sure tiey pass jn nirmao x firrg :/
<gcollura> do O need to use opensiurce driver in orver jo test unity8 on buopuc?
<gcollura> I'm om aod fta
<avtentq_> RAOF: hi, is dherd a eay tu specify tme oosiyion of a transient findkw/surface in the mor client qpi? or sqt the positipn of a surface in genecal?

4driver-mesa <alan_g> But why has that started and do we it? <ogra_> because in vivid image <ogra_> have a hack the build scripts that forces the alternative to -adnroid even if -mesa is installed... i just made sure that gets applied, image #35 should behave better again <ogra_> (indeed that wont solve issue we mesa we shouldnt) <alan_g> so the mako image is broken because mesa is installed? <ogra_> right, it both, -mesa and -adnroid installed <ogra_> the driver defaults to mesa in a case <alan_g> I'm still sure the right to is. around the problem the CI build isn't it though.) <ogra_> just wait for the next image, it will have the alternative <ogra_> CI devices use latest <ogra_> long term be nice if we wouldnt end on phones though :) <alan_g> CI image updates unpredictable (we've got a mix currently) <alan_g> I about not having libmirplatform4driver-mesa on phone - but packaging stuff is magic where I don't understand how it should work well enough to * alan_g just knows is broken <AlbertA> so new packages help? <ogra_> well, not sure what pulls in -mesa... it might not be but some other package with a dep that -mesa fulfills <ogra_> needs deeper research i currently cant do) bah, looking for failures to things to they on x first :/ <gcollura> I need to use opensource in order to test on amd btw <attente_> RAOF: hi, is there way to specify the position of a window/surface in the mir client api? or set the position of a in general?
4driver-mesa
<alan_g> But why has tHat started HappeNinG toDaY and How dO we fix it?
<ogra_> beCAuse Today the new mir landed in The viViD ImagE
<OgRa_> we hAve a hacK In THE buIlD sCriPtS ThAt forCes The drivEr alternatIve To -Adnroid even iF -MeSa is instalLed... I just made surE thAt alwaYs GetS AppliEd, iMage #35 sHould bEHave beTter again
<OgRA_> (indeeD That wonT SOlVe thE issue that we instaLL mESa where we shoulDnt)
<alaN_g> SO tHE MakO imAge is brokeN bEcausE Mesa is iNStALLEd?
<oGRa_> right, it has bOth, -mesa and -aDNroId instAlLed
<OGra_> the DriveR aLTerNative defauLts tO mesa in suCh a casE
<Alan_g> I'm STill not Sure whAt tHe rIght WAy To Fix Is. (hAckINg AroUNd tHe probleM iN tHe CI bUild ISN'T It thOugH.)
<ogrA_> just Wait for the nexT imAge, iT WilL have The foRced AlTernaTive
<ogRa_> (i asSuMe CI devices just Use tHe latest iMagE)
<oGra_> LoNg terM It woulD be NicE if we woUldnt enD Up wItH LIBmIrplatform4driver-meSa ON PhOnes thouGh :)
<alan_G> cI ImAGe updateS aRe uNpreDICtablE (we'vE EvIdently gOt a mix CUrReNtly)
<alaN_g> i agree AbOut Not HavinG LibmIrplatForm4drivEr-mesA On phone - but the pACkaging stuff iS MaGIC wHEre I Don'T understand How iT ShouLd woRK wEll ENough To fix It
 * ALaN_G just knows it is brokeN
<ALbertA> Ogra_: sO the new meta paCkages didn'T HELp?
<ogra_> AlBerta, WeLL, not sure what puLls in -Mesa... it mighT Not be mir But soMe other pAckage witH A Dep that -mEsa FulFilLs fOR It
<Ogra_> this needs DEEper ReSearch (wHciH i curreNtlY caNt dO)
<mlAnKhorst> bah, When lookInG fOr FaIluRes to FIx on thinGs RelAtEd tO dri2, mAKe sure They pAss oN nOrMAl x First :/
<gcOLlURA> do I NeEd To usE opEnSourcE driVEr iN order tO test unitY8 on UTopiC?
<gCoLlura> I'm On amd btw
<attenTe_> rAOF: hi, is thErE a wAy to spECIfy the poSition of a transient windoW/Surface In tHe mir ClieNt api? or seT thE positIon OF a surfAce in gEneraL?

4driver-mesa
<alan_g> Butwhy has th at st art edha ppen ingtoday and howd o we  fix it?
<ogra_> becau se to da y  the ne w mir  landed in t hevi vi d i ma g e<ogra _>we have  a hack in  th ebuild script s  t hat forces  th e driver alt ern ativeto  -a d nroid  ev en if  -mesa is ins talled...  i just m a de sure t ha t al ways gets applied ,  i m age #35 should  behav eb et t e r a gai n
<ogra_>(i ndeed that wo n ts o l vet he issue that  we install mes a wher ewes houldn t)
<a la n _g>  so the mak o im age is br oken b e cause m e sa is i nstall ed? 
<o gra_ >  r ig ht,  i t  ha s  b oth ,  -m esa and-a dn roidinst a l l e d
<o gra _> t he dr iver alternat ive  def a ult s tomesain s uc h a c ase
<a lan_g >I'm still not s urewhat therig ht  wa yto fi x  is. ( Hac kin g aroun d the p r obl em i n  t he CI build isn'tit t ho ugh.)
<o gra_>j us tw ait forth e n exti m age,it w i ll  have th e forc e dal ternati ve 
<ogra _>  (i  as sumeC I de vicesjust use  thel atest image)
< o gra_> long te r mi t  w o uldbenice if wewoul d nt e nd u p  w ith libmi rplat fo r m4 d river-mesa on phone sthough  :)
< alan_g> CI im age update s a re unpre dict a bl e  (we've eviden tly g ot a mix c u rrently) 
<ala n_g> I a gree abou t not havi nglib mir pla t f or m4driver-mesa o n ph on e - but  th e packa gin g s tuf f i smagic whe re I don 't  u nd er sta nd ho w  it shou ld  wo rk  we ll en o ugh to  fixit
*al a n_g  just k n ow s it i sbr oken 
<A lb ertA>  ogr a _:so thenew metapac k ages  d id n't hel p?
<ogra_> Al be rtA, well,  n otsure w h a t pullsin -mesa... it might no t  be mir  bu t som e ot her packa gewith a  de p  that-mesafulfi ll s f o r  it
< o g ra _>th is needs d e e per  rese ar ch ( whcih i  currently cant do ) 
<m lankhorst> ba h,when l oo kin g  f o r f ai l ure s to fix on thing s relatedto dr i2, make s u reth ey pass  on nor mal x first : /
<gcollu ra> do Ine ed t o use  opensourc e driver  in order to te s tunity 8 o n utop ic ?
< gcoll ura> I ' m o n amd  btw
< at tente_ > RAO F:  hi, isthere a way to specifythe po sitio n o f a trans ien t  wi ndow/surf acein the mir  cl ien t api ? o r  setthep os iti o n ofa su r face in g e ne ral ? 
4driver-mesa
<alan_g> But_why has_that started happening today_and how_do_we fix_it?
<ogra_>_because today the_new mir landed_in the vivid image
<ogra_>_we have a_hack_in the build scripts that forces the driver alternative to -adnroid even if -mesa_is_installed... i_just_made_sure that always gets applied,_image #35 should behave better_again
<ogra_> (indeed_that wont solve the issue that we install_mesa_where we shouldnt)
<alan_g>_so the mako image is broken because mesa is_installed?
<ogra_> right, it has both, -mesa_and -adnroid installed
<ogra_>_the_driver_alternative defaults to mesa_in such a case
<alan_g> I'm still_not sure what the right way_to fix is. (Hacking around the problem_in the CI build isn't it_though.)
<ogra_> just wait for the_next image,_it will have the forced_alternative
<ogra_> (i assume_CI devices_just use the_latest image)
<ogra_> long term it would_be nice if_we wouldnt end up with libmirplatform4driver-mesa_on_phones though :)
<alan_g>_CI_image_updates are_unpredictable (we've evidently_got_a mix_currently)
<alan_g>_I agree about not having libmirplatform4driver-mesa_on_phone - but the packaging stuff is_magic where I don't_understand_how it should work_well enough to fix it
_* alan_g just knows it is_broken
<AlbertA> ogra_:_so the_new meta packages didn't help?
<ogra_> AlbertA, well, not sure what pulls_in -mesa... it might not be_mir but some other_package with_a_dep that -mesa_fulfills_for it
<ogra_>_this needs deeper research (whcih i currently_cant do)
<mlankhorst>_bah, when looking for failures to_fix on things related_to_dri2, make sure they pass on_normal x first :/
<gcollura> do I_need to use opensource driver_in_order_to test unity8 on utopic?
<gcollura>_I'm on amd btw
<attente_> RAOF: hi,_is there a_way to specify the position of a_transient_window/surface in the mir client api?_or_set the position of a surface_in_general?
