[03:43] <pitti> Good morning
[04:19] <robert_ancell> RAOF, what provides xkeyboard-config.pc?
[04:19] <RAOF> xkb-data?
[04:21] <robert_ancell> RAOF, oh, its one of hose old ones in /usr/share
[04:21] <RAOF> Not so much one of those old ones as one of those arch-indep ones, yes :)
[04:23] <robert_ancell> RAOF, nah, most packages moved from /usr/share/pkgconfig to /usr/lib/pkgconfig well before arch independence
[05:15] <glatzor> hello to the early bird, pitti
[05:15] <glatzor> good morning
[05:15] <pitti> hey glatzor, guten Morgen
[05:48] <pitti> glatzor: nice announcement!
[05:51] <TheMuso> ~~~/c
[05:51] <pitti> TheMuso: bless you :)
[05:52] <TheMuso> ~heh
[05:52] <TheMuso> Yay for compiz and orca keybinding clashes/weirdness causing such issues in terminal windows...
[06:10] <didrocks> good morning
[06:12] <RAOF> Hey didrocks!
[06:13] <didrocks> hey RAOF, how are you?
[06:13] <RAOF> I'm pretty good.
[06:13] <RAOF> Back at boot camp-y-thing this morning, but that was long enough ago that I'm now invigorated rather than exhausted :)
[06:14] <RAOF> Hows about your fine self?
[06:15] <didrocks> I'm good as well, busy ubuntu week-end, so trying to get a non too mad week. I hope we can soon tackle this unity runtime crash when rebuilt on quantal gcc and boost
[06:19] <RAOF> Nothing says ?fun? like a build-chain related crash!
[06:24] <didrocks> RAOF: it clearly seems so :)
[07:07] <Sweetshark> moin
[07:47] <seb128> hey
[07:48] <didrocks> salut seb128, ça va?
[07:48] <pitti> hey seb128
[07:48] <didrocks> seb128: meeting report reminder!
[07:48] <seb128> didrocks, lut, nickel, et toi ?
[07:49] <seb128> didrocks, oh, thanks ;-)
[07:49] <didrocks> seb128: ça va bien :)
[07:49] <seb128> pitti, hey, wie gehts?
[07:49] <pitti> gut, danke!
[07:49]  * pitti just sent his first kernel patch to LKML and is now waiting for getting flamed
[07:55] <glatzor> morning mvo
[07:57] <glatzor> mvo: I cherry pick some fixes for the Python2 version of aptdaemon in lp:~aptdaemon-developers/aptdaemon/0.4x to upload it to Debian. This would also a good candidate for Precise
[08:02] <seb128> pitti, it wouldn't be the full kernel contributor experience if they just say thanks ;-)
[08:02] <seb128> hey glatzor
[08:02] <pitti> exactly!
[08:04] <mvo> glatzor: great, I can prepare a update
[08:06] <glatzor> morning seb128 !
[08:06] <glatzor> how are you
[08:07] <glatzor> ?
[08:07] <seb128> glatzor, good! how are you?
[08:07] <glatzor> seb128, fine. I am currently on vacations.
[08:07] <glatzor> mvo, perhaps some other bug fixes will go in
[08:09] <mvo> glatzor: cool, there is one I subscribed you too just some minutes ago that appears on errors.ubuntu.com, I can look for the bugnumber
[08:09] <glatzor> mvo, but could backport the fix of 659438 to oneiric? this would reduce my bug mail :)
[08:09] <glatzor> mvo, the fix should already by in the 0.4x branch :)
[08:10] <glatzor> mvo, LP# 981124
[08:10] <glatzor> mvo, I think that the GObject signal is a little picky about types
[08:14] <glatzor> mvo, to reproduce aptdaemon.client.AptTransaction("/org/debian/apt/123", None).emit("space-changed", 123123213213122132131321321123123)
[08:15] <alf_> didrocks: pong
[08:15] <mvo> glatzor: eh, but that is emited as int64, no? do we actually have sizes that exceed that?
[08:15] <Sweetshark> seb128: do we have a desktop meeting today? I carelessly created a wikipage for it already ....
[08:16] <glatzor> mvo, right, but the space-changed signal of client.AptTransaction only accepted a GObject.TYPE_INT
[08:16] <seb128> Sweetshark, hey, thanks for creating the wiki page, I'm about to send the reminder email ... we will have a meeting if anyone has a topic to discuss as usual
[08:16] <glatzor> mvo, there are also some broken third party packages which report really huge sizes :)
[08:17] <glatzor> mvo, I replaced all GObject.TYPE_INT by TYPE_INT64 where required
[08:20] <didrocks> alf_: hey, I think that ogra_ already went ahead, but FYI, your armhf patch doesn't compile with gcc 4.7
[08:20] <didrocks> (and -Werror)
[08:20] <BigWhale> Good Morning.
[08:20] <didrocks> alf_: on compiz :)
[08:20] <didrocks> hey BigWhale
[08:21] <alf_> didrocks: ok, I will contact ogra
[08:23] <mvo> glatzor: aha, I see, so this affects only older versions that use INT instead of INT64?
[08:23] <mvo> glatzor: but dosn't the bugreport show UInt64? or am I (still) missing something here .)?
[08:26] <BigWhale> didrocks, vive la France! :>
[08:26] <didrocks> BigWhale: c'est plutôt l'angleterre qui est en fête aujourd'hui, mais d'accord, vive la France ;)
[08:27] <BigWhale> Now... I need someone to replace existing keybinder with keybinder-3.0 :)
[08:27] <BigWhale> didrocks, now you overloaded my translation matrix ... :'(
[08:27] <didrocks> BigWhale: you knew it was going to be dangerous. Fortunately, google should have the answer ;)
[08:28] <BigWhale> That I know. :)
[08:28] <BigWhale> Oh, I know about UK being all happy and stuff, but since here are so many French people ...
[08:29] <BigWhale> and they are becoming more and more important ... :D
[08:29] <alf_> ogra_: Hi! Anything I can do to help with the compiz armhf build failure?
[08:29] <didrocks> heh ;)
[08:34] <glatzor> mvo, right. the value received value for the property from the daemon is a correct dbus.Int64()
[08:35] <glatzor> mvo, but the segfaults happen when emitting the space-changed signal in the client. and the signal type was set to INT and not to INT64. So if the dbus.Int64 value was higher than an INT it fails
[08:40] <ogra_> alf_, well, the GLES code seems to produce warnings with gcc-4.7 ... since upstream sets Werror by default that makes it fail on arm builds now
[08:42] <pitti> is rhythmbox working for anyone else in quantal today? it just hangs here without any window
[08:42] <pitti> apparently due to the U1 music store
[08:42] <seb128> pitti, ENOQUANTAL for me
[08:42] <seb128> i.e I'm still on precise so I can't test
[08:44] <alf_> ogra_: Hmm, do you have a link to any build logs? I am not on quantal, so no gcc 4.7 for me yet...
[08:45] <didrocks> pitti: was working 2 days ago, let me try again
[08:46] <didrocks> pitti: working and u1ms as well, let me see what happened since yesterday (didn't upgrade yet)
[08:47] <didrocks> ah, newer rythmbox
[08:47] <didrocks> let's see
[08:49] <ogra_> alf_, https://launchpad.net/ubuntu/+source/compiz/1:0.9.7.8-0ubuntu2/+build/3537962
[08:49] <didrocks> pitti: still working here after this morning upgrade
[08:50] <ogra_> alf_, use a chroot ;)
[08:52] <alf_> ogra_: Will probably do that, it seems that the fixes are trivial. Is updating the linaro-gles2-debianpatches branches good for you, or do you prefer some other way?
[08:53] <ogra_> alf_, well, i wont maintain any patch anymore in quantal (as discussed at UDS, the GLES bits should be merged before the next upload)
[08:54] <ogra_> so as long as it lands in the compiz code i'm fine :)
[08:55] <alf_> ogra_: ok, so you are saying there is no need to update the package now if the fixes are in the new codebase (they are by the way)?
[08:56] <ogra_> alf_, right, if there are fixes they should happen in the upstream tree
[08:56] <alf_> ogra_: ok, there is nothing to do here then :)
[08:57] <ogra_> are you sure the warnings dont happen with the upstream tree ?
[08:58] <glatzor> bye mvo pitti and seb128
[09:01] <alf_> ogra_: I am sure about that particular warning, but the code in compiz/gles2 (which will be merged into trunk) is changing fast so will probably need to recheck.
[09:02] <ogra_> that would be good :) -Werror is "the evil" during dev phases IMHO
[09:02] <ogra_> (it surely makes sense for releases, but during development ... not so much)
[09:15] <BigWhale> How do I list all the packages that depend on a certain package?
[09:16] <BigWhale> I want to know which packages depend on keybinder
[09:33] <geser> apt-cache rdepends (or reverse-depends from ubuntu-dev-tools)
[10:16] <chrisccoulson> hello peoples
[10:17] <ogra_> arent you supposed to still celebrate monarchy ?
[10:17] <ogra_> :)
[10:17] <chrisccoulson> lol
[10:17] <chrisccoulson> yes
[10:17] <chrisccoulson> too much to do though. no rest for the wicked ;)
[10:17] <ogra_> :)
[10:41]  * Sweetshark just watched http://www.youtube.com/watch?v=5twGTI_qw6o . need to lunch now ...
[12:28] <bcurtiswx> good morning
[12:40] <bcurtiswx> Congrats jbicha on MOTU :)
[12:40] <jbicha> bcurtiswx: good morning and thanks
[13:08] <seb128> chrisccoulson, hey, how is the queen party going? ;-)
[13:08] <chrisccoulson> seb128, what queen? ;)
[13:09] <desrt> anyone know how to use dejadup to restore only a specific subdirectory?
[13:09] <chrisccoulson> i've managed to completely avoid it all weekend :)
[13:09] <seb128> desrt, not sure, create the dir, right click on it in nautilus and pick the restore item?
[13:10] <desrt> hmm
[13:10] <desrt> timely.
[13:12] <seb128> desrt, what I described seems to be working (tried here)
[13:12] <desrt> will do, then
[13:12] <seb128> but mterry probably has a better way
[13:12]  * desrt just had a git incident
[13:12] <mterry> seb128, doubtful, what's up?  (hi)
[13:12] <seb128> mterry, hey
[13:12] <seb128> mterry,
 anyone know how to use dejadup to restore only a specific subdirectory?
 desrt, not sure, create the dir, right click on it in nautilus and pick the restore item?
 desrt, what I described seems to be working (tried here)
[13:13] <seb128> basically
[13:13] <mterry> desrt, you can do that, or you can click in the empty space of that directory and say "restore missing files"
[13:13] <desrt> nice...
[13:13] <seb128> mterry, will that not restore all the directories?
[13:14] <seb128> oh, you can pick what to restore
[13:14] <mterry> seb128, it will show you files that are in the backup but not in the directory and you can choose which to restore
[13:14] <seb128> I tried to be smart where not needed :p
[13:14] <seb128> deja-dup is smarter than me ;-)
[13:14] <mterry> seb128, desrt: those two context menus really need some discoverability
[13:15] <desrt> arghghgh vala bindings
[13:15] <seb128> chrisccoulson, so you just take the days off but don't celebrate the queen back in exchange? I see ;-)
[13:16] <chrisccoulson> seb128, yep :)
[13:27] <desrt> seb128: hey.  where's my glib SRU?
[13:27] <desrt> you promised :)
[13:30] <seb128> desrt, it got rejected, made me start a discussion with the TB about SRU rules
[13:30] <seb128> desrt, that's going to take a while
[13:30] <seb128> desrt, basically it's over the level of changes the current SRU team feels confident validating as a SRU
[13:31] <desrt> wtf
[13:31] <desrt> seb128: can you at least cherry-pick the non-NULL app ID thing?
[13:31] <seb128> desrt, yeah, I could cherry pick specific changes, I was still trying to get the update in but I need to get a TB approval for that
[13:31] <desrt> seb128: so here's what we do
[13:32] <desrt> cherry-pick all the patches, one or two at a time
[13:32] <seb128> but maybe doing cherry picks first while that's discussed is better
[13:32] <desrt> and then do the SRU saying "we carry all these patchs already anyway" :D
[13:32] <seb128> desrt, well I could do that, or I could get the new version in, they just want SRU tracking for each change basically
[13:33] <desrt> makes sense, actually
[13:33] <seb128> desrt, i.e if I want the new version in I need 15 bugs with testcase, regression potential, etc
[13:33] <desrt> seb128: is it the dbus stuff that's scaring them?
[13:33] <jbicha> desrt: don't encourage them! ;)
[13:33] <seb128> desrt, that was part of it, they judge incompetent to review a such diff
[13:33] <seb128> desrt, I did filter things out of them but they still don't feel like confident acking a such diff
[13:34] <seb128> desrt, https://lists.ubuntu.com/archives/technical-board/2012-June/001284.html
[13:34] <seb128> desrt, if you want the details, I tried to summarize
[13:34] <desrt> seb128: so the dbus stuff is really really unimportant
[13:34] <desrt> since it's all for windows
[13:34] <desrt> looking at the rest of the list there are some fixes for building on macos and/or with GNUstep installed
[13:34] <bcurtiswx> seb128, it's causing more trouble for GNOME packages than it needs. There may not be a bug report about an issue yet, so its like we have to wait for someone to report a bug about it or create a bug report about it to make sure all patches in a micro release have a bug report associated
[13:34] <desrt> neither of which impact your builders
[13:35] <desrt> also adding a bunch of testcases -- also no impact on you
[13:35] <desrt> GAppInfo: overwrite the DISPLAY only if it is set in the launch context looks interesting
[13:35] <desrt> as well gmain: block child sources when blocking the parent
[13:35] <desrt> GSocketControlMessage: Don't warn about unknown messages
[13:35] <seb128> desrt, but basically the bottom line is that slangasek thinks we should document every change that goes in a stable serie or get a TB approval to say we trust the source
[13:35] <desrt> and you probably really want Fix g_clear_object macro with C++ compilers
[13:35] <jbicha> we could just move release day back a few weeks to catch the 3.x.2 releases instead ;)
[13:36] <desrt> those are the only ones worth even thinking about
[13:36] <desrt> which means that if you can get a green light to cherry-pick those, i wouldn't even worry about the rest of the upgrade
[13:37] <seb128> desrt, I've a green line to cherry pick anything I want or to do the update if every commit is documented with an associated bug that get acked
[13:37] <seb128> desrt, but I don't want to go that path of having 35 bugs if there are 35 commits in the update
[13:37] <desrt> seb128: focus on those 5 ^^
[13:38] <desrt> (with my application_id being the 5th)
[13:38] <seb128> desrt, yeah, I can do that, I still want the rules changed
[13:38] <desrt> understood
[13:38] <seb128> but I can work on both sides at the same time
[13:38] <seb128> in fact that might be easier
[13:38] <desrt> the reason i ask is because we have our new developer tutorials being written right now
[13:38] <desrt> and they're using GtkApplication in a way that's currently not working on ubuntu
[13:38] <seb128> slangasek thinks I should get a MRE (micro release exception) for GNOME
[13:39] <desrt> maybe for GNOME + sanitycheck
[13:39] <bcurtiswx> seb128, were there issues with our more relaxed process for micro release updates? or was it other places and we just got caught in the wave of changes?
[13:39] <seb128> which I will do, but I still think the rules need to be changed and not only worked around for us by getting a pass for GNOME
[13:39] <desrt> some gnome microreleases are quite insane
[13:39] <desrt> i don't think it's appropriate to give blanket cover there without a check by someone like you
[13:39] <seb128> yeah, I'm arguing for "use best judgement, trust the maintainer who does the upload"
[13:40] <seb128> but still with the SRU team reviewing the diff and acking or nacking
[13:40] <seb128> I'm fine with them needing to be be convinced
[13:40] <desrt> ah
[13:40] <seb128> bcurtiswx, there was no "relaxed process"
[13:40] <desrt> it's just right now the answer is no, unless you have all the paperwork
[13:40] <seb128> yes
[13:40] <seb128> slangasek says the TB didn't get a mandate to apply their best judgement on an upload
[13:40] <seb128> they just got delegated powers to apply the rules
[13:41] <bcurtiswx> seb128, as long as I don't have to make 5 bug reports for a microrelease with 5 patches, I think I'll be OK with having to type a little bit more.. I also don't want to have to type a storybook for every SRU i want to make.
[13:41] <seb128> he also said pitti had extra powers by being a TB member so he could wave updates in if he though they made sense
[13:41] <seb128> well bottom line, there is an open discussion
[13:41] <desrt> seb128: the darker side of bureaucracy :)
[13:41] <seb128> let's see how that goes
[13:41] <pitti> not individually, just in a board decision
[13:42] <seb128> pitti, do you remember if GNOME ever had a MRE?
[13:42] <pitti> but really, I agree with seb128 that the SRU team should be able to decide that on a case by case basis
[13:42] <pitti> seb128: yes, we had one for hardy LTS I believe
[13:42] <seb128> pitti, I will apply for a permanent one I guess
[13:42] <seb128> or one for precise at least
[13:43] <pitti> but since the SRU team and slangasek just decided to make the process tighter, I'm not sure whether they would
[13:43] <seb128> slangasek says it's a TB call
[13:43] <pitti> but IMHO the problems are not new upstream versions, the problem is how to make sure they don't regress
[13:43] <pitti> which is a really tough one to do for things like glib
[13:43] <seb128> right
[13:43] <pitti> high-risk, high-benefit
[13:43] <seb128> I don't blame them for freaking out on the debdiff of this one
[13:44] <pitti> as opposed to many SRUs which are low-risk, low-benefit (the ones which got an explicit policy addition a few years back)
[13:44] <seb128> the point release added a dbus server implementation
[13:44] <seb128> which is only for win32 but still it makes the diff hard to read ;-)
[13:45] <bcurtiswx> how was the SRU team involved with GNOME SRU's before compared to how they want to be now? Is it a huge change, or just tightening up the security on it?
[13:47] <kenvandine> for gnome stuff i've always tried to do a micro-release upload if it fixed bugs that affected us as opposed to just pulling the patches
[13:47] <kenvandine> but if there wasn't fixes i was looking for, didn't both to go look for releases to upload
[13:53] <aquarius> when trying to upgrade, Update Manager says that I'll be installing packages from untrusted sources... and the list of packages from untrusted sources is everything that is planned to be upgraded. This worries me, because as far as I can tell I'm just getting them from the main archive. Can I verify that somehow? Might I have lost the signing key for the main archive?
[14:03] <kenvandine> aquarius, apt-key list
[14:03] <kenvandine> what does that return?
[14:04] <kenvandine> Ubuntu Archive Automatic Signing Key
[14:04] <kenvandine> ?
[14:04] <aquarius> kenvandine, ah, I haven't lost the key, then; that's in there
[14:06] <aquarius> kenvandine, to take an example, one thing that wants to be upgraded is winbind, which apt-cache policy says that I have from precise-security and wants to install from precise-updates
[14:06] <aquarius> so perhaps I do not have the key for precise-updates?
[14:07] <dobey> aquarius: are you using a mirror or the official archive?
[14:07] <kenvandine> ah
[14:07] <aquarius> dobey, the gb mirror
[14:07] <aquarius> I can't see a key in apt-key list about updates, but I don't know whether the updates are signed with the official key or their own key
[14:07] <dobey> aquarius: http://askubuntu.com/questions/110118/gpg-error-while-updating
[14:08] <aquarius> dobey, that's not the problem I have
[14:09] <aquarius> it's not throwing an *error* so much as trapping a condition it doesn't like
[14:09] <aquarius> heh
[14:09] <dobey> aquarius: if you run apt-get update again, does it complain about signature on the archive files?
[14:09] <aquarius> I have, however, just tried the apt-get clean and then apt-get update from the command line, and now update-manager works.
[14:09] <aquarius> how annoying. :)
[14:10] <aquarius> thanks, pal :)
[14:10] <dobey> heh
[14:17] <Sweetshark> pitti: did the tech board get the request for a LibreOffice MRE? I just got a reply about moderation so far ...
[14:17] <seb128> Sweetshark, it's on the public archive at least
[14:18] <Sweetshark> seb128: k, thanks
[14:36] <dobey> Sweetshark: i haven't heard any replies about my mre request for u1 either :-/
[15:23] <bcurtiswx> who's working on getting GTK 3.5.1 into Quantal ?
[15:24] <seb128> bcurtiswx, robert_ancell but it's blocking on Cimi to update unico
[15:24] <seb128> gtk changing some of the theming stuff and the theme segfaults
[15:25] <bcurtiswx> seb128, OK i need it for empathy 3.5.2 and also someone to sync telepathy-glib from debian
[15:25] <mhr3> seb128, gir and multiarch? no worky?
[15:26] <seb128> mhr3, no
[15:26] <seb128> mhr3, that has not been done yet
[15:26] <mhr3> seb128, patches on the horizon?
[15:26] <seb128> mhr3, if you are going to work on one maybe ;-)
[15:26] <mhr3> yea... no :)
[15:26] <mhr3> didrocks, fyi ^^
[15:26] <bcurtiswx> kenvandine, would you sync telepathy-glib from debian after A1 freeze for me?
[15:26] <kenvandine> sure
[15:27] <bcurtiswx> kenvandine, much thanks :)
[15:27] <didrocks> mhr3: yep, unmultiarching the gir file :)
[15:29] <seb128> didrocks, kenvandine, Sweetshark, Ursinha`, mterry, Laney, cyphermox_, tkamppeter: it's meeting time if anyone has a topic
[15:29] <cyphermox_> seb128: no topic for me.
[15:29] <didrocks> nothing for me
[15:29] <kenvandine> nothing from me...
[15:29] <Sweetshark> nothing here, spat it all to the wiki
[15:29] <kenvandine> but every week i forget that my calendar entry is off by an hour :)
[15:30] <seb128> hehe
[15:30] <mterry> nope
[15:31] <bcurtiswx> The official word on MRE for GNOME is still in the air/being talked about, right?
[15:31] <seb128> bcurtiswx, yes
[15:31] <bcurtiswx> seb128, ty
[15:31] <seb128> yw
[15:38] <desrt> aww
[15:38] <desrt> seb calls the meetings now :)
[15:43] <Sweetshark> desrt: yeah, isnt that cute?
[15:43] <Sweetshark> desrt: thankfully he is not doing it yet in french!
[15:43] <kenvandine> *yet* :-D
[15:43] <desrt> Sweetshark: i'll note that the nationality of our leader did not change...
[15:43] <cyphermox_> next week...
[15:43] <cyphermox_> seb128: ^
[15:44] <seb128> right!
[15:44] <Sweetshark> desrt: you are canadian, so your are half french anyway, right?
[15:44] <desrt> Sweetshark: my last name may have tipped you off to that, rather
[15:46] <cyphermox_> Sweetshark: outside of Quebec there are very few Canadians that actually speak french :)
[15:47] <Sweetshark> cyphermox_: But I bet you can start a flamewar anywhere in canada with that topic.
[15:47] <cyphermox_> Sweetshark: I don't think so
[15:47] <cyphermox_> Sweetshark: I'd be tempted to say instead that I wouldn't want to be caught speaking french is some parts of Canada :)
[17:07] <bcurtiswx> seb128, it seems cimi wont' work on the unico , unassigned themself from bug #1000545
[17:07] <ubot2`> Launchpad bug 1000545 in gtk+3.0 "Update to 3.5.2" [Wishlist,In progress] https://launchpad.net/bugs/1000545
[17:08] <seb128> bcurtiswx, that was sorted since, he got allocated work time to do it next week
[17:09] <bcurtiswx> seb128, OK great. I'll get a bug for empathy 3.5.2 up then so I dont' forget anything.
[17:11] <desrt> mterry: thanks again
[17:11] <mterry> desrt, worked? awesome
[17:11]  * kenvandine heads afk for a couple hours, bbiab
[17:11] <desrt> saved me at least a few hours of rewriting code :p
[17:57] <bcurtiswx> for debian sync is there any reason I should avoid experimental vs. unstable ?
[17:58] <ogra_> if you are confident the quality of the package you pull from experimental is good enough for a release ...
[17:59] <bcurtiswx> ogra_, great, thanks :)
[18:06] <desrt> lulz.  http://www.reddit.com/r/IAmA/comments/umavd/iama_ubuntu_community_manager_at_canonical/
[19:36] <seb128> micahg, hey, how is firefox 13 looking? did the final version got testing yet? when will it be uploaded?
[19:37] <micahg> seb128: will be released later this evening, in the middle of testing
[19:37] <seb128> micahg, great, no issue so far with testing I guess then?
[19:37] <micahg> looks fine though overall
[19:37] <seb128> good
[19:39] <stgraber> micahg: "will be released later this evening" <- but uploaded post-alpha1 right?
[19:39] <micahg> stgraber: quantal will skip the release :), 14b6 will be uploaded after the freeze
[19:41] <stgraber> micahg: k
[21:44] <bcurtiswx> good night all
[21:59] <micahg> stgraber: or it'll magically get uploaded to quantal-proposed :)
[23:19]  * RAOF takes it that there's no meeting today?
[23:28] <jasoncwarner_> RAOF sorry, had a kid meltdown...just back now.
[23:28] <jasoncwarner_> TheMuso RAOF bryceh (robert is sick) https://wiki.ubuntu.com/DesktopTeam/Meeting/2012-06-05
[23:29] <jasoncwarner_> if you have agenda items, please add them.
[23:29] <bryceh> none
[23:29] <jasoncwarner_> and make sure you fill in fun details for the week!
[23:29] <bryceh> done
[23:33] <jasoncwarner_> thanks, bryceh
[23:43] <TheMuso> None and done for me too.
[23:43]  * TheMuso crawls back under his blanket. :p
[23:43] <RAOF> :)
[23:45] <TheMuso> Its somewhat windy here...