[01:26] TheMuso, what video did you watch for utouch? [01:26] robert_ancell: Both the youtube and blip.tv versions. [01:27] TheMuso, it ran fine for me, weitd [01:27] weird [01:27] It ran fine for me as well, but the music was a little stuttery thats all. [01:30] TheMuso, right, I didn't notice it the first time around, but I do now :) [01:30] Ok not just me then. :) === bjf is now known as bjf[afk] === almaisan-away is now known as al-maisan [07:35] Good morning [07:59] good morning === ara__ is now known as ara [08:29] hey [08:30] hey seb128 [08:30] * pitti waves to and hugs the French mafia [08:30] * pitti hugs mvo, too [08:30] hey pitti [08:30] * vish *phew* was wondering when mvo became french [08:31] vish: hahaaha [08:31] vish: if that happens I'm screwed, my french is just too bad to survive [08:31] hehe :_ [08:37] mvo: we'll found our own little German community then [08:42] hey mvo pitti [08:42] sorry, xorg crashed on user switching [08:43] not sure if I should blame it on intel but it happens quite often since maverick it seems [08:44] seb128: I got that as well [08:44] on intel as well? [08:44] yep [08:44] it worked pretty reliably in lucid [08:45] same here [08:52] so natty is open today? [08:52] with compiz? or metacity as well? [08:53] salut seb128 [08:53] hey mvo, pitti [08:53] it seems to be pretty stable for me, but without compiz [08:53] hey didrocks [08:53] seb128: yep, upload away [08:53] hey didrocks [08:53] aha, its open? *cool* [08:54] was a nice wave of "accepted" mails this morning [08:54] got 2/3 of my merges done [08:56] so it's time to break natty ;-) [09:27] hey mpt [09:28] hi [09:28] Mumble? [09:29] mpt: ok, hold on a sec, I need to grab the headset [09:34] seb128, didn't you have a GTK3 package? Is it usable / safe to install ? [09:34] cassidy, yes and yes [09:34] https://edge.launchpad.net/~ubuntu-desktop/+archive/gnome3-builds [09:34] the amd64 builds have issues though [09:34] they seem to build again and again or something [09:35] cool, I'll push it to your PPA as well then [09:35] you can build it locally or use the i386 build though [09:35] to my ppa? [09:35] the TP one [09:35] as new empathy depends on gtk3 [09:35] cassidy, is that an unstable ppa? [09:35] we use to push latest versions of the TP stack [09:36] or maybe I should just depends on your PPA [09:36] there will be need for other sources no? [09:36] ie webkit-gtk3 [09:36] or libunique-gtk3? [09:36] yeah probably [09:36] we don't have those yet [09:36] are you going to push them to this ppa at some point ? [09:36] yes [09:36] I did gnome-desktop yesterday [09:36] we will add things as they get ready over time [09:37] are you just pushing the libs or the apps as well ? [09:37] just libs [09:37] that's meant to be a gtk3 stack that people can install to do porting work [09:37] it's not meant to turn your stable into an unstable [09:38] ok cool. Do you know how PPA deps are deal with? If I add this PPA as a dep of mine, does this mean user have to add your PPA manually ? [09:38] ok, so everything should be parrallel installable with existing libs [09:38] yeah, most of it should be [09:38] not sure for the ppa dep but I think users would have to do nothing [09:38] it should just work [09:39] ok, I'll add the dep on the tp-devel ppa for now [09:39] ok === al-maisan is now known as almaisan-away === macbookpro is now known as RainKing [11:34] how long does it typically take for a package to show up in -proposed after being submitted? [11:35] pitti: ^^ [11:36] these days around 24 hours [11:36] I process it every day, sometimes twice a day [11:41] ahhh. not automated then. :-/ [11:49] pitti: did you see evolution in your -proposed travels in the last 24h? [11:50] yes, it's in https://edge.launchpad.net/ubuntu/maverick/+queue?queue_state=1 [11:56] jcastro - do you think we should add http://askubuntu.com/ to our default bookmarks? === MacSlow is now known as MacSlow|lunch [12:02] seb128, didrocks: what's the best way to test gnome-shell on Maverick these days? Is there an official PPA or the maverick pkgs are recent enough? [12:03] pitti: do you use syncpackage script? [12:03] cassidy, jhbuild? [12:03] ari-tczew: yes, when I do Debian uploads [12:03] seb128, there is no official PPA as planned during UDS? [12:03] cassidy, the maverick pkg are recently for what you can get with tarballs [12:03] cassidy, g-s is not in a buildable state for months using released version [12:03] :( [12:04] ok, I'll jhbuild then [12:04] cassidy, they depends on gtk3 and other moving parts we didn't catch up with [12:04] do you plan to pkg gnome-shell 3.0 for Maverick+1 (even in universe) ? [12:04] yes [12:05] but not before UDS [12:05] I don't think they rolled tarballs for a while [12:05] they might still be refactoring things [12:05] ok [12:05] I guess/hope the RT will push more for releases this cycle === doko_ is now known as doko === MacSlow|lunch is now known as MacSlow === pedro__ is now known as pedro_ [13:36] chrisccoulson: I would like to do that yes, but I was just going to defer asking you until UDS [13:36] jcastro - ok, cool. i'll add that one to the default set then :) [13:37] seb128: seen this before? bug #660525 [13:37] Launchpad bug 660525 in tomboy (Ubuntu) "Pinned notes displayed as separator lines (affects: 1) (heat: 8)" [Undecided,New] https://launchpad.net/bugs/660525 [13:37] jcastro, hey, didn't see that one [13:38] jcastro, could you assign it to karl? [13:38] yep [13:38] thanks [13:41] chrisccoulson, hey [13:41] chrisccoulson, is firefox still using gnomevfs? [13:41] hi seb128 - how are you? [13:41] seb128 - the current version, yes [13:41] chrisccoulson: though after the discussion in that thread everyone wants a bookmark, maybe we should do it like we do the desktop and keep the entire thing clean [13:41] I'm doing fine thanks [13:41] but FF4.0 can use both gnomevfs and GIO [13:41] chrisccoulson, how are you? [13:42] yeah, i'm good thanks [13:42] chrisccoulson, both or either? [13:42] seb128 - yeah, it can use either, and it will select one at runtime [13:43] could you build only with gio? [13:43] or split the gnomevfs code in a different binary? [13:43] i'm not sure there's a build option for that, but it would be trivial to do [13:43] thanks [13:43] chrisccoulson, do you use bugs for your todolist? want one about that? [13:44] seb128 - please feel free to open a bug for that [13:44] on what component? [13:44] seb128 - just on firefox [13:44] seems firefox is the last remaining user on libgnomevfs on the depends install [13:44] out of libgnomeui and bindings [13:44] seb128: what's karl's workload on this? the appindicator patch is giving upstream problems, this one [13:45] yeah, we can fix that :) [13:45] jcastro, "on this"? [13:45] and the one that breaks it on xubuntu etc (I think the fallback is broken) [13:46] jcastro, dbarth said karl was on schedule for what he has to do and we can assign him bugs if we need some to be worked [13:46] jcastro, he said that early today [13:46] jcastro, so feel free to just assign those tomboy issues to him [13:46] ok [13:46] I'll ask him to look at these too [13:47] thanks [13:47] two even. [13:47] seb128: I thought DX was going to look into this pin/custom UI issue [13:47] hmm, you know what, nevermind. [13:47] * jcastro whistles [13:47] lol [13:47] yeah, let's not get started on what dx is supposed to do ;-) [13:51] seb128: we should have left it [13:51] like we did in 10.04 [13:51] what is the issue? [13:52] didn't you guys agree that the pinning was not required? [13:52] no [13:52] I was told we'd find some work around [13:55] seb128: would you agree to consider "if it's going to take him too long to fix it maybe we should look at just dropping the entire patch?" [13:56] jcastro, let's discuss it next week [13:57] ok [13:57] what is upstream going to do with tomboy this cycle? [13:57] g-s will not have a notification area either I think [13:57] what do they plan to use? [13:57] well, I don't think he's going to look favorably on our patch anymore for sure [13:57] what is the issue with our patch? [13:57] the xfce fallback? [13:57] seems tomboy works fine for most users [13:58] we get a brocken fallback but it's online fallback and that one bug you pointed today [13:59] didrocks: around? [13:59] Shred00: yeah, what's up? [14:00] seb128: I think he's just frustrated with the bugs, they're still bugs [14:00] and, they didn't exist before our patch [14:00] didrocks: so, i updated my evolution tree from your LP submission of yesterday. [14:01] and i'm getting a patch failure, but in debugging it i am finding that even though quilt applied says patches are applied, when i check actual source files, they don't appear to be. i must be missing something. [14:01] jcastro, well new code has bugs sometime... [14:01] Shred00: are you using exactly my branch or do you have your own setup and branch? [14:01] it's not like we were shipping a non working tomboy [14:01] hrm. i wonder if i have a stale .pc dir [14:01] jcastro, let's get karl to fix those [14:01] he's on it [14:01] that's the best we can do [14:02] I am just trying to communicate his frustration, and that sometimes even a little annoying bug can kill an entire idea with an upstream [14:02] we felt confident that we were going to fix this pin problem [14:02] (I know it's not your fault, but you're the tech lead so I am addressing these with you, heh) [14:03] sorry about that [14:04] I though we say we didn't care about the pinning [14:04] said [14:04] if it's important to tomboy users let's make sure we fix it this cycle [14:05] I think it's "ted said we didn't care about the pinning" [14:05] he managed to confuse me into thinking that was an agreement with you :p [14:06] hey don't speak ill of dx ;) [14:06] jcastro: go ahead and file a bug for the tomboy issue, if not already the case [14:07] they are filed and assigned to karl [14:07] and i'll put that on the alpha-1 radar [14:07] jcastro: ah cool [14:07] * kenvandine missed the pinning for a while... but got used to not having it [14:07] not saying i wouldn't be happy to see it come back :) [14:08] davidbarth: right, if we could have a recommendation for what we're going to do so I can show upstream we're taking the problem seriously that would be swell [14:09] what's the bug again, because i want to check that we have a decision on what to do [14:10] ie, design guildeines matching, implementation issue or whatnot [14:10] got it [14:10] https://bugs.launchpad.net/ubuntu/+source/tomboy/+bug/660525 [14:10] Launchpad bug 660525 in tomboy (Ubuntu) "Pinned notes displayed as separator lines (affects: 1) (heat: 8)" [Undecided,In progress] [14:10] yeah, and there's the other one with the broken fallback [14:11] which effectively breaks it on xubuntu and others [14:28] didrocks: hm, who taught you to name patches from git as 999999_git_*? They shoudl be at the top of the stack (00git_*) [14:29] i. e. the nearer a patch is towards upstream inclusion, the earlier it should be applied [14:29] and ubuntu specific patches will always go last [14:29] pitti: I saw a lot of patchs to get that name, hence the fact I use most of the time 90_git or 91… [14:29] pitti: also, with the evo express branch, I would have to touch 2 patches as this patch is pretty intrusive [14:31] but I will know next time :) [14:32] pitti, I usually use 90_... [14:32] it's just to have those out of the distro series [14:32] which usually start at the bottom [14:36] kenvandine: rejecting indicator-sound upload; please reupload with -v to cover previous changelog as well (SRU wasn't released yet) [14:39] ah [14:40] ok [14:41] pitti, --v ? what does that do? [14:41] you mean edit the changelog entry? [14:42] kenvandine: debuild -v [14:42] ah, and i can pass that to bzr bd ? [14:42] with -- -v [14:42] right? [14:43] that doesn't work... [14:44] kenvandine, how so? [14:44] kenvandine, bzr bd --source -- -v [14:47] kenvandine: bzr bd -S -- -vVERSION does work; I use it all the time [14:47] oh, you have to give it the version :) [14:47] it just gave me a parse error without it :) [14:48] well, it's not quite clever enough to mindread what you want :) [14:48] kenvandine: it's the same as with merging [14:48] but i want to give it the latest right? [14:48] 0.4.9-0ubuntu1 [14:49] i see [14:49] indicator-sound | 0.4.7-0ubuntu2 | maverick | source, amd64, i386 [14:49] kenvandine: you want -v0.4.7-0ubuntu2 [14:49] it's "include changes since the given one" [14:49] yeah [14:49] i was confused with what that flag was for :) [14:50] kenvandine: surprising that it's new to you -- you never merged a package with debian? [14:50] i have, but it has been a while [14:50] sorry, I would have been a bit more verbose then [14:50] :) [14:50] speaking of which now is the right time to do merges :p [14:51] call to everybody in the team there ;-) [14:51] yeah... :) [14:51] pitti, uploaded [14:52] thanks [14:52] speaking of merges [14:53] mterry, could you do the anjuta 2.32 one? [14:53] mterry, hey btw ;-) [14:53] hello world! [14:53] seb128, for natty? sure [14:55] seb128, might want to ask a LOSA to kill off the gtk+3.0 build in the gnome3-builds PPA... it's been running for two days :P [14:55] also, good morning :) [14:55] seb128: You mentioned some problem with latest anjuta which was being fixed before maverick release, has it been fixed now? [14:56] mterry, yes, thanks [14:56] bilalakhtar, did I? [14:56] cyphermox, I pinged the soyuz guys and lamont about it yesterday [14:56] seb128: yes, you told me when I offered to upgrade it in maverick [14:56] bilalakhtar, there was some build issues due to the new vala [14:56] but debian did the update since [14:56] we should merge on their version [14:56] and see if it builds [14:57] seb128: okie dokie, not my work since mterry took it :D Go ahead! [14:57] there is enough merges to keep everybody busy [14:57] :) [14:57] just pick any other one ;-) [14:58] yup [14:58] doko: there? [14:59] doko: I didn't understand what you meant in the cdebootstrap change === almaisan-away is now known as al-maisan [15:02] seb128, with non-Desktop packages, I would do something like 'bzr merge-package lp:debian/blah/blah'. I don't see any documention in DesktopTeam/Bzr for merges. Do I just do it old-school way and end up with debian/* changes in bzr? [15:03] I'm doing it the old way but maybe didrocks or pitti have better ways [15:03] didrocks, pitti: ^ [15:04] mterry, but for things in universe don't bother with the desktop team vcs workflow [15:04] mterry: I'm using merge-package most of the time [15:04] like anjuta [15:04] mterry: but again, do as you want, I guess :) [15:04] mterry: merge-package won't work for our debian/ only branches AFAIK [15:04] it's for the full source branches with integrated tarballs [15:05] pitti: I think he's talking about "non-desktop packages" == packages from lp:ubuntu/<…> so full source branch [15:05] mterry: if anjuta doesn't have a debian only ubuntu branch, and you are instead using lp:ubuntu/anjuta, then please feel free to try, of course [15:05] why not make the changes in a full branch and then copy debian dir? [15:05] seb128, but anjuta has a ~desktop-team branch [15:05] oh, it has? [15:05] if VcsVcs-Bzr: https://code.launchpad.net/~ubuntu-desktop/anjuta/ubuntu [15:05] s/if Vcs// [15:06] Right, so sounds like I do traditional way then [15:06] (unless I'm hearing that we don't actually care-about-having/want-to-have a ~ubuntu-desktop branch for anjuta?) [15:06] bilalakhtar, that could work too [15:07] Is it anjuta? Isn't that in universe? [15:07] kenvandine: hi ken; i've got a fix for https://bugs.launchpad.net/indicator-me/+bug/641252 (actually a duplicate of another bug i had a branch ready for) [15:07] Launchpad bug 641252 in indicator-me (Ubuntu) (and 1 other project) "Text in broadcast text field doesn't update or disappear automatically (dup-of: 655252)" [Medium,Triaged] [15:07] Launchpad bug 655252 in indicator-me "Hint not always hidden when the broadcast field is in use (affects: 14) (dups: 5) (heat: 65)" [Low,Fix released] [15:07] kenvandine: you can cherry pick on trunk now [15:07] Just the other day seb128 told me to remove Vcs-Bzr field from deskbar-applet since that was in universe [15:07] mterry: ^^ [15:07] kenvandine: can you start the SRU process for this fix please? [15:08] mterry, I don't really have a strong opinion, whatever is easier for you [15:08] it doesn't really make sense for universe packages since motus don't have commit right there [15:08] OK, easiest is probably to remove the special branch and converge on standard method for universe [15:08] davidbarth, great [15:08] Thanks all! [15:09] mterry, well consider anjuta updates are part of you opportunistic hacker pack so set whatever workflow will be easier for you [15:09] mterry, np ;-) [15:09] seb128, :) fair. What else besides anjuta and glade-3 should I be looking at? [15:09] and quickly [15:09] gedit? [15:10] I just did that merge btw [15:10] but if you want to maintain it from now on you are welcome [15:10] I think some of yours specs have gedit hacking [15:10] :) [15:10] to make it a better editor [15:10] or at least integrate it better in the quickly workflow [15:10] Seems tenuous, but I'll take it. :) [15:10] thanks ;-) [15:11] you can take devhelp as well [15:11] I think that's it but we will not stop you claiming other sources if you want some [15:11] ;-) [15:15] k [15:16] davidbarth: #627744 is the fallback [15:16] bug #627744 [15:16] Launchpad bug 627744 in tomboy (Ubuntu) (and 1 other project) "Tomboy note names are blank in the Application Indicator fallback menu (affects: 13) (dups: 2) (heat: 155)" [High,In progress] https://launchpad.net/bugs/627744 [15:23] seb128, lp:anjuta doesn't have a debian/ directory... I'm assuming this is because of the ~ubuntu-desktop branch, and since the plan is to drop that, to add it back [15:23] jcastro: ok, i see karl is on it now [15:24] mterry, lp:anjuta is the upstream import [15:24] mterry, you want lp:ubuntu/anjuta? [15:24] duh! stupid mental typo [15:24] ;-) === bjf[afk] is now known as bjf [15:30] pitti: on bug #657837, I should also add that we have an inconsistent behavior as well: if you choose notify on "all folder" in evolution, you get notification on the local inbox too, where you don't get when you choose inbox only [15:30] Launchpad bug 657837 in evolution-data-server (Ubuntu Maverick) (and 2 other projects) "Broken message indicator with Evolution (affects: 9) (dups: 6) (heat: 72)" [High,Triaged] https://launchpad.net/bugs/657837 [15:32] didrocks: okay [15:35] seb128, Cimi: it took forever but I ran into again just now : to easily get a git snapshot for a package, you can add /usr/share/gnome-pkg-tools/1/rules/gnome-get-source.mk to debian/rules and use version+gitYYYYMMDD.GITREV [15:35] thx [15:36] oh ok [15:36] means you need to autoreconf though, afaict [15:38] cyphermox: do you have an example package? [15:38] cyphermox: just to be sure to do it in the right way ;)) [15:38] yeah, synaptic is a good one ;) [15:38] ok [15:39] there's only one thing though, as I said you need to run autoreconf since it's a snapshot, not a tarball from make dist, so you need to add some more black magic [15:39] a new context menu for gnome-shell needs to be accepted upstream before being added to Ubuntu, right? [15:40] CImi: that would generally be: autoreconf -i under pre-build::, but ymmv [15:42] james_w: ping [15:42] * didrocks hugs pitti for all the SRU work :) [15:43] (ugh -- sru folder had 250 mails since yesterday) [15:43] do you really read the emails there? You don't only go and check the queue? [15:43] I need to [15:44] for verification results, regression reports, ACK requests, etc. [15:44] I can just skim most of them, of course [15:44] yeah, but still a scary number :/ [15:45] you need procmail + perl magic [15:45] there is still a bunch of commit we should backport [15:46] if some people are still on maverick and feel like doing some [15:46] I will try to do those on my old laptop next week otherwise [15:46] i guess i should probably start applying for motu soon too [15:47] seb128: did you see my question above? [15:47] micahg, no [15:47] can you repeat? [15:47] seb128: k, for a new context menu in gnome shell, we need it to be accepted upstream first, right? (bug 661106) [15:47] Launchpad bug 661106 in gnome-shell (Ubuntu) "gnome-shell clock applet needs menu option to change time (affects: 1) (heat: 6)" [Undecided,In progress] https://launchpad.net/bugs/661106 [15:48] yes [15:48] seb128: k, thanks [15:49] yw [15:53] hi dobey [15:55] james_w: hey. i was looking at backporting a couple packages from maverick to lucid for u1, and it looks like the bzr repos of a few things aren't up to date. in particular, couchdb and python-django seem to be fairly out of date [15:55] dobey, do you know how to check what happened with them yourself? [15:56] seb128: what kind of commit for backporting are you talking about? [15:56] james_w: not really, no [15:56] didrocks, one gvfs one, one rhythmbox one [15:56] I think chrisccoulson had his pango update to be sponsored [15:56] dobey, package-import.ubuntu.com [15:56] can do the rhythmbox one [15:57] dobey, and you will find that https://bugs.launchpad.net/udd/+bug/653312 is the cause of couchdb failing to import [15:57] Launchpad bug 653312 in udd "Import fails with NoSuchRevision (affects: 1) (heat: 5)" [High,Triaged] [15:58] seb128 - yeah, i prepared it in bzr, but robert_ancell updated the branch for natty already [15:58] python-django hasn't failed it seems, so I'll just prioritise that job for you [15:58] chrisccoulson, oh ok [15:58] so, it's not the most recent commit which needs sponsoring [15:58] which is a bit confusing [15:59] didrocks, check with pedro_ he had some bugs [15:59] didrocks, or check the "bugs with upstream task closed" list [15:59] chrisccoulson, ok [15:59] seb128: ok, I was looking for git first, thanks :) [15:59] there is quite some commits in git [15:59] several could be interesting to backport [15:59] james_w: hmm, ok, thanks. i'll bookmark that page :) [16:00] I'm afraid the ipod fixes are a little bit large for an SRU [16:00] james_w: any idea about the bug affecting couchdb? [16:01] dobey, nope, sorry, I haven't investigated yet [16:01] dobey, please comment on the bug that couchdb is important to u1 [16:02] will do [16:31] didrocks: around? [16:32] Shred00: yeah, please don't ask to ask, just ask :) [16:32] didrocks: so, yeah. i think i just had a stale .pc dir [16:32] but in doing a dpkg-rebuildpackage, i end up with this autogenerated patch at the end of the series representing a diff against the tarball. [16:33] Shred00: what are you tring to do? [16:33] which wants to be (un-)applied during unpatch. how can i avoid creating that autogenerated patch? [16:33] you didn't answer to: [16:33] 15:01:36 didrocks | Shred00: are you using exactly my branch or do you have your own setup and branch? [16:34] didrocks: my tree is actually from gnome git and i have the EVOLUTION_DATA_SERVER_2_30_3 tag checked out [16:35] Shred00: why? don't you want rather contributing to the ubuntu branch? do you have additional patch that you are required? [16:35] didrocks: yes and yes [16:35] Shred00: yes like "you don't want to contribute to the ubuntu branch?" :) [16:36] the /debian dir in my tree is actually from bzr [16:36] no, yes like i want to contribute and yes i have an additional patch. [16:36] Shred00: can you be more explicit? we can see if we can include it to ubuntu if that's an interesting one. Without more detailed it's hard to help you :) [16:37] if you have the debian/ dir from our bzr [16:37] and the git repo [16:37]