=== asac_ is now known as asac [07:58] morning mvo & tseliot [07:58] morning didrocks :-) [07:59] hey didrocks and tseliot [07:59] didrocks: the sponsoring for naitulis-sendto is still open? [08:00] hey mvo [08:01] mvo: yes, seb128 told me you will love sponsor it :) [08:02] didrocks: heh :) sure [08:12] Good morning [08:26] Guten Tag pitti [08:26] hey didrocks [08:43] hey tseliot [08:43] hey pitti :-) [08:44] hello pitti tseliot [08:44] hi seb128 [08:47] didrocks: I will do the sponsoring once I sorted some issues with the new python, I got some errors during this mornings update and it seems like all my packages (well, all python packages) needs updates in how setup.py is used. [08:52] pitti: guten morgen [08:52] hey davidbarth [08:52] bonjour [08:52] pitti: there is a new release notify-osd ready for jaunty [08:53] hello [08:53] if someone was kind enough to test the latest bluez release (4.32) in my ppa, the previous one was crashy [08:53] davidbarth: nice; do you think it has time until this afternoon? I'd like to teach kenvandine_wk how to handle this [08:54] pitti: sure, i still have a few gsd/gpm patches to update, this afternoon will be perfect [08:55] crevette: bluez or also the bluez-gnome part? [08:55] my ppa is https://edge.launchpad.net/~bmillemathias/+archive/ppa, I 'd like to have some feedback before asking FFE, I tested on my side, but I think it worth some test [08:55] davidbarth, only bluez [08:55] bluez-gnome is dead [08:55] uh!? [08:55] it is going to be replace by gnome-bluetooth [08:56] heay kind of tricky [08:56] http://www.hadess.net/2009/02/we-have-fork.html [08:56] crevette: what about the thing in the panel that uses libnotify notifications? is it also in the new bluez? [08:56] davidbarth, bluez-gnome [08:56] but that's not going to be shipped in Jaunty? [08:58] I don't know [08:58] I need to see that with hadess [09:00] davidbarth, you're the guy working on new notification system right? [09:00] crevette: yes, one of them that is [09:01] and so if we provide patches for bluez-gnome, i'd like to be sure that we're patching the right package... ;) [09:01] davidbarth, the code is almost the same I guess [09:01] crevette: what would be the alternative package to check then? packages in your PPA? [09:02] davidbarth, I guess we can continue with bluez-gnome for jaunty if there is no release before [09:03] davidbarth, there is no alternative package (I guess you're talking about gnome-bluetooth), hmm [09:03] actually gnome-bluetooth already existbut it does another purpose, it does Obex file sharing [09:03] but now it is deprecated in favoor of gnome-user-shaer [09:04] (bluetooth on GNOME is kind of difficult to track) [09:04] :) [09:04] crevette: dunno; between seb128, bastien and you, when will you be selecting what goes into jaunty? [09:04] bastien is from RH so I guess I won't take decision for ubuntu :) [09:05] and I'm not a core developer so but I think someone needs to see that with Bastien [09:07] crevette: ok, i'll ask cody (bratsche) to take a look at gnome-bluetooth too; but for the moment we're staying with bluez-gnome for our patches [09:07] crevette: thanks for warning me of the possible shift [09:07] hey no problem :) [09:07] davidbarth, about our patch you'd be interested with gnome-user-share also wich use actions in notification [09:07] I know that because I did the patch upstream :) [09:10] crevette: ;) good to know; it's one of the tricky interaction cases that mpt is on [09:10] why ? honnestly I don't know the details of the new notification implementation [09:15] crevette: because it both makes sense to request user feedback when accepting a file upload for security reasons, but at the same time it's a bit like receiving a mail: you may want to defer the time when you actually want to read it [09:16] the notification is displayed once the file is received actually [09:16] and you have 2 action, display the file or reveal it in the file manager [09:16] actions [09:21] crevette: interesting, we'll probably get back to you on that then; but we're not there yet. thanks [09:21] okay [09:21] crevette, for that I suggest having a "Received Files" or similar window that lists the files you've received so you can open/reveal them at your leisure [09:21] That would also work better for the case where you receive half a dozen files in quick succession [09:22] mvo: ok, no problem :) [09:22] instead of having a cascade of bubbles [09:22] they would just be items in the window. [09:23] mvo: I didn't have to change anything in setup.py for my previous upload (gnome-python) to make it builds with the new python version. Just change some paths in *.install files for {dist,site}packages [09:23] just my opinion, the notification bubble is not large enough [09:24] crevette, there's a similar example here: https://wiki.ubuntu.com/NotificationDesignGuidelines#Normal%20window [09:30] didrocks: its using autotools (configure) instead of distutils it seems, I think thats the explaination [09:35] mvo, hello, would you mind merging https://code.edge.launchpad.net/~bmillemathias/utils/ubuntu-bluez-4.x/+merge/3982 ? I don't know if I did the right values (like the reviewer) [09:38] mvo: yeah, that's right. distutils have been patched. Can you write somewhere in the wiki what you do so that we can use it again for other packages in the same configuration, please? [09:43] didrocks: I try to talk to doko about it, I think its something that should go to ubuntu-devel-announce [09:44] crevette: give me a sec, I have a look [09:44] crevette: https://code.edge.launchpad.net/~ubuntu-dev/utils/bluez-4.x <- says "this branch has not been pushed yet" [09:45] crevette: what did you base your merge on? I need to know what to checkout :) [09:48] where can I push nautilus-sento-universe package? in some kind of ~ubuntu-deskop-universe? :/ [09:50] mvo, perhaps I didn't understand the process of merging, I just wanted you to push the latest commit of https://code.edge.launchpad.net/~bmillemathias/utils/ubuntu-bluez-4.x to lp:~ubuntu-dev/utils/bluez-4.x [09:50] mvo, but actually you can wait as 4.31 won't be packaged, as it is too crashy [09:52] crevette: oh, I think the confusion is that there is a "bluez-4.x" and "ubuntu-bluez-4.x" branch [09:53] crevette: and one of them is not pushed [09:53] superm1: could you remove https://code.edge.launchpad.net/~ubuntu-dev/utils/bluez-4.x ? LP says the branch is not pushed yet and it looks like https://code.edge.launchpad.net/~ubuntu-dev/utils/ubuntu-bluez-4.x is the right one? [10:28] davidbarth, apparently we will have a release of gnome-bluetooth soon, so I think it can replace bluez-gnome [10:52] mvo: thanks for the sponsoring :) [10:53] mvo & seb128_ (hi seb!): an idea on that: where can I push nautilus-sento-universe package? in some kind of ~ubuntu-deskop-universe? :/ [10:54] didrocks: because there is no corresponding product on launchpad? [10:55] seb128_: didn't check yet, but I was just wondering about *where* to push. MOTU will not be available to push in ~ubuntu-desktop bzr repository and will ping you for that [10:55] s/available/able [10:55] didrocks: don't use bzr? [10:56] seb128_: so, let's say we only use bzr for desktop team for packages in main ? [10:56] right [10:56] or talk to mvo he's the one promoting bzr for everything ;-) [10:56] seb128_: ok :) [10:57] bzr [10:57] ! [10:57] * mvo leaves for lunch and lets seb128_ sort out the porblme ,) [10:58] seb128_: FYI, I updated eel, but I have a question. There are some library changes (dropping symbols), but no soname changes (only minor version change). What to do? cf http://paste.ubuntu.com/125208/ [10:58] didrocks: you could put it under ~ubuntu-dev [10:59] james_w: I just didn't understand if it was still experimental or if we have commit rights on it? (and it's updated automagically if someone is not using bzr?) [10:59] didrocks: nothing, they don't assure abi stability for this library [10:59] didrocks: it's deprecated anyway nautilus stopped using, etc, it's just for applications not updated yet [11:00] crevette: ok, so i'll be watching closely [11:00] seb128_: ok, but the "normal" process is to bump soname in this case, right? (if they don't say "we don't bother" ;)) [11:00] yes [11:00] hey pedro_! [11:00] didrocks: nothing is changing there [11:00] didrocks: it works the same way as pushing under ~ubuntu-desktop [11:00] seb128_: so, I will open the sponsoring request in the afternoon [11:00] hello seb128_! [11:01] didrocks: ok good [11:01] pedro_: you were on holidays? I was starting to wonder what happened to you, good to see you back ;-) [11:01] james_w: ok, so, it's not updated if someone don't use bzr, for the moment, right? [11:01] * didrocks is sure that james_w has an hilight on bzr ;) [11:02] seb128_: yeah even the bots need to take those :-P. thanks you, it's nice to be back [11:02] didrocks: correct [11:02] * pedro_ feels like new [11:02] the fist one :-) [11:02] james_w: :-) [11:02] james_w: ok, thanks :) [11:02] pedro_: enjoyed your holidays? [11:02] * seb128_ hugs pedro_ [11:03] seb128_: yup, went to the south with my parents, haven't taken holidays with them since mm 4 years or so, so it was amazing :-) [11:03] * pedro_ hugs seb128_ back [11:04] pedro_: sounds excellent! [11:05] pedro_: mark all bug emails as read or you will spend the week catching up with that backlog [11:06] seb128_: ok! will do it [11:08] hey pedro_, welcome back [11:08] hello pitti!, thanks you :-) [11:08] seb128_: I think we need to sponsor those netbook screen size fixes by Thursday (UIF) [11:08] seb128_: I'm grabbing the pidgin one now, FYI (just to avoid clashes) [11:09] pitti: ok thanks, I'm busy with the new GNOME, tarballs due today [11:09] seb128_: ok; if I touch something GNOMEish, I'll ask you before then [11:09] pitti: thanks === seb128_ is now known as seb128 [11:09] seb128_: just uploaded policykit-gnome (but I don't think that's affected by your updates) [11:10] no it's not === davidbarth is now known as davidb4 === davidb4 is now known as davidbarth [12:09] seb128: bug #336657 when you will have some time :) [12:09] Launchpad bug 336657 in eel2 "Please, sponsor eel2 2.25.91 to jaunty" [Undecided,New] https://launchpad.net/bugs/336657 [12:26] didrocks: ok, want other updates? [12:36] seb128: with pleasure :) [12:37] seb128: btw, I can't remember if you found a workaround for gnome-python-extras and the doc, or if we wait for usptream to respond about the html doc? [12:38] didrocks: workaround is to not install those files for now [12:38] didrocks: http://download.gnome.org/sources/yelp/2.25/yelp-2.25.1.tar.gz [12:38] didrocks: http://download.gnome.org/sources/glibmm/2.19/glibmm-2.19.3.tar.gz [12:40] seb128: ok, begin some work on them. For gnome-python-extras, do you want that I propose a new version excluding the html doc for the right .install file? [12:40] didrocks: open the bug upstream first, I'm not sure if we should wait for a new version or not [12:40] seb128: oki [12:41] * didrocks is fidding its "Contribution page" for UDS sponsoring first :) [12:41] feeding* [12:47] mvo: do you think you could review bug #327465 this week? it's a sponsoring request waiting for a while and it would be nice to have it reviewed before the interface freeze this week [12:47] Launchpad bug 327465 in gnome-control-center "HIG problem with my previous fix" [Low,New] https://launchpad.net/bugs/327465 [12:50] seb128: so am I the only person with weird ssh-agent borkages in jaunty? :) [12:50] Ng: yes [12:51] we didn't get ssh agent complains since the distro sprint some weeks ago [12:51] and it's working fine on all my boxes [12:52] seb128: does $SSH_AGENT_PID point at seahorse-agent or ssh-agent? [12:52] seahorse [12:52] mine is pointing at ssh-agent, but even with use-ssh-agent disabled in Xsession.options it still didn't seem to all work properly [12:52] hum [12:52] "/usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session /usr/bin/pulse-session /usr/bin/seahorse-agent --execute x-session-manager" [12:52] in fact [12:52] I'm convinced I shouldn't have both running [12:52] $ echo $SSH_AUTH_SOCK [12:53] /tmp/keyring-i1WBlI/socket.ssh [12:53] yeah I have that process to [12:54] according to lsof, no process has my socket.ssh open [12:57] seb128: I have a look now [12:57] mvo: thanks [12:58] Ng: gnome-keyring has mine open, maybe yours crashed or something? [12:59] I just rebooted with use-ssh-agent disabled and it's generally still all not working [12:59] I would blame something in your user config [12:59] as soon as I log in and fire up ssh I get asked to unlock a keyring (should have happened when I log in), ssh says it failed to read the auth details from the socket, and asks for my password [12:59] but dunno what ;-) [13:00] I would be blaming the software for breaking on what was previously a working config ;) [13:00] right [13:00] but you might have something which trigger the issue [13:00] no clue what that is though [13:00] it must be unlocking the keyring to some extent because NM doesn't prompt for wifi passwords [13:00] open a bug on bugzilla.gnome.org if you want they are pretty responsive usually [13:03] seb128: k, ta [13:08] seb128: huh, do you have two seahorse-agents running? [13:10] Ng: not sure, I've some dbus... lines and one seahorse-agent line, doesn't matter for ssh since seahorse doesn't do ssh anyway [13:11] * kenvandine_wk waves [13:12] james_w: with jauntys bzr-buildpackage, I'M unable to build lp:~ubuntu-desktop/gnome-control-center/ubuntu - it seems like the tarball is unpacked to the wrong level, do you have any idea? [13:12] mvo: python2.6 hates me [13:13] james_w: heh :) not just you ;) [13:13] I can't get python2.6 installed to debug either [13:13] I spend my morning updating all the setup.py, debian/rules for my stuff [13:13] I'm going to switch to a chroot to to that in a minute, once I've finished my current task [13:13] james_w: what errors do you get? have you talked to doko about them yet? [13:14] mvo: no errors [13:14] james_w: no rush :) [13:14] silent breakage [13:14] woah [13:14] even better :( [13:14] asac: was debugging it earlier in #ubuntu-devel [13:14] using "python2.5 /usr/bin/bzr" apparently works [13:14] mvo: i repointed my link to python2.5 for now [13:15] works well again [13:15] but since you need to work on python2.6 not sure if its an option for you [13:16] * asac feels scared about libc update arriving ;) [13:16] wish me luck [13:17] asac: thanks! not a good option, but good to know [13:17] james_w: thanks, I just checked the backlog and found it [13:18] mvo: command-not-found and gnome-app-install failed to upgrade [13:18] ;) [13:18] hu? [13:18] oh [13:18] seb128: yeah gnome-keyring-daemon is segfaulting [13:18] asac: could you please give me details [13:18] i think thats because of the link ;) [13:18] mvo: ValueError: /usr/bin/python does not match the python default version. It must be reset to point to python2.6 [13:18] Ng: good, use apport to report the crash ;-) [13:18] asac: the joy of the python world [13:18] ;) [13:19] asac: *no comment* [13:19] i always felt that using python everywhere reduces the overall quality of desktop ;) [13:19] * Ng wonders why apport isn't whining at him these days [13:19] * asac hides [13:21] I'm also not really sure if I want to upload the guts of my keyring daemon to launchpad :/ [13:22] Ng: use sudo apport-retrace .crash locally and open a bug attaching the clean stacktrace [13:22] ah nice [13:22] thanks [13:23] Ng: you can try to use gdb and give the first function there so we can look if that's a duplicate quickly [13:24] unhelpfully the first function is in a -dbg package I don't have installed [13:24] (I assume, it's showing up as ???) [13:24] the second is egg_secure_realloc () [13:26] Ng: could be bug #332342 [13:26] Launchpad bug 332342 in gnome-keyring "gnome-keyring-daemon crashed with SIGSEGV" [Medium,Incomplete] https://launchpad.net/bugs/332342 [13:28] hmm, it looks a bit different [13:28] Ng: open a new bug then [13:28] will do :) [13:28] davidbarth: hm, is there a new LP project page for notify-osd now? it's apparenlty not "notify-osd" :) [13:28] seb128: I replied to the sponsoring bug, patches does not apply cleanly anymore and bzr-builddeb does not like me anymore ,) [13:29] kenvandine_wk: davidbarth has a new notify-osd upstream version; this is a bzr-maintained package, and would be an excellent exercise/mentoring matter [13:29] mvo: ok thanks and sorry for the nag about this one [13:29] pitti: it is: https://launchpad.net/notify-osd [13:29] kenvandine_wk: I need some lunch first, can we do that in an hour or two? [13:29] pitti: great! [13:29] seb128: np, thanks for the reminder [13:29] yes [13:30] (and sorry for my lack o fattention) [13:30] davidbarth: ah, apparently I mistyped then [13:31] pitti: bug #336640 [13:31] Launchpad bug 336640 in deskbar-applet "deskbar-applet crashed with SIGSEGV in PyType_IsSubtype()" [Undecided,Invalid] https://launchpad.net/bugs/336640 [13:32] pitti: shouldn't the retracer clean the coredump.gz in such cases? [13:33] seb128: I guess it should, yes [13:34] seb128: in other news, launchpadlib just started to work on ronne \o/ [13:34] cool! [13:34] thus we can move from p-lp-bugs to launchpadlib [13:34] yeah! [13:34] but I need some lunch first, 14:30 already... [13:34] pitti: enjoy your lunch [13:34] hello everyone ! [13:38] lut huats [13:39] huats: how are you? [13:39] seb128: better [13:39] good! [13:39] huats: salut! [13:39] not completly healer [13:39] but better :) [13:39] thanks seb128 [13:39] what about you ? [13:39] hey james_w ! [13:39] I'm good thanks [13:40] seb128: don't bother to speak in english with james_w, he speaks a perfect french... [13:40] huats: would you be able to take a look at pywebkitgtk today? [13:40] james_w: it is on my todo list [13:40] huats: excellent [13:40] huats: http://bugzilla.gnome.org/show_bug.cgi?id=573753 might be of interest to you [13:40] james_w: I am trying to tackle it today or tomorrow.. [13:41] Gnome bug 573753 in codegen "DeprecationWarning under python 2.6" [Normal,Unconfirmed] [13:41] james_w: I have a look too [13:45] davidbarth, bratsche is working for canonical ? [13:45] crevette: Hi. Yes. [13:45] ah okay [13:45] hello bratsche [13:46] crevette: Hey [13:47] I can't seem to get my phone and laptop to work with bluetooth, so I'm not sure if I can test any patch I can come up with here. :/ [13:47] bratsche, you're assigned to test bluetooth ? [13:47] :) [13:47] I'm assigned to patch bluez-gnome for the notify stuff. [13:48] So unless someone else has some bluetooth hardware to test with, I think I'm just going to have to take a shot in the dark on this one and hope it works right. :/ [13:51] bratsche, what is the brand of you phone ? [13:53] G1 [14:04] mvo: you are the kvm expert. how can i quickly get a hardy kvm image that just works? [14:07] asac: ubuntu-vm-builder kvm hardy --rootsize=20000 [14:07] asac: but I think there are also pre-build ones around, give me a sec [14:12] mvo: good. and how do i get X setup? is all ready for use? [14:12] asac: oh, that is a minimal one [14:12] asac: hm, I could upload you one of mines with X setup etc [14:12] mvo: are those private? [14:12] mvo: how hard is it? [14:13] can i just go there and say: sudo apt-get install ubuntu-desktop? [14:13] mvo: do you know how well that works on amd64? [14:14] * asac trashes a fedora VM to get some space [14:15] asac: with the latest updates it works fwell for me [14:16] asac: with the ubuntu-vm-builder ones you can just do apt-get install ubuntu-desktop? [14:16] (no ? at the end :) [14:16] hah [14:16] ok [14:16] i will try that asap [14:17] * Ng being stupid, where is it pitti's pool of debsyms packages lives? [14:17] Ng: its ddebs.ubuntu.com [14:17] ta [14:19] Ng: https://wiki.ubuntu.com/DebuggingProgramCrash has some documentation [14:20] thanks [14:20] erk, it exploded a little over libc6 [14:20] do those ddebs lag a little? [14:20] Ng: yes, they do, a couple of hours [14:21] ok. I sucked in a new libc6 just before lunch, so I'll check back on this later :) [14:21] Ng: ddebs.u.c. is a horrible hack, but the best we can get without proper soyuz support :/ [14:21] heh [14:21] hack or not, it's a truly fantastic idea [14:36] mvo, sure. trashed. [14:37] superm1: thanks [14:39] mvo, i seem to think the last few uploads might not have been put into bzr when sponsored to the normal tree. they were uploaded as a diff rather than a merge request, but they should have been fairly minimal [14:43] superm1: thanks, I will remember that when doing a merge [14:44] seb128: ok if I sponsor bug 336518? [14:44] Launchpad bug 336518 in brasero "Please sponsor brasero 2.25.92 (main) into Jaunty" [Undecided,New] https://launchpad.net/bugs/336518 [14:44] pitti: yes, thank you [14:48] seb128: ok if I sponsor bug 336657 ? [14:48] Launchpad bug 336657 in eel2 "Please, sponsor eel2 2.25.91 to jaunty" [Undecided,Confirmed] https://launchpad.net/bugs/336657 [14:48] pitti: yes, thank you ;-) [14:54] pitti: hope you will like it :) [14:55] didrocks: at some point we should move the bzr to ~ubuntu-desktop, but I won't worry about this for now [14:56] pitti: ? if you accept the sponsoring, you can then bzr push to ~ubuntu-desktop, that's the goal :) When the branch is created, I generally ask for merge as I can't write into it [14:56] didrocks: ok, will do [14:59] didrocks: do you know the "UNRELEASED"/dch -r/debcommit -r schema? [14:59] pitti: sincerely, no. I only debcommit the change at the end [15:00] didrocks: so: [15:00] - only commit one change at a time, not an entire heap [15:00] however, the change should be consistent [15:01] so, in your case, it was correct (since changing build-deps goes along with updating upstream version) [15:01] didrocks: while you are working on a new upload, keep the changelog target as UNRELEASED, not jaunty [15:01] once you think that you did enough work and it should be uploaded, do [15:01] dch -r [15:01] -> changes UNRELEASED to jaunty [15:01] and [15:01] debcommit -r [15:02] -> commits the UNRELEASED->jaunty change to bzr, and adds a version number tag [15:02] didrocks: that makes it easy to reconstruct previous uploaded versions from the bzr history [15:02] hum, I don't get it, there will be 2 log revision for each upload? [15:02] didrocks: also, if you check out a branch, you immediately see whether there are commited changes which aren't uploaded yet (UNRELEASED) or whether you have to use dch -i to start a new changelog version (jaunty) [15:03] didrocks: no, there will be one commit for each change to the package, and one commit per upload [15:04] pitti: for each "consistent change", I have to tell it in the changelog, no? [15:05] didrocks: right [15:05] didrocks: and "debcommit" will grab the changelog entry from debian/changelog, and use it as bzr changelog [15:05] didrocks: look at http://bazaar.launchpad.net/~ubuntu-core-dev/jockey/ubuntu/ [15:05] didrocks: there you see individual changes, and which revisions got uploaded as which package version [15:06] pitti: let me check this (slow ;)) [15:06] didrocks: bzr get lp:~ubuntu-desktop/eel/ubuntu/ [15:06] didrocks: and check bzr log [15:06] pitti: that's what I am currently doing :) [15:06] and look at [15:06] bzr diff -c 5 [15:07] whoops [15:07] I messed up [15:07] yeah, I corrected it myself ^^ [15:07] there was a vcs-bzr already [15:08] but a wrong one [15:08] really? I put it :/ [15:08] upstream project is called eel, not eel2 [15:09] oh, crap, I did it offline and didn't check atm on launchpad [15:09] didrocks: please rm -r above checkout [15:10] didrocks: fixed, please bzr get it again [15:10] meh! [15:10] I HATE HATE HATE control.in [15:11] pitti: normal, when you aren't get used to them :) [15:12] didrocks: ok, please get it again (or use bzr pull --overwrite) [15:12] pitti: how can you fix this? bzr uncommit and then --force_overwrite ? [15:12] it should finally be good now [15:13] didrocks: right [15:14] didrocks: ok, uploaded; thanks! [15:14] pitti: thanks a lot for the explantion. I understood from the jockey's example [15:14] pitti: just one question [15:14] didrocks: please go into your branch and do bzr pull lp:~ubuntu-desktop/eel/ubuntu/, so that your branch becomes consistent with the ubuntu-desktop one [15:15] didrocks: from now on, sponsoring from your brnach will be very easy [15:15] pitti: is there an option for dch to put UNRELEASED when dch -v... or dch -a... ? [15:15] didrocks: usually you just need it with -i [15:15] I use dch -iDUNRELEASED [15:15] didrocks: yes, -D [15:16] pitti: thanks. I push it now :) [15:17] pitti: so, I will change https://wiki.ubuntu.com/DesktopTeam/Bzr. The "one feature = one commit" is great for cherrypicking [15:17] didrocks: oh, didn't know about that page; thanks [15:17] didrocks: yes, it is indeed [15:18] didrocks: I'll look at that page, too, since I haven't used bzr-builddeb so far [15:19] pitti: if there is any other mistake I put in this page, you can ping me :) [15:39] seb128: i saw a comment from a gvfs developer that claims that touching files on smb should work now as of gvfs 1.1.1 but still doesn't seem to work on Ubuntu [15:39] calc: where did you read that comment? [15:39] seb128: https://bugzilla.redhat.com/show_bug.cgi?id=479199#c28 [15:39] bugzilla.redhat.com bug 479199 in gvfs "posix apis unreliable on files mounted over gvfs, e.g. truncate, open, causes OpenOffice.org to fail to save." [Medium,Modified] [15:40] seb128: it came up during the discussion of the truncate bug in gvfs [15:40] ok, dunno about that [15:40] did you try over fuse or over smb? [15:42] yea it still gives operation not supported as of our current 1.1.6 [15:42] seb128: ok if I sponsor bug 327933 ? [15:42] Launchpad bug 327933 in gnome-python "Please, sponsor gnome-python 2.25.90 to jaunty" [Wishlist,Confirmed] https://launchpad.net/bugs/327933 [15:42] pitti: yes ;-) [15:43] pitti: thanks for all the sponsoring ;-) [15:43] * seb128 hugs pitti [15:43] I'm just in the mood [15:43] seb128: I was actually trying to sponsor all the netbook screen size fixes, but I did one, left evo for you, and the rest already seems to have been done.. [15:44] pitti: right, I did some previous week [15:44] seb128: just for the record, eel2 is in bzr now (from didrocks' branch) [15:44] seb128: are you okay with having more packages in bzr officially? [15:44] pitti: right [15:44] seb128: gnome-python is same situation (about to push didrocks' branch to ~ubuntu-desktop) [15:45] or shall we not have an official branch, and just leave didrocks to use his for his own purposes? [15:45] pitti: as said didrocks is adding each package he's working on to bzr following mvo recommendation so I try using it too now [15:45] pitti: add those to the ubuntu-desktop team [15:45] that's handy for review and sponsoring ;-) [15:45]