[07:39] <baptistemm> oops
[07:59] <didrocks> good morning
[08:01] <didrocks> RAOF: hey, I still can't upgrade my xserver because of nvidia: http://paste.ubuntu.com/449524/ any idea?
[08:01] <baptistemm> heya didrocks
[08:03] <didrocks> salut baptistemm, ça va ?
[08:03] <baptistemm> ouep
[08:14] <pitti> Good morning
[08:15] <pitti> slomo: I tried vala-gen-introspect, but I didn't even get that to work; produces 0-byte output and crashes
[08:15] <pitti> vish: perhaps try poking cjwatson/slangasek?
[08:15] <pitti> vish: I'll try to have a look, but I can only spend very limited hours on SRUs this cycle
[08:17] <didrocks> good morning pitti
[08:18] <baptistemm> I packaged bluez 4.66 and obexd 0.27 for who concerned, but I guess I need james_w has to merge the code first
[08:18] <baptistemm> s/who/whom/
[08:19] <james_w> hi baptistemm
[08:19] <james_w> any developer can do it, it doesn't have to be me
[08:20] <baptistemm> hi james_w, ah Okay, I thought you were managing that as the merge recipient is you
[08:21] <vish> pitti: oh , ok. they seemed a bit busy .. and you had already seen the branch when you approved the lucid task, so thought it might be easier for you..  i'll wait then  :)
[08:21] <baptistemm> so anyone willing to, you can merge https://code.edge.launchpad.net/~bluetooth/ubuntu/maverick/obexd/main and https://code.edge.launchpad.net/~bluetooth/ubuntu/maverick/bluez/main :)
[09:07] <seb128> hey there
[09:11] <didrocks> salut seb128
[09:11] <seb128> lut didrocks
[09:12] <didrocks> seb128: tu as le bonjour de kinouchou et YoBoY :)
[09:13] <seb128> didrocks, ;-)
[09:13] <seb128> didrocks, c'était bien votre réunion ?
[09:13] <didrocks> seb128: boarf, comme d'hab, beaucoup de plan sur la comète… :)
[09:14] <seb128> hehe
[09:15] <didrocks> seb128: et sinon, toi bon week-end?
[09:16] <seb128> oui, nickel
[09:18] <pitti> bonjour seb128
[09:19] <seb128> pitti, hey
[09:20] <pitti> oh, mvo is on holiday all week
[09:27] <seb128> pitti, right
[09:29] <huats> morning
[09:33] <didrocks> hum, last version of libappindicator0.0-cil broke banshee indicator
[09:36] <seb128> didrocks, right, they were discussing the 0 or 1 abi before weekend
[09:36] <seb128> didrocks, check with kenvandine or ted when they will be there
[09:36] <didrocks> seb128: sure, I will, I have also another thing to discuss with ted about the python binding (some function not working). That will be his day :)
[09:37] <didrocks> do you think I should write a page for banshee evaluation for default in UNE or just discuss that in the meeting? (I have some TODO and WI list)
[09:40] <seb128> would be nice to do a summary of what you noted
[09:40] <seb128> could be worth sending to the ubuntu-desktop mailing list
[09:40] <seb128> seems better than a wiki to discuss
[09:40] <seb128> or start with the meeting tomorrow
[09:41] <didrocks> ok, starting with the meeting tomorrow and then, launch the discussion in the ubuntu-desktop mailing list
[09:42] <seb128> ok
[10:17] <seb128> milanbv, hi, thanks for not trolling on upstream lists
[10:17] <seb128> milanbv, we already have enough discussion about what Ubuntu does or not without that
[10:21] <milanbv> seb128: sorry, but I don't think that's trolling :-)
[10:21] <seb128> milanbv, so you think porting firefox and openoffice to gtk3 is trivial?
[10:21] <milanbv> why doesn't an Ubuntu dev clearly explain what's the problem with GTK+3 on desktop-devel?
[10:21] <seb128> and chromium
[10:21] <seb128> milanbv, I'm going to
[10:22] <milanbv> ah, here's a point - but I had never heard it before
[10:22] <milanbv> cool :-)
[10:22] <seb128> this discussion started before weekend
[10:22] <seb128> and I don't work on weekends
[10:22] <seb128> I'm just starting my week
[10:22] <seb128> milanbv, the issue in short is that we need to duplicate the stack
[10:22] <seb128> ie every lib using gtk needs 2 build
[10:22] <seb128> a gtk2 and a gtk3 one
[10:22] <milanbv> yeah, that I understand
[10:22] <seb128> it's lot of work
[10:23] <seb128> and we have no CD space for 2 stacks
[10:23] <seb128> and we will not port firefox this cycle
[10:23] <seb128> you can't change firefox without mozilla ack anyway
[10:23] <milanbv> but are you sure porting Firefox and OO.o is so much work?
[10:23] <milanbv> I've no idea about that, but usually it's not that hard
[10:23] <milanbv> even if their codebases are evil ;-)
[10:23] <seb128> mozilla doesn't let firefox to be changed without them approving the change
[10:23] <seb128> to start with
[10:24] <seb128> and I doubt they will allow such changes in a distribution
[10:24] <milanbv> though I doubt they would refuses patches for that...
[10:24] <seb128> I doubt they will want to switch to gtk3
[10:24] <seb128> they don't have 2 codecases
[10:24] <seb128> and most of their users are on gtk2 systems
[10:24] <seb128> what would they win?
[10:25] <milanbv> no idea, but that's definitely something to discuss with GNOME, because verybody is affected
[10:25] <milanbv> they wouldn't win much, but anyway they'll have to switch
[10:26] <seb128> not so sure
[10:26] <seb128> gtk2 will be around for a while
[10:26] <seb128> ie years
[10:26] <seb128> they have no hurry to switch
[10:27] <milanbv> yeah, but Linux distribs aren't going to use a GTK2 firefox for ages
[10:27] <seb128> I'm pretty sure no distro will be able to do without gtk2 in the next year for their default installation
[10:27] <milanbv> else that means GNOME will stay 2.30
[10:27] <seb128> milanbv, what will they use?
[10:27] <seb128> no
[10:27] <seb128> it ship means you have to ship 2 versions of GTK
[10:27] <seb128> which is not so much of an issue and most distros will do
[10:27] <seb128> but it requires work and CD space
[10:27] <milanbv> I agree that's really not optimal
[10:28] <seb128> and we don't have the manpower for the packaging work and port work in half a cycle
[10:28] <seb128> we aim for GTK3 and GNOME3 next cycle
[10:28] <seb128> our team is small and we can't get there this cycle
[10:28] <milanbv> but I fear all that patching work will be tedious too
[10:29] <seb128> it will
[10:29] <seb128> that's why we plan to do the platform this cycle
[10:29] <seb128> ie we will have gtk3 and libraries built for it this cycle
[10:30] <seb128> but not on the default installation
[10:30] <seb128> so we can start working on getting things building with it
[10:30] <seb128> but I've little doubt we will not be done by end of the cycle
[10:30] <milanbv> anyway, I really believe this kind of decision should be explained upstream ASAP
[10:31] <milanbv> you're helping rants against Ubuntu by not talking
[10:33] <seb128> I talked to andre and vuntz about it
[10:33] <seb128> we had fpeters at UDS
[10:34] <seb128> and it has publically mentioned to several upstream
[10:34] <seb128> ie empathy, tomboy
[10:34] <seb128> I do plan to reply to those emails
[10:34] <seb128> I didn't do an email upstream before because it's a distro choice
[10:34] <seb128> and I don't see how what we do is revelant for upstream
[10:34] <seb128> as you said on the list Ubuntu is only one distro
[10:35] <seb128> why our choice should matter enough to be announced upstream
[10:35] <milanbv> that's not one distro - that's one of the main distros
[10:36] <seb128> I will reply to this email
[10:36] <seb128> the bottom line is that I think GNOME is right to go to GTK3 this cycle
[10:36] <milanbv> and that's relevant because e.g. Empathy devs are primarily concerned about getting 2.32 into Ubuntu
[10:36] <seb128> but I don't trust GNOME3 to be ready on time
[10:37] <seb128> well they are not the only ones and they are right as a project
[10:37] <seb128> lot of upstream care about their code to run on the current lts
[10:37] <didrocks> milanbv: empathy guys are already aware of that, we discussed it over the week-end and I annonced the point seb128 just explained to you
[10:37] <seb128> and will do for some years
[10:37] <didrocks> announced*
[10:37] <seb128> or on the coming Debian stable
[10:37] <seb128> or on RHEL6
[10:37] <seb128> or on the current opensuse
[10:37] <seb128> the fact that GNOME3 is coming doesn't mean those distro will stop being used
[10:38] <seb128> and upstream will keep carring about having their software new versions available for those users
[10:38] <seb128> I doubt firefox we go with "we do builds for GTK3, if you use RHEL or Lucid LTS or Debian you loose"
[10:38] <seb128> will go
[10:39] <seb128> I think it's not realistic to ask softwares writers to go GTK3 only
[10:39] <milanbv> Firefox is another kettle of fish...
[10:39] <seb128> well take pidgin if you like
[10:39] <seb128> or chrome
[10:39] <seb128> or openoffice
[10:39] <seb128> or eclipse
[10:39] <seb128> everything which matters out of GNOME itself
[10:40] <milanbv> ...and is on the CD
[10:40] <seb128> that's orthogonal
[10:40] <milanbv> people using Eclipse can afford loading a second GTK+ version
[10:40] <seb128> I'm explaining you why empathy and other will care about being gtk2 compatible still
[10:40] <seb128> it doesn't mean they will not allow building with gtk3
[10:41] <seb128> but dropping gtk2 support doesn't seem something software writters should or will do
[10:41] <seb128> well there is 2 topics there
[10:41] <seb128> - default gtk version we can and will use
[10:41] <seb128> - what upstream code will build with
[10:41] <seb128> and saying upstream code should stop building with gtk2 is a no go
[10:41] <seb128> it means upstream code will stop building on Lucid LTS
[10:41] <seb128> or RHEL6
[10:41] <seb128> or Debian
[10:42] <seb128> or opensuse
[10:42] <milanbv> that's true for standalone software
[10:42] <seb128> those distros don't have gtk3 in their current stable
[10:42] <milanbv> but for GNOME core
[10:42] <seb128> well, empathy is standalone software
[10:42] <Zdra> seb128, it's really unsure empathy will build with gtk2
[10:42] <seb128> or they can decide if they care about their software being shipped out of the new GNOME
[10:43] <milanbv> and I think gnome-settings-daemon depends on GTK+3 already
[10:43] <seb128> Zdra, well it's a call your team should be doing but knowing you drop support for all those distro when you do it
[10:43] <Zdra> seb128, we are really in the middle of dilemma tbh
[10:43] <seb128> milanbv, right, which is why we don't update to GNOME 2.31
[10:43] <milanbv> yeah, but it's really not that nice...
[10:43] <seb128> we don't have confidence on GNOME3 to be ready this cycle
[10:43] <milanbv> I see
[10:43] <seb128> it's going to be like the new KDE
[10:44] <seb128> buggy and crashy
[10:44] <milanbv> :D
[10:44] <seb128> it's lot of changes for one cycle
[10:44] <seb128> it's mixing gtk3 and dconf
[10:44] <milanbv> not as many as for KDE4
[10:44] <Zdra> seb128, I think the big big mistake is to not provide GtkApplication in Gtk 2.22
[10:45] <Zdra> luckily they are (it seems) still making libunique-3
[10:45] <Zdra> so that could safe us all
[10:45] <seb128> how does that makes any difference?
[10:45] <seb128> that's libunique for gtk3
[10:46] <seb128> oh, you mean you can keep using that and not depends on gtk3 specific apis
[10:46] <seb128> right...
[10:46] <rodrigo_> seb128, have you seen the 'Call to maintainers: GNOME 2.31 to ship GTK 2.90' in desktop-devel-list?
[10:46] <Zdra> seb128, exactly
[10:46] <milanbv> rodrigo_: sure he has ;-)
[10:46] <rodrigo_> seb128, they're talking about ubuntu not shipping gtk3, if you have something to say
[10:46] <rodrigo_> ah, ok :)
[10:47] <rodrigo_> ah, I see you've been discussing it :)
[10:48] <Zdra> seb128, in the unlikely hypotheses that all packages shipped with ubuntu liveCD can build with GTK3, would you accept to ship gtk3 with maverick?
[10:48] <seb128> Zdra, if it's available on time and working yes
[10:49] <seb128> I still have little confidence on the GNOME3 schedule
[10:49] <seb128> Zdra, but I doubt firefox or openoffice will be gtk3 friendly this cycle
[10:49] <seb128> knowing those it will take a year to get there
[10:50] <seb128> I don't think openoffice will roll a new version this cycle
[10:50] <Zdra> seb128, yeah, it is unlikely... but to totally fair, I think you should communicate your position, give a list of packages that needs absolutely to build with gtk3, then we'll see...
[10:50] <seb128> Zdra, I plan to reply to the mailing list with what I just said there
[10:50] <seb128> I think it's not a good choice for software writters to drop gtk2 support
[10:51] <seb128> it's not something any reasonable isv would do
[10:51] <seb128> I don't ever see firefox telling all those RHEL or Debian or LTS use to stop using firefox
[10:51] <Zdra> in the first place I think it is a *really* bad idea from GTK dev to add features in GTK 3.0
[10:51] <Zdra> the initial plan was to have gtk 3.0 == gtk2.22 - deprecated
[10:51] <milanbv> Firefox could be GTK2 and 3 friendly at the same time
[10:52] <milanbv> just removing deprecated symbols
[10:52] <milanbv> that's what most GNOME modules will do
[10:52] <milanbv> the problem is, will they want it in time...
[10:53] <seb128> no, it's not what GNOME will do
[10:53] <seb128> that's why we have this discussion
[10:53] <seb128> empathy 2.32 for example might depends on gtk3
[10:53] <seb128> ie using gtkapplication
[10:53] <seb128> which is a gtk3 feature only
[10:53] <seb128> which means it will not be able to build it with gtk2 or on any gtk2 only distro
[10:54] <seb128> well again those are 2 different issues
[10:54] <Zdra> seb128, tbh we didn't make any decision, and we understand it is important to support gtk2, and even more important to be shipped with ubuntu
[10:54] <seb128> one being what default gtk we will use
[10:54] <seb128> the other is what software writters will support
[10:54] <seb128> I can't really speak for GNOME components
[10:54] <seb128> ie empathy
[10:54] <Zdra> seb128, but if that becomes a GNOME goal to drop libunique and use GtkApplication... then that will become problematic
[10:55] <seb128> but I can for sure say that things like pidgin or firefox or chrome will not let gtk2 users down by stopping building with it
[10:55] <seb128> Zdra, you could have buildtime if code to use one or the other I guess
[10:55] <milanbv> using libunique for yet one cycle won't be considered a crime I guess
[10:55] <Zdra> seb128, I think the important thing now is the explain the ubuntu position, and ask GNOME release them to ensure that 2.32 still build with gtk2 as compatibility
[10:55] <seb128> I plan to do that
[10:56] <Zdra> seb128, and also ask GTK dev WTF they are doing with 2.22
[10:57] <Zdra> they should really backport gtkapplication, I see no reason for not doing it
[10:57] <rodrigo_> someone mentioned having GtkApplication in2.22, iirc
[10:57] <rodrigo_> with that, most stuff should work ok with both gtk2 and gtk3, I think
[10:57] <milanbv> Zdra: ask Colin Walters, I think he was OK to do it
[12:42] <didrocks> seb128: did your rhythmbox snapshot work for you?
[12:45] <seb128> didrocks, no, I like to upload broken things
[12:45] <seb128> ;-)
[12:45] <didrocks> seb128: I knew that! :-)
[12:45] <seb128> didrocks, what issue do you have?
[12:46] <didrocks> seb128: more seriously, it's segfaulting each times it tries to play something (local mp3/ogg, radio, upnp shared music)
[12:46] <seb128> stacktrace?
[12:46] <seb128> let me try
[12:46] <didrocks> on the way, installing the -dbgsym now
[12:46] <seb128> I'm still on lucid so I tested it on lucid
[12:46] <seb128> I'm starting my mini which runs maverick now
[12:47] <didrocks> ok
[12:47] <didrocks> that's why I asked you first :-)
[12:48] <seb128> can you try to play an ogg in totelm
[12:48] <seb128> totem
[12:49] <didrocks> mp3 and ogg are working in totem
[12:49] <didrocks> so, doesn't seem to be gstreamer related
[12:51] <seb128> didrocks, I can play the example-contents ogg fine on the mini
[12:51] <seb128> let's wait for your stacktrace
[12:51] <didrocks> hum, it seems to fail in gstreamer :/ let me install the -dbgsym for it
[12:51] <seb128> didrocks, try changing the crossfading option
[12:52] <didrocks> oh, now I remember I activated this morning a plugin
[12:53] <didrocks> got it it's ReplayAgain
[12:53] <didrocks> ReplayGain
[12:53] <seb128> ok
[12:53] <didrocks> seb128: this plugin is officiel, right? I can report in upstream bugtracker?
[12:54] <didrocks> official*
[12:54] <seb128> yes
[12:55] <didrocks> ok, I will report that, thanks seb128!
[12:55] <seb128> thanks didrocks!
[12:58] <rodrigo_> what consumer does manage-credentials need to authenticate for lp-project-upload to work?
[13:05] <didrocks> rodrigo_: from the code, it's 'ubuntu-dev-tools'
[13:05] <didrocks> (function get_launchpad() used by some scripts in ubuntu-dev-tools)
[13:06] <rodrigo_> didrocks, ok, thanks
[13:13] <nessita> didrocks: hey there, I was asking rodrigo_ how to create credentials to upload releases to LP
[13:14] <nessita> and manage-credentials -c ubuntu-dev-tools is failing with "manage-credentials: error: Please define a sub-tool you would like to use
[13:14] <nessita> didrocks: any idea what am I missing?
[13:16] <didrocks> nessita: why do you use manage-credentials? you should just use lp-project-upload
[13:16] <didrocks> this one will create the crendential for you
[13:16] <nessita> didrocks: well, yes, but it says:
[13:16] <nessita> Could not connect to Launchpad: No credentials found for 'ubuntu-dev-tools', please see the manage-credentials manpage for help on how to create one for this consumer.
[13:17] <didrocks> oh ok, it's been a while I've created my credential for it, let me check
[13:17] <didrocks> because manage-credentials -c foo works
[13:17] <nessita> didrocks: thanks :-)
[13:17] <didrocks> but yeah, not with ubuntu-dev-tools
[13:18] <rodrigo_> I never had to use manage-credentials, not sure which tool created my credentials
[13:19] <nessita> rodrigo_: maybe because this is a new installation? though my home is the same, and I can push and pull from LP with no problem (to private projects as well)
[13:19] <rodrigo_> nessita, the credentials for bzr branches are different, afaik
[13:19] <nessita> oh ok
[13:20] <didrocks> nessita: manage-credentials create -c 'ubuntu-dev-tools'
[13:20] <nessita> didrocks: no way! :-)
[13:20] <didrocks> nessita: you forgot the create tool
[13:20] <nessita> yes
[13:21] <nessita> didrocks: anyways, it failed with http://ubuntu.pastebin.com/EJQDzkWt
[13:21] <nessita> I'll try again
[13:22] <didrocks> nessita: did you accepted in your browser before pressing enter?
[13:22] <didrocks> lazr.restfulclient.errors.HTTPError: HTTP Error 401: Unauthorized
[13:22] <didrocks> -> I guess no :)
[13:23] <nessita> didrocks: didn't see the browser tab, honestly
[13:23] <didrocks> nessita: is it there now?
[13:23] <nessita> didrocks: thank you! I'm uploading the project now
[13:23] <nessita> didrocks: yes, ti worked
[13:23] <nessita> it*
[13:23] <didrocks> nessita: sweet, you're welcomed :)
[13:30] <didrocks> going out for half an hour for some errands
[13:41] <seb128> didrocks, you didn't add a stacktrace to the rb crash bug
[13:43] <didrocks> seb128: got a bugzilla timeout (just checking the tab)
[13:43] <seb128> ok
[13:43] <didrocks> fixing this
[13:43] <seb128> thank you
[13:44] <didrocks> seb128: done, thanks :)
[13:45] <seb128> didrocks, you might want to change the type to a text one as well
[13:45] <seb128> didrocks, you might want to change the type to a text one as well rather than a binary one
[13:45] <seb128> didrocks, you might want to change the type to a text one as well rather than a binary one
[13:45] <seb128> ups
[13:45] <seb128> sorry
[13:45] <didrocks> seb128: hum? I don't know that feature, let me have a look
[13:45] <seb128> well usually clicking on a stacktrace works
[13:46] <seb128> there is wants to open it and it says it's a binary format to download
[13:46] <didrocks> hum, that's because it gave a bad MimeType
[13:47] <didrocks> (bugzilla is horribly slow there today)
[13:47] <seb128> usually people just copy the stacktrace in a comment on bugzilla I think
[13:47] <pedro_> didrocks, i've paste the stacktrace you attached in the bug report so it can be looked more easily
[13:47] <seb128> bugzilla is clever about those and display only the start with a expender sign
[13:47] <seb128> thanks pedro_
[13:47] <pedro_> that way it would work as seb128 said
[13:47] <seb128> pedro_, hey btw, how are you?
[13:47] <didrocks> pedro_: thanks a lot :)
[13:47] <pedro_> with the stacktrace parser and all that
[13:48] <pedro_> seb128, I'm good! how are you doing?
[13:48] <pedro_> didrocks, you're welcome ;-)
[13:48] <seb128> I'm fine thanks
[13:48] <didrocks> seb128: ok, I will do that way next time, just paste it
[13:48] <didrocks> seb128: thanks too :-)
[13:48] <seb128> didrocks, see what it gives now that pedro copied it
[13:49] <didrocks> right, it's easily readable without cluttering the page
[13:53] <ravibn> Hi! I need help installing ubuntu 10.04 64 bit
[13:53] <seb128> ravibn, hi, try #ubuntu
[13:54] <ravibn> seb128: been there and they said they do not know
[13:54] <seb128> ravibn, well try again later then
[13:54] <ravibn> no one else wanna try here
[13:55] <ravibn> looks like people are watching football
[13:56] <seb128> didrocks, is oneconf in s-c or ubiquity still likely for a2 or should that be revisited?
[13:57] <seb128> didrocks, can you give me a summary of where it stands? does it need design input? did people agree to get it in there?
[13:57] <seb128> hello rickspencer3
[13:57] <didrocks> seb128: mvo told me last week that the software-center plugin was available end of last week, which didn't happen. So, it will be delay by one more week now that he is in holidays
[13:58] <didrocks> mpt is working today on the design (we discussed together last Friday about that point)
[13:58] <seb128> didrocks, mvo is not the only one to work on s-c ;-)
[13:58] <didrocks> so, designed-view, it shold be ok
[13:58] <seb128> ok
[13:58] <seb128> so design agree to get it in s-c?
[13:58] <didrocks> seb128: yeah, but the plugin part was his task, apparently
[13:58] <didrocks> right
[13:58] <seb128> I though there were some discussions about it and I though I read about ubiquity being an issue due to connectivity not always being there etc
[13:58] <didrocks> ubiquity, I think it won't do it this cycle to be honest
[13:58] <rickspencer3> good morning seb128
[13:59] <didrocks> hey rickspencer3
[13:59] <seb128> didrocks, ok, I agree with that, can you change the workitem to delayed?
[13:59] <didrocks> seb128: sure, DELAYED or POSTPONED? both are valid?
[13:59] <seb128> ups, postponed
[13:59] <didrocks> ok :)
[13:59] <seb128> sorry ;-)
[13:59] <didrocks> no worry :-)
[14:00] <seb128> the appmenubar is in main btw now
[14:00] <didrocks> ok, will seed it today so
[14:00] <seb128> so it should be easy to check that workitem this week if you want ;-)
[14:00] <seb128> check with davidbarth first though
[14:00] <didrocks> sure
[14:00] <seb128> I think he had some concern about quality on friday
[14:00] <didrocks> also, I will POSTPONE some Quickly tasks as gedit is changing his plugin system this cycle
[14:01] <seb128> it might require to confirm if it's ready to go or not
[14:01] <didrocks> ok, will check with him
[14:01] <seb128> didrocks, ok
[14:01] <seb128> thanks!
[14:01] <didrocks> you're welcome :)
[14:01] <seb128> tremolux, hello
[14:02] <didrocks> hey tremolux
[14:03] <seb128> tremolux, can you let me know when you have some time to talk about your workitems?
[14:03] <seb128> tremolux, you are a bit behind on the alpha2 list, we are near of the mid-milestone mark and you got 5 items on 18 done
[14:04] <seb128> tremolux, that's not an issue but need to look if those items are still realistics or if some need to be moved to a3 now
[14:04] <seb128> kenvandine, hey
[14:05] <seb128> kenvandine, it seems the tp-approver thing will not happen for a2 right?
[14:05] <seb128> kenvandine, can you move it to a3 if that's the case?
[14:05] <seb128> ArneGoetje, hi
[14:06] <seb128> ArneGoetje, where do you stand with design for language-selectors mockups? can you ping them to get an update if you didn't have one recently?
[14:07] <seb128> RAOF, you are probably sleeping or not working right now but for tomorrow, we need to discuss your workitems, we are mid a2 milestone and you got 2 items out of 21 crossed
[14:07] <seb128> RAOF, I would like to check with you if you need help or if we shoul reschedule some of those for later
[14:10] <kenvandine> seb128, yeah, will do
[14:10] <seb128> kenvandine, thanks
[14:10] <seb128> kenvandine, hey btw, did you have a nice weekend?
[14:26] <kenvandine> seb128, not really... but i hope you did :)
[14:26] <kenvandine> seb128, i started getting sick thurs and friday... and friday night i went to the doctor... turns out i have an infection caused by a tick bite
[14:27] <seb128> urg
[14:27] <kenvandine> something similar to rocky mountain spotted fever, not sure if you ever heard of that
[14:27] <seb128> :-(
[14:27] <kenvandine> but it's a pain...
[14:27] <seb128> my weekend was quite nice thanks
[14:27] <seb128> kenvandine, no I didn't, checking on internet now ;-)
[14:28] <seb128> kenvandine, I hope you get better
[14:28] <kenvandine> anyway... i'll survive... but will have joint pain.. aches and pains and a fever for probably 2 full weeks :(
[14:28] <seb128> kenvandine, take some rest today if you need it
[14:28] <seb128> :-(
[14:28] <kenvandine> it's a nasty infection... i was never too worried about ticks before...
[14:28] <kenvandine> anyway... i'll be ok :)
[14:28] <seb128> they are known to be bad around there
[14:29] <kenvandine> yeah
[14:29] <seb128> we try to be careful with those
[14:29] <kenvandine> i was working on my fence two weeks ago... and got a bunch of bite
[14:29] <kenvandine> +s
[14:30] <seb128> anyway at least you know what you have now
[14:30] <kenvandine> yeah... glad my wife made me go to the doctor...
[14:30] <kenvandine> she's the one that remembered i got the tick bites... and knew to make me go to the doctor asap
[15:28] <tremolux> seb128: hi Seb, we can talk about work items; last week was a bit of a backfill week but I plan to focus on work items this week exclusively
[15:28] <kenvandine> seb128, just talked to rickspencer3, we moved all my existing gwibber WIs to a3
[15:29] <rickspencer3> and add work items for fixing Twitter after Twitter breaks Gwibber
[15:29] <kenvandine> and i added a couple new ones to a2, to handle an important change to twitter that needs to get into lucid by the end of june
[15:29] <seb128> ok, thanks
[15:29] <seb128> tremolux, hey
[15:29] <kenvandine> seb128, basically twitter.com is turning off the auth mechanism that we use currently, and they just published the spec for how open source apps will need to auth
[15:29] <tremolux> seb128: particularly the New Apps and Buy something items are moving now
[15:30] <tremolux> seb128: hiya  :)
[15:30] <seb128> kenvandine, seems something to move priority on indeed
[15:30] <kenvandine> yeah
[15:30] <seb128> tremolux, so do you think you are on track to get everything on http://people.canonical.com/~pitti/workitems/maverick/canonical-desktop-team-maverick-alpha-2.html done by end of the month or not?
[15:31] <seb128> tremolux, ""Where is it" feature; investigate whether we need to enable accessibility by default (enables us to talk to the menu)"
[15:31] <seb128> tremolux, did you take into consideration environments without menus, ie UNE, for this one?
[15:32] <tremolux> seb128: no, actually, I haven't dug into that one at all yet
[15:32] <tremolux> seb128: those items in the UI Enhancements lists test to be standalong features, they are good candidates for trading in and out as we see fit
[15:33] <seb128> ok
[15:33] <seb128> it seems to me this one should be move to alpha3
[15:33] <seb128> what do you think?
[15:34] <tremolux> seb128: yeah, I agree; the issue with accessibility was the gate for that
[15:34] <seb128> ok, please move it then on the blueprint then, thanks
[15:34] <tremolux> seb128: will do
[15:34] <seb128> tremolux, otherwise you have quite some items still but it seems doable if you focus on those this week
[15:34] <seb128> tremolux, let's see how it goes
[15:35] <seb128> tremolux, keep the good work, s-c looks great ;-)
[15:35] <tremolux> seb128: yes, that sounds good
[15:35] <seb128> tremolux, btw let me know if you need sponsoring for an upload this week since mvo is on holidays
[15:35] <tremolux> seb128: thanks :)
[15:35] <tremolux> seb128: right, thanks, mvo mentioned that, I think later this week may be a good time to do one
[15:36] <seb128> ok
[15:36] <seb128> just let me know when you think we should do an update
[15:36] <tremolux> seb128: we did a release last week with a lot of new stuff and I've done some cleanup since
[15:36] <tremolux> seb128: thanks
[15:38] <bcurtiswx> seb128: will the testing PPA's be posted on the mailing lists.  I can use my VM if it'll help out. (i.e. the new gnome panel)
[15:39] <seb128> bcurtiswx, what testing ppa?
[15:39] <seb128> oh, you mean specifically for gnome-panel
[15:39] <seb128> I guess we will not do the update
[15:39] <seb128> I should update the blueprint
[15:39] <seb128> the gtk3 issue got added to the list since UDS
[15:39] <bcurtiswx> seb128: yeah, im reading ahead on some of the blueprints
[15:45]  * bcurtiswx shrugs as to why his wireless is bad today
[15:48] <tremolux> kenvandine: hi Ken, mpt has some useful comments for Gwibber integration in Software Center here:  https://bugs.edge.launchpad.net/ubuntu/+source/software-center/+bug/592619
[15:48] <ubot2> Launchpad bug 592619 in software-center (Ubuntu) "Software item screen has unspecified "Share via microblog" item (affects: 1) (heat: 6)" [Undecided,New]
[15:49]  * kenvandine looks
[15:49] <tremolux> kenvandine: p.s.  sorry to hear about your tick bite!
[15:49] <tremolux> kenvandine: not Lyme disease, is it?
[15:50]  * bcurtiswx agrees it sounds like Lyme disease
[15:51] <kenvandine> no.. thankfully
[15:51] <kenvandine> ehrlichiosis
[15:52]  * kenvandine hates medical terms... do that have to be so hard to pronounce and spell?
[15:52] <tremolux> kenvandine: ug, still sounds like no fun
[15:52] <kenvandine> it is pretty similar to rocky mounted spotted fever, but not as agressive
[15:53] <tremolux> kenvandine: it's great for parties tho, "oh, yes, I've got this nasty case of ehrlichiosis.  please pass the onion dip"
[15:54] <kenvandine> hehe
[15:54] <kenvandine> that's awesome
[15:54] <tremolux> kenvandine: anyway, feel better soon
[15:55] <kenvandine> thx man
[15:56] <tremolux> kenvandine: note on that bug, reviews are not currently in the plan for maverick
[15:58] <kenvandine> tremolux, indeed... my original branch didn't use the term microblog... i think it said something like Share with your social networks
[15:58] <kenvandine> or something like that
[15:59] <tremolux> kenvandine: ah, interesting!
[15:59] <kenvandine> i know we avoid the term microblog... but i am not sure there is a consensus on what should be used
[15:59] <tremolux> kenvandine: I can check, maybe mvo changed that?
[15:59] <kenvandine> mpt, "Broadcast"
[15:59] <kenvandine> mvo did change it... almost certain
[15:59] <tremolux> kenvandine: yeah
[16:00] <kenvandine> maybe mpt can give us some guidance on terminology
[16:00] <kenvandine> and he makes a good point for apturl
[16:00] <kenvandine> but... other gwibber users get something useful
[16:02] <mpt> kenvandine, I think first we should nail down what user stories we want to satisfy. "Check out {this thing}" doesn't seem obviously something we should make easy -- or at least, not easier than, say, e-mailing someone about this thing.
[16:03] <mpt> kenvandine, were there any other suggestions made during the UDS session?
[16:15] <rodrigo_> seb128, more questions :)
[16:15] <seb128> ?
[16:15] <seb128> I didn't get your previous question if you asked one
[16:15] <rodrigo_> seb128, we have a package split from u1-client that we want to upload to maverick and included in main
[16:15] <seb128> so ask again ;-)
[16:16] <rodrigo_> seb128, just warning you that I have more questions :)
[16:16] <seb128> oh ok
[16:16] <rodrigo_> seb128, so, should we go via REVU?
[16:16] <rodrigo_> or just upload and file a MIR?
[16:16] <seb128> source split or binaries split from what is built?
[16:16] <rodrigo_> source split
[16:16] <seb128> I doubt you will be able to upload the new source
[16:16] <seb128> you need a new package, review, etc
[16:17] <nessita> seb128: we almost have the new package ready
[16:17] <seb128> ok good
[16:17] <seb128> so feel free to upload
[16:17] <seb128> REVU is not an hard requirement
[16:17] <kenvandine> mpt, https://blueprints.launchpad.net/ubuntu/+spec/desktop-maverick-social-api
[16:17] <nessita> seb128: to upload to revu or to a branch?
[16:17] <kenvandine> the notes are on the bottom of the whiteboard
[16:17] <nessita> ah, right
[16:18] <mpt> kenvandine, our GSoC student intends to do the apturl part of that
[16:18] <seb128> nessita, to upload to Ubuntu
[16:18] <seb128> ie get somebody to sponsor it
[16:18] <seb128> ie kenvandine
[16:18] <rodrigo_> seb128, and once it's uploaded?
[16:18] <rodrigo_> ah, ok
[16:18] <nessita> perfect
[16:18] <rodrigo_> hey kenvandine, feeling better?
[16:19] <seb128> rodrigo_, I will review it in NEW once it's uploaded
[16:19] <kenvandine> rodrigo_, the ibuprofin is helping a little... keep the fever a bit down
[16:19] <kenvandine> best i can hope for :)
[16:19] <rodrigo_> kenvandine, cool, I thought you were not working today because of that, so hope it gets better :)
[16:20] <kenvandine> mpt, cool... my branch had a urlhandler for software-center specific urls, so other ubuntu users would go straight into software-center
[16:20] <kenvandine> mpt, but mvo didn't take that part of my branch :)
[16:20] <kenvandine> getting it in apturl is much better
[16:30] <ArneGoetje> seb128: I did have a meeting on Friday with them. I'm in the process of updating the specs and creating the mockups now.
[16:30] <seb128> ArneGoetje, thanks
[16:34] <kenvandine> rodrigo_, nah... i can't do anything terribly physical... but i can touch keys and move the mouse :)
[16:39] <rodrigo_> kenvandine, cool then :)
[16:52] <LaserJock> didrocks: around?
[16:52] <didrocks> LaserJock: sure
[16:54] <cjohnston> rickspencer3: are you around?
[16:54] <rickspencer3> cjohnston, yeah, but otp
[16:54] <rickspencer3> 5 - 10 mins
[16:55] <cjohnston> Could you let me know when you have a few minutes to talk about something real quick... I'm at work today, so if I'm not around I'm on a call
[16:58] <cjohnston> rickspencer3: bbiab
[17:05] <mpt> tremolux, I've specced that USC should remember {whether hidden items were shown} only inside the Back/Forward history. <https://wiki.ubuntu.com/SoftwareCenter?action=diff&rev2=376&rev1=373>
[17:05] <tremolux> mpt: excellent, thanks
[17:17] <Riddell> what's the sound mixer applet in ubuntu these days?
[17:18] <seb128> indicator-sound
[17:18] <Riddell> seb128: in lucid?
[17:18] <seb128> yes
[17:29] <LaserJock> didrocks: is there a new PPA for Unity or is it still at ppa:canonical-dx-team/une
[17:36] <didrocks> LaserJock: still the same
[17:36] <didrocks> LaserJock: just follow the instructions there: https://wiki.ubuntu.com/DesktopTeam/Unity
[18:02] <Riddell> what's the ubuntu desktop user config/new user tool these days?
[18:07] <rickspencer3> Riddell, I think that's called "the desktop"
[18:07] <rickspencer3> just kidding
[18:07] <rickspencer3> are you looking for the package name?
[18:07] <Riddell> yes
[18:08] <rickspencer3> Riddell, well, I guess it's users-admin
[18:09] <rickspencer3> but it's in the gnome-desktop
[18:09] <rickspencer3> so I don't know what package it would be in other than ubuntu-desktop
[18:09] <rickspencer3> hth
[18:10] <seb128> we are going to get a new one this cycle
[18:10] <seb128> Riddell, what are you trying to do?
[18:10] <Riddell> seb128: look at the add new user tool for ubuntu desktop
[18:10] <Riddell> if there's two such tools even better :)
[18:10] <seb128> we don't have it packaged yet
[18:10] <cjohnston> kenvandine: do you have any idea if Ryan has had a chance to look at bug 580067?
[18:10] <ubot2> Launchpad bug 580067 in gwibber "twitter fails to download messages, sometimes (affects: 2) (heat: 16)" [Undecided,New] https://launchpad.net/bugs/580067
[18:10] <Riddell> seb128: what's the old one?
[18:12] <seb128> Riddell, users-admin
[18:12] <rickspencer3> urk
[18:13] <rickspencer3> seb128, evo is crashing as soon as it is done loading messages for me
[18:13] <Riddell> ah, gnome-system-tools
[18:13] <rickspencer3> I don't see a bug assigned to our team on this
[18:13] <seb128> rickspencer3, maverick?
[18:13] <seb128> or lucid
[18:13] <rickspencer3> seb128, yah
[18:13] <rickspencer3> maverick
[18:13] <rickspencer3> I'm doing a dist-upgrade right now
[18:13] <seb128> rickspencer3, it's a bit early to start tracking bugs in maverick this way
[18:13] <rickspencer3> but didn't see a new evo
[18:14] <seb128> rickspencer3, quickly click on an another email when it opens
[18:14] <rickspencer3> seb128, ack ... but I was looking for a bug report to see if there is a workaround, etc...
[18:14] <rickspencer3> and make sure one has been logged
[18:14]  * rickspencer3 tries the quickly click trick
[18:14] <seb128> we got some similar bugs
[18:14] <seb128> not easy to say if it's the same without a stacktrace
[18:15] <rickspencer3> ok
[18:15] <rickspencer3> so long as it's tracked
[18:15] <seb128> you can also use apport to open a bug
[18:15] <seb128> if you want to be sure
[18:15] <seb128> but we do have similar crash bugs tracked
[18:16] <seb128> if you don't want to bother wait a bit
[18:16] <didrocks> rickspencer3: seb128: there are still some messages not working with the workaround
[18:16] <didrocks> didn't have the time to look at it recently
[18:18] <rickspencer3> seb128, I like the "if you don't want to bother approach" ;)
[18:18] <seb128> ;-)
[18:20] <kenvandine> cjohnston, oh... i think he did
[18:20] <kenvandine> and i think he has a fix... he should really comment on those bugs
[18:20] <kenvandine> i'll bug him about it and see if we can get the patch in an SRU
[18:21] <seb128> ok, time for sport, see you later
[18:21] <kenvandine> later seb128
[18:21] <kenvandine> have fun
[18:21] <seb128> thanks
[18:48] <cjohnston> kenvandine: I'm running the daily... was it already put in there do you think?
[19:07] <kenvandine> no... it hasn't been committed
[19:08] <kenvandine> it is bumping the timeout for pycurl
[19:08] <didrocks> rickspencer3: urgh, you got me :)
[19:08] <rickspencer3> didrocks, what?
[19:08] <didrocks> rickspencer3: I was reading http://theravingrick.blogspot.com/2010/06/go-here-to-learn-to-program-from-mit.html in my feed reader thinking I was reading xkcd and saw him mentionned Quickly !
[19:08] <didrocks> rickspencer3: but it was your blog :)
[19:08] <kenvandine> cjohnston, he thinks it will fix a handful of things... i'll get it SRU'd and committed
[19:08] <kenvandine> :)
[19:08] <rickspencer3> hehe
[19:08]  * kenvandine goes to finish eating... bbiab
[19:08] <rickspencer3> sorry didrocks
[19:09] <didrocks> rickspencer3: no pb. I was so happy for 4 seconds. It worthed it :p
[19:09] <rickspencer3> hehe
[19:23] <cjohnston> awesome
[19:46] <fta> slomo, here?
[19:50] <fta> slomo, wrt libvpx, do you track only releases? i see that mozilla is tracking a snapshot, and chromium is still with the initial git commit, while otoh, commits started to flow in upstream git
[19:53] <slomo> fta: libvpx 0.9.0-6 contains latest GIT version as of 8 days ago
[19:53] <slomo> fta: soon there will be a 0.9.1 release, i'll update to that then
[19:53] <slomo> fta: why?
[19:53] <fta> slomo, so 0.9.0-6 is 0.9.0+gitxxxx, not 0.9.0 proper, right?
[19:54] <slomo> yes
[19:54] <slomo> see the changelog
[19:54] <fta> slomo, the reason i ask is because i see some fixes and perf improvements in git. and using webm in chromium, 720p is using lots of cpu
[19:55] <fta> chromium is not yet using the GPU, so any perf improvement in the codec is good to have
[19:55] <slomo> the performance improvements are not *that* much, only a few percent
[19:56] <slomo> it's still using quite some cpu
[19:56] <fta> i know, but each % counts ;)
[20:00] <dobey> any sponsors around?
[20:06] <fta> slomo, i had to disable crossfading in rhythmbox, it was doing weird stuff since the upgrade to maverick, is there already a bug i can track?
[20:10] <slomo> fta: no idea
[21:07] <nessita> seb128: ping
[21:08] <seb128> nessita, hi
[21:08] <nessita> seb128: I'm trying to upload the package that rodrigo_ mentioned before, and I'm getting
[21:08] <nessita> nessita@dali:~$ bzr push lp:~nataliabidart/ubuntu/maverick/ubuntu-sso-client/first-release
[21:08] <nessita> bzr: ERROR: Invalid url supplied to transport: "lp:~nataliabidart/ubuntu/maverick/ubuntu-sso-client/first-release": No such source package ubuntu-sso-client.
[21:09] <nessita> seb128: I'm new to packaging, but rodrigo_ said that would be correct, could you please point what's missing?
[21:10] <nessita> seb128: or do I need to upload using dput?
[21:10] <seb128> is there a ubuntu-sso-client product on launchpad?
[21:10] <seb128> urg, rather source package in ubuntu
[21:11] <nessita> seb128: yes to project, no to source package on ubuntu
[21:11] <nessita> seb128: this is meant to be that package :-)
[21:11] <seb128> ok so you can't use the ubuntu maverick namespace
[21:11] <seb128> well you need to push somewhere else until it's in ubuntu
[21:11] <seb128> ie lp:~nataliabidart/ubuntu-sso-client/first-release
[21:11] <james_w> even a ppa would make that command work
[21:12] <nessita> james_w: you mean dputting to a PPA?
[21:13] <dobey> hey seb128 and james_w
[21:13] <seb128> hey dobey
[21:13] <seb128> nessita, I guess he does yes
[21:14] <nessita> seb128: what should I do after pushing to a branch of mine/putting into a PPA?
[21:14] <dobey> could i get one of you guys to poke at my mocker upload in REVU? :)
[21:15] <james_w> hi dobey
[21:15] <seb128> dobey, try #ubuntu-motu?
[21:15] <dobey> ah ok
[21:15] <james_w> nessita: yes, just dputting to a ppa would allow you to push to that url
[21:15] <seb128> I've no clue about REVU
[21:15] <dobey> i asked in -dev, but it seems pretty dead over there :)
[21:21] <nessita> james_w: yey! I could push indeed, thanks!
[21:23] <nessita> seb128: package is uploaded to lp:~nataliabidart/ubuntu/maverick/ubuntu-sso-client/first-release, I need a sponsor now, right?
[21:25] <seb128> nessita, yes
[21:30] <kenvandine> rodrigo_, got those branches merged!
[23:40] <RAOF> Mornin' all.
[23:43] <TheMuso> Morning RAOF.
[23:45] <ronoc_narruc> TheMuso: good morning !
[23:46] <TheMuso> Hey ronoc_narruc.
[23:46] <ronoc_narruc> TheMuso: how's all in Sydney since you got back ?
[23:47] <TheMuso> ronoc_narruc: Not too bad thanks. Finally into winter, although our winter is nothing compared to what the northern hemisphere gets.
[23:47] <ronoc_narruc> TheMuso: took a holiday for two weeks recently - just what I needed
[23:47] <TheMuso> Nice
[23:47] <ronoc_narruc> TheMuso: So Ivanka wants to get this sound theme redesign underway.
[23:48] <TheMuso> ronoc_narruc: ok cool
[23:49] <ronoc_narruc> TheMuso: I told her we(Michael, you and I) would come up with a list of what sounds are to be redesigned..
[23:49] <TheMuso> ok we need to look those over
[23:50] <ronoc_narruc> TheMuso, I'm pretty flat out but will fire off an email in the next day or so with my thoughts
[23:50] <TheMuso> ok
[23:50] <ronoc_narruc> TheMuso: new speakers arrived today
[23:51] <TheMuso> nice
[23:51] <ronoc_narruc> TheMuso: dynaudio BM15a's
[23:51] <TheMuso> cool
[23:51] <ronoc_narruc> as nice as i remember them from a session i did about 5 years ago
[23:51] <TheMuso> heh