[00:32] <LuvSy> hello everyone
[00:33] <LuvSy> I need some help
[00:33] <LuvSy> :)
[00:34] <LuvSy> I've a nexus 4 device
[00:34] <LuvSy> And I would like to install ubuntu touch on
[00:36] <LuvSy> achiang:
[00:36] <LuvSy> adam_b:
[00:36] <LuvSy> ajmitch:
[00:40] <achiang> LuvSy: please do not ping everyone in the channel. that is not very polite.
[00:40] <achiang> LuvSy: https://wiki.ubuntu.com/Touch/Install
[00:41] <LuvSy> achiang: I only pinged three people
[00:41] <LuvSy> :)
[00:41] <LuvSy> I went there :v but understood nothing
[00:41] <LuvSy> I wipped my data
[00:41] <LuvSy> :D without a backup
[00:42] <LuvSy> And I have now an empty mobile phone :v with android os
[00:45] <jefinc_> has anyone tried installing on a Samsung Galaxy Rugby?
[02:17] <johnrose13> trying to install Ubuntu Touch on my Nexus 4 and after I type in ubuntu-device-flash --channel devel --bootstrap it keeps telling me ubuntu-device-flash: command not found any suggestions??
[02:18] <johnrose13> i have followed all instructions thus far
[02:23] <nhaines> Aww, I was just about to help him.
[03:54] <vacantplains> Hello, Im following the tutorial on flashing Ubuntu Touch to my Nexus 7 and am on the step that requires actually flashing the device with the ubuntu-device-flash command
[03:55] <vacantplains> the issue is that it says that  command is not found even though I installed everything mentioned in the tutorial
[03:55] <RAOF> vacantplains: Which tutorial?
[03:55] <cwayne> where'd the update-manager app go?
[03:55] <RAOF> The command hasn't been “ubuntu-device-flash” for some months.
[03:55] <vacantplains> https://wiki.ubuntu.com/Touch/Install
[03:56] <vacantplains> Hmm interesting
[03:56] <vacantplains> " ubuntu-device-flash --channel devel --bootstrap" is the full line
[03:58] <vacantplains> where can I find updated documentation? I'm new to Ubuntu in general so i'm not super confident in terminal just yet
[04:02] <Bray90820> Is the touch skin for the desktop version of ubuntu
[04:04] <vacantplains> I dont think so
[04:08] <vacantplains> Sorry but does anyone know the terminal command to flash Ubuntu Touch. I was told  ubuntu-device-flash --channel devel --bootstrap is no longer accurate.
[04:11] <cwayne> vacantplains, what version of ubuntu are you running?
[04:12] <vacantplains> 13.10
[04:13] <cwayne> vacantplains, you'll want to first 'sudo apt-get install phablet-tools'
[04:13] <cwayne> and then the command is 'phablet-flash ubuntu-system --channel devel --bootstrap'
[04:14] <cwayne> ubuntu-device-flash is actually the *newer* one, but AFAIK it's only available on 14.04
[04:14] <vacantplains> awesome thank you! Ill try that now
[04:14] <cwayne> but phablet-flash will surely work, i use it all the time :)
[04:15] <vacantplains> it is indeed running
[04:15] <vacantplains> thank you for the help
[04:15] <cwayne> no problem :)
[04:54] <airking> Hey, where does the phone store the .csv file with my contacts?
[04:54] <airking> and how can I pull it off the phone?
[05:44] <inahandizha> http://VisitsToMoney.com/index.php?refId=386970
[05:49] <airking> quit
[06:38] <fi_> Hello ?
[06:39] <fi_> Is it possible to install ubuntu phone on a IOS device ?
[07:00] <dholbach> good morning
[08:15] <batlol> The Nexus 5 isnt supported?:o
[08:55] <nhaines> rsalveti: ping
[09:23] <JamesTait> Good morning all; happy Love Your Pet Day! :-D
[09:29] <jeanbaptiste> hi everyone
[09:30] <jeanbaptiste> does anyone knows where i can get image for alcatel one
[12:51] <kris825> hi is someone here who speak Polish?
[13:11] <jcbjoe> hi all question
[13:11] <jcbjoe> when i run ./rootstock-touch-install path/to/trusty-preinstalled-touch-armhf.tar.gz /path/to/system.img
[13:12] <jcbjoe> it tells me to put the device in recovery mode yet i can't because i already did a fastboot flash boot boot.img and a fasboot flash recovery recovery.img
[13:12] <jcbjoe> any ideas ?
[13:12] <jcbjoe> im looking at https://wiki.ubuntu.com/Touch/Install_UT_on_android4.4.2
[13:13] <ogra_> jcbjoe, why cant you boot into recovery ?
[13:14] <popey> jcbjoe: why can'#'t you put it in re...
[13:14] <ogra_> (note recovery != bootloader mode)
[13:14] <popey> reboot to fastboot then choose recovery from menu
[13:14] <jcbjoe> it stuck at google logo
[13:14] <ogra_> when you chose recovery from the bootloader menu ?
[13:14] <jcbjoe> yes it boots to a google logo with a lock at the bottom
[13:14] <ogra_> an open one i guess
[13:15] <ogra_> try: adb reboot recovery
[13:15] <jcbjoe> yes
[13:15] <ogra_> smells like to triggered a normal boot (that indeed fails if you have no tarball installed)
[13:15] <ogra_> s/to/you/
[13:16] <jcbjoe> do i start over ?
[13:16] <ogra_> no, do what i wrote
[13:16] <ogra_> adb reboot recovery
[13:17] <jcbjoe> adb devices dosen't show my device
[13:17] <ogra_> ah, then hold power and vol-down until you get back into the bootloader mode
[13:17] <jcbjoe> ok
[13:18] <ogra_> select "recovery mode" in the big arrow via the volume keys and press power to boot into recovery
[13:18] <jcbjoe> ok
[13:18] <jcbjoe> now its stuck at google logo
[13:21] <jcbjoe> the recovery.img im using do you thin its jacked ?
[13:21] <jcbjoe> http://people.canonical.com/~rsalveti/aosp/name_of_device/ < --- this website fails to work
[13:21] <jcbjoe> i downloaded the files somehwer elese
[13:21] <ogra_> err, you need to put your device name there
[13:21] <ogra_> (instead of "name_of_device")
[13:22] <jcbjoe> oh
[13:22] <ogra_> what do you try to install on ?
[13:22] <jcbjoe> so nexus7 or flo since its a n7 2013 ?
[13:22] <ogra_> flo then
[13:22] <ogra_> http://people.canonical.com/~rsalveti/aosp/flo/
[13:23] <ogra_> what did you flash then, if you didnt have the files ?
[13:24] <jcbjoe> i googled people.anicicalcom aosp something and it took me to http://people.canonical.com/~rsalveti/aosp/
[13:24] <jcbjoe> it has a lit of files
[13:25] <jcbjoe> flo / grouper / mako etc ..
[13:25] <jcbjoe> i think i downloaded grouper
[13:25] <jcbjoe> all the files where like 7.2mb
[13:26] <jcbjoe> alright le tme try theses
[13:28] <jcbjoe> oo
[13:29] <jcbjoe> recovery has a ubuntu symbol in the back
[13:29] <ogra_> great
[13:29] <jcbjoe> :D
[13:29] <ogra_> now run the rootstock script
[13:29] <jcbjoe> wrong files so sad
[13:30] <jcbjoe> im so exicted
[13:30] <ogra_> :)
[13:31] <jcbjoe> http://people.canonical.com/~rsalveti/aosp/
[13:31] <jcbjoe> oops sorry
[13:31] <jcbjoe> copying and pasting from a vm machine
[13:32] <jcbjoe>  transfering rootfs tarball ...
[13:32] <jcbjoe> that normal ?
[13:37] <luvsy> I am trying to install ubuntu touch on my nexus 4
[13:37] <luvsy> And I got an error
[13:37] <jcbjoe> ogra_ or popey transfering rootfs tarball ... been there for like 5 mins
[13:37] <jcbjoe> is that normal ?
[13:37] <luvsy> usage: phablet-flash [-h]  ... phablet-flash: error: too few arguments
[13:37] <ogra_> jcbjoe, yes
[13:37] <jcbjoe> ok
[13:37] <ogra_> luvsy, what was the exact line you typed ?
[13:38] <luvsy> phablet-flash -b
[13:38] <ogra_> heh
[13:38] <luvsy> ogra_:
[13:38] <ogra_> luvsy, phablet-flash ubuntu-system --channel trusty -b
[13:38] <ogra_> try that one
[13:38] <luvsy> ok
[13:39] <luvsy> ogra_: it is working
[13:39] <ogra_> yup :)
[13:39] <luvsy> I am not into these things alot
[13:39] <luvsy> so if you are not busy you can help me to finish it
[13:39] <luvsy> Only if you are not busy
[13:39] <timppa> should luvsy use ubuntu-device-flash ?
[13:39] <ogra_> it should finish alone
[13:39] <luvsy> ok
[13:39] <ogra_> timppa, theoretically yes
[13:40] <timppa> luvsy: https://wiki.ubuntu.com/Touch/Install
[13:40] <sergiusens> theoretically?
[13:40] <ogra_> :)
[13:40] <timppa> :)
[13:40] <luvsy> timppa: I tried to do these lines on wiki ubuntu
[13:40] <luvsy> But I get stuck in some points
[13:41] <ogra_> sergiusens, make phbalet-tools a metapackage that pulls in ubuntu-device-flash and make phablet-flash a link to it
[13:41] <ogra_> s/it/the binary/
[13:41] <timppa> luvsy: that's ok, we'll try to help you
[13:42] <luvsy> timppa:  :D Thanks
[13:42] <luvsy> I always wanted to try ubutu touch on my phone
[13:42] <luvsy> I bought necus 4 special to install this os :)
[13:42] <timppa> luvsy: It's great and get's better and better every day!
[13:42] <luvsy> Thanks fantastic
[13:43]  * sergiusens nexus 4 and ubuntu are the only thing I have
[13:43] <timppa> luvsy: I've been running it as my main phone os for a while now
[13:43] <luvsy> I wish I was a programmer to help you guys
[13:43] <luvsy> :D timppa it will be my only phone os for a long while up to now
[13:43] <ogra_> we sometimes put bugs in for you to find :)
[13:44] <ogra_> use it and report them ;)
[13:44] <luvsy> :v once i found a bug in ubuntu
[13:44] <luvsy> Sure
[13:44] <luvsy> :)
[13:44] <ogra_> that helps a lot already
[13:44] <luvsy> :D I am helpful xD
[13:45] <jcbjoe> ogra_ how longs does transfering rootfs tarball ... do this ?
[13:45] <timppa> luvsy: Did you read that there will be two new ubuntu phones this year?
[13:46] <ogra_> jcbjoe, 10min or so usually
[13:46] <jcbjoe> aw
[13:46] <luvsy> timppa: really? nope
[13:46] <timppa> luvsy: yes! That wicked!
[13:46] <luvsy> Can i bought one ?
[13:46] <luvsy> buy
[13:46] <luvsy> :D
[13:47] <doomlord_> phones with ubuntu by default? will they have desktop convergance ?
[13:47] <ogra_> luvsy, http://www.omgubuntu.co.uk/2014/02/bq-meizu-ubuntu-smartphones-confirmed-for-2014-release
[13:47] <ogra_> doomlord_, nope
[13:47] <ogra_> convergence is still far out ... just great phones for now
[13:48] <doomlord_> ok convergance is where it gets interesting for me :)
[13:48] <doomlord_> i would take something with even a primitive desktop
[13:48] <ogra_> first unity8 needs to enter the desktop
[13:48] <timppa> I'm also waiting for it too
[13:48] <luvsy> ogra_ timppa no problem, I will give my necus 4 to my young brother and will buy one :D
[13:48] <ogra_> then we can start wroking on convergence
[13:53] <doomlord_> would it be possible to get an old 2d desktop (gnome classic, XFCE, whatever) on an ubuntu phone
[13:54] <doomlord_> i'd use that :)
[13:54] <ogra_> nope
[13:54] <ogra_> well, the system is open, you can indeed hack the hell out of it
[13:55] <OttOmanTR> ogra_: Ubuntu Touch phone is in sight huh? :)
[13:55] <ogra_> yep :)
[13:56] <OttOmanTR> I don't know about bq but meizu is a good company
[13:56] <ogra_> BQ is fine too
[13:56] <ogra_> not as powerful HW but it will alos be cheaper
[13:57] <OttOmanTR> umm
[13:57] <OttOmanTR> both company will manufacture the same hardware right?
[13:57] <ogra_> no
[13:57] <OttOmanTR> same features etc
[13:57] <ogra_> two pdifferent phones
[13:57] <OttOmanTR> umm
[13:58] <ogra_> i would say bq is rather upper middle class, while meizu is high end
[13:59] <luvsy> ogra_: INFO:phablet-flash:Decompressing partitions/recovery.img from /home/ahmad/التنزيلات/phablet-flash/imageupdates/pool/device-9d396bed22b036d92241420d70b4656ea3ef895a3b43274f936d764081b0d1e2.tar.xz INFO:phablet-flash:Restarting device... wait error: device not found ERROR:phablet-flash:Command 'adb reboot bootloader' returned non-zero exit status 1 Removing directory /tmp/tmpZIYDL6 Removing directory /tmp/tmpgI7XHV
[13:59] <luvsy> it gave me this in the end
[13:59] <OttOmanTR> I couldn't find any answer one of my questions. How will end users get updates if let say samsung makes an ubuntu touch phone?
[14:00] <jcbjoe> ogra_ thanks im on ubuntuy touch looks so nice
[14:01] <popey> OttOmanTR: that depends on what samsung and the carriers who deliver it want to some degree
[14:02] <luvsy> timppa: it gave me some errors
[14:02] <OttOmanTR> popey: I'm a long term Samsung user. The biggest problem with Samsung(and others too) is their update policies. I know you aware of this issue as well
[14:03] <timppa> luvsy: just a moment
[14:03] <luvsy> ok
[14:03] <sergiusens> xnox, can you check lp:~xnox/phablet-tools/py2-3  again?
[14:07] <xnox> sergiusens: ok about first comment.
[14:07] <xnox> sergiusens: confused about the seccond one.
[14:07] <xnox> sergiusens: we agreed that "x-test/autopilot" will have the value of the test modules and is python3 capable one.
[14:08] <xnox> sergiusens: no key, we assume stock location (tests/autopilot) and python2.
[14:08] <xnox> sergiusens: or are you planning to keep enforcing "tests/autopilot" in python3 capable modules and thus "x-test/autopilot" value is ..... "True" ?
[14:09] <xnox> sergiusens: or are there two keys "x-test/autopilot" and "x-source/autopilot-dir" ?
[14:11] <ogra_> jcbjoe, yay, great
[14:30] <sergiusens> xnox, oh, the second comment is; the value is the python module, not the path to the python module
[14:31] <sergiusens> python package...
[14:33] <xnox> sergiusens: oh, as in "app_foobar_tests", not "tests/autopilot/app_foobar_tests" as i though ?
[14:33] <xnox> s/though/thought/
[14:33] <xnox> gotcha.
[14:34] <sergiusens> xnox, yeah, I though of it more for the target and not the source; if that makes it clearer
[14:34] <sergiusens> xnox, the last part of it is just a comment, not something we agreed on or anything
[14:48] <luvsy> ogra_:  one last thing dude
[14:48] <luvsy> :D
[14:48] <ogra_> sure
[14:48] <luvsy> it says, ROM may flash stock recovery on boot
[14:49] <luvsy> fix?
[14:49] <luvsy> what should I do
[14:50] <ogra_> hmm
[14:50]  * ogra_ hasnt used phablet-flash in a while 
[14:50] <ogra_> but i think you can say yes there
[14:50] <luvsy> the optoins are no no no no no and yes disable recovery flash
[14:51] <luvsy> :D
[14:51] <luvsy> I thought that to
[14:51] <luvsy> too
[14:51] <luvsy> thanks
[14:51] <ogra_> (we default to ubuntu-device-flash nowadays ... as sergiusens mentioned earlier ....)
[14:51] <ogra_> https://wiki.ubuntu.com/Touch/Install#Step_4_-_Downloading_.26_Deploying_Image_to_Device
[14:52] <luvsy> it restart the device when I choose yes
[14:53] <luvsy> I see a black screen now
[14:53] <luvsy> wow
[14:53] <luvsy> I see ubuntu
[14:53] <luvsy> ogra_:  wow
[14:53] <OttOmanTR> Ubuntu Touch's dual boot feature is awesome. Too bad it's not available for all devices :(
[14:55] <luvsy> ogra_: I am going now :3 thank
[14:55] <ogra_> luvsy, enjoy :)
[14:55] <luvsy> ogra_: :3
[14:56] <mterry> kgunn, you filed a bug on my behalf regarding letting an app continue working in background while the screen was off (related, but not the same as bug 1233564).  Do you still have that bug number?  I closed that tab and didn't find it on some quick searches
[14:57] <kgunn> mterry: yep....2 secs
[15:00] <kgunn> mterry: hmmm....now i'm having trouble finding....wonder if someone dup'd (it the one bad thing on lp)
[15:02] <kgunn> mterry: found it....https://bugs.launchpad.net/mir/+bug/1279422
[15:02] <kgunn> weird...i didn't find it under my own user view
[15:02] <kgunn> bad eyes i guess
[15:03] <mterry> kgunn, thanks!  I was searching in ubuntu bugs.  :)  Added task
[15:04] <kgunn> mterry: do the mir guys really understand what you need ?....they were kind of "head scratching" when i logged it saying "huh"
[15:05] <kgunn> might want to share more....
[15:05] <xnox> sergiusens: is there a click i can test the python3 codepath with?
[15:05] <xnox> sergiusens: and/or write some tests for this stuff.
[15:06] <mterry> kgunn, I think I need a better understanding of how Mir "freezes" apps when it can't accept buffers in order to put it in the right technical terms for the Mir guys.  Do you know a particular person that could explain that to me?
[15:07] <kgunn> mterry: honestly mir shouldn't "freeze" anything in particular...simply if a buffer is available to render into, you can make draw calls...
[15:07] <kgunn> only time you might get serialized is in the case where you overdrive the display
[15:07] <sergiusens> xnox, nothing is really ap/py3 yet; would need to ask balloons
[15:07] <kgunn> e.g. you might wait for 16ms max (theoretical)
[15:08] <sergiusens> xnox, wrt to tests; I was told you need to make it a module; unless you mean more of an integration tests
[15:08] <kgunn> but otherwise, i'm not aware of any reason or mechnanism that "freezes" the client
[15:08] <xnox> sergiusens: true, cause i get some other issues might come up during py3 tests enabling. and we'll need to handhold some things.
[15:08] <kgunn> ....and i think that's why the team said "huh"
[15:09] <sergiusens> xnox, fwiw; balloons told me that the qa sprinters were going to make the move
[15:09] <mterry> kgunn, I had it described that apps are put to sleep when the screen is off by virtue of Mir not accepting their draw buffers (and this somehow also stopped their logic -- I assumed by Qt's mainloop blocking)
[15:09] <xnox> sergiusens: but they seem to be confused, hence the conference call with them at 5pm GMT today.
[15:09] <mterry> kgunn, how are apps put to sleep normally, when unfocused?  I assume it's the same mechanism
[15:09] <luvsy> ogra_: Dude are you still
[15:09] <xnox> sergiusens: did you get an invite?
[15:09] <kgunn> mterry: mmm...might be up the stack then...maybe unity-mir blocking ?
[15:09] <sergiusens> xnox, nope
[15:11] <mterry> greyback, heyo!  Do you know anything about how apps are put to "sleep" when unfocused?  Is that via unity-mir?
[15:11] <mterry> greyback, er, probably not unity-mir...  But do you know how Mir does that?
[15:11] <kgunn> mterry: might give greyback some breathing room :) ...mwc getting "fun"
[15:11] <mterry> kgunn, OK  :)
[15:12] <mterry> kgunn, this question doesn't need to be solved today
[15:12] <kgunn> mterry: sure....and i bet racarr might be able to chat on this....when he's awake
[15:12] <luvsy> guys how to fix the wifi problem
[15:12] <luvsy> and there is no sound too
[15:12] <luvsy> on ubuntu touch device
[15:12] <xnox> sergiusens: you should have mail.
[15:13] <greyback> mterry: a message is sent by unity-mir via mir, there's a lifecycle message type in Mir itself. Client's listen for it and can save their state if they want. After 3 seconds, unity-mir sends a SIGSTOP to pause the app. on reusme it sends SIGCONT
[15:14] <mterry> greyback, thanks!  I will bug racarr for details  :)
[15:14] <greyback> np
[15:19] <sergiusens> xnox, sounds good
[15:23] <boiko> cwayne: you probably have seen it already, but just in case: webbrowser changes are alraedy released
[15:23] <cwayne> boiko, yep, is aw that.. thanks a lot :)
[15:23] <boiko> cwayne: np
[15:44] <jcbjoe> is ubuntu-touch very beta still
[15:44] <jcbjoe> i got it on my n7 and its smooeth but finiky
[15:46] <ogra_> jcbjoe, the flo image is only about two weeks old :)
[15:50] <jcbjoe> ogra_ http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/pending/trusty-preinstalled-touch-armhf.tar.gz  ?
[15:50] <jcbjoe> is that the image ?
[15:50] <ogra_> no
[15:50] <ogra_> there is no actual  "image" yet
[15:50] <jcbjoe> oh system.img is the image ?
[15:50] <jcbjoe> oh
[15:50] <jcbjoe> so what am i running ?
[15:50] <ogra_> rootstock resempbles the process of image creation on the device actually
[15:50] <jcbjoe> ok i got it
[15:51] <ogra_> official images will show up soon on system-image.ubuntu.com
[15:52] <jcbjoe> cool
[15:53] <ogra_> the rootstock image is created in a way that you should be able to do an OTA upgrade via adb with it
[15:53] <jcbjoe> do you work for canicol ?
[15:53] <ogra_> yep
[15:54] <jcbjoe> oh nice
[15:54] <ogra_> well, not for canicol ...
[15:54] <mrgoodcat> ogra_ was helping manage the ubuntuonair yesterday
[15:54] <ogra_> well, i just tried to tame the storm of questions :)
[15:55] <jcbjoe> if im correct earlier somebody said some ubuntu phones will be coming out
[15:56] <jcbjoe> verizon or only gsm carriers ?
[15:57] <mrgoodcat> verizon would be awesome, but i doubt meizu or bq is likely to make a verizon compatible device...
[15:58] <pmcgowan> jcbjoe, only gsm for now, no cdma support
[15:59] <pmcgowan> hopefully verizon will move on from that
[15:59] <ogra_> jcbjoe, i think the meizu will be GSM/HSPA hardware (and no carrier) and Bq is a spanish company ... so unlikely to ship CDMA or some such
[15:59] <mrgoodcat> meizu's current flagship is GSM/GPRS/EDGE/WCDMA/HSPA+
[16:09] <jcbjoe> ubuntu-touch support flash ?
[16:09] <jcbjoe> can't play this cnn video
[16:24] <daker> AlanBell: http://www.jonobacon.org/2014/02/20/todays-ubuntu-news/#comment-1252665950
[16:28] <sergiusens> jcbjoe, no flash
[16:36] <buharim> Anyone can help me in Samsung P6200 model
[16:38] <buharim> Anyone can help me in Samsung P6200 model
[16:43] <sergiusens> balloons, what's the status of py3 migration for tests?
[16:45] <balloons> sergiusens: we're meeting with barry again in 10 mins, however it requires a patch to AP
[16:45] <balloons> so eta atm is pending that patch, but sounds like they have everything ready
[16:45] <sergiusens> balloons, yeah, not autopilot itself, the tests :-)
[16:46] <sergiusens> balloons, one of the MRs is the one I asked you to check from xnox ;-)
[16:58] <Laney> barry: you getting on the train?
[16:58] <Laney> choo choo
[16:59] <barry> Laney: chugga chugga
[17:00] <Laney> I saw you managed to get a build
[17:00] <barry> Laney: on a non-virt ppa, yes
[17:00] <Laney> ya
[17:07] <balloons> sergiusens: re:py3, see https://code.launchpad.net/~barry/autopilot/reexec/+merge/203765
[17:07] <balloons> and https://blueprints.launchpad.net/ubuntu/+spec/core-1311-python3-roadmap
[17:15] <xnox> sergiusens: i think the plan is coming together. W.r.t to package to test, we'll just make a dummy python2 and python3 click and deb for testing.
[17:16] <xnox> sergiusens: such that i can verify phablet-test-run end-to-end.
[17:16] <xnox> sergiusens: and then we can upload p-t-r.
[17:16] <xnox> sergiusens: and that will then unblock everything else.
[17:17] <barry> xnox, sergiusens sounds great.  i am going to leave things to you guys until the infrastructure changes land, then i'll return to actual porting of the various app tests (first)
[17:17] <xnox> barry: ack.
[17:19] <xnox> ogra_: back in the day, on a "ubuntu-desktop-nexus7" did we have plymouth up and running?
[17:19] <ogra_> xnox, nope
[17:19] <ogra_> tegra issue
[17:19] <ogra_> we had plymouth running on the panda desktop installs
[17:19] <xnox> ogra_: i thought i remembered boot splash on it =/
[17:20] <ogra_> on shutdown perhaps
[17:20] <xnox> ogra_: do we still have those images around anywhere?
[17:20] <ogra_> the console handling on tegra isnt sane
[17:20] <ogra_> might be on cdimage.../releases/ports or so
[17:20] <Tassadar> they are there
[17:21] <Tassadar> http://cdimage.ubuntu.com/releases/raring/release/
[17:21] <xnox> Tassadar: thanks.
[17:22] <xnox> now to remember how to install it =) i guess flash boot and flash userdata....
[17:22] <ogra_> xnox, http://cdimage.ubuntu.com/releases/raring/release/
[17:22] <Tassadar> yeah, the wiki is still up too I think
[17:22] <ogra_> ah, Tassadar was faster
[17:24] <luvsy> guys, I installed ubuntu touch on nexus 4
[17:24] <luvsy> But it doesnt connect to wifi
[17:24] <luvsy> also it has no sound
[17:24] <ogra_> luvsy, did you have android 4.4 installed before ?
[17:24] <luvsy> yeah
[17:24] <luvsy> :O
[17:24] <ogra_> one sec
[17:24] <luvsy> ok
[17:25] <ogra_> luvsy, https://wiki.ubuntu.com/Touch/DualBootInstallation#Getting_phone_calls_to_work_in_Ubuntu_and_Android_4.4
[17:25] <luvsy> I will check it out
[17:25] <ogra_> (that wont happen anymore next week when we have switched the official images to a 4.4 base)
[17:27] <luvsy> Download an Android 4.3 firmware for your device onto your PC. Follow the links on this table >
[17:27] <luvsy> ogra_: which firmware ? I saw nothing
[17:27] <ogra_> from google
[17:29] <luvsy> Okay I think I got it
[17:29] <luvsy> It is downloading
[17:30] <sergiusens> xnox, do you need me in any meeting? I don't think I recv any email
[17:30] <xnox> sergiusens: it's all done and dusted... i did sent a canonical calendar invite to you via google calendar....
[17:31] <Tassadar> ogra_: wouldnit's gonna be incompatible the other way around after that
[17:31] <Tassadar> *wouldn't keep my hopes up, it's gonna be...damn return key is too close to backspace)
[17:32] <ogra_> Tassadar, i think it is backwards but not forwards compatible
[17:33] <Tassadar> I thought it was the both ways, hm
[17:35] <luvsy> ogra_: should i download android 4.3 fir,ware or 4.4
[17:35] <luvsy> -_- I feel silly
[17:35] <ogra_> luvsy, 4.3
[17:35] <luvsy> ok
[17:35] <luvsy> I downloaded 4.4
[17:35] <ogra_> the current hardware layer ubuntu touch uses uses drivers from 4.3
[17:36] <luvsy> ah
[17:36] <luvsy> ok
[17:36] <ogra_> thats why the 4.4 firmware (that is already installed from your android install) does not work
[17:36] <luvsy> I see
[17:49] <Saviq> ogra_, rsalveti, hum we fell into tablet greeter on portrait flo
[17:50] <ogra_> due to the GU change ?
[17:50] <Saviq> ogra_, yes
[17:50] <ogra_> sight
[17:50] <ogra_> -t
[17:51] <Saviq> ogra_, well, it's meant to be available https://docs.google.com/a/canonical.com/file/d/0B-a_7E3tDxOgMzI2TFlYOGNrOVU/edit
[17:51] <Saviq> ogra_, but it's not looking like that atm ;)
[17:52] <ogra_> is there a fix in the pipe ?
[17:52] <ogra_> before monday ?
[17:52] <Saviq> ogra_, no
[17:52] <ogra_> so do we need to roll the GU back to 21 ?
[17:52] <ogra_> or what do we do now
[17:53] <Saviq> ogra_, no, I'll just increase the threshold for tablet greeter
[17:53] <ogra_> ah, k
[17:53] <Saviq> ogra_, or actually make it height > width
[17:53] <Saviq> as that's the only place where it makes sense right now
[17:55] <Saviq> ogra_, will you have time to get silo 016 on your flo and check it out?
[18:02] <ogra_> Saviq, did you upload already ?
[18:02] <Saviq> ogra_, the fix, not yet
[18:02] <ogra_> note that i'm only running the normal image here
[18:02] <Saviq> ogra_, that's what I'm testing, too
[18:02] <ogra_> ok
[18:02] <Saviq> ogra_, otherwise I'd be in landscape ;)
[18:02] <ogra_> hehe, yeah
[18:03] <ogra_> you must be cwayne or pmcgowan to like that :)
[18:03] <Saviq> ogra_, ;D
[18:03] <Saviq> ogra_, I like it in landscape :)
[18:03]  * pmcgowan looks around
[18:03] <Saviq> @18px, though, not @21 ;D
[18:03] <ogra_> i would like it if it was optional
[18:04] <Saviq> ogra_, it is
[18:04] <Saviq> ogra_, even when we merge all of that
[18:04] <pmcgowan> once Saviq fixes shell rotation its all good
[18:04] <Saviq> ogra_, it's just a NATIVE_ORIENTATION in /etc/ubuntu-touch-session
[18:04] <ogra_> optional by hacking the option on cmdline
[18:04] <ogra_> :)
[18:04] <Saviq> pmcgowan, once the designers... oops, who's that?
[18:04] <ogra_> pmcgowan, ++
[18:04] <pmcgowan> ouch
[18:06] <Saviq> pmcgowan, no, but for real once we get the new right edge+side stage sorted out, shell rotation will happen
[18:06] <pmcgowan> Saviq, good makes sense
[18:07] <Saviq> ogra_, kicked a rebuild, should be ready in 20 or so
[18:07] <ogra_> Saviq, ok, just getting dinner here and re-generating the meta for sergiusens ... might take a bit more than 20min until i return, but i will test
[18:07] <Saviq> ogra_, o/
[18:09] <sergiusens> ogra_, no hurries from me; lots of building needs to happen as well
[18:13] <timppa> hi!
[18:13] <timppa> Is there a way to start unity8 on 14.04 desktop version by default?
[18:17] <nhaines> Okay, I'm bringing my Nexus 5 to SCALE tomorrow and I want to show off Ubuntu.  I have an XDA rootfs that works beautifully (no sound though) and the daily rootfs has some graphical corruption.
[18:17] <nhaines> I'm not worried about sound--I'm dualbooting at the momment.  Is there any recommended rootfs for hammerhead?
[18:18] <rsalveti> Saviq: ogra_: cool, let me know if you need a hand to test flo as well
[18:18] <nhaines> rsalveti: oh, maybe you have some idea about hammerhead.  :)
[18:45] <nik90> charles_: you around?
[18:48] <ogra_> re
[18:53] <ogra_> sergiusens, -meta is in the silo
[18:53] <ogra_> nhaines, https://wiki.ubuntu.com/Touch/Install_UT_on_android4.4.2
[18:54] <sergiusens> ty
[18:54] <ogra_> nhaines, but not everything works yet
[18:54] <ogra_> (i.e. no sound=
[18:54] <ogra_> )
[18:54] <mandel> barry, do you want to try and test the entire stack for updates?
[18:54] <mandel> Laney, is EOD but we can ask someone else to do the build for us
[18:56] <nhaines> ogra_: thanks, I'm okay with sound--I'm not taking calls at the Ubuntu booth at the conference anyway.  :)
[18:57] <ogra_> :)
[18:57] <nhaines> ogra_: I was hoping for an up-to-date ubuntu-touch-4.4.2-mir.rootfs-armhf.zip like the one you kicked off at the end of January.
[18:57] <ogra_> you dont need any special rootfs anymore
[18:57] <nhaines> The daily preinstalled is still 4.3-based, I guess, and has graphical corruption on switching.
[18:57] <ogra_> just follow the doc
[18:58] <nhaines> ogra_: then the graphical regressions (right-side switching) isn't suitable for the conference... and your special rootfs is actually going to be the best for the weekend.
[18:59] <nhaines> Is it worth it to file hammerhead performance bugs at this time?  I can do it next week.
[18:59] <ogra_> well, you can indeed file them, but hammerhead isnt planned as supported device atm
[19:02] <Tassadar> nhaines: did you turn on MIR?
[19:03] <Tassadar> surfaceflinger has some graphical corruption when you're switching apps and couple other places, but it's okay with mir
[19:04] <ogra_> rootsotck does that automatically
[19:04] <ogra_> the image should be flawless apart from the non working sound (and probably non working radio, not sure)
[19:04] <Tassadar> yeah, that's why it works with your rootfs
[19:05] <Tassadar> radio works, - you can call, but you can't hear anything, and messages work too
[19:05] <ogra_> heh
[19:12] <ogra_> Saviq, hmm, so i git the normal phone greeter here
[19:12] <ogra_> (testing flo with the PPA)
[19:14] <ogra_> i *really* like the resolution with GU=18
[19:16] <ogra_> hmm, but i get a weird black bar on the right
[19:16] <ogra_> when running the calculator
[19:17] <ogra_> thats all pretty weird
[19:19] <ogra_> settings app doesnt take my tap after selecting my city in the TZ selection
[19:19] <ogra_> bah
[19:19] <Saviq> ogra_, yeah, it built already
[19:19] <ogra_> and now the kbd died
[19:25] <sergiusens> xnox, do you have time to help fix libcontent-hub-dev:armhf -> libcontent-hub0:armhf -> libupstart-app-launch2:armhf -> click:armhf ?
[19:27] <xnox> sergiusens: sure, what in particular you need fixing? e.g. something fails to cross-compiler, or does e.g. click chroot fails to be created?
[19:27] <ogra_> Saviq, that doesnt look ok to me
[19:28] <ogra_> looks like i have a sidestage without content dangling around permanently
[19:28] <sergiusens> xnox, I need to install libcontent-hub-dev:armhf in the click chroot, but it fails due to that dep chain (wants click:armhf)
[19:29] <xnox> sergiusens: i see. libupstart-app-launch2:armhf should not depend on click.
[19:29] <sergiusens> xnox, it uses click in it's runtime I think to get the click dir; tedg ?
[19:30] <xnox> sergiusens: tedg always puts bogus dependencies in. libraries should not depend on runtime application. it should be the other way around, as otherwise cross-compilation is broken.
[19:30] <sergiusens> xnox, but busts cross building while at it
[19:30] <xnox> sergiusens: sure, but you are cross-compiler and not running/executing click..... thus you don't need runtime click at all.
[19:31] <xnox> sergiusens: i'd be surprised how a shared library could call exec to click when something else compiles against it =)
[19:31] <sergiusens> xnox, yeah, that's not fun :-)
[19:38] <Saviq> ogra_, yeah, it's no good
[19:40] <xnox> sergiusens: uploaded.
[19:41] <sergiusens> xnox, sweet; thanks
[19:45] <Saviq> ogra_, it looks like it gets confused whether to put the apps in side stage or not
[19:46] <ogra_> well, my apps are all stuck on the left side
[19:46] <Saviq> ogra_, not browser, though
[19:46] <Saviq> ogra_, nor gallery
[19:47] <Saviq> ogra_, so it does feel like sidestage apps are positioned wrong
[19:47] <ogra_> ah, havent tried them ... i had calc, clock and system-settings
[19:47] <ogra_> (and i'm in recovery atm to check something else)
[19:48] <Saviq> greyback, you around?
[19:55] <tedg> xnox, Uhm, it kinda does. A function in the lib calls click.
[19:56] <tedg> xnox, Once libclick exists, that'll be more appropriate, but it doesn't exist yet.
[19:58] <xnox> tedg: no. a shared library.so does not call anything, when a executed ld against it.
[19:59] <xnox> tedg: i think you wanted "Breaks: click (<< 4.9)" to indicate that you need click as good as that version with libupstart-app-launch2 as otherwise the two are incompatible.
[19:59] <xnox> (e.g. either fetch newer click, or older libupstart-app-launch)
[20:00] <xnox> tedg: honestly libfoo package may only ever depend on other libraries, and at most runtime packages which must be Multi-Arch:foreign.
[20:00] <xnox> (any non-Multi-arch:foreign runtime packages make no sense)
[20:00] <tedg> xnox, The lib shells out to call click though, as a part of it's functionality.
[20:01] <tedg> xnox, It's effectively using like a .so.
[20:01]  * tedg would rather have a .so
[20:17] <mandel> barry, hey, can you give us a hand related to the si new code? do you know if all the branches you need are reviewed?
[20:17] <mandel> barry, ralsina_ is requesting a silo and would be nice to test the full stack for the updates
[20:17] <barry> mandel: otp.  give me a few minutes
[20:18] <ralsina_> barry, mandel: silo 10, it's building now
[20:18] <ralsina_> http://162.213.34.102/job/landing-010-1-build/16/console
[20:25] <ajalkane> Anyone know where can I find #ubuntu-touch-meeting logs? I'm looking at this page   https://wiki.ubuntu.com/Touch/CoreApps/Meetings but it does not have this weeks meeting logs
[20:27] <xnox> tedg: right, but libfoo.so:armhf libfoo.so:i386 can be both present on my machine, yet only click:amd64  is executable.
[20:27] <xnox> tedg: therefore the dependency declared, doesn't satisfy your requirements.
[20:30] <barry> mandel, ralsina_ so, i've made an upstream release, but i need to get the new packaging branch mp put together.  then stgraber will review it and we'll get on the train.  do you need something else?
[20:31] <ralsina_> mandel, barry: I'll EOD in ~1 hour so you may need another lander if you want to move this tomorrow
[20:31] <ralsina_> other than that, I am just a remotely-controlled button-clicker in this case ;-)
[20:31] <barry> ralsina_: cool :)  i guess we'll land it tomorrow.  this will be our first journey on the train
[20:32] <ralsina_> barry: cool :-)
[20:32] <tedg> xnox, I don't care about the arch of what /usr/bin/click is… so, I don't understand.
[20:32] <tedg> xnox, You could use both versions of the lib with the amd64 click.
[20:33] <xnox> tedg: correct. "Depends:click" on a multi-arch library however enforces the architecture of /usr/bin/click.
[20:33] <xnox> tedg: hence the "dependency declared is not the one you need"
[20:33] <tedg> xnox, Can I depend on "click:any" ?
[20:34] <xnox> tedg: no, unless click is declared "multi-arch: allowed" i believe. It would not be an issue if click was declared "multi-arch:foreign" as that's a mirror declaration for everyone. (as in any depends are treated as :any)
[20:35] <xnox> tedg: and i don't think click can declare itself "multi-arch: allowed" nor "multi-arch: foreign" due to e.g. shipping an ld-preload .so file.
[20:36] <tedg> xnox, Ah, sure.  This will all go away with libclick, which should be soon.
[20:37] <xnox> tedg: correct. hence i've dropped the dependency from upstart-app-lauch, which is "too big of a hammer" and dependency on click is implicitly provided anyway.
[20:37] <xnox> via other means.
[20:38] <tedg> Eh, that seems like a hack.
[20:38] <tedg> Working around a problem in the system not being able to represent the correct dependencies.
[20:39] <Sleep_Walker> hi
[20:39] <xnox> tedg: the system can represent correct dependencies. but a good library practice is to propagate runtime errors correctly.
[20:40] <xnox> tedg: such that if exec to click fails, you are I presume raising/returning a runtime error, but don't e.g. abort or segfault.
[20:40] <Sleep_Walker> did I understood correctly that for Ubuntu Touch there was programmed new dialer which can work with Android's RILd?
[20:40] <xnox> tedg: thus whilst necessory for correct operation, it is not a hard/mandatory dependency (like a linked-in shared library)
[20:40] <tedg> xnox, The library is mostly useless without click, there's no reason you'd want it without it.
[20:40] <Sleep_Walker> (not only dialer, but control for many HW peripherials)
[20:40] <xnox> tedg: and during compilation / cross-compilation, that library does not need click binary to be present at all.
[20:41] <xnox> tedg: the library is 100% useful when I'm cross-compiling against it.
[20:41] <xnox> tedg: and no, i don't need /usr/bin/click to be present at all, when i am compiling / linking against libupstart-app-lauch2.
[20:41] <tedg> xnox, Heh, it's 100% useful as a symbol table, just not runtime.
[20:41] <xnox> =)))))
[20:42] <xnox> tedg: also libupstart-app-lauch byitself is not a useful thing, cause i hope you didn't go throught trickeries of making the .so executable.
[20:42] <tedg> xnox, Can I add click to the misc depends of any package that depends on the lib?
[20:42] <xnox> tedg: it is unfortunate that end-executables that link against libupstart-app-lauch must declare Depends:click.
[20:43] <xnox> tedg: oooooh, that would be nice wouldn't it be?! i don't think there is mechanism to do that though.
[20:43] <xnox> ideally it would be something in pkg-config data.....
[20:44] <tedg> I think it has to be a dh thing.  pkgconfig isn't tied into the debian stuff enough.
[20:56] <jcbjoe> anyone bored with there nexus 7 or have a rom that will sprice it up
[21:01] <smot> argh
[21:01] <smot> so i just received my nexus 4 and am attempting to flash it. may i just go ahead here? great.
[21:02] <smot> Cannot push /home/derek/.cache/ubuntuimages/stable/mako/version-101.tar.xz to device
[21:08] <ovoodoo> ubuntu touch,  installable on Galaxy Note3?
[21:10] <smot> nevermind
[21:10] <smot> had to unlock bootloader dederrr
[21:14] <popey> 123
[21:14] <popey> bah
[21:18] <sergiusens> popey, is that your password?
[21:21] <smot> almost done deploying manually
[21:21] <ovoodoo> ubuntu touch at MWC?
[21:29] <barry> stgraber: just to verify before i do too much, to get on the ci-train, i need to mp against lp:~ubuntu-managed-branches/ubuntu-system-image/system-image right?
[21:30] <smot> yay, got ubuntu touch running
[21:36] <mterry> ogra_, heyo!  So any objection to me marking /var/lib/lightdm-data as persistent storage in lxc-android-config?
[21:36] <mterry> ogra_, it's a new location that lightdm uses for medium-term storage of larger files
[21:36] <mterry> for sharing between greeter and user sessions (things like camera photos or contact avatars)
[21:36] <ogra_> mterry, fine with me, note that i just uploaded an lxc-android-config change
[21:37] <ogra_> (like this second)
[21:37] <mterry> ogra_, drat  :)
[21:37] <mterry> ah well, I'll get it and upload a new one
[21:38] <ogra_> mterry, literallly pinging 1min earlier i would just have grabbed it from you :)
[21:40] <mterry> ogra_, what does the transition action do?
[21:40] <ogra_> copy existing stuff iirc
[21:41] <mterry> ah, cool
[22:14] <mandel`> barry, I'm going to be around for a little longer
[22:15] <mandel`> barry, we can get another lander (sorry I was having dinner)
[22:15] <barry> mandel`: no worries.  i'm working out the packaging updates and should have an mp before my eod
[22:15] <barry> we can land tomorrow
[22:16] <mandel`> barry, ok, I have my code ready for the and is a matter of testing :)
[22:16] <barry> mandel`: yes, we definitely need to test! :)
[22:16] <mandel`> barry, I think is better to test over the weekend over doing a weekend release, what do you think?
[22:17] <mandel`> barry, the workaround is there so that people can update, and we can reenable automatic updates on monday
[22:17]  * barry invokes warsaw's second law
[22:18] <mandel`> barry, lol
[22:18] <barry> mandel`: i'm good with that, as long as we can get people to actually test the stuff
[22:18] <barry> but i guess that's part of what the ci-train is all about, eh?
[22:19] <mandel`> barry, yes, that is the theory, we can ping asac and others that have real devices to test with
[22:19] <mandel`> barry, worst case, we have a correct fix and will land it late
[22:20] <mandel`> barry, well, I'm going to call it a day then :)
[22:20] <barry> mandel`: sounds good.  i have a real device too.  i think there are three things we need to test together: 1) new udm; 2) new si; 3) previous ui behavior re-enabled
[22:20] <barry> mandel`: cool, let's chat tomorrow
[22:20] <mandel> barry, lets chat that now :)
[22:20] <mandel> barry, the silo has AFAIK latests udm and ui
[22:21] <barry> mandel: does the silo have the ui behavior re-enabled?
[22:21] <mandel> barry, yes
[22:21] <mandel> barry, Laney took care of that
[22:21] <barry> mandel: perfect, then when si gets in the silo we'll have everything we need to test
[22:21] <Laney> hey
[22:21] <Laney> I can press butan
[22:21] <mandel> barry, exactly, that is the idea, that way we land everything at one
[22:21] <mandel> Laney, I though it was later for you ;)
[22:22] <Laney> yeah, but internets are addictive you know
[22:22] <barry> ;)
[22:22] <mandel> Laney, my answer would have been, spanish tv sucks ;)
[22:22] <Laney> I don't know why, but ralsina_ took it over and built with just sytem-settings and udm
[22:22]  * mandel has in the background one of the worst B movies he has ever watched
[22:23] <Laney> but we should still be able to add s-i in
[22:23] <mandel> Laney, ah, he was trying to help and forgot the si
[22:23] <Laney> just got to list the branches
[22:23] <Laney> and get someone from the landing team to reconfigure with those ones included
[22:24] <Laney> barry: do you have the branches ready to go?
[22:25] <mandel> Laney, ok, we can do that in the morning, correct? or are we going to gain anything doing it now? I just don't want to to work this late
[22:25] <barry> Laney: not a packaging branch yet.  still working on that.  upstream is landed
[22:25] <Laney> alright
[22:25] <Laney> mandel: other than being tz-challenged with barry
[22:25] <mandel> Laney, correct, you have a point
[22:26] <barry> Laney, mandel: stgraber will need to review and approve the mp
[22:26] <Laney> barry: add (or get them added) them to 47H when they're ready, that's all you need to do
[22:26] <barry> remember too, this is our first time ridin' the train
[22:26] <Laney> sure
[22:26] <Laney> in the morning I'll press build and then mail the list for people to test
[22:26] <barry> 'k
[22:26] <mandel> ok
[22:26] <stgraber> barry: nope, I don't need to
[22:27] <mandel> Laney, we should get as many tests for this as possible
[22:27] <stgraber> barry: you just need to raise the MP against ~ubuntu-managed-branches/ubuntu-system-image/client and pass that link to the landing team to get it added to the existing silo
[22:27] <mandel> stgraber, but he needs a review, or not?
[22:27] <Laney> yeah
[22:28] <Laney> it should be approved before being silo'd though
[22:28] <stgraber> not in the Foundations team workflow, no
[22:28] <stgraber> because technicall nobody can approved our MP as nobody is in the team owning the target branch
[22:28] <barry> it'll just be package changes anyway
[22:28] <stgraber> *technically
[22:28] <Laney> man you guys weird
[22:29] <stgraber> well, we just wanted to have something that didn't change our old habits (doing clean upstream release + upload) yet use the new CI stuff because we have to
[22:29] <barry> of course, if there's anybody out there that *wants* to help do code reviews on the upstream branches, i wouldn't mind
[22:29] <mandel> Laney, and we though me doing a self-approved was bad hehehe
[22:29] <stgraber> so w found that compromise with Didier ;)
[22:29] <Laney> haha
[22:29] <Laney> anyway, put it in that cell, get landing team to silo, press build, test, ???, profit
[22:29] <stgraber> I thikn our current test list for our projects is basically "[ ] ready for the archive"
[22:30] <stgraber> gah, can't type today apparently, sorry...
[22:30] <mandel> barry, if it is python I can review things, at least I'll ask questions :)
[22:30] <barry> first step: get a working mp
[22:30] <Laney> stgraber: this is a silo with some other fixes, we want to check the stuff all works together
[22:30] <barry> mandel: i *love* the socratic method of code reviews, thanks to kiko :)
[22:31] <Laney> I think you guys have this, so I'm going to play some games
[22:31] <Laney> bye!
[22:31] <stgraber> Laney: sure, in this case it makes sense to do proper testing and everything against the silo.
[22:31] <mandel> barry, then add me for reviews and I'll d them, I'll be more than happy
[22:31] <mandel> stgraber, yes, the idea is that there are 3 projects that have updates that must work together well
[22:32] <stgraber> Laney: it's the process for our other "standard" uploads where we only do a quick check of the resulting binaries but that's about it (since we already run through all the tests when we do the upstream release, long before anything is sent through CI)
[22:32] <barry> stgraber, ah, so one of the fun things about the managed branch is that it includes the source.  my old packaging branch had only debian/.  should we delete the source and just keep debian/ or should we import the new orig.tar.gz?
[22:32] <barry> mandel: okay!  next bunch of code, i will do that
[22:32] <barry> (upstream code)
[22:32] <Laney> stgraber: I think I don't really mind how the sausage is made, actually. :P
[22:32] <stgraber> barry: didn't we say we'd just burn your old packaging branch with fire?
[22:33] <Laney> One issue I have with CI is that it almost removes the concept of upstream releases
[22:33] <barry> Laney: especially the gluten free vegan "sausage"
[22:33] <Laney> (CI as implemented by us)
[22:33] <Laney> so you win on that count as far as I'm concerned
[22:33] <stgraber> Laney: right, that's the bit that bothered me and why we have that weird process for foundations. We do clean upstream releases in a branch without packaging, then we merge-upstream the resulting tarball and branch into another branch which has the packaging and we use that one for CI
[22:33] <barry> stgraber, yes.  but the question is how to transition from the old packaging branch to the new one.  i forget what we decided to do, since the managed branch has the old code, so bzr bd -S complains
[22:34] <stgraber> barry: ah right because we never landed the branch with the current upstream due to the dbus bug?
[22:34] <barry> stgraber right.  so i guess i don't have a strong opinion on whether we should merge-upstream to get the new source, or just have a debian/
[22:35] <stgraber> barry: can you use https://code.launchpad.net/~stgraber/ubuntu-system-image/client-for-didier as a base?
[22:35] <stgraber> barry: that's the one we never landed due to the dbus issue. So you could take that one, add your stuff and send a MP for the result
[22:35] <barry> stgraber for the first time?  then after that we'd use the managed branch, right?
[22:36] <stgraber> barry: so what I'm saying is:
[22:36] <stgraber> 1) bzr branch lp:~stgraber/ubuntu-system-image/client-for-didier new-stuff
[22:36] <stgraber> 2) commit your changes to new-stuff
[22:36] <stgraber> 3) bzr push lp:~barry/ubuntu-system-image/my-fixes
[22:36] <stgraber> 4) bzr lp-propose-merge lp:~ubuntu-managed-branches/ubuntu-system-image/client
[22:37] <stgraber> actually, lp:~ubuntu-managed-branches/ubuntu-system-image/system-image for that last one
[22:37] <barry> stgraber, yep, i see.  i'll still have to merge-upstream into client-for-didier though
[22:37] <barry> which is no big deal
[22:38] <stgraber> barry: right, I only have upstreams up to 2.0.5 in there
[22:38] <stgraber> barry: what's the current upstream version?
[22:38] <barry> stgraber: 2.1
[22:38] <barry> stgraber: makes sense.  let's see if i can make that work ;)
[22:38] <stgraber> ok, so yeah: bzr merge-upstream --version 2.1 --revision tag:2.1 <tarball> <upstream branch>
[22:39] <barry> yep
[22:39] <stgraber> at least you don't need to import every individual upstream release since the last upload ;)
[22:39] <barry> yeah :)
[23:53] <xnox_> sergiusens: sorry, upstart-app-launch upload got rejected. now it's uploaded for real.
[23:54] <xnox_> Laney: please review https://code.launchpad.net/~xnox/unity-control-center/versioned-logo/+merge/207574