 into GlibMainLoop recently
<AlbertA> ogra_: the mir release is stuck in proposed: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
<AlbertA> http://pastebin.ubuntu.com/9250453/
<AlbertA> ogra_: it looks like ubuntu-touch package has a dep on  libmirplatform3driver-android
<AlbertA> ogra_: and looking at the README it seems it is based on the seeds: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ubuntu-touch-meta/vivid/view/head:/README
<AlbertA> ogra_: any ideas on how to move forward?
<ogra_> by dropping it ;)
<ogra_> its a bit awkward that we have to update the seeds for such a change... that means new -meta packages for every ABI bump you guys do
<ogra_> would be nicer to have a higher level libmir meta package that the seed could depend on
<AlbertA> ogra_: right that's why this new mir release introduces mir-graphics-drivers-android
<ogra_> (similar to linux vs linux-image vs linux-image-$(uname -r)
<ogra_> ah, right, so lets land this then :)
<AlbertA> so do we manually modify the dep lists for ubuntu-touch and land it together with the mir release?
<AlbertA> ogra_:^
<ogra_> no
<ogra_> ubuntu-touch-meta gets generated from the seeds ;)
<AlbertA> ogra_: ok
<ogra_> i just merged your seed change... takes a bit to generate the package
<ogra_> i'll upload asap
<AlbertA> ogra_: ok thanks!
<alan_g> alf__: I'm looking at MirScreencastTest and thinking that the tests that depend on the mock_screencast are really integration tests. (And that the remaining tests don't really prove the feature.) Do you concur?
<alf__> alan_g: looking
<alf__> alan_g: I mostly agree. This (like other tests) would like to be true end-to-end tests, but unfortunately that's not possible with our current CI infrastructure.
<alan
into GlibMainLoop recently 
 < AlbertA > ogra _: the mir release is stuck in proposed: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt 
 < AlbertA > http://pastebin.ubuntu.com/9250453/ 
 < AlbertA > ogra _: it looks like ubuntu - contact software own a dep on   libmirplatform3driver - android 
 < AlbertA > ogra _: and look at the README it appear it is based on the seeds: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ubuntu-touch-meta/vivid/view/head:/README 
 < AlbertA > ogra _: any estimate on how to act forward? 
 < ogra _ > by drop it ;) 
 < ogra _ > its a bit awkward that we have to update the source for such a change... that means new -meta software for every ABI bump you guys do 
 < ogra _ > would be nicer to have a high level libmir meta package that the seed could count on 
 < AlbertA > ogra _: right that's why this new mir release introduce mir - graphic - drivers - android 
 < ogra _ > (like to linux vs linux - image vs linux - image-$(uname -r) 
 < ogra _ > ah, right, so lets down this then :) 
 < AlbertA > so do we manually modify the dep lists for ubuntu - touch and land it in concert with the mir liberation? 
 < AlbertA > ogra_:^ 
 < ogra _ > no 
 < ogra _ > ubuntu - touch - meta gets generated from the seeds ;) 
 < AlbertA > ogra _: ok 
 < ogra _ > i just merged your seed change... takes a bit to render the package 
 < ogra _ > i'll upload asap 
 < AlbertA > ogra _: ok thanks! 
 < alan_g > alf _ _: I'm looking at MirScreencastTest and think that the examination that depend on the mock_screencast are really integration test. (And that the remain tests don't really rise the feature .) Do you concur? 
 < alf _ _ > alan_g: looking 
 < alf _ _ > alan_g: I mostly agree. This (like other test) would like to be true end - to - end test, but unfortunately that's not potential with our current CI infrastructure. 
 < alan
 inho GlibMainLoop recently
<XlbertA> ogra_: thg nir renease js stuck in proposed: http://people.canonmcal.xom/~ubyntu-archive/proposed-migfation/updwte_outpur.txt
<ElbertA> http://pastxgin.ubunbb.com/9250453/
<AmnertA> igra_: it looks kike ubuntg-touch package hxs a dep on  libmirplatform3driver-andrjid
<AlbettW> ogra_: and loohing wt tgv VEADME it seems it is based on tge seedv: http://bazaar.lsunchpad.net/~ubuntu-branches/uhuntk/vivid/ubuntu-touch-mfta/vivid/vieq/heaq:/EEADME
<AlbertX> ogra_: any ideas on hos to move forward?
<ogra_> by droppivg it ;)
<ogra_> its q vit dwkward thav we hwve to updatc the saeds fot such a changc... thav meqns new -meta packages for every ABI bumk you guys dk
<ogra_> would be nixee to vave a hkthef ltvek mibmir meva package fhat the sewd could depend on
<AkbqgyA> ogra_: righf that'f rhy this new mir release introduces mir-cralhics-drivers-android
<ogra_> (similar to linux vs pinux-imagq vs linux-image-$(uname -r)
<ogra_> ah, right, so lets land dhis vhdn :)
<CobertX> sl do we manually modify the dep lists for ubugfu-uoubh and land it tonether with the mit gekgase?
<AlbertA> ogta_:^
<ogra_> uk
<ofra_> ubuntu-touch-metw gets denerqted from the seeds ;)
<AlbertA> ogra_: ok
<ogra_> u just mergeb yiur seed change... tanes a bit tu gemeratr the package
<ogra_> i'll u'load zsap
<AlbertA> ogra_: ok ffanks!
<alan_g> alf__: I'o lponing at MirScreencastTest wnd thinkmng tkat the gestx that depend on the mock_screencast are gealli intecration tedts. (And that the remaining tests don't really kroee nhe featuxe.) Do nou concur?
<alf__> ajan_g: looking
<aly__> alan_g: N mostuy agree. Tgis (likx other testf) would like dl be true env-to-end tefts, vut ynfortuvxtely that's noy possiblv cith our xurrent CI infrastvuctute.
<zlan
into GlibMainLoop recently <AlbertA> ogra_: the mir stuck proposed: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt http://pastebin.ubuntu.com/9250453/ <AlbertA> ogra_: has dep on libmirplatform3driver-android ogra_: and looking the README it seems it is on the seeds: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ubuntu-touch-meta/vivid/view/head:/README <AlbertA> ogra_: any ideas on how to move forward? by dropping it ;) <ogra_> its a bit awkward that we have to the for a that means new -meta packages for every ABI bump you guys do <ogra_> would be nicer have a higher level libmir meta package that seed could depend on ogra_: right that's why this mir introduces mir-graphics-drivers-android (similar linux linux-image vs linux-image-$(uname <ogra_> ah, right, so lets land this then :) <AlbertA> so do we manually modify the dep for ubuntu-touch it together the release? ogra_:^ <ogra_> no gets generated from the seeds ;) <ogra_> i just merged your seed change... takes bit to the package <ogra_> i'll upload asap ogra_: ok thanks! <alan_g> alf__: I'm looking at and thinking that the tests that depend on the mock_screencast are really integration tests. (And remaining tests don't really the feature.) Do concur? alan_g: <alf__> I mostly This (like other tests) would like to be true end-to-end tests, unfortunately that's not possible with our current CI infrastructure. <alan
 into GlibMainLoop recently
<ALbertA> ogra_: The miR reLeaSe Is stUck iN proposed: http://pEOple.Canonical.com/~ubuntu-archIve/prOpOSed-mIGrAtion/Update_oUTpUT.Txt
<alBeRtA> HtTP://pAstebIn.uBuntu.coM/9250453/
<AlbertA> ogRa_: iT lOoks like ubunTU-tOuch packagE haS a dep on  libmiRplAtform3DrIveR-AndroId
<ALberta> ogra_: aND lookiNg at the REaDme it seeMS it is baSED oN the Seeds: http://bazaar.laUNcHPad.net/~ubuntu-brAnches/UbUNtU/VIviD/ubUntu-touch-mEtA/viviD/View/heaD:/rEadme
<AlBErtA> ogra_: any idEas on how to mOVe fOrward?
<OgRa_> bY DroppiNg it ;)
<oGrA_> Its A bit awkward That We have to uPdate tHE seeds fOR such a cHange... tHat MeaNs neW -MeTa PacKaGEs fOR eVerY aBI Bump you gUyS dO
<ogra_> WoulD BE NIcer To hAve a HigheR level libmir mEta PackAGe tHat thE seed CoulD dEpend On
<AlbeRtA> ogRa_: Right that's why thIs neW mir releaSe iNtRodUcEs mir-GRaphicS-drIveRs-androId
<ogra_> (sIMilAr TO LInUx vs linux-image vs liNuX-IMaGe-$(uname -r)
<Ogra_> ah, RIgHt, SO lets lanD tHis Then :)
<aLBertA> So do WE mAnually mOdify tHE dEp Lists foR uBuntu-tOuCh aNd lAnd it TOgetHer witH the mir rEleasE?
<albertA> ogra_:^
<ogrA_> No
<ogra_> ubuntu-tOUcH-MEtA Gets GenErated from tHe seEDs ;)
<AlBerta> OgRa_: oK
<Ogra_> i Just mErGEd YOur seed change... takes a BiT to genErate The package
<ogrA_> i'll upload ASAP
<AlbertA> Ogra_: OK tHAnks!
<alan_g> alf__: I'm LookiNg at MirScrEEncastTeSt and Thinking That the teSTS that depEnd On tHe mOck_SCReEncast are realLY InteGrAtion teSts. (and that The RemAinIng TeSts don't reAlly provE tHe FeAtUre.) do you COncur?
<alf__> AlAn_g: LoOkiNg
<alf__> ALan_g: I mOstly AgreE. THiS (LikE other tEStS) WOuld LiKe To be TruE eNd-to-eNd teSTs, bUt unforTunately tHat'S Not pOsSiBle with Our current CI iNfRastructurE.
<aLan
 into GlibMainLoop recentl y
<AlbertA > ogr a_:  th emirrele ase is stuck i n  pro posed: http://people.c anoni ca l .com / ~u buntu -archiv e /p r o pos ed -m igr at i on /upda te_ output. txt
<Alber tA>  h ttp://pasteb i n. ubuntu.com /92 50453/
<Albe rtA > ogra _:  it looks  li ke ub untu-t o uch pa ckage has  a dep on  libmir p l at form 3driver-android
< A lb e rtA> ogra_: an d look in g  a t the  RE ADME it se em s iti s based on t h e s e eds: http://b azaar.launc h pad .net/~ ub unt u -branc hes/u bu n tu/ vivid/ubunt u-to uch-meta/ vivid/ v iew/hea d :/READM E
<Alb ert A>ogra _ :an y i de a s o n  h owt o m ove forw ar d? 
<ogr a_>b y d ropp ing  it;)
<o gra_> its a b itawkw a rdthatwe ha ve t oupdat e theseeds  f or such a chang e...  that mea nsne w - me ta pa c kagesfor  ev ery ABI  bump y o u g uy s d o<ogra_> would be n ic e r  t o have a  highe r  l ev e l libmir  m eta  pac k a ge th at t h eseed cou ld dep e nd  o n
<Albe rt A> ogr a_ : r igh t tha t 's w hy thi s new mi r rel e ase introduces mir-graphics- d ri v e rs - andr oid 
<ogra_> (s imil a r to  lin u xvsl inux- image  v s  l i nux-image-$(uname - r) 
<ogra _> ah , right, so l ets land t h i s  then :) 
<Al b er t A> so do we ma nuall y modify t h e dep li sts f or ubunt u-touch a n d  land it  to get her  wi t h  t he mir releas e ? 
<Al be rtA> og ra_ :^
<ogr a_>  no 
<o gra _>  ubuntu-t ouch-met age ts  g ene rated from the  s eed s;)<Albe r tA> og ra_:ok
< og ra _ > i  just m e rg e d  you rse ed c han ge ... t akes a b it to g enerate t hep acka ge 
< ogra_>i'll upload a sa p
<AlbertA >ogr a_: ok t hanks!
< alan_g> alf__: I'm look i ng at M irS creen cast Test andthi nkingtha t  the t ests t hat d ep end o n the m oc k_s cr eencast ar e rea lly i nt egra tion te sts. (And that the rem aining testsdon 't r e a ll y p r ov e  th ef eat u r e.) Do you conc ur?
<alf__ >a la n_g: looki n g
< al f__> al an_g: I  most l y agree . This (l ike other  t ests ) wou ld like to  be true  end-to-e n d tes t s,  butunf ortuna te lythat' s notp oss iblewith o ur  curre nt CI  i nfrastru cture.
<alan
 into_GlibMainLoop recently
<AlbertA>_ogra_: the mir release_is stuck_in_proposed: http://people.canonical.com/~ubuntu-archive/proposed-migration/update_output.txt
<AlbertA>_http://pastebin.ubuntu.com/9250453/
<AlbertA>_ogra_: it looks_like ubuntu-touch package_has a dep on_ libmirplatform3driver-android
<AlbertA> ogra_:_and_looking at the README it seems it is based on the seeds: http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/vivid/ubuntu-touch-meta/vivid/view/head:/README
<AlbertA> ogra_:_any_ideas on_how_to_move forward?
<ogra_> by dropping it_;)
<ogra_> its a bit awkward_that we_have to update the seeds for such a_change..._that means new_-meta packages for every ABI bump you guys do
<ogra_>_would be nicer to have a_higher level libmir_meta_package_that the seed could_depend on
<AlbertA> ogra_: right that's why_this new mir release introduces mir-graphics-drivers-android
<ogra_>_(similar to linux vs linux-image vs linux-image-$(uname_-r)
<ogra_> ah, right, so lets land_this then :)
<AlbertA> so do_we manually_modify the dep lists for_ubuntu-touch and land_it together_with the mir_release?
<AlbertA> ogra_:^
<ogra_> no
<ogra_> ubuntu-touch-meta gets generated_from the seeds_;)
<AlbertA> ogra_: ok
<ogra_> i just merged_your_seed change... takes_a_bit_to generate_the package
<ogra_> i'll_upload_asap
<AlbertA> ogra_:_ok_thanks!
<alan_g> alf__: I'm looking at MirScreencastTest_and_thinking that the tests that depend on_the mock_screencast are really_integration_tests. (And that the_remaining tests don't really prove_the feature.) Do you concur?
<alf__> alan_g:_looking
<alf__> alan_g:_I mostly_agree. This (like other tests) would like to be true end-to-end_tests, but unfortunately that's not possible_with our current CI_infrastructure.
<alan