=== espacious_ is now known as espacious === ember_ is now known as ember === asac_ is now known as asac [07:56] Good morning [07:58] morning pitti o/ [08:13] hey didrocks [08:28] hello seb128, did you have a nice week-end? [08:29] hey didrocks [08:29] yes, too short as usual but good, you? [08:29] seb128: yes, very restful :) [08:36] hey seb128 [08:44] hello pitti [08:44] lut huats [08:45] hello seb128 and pitti [08:45] huats: how are you this week? [08:45] * pitti hugs seb128 and huats [08:45] seb128: I am feeling better ! [08:45] thanks ! [08:45] * seb128 hugs pitti [08:45] how are you ? [08:46] * huats hugs pitti and seb128 too ! [08:46] huats: good thank you [08:46] * huats even hugs the mighty didrocks [08:50] pitti: the indicate-applet needs an handle, how would you remove it from the configuration or move it otherwise? [08:50] seb128: if you see it, you can move it; if you don't see it, what does its position matter? [08:50] update-notifier is exactly the same [08:50] pitti: how can you move it when you see it without using the handle? [08:50] seb128: do you really like that handle? I find it awful [08:51] pitti: no, update-notifier is a notification area icon, not an applet [08:51] seb128: well, just like any other thing there? middle-click and drag, or right click -> move [08:51] pitti: I don't like the handle, I ask how you move or remove the applet without using it [08:51] seb128: that's a technical detail that an user doesn't need to understand [08:51] pitti: they choiced by design to open the same menu on any click [08:51] it's all just little pictures in my panel [08:51] * pitti thinks in user terms right now [08:51] pitti: try to middle or right click on it [08:52] seb128: I know that it doesn't have a menu [08:52] but it should [08:52] every other applet has one [08:52] they think every other applet is wrong [08:52] and that's one of the things they want to fix [08:52] well, it might very well be [08:52] but jaunty isn't the time to fix them all [08:52] good luck, I tried to fight this battle at distro sprint ;-) [08:53] for the jaunty version we should aim for consistency [08:53] +1 [08:53] right now it's just plain ugly and inconsistent [08:53] as said I tried to convince them during the sprint but maybe they will listen to extra opinions [08:53] seb128: asked the other way round, how do I remove it right now? [08:53] I just have the handle, but it doesn't have a menu either [08:54] it has move and delete items there [08:54] when right clicking on it [08:54] that's similar to the task list [08:54] or the notification area applet [08:54] right-click doesn't do anything for me [08:54] they are both empty when there is no entry and have an handle [08:54] weird [08:54] ah, after then 10th click or so I hit it [08:55] bah [08:55] seb128: I filed bug 339818 for the record [08:55] Launchpad bug 339818 in indicator-applet "do not display tray handle" [Undecided,New] https://launchpad.net/bugs/339818 [08:55] pitti: my comment was in reaction to the bug ;-) [08:55] * didrocks hugs huats back ;) [08:55] I'm just reading my weekend bug emails [08:55] didrocks: you can do the pidgin update if you want [08:55] oh, right [08:56] seb128: ok, I am on it :) [08:58] seb128: would you pind pinging me on jabber? [09:24] seb128: btw, gksu/libgksu are in my ppa, I guess its enough part of gnome to be part of the freeze exception for it? [09:25] mvo: I'm not sure, it doesn't follow upstream freezes, etc, better to ask pitti or slangasek for an exception [09:25] mvo: hello btw, nice to see you back, do you feel better? [09:28] seb128: hello :) better, but not well :( I felt pretty good saturday and was happy that its over and sunday was bad again. today is ok, I'm a bit slow on everything (and feel weak), but otherwise ok [09:29] * seb128 hugs mvo [09:29] * mvo hugs seb128 [09:39] hey mvo :) [09:39] hey didrocks [09:39] mvo: the section "quilt + bzr + autotools = <3" in https://wiki.ubuntu.com/DesktopTeam/Bzr is dedicated to you :) [09:44] didrocks: that is a clever way of doing it [09:48] mvo: just long to proceed when you have to do it (gnome-games, I hate you ^^) :) [09:48] but with the checklist, you can avoid to forget something (like quilt add :/) in the pbuilder chroot and have to begin again (yes, I did it :p) [09:57] pitti: do I need any exception if I want to sync gtkmm-documentation which is a new package in debian? [09:58] seb128: in theory that's an FFE, but that was meant to ease work for archive admins [09:58] seb128: so go ahead [09:58] pitti: and I've delegated to grant desktopish universe exceptions ;-) [09:58] seb128: and if you feel better, hereby I grant it :) [09:58] pitti: thanks [09:58] ah, indeed :) [10:12] vuntz: hey, can join #nautilus when you have a minute? [10:59] seb128: hm, didn't we use to have fuse file systems from gvfs mounts, such as ssh? [10:59] pitti: ls .gvfs? [10:59] empty [11:00] ps ax | grep fuse [11:00] mount | grep fuse -> nothing for gvfs [11:00] seb128: ps> nothing [11:00] $ ps ax | grep fuse [11:00] 16677 ? Ssl 0:00 /usr/lib/gvfs//gvfs-fuse-daemon /home/seb128/.gvfs [11:00] hmm [11:00] is your user in the fuse group? do you have fuse-utils installed? [11:00] hah [11:00] $ /usr/lib/gvfs//gvfs-fuse-daemon /home/martin/.gvfs/ [11:00] fusermount: failed to open /etc/fuse.conf: Permission denied [11:00] fusermount: user has no write access to mountpoint /home/martin/.gvfs [11:01] seb128: seems I'm not [11:01] there you go [11:01] but I thought we obsoleted the fuse group in intrepid.. [11:01] -rw-r----- 1 root fuse 216 2009-01-14 14:35 /etc/fuse.conf [11:01] BWAH! [11:01] that wasn't so in intrepid [11:01] you did IIRC yes [11:01] getfacl /dev/fuse looks good [11:02] and /bin/fusermount is 4755, as it should be [11:02] seb128: okay, I'll look into that [11:02] thanks [11:02] pitti: would it be easy to make apport ignore the totem-video-thumbnailer crashes? [11:03] seb128: yes, but they shouldn't really crash.. [11:03] pitti: well, we get quite some crashers about totem trying to thumbnails video being downloaded [11:04] oh, I understand [11:04] so, incomplete files [11:04] crashes in ffmpeg libs and siretart said those are basically pointless because without a video example to get the crash they can't really be worked [11:04] right [11:04] . o O { can we please stop thumbnailing videos at all? it's a horrible cpu/IO/battery sink } [11:04] *cough* [11:05] there is a gconf key you can change if you want to do that ;-) [11:05] I like having thumbnails and they are done once only [11:05] so that's okish [11:05] seb128: the cleanest method is to install a signal handler in the thumbnailer, to catch segv and exit(1) [11:05] the next method is to install a generic apport hook to ignore the crashes [11:06] but I don't recommend that here [11:06] since that will bring the overhead of generating .crash files for no good [11:06] ok [11:06] and it'd present the 'cannot report problem' dialog to an user [11:06] thanks [11:06] so I think catchign the signal is the only sane option here [11:06] right [11:07] it's not so much an issue on stable versions [11:07] right [11:07] that's just to not flood ffmpeg-debian guys ;-) [11:15] mpt: any reason you open notify-osd on the ubuntu package rather than on the upstream component? [11:15] +bugs [11:17] * seb128 opens upstream tasks for those bugs now [11:20] seb128, MacSlow is concentrating on the package list, for much the same reason as the Ubiquity and Update Manager devs do [11:21] (or that's what he just told me) [11:21] mpt: ok, my experience until now has been that I've to ping him for a week to have him having a look over the list but if you says he looks at bugs regularly there now [11:21] all good [11:22] seb128, he also says that if other distributions adopt Notify OSD, it will become more important to distinguish between project-general bugs and Ubuntu-packaging-specific bugs [11:23] ok, no problem, if the dx guys look at those bugs that's all good [11:24] seb128, the ubuntu-docs team have similarly just been discussing migrating from bugtracking on the ubuntu-docs project to the Ubuntu ubuntu-doc package [11:25] mpt: as said if they read those bugs that's fine, they were not subscribed to the package until recentlu [11:25] recently [11:28] seb128, this is another example of bug 76416, so maybe nag the Launchpad developers about it :-) [11:28] Launchpad bug 76416 in malone "Handle a distribution being its own upstream for a package" [Medium,Triaged] https://launchpad.net/bugs/76416 [11:28] right :-) [11:36] pedro_: hi, the i386 retracer was stucked for some days I just restarted it so let it some time to catch up before cleaning recent crashers [11:37] seb128: ok! thanks for letting me know about it [11:37] you're welcome [11:41] pedro_: btw there is no need to set milestone for bugs fixed to GNOME svn since GNOME 2.26 is due before jaunty beta [11:42] seb128: alright, just don't want to forget about that f-spot issue (cannot find the svn commit) [11:43] btw it seems the gvfs auto mount is causing issues again [11:43] pedro_: I was commenting about a nautilus bug you just changed [11:43] bug 338466 [11:43] Launchpad bug 338466 in gvfs "Fspot doesn't load pictures from my digital camera" [Low,Confirmed] https://launchpad.net/bugs/338466 [11:43] seb128: ah that one, alright no problem [11:43] pedro_: hum [11:44] pedro_: https://edge.launchpad.net/ubuntu/+source/f-spot/0.5.0.2-0ubuntu3 [11:44] seb128: it's the same behavior of the bug you fixed las cycle [11:44] pedro_: that's a f-spot issue and not a gvfs one [11:44] "f-spot (0.5.0.2-0ubuntu3) intrepid; urgency=low [11:44] * Add f-spot-import-gphoto.dpatch: Fix f-spot-import to understand GIO [11:44] gphoto:// URLs, which fixes (i. e. gets rid of) the device dialog on [11:44] import. Also speculatively gvfs-umount the camera, otherwise F-Spot cannot [11:44] communicate with it. [11:44] " [11:44] * pedro_ looking [11:44] was the upload to fix the locking issue [11:45] seb128: i'll try that right away and comment on the report then, thanks! [11:45] the patch is still there [11:45] do you use f-spot-import or an another command? [11:48] seb128: yep, i use the f-spot-import command [11:50] workaround on bug 196757 makes the import to work again [11:50] Launchpad bug 196757 in gvfs "camera automount prevents import" [Low,Fix released] https://launchpad.net/bugs/196757 [11:53] pedro_: could be a side effect of bug #570888 [11:53] Error: Launchpad bug 570888 could not be found [11:54] gnome bug #570888 [11:54] Gnome bug 570888 in gphoto backend "gvfs-gphoto2 mount 4 devices when pluging one camera" [Major,Unconfirmed] http://bugzilla.gnome.org/show_bug.cgi?id=570888 [11:55] * pedro_ tests [12:00] seb128: seems so, I'm getting two camera devices, I'll follow up with the reporter for confirmation on that [12:03] pitti: I ran ps aux straight after the log up it's on bug 338340 let me know if it is of any use or not :) [12:03] Launchpad bug 338340 in jockey "Jaunty: Jockey doesn't download driver" [Undecided,New] https://launchpad.net/bugs/338340 [12:03] pedro_: the upstream bug is confirmed, right the current version has only 2 icons displayed [12:33] pitti: was the info I added to the bug of any use as I need the system for further testing? [12:49] guys the new restart dialogue looks strange in grey with the rest of the notifications being black is there any plan to change this? [12:49] why should those dialogs be different of any dialog? [12:50] they are not notifications but standard dialogs [12:52] seb128_: It just looks strange. It's grey and slightly transparent and looks wrong with the rest of the messages seemingly black and slightly transparent if that makes sense? [13:00] re [13:00] is anybody running intrepid there? [13:01] mvo: ? [13:02] seb128: I have a intrepid box [13:02] mvo: box or vmbox is fine, can you boot it for me? ;-) [13:04] seb128: sure. what then? [13:04] mvo: python-dbg -c 'import gnomecanvas' [13:05] ImportError: /usr/lib/python2.5/site-packages/apt_pkg.so: undefined symbol: Py_InitModule4 [13:05] grrr [13:05] why do we keep having those changes, it's broken, obviously nobody use that since nobody ever noticed and it's extra work [13:06] I was looking at why it's broken in jaunty and it didn't change much since intrepid [13:06] that was broken in intrepid already... [13:06] seb128: I have a different system and there it seems to be ok [13:06] hmmm [13:06] system = intrepid or hardy? [13:06] both intrepid [13:07] weird [13:11] mvo: hum ok, seems to work now, I was lacking some depends apparently [13:11] mvo: thanks anyway ;-) === Amaranth_ is now known as Amaranth [13:24] hey [13:25] lut crevette [13:26] salut seb128 [13:35] pitti, for bug 284994, vuntz has some patch to fix this problem, I think he pushed in opensuse [13:35] Launchpad bug 284994 in bluez-gnome "bluetooth-wizard unable to pair to fixed pin devices" [High,In progress] https://launchpad.net/bugs/284994 [13:35] crevette: can you attach the patch to the bug? [13:36] pitti, or we can investigate in gnome-bluetooth 2.27.x? [13:37] seb128, it is in upstream bug [13:37] crevette: he's away for lunch and it's too late to switch to a complete new technology for jaunty now [13:37] seb128, the code base it almost the same than bluez-gnome [13:38] crevette: it's versionned 2.27 for a reason and bastien said he could still be quite buggy and it didn't get testing it [13:38] actually I updated the packaging of gnome-bluetooth for myself to replace bluez-gnome [13:38] it -> yet [13:38] you can do the update in universe as a first step but it needs testing [13:39] the only thing I need to see is how to do for people using gnome-bluetooth =<0.11 [14:10] crevette: yes, upstream accepted the initial patch, and then did a better one [14:10] crevette: but I'd like to backport it, since I heard lots of complaints about the current bug [14:14] davmor2: thanks; replied in the bug [14:16] tkamppeter: welcome back [14:19] hey rickspencer3 [14:27] pitti: the latter log shows the initial problem the first log was the one with the restarted backend with debugging enabled. Initial problem was that it displays 0% downloading and then just stops and goes back to the original jockey window. Hopefully fully explained in report [14:30] hi rickspencer3, I have solved most issues now which were coming up during my vacation ... [14:30] tkamppeter: isn't it nice to come back and stare at an exploding mail box? :-/ [14:30] tkamppeter: enjoyed Brazil? [14:31] It is not so exploding, as IO read mail from time to time from Brazil, but I did not do bigger stuff, mainly organizational stuff on the OpenPrinting Summit, to get sponsors for community people. [14:38] Now I have caught up somewhat, fixed all but one bug for foomatic-filters 4.0.1, discussed s-c-p changes, uploaded collected upstream patches, solved HPLIP FFE, ... [14:42] tkamppeter: great work [14:45] pitti: should bug #336420 be assigned to seb128 ? [14:45] Launchpad bug 336420 in compiz "Jaunty: Gnome 'run a terminal shortcut' does not work anymore" [Medium,Triaged] https://launchpad.net/bugs/336420 [14:46] no please [14:46] I've no clue about compiz and lot to do already [14:46] rickspencer3: I think I assigned it to me, didn't know a better assignee; if kenvandine_wk has time for it, I'd be grateful, otherwise I'll squeeze it in [14:48] it's assigned to canonical-desktop-team, I'll assign to kenvandine_wk, who can always reassign to seb128 if needed ;) (j/k seb128) [14:49] ;-) [14:51] pitti: assign that to me [14:51] sorry... my box froze when i started a build in pbuilder [14:51] rickspencer3: ah, thanks [14:51] second time that has happened, need to figure out what is up with that [14:51] kenvandine_wk: dmesg? [14:51] will look [14:52] usually my laptop freezes after doing use switching in jaunty [14:52] kenvandine_wk: or perhaps something weird like having udev running in the pbuilder or so? [14:53] pitti: what are all these --MARK-- lines in my messages log? [14:54] kenvandine_wk: that your syslog didn't die [14:54] kenvandine_wk: they appear every 20 minutes [14:54] ah... never seen that before :) [14:55] they only appear it there was no activity in syslog for a certain period of time [14:56] seb128: I'll upload ekiga, gnome-utils, and gnome-vfs in the next minutes, FYI [14:56] (strip gconf translations) [14:56] pitti: ok thanks, you did check gnome-utils, a rebuild will not likely be enough there [14:56] should buy us perhaps 800 KB on the desktop CD [14:56] seb128: no, these aren't rebuilds [14:57] ok good then [14:57] seb128: ekiga doesn't use cdbs (I copied the rules) [14:57] because I uploaded gnome-utils recently [14:57] seb128: gnome-utils didn't use gnome.mk before; testing with that now [14:57] and gnome-vfs is just old [14:57] that was just to let you know in case you wanted to just do no change uploads [14:57] ok good [14:57] no, they wouldn't work [14:57] * pitti hugs seb128, thanks [14:57] * seb128 hugs pitti [14:57] mvo: any idea about that one? [14:57] $ apt-cache rdepends python-glade2-dbg [14:58] "apt-cache rdepends python-glade2-dbg" returns nothing [14:58] where deskbar-applet-dbg depends on it [14:58] that's current jaunty [14:59] seb128: does rdepends work on non-existing packages? [15:00] geser: that's part of the question ;-) === thunderstruck is now known as gnomefreak [15:02] seb128: I think its because there is no python-glade2-dbg, so apt has a stub of it in the database because its refered via a dep [15:02] but nothing more [15:02] (but to be 100% sure I would have to look into the source) [15:03] mvo: ok, do you have a workaround to list those which still depends on this one and should be transitioned? [15:04] seb128: filter the output of apt-cache unmet (perhaps also add -i) [15:04] geser: thanks [15:04] $ apt-cache unmet | wc -l [15:04] 2226 [15:04] urg [15:06] seb128: give me a sec [15:06] mvo: that's ok, unmet will do, thanks [15:07] seb128: gnome-utils b-deps on cdbs, but doesn't actually use it in debian/rules; would you mind if I change debian/rules to do so? [15:07] pitti: no [15:07] okay, doing [15:07] pitti: please put it in bzr too if you have a minute while doing the changes ;-) [15:08] oh, ok [15:09] seb128: how come that you ask for bzrifying things? :-) [15:09] bzr! [15:09] * mvo hugs seb128 [15:10] pitti: because if you look to https://code.edge.launchpad.net/~ubuntu-desktop you will see we use bzr in most modules now so there is little point stopping the changes, better to switch everything and have a consistant workflow [15:10] and I'm getting used to it now anyway so that's ok ;-) [15:10] heh [15:10] * seb128 hugs mvo [15:10] over the weekend I learned bzr-builddeb [15:10] and bugged james_w with two bugs, which he promptly fixed [15:10] * pitti hugs james_w [15:10] I like the "bzr get && bzr-buildpackage" for sponsoring [15:10] it does orig download and everything [15:11] right, and bd even checks out the branch for you [15:11] seb128: apt-cache unmet lists also suggests and recommends, if you want only depends use apt-cache unmet -i (it's much less output) [15:11] patch editing is one command away with bzr bd-do so that's ok too [15:11] geser: ah right [15:11] seb128: I like it to tell kwwii to just do "bzr bd lp:usplash" to fetch and build the latest usplash stuff :) [15:12] * pitti pushes lp:~ubuntu-desktop/gnome-utils/ubuntu [15:14] didrocks: btw, I made some corrections to https://wiki.ubuntu.com/DesktopTeam/Bzr [15:16] pitti: why did you change bzr commit to debcommit? [15:16] seb128: I find it much better to have debian/changelog and bzr changelog to be consistent; you don't? [15:17] also, it spares you to create a sensible bzr message; you should rather write good debian/changelog [15:17] pitti: bzr commit uses the debian changelog for me on jaunty [15:17] right, that's what it does? [15:17] well, since the recent version yes [15:17] I'm just wondering what else debcommit does ;-) [15:17] (for ages, really) [15:18] it just parses the changes in debian/changelog and mangles it to look good in a bzr changelog (indentation, etc.) [15:20] ok [15:20] yeah for good workflows now ;-) [15:20] the only annoying thing is how to handle packages which are sometimes in sync with debian [15:20] and then not because we package unstable versions first [15:22] debcommit is wonderful [15:23] debcommit is handy indeed [15:23] i even use that for upstream ChangeLogs sometimes ;) [15:23] seb128: I usually import the debian svn into a bzr branch [15:23] but i guess bzr has a similar feature build in for such cases [15:23] seb128: and merge from that (instead using MoM) [15:24] seb128: if we sync, we could just do the same with bzr (bzr pull --overwrite ../debian) [15:24] seb128: that would kill our Vcs-Bzr:, though [15:24] seb128: but all in all, if we are mostly in sync for some packages, we shouldn't maybe put them into bzr [15:25] pitti: right, that's what I've told didrocks to do right now [15:25] ie not put those in bzr [15:26] mvo: i am wainting for retracers to process that bug [15:26] not sure if it will happen though. [15:27] it has the need-i386-retrace tag [15:29] whast the status of retracers. are they broken? [15:29] (i remember that seb said something about backlog) [15:33] asac: I don't know, seb128 is the retracer working curretnly? [15:41] seb128: you are speaking about libgtkmm for instance, right? [15:41] pitti: ok, let me have a look [15:42] asac, mvo: the retracer was stucked for 6 days I restarted it around lunch [15:42] didrocks: yes [15:45] asac: what bug is that about? [15:45] pitti: just a question of debcommit. I make a change A, so, my debian/changelog will be: http://paste.ubuntu.com/128809/ and I debcommit. Then, I make a change B an my changelog is: http://paste.ubuntu.com/128811/. debommit will "bzr commit -m *A\n*B" [15:46] pitti: commiting manually would enables us to just write "* B" [15:47] thanks seb128 [15:47] didrocks: no, debcommit usually figures that out [15:47] didrocks: that only happens if you change the A changelog [15:47] don't do that [15:47] pitti: ok. I have to take a test :) [15:47] if you fix a previous changelog, bzr commit manually [15:47] and commit the other change separately [15:48] great, never experienced that. thought that debcommit was not so clever :) [15:48] didrocks: in technical terms, debcommit looks at all the added lines (bzr diff | grep ^+ [15:48] didrocks: when you are done with the pidgin update can you look at updating evolution-mapi in universe? [15:49] pitti: thanks for the infos. I will do that in my next update :) [15:49] seb128: there is an update to make? no problem :) [15:49] didrocks: yes 2.25.91 to 2.25.92 [15:49] ok [15:49] seb128: for piding, I merge from debian, right? [15:49] didrocks: yes [15:50] didrocks: or just update, as you want [15:50] didrocks: they just added an update since you merged so it might be easier to just add their debian dir diff to that [15:50] seb128: i have to figure out an easy workflow to merge with bzr :) [15:50] seb128: i was thinking about that, seems easy :) [15:51] * pitti radiates hate at gnome-utils' broken debian/rules [15:51] using both dh_movefiles and dh_instal [15:52] pitti: strange, seems that it hasn't been fully migrated :/ [15:53] didrocks: I'm on it.. [16:02] seb128: next bug failed; I'll have a look, this isn't normal [16:02] pitti: ok thanks, a firefox bug again? [16:02] assert os.path.exists(self.get('InterpreterPath', self['ExecutablePath'])) [16:02] ah [16:02] seb128: yes, with ffox that's very common [16:02] bug reports filed against 3.0.6 [16:02] but now we have 3.0.7 [16:03] so the /usr/lib/firefox/3.0.6/ thing doesn't exist any more [16:03] that's it [16:03] right [16:03] I'll untag [16:04] * kenvandine_wk -> lunch [16:21] * pitti pats his new gnome-utils debian/rules; yay sanity [16:21] pitti: retracer crasher again, can we make it ignore those errors? [16:22] seb128: we can, but that'll take a bit of work [16:22] pitti: ok, let's untag then [16:22] * seb128 untags this one [16:22] seb128: how do you untag? [16:23] seb128: I usually log into launchpad as apport and do it there [16:23] or do you have a clever script for it? [16:23] pitti: ssh ronne; log into a retracer environment, use the mass tagging script there [16:23] seb128: I keep the next cron mail as a reminder to fix it [16:23] ah [16:23] subscribing rather [16:25] pitti: would be nice to give some team the right to browse those bugs by default though [16:25] ubuntu-archive or something [16:25] so we have some people who could clean such issues [16:25] right [16:25] would make sense, given that the retracers run as ubuntu-archive [16:27] ~/msg -freenode rickspencer3 so unless we get overwhelming feedback we do that properly as a karmic spec [16:28] asac: ECHANNEL? ;-) [16:28] seb128: ETYPO ;) [16:28] + [16:28] ~ [16:28] /msg asac I sent you the s3kr1t world domination plan [16:28] lol [16:29] i really should review how i do /msgs in irssi [16:29] ;) [16:29] well, with "/msg"? [16:29] pitti: thats what i am currently doing. but thats error prone on long conversations [16:29] pitti: e.g. i dont open a new window for each conversation [16:29] so i have to type /msg all the time ;) [16:30] seb128: I won't bother bzrifying gnome-vfs; it should just die.. [16:30] pitti: right don't bother, it's going to be around for a while but maybe quickly in universe or something [16:30] seb128: at least that one looks like a no-change upload :-) [16:42]