[02:24] <racarr> yay...hypothetically cross built against rtm
[02:32] <racarr> something didnt work
[08:49] <alf_> greyback: what is "wizard_socket"?
[08:49] <alf_> greyback: (Good morning!)
[08:50] <greyback> alf_: hey. I've no idea, first I've heard of it
[08:50] <greyback> too early to make a harry pooter joke
[08:51] <greyback> alf_: I know hte startup wizard uses qtmir, as it needs to be a mir server in order to have an OSK client. Perhaps it decided to call its own socket that?
[08:52] <alf_> greyback: Any idea where the start-up wizard project is?
[08:53] <greyback> alf_: lp:ubuntu-system-settings
[08:53] <alf_> greyback: thanks
[08:53] <greyback> np
[08:54] <greyback> alf_: yep, wizard/ubuntu-system-settings-wizard.conf sets a wizard_socket
[08:55] <alf_> greyback: So, I guess unity8 has no business connecting to that socket, right?
[08:55] <greyback> alf_: right
[08:56] <alf_> greyback: I think it picks up by mistake, some leftover environment variable somehow
[08:56] <alf_> greyback: I will check the start-up scripts
[08:56] <greyback> alf_: in post-stop, might be good idea to unset MIR_SOCKET
[08:57] <greyback> or else specify exactly the socket for unity8 to connect to in its startup job
[08:59] <alf_> greyback: so ubuntu-system-settings-wizard-cleanup.conf supposedly restores the MIR_SOCKET to its previous value (WIZARD_ORIG_MIR_SOCKET), but there is probably some kind of race there
[09:07] <greyback> alf_: agreed
[09:07] <alf_> greyback: if only I could reproduce it...
[09:07] <RAOF> Can we have a wizard_socket as a mainstay? :)
[09:08] <greyback> RAOF: back to the muggle mines you
[09:08]  * RAOF returns to his lunar abode
[09:12] <duflu> Oh lunar. Cheesy.
[09:14] <duflu> Mirv, tvoss: Can we drop the overly wordy (and wrong) description text here?... https://launchpad.net/ubuntu/+source/mir
[09:14] <duflu> I don't seem to have permission
[09:15] <tvoss> duflu, did you mean launchpad.net/mir
[09:15] <tvoss> ?
[09:15] <duflu> tvoss: No the link I just gave (under “mir” package in Ubuntu)
[09:16] <Mirv> duflu: I don't see any description there, aside from listing the packaging short descriptions
[09:16] <duflu> Mirv: Yes, they're wrong. And very old
[09:16] <Mirv> duflu: so that's a list of debian/control Description: first lines
[09:16] <duflu> Delete please
[09:16] <tvoss> duflu, those are auto generated
[09:16] <duflu> Hmm where from?!
[09:16] <duflu> Maybe from trusty
[09:16] <duflu> ?
[09:17] <tvoss> duflu, I don't know
[09:17] <duflu> Ah yes. Looks like auto-generated  from trusty
[09:17] <Mirv> duflu: is there some difference to the utopic ones on that page? http://bazaar.launchpad.net/~mir-team/mir/utopic/view/head:/debian/control
[09:17] <Mirv> right, trusty
[09:18] <Mirv> that's really a Launchpad problem/choice then
[09:18] <duflu> Mirv: Yeah the ABI levels are different, and the package names are changing a bit
[09:18] <Mirv> it's definitely a bug also that https://launchpad.net/ubuntu/utopic/+source/mir looks similar
[09:18] <duflu> Excellent. Another important Launchpad page with misleading info we can't fix
[09:19] <Mirv> :(
[09:20] <duflu> Mirv: OK thanks for clarifying :/
[09:22] <alf_> greyback: duflu: Any idea how to add ubuntu-system-settings as affected by the bug? The project doesn't track bugs in launchpad (it's tracked in the ubuntu package).
[09:22] <duflu> alf_: I'll do it
[09:22] <alf_> duflu: thanks
[09:22] <duflu> alf_: (Also affects distribution...)
[09:23] <alf_> duflu: ah, right, that one again... :)
[09:27] <duflu> anpok_: Your 0.7.3 is served
[09:27] <duflu> https://launchpad.net/ubuntu/+source/mir
[09:59] <RAOF> Woo! Branches all green.
[10:00] <duflu> RAOF: Time to run away then :)
[10:00] <RAOF> Yup.
[10:01]  * davmor2 lassos ROAF and stakes him down in front of a computer
[13:51] <sil2100> kgunn: hello!
[13:53] <kgunn> uh-oh
[13:53] <kgunn> sil2100: hello ?
[13:53] <kgunn> :)
[13:56] <sil2100> kgunn: sooo, I'm preparing the FFe for touch inbetween stuff, and noticed that some parts of mir are now used in the default utopic desktop images
[13:56] <sil2100> kgunn: we would like to know what things are planned for mir in this cycle still
[13:56] <sil2100> kgunn: can you guarantee ABI stability at least? :)
[13:57] <kgunn> camako: fyi....
[13:57] <kgunn> sil2100: so right now we are truly in bug fix mode
[13:57]  * camako is all ears (eyes)
[13:57] <kgunn> so no FFe needed i think
[13:58] <kgunn> for utopic
[13:58] <kgunn> sil2100: however, yes, we still break ABI every now and then tho we try not to
[13:58] <camako> what is FFe?
[13:58] <kgunn> sil2100: only if a bug fix ends up causing us to do so
[13:58] <kgunn> but we know all our clients....so...
[13:58] <kgunn> FFe = feature freeze exception
[13:59] <kgunn> camako: cause even tho we're thinking phone alot....there's utopic going on delivering to desktop
[13:59] <sil2100> kgunn: ok, so we'll not include mir in the FFe, and simply make sure anything that gets released is a bugfix
[13:59] <camako> I see
[13:59] <kgunn> camako: do you agree with what i said?....i can't see anything that's a "feature" landing before Oct ?
[13:59] <kgunn> everything is really just a bug fix
[14:00] <camako> there will be a 0.8.0 release coming (probably next week)...  which will/should reduce ABI breaks
[14:00] <kgunn> ...and we're not even cheating on definitions :)
[14:00] <kgunn> camako: i think even that is ok....we just can't break client
[14:01] <camako> yeah that's all under control... we have a deprecation path, rather than breakage
[14:01] <sil2100> Excellent
[16:04] <alf_> kgunn: @ lp bug 1371593, is the media hub part of the unity8 process, but something separate from it?
[16:10] <kgunn> alf_: seperate
[16:11] <kgunn> alf_: haven't spoke in a while...have a nice weekend btw
[16:12] <alf_> kgunn: (thanks, you too!) But it is loaded in the unity8 process, right (that's where I got the backtrace from)?
[16:12] <alf_> kgunn: So it's a library used by unity8?
[16:19] <kgunn> alf_: right....
[19:21] <kgunn> rsalveti: so where's the best place to look for quick devel-proposed image#/date/commits ?
[19:22] <kgunn> like a list
[19:22] <rsalveti> ogra_'s changes list?
[19:22] <rsalveti> like http://people.canonical.com/~ogra/touch-image-stats/222.changes
[19:22] <rsalveti> that will at least show what was new in every image
[20:45] <kgunn> rsalveti: sorry to bother...so was working on bisect, flashed image #235 devel-proposed....but
[20:45] <kgunn> need to manually install unity8-autopilot
[20:46] <kgunn> so...it needs to pull in a bunch of stuff
[20:46] <rsalveti> right
[20:46] <kgunn> but are those packages like blown away or something
[20:46] <kgunn> i'm getting
[20:46] <kgunn> Err http://ports.ubuntu.com/ubuntu-ports/ utopic/main python2.7 armhf 2.7.8-6ubuntu1
[20:46] <rsalveti> might need to run apt-get update first
[20:46] <kgunn> rsalveti: but...won't that take me to the latest ?
[20:47] <kgunn> i don't want the latest...i want #235 stuff
[20:47] <rsalveti> that will install the latest dependencies, yes
[20:47] <rsalveti> hopefully that will not cause any issue
[20:47] <kgunn> :-/
[20:47] <rsalveti> but we don't store the older packages
[20:47] <kgunn> well...asking for bisect ain't such a good idea then
[20:47] <kgunn> this sucks
[20:47] <kgunn> "hope"
[20:47] <rsalveti> if the broken package is the one already available *in* the image, then it can still work
[20:48] <rsalveti> I know it's not ideal
[20:48]  * kgunn prepares to chase tail, wild gooses and red herrings
[20:48] <kgunn> rsalveti: thanks for the info
[20:48] <rsalveti> np, good luck
[20:48] <rsalveti> this is painful
[20:49] <kgunn> lol
[20:49] <kgunn> tell me
[21:31] <tvoss> morphis, ping