[00:09] <TheMuso> chrisccoulson: Are the bugs ready to go SRU wise?
[01:02] <TheMuso> Woo! Natty is having its toolchain prepared.
[03:04] <hyperair> pitti: Bug #652855 now has a test case and rationale.
[03:04] <ubot2> Launchpad bug 652855 in libgpod (Ubuntu Maverick) (and 1 other project) "Please fakesync libgpod 0.7.95-1 from Debian experimental to maverick-updates (affects: 1) (heat: 10)" [Undecided,Triaged] https://launchpad.net/bugs/652855
[07:40] <pitti> Good morning
[07:40] <pitti> hyperair: ah, good
[07:40]  * pitti will do the morning SRU round then :)
[07:42] <hyperair> thanks =)
[08:29] <hyperair> pitti: just got the accepted mail. thanks!
[08:29] <pitti> no problem
[08:40] <didrocks> good morning
[08:41] <didrocks> pitti: Guten Morgen, thanks for the approval :)
[08:41] <pitti> hey didrocks, yw
[08:41] <pitti> I'll watch NEW
[08:41] <pitti> it should only be NEW on i386
[08:41] <didrocks> right
[08:42] <didrocks> how are you, btw?
[08:42] <pitti> I'm great, thanks!
[08:42]  * pitti crossed the "1000 pushups" mark last night :)
[08:43] <didrocks> oh really? I'll only cross the 900 today :-)
[08:44] <didrocks> congrats in any case :-)
[08:44]  * pitti updates the wiki
[08:44] <pitti> 900 is great!
[08:44] <pitti> I primarily keep the count on a sheet of paper on my wall
[08:44] <pitti> so I'm sloppy with wiki updates
[08:45] <didrocks> hehe :-) I'm keeping it into my head rather, as I try to do everytime the same number (30/30/30/15) each day
[08:45] <didrocks> adding more and more with the time :)
[08:46] <pitti> didrocks: n-l NEWed
[08:48] <didrocks> pitti: thank! I think I can have a test at it, will that enable pushing it to -updates sooner? (I think that most of people upgrading without ubuntu-netbook installed and having this issue will be this week)
[08:48] <pitti> didrocks: yes, if you can confirm that the debs from the archive still work, and perhaps test an upgrade in that scenario (chroot/pbuilder will do), we can push it out soon
[08:49] <didrocks> pitti: ok, I'm preparing a chroot, thanks :)
[08:51] <pitti> didrocks: it's not published yet
[08:52] <didrocks> pitti: I'll monitor the publisher or pick from launchpad directly. The time to prepare my lucid chroot will take time already :)
[09:40] <pitti> chrisccoulson: good morning
[09:40] <pitti> chrisccoulson: need a sponsor for bug 625793?
[09:40] <ubot2> Launchpad bug 625793 in gnome-settings-daemon (Ubuntu Maverick) (and 4 other projects) "Regression: Multiple Keyboard Layouts unusable: continuously changes layout + 100% CPU usage [updated] (affects: 266) (dups: 23) (heat: 1240)" [Critical,In progress] https://launchpad.net/bugs/625793
[09:44] <seb128> slomo, hey
[09:44] <seb128> did you try to build gtk3 from the debian svn?
[09:44] <slomo> sjoerd did, apparently it works :) i've installed his packages
[09:45] <slomo> but you need glib 2.27 :P
[09:45] <seb128> right, I've that installed in a ppa there
[09:45] <seb128> but the static build fails for me on some missing include
[09:45] <seb128> I've commented the static build for now
[09:46] <seb128> it's somewhat useless and wins a build which is nice when you rebuild several times gtk
[09:46] <seb128> chrisccoulson, I though you had upload rights for gsd
[09:46] <seb128> is it broken now?
[09:50] <slomo> seb128: no idea, ask sjoerd what he did ;)
[10:59] <seb128> https://edge.launchpad.net/~ubuntu-desktop/+archive/gnome3-builds
[10:59] <seb128> ^ there is a first gtk3 build there
[10:59] <seb128> or rather it's building
[10:59] <seb128> could be useful for those who want to start porting code
[11:01] <chrisccoulson> hi seb128
[11:01] <seb128> hey chrisccoulson
[11:01] <chrisccoulson> i don't think i've ever had upload rights for g-s-d
[11:01] <chrisccoulson> let me check ;)
[11:02] <seb128> hum ok
[11:02] <seb128> I'm wondering why, that seems pretty desktopish, are other derivative using g-s-d?
[11:03] <chrisccoulson> seb128 - oh, you're right, i do!
[11:03] <chrisccoulson> i never used to though
[11:03] <seb128> lol
[11:03] <chrisccoulson> ok, i'll upload my fix to maverick-proposed
[11:03] <seb128> thanks
[11:03] <seb128> that's a very noisy bug
[11:04] <didrocks> let me guess… the "switch layout" one? :)
[11:04] <chrisccoulson> didrocks, yeah, that's the one
[11:04] <didrocks> won \o/
[11:04] <chrisccoulson> it's pretty much a 1 liner to fix that, but i've also fixed a memory error too
[11:05] <didrocks> chrisccoulson: oh great! :)
[11:05] <seb128> chrisccoulson is made of awesome
[11:05] <chrisccoulson> :)
[11:06]  * didrocks hugs chrisccoulson
[11:06]  * chrisccoulson hugs didrocks
[11:06] <didrocks> great work on bug fixing :)
[11:31] <chrisccoulson> heh, firefox 4 is going to ship with Bing in the list of search engines
[11:31] <chrisccoulson> http://blog.mozilla.com/blog/2010/10/06/refreshing-the-firefox-search-bar/
[11:31] <seif_> mvo, mpt I want to wrtie the article to cal lfor developers to work on Software-Center + Zeitgeist integration
[11:32] <seif_> it will help new developers look into zeitgeist as well as s-c
[11:32] <seif_> therefore we need ideas
[11:32] <mpt> seif_, great
[11:32] <seif_> 3 things we would like ot have S-C d owiht Zeitgeist
[11:32] <seif_> the article will be on pgo and ubuntu
[11:32] <seif_> as well as omgubuntu
[11:35] <mvo> seif_: I'm about to leave for lunch, but I think that this is a good idea, the zeitgeist stuff opens up whole new capabilities
[11:36] <mvo> seif_: a brainstorm of ideas would be good too, I'm sure people will come up with lots of creative ideas
[11:36]  * mvo is really at lunch now and will read scrollback
[11:39] <seif_> mpt and mvo ok so i will call for brainstorming in comments
[11:39] <seif_> then we can choose the best 3 and actually provide mentorship for them
[11:40] <seif_> i am ready to provide mentroship
[11:40] <didrocks> seif_: just being curious, what's the 3 things you want to achieve on your personal list? :-)
[11:41] <Cimi> seb128: any good news on the gtk+ 3.0 front? ;) still thrilled :D
[11:43] <chrisccoulson> hi mvo. would it be possible to also get bug 656881 in to lucid?
[11:43] <ubot2> Launchpad bug 656881 in update-manager (Ubuntu Maverick) (and 1 other project) ""Install" button sometimes doesn't do anything (affects: 1) (heat: 6)" [Medium,Fix released] https://launchpad.net/bugs/656881
[12:08] <seb128> Cimi, https://edge.launchpad.net/~ubuntu-desktop/+archive/gnome3-builds
[12:08] <seb128> Cimi, it's only gtk so far, no theme or other libraries
[12:08] <Cimi> super cool
[12:09]  * Cimi let's broke my system with seb128's ppa
[12:09] <seb128> ;-)
[12:09] <Cimi> ops, break!
[12:09] <seb128> no way ;-)
[12:09] <seb128> btw it's not a gtk update it's a new version
[12:10] <Cimi> that might imply a completely breakage
[12:10] <Cimi> 2~
[12:10] <seb128> you will need to install libgtk3.0-0
[12:10] <Cimi> ?
[12:10] <Cimi> oh ok
[12:10] <seb128> no, it implies it will not touch your gtk2
[12:10] <seb128> so it should probably not break anything
[12:10] <Cimi> yeah
[12:15] <mvo> chrisccoulson: hey, I think so
[12:15] <mvo> chrisccoulson: but isn't that the policykit-1-gnome issue?
[12:15] <mvo> chrisccoulson: oh, sorry, this one
[12:16] <mvo> chrisccoulson: I can prepare a sru
[12:16] <chrisccoulson> mvo - excellent, thanks :)
[12:26] <chrisccoulson> seb128 - are you working on the SRU for pango, or do you want me to do that?
[12:26] <seb128> chrisccoulson, you can do it you want
[12:26] <chrisccoulson> cool, thanks. i'll do that one now
[12:26] <seb128> thank you
[12:26] <seb128> I was planning to work on some surs
[12:27] <seb128> srus
[12:27] <seb128> but I got sidetracked in starting gtk3 work
[12:27] <seb128> I want those to be available in a ppa this week to unblock other people
[12:31] <nessita> good morning everyone!
[12:32] <nessita> any idea why I can't propose for merge the a natty package for ussoc? https://code.launchpad.net/~nataliabidart/ubuntu/natty/ubuntu-sso-client/ubuntu-sso-client-1.1.1
[12:32] <nessita> seems like lp:ubuntu/ubuntu-sso-client doesn't exist... at least I couldn't branch it
[12:33] <chrisccoulson> seb128 - we should probably only upgrade to pango 1.28.2, rather than 1.28.3. The later version only has a single change which bumps the GIR version
[12:34] <seb128> chrisccoulson, right
[12:34] <chrisccoulson> i don't think we want this: http://git.gnome.org/browse/pango/commit/?h=1.28&id=b7dd5c0ca11672510f5ab870719a46b01c5a6df4
[12:34] <seb128> nessita, hey, how are you?
[12:34] <seb128> nessita, you should wait a bit, they are still sorting issues to open the new release serie, updates don't go through anyway yet
[12:35] <seb128> ok, another session restart and I should be done for a bit
[12:43]  * Cimi much work porting a gtk+ engine to gtk+3.0... easy but a lot :)
[12:44] <seb128> re
[12:44] <seb128> ok, that was not a great idea, but back to normal
[12:45] <seb128> hum, in fact not
[12:45] <seb128> be back in a bit
[12:49] <nessita> seb128: welcome back :-)
[12:49] <nessita> thanks for the info re the natty package
[12:49] <seb128> thanks
[12:49] <seb128> sorry I had some stability issue, better after a restart
[12:52] <nessita> guys, I'm getting a report for the ussoc package where usso failed to install due to:
[12:52] <nessita> /var/lib/dpkg/tmp.ci/preinst: 9: dpkg-maintscript-helper: not found
[12:52] <nessita> but the package has the following require:
[12:52] <nessita>  dpkg (>=1.15.7.2),
[12:52] <nessita> and in the report Dependencies.txt shows that dpkg version is 1.15.8.4ubuntu3
[12:52] <nessita> any idea why this failed? bug report is at https://bugs.launchpad.net/ubuntu/+source/ubuntu-sso-client/+bug/658765
[12:52] <ubot2> Launchpad bug 658765 in ubuntu-sso-client (Ubuntu) "package ubuntu-sso-client 1.0.3-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 127 (dup-of: 658768)" [Undecided,New]
[12:52] <ubot2> Launchpad bug 658768 in ubuntu-sso-client (Ubuntu) "package ubuntu-sso-client 1.0.3-0ubuntu1 failed to install/upgrade: subprocess new pre-installation script returned error exit status 127 (affects: 1) (dups: 1) (heat: 12)" [Undecided,New]
[12:53] <seb128> nessita, you need a predepends
[12:54] <Laney> raphael blogged about using maingscript-helper recently
[12:55] <nessita> Laney: have a link at hand? :-)
[12:55] <Laney> http://raphaelhertzog.com/2010/10/07/the-right-way-to-remove-an-obsolete-conffile-in-a-debian-package/
[12:56] <seb128> ups, ctrl-w doesn't do what I want
[12:56] <seb128> nessita, sorry I was say, you need to Pre-Depends on the new dpkg
[12:56] <seb128> since that once needs to be available when your preinst runs
[12:56] <nessita> seb128: right, I'll make a new package.
[12:56] <seb128> new dpkg -> the one which has the helper you use
[12:57] <nessita> yes, dpkg (>= 1.15.7.2)
[12:58] <didrocks> I'm always confused by the debian policy telling "When a package declaring a pre-dependency is about to be unpacked " where in fact, it's before the preinst
[13:13] <chrisccoulson> seb128 - ok, pango is pushed to bzr now
[13:13] <chrisccoulson> (i can't upload that one)(
[13:19] <nessita> seb128: so, I can't branch lp:ubuntu/maverick-proposed/ubuntu-sso-client either (I need to package a couple of SRUs). What am I missing?
[13:22] <bilalakhtar> seb128: maverick-proposed isn't open yet, you need to branch from maverick instead
[13:22] <bilalakhtar> sorry
[13:22] <bilalakhtar> nessita: ^^
[13:24] <nessita> bilalakhtar: I see. And how shall the procedure for a SRU follow?
[13:24] <nessita> I mean, if I don't branch -proposed :-)
[13:24] <bilalakhtar> nessita: When you will propose merge, you will need to propose to maverick only
[13:24] <bilalakhtar> the sponsor will upload to proposed
[13:24] <bilalakhtar> of course, you will need to specify proposed in changelog
[13:25] <nessita> bilalakhtar: I never specify the version on the changelog... I was told the sponsor sets the version accordingly
[13:26] <bilalakhtar> nessita: what version?
[13:26] <bilalakhtar> I mean
[13:26] <bilalakhtar> foo (0.1.2-3ubuntu2.1) maverick; urgency=low
[13:26] <bilalakhtar> will become
[13:26] <bilalakhtar> foo (0.1.2-3ubuntu2.1) maverick0proposed; urgency=low
[13:26] <bilalakhtar> *maverick-proposed
[13:31] <nessita> bilalakhtar: yeah, I don't set that, I leave the UNRELEASED string
[13:32] <bilalakhtar> nessita: yes you can
[13:33] <nessita> bilalakhtar: I know I can (I know how to use an editor! :-P), but seb128 told me in last platform sprint that I should leave that field to be changed by the sponsor
[13:34] <bilalakhtar> nessita: ah, if seb128 said that, leave it like that then
[13:34] <nessita> :-)
[13:34] <nessita> he's like a God or something, right?
[13:35] <cyphermox> bilalakhtar, this is likely because when working in a branch, the sponsor runs dch -r / debcommit -r, and the default commit message is "releasing <version>"; whereas dch -r automatically sets the release field to what it should be instead of UNRELEASED
[13:36] <cyphermox> well, not just the sponsor, but when one uploads a package :)
[13:36] <cyphermox> good morning btw :)
[13:54] <nessita> hello cyphermox
[13:54] <cyphermox> hi
[14:29] <nessita> sponsor wanted! https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.4/+merge/38221
[14:33] <Laney> nessita: changelog doesn't say anything about the pre-depends change
[14:33] <jcastro> seb128: let's ambush rickspencer3 today wrt. blueprints.
[14:33] <rickspencer3> jcastro, in point of fact, I wanted to ask you about that
[14:33] <nessita> Laney: nopes, it doesn't, you're right. I didn't realize I had to add it, I usually just add the changelog from the upstream project
[14:33] <jcastro> aha, perfect!
[14:34] <nessita> Laney: is on the bzr log, shall I add it the same?
[14:34] <Laney> nessita: And that bug you reference in the commit message is a dupe ;-)
[14:34] <rickspencer3> jcastro, where can I see some organized lists of the blueprints registred to date for Natty?
[14:34] <Laney> nessita: as changleogs are what users (and the SRU team) see, I'd say so
[14:34] <jcastro> https://blueprints.edge.launchpad.net/sprints/uds-n
[14:34] <nessita> Laney: I'll fix that, thanks!
[14:34] <jcastro> the link at the bottom takes you to the "pending" ones people are submitting
[14:34] <jcastro> which is the link you'll want to check regularly
[14:35] <rickspencer3> jcastro, can I see them listed by track?
[14:35] <rickspencer3> also, I'd like to be able to list them by team if possible
[14:35] <rickspencer3> jcastro, does stuff like this work: https://blueprints.edge.launchpad.net/sprints/uds-n?searchtext=*-foundations-*
[14:35] <rickspencer3> ?
[14:36] <jcastro> rickspencer3: clicking on the column sorts them by name, which is are the tracks
[14:36] <jcastro> yes, it does
[14:36] <pitti> hey rickspencer3, made it back in one piece?
[14:36] <rickspencer3> pitti, yes indeed
[14:36] <rickspencer3> slept until 4am, so not too much jet lag this time ;)
[14:37] <rickspencer3> I discovered this morning that my neighborhood is owned by cats at 4am
[14:37] <pitti> heh; they were screaming?
[14:37] <rickspencer3> no, just a bit shocked to see a person walking by
[14:37] <rickspencer3> some ran, some stretched out to be petted ;)
[14:38] <jcastro> my cat tried to kill me the other day, I never did manage to get him in the carrier to get to the vet.
[14:38]  * jcastro carries the scars
[14:38] <jcastro> rickspencer3: as long as you stick to the naming convention it should be fine
[14:38] <jcastro> rickspencer3: jono's mail to -devel explains it
[14:38] <jcastro> but basically
[14:38] <jcastro> $track-$team-n-$title
[14:41] <kenvandine> jcastro, we know who the boss is there :)
[14:41] <kenvandine> hey rickspencer3, welcome back!
[14:41] <nessita> Laney: fixes added and pushed!
[14:41] <Laney> cool
[14:41] <Laney> I can't actually sponsor it though :P
[14:42] <nessita> Laney: is ok, thanks for the pointers :-)
[14:42] <Laney> np
[14:42] <nessita> sponsor wanted! https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.4/+merge/38221
[14:49] <mpt> mvo, hi, for bug 449337
[14:49] <ubot2> Launchpad bug 449337 in software-center (Ubuntu) "does not support --addon-cd (regression from g-a-i) (affects: 2) (heat: 15)" [Medium,Confirmed] https://launchpad.net/bugs/449337
[14:50] <mpt> mvo, when the disc has been previously added, but is not inserted right now, how much would USC know about the packages on it?
[14:51] <mvo> mpt: the packages are stored by apt, it knows what packages are on what disk
[14:51] <mvo> mpt: meta-data is more problematic as this is currently not considered by apt at all
[14:52] <mpt> mvo, does it know all their descriptions, icons?
[14:52] <mpt> hm
[14:52] <mpt> So it doesn't even know their titles?
[14:52] <mvo> mpt: we should add something for that to apt, that will do no harm (a meta-data fetcher)
[14:52] <mvo> mpt: correct, it will know only about packages
[14:52] <mpt> ok
[14:52] <mvo> mpt: unless the CD is inserted
[14:53] <mvo> mpt: we could make that a requirement for now, I'm not sure what the best UI for this is
[14:53] <mvo> mpt: the trouble with remembering is that users tend to misplace cds
[14:53] <mpt> I'm working on the interface design now
[14:53] <mpt> A way to add a CD, and a way to remove it
[14:53] <mvo> and for usb sticks its even worse, people erase them etc
[14:54] <mvo> so maybe the answer is to not remember those packages permanently
[14:54] <mpt> And three versions of the main pane: (1) it's inserted but not added, (2) it's added but not currently inserted, and (3) it's both added and inserted.
[14:54] <tedg> mterry, Hey, so the gtk3 merge requests from a while back, are those the "blessed way" of doing GTK 3 now?
[14:54] <tedg> mterry, I know it's changed a couple of times and I'm honest not sure what's the right way anymore :)
[14:54] <mterry> tedg, what, the --with-gtk=2/3?
[14:55] <mterry> tedg, AFAIK there is no super-official way to do it.  The list came down on the side of an argument, not a flag like --with-gtk3.  As for the format of the argument 2 vs 2.0 or whether to use enable or with, I don't think there was concensus
[14:55] <tedg> mterry, Yeah, and the building a new lib name (i.e. libindicator3)
[14:56] <mterry> tedg, as for a new lib name, you need *some* new lib name for parallel installability.  I believe libunique did that (libunique3)
[14:56] <mterry> tedg, not sure about other examples.  There hasn't been much official guidance for the transition for libraries
[14:57] <tedg> mterry, Okay, and so then what should the pkgconfig file point to, or should there be two?
[14:57] <mterry> tedg, there needs to be two for parallel installability
[14:57] <seb128> hey mterry
[14:57] <mterry> seb128, heyo
[14:58] <seb128> mterry, https://edge.launchpad.net/~ubuntu-desktop/+archive/gnome3-builds
[14:58] <mterry> seb128, ^^ guidance?
[14:58] <tedg> mterry, Hmm, yeah.  But it means that every other package has to upgrade manually...
[14:58] <seb128> gtk3 first build
[14:58] <mterry> seb128, ah nice
[14:58] <mterry> tedg, yeah, as they do for gtk3 itself
[14:58] <seb128> mterry, guidance on what topic exactly?
[14:58] <seb128> you need to rename the pkgconfig yes
[14:59] <mterry> seb128, library naming for the transition to gtk3 and common configure arguments for it
[15:01] <seb128> not sure there is an official way, any configure flag naming will do
[15:01] <seb128> --with-gtk=... works fine
[15:02] <mterry> tedg, you want it to be manual for consumers because getting the wrong version of gtk is disasterous for them, so you don't want them to accidentally upgrade a library they use to gtk3
[15:03] <tedg> mterry, Yeah, I'm just thinking of libindicator, which really isn't something we want parallel installable.... it's basically just a connector between the indicators and unity/applet.
[15:05] <mterry> tedg, well, then you need a flag day for all reverse-depends
[15:05] <seb128> would it work to load indicators using different gtk versions?
[15:05] <mterry> tedg, in which you port all of them to gtk3
[15:05] <mterry> seb128, in the same process, no
[15:05] <seb128> ok, so you sort of need this all reverse-depends upload
[15:06] <desrt> can someone explain ia32-libs to me?
[15:06] <mterry> seb128, well, the panel can just not load old gtk2 indicators without forcing a mass port (lost functionality, but no FTBFS)
[15:06] <mterry> seb128, not much of a distinction, I suppose because of how important indicators are
[15:07] <seb128> right
[15:07] <tedg> So we'll need to bump the indicator directory as well.
[15:07] <mterry> seb128, tedg: but there needs to be a way for gtk2 apps to talk to the panel
[15:07] <tedg> mterry, ?  Why?
[15:08] <mterry> tedg, well, for universe and things that aren't porting right away.  For example, do you want to force banshee to port to gtk3 to continue showing in the panel?
[15:08] <desrt> is the indicator stuff straight dbus or is there a panel-side .so?
[15:09] <tedg> mterry, Ah, no.  You're confusing libindicator and libappindicator.  Applications use the second one, but only stuff we maintain use the first.  So we do want || install for the second, but not the first.
[15:09] <tedg> desrt, Panel side so
[15:09] <desrt> definitely separate install dir, then
[15:09] <tedg> desrt, For some of the custom menu items, etc.
[15:10] <desrt> dlopen()ing a gtk2-linked .so into a gtk3 app tends to be quite fatal
[15:10] <mterry> tedg, so only reverse depends are indicators themselves?  I see.  That's not so bad for a flag day
[15:11] <kenvandine> sigh.... today's kernel update breaks suspend on my laptop
[15:11]  * kenvandine looks for bug reports
[15:11] <tedg> Does libgtk2-dev and libgtk3-dev conflict so that you can't accidentally have both?
[15:11] <desrt> no.  they are fully parallel-installable
[15:12] <tedg> Doesn't that seem like a bad idea?
[15:12] <desrt>  /usr/share/gtk-2.0/ vs /usr/share/gtk-3.0/
[15:12] <desrt> well, they have different pkgconfig name...
[15:12] <desrt> it's as if they're two completely separate unrelated libraries
[15:12] <seb128> tedg, no they don't
[15:12] <desrt> except that they violently explode if you try to use both (by virtue of using each others namespace)
[15:12] <tedg> That if you use at the same time they blow up :)
[15:13] <seb128> tedg, not sure what is your issue with that?
[15:13] <desrt> we actually have a check in gtk_init() that if it sees symbols that it knows belog to "the other" gtk, it aborts straight away
[15:13] <tedg> I guess there's no way to say "can be installed at the same time" but not "can't be build-deps at the same time."
[15:13] <tedg> Because installed isn't really an issue, but build-deps is.
[15:14] <seb128> well it's up to the maintainer to not screw
[15:14] <desrt> tedg: i could imagine a single package that wants to install a gtk2 and gtk3 version of itself depending on both gtk2 and gtk3
[15:14] <seb128> well any lib that do a build for each
[15:14] <tedg> Ah, yeah.
[15:15] <seb128> ie 2 builds from the same source, one gtk2 and one gtk3 one
[15:15]  * tedg doesn't trust these "maintainer" people ;)
[15:15] <seb128> ;-)
[15:15] <desrt> here's a fun example:
[15:15] <desrt> it might make sense to port banshee's app indicator .so to link against gtk3
[15:16] <desrt> and leave banshee as gtk2 (since it's a lot more work)
[15:16] <seb128> out of the fact that appindicators are not different .so
[15:16] <seb128> they are a libappindicator api used in the application
[15:16] <seb128> the same way that the notification area is used
[15:17] <tedg> Yeah, appindicators are all dbus, so we're good there.
[15:17] <desrt> ah.  right.
[15:17] <seb128> hum maybe not in the banshee case, they probably did it as a .so indeed
[15:17] <desrt> don't they have that music-player-over-dbus spec they use?
[15:17] <seb128> but banshee gtk2 probably can't load a gtk3 .so
[15:17]  * tedg is tired of thinking about all this.  Let's just never upgrade library versions, ever, okay? :)
[15:17] <seb128> lol
[15:18] <tedg> desrt, Yes, MPRIS.
[15:18] <desrt> tedg: expect it again in 3-5 years
[15:18] <seb128> right, the banshee case is a non issue now
[15:18] <seb128> we stopped using an appindicator for music players
[15:18] <seb128> we just use mpris over dbus
[15:23] <mclasen> desrt: its a lot more painful that it has to be, due to our unholy mess of dependencies, and modules mixing apps, services and libraries...
[15:24]  * desrt feels a little heat from that statement
[15:25] <nessita> kenvandine: hello! could sponsor an upload into maverick-proposed? https://code.launchpad.net/~nataliabidart/ubuntu/maverick/ubuntu-sso-client/ubuntu-sso-client-1.0.4/+merge/38221
[15:25] <nessita> could you*
[15:25] <kenvandine> nessita, sure
[15:26] <nessita> kenvandine: I couldn't branch maverick-proposed nor merge propose against, so I use maverick as per bilalakhtar's advice
[15:27] <kenvandine> ok
[15:38] <Sarvatt> darn, seeing minecraft on here made me think it was actually available for purchase in the software center - http://www.ubuntu.com/desktop/features :)
[15:41] <Laney> that's a bit weird if it isn't
[15:56] <pitti> baptistemm: bonjour! would you like to merge bluez with debian unstable?
[15:57] <kklimonda> Sarvatt: it would be a great idea
[16:01] <jcastro> seb128: I see karl nailed that 100% CPU bug?
[16:02] <seb128> jcastro, no, chrisccoulson did
[16:02] <jcastro> woo!
[16:02] <chrisccoulson> :)
[16:02] <jcastro> seb128: do you have more bugs for him?
[16:02] <seb128> jcastro, wondering what karl has been doing though for a week
[16:02] <seb128> is he still working?
[16:02] <jcastro> I thought he was working with you?
[16:02] <jcastro> that was my impression
[16:03] <seb128> it seems it has spent one week on this g-s-d bug chrisccoulson fixed so not sure what's up there
[16:05] <chrisccoulson> nice, i just ported my first extension to ff-4 \o/
[16:06] <chrisccoulson> and all without a debugger, seeing as JS debugging is currently broken
[16:18] <Riddell> seb128: could you update your weekly meeting reminder template to include the meeting time?  that way I wouldn't have to look it up every week :)
[16:18] <seb128> Riddell, it's a wiki, feel free to do it ;-)
[16:18] <seb128> Riddell, https://wiki.ubuntu.com/DesktopTeam/MeetingTemplate
[16:26] <cyphermox_> brb
[16:53] <Cimi> seb128: porting an engine to gtk+ 3.0 is much much much longer than I expected :)
[17:30] <seb128> hey there
[17:30] <cyphermox_> hey
[17:30]  * kenvandine waves
[17:30] <Riddell> hi
[17:30] <seb128> chrisccoulson, didrocks, tremolux, kenvandine, Riddell, pitti, mterry, cyphermox, tkamppeter: hey
[17:30]  * pitti waves
[17:30] <chrisccoulson> \o/
[17:30] <seb128> starts being challenging to forget nobody
[17:30] <seb128> how is everybody?
[17:31]  * mterry says great!
[17:31] <kenvandine> great!
[17:31] <seb128> congratulation to all on a a great maverick release
[17:31] <tremolux> hey!
[17:31] <didrocks> great!
[17:31] <seb128> but as you know it never stays quiet long there
[17:32] <seb128> ;-)
[17:32] <seb128> ok, let's get started
[17:32] <seb128> https://wiki.ubuntu.com/DesktopTeam/Meeting/2010-10-12
[17:32]  * pitti ♥ natty
[17:32] <seb128> I guess there is no much updates
[17:32] <seb128> we careful to typos btw
[17:32] <pitti> seb128: ?
[17:32] <seb128> naty is nessita, natty is the new ubuntu
[17:33] <seb128> but she's not there so it's not fun
[17:33] <kenvandine> haha
[17:33] <seb128> anyway let's get started
[17:33] <pitti> seb128: yes, and Netti is my wife :)
[17:33] <seb128> pitti, ;-)
[17:33] <didrocks> seb128: try again next week? :-)
[17:33] <pitti> (pronounced the same)
[17:33] <seb128> didrocks, :p
[17:33] <kenvandine> pitti, oh confusing :)
[17:33] <seb128> I guess status updates will be short
[17:33] <pitti> 1. release 2. sleep 3. merge
[17:33] <tkamppeter> hi
[17:33] <seb128> maybe just do a summary of the maverick feedback
[17:33] <kenvandine> hehe :)
[17:34] <seb128> if you expect some sru or not
[17:34] <seb128> ok
[17:34] <seb128> kenvandine, hey
[17:34] <pitti> from an SRU POV I can report that things are much quieter than usual
[17:34] <seb128> partner update? ;-)
[17:34] <kenvandine> sure... natty planning and a couple SRUs
[17:34] <kenvandine> nothing particular to report, yet
[17:34] <kenvandine> everyone is preparing for UDS
[17:34] <seb128> pitti, yeah, that's wanted
[17:34] <pitti> I guess partly because maverick was a solid release, and also because we've been quite liberal with post-RC updates
[17:35] <seb128> next cycle will be busy and the lts was only one cycle away
[17:35] <pitti> which wasn't without risk, but has gone well
[17:35] <seb128> I for one decided to move full speed to the new version early
[17:35] <seif_> mvo, and mpt so back to the issue at hand
[17:35] <seb128> seif_, hey, we are in a meeting at the moment can you wait it's over ?
[17:35] <pitti> seif_: sorry, we currently (ab)use the channel for our meeting
[17:35] <seif_> what 3 features would u like to see in S-C that are not fully implemented yet
[17:35] <pitti> seif_: perhaps we can temporarily redirect you to #u-devel?
[17:35] <kenvandine> i am very pleased and surprised how smooth things went considering the amount of late changes
[17:36] <seb128> yeah
[17:36] <kenvandine> whew :)
[17:36] <seb128> thanks kenvandine, let's keep moving with status updates
[17:36] <seb128> didrocks, hey, anything you want to mention?
[17:36] <seb128> (will be easier asked this way)
[17:36] <seb128> no need to bother doing a status update if there is nothing to say ;-)
[17:36] <didrocks> not a lot to say as of today. UNE 10.10 kindly released.
[17:36] <didrocks> Of course, we now got, some bugs and try to catch up with them.
[17:36] <didrocks> Planning on what to discuss at UDS is now in order.
[17:37] <didrocks> short :)
[17:37] <seb128> thanks didrocks
[17:37] <seb128> tremolux, hey, anything you want to mention?
[17:37] <seb128> as a status update I mean
[17:38] <tremolux> sure  :)
[17:38] <tremolux> * Software Center 3.0.4 released with 10.10
[17:38] <tremolux> * Ratings and Reviews has been kicked off and is shaping up to be the first new major feature for Software Center in Natty
[17:38] <tremolux> * We have been merging some very cool new Zeitgeist integration features from Seif Lofty
[17:38] <tremolux> * Planning for Natty cycle in progress
[17:38] <tremolux> just some stuff we are getting going with
[17:38] <seb128> great
[17:38] <tremolux> but of course it's all about 10.10 today  :D
[17:38] <seb128> great release, with rating and reviews landing I guess s-c will be even happier ;-)
[17:39] <seb128> let's see what else we get next cycle
[17:39] <seb128> tremolux, thanks
[17:39] <seb128> no pedro, so no bug status update I guess
[17:39] <tremolux> you're welcome  :)
[17:39]  * Riddell coughs politely
[17:39] <seb128> ups
[17:39] <kenvandine> :)
[17:39] <seb128> Riddell, hey ;-)
[17:39] <seb128> sorry I somewhat forgot about the kubuntu update
[17:39] <Riddell>  * 10.10 is out!  no major problems so far
[17:39] <Riddell>  * SRUs for kdelibs, choqok, qoauth, bluedevil in progress
[17:39] <Riddell>  * specs to be registered today, just need to sort out the ideas at https://wiki.kubuntu.org/Kubuntu/UDSNatty
[17:40] <seb128> how did maverick go for you? ;-)
[17:40] <Riddell> maverick is all good, X and compositing was our biggest trouble area but that's upstream's fault
[17:40] <seb128> ok, great, I see you are well organized as usual ;-)
[17:40] <Riddell> also I got down from 4000 to <100 unread e-mails today :)
[17:41] <seb128> impressive ;-)
[17:41] <seb128> thanks Riddell
[17:41] <seb128> ok, so no release status from me today
[17:41] <seb128> but new topic: blueprints
[17:42] <seb128> is everybody clear on what to do there?
[17:42] <seb128> just give some thinking to what you would like to get done next cycle and register blueprints for those
[17:42] <seb128> jcastro wrote an email to the list "Naming sessions in Launchpad for UDS"
[17:42] <seb128> read it if you didn't
[17:43] <seb128> the summary is that the naming to use is "$trackname-$team-n-$title"
[17:43] <seb128> jcastro, ^ correct?
[17:43] <seb128> http://summit.ubuntu.com/uds-n/
[17:43] <jcastro> yes
[17:43] <jcastro> https://lists.ubuntu.com/archives/ubuntu-devel/2010-October/031779.html
[17:43] <seb128> has a summary of the tracks
[17:43] <kenvandine> make sure you read that mail too, the track names are different :)
[17:44] <pitti> and please target them at natty now
[17:44] <pitti> so that they'll appear on the WI tracker
[17:44] <seb128> https://blueprints.edge.launchpad.net/sprints/uds-n
[17:44] <seb128> your specs should show up there
[17:44] <seb128> the WI tracker which spams my inbox every hour since yesterday ;-)
[17:44] <pitti> how can so many specs be approved already??
[17:45] <pitti> ah, apparently carried over from m
[17:45] <seb128> right
[17:45] <seb128> be aware that next cycle will be busy out of specs
[17:45] <seb128> we will have quite some stack updates, ie gtk3
[17:45] <didrocks> seb128: it's not in the list until something approved the uds-n target, right?
[17:46] <seb128> so we will time to handle bugs to that and port code
[17:46] <pitti> didrocks: yes
[17:46] <pitti> seb128: that sounds great
[17:46] <seb128> so don't over-sign for work
[17:46] <didrocks> someone*
[17:46] <seb128> didrocks, correct
[17:46] <pitti> I just have one blueprint for now, which will be a huge one; so I don't actually plan to do more
[17:46] <seb128> ok
[17:46] <seb128> is anybody having questions on blueprints registration?
[17:47] <seb128> or anything to add?
[17:47] <kenvandine> nope
[17:47] <chrisccoulson> i've got some which need approving i think
[17:47] <chrisccoulson> they don't appear on that list
[17:48] <seb128> chrisccoulson, just tell me which ones after the meeting and I will see if I can approve those
[17:48] <chrisccoulson> thanks
[17:48] <seb128> or we will track jcastro to get that sorted if that doesn't work
[17:48] <seb128> ok, seems there is nothing to add
[17:48] <seb128> great work on maverick everybody
[17:48] <seb128> let's get ready for UDS now ;-)
[17:49] <seb128> end of meeting
[17:49] <seb128> ;-)
[17:49] <didrocks> thanks everyone :)
[17:49] <pitti> and if anyone feels bored, https://merges.ubuntu.com/main.html has plenty of stuff :)
[17:50] <seb128> pitti, do we know when natty opens?
[17:50] <pitti> seb128: I guess another day or two (still need a kernel upload), but please don't let that stop you
[17:50] <pitti> unapproved is waiting
[17:50] <seb128> speaking of getting borred
[17:50] <seb128> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=gnome3-gtk3
[17:50] <seb128> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=gnome3-gsettings
[17:51] <seb128> https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=gnome3-gtkbuilder
[17:51] <seb128> if you want to work on some of those
[17:51] <seb128> https://edge.launchpad.net/~ubuntu-desktop/+archive/gnome3-builds has a first gtk3 build
[17:51] <seb128> pitti, btw can you stop builds? it seems the amd64 build it going over and over
[17:51] <seb128> the i386 built it 19 minutes but amd64 is building for half a day
[17:51] <pitti> seb128: I can't, no; that requires lamont or elmo
[17:53] <bcurtiswx_> seems gnomes moving over to 3.0 finally, im assimung we will too?
[17:55] <chrisccoulson> m'eh, debugging firefox extensions without a debugger is pretty difficult :/
[17:59] <seb128> bcurtiswx_, we will see where we get
[17:59] <seb128> we plan to get there though
[17:59] <bcurtiswx_> Good :)
[17:59] <seb128> but let's update the stack first and see how much we can port of update without impacting the desktop stability
[17:59] <seb128> we will do incremental updates
[17:59] <Riddell> tremolux: where are the docs about how apps get into extras.ubuntu.com ?
[18:01] <tremolux> Riddell: here's the process:  https://wiki.ubuntu.com/PostReleaseApps/Process
[18:02] <Riddell> thanks
[18:04] <tremolux> Riddell: you're welcome  :)
[18:23] <dobey> pitti: still around?
[18:23] <pitti> dobey: o/
[18:23] <dobey> pitti: hi! what do you mean by "it needs to be built with -v<version in lucid/-updates/-security>" ?
[18:23] <dobey> pitti: i don't see a -v option to debuild or dpkg-buildpackage?
[18:23] <pitti> dobey: that's a dpkg-buildpackage option
[18:24] <dobey> is it undocumented?
[18:24] <pitti> dobey: it's passed to dpkg-genchanges
[18:24] <pitti> dobey: no, dpkg-buildpackage manpage says it's a dpkg-genchanges option
[18:24] <pitti> dobey: it causes all changelog records since the specified version to appear in the generated .changes file
[18:24] <pitti> dobey: but that's not really relevant for couchdb, we can't just take a maverick backport for lucid and karmic
[18:24] <dobey> ah ok
[18:25] <seb128> chrisccoulson, so those blueprints?
[18:25] <pitti> dobey: usually we use that option if you do two SRUs in a row without the first one going to -updats
[18:25] <dobey> right
[18:25] <dobey> i was just looking for docs on that option, as i didn't really understand the comment fully
[18:25] <chrisccoulson> seb128 - https://blueprints.edge.launchpad.net/ubuntu/+spec/other-desktop-n-thunderbird-messaging-indicator
[18:25] <chrisccoulson> https://blueprints.edge.launchpad.net/ubuntu/+spec/other-desktop-n-firefox-4
[18:26] <chrisccoulson> and https://blueprints.edge.launchpad.net/ubuntu/+spec/other-desktop-n-firefox-pgo-builds
[18:26] <seb128> chrisccoulson, ok, I can approve those
[18:26] <chrisccoulson> excellent, thanks
[18:26] <seb128> chrisccoulson, you didn't propose https://blueprints.edge.launchpad.net/ubuntu/+spec/other-desktop-n-firefox-pgo-builds for the uds it seems, should I do it?
[18:27] <chrisccoulson> seb128 - we probably don't need to discuss that at UDS, but it should still appear on our list i think
[18:28] <seb128> chrisccoulson, ok, so let's set a serie and not a sprint
[18:28] <chrisccoulson> thanks
[18:28] <seb128> yw
[18:28] <dobey> pitti: thanks
[18:28] <seb128> chrisccoulson, what is pgo btw? I guess not people.gnome.org ;-)
[18:28] <pitti> dobey: you're welcome
[18:29] <chrisccoulson> seb128 - profile guided optimization
[18:29] <chrisccoulson> it will hopefully make things faster ;)
[18:30] <seb128> great ;-)
[18:31] <chrisccoulson> if i can get it to build. so far, the profiling step hangs in the PPA builders, and i'm not sure how to debug that really :/
[18:32] <andreasn> jcastro, ping
[18:33] <jcastro> andreasn: pong
[18:33] <devildante> mvo: ping
[18:34] <andreasn> jcastro, First. Congrats on the 10.10 release. I'm coming all week for UDS, but David and Bryan can only stay a couple of days and are trying to plan their stay
[18:34] <jcastro> oh awesome, what do you need?
[18:34] <andreasn> jcastro, do you have any estimate when during the week the Firefox and Thunderbird discussions will be
[18:34] <andreasn> ?
[18:35] <jcastro> yes, so here's how you do that
[18:35] <andreasn> I couldn't find anything in the schedule
[18:35] <jcastro> when they register in launchpad
[18:35] <jcastro> make sure they put in there what days they will be attending
[18:35] <andreasn> oh, so it's kind of up to them?
[18:35] <jcastro> then we can mark them as "Essential" for the spec
[18:35] <jcastro> then the session can only be scheduled when all three of you are available
[18:36] <andreasn> ok, I see
[18:36] <jcastro> so yes, based on your availablity
[18:36] <jcastro> https://launchpad.net/sprints/uds-n <-- when they register here
[18:36] <jcastro> that's the link that they need to make sure they add themselves to
[18:39] <jcastro> andreasn: they'll need to mark themselves as essential to every tbird spec: https://blueprints.edge.launchpad.net/ubuntu/+spec/other-desktop-n-thunderbird-messaging-indicator
[18:39] <jcastro> like how micahg did there ^^^. It's a checkbox when they subscribe as to wether be essential or not.
[18:39]  * micahg thought he added all the Mozilla people to our specs
[18:40] <jcastro> I think you're getting 2 more!
[18:40] <micahg> \o/
[18:41] <andreasn> jcastro, ok, will catch bryan in 30 mins or so
[18:41]  * Cimi is happy to announce murrine is not ported to gtk+ 3.0 :-)
[18:41] <Cimi> *now
[18:41] <Cimi> not not :P
[18:42] <andreasn> Cimi, heh :)
[18:42] <andreasn> Cimi, but great!
[18:42] <andreasn> micahg, what mozilla specs are there?
[18:43] <jcastro> andreasn: keep checking in, the design specs should be landing today/tomorrow if you guys are interested in those
[18:43] <andreasn> micahg, I'm on other-desktop-n-thunderbird-messaging-indicator, other-desktop-n-firefox-4 and appselection-n-thunderbird-on-ub...
[18:43] <micahg> andreasn: https://blueprints.launchpad.net/ubuntu/+spec/other-desktop-n-firefox-4
[18:44] <micahg> andreasn: there will be one more general team spec that I'll add later this week, I'll add everyone essential from the firefox-4 spec to it
[18:44] <andreasn> ok, sounds good!
[18:45] <seb128> didrocks, hey
[18:45] <didrocks> hey seb128
[18:45] <seb128> didrocks, I just assigned you 2 evolution bugs
[18:46] <seb128> didrocks, basically 2 upstream commits to sru if you can, the reported has pointed to upstream bugs and they got fixed in 2.32
[18:46] <didrocks> that's not kind of you :)
[18:46] <didrocks> that's better then :)
[18:46] <seb128> ;-)
[18:46] <didrocks> seb128: ok, will have a look tomorrow morning :)
[18:46] <didrocks> thanks!
[18:46] <didrocks> I'll try to work on a third in a round
[18:46] <seb128> didrocks, if you want to reply on the why we don't ship the current version tell him that the 2.312 schedule was decided late and we didn't have ressources to do the update but he's welcome to contribute
[18:46] <didrocks> (the "mark all as read"
[18:47] <seb128> didrocks, ok, thanks!
[18:47] <didrocks> seb128: yeah, I've already made similar statement in #evolution
[18:47] <didrocks> seb128: thanks :)
[18:49] <seb128> didrocks, btw did you see robert_ancell connected this week?
[18:53] <didrocks> seb128: no, I didn't pay attention (at least, he didn't discuss when I was connected)
[18:53] <didrocks> seb128: but he made an SRU, doesn't he?
[18:53] <seb128> right
[18:53] <seb128> I just wondered if somebody talked to him
[18:53] <didrocks> no, and as I ignore join/quit…
[18:59] <chrisccoulson> yeah, i spoke to him briefly last night
[18:59] <seb128> ok
[18:59] <seb128> I will write him an email
[18:59] <seb128> just to let him updated on what we are doing
[18:59] <seb128> he was away for some weeks
[19:00] <didrocks> good evening guys!
[19:01] <Cimi> seb128: I could make a gtk3-engines-murrine from git maybe
[19:02] <seb128> Cimi, I'm about to go for dinner but I will tomorrow
[19:02] <seb128> Cimi, thanks for working on that btw ;-)
[19:03]  * Cimi going to the gym club, instead :)
[19:51] <devildante> YokoZar: around?
[19:51] <YokoZar> devildante: aye
[19:51] <devildante> YokoZar: https://blueprints.edge.launchpad.net/software-center/+spec/other-n-wine-software-center
[19:52] <YokoZar> Saw it :)
[19:53] <devildante> great :)
[19:53] <devildante> A little lacking at the moment, though :p
[19:54] <devildante> YokoZar: any ideas you want to add there?
[19:54] <YokoZar> link it to a wiki page
[19:55] <devildante> I create a new wiki page?
[19:55] <YokoZar> Yeah
[20:06] <devildante> YokoZar: done and linked: https://wiki.ubuntu.com/NattyWineSoftwareCenter
[20:25] <YokoZar> devildante: I put some content there
[20:26] <devildante> YokoZar: looks great, thanks :)
[21:20] <bcurtiswx_> when will we be able to update manager -d  to natty?
[21:25] <chrisccoulson> bcurtiswx_ - what's stopping you from doing that already? (not that there's really any compelling reason too)
[21:26] <chrisccoulson> i think i'll wait until after UDS ;)
[21:26] <Sarvatt> bcurtiswx: after an alpha release probably
[21:26] <soren> I kind of doubt there's a natty upgrade tool yet.
[21:26] <micahg> bugabundo already upgraded
[21:26] <chrisccoulson> oh, right. but you can still sed -ri s/maverick/natty /etc/apt/sources.list and apt-get upgrade ;)
[21:26] <bcurtiswx_> well i want to start "playing" after auto sync starts.. but is there an easy way to use the repos for natty? or will i have to manually do and change all maverick to natty
[21:27] <bcurtiswx_> hmm, i tend to ask questions right after they're already answered
[21:27] <bcurtiswx_> thx :)
[21:28] <chrisccoulson> i really can't think of any reason why people would want to upgrade just now though
[21:28] <Sarvatt> manually change the sources to natty yeah, it's always like that until the alphas
[21:28] <chrisccoulson> with the exception of a few bits of the toolchain, natty is actually behind maverick whilst we process SRU's
[21:28] <bcurtiswx_> chrisccoulson, yeah, im gonna wait until auto sync, wasn't sure if there was a time when natty repos were opened. (if not already) :P
[21:29] <chrisccoulson> well, the release exists, but it's not open
[21:29] <Sarvatt> already switched my maverick-changes bookmarks to point at https://lists.ubuntu.com/archives/natty-changes/2010-October/date.html :)
[21:29] <chrisccoulson> and there's a whole load of SRU's waiting in maverick-proposed that haven't been copied to natty yet
[21:29] <micahg> chrisccoulson: usually when stuff moves to -updates, it gets pocket copied to natty
[21:29] <chrisccoulson> micahg - yeah, that's right
[21:30]  * bcurtiswx_ is learning more new things.. woo
[21:30] <bcurtiswx_> free education!
[21:31] <chrisccoulson> i've got "dput ubuntu firefox-4.0" on my terminal and my finger resting on ENTER, waiting for natty to open ;)
[21:31] <chrisccoulson> j/k ;)
[21:31] <bcurtiswx_> haha, i played around with 4-0... stayed with chrome
[21:32] <bcurtiswx_> i hope someone discusses moving the greasemonkey scripts to chrome at thie upcoming UDS
[21:32] <bcurtiswx_> this*
[21:32] <micahg> bcurtiswx_: what scripts?
[21:32] <Sarvatt> same with libdrm and xserver-xorg-video-intel here, so many bug fixes we couldn't get in because of the 10/10 release date move timing badly with upstream releases
[21:32] <bcurtiswx_> LP
[21:32] <micahg> bcurtiswx_: already done
[21:33] <bcurtiswx_> orly?
[21:33] <chrisccoulson> Sarvatt, yeah. but that didn't really make too much difference for me, as firefox 4.0 was never really going to make it to maverick ;)
[21:33] <chrisccoulson> even though users asked for it
[21:33] <bcurtiswx_> im excited for this cycle, we get a few extra weeks :D
[21:33] <bcurtiswx_> we'll need it for GNOME3.0
[21:34] <Sarvatt> for sure, it's going to be a *fun* release cycle full of brokenness there :)
[21:34] <chrisccoulson> yeah, it's going to be crazy
[21:34] <chrisccoulson> the only advice i can give is "SLEEP BEFORE UDS" ;)
[21:34] <bcurtiswx_> good cycle to get into packaging :).. at least thats what seb128 keeps telling me :P
[21:35] <bcurtiswx_> im gonna hate not being at UDS.. someone will have to give jcastro a good word for me for support
[21:35] <bcurtiswx_> im a poor college student..
[21:36] <micahg> chrisccoulson: I just found out the next DMB meeting is 8AM on Monday at UDS
[21:36] <chrisccoulson> nice!
[21:36] <chrisccoulson> i really need to do my core-dev application :/
[21:36] <bcurtiswx_> you out of the US peeps looking forward to some florida weather (lots of thunderstorms)
[21:37] <jcastro> I don't make those decisions!
[21:37]  * bcurtiswx_ hides in corner
[21:38] <chrisccoulson> i really really like thunderstorms
[21:38] <chrisccoulson> i went to orlando in the first week of june a few years back, hoping to see lots
[21:38] <chrisccoulson> and we didn't have any
[21:38] <chrisccoulson> then there was a thunderstorm every day the week after i left
[21:38] <chrisccoulson> :(
[21:38] <bcurtiswx_> chrisccoulson, me too. <--- B.S. Meteorology
[21:39] <chrisccoulson> cool!
[22:52] <Cimi> I would like to be added to planet ubuntu, how can I do this since I'm not an ubuntu member yet?
[22:53] <TheMuso> Cimi: Unless there is a good reason that someone in the Ubuntu community thinks your blog should be sindicated, you need to become an Ubuntu member.
[22:54] <Cimi> TheMuso: I want to blog about the things I'm doing :-)
[22:55] <TheMuso> I'm not really the person who can answer your query, and this is somewhat off topic for in here anyway.
[22:55] <Cimi> yeah I know
[23:01] <Cimi> ops damn
[23:01] <Cimi> kenvandine: help pls
[23:03] <Cimi> i don't know what happened, I pushed in a branch, it was pushed even in trunk
[23:03] <Cimi> code.launchpad.net/light-themes
[23:03] <Cimi> it's the first time this happens
[23:06] <jcastro> Cimi: nice work on the gtk3 port!
[23:06] <Cimi> ok I've got the error
[23:06] <Cimi> I did bzr co lp:light-themes and then I pushed in the branch
[23:07] <Cimi> instead branching light-themes at first
[23:07]  * Cimi idiot, as always :)
[23:07]  * Cimi should not work at midnight
[23:07] <Cimi> thanks jcastro