[00:00] <seb128> let those for now and we will see if somebody complains
[00:00] <seb128> to change then:
[00:00] <seb128> - unsplit the C locale
[00:00] <seb128> - use replaces to avoid file conflicts error on upgrade
[00:00] <seb128> - do the 2.25.91 upgrade
[00:01] <seb128> thanks again for your work ;-)
[00:01] <asomething> no problem, I'll include the split with the 2.25.91 upgrade
[01:20] <bryce> chrisccoulson: you referring to 160_log_timestamping.patch?
[01:23] <chrisccoulson> does that patch add timestamps then? the only reason i asked is because i was looking at a bug report where the user couldn't open a second session via FUSA. the reporter already provided a Xorg.0.log, but it didn't contain anything useful, so i asked them to attach their Xorg.20.log too. That didn't have any trace of what went wrong either, andt it wasn't clear from the log when it was created, as there was no timestamp
[01:23] <chrisccoulson> the log they provided might have been several months old ;)
[01:31] <chrisccoulson> i've just noticed the timestamps in my own log actually
[01:32] <bryce> chrisccoulson: you're welcome ;-)
[01:32] <bryce> actually they're time since server start, so may not solve the issue in this particular case
[01:32] <chrisccoulson> the only thing that is missing though is the time that the server actually started
[01:33] <bryce> chrisccoulson: I'd accept a patch to add that if you'd be up for taking a shot at it; probably a 1-liner
[01:33] <chrisccoulson> i might be able to have a look at that. probably tomorrow though as it's getting quite late here now
[01:33] <bryce> cool
[01:34] <bryce> probably make sense to slot it in right after the Build Date line
[01:34] <bryce> oh hang on
[01:35] <bryce> [    0.000982] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 13 11:54:14 2009
[01:35] <bryce> isn't that it there?
[01:39] <chrisccoulson> ah yes, it is there in my log too
[01:39] <chrisccoulson> d'oh! i should probably get some sleep
[01:41] <bryce> :-)
[02:40] <ovnicraft> glatzor?
[02:41] <ovnicraft> bryce, hi how i can see the  displayconfig-gtj dependences ?
[02:41] <ovnicraft> s/gtj/gtk
[08:18] <seb128> hello
[08:23] <seb128> mvo: hello!
[08:23] <mvo> hey seb128
[08:28] <mvo> seb128: I take brasero and gnome-terminal for a start
[08:28] <seb128> mvo: danke
[08:28] <seb128> I take evolution-data-server and evolution
[08:28] <seb128> lut crevette
[08:28] <crevette> salut
[08:28] <seb128> didrocks: hello, want some work? I got libs updates for you ;-)
[08:32] <didrocks> seb128: hi :) and yes ;)
[08:32] <didrocks> seb128: thanks for all the sponsoring you did yesterday but you have to sleep, you know :)
[08:33] <didrocks> seb128: I think you forgot gnome-python (just pass it to whishlist)
[08:33] <didrocks> and gnome-python-extra is waiting for libgda
[08:33] <didrocks> talking about libgda :p, hey huats!
[08:33] <seb128> didrocks: no I didn't, I was not sure if you moved it to the right component or was still junk to use
[08:33] <huats> morning everyone
[08:33] <huats> I knew you were talking about me...
[08:33] <seb128> lut huats
[08:34] <huats> hey seb128 and didrocks
[08:34] <didrocks> huats: in a bad way, of course :)
[08:34] <huats> the gda update is ready just need to test it (which is not obvious)
[08:34] <huats> didrocks: because you can say nice word about me ?
[08:34] <didrocks> huats: as usually :)
[08:34] <huats> seb128: gtksourceview2, gucharmap and gnome-syste-monitor are on they way too....
[08:34] <didrocks> usual*
[08:35] <huats> (well if you haven't done one of them...)
[08:35] <didrocks> seb128: let me check for gnome-python
[08:35] <seb128> huats: I did upload gucharmap and gnome-system-monitor yesterday night
[08:35] <huats> ok
[08:35] <seb128> huats: did you start on those?
[08:35] <huats> seb128: I was trying to find you yesterday but I didn't...
[08:36] <huats> yeah but it is not a big deal... I didn't spend a lot of time... (it was more a parallele task)
[08:37] <huats> seb128: don't worry I'll take care of the gcalctool this morning in order to dry my tears :P
[08:37] <seb128> didrocks: there is also gnome-games if you want
[08:37] <seb128> huats: want other updates?
[08:37] <huats> why not...
[08:39] <didrocks> didrocks: yes, I can handle it, and what about the lib updates?
[08:39] <didrocks> seb128: there is no gnome-python project
[08:39] <didrocks> bzr: ERROR: Invalid url supplied to transport: "lp:~didrocks/gnome-python/ubuntu": No such project: gnome-python
[08:40] <huats> seb128: just a question you had to do a MIR for libgirepository right ?
[08:40] <seb128> huats: that doesn't seem ot be a convinced ping, just let me know when you are done with your updates and you want new ones
[08:40] <seb128> huats: no, why?
[08:41] <huats> no no I was kidding... give me some updates :)
[08:41] <seb128> didrocks: we should ping jcastro do fix that ;-)
[08:41] <seb128> jcastro: hello?
[08:41] <huats> because it seems to me that it was a bdeps of one of the update (gucharmap or gnome-system-monitor)
[08:41] <huats> (something new)
[08:42] <seb128> huats: gucharmap can build bindings using gir but that's not a requirement
[08:42] <vuntz> seb128: you joined at 9:18. Tsss. That's so late!
[08:43] <seb128> vuntz: do you ever sleep? you uploaded tarballs until 6am
[08:43] <didrocks> vuntz: seb128 sponsored a lot of work very late, you know? :)
[08:43]  * vuntz should really roll his panel tarball
[08:43] <huats> seb128: ok
[08:43] <vuntz> seb128: I decided to not answer this question today ;-)
[08:43] <didrocks> ok, not at 6am :p
[08:43] <seb128> vuntz: I'm a bit disapointed that neither session storing or the session dialog theming have been fixed though, stop slacking!
[08:43] <huats> like I said I had a rought look at it....
[08:43] <vuntz> seb128: session storing: I'm pinging lucasr for his patch
[08:44] <vuntz> seb128: session dialog theming: well, you know who to ask...
[08:45] <seb128> vuntz: I pinged him on IRC but got no reply, will try again ;-)
[08:45] <seb128> vuntz: did you find mvo for your gconf question yesterday?
[08:46] <vuntz> didrocks, huats: btw, congrats for the MOTU promotion!
[08:46] <huats> seb128: so what about those updates ? ;)
[08:46] <huats> vuntz: thanks !
[08:46] <seb128> huats: http://download.gnome.org/sources/eog/2.25/eog-2.25.91.tar.gz
[08:46] <huats> ok seb128
[08:46] <vuntz> seb128: hrm, no. But I think you guys should patch the code to not use gconf.xml.system and use gconf.xml.defaults (since they are both for the exact same use case)
[08:46] <seb128> didrocks: http://download.gnome.org/sources/libgtop/2.25/libgtop-2.25.91.tar.gz
[08:46] <seb128> huats:
[08:47] <seb128> http://download.gnome.org/sources/gtk-engines/2.17/gtk-engines-2.17.3.tar.gz
[08:47] <vuntz> seb128: (and because you're stuck with gconf.xml.defaults forever for compatibility)
[08:47] <huats> vuntz: you know it is mainly thanks to the whip of seb128....
[08:47] <vuntz> huats: and then people will say again and again that french people love whips...
[08:47] <huats> :)
[08:47] <didrocks> seb128: ok. I will do it once gnome-games is ok
[08:47] <seb128> vuntz: I think we misunderstood the way it was supposed to work
[08:48] <seb128> vuntz: to what change did you look exactly yesterday? to the gconf path we are using?
[08:48] <seb128> vuntz: anyway having extra paths in the list doesn't cost much I think
[08:48] <didrocks> vuntz: and thanks ;)
[08:48] <vuntz> seb128: yeah, looking at your gconf path. It all looks fine. We do the same thing in openSUSE
[08:48] <vuntz> seb128: it's just meaningless to have both gconf.xml.system and gconf.xml.defaults
[08:49] <seb128> right
[08:49] <vuntz> (potentially harmful too since it's confusing for a sysadmin)
[08:49] <vuntz> I was discussing with halfline yesterday on how to move all this upstream
[08:50] <seb128> so the code now uses gconf.xml.defaults?
[08:50] <vuntz> seb128: no, the code uses gconf.xml.system. That's a fedora-ism, because it was developed by a fedora hacker
[08:50] <vuntz> seb128: if you or I had written the code, we'd have used gconf.xml.defaults
[08:51] <vuntz> seb128: because that's how our gconf path is set
[08:51] <seb128> I see
[08:51] <seb128> we need dconf ;-)
[08:51] <vuntz> anyway, you can do whatever you want. I know I will patch gconf.xml.system out in openSUSE ;-)
[08:51] <seb128> I'm pondering what to do now due to upgrades
[08:52] <vuntz> well, since the only user of the gconf PK stuff in 2.24 was gnome-power-manager, and since it was broken (!), nobody was able to use gconf.xml.system
[08:52] <vuntz> so it's still time to kill it ;-)
[08:53] <seb128> not in ubuntu
[08:53] <seb128> the gconf was added by mvo because he used that to set the system proxy key
[08:53] <vuntz> bad him
[08:53] <vuntz> slap him hard
[08:53] <seb128> lol
[08:53]  * seb128 hugs mvo
[08:54] <vuntz> mvo: I still love you, of course
[08:54] <mvo> vuntz: oh, was that not the right way to do it?
[08:55] <seb128> huats: undo gtk-engines it has been done already by somebody else
[08:55]  * mvo reads backlog
[08:55] <huats> seb128: ok
[08:58] <pitti> hmm; when linking libindicate, I get
[08:58] <pitti> /home/martin/ubuntu/dx/indicator-applet-ubuntu/libindicate/listener.c:699: undefined reference to `g_memory_input_stream_new_from_data'
[08:59] <pitti> do I explicitly need to -lgio?
[08:59] <pitti> PKG_CHECK_MODULES(LIBINDICATE, glib-2.0 >= $GLIB_REQUIRED_VERSION
[08:59] <pitti>                                gio-2.0 >= $GIO_REQUIRED_VERSION
[09:00] <pitti> so that should be ok, in theory?
[09:01] <jeromeg> pitti: in theory you need to add the flags in your makefiles too
[09:01] <pitti> hm, somehow this is totally wrecked, nevermind for now
[09:01] <mvo> vuntz: I'm pretty sure that when I did that change, our default config would not allow me to do system settings modification. I use the dbus "org.gnome.gconf.defaults.set-system" stuff for it
[09:01] <mvo> vuntz: might be a issue with a early implementation of this interface of course :/
[09:01] <vuntz> mvo: sure. The thing is that in an ideal world, you should have patched the PK helper to use gconf.xml.defaults instead of gconf.xml.system
[09:02] <vuntz> mvo: (which is hard to know, I'll admit ;-))
[09:02] <mvo> vuntz: thanks for this information :)
[09:03] <vuntz> mvo: now the questions are "is it too late? Does that matter now that we have one release with it?"
[09:03] <vuntz> mvo: and I'll let you decide
[09:03] <seb128> pitti: do you have a -lglib2.0 on the ld line?
[09:03] <vuntz> seb128: fwiw, I forgot to explicitly mention it in NEWS, but the change in libgweather is because of tzdata 2009a. Don't know if you have it in jaunty
[09:04] <pitti> seb128: no, but /usr/lib/libglib-2.0.so (totally wrecked)
[09:04] <pitti> seb128: I think that's probably it
[09:05] <pitti> seb128: oh, hang on, it is there for the libtool call
[09:05] <pitti> /bin/bash ../libtool --tag=CC   --mode=link cc -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include   -g -O2 -g -Wall -O2 -version-info 0:1:0 -no-undefined -export-symbols-regex "^[^_].*" -Wl,-Bsymbolic-functions -Wl,-z,defs -Wl,--as-needed -o libindicate.la -rpath /usr/lib  libindicate_la-server.lo libindicate_la-listener.lo
[09:05] <pitti>  libindicate_la-listener-marshal.lo libindicate_la-indicator.lo libindicate_la-indicator-message.lo -L//lib -lgdk_pixbuf-2.0 -lm -lgmodule-2.0 -ldbus-glib-1 -ldbus-1 -lgobject-2.0 -lglib-2.0
[09:05] <pitti> seb128: I think that's just missing a -lgio then ?
[09:05] <mvo> vuntz: I check it out, thanks again
[09:06] <seb128> pitti: right
[09:06] <seb128> pitti: you need to use $(LIBINDICATE_LIBS) somewhere in your Makefile.am I think
[09:07] <seb128> pitti: and $(LIBINDICATE_CFLAGS) maybe too
[09:07] <pitti> libindicate_la_LIBADD = \
[09:07] <pitti>         $(LIBINDICATE_LIBS)
[09:08] <pitti> it does
[09:08]  * pitti just appends -lgio-2.0 and leaves the proper fix to ted
[09:09] <seb128> pitti: grep LIBINDICATE_LIBS Makefile.in?
[09:09] <seb128> pitti: is the source downloadable somewhere?
[09:09] <mvo> vuntz: hm, I may be a bit slow, but do I need to change this in our code or in the gconf wrapper? because afaics all I do is using org.gnome.GConf.Defaults and calling "SetSystem" on it? I don't see (currently) that I can do it from my code
[09:10] <pitti> seb128: https://edge.launchpad.net/indicator-applet/+download, indicator-applet
[09:10] <pitti> seb128: nevermind for now, I'll apply the quickfix and ask Ted
[09:10] <pitti> works now
[09:12] <vuntz> mvo: https://api.opensuse.org/public/source/GNOME:Factory/gconf2/gconf2-pk-default-path.patch?rev=c9daf410c2d59d940c81b060cdaa9238
[09:12] <vuntz> mvo: that's the patch I have in openSUSE
[09:12] <mvo> cool, thanks vuntz
[09:13] <mvo> vuntz: will that go upsteam too?
[09:13] <vuntz> mvo: and if you need to double check, /etc/gconf/2/path is changed like this: https://api.opensuse.org/public/source/GNOME:Factory/gconf2/gconf2-schemas-path.patch?rev=c9daf410c2d59d940c81b060cdaa9238
[09:13] <vuntz> mvo: I've talked with halfline yesterday about it
[09:13] <mvo> IIRC mclassen wrote the gconf interface, no?
[09:14] <vuntz> mvo: I think he's more or less convinced that upstream should adopt what Debian/openSUSE/Ubuntu are doing (since we're doing the same thing)
[09:14] <mvo> heh .)
[09:14] <mvo> good
[09:14] <vuntz> mvo: so this will hopefully end up upstream. But in 2.27
[09:14] <mvo> I think I apply the patch, I will just need the old location until the next LTS :/
[09:14] <mvo> (for backward compat)
[09:15] <vuntz> mvo: well. It's really up to you. Maybe it's simpler for you now to not use this patch. I'd say it's broken, but most people won't notice anyway
[09:15] <vuntz> "most people" as in "99.9999%"
[09:15] <seb128> pitti: builds fine for me
[09:15] <vuntz> okay, make that "99.99%"
[09:16] <mvo> vuntz: heh .) ok
[09:16]  * mvo scratches his head about it
[09:17] <vuntz> mvo: if it helps you: if I were you, I'd use the patch to try killing gconf.xml.system harder. It's a one-line patch used by at least one other distro.
[09:17] <vuntz> mvo: but I'm not you ;-)
[09:17] <vuntz> and I'm biased
[09:22] <seb128> pitti: dunno where you got your pkg_config line, the tarball has
[09:22] <seb128> PKG_CHECK_MODULES(LIBINDICATE, glib-2.0 >= $GLIB_REQUIRED_VERSION
[09:22] <seb128>                                gdk-pixbuf-2.0 >= $GDK_PIXBUF_REQUIRED_VERSION
[09:22] <seb128>                                dbus-glib-1 >= $DBUS_REQUIRED_VERSION)
[09:23] <pitti> seb128: weird, I have gio-2.0 there, too
[09:23] <seb128> pitti: adding a gio-2.0 line in there fixes the issue
[09:24] <seb128> pitti: ok so we don't have the same version, I did add gio line, ran autoconf and automake and now the Makefile.in LIBINDICATE_LIBS lists -lgio-2.0
[09:24] <pitti> seb128: aaah
[09:24] <pitti> seb128: that change is in the packaging branch, but not in the tar.gz
[09:24] <pitti> seb128: so a mere autoreconf should do it
[09:24] <seb128> pitti: you probably need to run autoconf and automake then
[09:24] <seb128> pitti: right
[09:27] <mvo> vuntz: I trust you (famous last words ;)
[09:27] <mvo> seb128: new gconf is comming
[09:27] <seb128> mvo: thanks!
[09:27]  * mvo hugs vuntz
[09:33] <crevette> "debian/patches/05_from_vuntz_gconf2-pk-default-path.patch"
[09:33] <crevette> :)
[09:35] <vuntz> ahah
[09:36] <vuntz> positive way to see it: "yay, I get the credit!"
[09:36] <vuntz> negative way to see it: "if it's wrong, everybody will know it's my fault"
[09:36] <seb128> vuntz: everybody knows that GNOME being broken is your fault anyway
[09:41] <seb128> waouh
[09:41] <seb128> the new title edition in launchpad is cool ;-)
[09:44] <didrocks> seb128: yeah it's really fun :)
[09:44] <crevette> new title edition ?
[09:44] <didrocks> crevette: try to edit a bug title, for instance
[09:44] <didrocks> (on edge)
[09:45] <vuntz> seb128: is it inline edition?
[09:45] <seb128> vuntz: yes
[09:45] <crevette> ah okay
[09:45] <seb128> vuntz: how do you know? ;-)
[09:45] <didrocks> I look the little red animation when you cancel the edition :)
[09:46] <vuntz> seb128: don't know. Just makes sense.
[10:05] <pitti> seb128: indicator-applet uploaded to NEW
[10:06] <seb128> pitti: do you want me to do review?
[10:06] <pitti> seb128: if you have some time, that'd be great
[10:06] <seb128> pitti: ok, doing that next
[10:09] <jeromeg> pitti: I managed to fix two additionnal bugs in abiword's packaging which made documentation unusable
[10:09] <jeromeg> I'm doing a last test build and will attach to LP
[10:10] <pitti> jeromeg: cool, thanks
[10:10] <jeromeg> I will forward my fix to debian later, so that we don't divert too much
[10:12] <seb128> pitti: ENOTINTHEQUEUE
[10:13] <seb128> pitti: are you reviewing the abiword update? I was going to give it a look but I don't want to dup work
[10:14] <jeromeg> seb128: I'm doing a last test build and will attach and improved package fixing 3 additionnal bugs
[10:14] <seb128> jeromeg: ok
[10:14] <pitti> seb128: abiword> not today, I'm afraid; dx team packaging, meeting, 8th anniversary with my wife this evening..
[10:14] <seb128> pitti: oh, happy anniversary ;-)
[10:14] <seb128> pitti: yeah, busy day for me too, new GNOME, dx team, meeting ... doh need to send activity report!
[10:15] <pitti> seb128: queue> weird, I uploaded it, and no reject mail so far
[10:15] <seb128> pitti: still not there but there is one less item now so maybe somebody else is cleaning
[10:15] <pitti> well, I should have gotten a NEW mail
[10:15] <pitti> ah, there it is
[10:16] <pitti> got caught in the :15 run
[10:16] <seb128> ok, it's in the queue
[10:16]  * seb128 fetchs it
[10:20] <mvo> mpt: hello, could you give me your opinion on the "auto_launch" update-manager feature. how should it behave on the development release? should we have a "7 days for regular updates until its started" policy here too?
[10:21] <seb128> pitti: ok, package looks all fine to me, accepted
[10:22] <mpt> mvo, that's more of a managerial sort of decision
[10:22] <pitti> seb128: thanks
[10:22] <seb128> pitti: the .schemas is weird but I will ask ted about that later that's a detail
[10:22] <mpt> mvo, because if you have the 7-days-between-updates working during the alpha/beta, testers aren't receiving updates as often as they probably want to
[10:22]  * mvo looks up "managerial"
[10:22] <mvo> ok
[10:22] <jeromeg> seb128: could you possibly move xfce4-notifyd and xfswitch-plugin out of new ?
[10:23] <mpt> mvo, but if you have daily updates during the alpha/beta, you won't get testing of the code that tests that updates during the release are weekly :-)
[10:23] <mvo> yeah :)
[10:23] <mvo> I guess I make it two days for now
[10:23] <seb128> jeromeg: I don't plan to spend too much time on NEW today I've lot to do, let me have a quick look to see if those are easy ones
[10:23] <mpt> mvo, so if you're quite confident of the code that makes updates weekly, then make it daily during the testing period
[10:23] <mvo> so that the interval codes get testing
[10:23] <mpt> ah, good idea
[10:24] <jeromeg> seb128: we took them from debian svn, it should be safe
[10:24] <mvo> do you think we should treat outside updates (from external repository) different? or just apply the same interval on them as well (on a stable release) ?
[10:24] <mpt> mvo, and set yourself at least one reminder alarm to change that period before the freeze :-)
[10:24] <jeromeg> seb128: Corsac will upload them to debian in the next few days
[10:25] <mvo> mpt: reminder> yes
[10:25] <mpt> mvo, I don't know. Are there examples of external repositories that change very often? I suppose heavily-in-development PPAs might.
[10:26] <mvo> mpt: I'm not sure, I guess there are some but I don't know how much flux there is. sounds like something I should ask on ubuntu-devel-discuss or ubuntu-devel
[10:26] <mvo> mpt: to gather some data on it
[10:27] <seb128> jeromeg: xfswitch-plugin accepted, xfce4-notifyd is not good
[10:27] <seb128> jeromeg: xfce4-notifyd sources a GPL2 and the COPYING in GPL3
[10:27] <seb128> a -> are
[10:28] <jeromeg> arg
[10:28] <seb128> " *  This program is free software; you can redistribute it and/or modify
[10:28] <seb128>  *  it under the terms of the GNU General Public License as published by
[10:28] <seb128>  *  the Free Software Foundation; version 2 of the License ONLY."
[10:28] <jeromeg> seb128: ok, thank you very much for the review
[10:28] <seb128> you're welcome
[10:28] <jeromeg> I'll fix this asap
[10:28] <seb128> thanks
[10:30] <seb128> tseliot: SimpleGladeApp.py is LGPL in xorg-options-editor-gtk and the tarball has no LGPL copy and the debian copyright doesn't list this one
[10:39] <asac> bryce: 330108 -> please ack this sponsoring
[10:48] <tseliot> seb128: what do you suggest that I do? Shall I add another license file or simply add LGPL to the current COPYING file?
[10:48] <tseliot> seb128: and maybe explain it all in the README?
[10:49] <seb128> tseliot: add a COPYING.LIB or similar which has the LGPL copy and list in the debian copyright
[10:49] <seb128> tseliot: you need to ship the texts for the license you use and the copyright needs to list those
[10:50] <tseliot> seb128: ok, I'll do it and I'll update my bzr branch
[10:51] <seb128> thanks
[12:13] <jeromeg> seb128: about xfce4-notifyd, if I patch COPYING with upstream's agreement, is that enough ?
[12:17] <seb128> jeromeg: can't you get them to roll a new tarball with a fixed license?
[12:18] <jeromeg> seb128: I'll see what I can do
[12:18] <seb128> jeromeg: if they fix it to their vcs I guess patching for the current version until the next tarball come is ok
[12:18] <jeromeg> ok, that should be easier :D
[12:19] <seb128> well if they want their software distributed they should be conciliant and roll a new tarball ;-)
[12:20] <seb128> pitti: is your ssh agent working again with the gnome-keyring uploaded yesterday?
[12:20] <jeromeg> seb128: sure
[12:23] <fta2> seb128, thanks for gwibber. i'll clarify that with upstream
[12:23] <seb128> fta2: you're welcome
[12:24] <fta2> seb128, could I re-up with a fixed tarball but using the same upstream version? or will it be rejected because of md5 mismatch?
[12:26] <pitti> seb128: "again"? It never stopped working
[12:26] <seb128> pitti: I though it broke for you during the sprint when I uploaded the version which fixed the timeout issue
[12:27] <seb128> pitti: we got several bugs about the ssh agent being broken in 2.25.90
[12:27] <seb128> asac: ^ does it work for you now?
[12:27] <seb128> fta2: you can reupload the same version, the other one has not been accepted or published
[12:28] <asac> seb128: dont have 64bit system at hand right now. dholbach also saw this
[12:28] <seb128> asac: that was 64b specific?
[12:28] <asac> it always worked on 32bit
[12:28] <asac> seb128: yes i think so
[12:29] <seb128> asac: ok, you didn't tell me that or I didn't note the information ;-)
[12:29] <pitti> seb128: oh, during the sprint, yes
[12:29] <pitti> seb128: it has worked again for a long time
[12:29] <asac> seb128: sorry. i think dholbach noted that in the bug
[12:30] <seb128> pitti: ok
[12:31] <seb128> asac: I've pinged dholbach and mdz who had the issue too
[12:34] <mvo> mpt: everything should auto-launch, no notification area applets at all? so apport will auto-launch on login (if needed) and reboot required comes up too?
[12:35] <mpt> mvo, the "restart required" is update-notifier, correct? that should come up automatically
[12:35] <mpt> Does apport use notification bubbles?
[12:35] <mpt> I didn't notice that
[12:38] <mvo> mpt: apport uses a notiifcation icon for crashes that happened for system processes
[12:38] <mvo> mpt: or that happend while noone was logged in
[12:39] <mpt> mvo, just an icon and no bubble? That's fine for now
[12:39] <mvo> mpt: so when the user clicks on it he may get a gksu style dialog first to access the crash
[12:39] <mvo> mpt: it also contains a bubble that just tells about the crash report
[12:40] <mpt> ergh
[12:40] <mpt> What's the exact text of the bubble?
[12:40] <mpt> (Thanks for thinking of that case!)
[12:40] <mvo> http://paste.ubuntu.com/119190/
[12:41] <mpt> "Click on the notification icon to "
[12:41] <mpt> rats
[12:42] <mpt> And we can't stuff explanatory text into the gksu dialog, can we?
[12:42] <seb128> you are not suggesting auto-opening a gksu dialog right?
[12:42] <mpt> probably not :-)
[12:43] <seb128> ok good ;-)
[12:43] <mvo> mpt: I guess we could but it would be a bit inconvinent to login and get a dimmed screen
[12:43] <mpt> exactly
[12:44] <mpt> hm
[12:46] <mpt> mvo, what would be the impact of nuking both the icon and the bubble?
[12:47] <mpt> -> not providing graphical access to crash reports of system processes
[12:47] <mpt> -> ...? Who uses that?
[12:47] <mvo> mpt: nuking the bubble woudl make it less discoverable, nuking the icon means we don't get bugreports for this type of crashes anymore
[12:47] <seb128> lot of users looking at launchpad
[12:47] <seb128> all the installation issues are reported this way
[12:48] <mpt> hm, ok
[12:48] <seb128> mvo: I would not say no to less installation issues bugs though ;-)
[12:49]  * seb128 runs away from mvo quickly
[12:49]  * mpt thinks seb128 is confusing bugs with bug reports ;-)
[12:49] <mpt> I guess it should be a preliminary alert that segues into the gksu one, ugh
[12:49] <mpt> until we have a nice Crash Reporter utility thingy
[12:50] <mpt> ok, I'll write this up
[12:53] <mvo> mpt: that may not make it to FF, I mean, there is *very* little time already and I need to finish more than just the UX team changes. adding more code is going to make it even more difficult (unless I get a FF expection for this)
[12:54] <mpt> mvo, do you have an alternative suggestion?
[12:54] <mvo> mpt: just showing the icon and not the bubble and hoping the user discovers it on his own (sorry, not a very good one I guess)
[12:55] <mvo> mpt: please still draw the suggestion you have, but its going to be difficult to meet the deadline
[12:55] <mpt> mvo, ok, the icon only would be tolerable
[12:55] <mpt> I'll mock up the alert now
[12:56] <mvo> thanks
[13:02] <mpt> mvo, maybe bratsche could take care of apport instead
[13:06] <asac> mvo: so does the user see partner apps in update-manater?
[13:06] <mvo> asac: sure, why not?
[13:08] <mvo> mpt: sure, the code is in update-notifier bzr: src/crash.c - the recent commits should be good templates in what needs to be changed
[13:08] <mvo> mpt: I will leave that change out and upload what I have now and let him add the required code
[13:09] <mpt> thanks mvo
[13:09] <mvo> mpt: will you be able to write a mail to ubuntu-devel asking for opinions about if we need a special interval for third party repos (like PPAs) or if 7 days is good for those as well
[13:09] <mvo> ?
[13:09] <mpt> mvo, wait, src/crash.c is in update-notifier? Not in apport?
[13:10] <mvo> mpt: correct, update-notifier acts as the messanger, it detects the files and calls apport
[13:11] <mvo> (update-notifier should really be named event-notifier)
[13:11] <mpt> ok
[13:17] <asac> mvo: i am not sure why not. because its not enabled?
[13:17] <asac> mvo: so are the partner apps visible in update-manager or not? ;)
[13:20] <mvo> asac: partner apps are only visable when the partner repo is enabled and a partner app is installed
[13:20] <mvo> asac: but then they will show up just fine
[13:20] <asac> mvo: ok
[14:12] <jcastro> seb128: looking for me?
[14:13] <seb128> jcastro: hello
[14:13] <seb128> jcastro: could you create a gnome-python component on launchpad? ;-)
[14:14] <jcastro> yessir!
[14:14] <seb128> thanks ;-)
[14:14] <jcastro> I have something for you seb128
[14:14] <jcastro> https://code.edge.launchpad.net/lp-upstream-tools
[14:14] <jcastro> I am announcing this on the bugs list later today
[14:15] <jcastro> it will let you mass open upstream tasks
[14:16] <seb128> cool, will try that later
[14:16] <seb128> I'm busy with GNOME updates right now
[14:16] <jcastro> no worries
[14:17] <seb128> hey tedg
[14:17] <tedg> seb128: Good morning.
[14:17] <seb128> tedg: I cc-ed you on a sponsoring request for fast-user-switch-applet, the change seems to be quite some good work if you could give it a review
[14:17] <tedg> seb128: Cool.  I'll look at it.
[14:17] <seb128> thanks
[15:04] <pitti> hey tedg
[15:05] <tedg> pitti: Morning, going through your mail :)
[15:22] <seb128> vuntz: gnome-panel 2.25.91 fixes the vertical notification area issue (and a similar one with the clock applet when showing the weather)
[15:24] <calc> seb128: is there a known issue with gnome panel locking up when attempting to access the clock applet?
[15:24] <calc> seb128: its happening to me all the time :\
[15:24] <seb128> calc: yes,   http://bugzilla.gnome.org/show_bug.cgi?id=570765
[15:24] <calc> seb128: ok thanks
[15:25] <seb128> calc: you are welcome to try the patch one the bug if you get the bug all the time and tell us if it fixes the issue
[15:25] <seb128> calc: that's a one line and I will probably upload to jaunty later today
[15:25] <seb128> vuntz: ^ do something!
[15:27] <calc> seb128: ok, i'm pretty busy today but if i have a chanse before its uploaded i will look at it
[15:33] <pitti> hey calc
[15:36] <pitti> ugh, our gpm package is a patch swamp
[15:36] <vuntz> seb128: what can I do if it's an eds bug?
[15:38] <seb128> vuntz: well whatever e-d-s do the clock should not hang, no?
[15:38] <seb128> vuntz: there is an e-d-s bug for sure but the clock not handling e-d-s crashes is a bug too
[15:38] <seb128> pitti: talk to tedg ;-)
[15:40] <vuntz> seb128: it's a bug in the library part of e-d-s
[15:40] <seb128> vuntz: well, shouldn't those calls be async in the clock code?
[15:40] <bryce> morning
[15:41] <vuntz> seb128: if you read my comment, you can see that I asked: "why don't we have an async version of this function?"
[15:41] <vuntz> seb128: so, hrm, what can I do? :-)
[15:41] <seb128> vuntz: debug eds? ;-)
[15:43] <vuntz> seb128: that's your job ;-)
[15:43] <seb128> vuntz: ok, so your job is to make it on a gnome-2-26 targets list
[15:45] <crevette> I was to propse that
[15:45] <crevette> I think it could be a good candidate
[15:46] <vuntz> seb128: see, crevette can handle that part ;-)
[15:46] <vuntz> it's just a matter of changing the GNOME target in bugzilla
[15:46] <seb128> vuntz: well if that's just changing the target and having nobody to care about it then
[15:47] <seb128> nobody seems to consider using the clock applet freezing the session as an issue
[15:48] <vuntz> seb128: oh andre will care, don't worry ;-)
[15:48] <jeromeg> seb128: I finally managed to get rid of my ln issues, I attached my improved package to bug #318444
[15:48] <seb128> jeromeg: ok thanks
[15:48] <jeromeg> seb128: should fix at least 10 bugs on LP
[15:48] <seb128> cool
[15:49] <jeromeg> some of which were due to our packaging
[16:03] <bryce> brb
[16:14] <mvo> james_w: hi, do you have a moment?
[16:14] <mvo> james_w: I was sponoring tomboy (bzr get lp:~ubuntu-desktop/tomboy/ubuntu ; bzr-buildpackage -S) - and I get all sorts of strange errors from dpkg-source now
[16:15] <rickspencer3> desktop team meeting in 15 minutes
[16:15] <rickspencer3> https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-02-17
[16:15] <james_w> mvo: sure, for you anything
[16:16] <mvo> james_w: bzr-buildpackage -e gives me a strange layout with a "PaxHeaders" direcotry
[16:16] <mvo> james_w: do you have any idea what might be wrong here?
[16:16] <james_w> mvo: aha
[16:16] <ember> we already tried to repack the tarball, same error
[16:17] <james_w> is this a git export generated tarball?
[16:17] <james_w> https://bugs.launchpad.net/bzr-builddeb/+bug/303931
[16:18] <james_w> I assume it is that
[16:20] <mvo> james_w: hm, that sounds likely, could we have a compat mode? I assume it uses python tarfile =
[16:20] <mvo> ?
[16:21] <mvo> so compat would just run subprocess.call()
[16:21] <mvo> ?
[16:21] <mvo> heh :)
[16:21] <mvo> kees already did that
[16:21] <james_w> mvo: "Fix Committed"
[16:21] <james_w> :-)
[16:21]  * mvo hugs james_w
[16:21] <ember> heh
[16:21] <james_w> lp:bzr-builddeb if you want to use it locally to get going now
[16:22] <mvo> james_w: thanks, you are my hero of the day. getting it now
[16:22] <james_w> there are probably a few dragons hiding in that branch though
[16:22] <james_w> please kick me if something doesn't work
[16:23] <mvo> heh :) will do
[16:23] <mvo> I'm not afraid of dragons, I got a chainmail+2 and a good sword, what could possibly go wrong?
[16:23] <james_w> heh
[16:25] <mvo> bzr-buildpackage is now much happier
[16:27] <james_w> \o/
[16:29]  * asac thinks its meeting time
[16:30] <asac> @time
[16:30]  * rickspencer3 hammers gavel on table
[16:30] <rickspencer3> is everyone here?
[16:30] <asac> hmm no bot here ;)
[16:30] <ArneGoetje> I am
[16:30] <seb128> hey rickspencer3
[16:30] <calc> hi
[16:31] <pitti> o/
[16:31] <rickspencer3> ArneGoetje: asac: bryce: Riddell: pitti: calc: let's go!
[16:31] <ArneGoetje> rickspencer3: I'm here
[16:31] <bryce> alrighty
[16:31] <Riddell> hola
[16:31] <rickspencer3> First, I know that some of us are under a lot of pressure over the next couple of days, so feel free to ...
[16:32] <rickspencer3> work issues off list if you think it will help the meeting go faster
[16:32]  * kenvandine waves howdy
[16:32]  * rickspencer3 wave to Ken
[16:32] <Riddell> hi kenvandine
[16:32] <asac> meeting wiki is: http://wiki.ubuntu.com/DesktopTeam/Meeting/2009-02-17/
[16:32] <asac> hi kenvandine
[16:32] <asac> welcome to the team
[16:32] <rickspencer3> outstanding items - bryce, anything on https://launchpad.net/bugs/309482
[16:33] <rickspencer3> while bryce is working on that ...
[16:33] <rickspencer3> pitti: graphical installer for server is a non-issue, right?
[16:33] <pitti> rickspencer3: sorry, forgot about mailing that; please keep it as an action item for me
[16:34] <pitti> but it's certainly not jaunty matter
[16:34] <rickspencer3> k
[16:34] <kenvandine> asac: thx
[16:35] <rickspencer3> before we go on, any agenda items to add?
[16:36] <pitti> we'll walk over the specs list, I assume
[16:37] <rickspencer3> pitti: yes, I want to review work items for feature freeze readiness
[16:37] <bryce> rickspencer3: looks like we have a backtrace now; I'll investigate further today
[16:37] <rickspencer3> bryce: ack
[16:37] <rickspencer3> pitti: do you want to say a few words about Dx integration status?
[16:37] <bryce> I notice *** glibc detected *** kwin: double free or corruption (!prev): 0x0a06a030 *** so possibly it's not X that's crashing but kwin, but I'll look into it more
[16:37] <pitti> eek, a glibc was detected!
[16:38] <pitti> so, today we got the "go!" for the IM indicator stuff
[16:38] <asac> rickspencer3: those numbers are wrong right?
[16:38] <rickspencer3> the ones on the table, where I have note that says they are wrong ;)
[16:38] <pitti> I uploaded three packages related to that, and a patch, seb will look on two other patches to fix notifications
[16:38] <pitti> I'm still waiting for the new notification daemon
[16:39] <pitti> there are still some open questions wrt. upgrades and automatically enabling them
[16:39] <pitti> that'll still require some work
[16:39] <rickspencer3> is there an eta for having that figured out? Anything anyone could be doing to help?
[16:39] <seb128> I'm discussing some issue with the patch for gsd but that should be uploaded soon
[16:40] <pitti> rickspencer3: I was promised "today"
[16:40] <pitti> for the notification daemon
[16:40] <pitti> no ETA for migration issues, just got one round of discussion
[16:41] <rickspencer3> will the migration issue block FF in your opinion?
[16:41] <pitti> it'll need a (minor) FF exception IMHO
[16:41] <pitti> but it's borderline
[16:41] <rickspencer3> ok
[16:41] <pitti> but we can certainly get that
[16:41] <pitti> we have similar code in intrepid for fusa
[16:41] <tkamppeter> hi
[16:41] <rickspencer3> ok
[16:42] <rickspencer3> moving on
[16:42] <rickspencer3> let's quickly touch on status with regard to FF, round table style
[16:43] <rickspencer3> ArneGoetje: is the language selector on track for Feature Freeze?
[16:43] <ArneGoetje> maybe need a few days more
[16:43] <rickspencer3> ArneGoetje: there are no more days
[16:43] <rickspencer3> FF is Thursday
[16:43] <pitti> what's still left? features or just UI changes?
[16:43] <pitti> UIF is two weeks later
[16:44] <pitti> PKification etc. would need to land by Thursday
[16:44] <pitti> throwing around the .glade still has some grace time
[16:44] <ArneGoetje> basically debugging. GUI is done, just the code is not fully workable yet.
[16:45] <Riddell> we don't care about bugs yet :)
[16:45] <rickspencer3> so sounds like that is on track for FF
[16:45] <pitti> ArneGoetje: is it realistic to get something uploaded by Thursday then, even if it's still buggy?
[16:45] <ArneGoetje> well, it's not usable yet
[16:45] <pitti> oh, hmm
[16:45] <rickspencer3> I'm afraid that is at risk for missing Jaunty then
[16:46] <ArneGoetje> how about a FF exception?
[16:46] <pitti> well, if it's just another week, a FFE is realistic
[16:46] <asac> for important building blocks we had the mean of FFe in the past
[16:46] <pitti> and for changes that are relatively confined as well
[16:46] <rickspencer3> pitti: can you follow up with ArneGoetje tomorrow and make the call?
[16:47] <pitti> rickspencer3: ack
[16:47] <rickspencer3> asac: what do you have for FF? just flash repos?
[16:48] <pitti> no asac on https://blueprints.edge.launchpad.net/ubuntu/jaunty/+specs
[16:48] <asac> rickspencer3: all i had is done ... but not on the worklist either because there was no spec
[16:48] <rickspencer3> asac: so sounds like you're all good for FF
[16:48] <rickspencer3> bryce: xorg options editor?
[16:48] <asac> rickspencer3: i uploaded new pppd and new network-manager and connman today/yesterda
[16:48] <asac> connman awaits archive admin push
[16:48] <rickspencer3> asac: ack
[16:49] <asac> rickspencer3: all those are not on that list ;)
[16:49] <bryce> rickspencer3: I uploaded it last week, although it got rejected so I think there must be some additional paperwork necessary
[16:49] <rickspencer3> hmmm
[16:49] <rickspencer3> no Qt version, right? That was handled differently in Kubuntu
[16:49] <bryce> unfortunately no details were given in the reject email so I'll have to do some research
[16:49] <pitti> really
[16:49] <pitti> I saw the reject mail, and alberto's reply on the u-archive list, I thought
[16:49] <pitti> some missing license file
[16:50] <bryce> ah, I'm not on u-archive
[16:50] <pitti> sounded easy
[16:50] <bryce> ok cool
[16:50] <pitti> bryce: no, the uploader get's CC:ed
[16:50] <pitti> which was tseliot, I suppose
[16:50] <bryce> ah
[16:50] <pitti> well, s/uploader/person in changelog/
[16:50] <seb128> tseliot already fixed it in bzr
[16:50] <rickspencer3> bryce: could you work with tseliot to get it done tomorrow?
[16:50] <pitti> but sounds as if it's on track
[16:50] <seb128> it just needs to be sponsroed
[16:50] <bryce> rickspencer3: sure thing
[16:50] <seb128> sponsored
[16:50] <pitti>   aspectj |    1.5.4-1 | unstable/contrib | source, all
[16:50] <pitti> sorry, ECHANNEL
[16:51] <tseliot> yes, I fixed it
[16:51] <bryce> tseliot: ready for another upload now?
[16:51] <tseliot> bryce: sure
[16:51] <pitti> ok, next
[16:51] <rickspencer3> bryce: what about xtesting infrastructure
[16:51] <pitti> calc:
[16:52] <pitti> you didn't have any jaunty spec, so you are off the hook in that regard :)
[16:52] <bryce> xsmoke is implemented.  I want to run through it a few times before calling it done though
[16:52] <calc> pitti: ok :)
[16:52] <bryce> it's not FF critical since it's not going into ubuntu proper
[16:52] <pitti> calc: anything you are planning/working on right now which smells FF relevant?
[16:52] <calc> pitti: not really no, i am currently working on split build work, uploaded a new build of OOo 3.0.1 with up to date ooo-build last night
[16:53] <pitti> calc: split build is for jaunty+1, though, I assume?
[16:53] <calc> pitti: yes, assuming it works well, though there are other issues to discuss probably by that point :)
[16:54] <pitti> bryce: radeon-change-xaa-to-exa is a done deal, I think
[16:54] <pitti> bryce: what's missing for "implemented"?
[16:54] <bryce> pitti: yep, it's basically done
[16:54] <bryce> pitti: we're just giving until alpha-5 for reporting regressions
[16:55] <bryce> however there haven't really been many so it's just a formality at this point
[16:55] <pitti> bryce: but we certainly won't revert it past FF?
[16:55] <pitti> well, "hopefully", I think
[16:55] <pitti> ok, great
[16:55] <bryce> pitti: correct, there seems no reason to revert it at this point
[16:56] <pitti> Riddell: kubuntu-jaunty-gap-analysis -> this sounds like some parts are done, and some might get deferred?
[16:56] <Riddell> pitti: yes
[16:56] <Riddell> some bits are deferred
[16:57] <Riddell> and some bits done
[16:57] <pitti> should they be moved to a new blueprint, to not forget about them, and call the jauty bits done?
[16:57] <pitti> well, I'm fine with leaving it open and retitling it karmic as well, depends on what you prefer
[16:58] <pitti> Riddell: kubuntu-jaunty-package-manager sounds like a more atomic issue; how's PK doing so far?
[16:58] <Riddell> hard to know what best to do with these "lots of things in one spec" specs, we have a page on the canonical wiki for "things to do later" that we might copy
[16:58] <pitti> Riddell: right, please feel free to do that
[16:58] <Riddell> pitti: kpackagekit is in and doing well
[16:58] <pitti> great to hear
[16:58] <pitti> Riddell: adept is still in main, should it?
[16:59] <Riddell> pitti: rgreening has been looking into the 'simple Add/Remove interface for Apps' interface and seems to be talking with upstream about how to do it best
[16:59] <bryce> tseliot: 0.2 uploaded
[16:59] <Riddell> pitti: adept can go, I need to fix the depends on update-notifier-kde first
[16:59] <pitti> Riddell: ok; that doesn't seem to be a FF matter then
[16:59] <Riddell> pitti: so the 'simple Add/Remove interface for Apps' is likely deferred in favour of doing it properly upstream
[16:59] <pitti> Riddell: kubuntu-jaunty-setup ?
[16:59] <pitti> Riddell: *nod*
[16:59] <pitti> I think the PK GUIs are not exactly hard to use either
[16:59] <Riddell> kubuntu-jaunty-setup is all done
[17:00] <pitti> in fact they rather lack features than usability IMHO
[17:00] <pitti> Riddell: so "good progress" -> Implemented or "beta avail"?
[17:00] <pitti> ah, saw the description update
[17:00] <Riddell> Implemented I guess, although we might make tweaks depending on feedback for various settings
[17:01] <pitti> so in terms of features this is by and large done
[17:01] <Riddell> yep
[17:01] <pitti> kubuntu-jaunty-setup is a gain a conglomerate
[17:02] <pitti> Riddell: ^ same split handling as kubuntu-jaunty-gap-analysis ?
[17:03] <pitti> in the meantime: pitti -> apport-retracer-maintenance -> all done, and by and large doing what we want; also not FF relevant, since it's infrastructure
[17:03] <Riddell> pitti: I don't think there's anything to be carried over for kubuntu-jaunty-setup
[17:03] <rickspencer3> pitti: do you think the vanilla session thing needs to be done for FF?
[17:03]  * Riddell committed his first line of code to apport today
[17:04] <pitti> rickspencer3: oh crap, completely forgot about that; I think we should get some bits, yes
[17:04] <pitti> rickspencer3: this also involves changing the dx packages
[17:04] <pitti> I don't think it's realistic to get done by thursday, though, so we'll need an FFE for that
[17:04] <pitti> we should have a blueprint for that, though
[17:05] <pitti> Riddell: \o/
[17:05] <rickspencer3> we could a) push to get it done, b) try to postone it to Karmic, c) try to work on exception
[17:05] <pitti> Riddell: ok, thanks for the update; Kubuntu progress looks well, congrats
[17:05] <pitti> rickspencer3: first we need to write down the goal and implementation design, though
[17:05] <rickspencer3> pitti: I started a blueprint and assigned it to you, but due to several bugs in launchpad, it's in "launchpad" instead of "ubuntu"
[17:06] <seb128> pitti, rickspencer3: I don't consider the jaunty bits for that as really a feature since that will not be something installed by default or requiring lot of changes
[17:06] <pitti> rickspencer3: eww
[17:06] <rickspencer3> I thought we discussed this, as you had a much better name for the feature than I had :)
[17:06] <pitti> seb128: FF covers new packages, though, and it's still an Ubuntu feature
[17:06] <pitti> rickspencer3: straciatella? :-)
[17:06] <seb128> pitti: no chance for me to work on that this week
[17:07] <pitti> rickspencer3: let's fix the blueprint after the meeting
[17:07] <pitti> seb128: ack
[17:07] <rickspencer3> that's the name! but I called it "vanilla chocolate chip" or something lame like that
[17:07] <pitti> seb128: gdm-upgrade -> migration code can be done post-FF IMHO
[17:07] <pitti> but the package itself is there and works
[17:07] <seb128> pitti: yes, dx team has no really interest in the new gdm right now and almost nobody replied to my call for testing
[17:08] <bryce> rickspencer3: btw I've gone ahead and marked radeon-change-xaa-to-exa implemented; we're close enough to alpha-5, and there's been no new problems so far tied to EXA.  :-)
[17:08] <pitti> seb128: I saw one happy reply, and I tested it too
[17:08] <seb128> right
[17:08] <seb128> I've been running it for a while too, I came back to the normal gdm to do bootcharts though :-)
[17:08] <pitti> ok, I think that's it
[17:09] <pitti> so except for that straciatella session we should be able to make it, with some extra efforts
[17:09] <pitti> not too many FFEs
[17:09]  * pitti hands the mike back to rickspencer3
[17:09] <rickspencer3> shweet
[17:10] <rickspencer3> btw pitti: nice job getting all your spec work done so early
[17:10] <rickspencer3> looks like we are in decent shape for FF, which is great
[17:10] <pitti> well, it wasn't so much this tim e:)
[17:10] <rickspencer3> Next is a discussion topic regarding Main Inclusion
[17:10] <bryce> whoa, in-place bug title editing.  sweet.
[17:11] <pitti> I did the devkit bits, but those were easy as well
[17:11] <rickspencer3> I think in the interest of time I will move that to email
[17:11] <pitti> bryce: ajax FTW
[17:11] <bryce> pitti: I like
[17:11] <pitti> rickspencer3: MIR?
[17:11] <pitti> rickspencer3: for OLS? done
[17:11] <rickspencer3> pitti: btw, looks like they fixed the bug that kept me from retargetting the blueprint
[17:12] <rickspencer3> pitti: it's more about Main Inclusion guidelines, but I think we should defer the discussion until after FF
[17:12] <pitti> right
[17:12] <rickspencer3> staffing
[17:12] <pitti> hooray!
[17:12] <rickspencer3> Ken VanDine starts tomorrow!
[17:12] <kenvandine> woot!
[17:13] <rickspencer3> Ken, look for a "getting started mail" from me later today
[17:13] <pitti> rickspencer3, seb128, kenvandine: can we have a phone call on Friday to discuss how to get you started?
[17:13] <bryce> welcome aboard kenvandine!
[17:13] <rickspencer3> pitti: of course
[17:13] <calc> kenvandine: looking forward to meeting you in May :)
[17:13] <seb128> pitti: if it's not after european work hours yes
[17:14] <pitti> the getting started tasks, plus diving into the wiki and doing some Debian packaging tutorials should keep you busy until Friday, I guess ;)
[17:14] <rickspencer3> ACTION: rickspencer3 to schedule pitti kenvandine seb128 call for Friday
[17:14] <pitti> seb128: just post-FF, since we all have our hands full, I think
[17:14] <seb128> pitti: right
[17:14] <kenvandine> i am sure
[17:14] <rickspencer3> heh
[17:14] <rickspencer3> ok, welcome to the team ken
[17:14] <pitti> kenvandine: sorry, it's just an unfortunate timing, and I want to take some time for the call and get you started
[17:15] <pitti> kenvandine: oh, and please install current jaunty somewhere :)
[17:15] <kenvandine> sure, i am sure i can stay busy :)
[17:15] <kenvandine> pitti: i have :)
[17:15] <pitti> kenvandine: and you are still online? w00t :)
[17:15] <seb128> kenvandine: welcome, feel free to ask any question on this channel if you have some btw
[17:15] <rickspencer3> pitti: I think it's good to give Ken a couple of days to get his basics in place, so timing is good
[17:15] <kenvandine> pitti: giving me a high level of confidence here :)
[17:15] <rickspencer3> hehe
[17:16] <rickspencer3> next topic: release bugs
[17:16] <rickspencer3> I'm not sure there is much to discuss there, but I want to make sure that everyone is hyper aware of these week to week
[17:16] <pitti> https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[17:16] <pitti> right, I don't think it makes much sense to discuss
[17:17] <pitti> I already bothered everyone with them last Friday, before the release team meeting
[17:17] <pitti> and they aren't really tied to FF (but urgent anyway)
[17:17] <pitti> some are utterly hard, though, and/or depend on upstream actions
[17:17] <bryce> I'm a bit concerned about -intel performance
[17:17] <bryce> we seem stuck between a rock and a hard place
[17:18] <pitti> bryce: EXA being slow?
[17:18] <bryce> pitti: right
[17:19] <bryce> upstream recommends moving to UXA.  Their reply to my concerns about its instability is to forward bugs to them and they'll take a look
[17:19] <bryce> which I guess would work well for them but I'm not confident we'd get enough fixed to make it worth the effort
[17:20] <rickspencer3> ok
[17:20] <LaserJock> does the desktop team take care of abiword?
[17:20] <calc> bryce: is this something that will likely be stable by 10.04 ?
[17:21] <calc> bryce: otherwise we might have to be their bug testers :-\
[17:21] <bryce> calc: oh it pretty well better be ;-)
[17:21] <pitti> LaserJock: we should, primarily a manpower issue
[17:21] <pitti> LaserJock: but there's a pending update to be sponsored
[17:21] <seb128> LaserJock: we are in a middle of a meeting and no the xubuntu does usually
[17:21] <calc> bryce: well i mean if not enough distros test it might still be buggy by then (i assume fedora will be turning on UXA?)
[17:21] <calc> bryce: and by that time EXA support may be completely unusable, heh
[17:22] <seb128> I think we should rather go for stable and slow than faster and buggy
[17:22] <bryce> not sure, but fedora does tend to run pretty close to bleeding edge
[17:22]  * calc just wants to make sure we don't end up broken on a LTS
[17:22] <rickspencer3> moving on
[17:23] <rickspencer3> pitti: release status, anything to discuss there?
[17:24] <pitti> we covered it pretty well
[17:24] <pitti> still blocking on getting the notification stuff
[17:24] <rickspencer3> Riddell: tkamppeter: I still don't have activity reports from you guys for this week, please resend
[17:24] <tkamppeter> rickspencer, I have posted it on the meeting page.
[17:24] <rickspencer3> pitti: dbarth says that you should be able to upload any minute now
[17:25] <rickspencer3> tkamppeter: ack
[17:25]  * pitti needs to run in 5 minutes
[17:25] <rickspencer3> Any other business?
[17:25] <pitti> I'll do it tomororw morning, first thing
[17:25]  * rickspencer3 rubs temples
[17:25] <pitti> seb128: I reviewed their PPA packageging branch it's fine now, BTW
[17:25] <pitti> so if anyone urges you, it's just branch, clean changelog, go
[17:25] <pitti> or anyone else
[17:25] <seb128> pitti: which one?
[17:26] <pitti> seb128: notification daemon
[17:26] <seb128> ah ok
[17:26] <rickspencer3> seb128: may I ask dbarth to ping you when he is ready?
[17:26] <seb128> ok noted
[17:26] <seb128> rickspencer3: yes sure
[17:26]  * rickspencer3 waves goodbye to pitti (who probably has his coat on) ;)
[17:26] <pitti> thanks all
[17:27] <pitti> 8th anniversary today
[17:27] <asac> pitti: congrats
[17:27] <pitti> I really shouldn't be late
[17:27] <bryce> pitti: congrats!
[17:27] <pitti> lest it would be my last :)
[17:27]  * asac hugs pitti 
[17:27] <ArneGoetje> pitti: hurry up!
[17:27] <rickspencer3> pitti: yeah, see you tomorrow, and run~
[17:27] <tkamppeter> 8th anniversary of what?
[17:27] <kenvandine> congrats pitti
[17:27] <pitti> tkamppeter: knowing my wife
[17:27] <seb128> pitti: have fun, see you tomorrow!
[17:27] <pitti> bye everyone
[17:31] <asac> are we done ?
[17:32] <kenvandine> sounded like it to me
[17:32] <asac> seems so. thanks all
[17:32] <asac> kenvandine: when is your official first day?
[17:32] <kenvandine> tomorrow
[17:33] <asac> nice ;)
[17:33] <kenvandine> looking forward to it :)
[17:33] <jeromeg> LaserJock: I packaged the abiword update
[17:34] <bryce> kenvandine: enjoy the sunlight while you still can
[17:34] <kenvandine> hehehehe
[17:34] <kenvandine> i plan to spend the afternoon outside with the kids :)
[17:34] <LaserJock> jeromeg: ok
[17:35] <LaserJock> Sugar needs to do some work on Abiword
[17:35] <asac> kenvandine: enjoy your last day off ;)
[17:35] <kenvandine> :)
[17:35] <LaserJock> but I wanted to find out who would be good to work with and who would care if we broke it ;-)
[17:35] <jeromeg> LaserJock: I fixed some packaging issues, but there are still a lot remaining
[17:35] <jeromeg> LaserJock: as it's shipped by default in Xubuntu, I guess they would not be happy
[17:36] <LaserJock> jeromeg: yeah, that was my guess :-)
[17:36] <LaserJock> we need a libabiword package split out
[17:36] <LaserJock> and python bindings built
[17:36] <jeromeg> I've seen the bug report
[17:37] <LaserJock> jeromeg: you have any thoughts on that?
[17:37] <jeromeg> I think we should work on this with the debian folk
[17:37] <jeromeg> or maintaining this will become a pain
[17:37] <LaserJock> right
[17:38] <LaserJock> but we've also got 2 days until FF
[17:38] <jeromeg> true
[17:38] <LaserJock> jeromeg: are you connected with Debian at all?
[17:38] <LaserJock> the abiword maintainers that is
[17:38] <jeromeg> there is one maintainer
[17:39] <jeromeg> I'm writing him a mail at the moment to share a patch or two
[17:39] <LaserJock> jeromeg: would you mind also asking about this issue?
[17:39] <jeromeg> but I don't have any special contacts with him
[17:39] <jeromeg> LaserJock: will do
[17:40] <LaserJock> jeromeg: awesome, thanks
[17:40] <jeromeg> no problem
[17:40] <jeromeg> LaserJock: if you give me your email adress, I can CC you
[17:41] <LaserJock> jeromeg: laserjock@ubuntu.com
[17:42] <jeromeg> LaserJock: ok, cool
[17:42] <jeromeg> LaserJock: I've something to do right now, but I'll make sure it's sent within two hours
[17:44] <LaserJock> jeromeg: np, thanks a lot
[17:59] <jeromeg> LaserJock: sent
[18:01] <LaserJock> jeromeg: great
[18:02] <jeromeg> LaserJock: I did not insist insist on the freeze, I thought it would be a bit unpolite for a first mail
[18:07] <LaserJock> jeromeg: of course
[18:44] <jeromeg> seb128: upstream is ok with me repackaging the tarball for xfce4-notifyd
[18:44] <seb128> good
[18:44] <jeromeg> Shall I put a higher version number ?
[18:45] <jeromeg> ie 0ubuntu2 ?
[18:46] <seb128> no
[18:46] <seb128> just fix and reupload using the same number
[18:58] <jeromeg> seb128: my sponsor would like to know if you want me to add a +dfsg to the version ?
[19:18] <chrisccoulson> seb128 - there was a recent stable update to gnome-power-manager (2.24.4). do you want me to prepare an update for jaunty?
[19:28] <jcastro> welcome kenvandine!
[19:28] <kenvandine> jcastro: woot!
[19:28] <kenvandine> wow the flood of PMs
[19:29] <pochu> kenvandine: and you're lucky the meeting is here and not in #ubuntu-meeting ;-)
[19:29] <pochu> kenvandine: welcome, btw
[19:29] <kenvandine> hehe
[19:31] <didrocks> jcastro: hey!
[19:32] <didrocks> jcastro: seb128 wanted to ping you because we can't push a branch ~whathever/gnome-python/ubuntu for instance
[19:33] <jcastro> didrocks: I created a gnome-python this morning
[19:33] <jcastro> didrocks: have you tried pushing recently?
[19:33] <didrocks> jcastro: great, let me try to push my branch now
[19:33] <didrocks> jcastro: not today :)
[19:34] <didrocks> jcastro: it works now, thanks :)
[19:34] <jcastro> <3
[19:34]  * didrocks hugs jcastro ;)
[19:42] <fta> seb128, for gwibber, should we ask upstream to mention BSD in COPYING, or is it enough if we fix d/copyrights?
[19:43] <seb128> fta: usually you need to have a copy of the license you use in the tarball
[19:44] <seb128> didrocks: jcastro fixed it apparently so great
[19:44] <seb128> jcastro: thanks
[19:44] <seb128> jeromeg: dunno, who is you sponsor, aren't you supposed to figure those details? I've no clue about abiword and how it's packaged uusually
[19:44] <seb128> chrisccoulson: yes feel free to do it thanks
[19:46] <seb128> I will be back in half an hour if somebody has questions or comments
[19:46] <didrocks> seb128: yes, I added the new branch
[19:46] <didrocks> seb128: I think I will update first my merge of gnome-python-extras, I am tired of waiting libgda update and begins to forget what I have done
[19:46] <seb128> didrocks: do you still have work to do or are you looking for updates?
[19:46] <didrocks> then, I will upload the updates
[19:46] <seb128> didrocks: ok
[19:47] <didrocks> seb128: I have the lib you gave me, but if there is something else, no problem :)
[19:47] <fta> seb128: here, unless i missed something, it's just a user contributed theme, everything else is GPLv2, so i thought mentioning it in d/copyright would be enough, like all multi-license packages i maintain
[19:47] <seb128> ok, that should be enough to keep you busy until I'm back
[19:47] <didrocks> seb128: do I had gnome-python-extras in a branch? We won't upload it at ~ubuntu-desktop because it's in universe
[19:47] <seb128> fta: I'm not a license expert, I just apply what I've been told when I joined the archive admin team in ubuntu
[19:48] <seb128> fta: I guess that's ok if you mention it in the copyright, do that and upload and I will check with pitti tomorrow
[19:48] <fta> ok :)
[19:48] <fta> thanks
[19:48] <seb128> didrocks: you can use bzr for packaging and review if you want
[19:48] <seb128> didrocks: it's not universe
[19:49] <didrocks> seb128: yeah, you're right, I have mixed with something else probably :)
[19:49] <seb128> ok, be back in half an hour
[19:49] <didrocks> ok
[20:36] <didrocks> huats: !!!
[20:37] <didrocks> huats: I really need libgda :)
[20:37] <huats> didrocks: I know
[20:37] <huats> I am working on that right now
[21:01] <huats> seb128: I was looking for you !
[21:01] <didrocks> seb128: I am not able to split only the merge as I had already began the update :/
[21:01] <huats> and didrocks was waiting for me to see you :)
[21:02] <didrocks> seb128: so, I will update the merge + upgrade when libgda will be ready
[21:02] <seb128> hello frenchies
[21:02] <seb128> didrocks: ok
[21:02] <seb128> didrocks: it's annoying to be blocked on huats isn't it? ;-)
[21:03] <huats> bug 330720
[21:03] <jeromeg> seb128: I was speaking about the xfce4-notifyd tarball, I don't have a sponsor for abiword, I still have to find one
[21:03] <jeromeg> but I'll sort the xfce4-notifyd issue with my sponsor
[21:03] <seb128> jeromeg: what was the question again?
[21:04] <seb128> jeromeg: oh, +dfsg? no need for that, the issue is not a dfsg one but a license one
[21:04] <didrocks> seb128: really, the merge was done on 24/01 and it's difficul for me to remember of it :/
[21:04] <jeromeg> ok
[21:04] <huats> seb128: the thing I am the least sure on that is the need of adding conflicts/replace ....
[21:04] <jeromeg> seb128: thanks
[21:04] <seb128> jeromeg: you're welcome
[21:04] <seb128> didrocks: it should just build once libgda is ready?
[21:04] <seb128> huats: let me look
[21:04] <huats> this is really a frenchy place here : seb128, didrocks, jeromeg, myself :)
[21:05] <huats> seb128: sure
[21:05] <seb128> oh, jeromeg is french too?
[21:05] <huats> yep
[21:05] <jeromeg> et ouais
[21:05] <didrocks> huats: that's for sure :)
[21:05] <didrocks> crevette: ?
[21:05] <didrocks> yep crevette is there too \o/
[21:05] <huats> another one :)
[21:05] <seb128> don't forget vuntz
[21:05] <huats> for sure :)
[21:05] <didrocks> free hl for vuntz :)
[21:06] <crevette> yes I am
[21:11] <seb128> huats: you added a suggests on libgda4-jdbc which seems to not be available anywhere where did you find this one?
[21:11] <huats> oh crap
[21:11] <huats> I forgot to remove it on some point...
[21:12] <huats> OK, I'll clean that
[21:12] <huats> (that is didrocks fault who pushes me...)
[21:12] <huats> ;)
[21:13] <seb128> huats: it had been hard to find something to complain about there ;-)
[21:13] <seb128> the update looks pretty good
[21:13] <huats> ok
[21:13] <huats> but there was something :(
[21:13] <seb128> I just read the diff, I'm building it now
[21:13] <didrocks> huats: :p
[21:14] <seb128> huats: why did you remove the flex build-depends too btw?
[21:14]  * huats worships seb128 aka "the man who reads the diff"
[21:14] <seb128> huats: lol
[21:14] <huats> seb128: because it has been removed from the configure checks, if I remember well
[21:16] <seb128> rickspencer3: dunno how you sent your meeting minutes email to the ubuntu-desktop team but it's displayed as a followup for the previous one in my emails client
[21:16] <didrocks> huats: during this time, you can update ubuntu-fr.org/telechargement page :p
[21:16] <rickspencer3> seb128: lol
[21:16] <rickspencer3> I replied to the last one so that I didn't have to copy certain things over again
[21:17] <huats> seb128: I have corrected the suggest and put it on LP
[21:17] <seb128> rickspencer3: you send the reminder for activity report the same way I guess because it does the same ;-)
[21:17] <rickspencer3> thanks for the heads p
[21:17] <seb128> ;-)
[21:17] <rickspencer3> seb128: yeah, thanks for letting me know
[21:17] <seb128> that's alright, just a detail
[21:17] <seb128> I was just curious to know why it was listed as a follow up to the previous one
[21:17] <huats> rickspencer3: you'll notice that seb128 always find something to correct... or is it just when I do something ? ;)
[21:18] <rickspencer3> huats: no critising seb128 for attention to detail!
[21:18] <rickspencer3> we all rely on that :)
[21:18] <rickspencer3> (and if the way I send emails is the worst thing he can point out, then I'm prolly ok ;) )
[21:18] <huats> rickspencer3: I am just teasing seb128. I am really happy with his comments :)
[21:19] <rickspencer3> huats: I know, I was teasing you for teasing him
[21:19] <huats> they are always really helpful :)
[21:23] <seb128> huats: there is no need to add replaces on conflicts, almost everything is versionned, there is only some binaries in -bin and the previous version didn' have those
[21:24] <huats> yeah that is what I noticed
[21:24] <huats> but I was not really confident...
[21:24] <huats> didrocks: sounds good to you ;)
[21:25] <didrocks> huats: hope that :)
[21:26] <pochu> huats: don't forget about lool too
[21:26] <pochu> this should really be #ubuntu-desktop-fr ;)
[21:27] <huats> pochu: how can I forget him... sorry lool :)
[21:28] <huats> seb128: I will tackle anjuta next
[21:28] <huats> :)
[21:28] <pochu> or #ubuntu-ordinateur-de-bureau :)
[21:28] <huats> do you want me to tackle libgdl too ?
[21:28] <huats> pochu: :)
[21:28] <didrocks> pochu: :)
[21:29] <huats> (it will be tomorrow)
[21:29] <didrocks> tomorrow… or later :p
[21:29] <seb128> huats: tackle any of those as you want
[21:29] <seb128> didrocks: do you still have work to do or do you want updates?
[21:30] <didrocks> seb128: I can handle some stuffs tomorrow :)
[21:30] <seb128> didrocks: ok ping me tomorrow then
[21:30] <didrocks> seb128: oki
[21:32]  * lool waves
[21:32] <lool> Folks, I need some help for some C# updates
[21:33] <lool> evolution-sharp and tasque namely
[21:33] <lool> I have prepared the updates and am looking for a reviewer
[21:34]  * pochu stares at slomo ;)
[21:34] <lool> Yeah, well I was hoping to not hit poor slomo again!
[21:34] <lool> slomo: Hey!
[21:35] <pochu> lool: RAOF also does C# stuff. He's in -motu
[21:35] <pochu> and directhex
[21:36] <lool> slomo: I'm not a C# dude (far from it); currently, libevolution-cil would fail on install and so I couldn't try out tasque; I think this was due to the gnome-sharp2 transition but evolution-sharp doesn't build against the latest e-d-s (too recent)
[21:36] <lool> slomo: So I updated libevolution-cil to a new upstream which unfortunately seems to change API; it's libevolution5.0-cil now; I also updated tasque and rebuilt it against that; tasque now starts fine
[21:36] <lool> I have issues with tasque, but that's another topic
[21:37] <lool> slomo: I need some review and guidance on how to proceed; notably I had to update a patch in evolution-sharp which I don't really understand (but seems still needed) and I had to tweak build-deps to drop an alternate bdep, I don't know why
[21:38] <lool> slomo: Also, I would rather have a second pair of eyes before starting this mini-subtransition
[21:38] <lool> slomo: The packages are in my ppa
[21:38] <seb128> lool: you can ask to directhex on the next chan too
[21:38] <seb128> lool: he has been doing most of the C# work in jaunty
[21:38] <lool> Ok
[21:46] <seb128> didrocks: still there?
[21:46] <didrocks> seb128: yes :)
[21:46] <seb128> didrocks: what do you mean by using the jaunty libtool? what else libtool do you expect to use on jaunty?
[21:47] <didrocks> seb128: most of time, you can use autoconf from intrepid one. I guess that most of users who are still on intrepid does
[21:47] <seb128> didrocks: jaunty upgrades should be built and tested on jaunty ;-)
[21:47] <didrocks> here, it's just to explicitely tell that only jaunty libtool (thx to Keybuk update) works on it
[21:48] <didrocks> seb128: even when only autoconf ?
[21:48] <seb128> didrocks: what do you mean? well it's normal to build using the current toolchain, the code might not be new-gcc friendly or something
[21:49] <didrocks> seb128: yes, but when you use pbuider, most of time, people are on stable release and I guess they use autoconf on it…
[21:49] <didrocks> and not in the chroot
[21:49] <seb128> didrocks: there is not lot of GNOME jaunty packages building on intrepid
[21:50] <seb128> didrocks: there is many requesting a new glib or new gtk, etc
[21:50] <didrocks> seb128: it's not about building, just about executing autoconf
[21:51] <seb128> didrocks: ok, I see what you mean, I expect most of people upgrading to jaunty running it that's the easier way to build, test upgrades, etc but I guess if you don't that makes sense
[21:52] <seb128> didrocks: the default assumption is that jaunty updates are done using jaunty tools so the changelog note is somewhat weird, but that's not an issue don't worry ;-)
[21:53] <didrocks> seb128: I understand :) but how can you be sure that all your b-d are listed on debian/control when not building in a pbuilder chroot?
[21:54] <seb128> didrocks: I assume the previous version was correct and diff the configure to see requirement changes
[21:54] <didrocks> seb128: yes, we can assume from that :)
[21:54] <didrocks> s/from//
[21:54] <seb128> didrocks: that works in 95% of the cases and I reupload for the 5% remaining, I found that less annoying that doing 95% of pbuilder use for nothing
[21:55] <didrocks> seb128: I think that I will try this for next release
[21:56] <seb128> well that's not a recommendation, if you are fine with the extra resource use using pbuilder is a nice way to make sure your upgrade builds
[21:57] <seb128> but that's an orthogonal issue to the jaunty use
[21:57] <seb128> you still need a jaunty environment to do the update and test it
[21:57] <didrocks> yes, that's for sure, and a local repository to update them in the VM…
[22:10] <seb128> didrocks: gnome-games uploaded
[22:10] <didrocks> seb128: thanks libgtop2 is on the road
[22:10] <seb128> didrocks: I uploaded the new libgda too which should unblock you tomorrow
[22:11] <didrocks> seb128: great! I hope I made not too much error because the merge was not trivial and I did it some time ago
[22:14] <didrocks> seb128: libgtop ready: bug #330751
[22:15] <didrocks> enough for today. Normally, the new gnome-python-extras is ready. Juste have to testbuild and install tomorrow :)
[22:17] <seb128> ok, have a good night and see you tomorrow
[22:17] <didrocks> seb128: thanks, have a good night too ;)
[22:17] <seb128> thanks
[22:25] <seb128> chrisccoulson: want to do the gnome-session update?
[22:25] <chrisccoulson> yeah, i can do that
[22:25] <seb128> thanks!
[22:26] <chrisccoulson> np
[22:31] <seb128> Laney: there?
[22:31] <Laney> seb128: hi, just got back in
[22:31] <Laney> good timing
[22:31] <seb128> good ;-)
[22:32] <seb128> Laney: do you know what is going on with evolution-mapi? you wouldn't be interested by getting it reviewed and sponsored to universe by any chance?
[22:32] <Laney> I have no idea about that package
[22:32] <Laney> got a bug #?
[22:33] <seb128> bug #319400
[22:34] <huats> seb128: I am back for a few seconds... as I said, I'll tackle the anjuta and the libgdl update tomorrow
[22:34] <huats> you should go to bed btw :)
[22:34] <seb128> huats: ok thanks!
[22:35] <seb128> huats: I should yes but there is still a bunch of sponsoring I want to do before
[22:35] <huats> ok :
[22:35] <huats> :)
[22:35] <huats> I let you work then
[22:36] <seb128> huats: good night!
[22:36] <huats> seb128: thanks !
[22:36] <Laney> seb128: Looks like james_w is on the initial review
[22:36] <Laney> if it gets advocated in the next day or so then I can do the second one
[22:36] <seb128> Laney: well there is no activity recently and feature freeze is this week
[22:37] <seb128> Laney: do they use revu for reviewing it or something?
[22:37] <Laney> the review was yesterday
[22:37] <Laney> yeah
[22:37] <Laney> James made some comments there
[22:37] <seb128> ok good
[22:38] <Laney> I subscribed to it
[22:38] <Laney> so if there's any movement I'll kno
[22:38] <Laney> w
[22:38] <Laney> also if we really need it in Jaunty there's always FFe possibilities
[22:41] <seb128> right
[22:41] <seb128> I can grant those for desktop so that's no issue
[22:41] <seb128> but it's time to get it some testing now
[22:41] <Laney> cool
[22:42] <seb128> it's to allow evolution users to user recent exchange 2007 servers