/srv/irclogs.ubuntu.com/2009/02/17/#ubuntu-desktop.txt

seb128let those for now and we will see if somebody complains00:00
seb128to change then:00:00
seb128- unsplit the C locale00:00
seb128- use replaces to avoid file conflicts error on upgrade00:00
seb128- do the 2.25.91 upgrade00:00
seb128thanks again for your work ;-)00:01
asomethingno problem, I'll include the split with the 2.25.91 upgrade00:01
brycechrisccoulson: you referring to 160_log_timestamping.patch?01:20
chrisccoulsondoes 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 timestamp01:23
chrisccoulsonthe log they provided might have been several months old ;)01:23
chrisccoulsoni've just noticed the timestamps in my own log actually01:31
brycechrisccoulson: you're welcome ;-)01:32
bryceactually they're time since server start, so may not solve the issue in this particular case01:32
chrisccoulsonthe only thing that is missing though is the time that the server actually started01:32
brycechrisccoulson: I'd accept a patch to add that if you'd be up for taking a shot at it; probably a 1-liner01:33
chrisccoulsoni might be able to have a look at that. probably tomorrow though as it's getting quite late here now01:33
brycecool01:33
bryceprobably make sense to slot it in right after the Build Date line01:34
bryceoh hang on01:34
bryce[    0.000982] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Feb 13 11:54:14 200901:35
bryceisn't that it there?01:35
chrisccoulsonah yes, it is there in my log too01:39
chrisccoulsond'oh! i should probably get some sleep01:39
bryce:-)01:41
ovnicraftglatzor?02:40
ovnicraftbryce, hi how i can see the  displayconfig-gtj dependences ?02:41
ovnicrafts/gtj/gtk02:41
=== bluesmoke is now known as Amaranth
=== bluesmoke_ is now known as Amaranth
seb128hello08:18
seb128mvo: hello!08:23
mvohey seb12808:23
mvoseb128: I take brasero and gnome-terminal for a start08:28
seb128mvo: danke08:28
seb128I take evolution-data-server and evolution08:28
seb128lut crevette08:28
crevettesalut08:28
seb128didrocks: hello, want some work? I got libs updates for you ;-)08:28
didrocksseb128: hi :) and yes ;)08:32
didrocksseb128: thanks for all the sponsoring you did yesterday but you have to sleep, you know :)08:32
didrocksseb128: I think you forgot gnome-python (just pass it to whishlist)08:33
didrocksand gnome-python-extra is waiting for libgda08:33
didrockstalking about libgda :p, hey huats!08:33
seb128didrocks: no I didn't, I was not sure if you moved it to the right component or was still junk to use08:33
huatsmorning everyone08:33
huatsI knew you were talking about me...08:33
seb128lut huats08:33
huatshey seb128 and didrocks08:34
didrockshuats: in a bad way, of course :)08:34
huatsthe gda update is ready just need to test it (which is not obvious)08:34
huatsdidrocks: because you can say nice word about me ?08:34
didrockshuats: as usually :)08:34
huatsseb128: gtksourceview2, gucharmap and gnome-syste-monitor are on they way too....08:34
didrocksusual*08:34
huats(well if you haven't done one of them...)08:35
didrocksseb128: let me check for gnome-python08:35
seb128huats: I did upload gucharmap and gnome-system-monitor yesterday night08:35
huatsok08:35
=== BugMaN1 is now known as BugMaN
seb128huats: did you start on those?08:35
huatsseb128: I was trying to find you yesterday but I didn't...08:35
huatsyeah but it is not a big deal... I didn't spend a lot of time... (it was more a parallele task)08:36
huatsseb128: don't worry I'll take care of the gcalctool this morning in order to dry my tears :P08:37
seb128didrocks: there is also gnome-games if you want08:37
seb128huats: want other updates?08:37
huatswhy not...08:37
didrocksdidrocks: yes, I can handle it, and what about the lib updates?08:39
didrocksseb128: there is no gnome-python project08:39
didrocksbzr: ERROR: Invalid url supplied to transport: "lp:~didrocks/gnome-python/ubuntu": No such project: gnome-python08:39
huatsseb128: just a question you had to do a MIR for libgirepository right ?08:40
seb128huats: that doesn't seem ot be a convinced ping, just let me know when you are done with your updates and you want new ones08:40
seb128huats: no, why?08:40
huatsno no I was kidding... give me some updates :)08:41
seb128didrocks: we should ping jcastro do fix that ;-)08:41
seb128jcastro: hello?08:41
huatsbecause 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:41
seb128huats: gucharmap can build bindings using gir but that's not a requirement08:42
vuntzseb128: you joined at 9:18. Tsss. That's so late!08:42
seb128vuntz: do you ever sleep? you uploaded tarballs until 6am08:43
didrocksvuntz: seb128 sponsored a lot of work very late, you know? :)08:43
* vuntz should really roll his panel tarball08:43
huatsseb128: ok08:43
vuntzseb128: I decided to not answer this question today ;-)08:43
didrocksok, not at 6am :p08:43
seb128vuntz: I'm a bit disapointed that neither session storing or the session dialog theming have been fixed though, stop slacking!08:43
huatslike I said I had a rought look at it....08:43
vuntzseb128: session storing: I'm pinging lucasr for his patch08:43
vuntzseb128: session dialog theming: well, you know who to ask...08:44
seb128vuntz: I pinged him on IRC but got no reply, will try again ;-)08:45
seb128vuntz: did you find mvo for your gconf question yesterday?08:45
vuntzdidrocks, huats: btw, congrats for the MOTU promotion!08:46
huatsseb128: so what about those updates ? ;)08:46
huatsvuntz: thanks !08:46
seb128huats: http://download.gnome.org/sources/eog/2.25/eog-2.25.91.tar.gz08:46
huatsok seb12808:46
vuntzseb128: 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
seb128didrocks: http://download.gnome.org/sources/libgtop/2.25/libgtop-2.25.91.tar.gz08:46
seb128huats:08:46
seb128http://download.gnome.org/sources/gtk-engines/2.17/gtk-engines-2.17.3.tar.gz08:47
vuntzseb128: (and because you're stuck with gconf.xml.defaults forever for compatibility)08:47
huatsvuntz: you know it is mainly thanks to the whip of seb128....08:47
vuntzhuats: and then people will say again and again that french people love whips...08:47
huats:)08:47
didrocksseb128: ok. I will do it once gnome-games is ok08:47
seb128vuntz: I think we misunderstood the way it was supposed to work08:47
seb128vuntz: to what change did you look exactly yesterday? to the gconf path we are using?08:48
seb128vuntz: anyway having extra paths in the list doesn't cost much I think08:48
didrocksvuntz: and thanks ;)08:48
vuntzseb128: yeah, looking at your gconf path. It all looks fine. We do the same thing in openSUSE08:48
vuntzseb128: it's just meaningless to have both gconf.xml.system and gconf.xml.defaults08:48
seb128right08:49
vuntz(potentially harmful too since it's confusing for a sysadmin)08:49
vuntzI was discussing with halfline yesterday on how to move all this upstream08:49
seb128so the code now uses gconf.xml.defaults?08:50
vuntzseb128: no, the code uses gconf.xml.system. That's a fedora-ism, because it was developed by a fedora hacker08:50
vuntzseb128: if you or I had written the code, we'd have used gconf.xml.defaults08:50
vuntzseb128: because that's how our gconf path is set08:51
seb128I see08:51
seb128we need dconf ;-)08:51
vuntzanyway, you can do whatever you want. I know I will patch gconf.xml.system out in openSUSE ;-)08:51
seb128I'm pondering what to do now due to upgrades08:51
vuntzwell, 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.system08:52
vuntzso it's still time to kill it ;-)08:52
seb128not in ubuntu08:53
seb128the gconf was added by mvo because he used that to set the system proxy key08:53
vuntzbad him08:53
vuntzslap him hard08:53
seb128lol08:53
* seb128 hugs mvo08:53
vuntzmvo: I still love you, of course08:54
mvovuntz: oh, was that not the right way to do it?08:54
seb128huats: undo gtk-engines it has been done already by somebody else08:55
* mvo reads backlog08:55
huatsseb128: ok08:55
pittihmm; when linking libindicate, I get08:58
pitti/home/martin/ubuntu/dx/indicator-applet-ubuntu/libindicate/listener.c:699: undefined reference to `g_memory_input_stream_new_from_data'08:58
pittido I explicitly need to -lgio?08:59
pittiPKG_CHECK_MODULES(LIBINDICATE, glib-2.0 >= $GLIB_REQUIRED_VERSION08:59
pitti                               gio-2.0 >= $GIO_REQUIRED_VERSION08:59
pittiso that should be ok, in theory?09:00
jeromegpitti: in theory you need to add the flags in your makefiles too09:01
pittihm, somehow this is totally wrecked, nevermind for now09:01
mvovuntz: 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 it09:01
mvovuntz: might be a issue with a early implementation of this interface of course :/09:01
vuntzmvo: 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.system09:01
vuntzmvo: (which is hard to know, I'll admit ;-))09:02
mvovuntz: thanks for this information :)09:02
vuntzmvo: now the questions are "is it too late? Does that matter now that we have one release with it?"09:03
vuntzmvo: and I'll let you decide09:03
seb128pitti: do you have a -lglib2.0 on the ld line?09:03
vuntzseb128: 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 jaunty09:03
pittiseb128: no, but /usr/lib/libglib-2.0.so (totally wrecked)09:04
pittiseb128: I think that's probably it09:04
pittiseb128: oh, hang on, it is there for the libtool call09: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.lo09: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.009:05
pittiseb128: I think that's just missing a -lgio then ?09:05
mvovuntz: I check it out, thanks again09:05
seb128pitti: right09:06
seb128pitti: you need to use $(LIBINDICATE_LIBS) somewhere in your Makefile.am I think09:06
seb128pitti: and $(LIBINDICATE_CFLAGS) maybe too09:07
pittilibindicate_la_LIBADD = \09:07
pitti        $(LIBINDICATE_LIBS)09:07
pittiit does09:08
* pitti just appends -lgio-2.0 and leaves the proper fix to ted09:08
seb128pitti: grep LIBINDICATE_LIBS Makefile.in?09:09
seb128pitti: is the source downloadable somewhere?09:09
mvovuntz: 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 code09:09
pittiseb128: https://edge.launchpad.net/indicator-applet/+download, indicator-applet09:10
pittiseb128: nevermind for now, I'll apply the quickfix and ask Ted09:10
pittiworks now09:10
vuntzmvo: https://api.opensuse.org/public/source/GNOME:Factory/gconf2/gconf2-pk-default-path.patch?rev=c9daf410c2d59d940c81b060cdaa923809:12
vuntzmvo: that's the patch I have in openSUSE09:12
mvocool, thanks vuntz09:12
mvovuntz: will that go upsteam too?09:13
vuntzmvo: 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=c9daf410c2d59d940c81b060cdaa923809:13
vuntzmvo: I've talked with halfline yesterday about it09:13
mvoIIRC mclassen wrote the gconf interface, no?09:13
vuntzmvo: 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
mvoheh .)09:14
mvogood09:14
vuntzmvo: so this will hopefully end up upstream. But in 2.2709:14
mvoI think I apply the patch, I will just need the old location until the next LTS :/09:14
mvo(for backward compat)09:14
vuntzmvo: 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 anyway09:15
vuntz"most people" as in "99.9999%"09:15
seb128pitti: builds fine for me09:15
vuntzokay, make that "99.99%"09:15
mvovuntz: heh .) ok09:16
* mvo scratches his head about it09:16
vuntzmvo: 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
vuntzmvo: but I'm not you ;-)09:17
vuntzand I'm biased09:17
seb128pitti: dunno where you got your pkg_config line, the tarball has09:22
seb128PKG_CHECK_MODULES(LIBINDICATE, glib-2.0 >= $GLIB_REQUIRED_VERSION09:22
seb128                               gdk-pixbuf-2.0 >= $GDK_PIXBUF_REQUIRED_VERSION09:22
seb128                               dbus-glib-1 >= $DBUS_REQUIRED_VERSION)09:22
pittiseb128: weird, I have gio-2.0 there, too09:23
seb128pitti: adding a gio-2.0 line in there fixes the issue09:23
seb128pitti: 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.009:24
pittiseb128: aaah09:24
pittiseb128: that change is in the packaging branch, but not in the tar.gz09:24
pittiseb128: so a mere autoreconf should do it09:24
seb128pitti: you probably need to run autoconf and automake then09:24
seb128pitti: right09:24
mvovuntz: I trust you (famous last words ;)09:27
mvoseb128: new gconf is comming09:27
seb128mvo: thanks!09:27
* mvo hugs vuntz09:27
crevette"debian/patches/05_from_vuntz_gconf2-pk-default-path.patch"09:33
crevette:)09:33
vuntzahah09:35
vuntzpositive way to see it: "yay, I get the credit!"09:36
vuntznegative way to see it: "if it's wrong, everybody will know it's my fault"09:36
seb128vuntz: everybody knows that GNOME being broken is your fault anyway09:36
seb128waouh09:41
seb128the new title edition in launchpad is cool ;-)09:41
didrocksseb128: yeah it's really fun :)09:44
crevettenew title edition ?09:44
didrockscrevette: try to edit a bug title, for instance09:44
didrocks(on edge)09:44
vuntzseb128: is it inline edition?09:45
seb128vuntz: yes09:45
crevetteah okay09:45
seb128vuntz: how do you know? ;-)09:45
didrocksI look the little red animation when you cancel the edition :)09:45
vuntzseb128: don't know. Just makes sense.09:46
pittiseb128: indicator-applet uploaded to NEW10:05
seb128pitti: do you want me to do review?10:06
pittiseb128: if you have some time, that'd be great10:06
seb128pitti: ok, doing that next10:06
jeromegpitti: I managed to fix two additionnal bugs in abiword's packaging which made documentation unusable10:09
jeromegI'm doing a last test build and will attach to LP10:09
pittijeromeg: cool, thanks10:10
jeromegI will forward my fix to debian later, so that we don't divert too much10:10
seb128pitti: ENOTINTHEQUEUE10:12
seb128pitti: are you reviewing the abiword update? I was going to give it a look but I don't want to dup work10:13
jeromegseb128: I'm doing a last test build and will attach and improved package fixing 3 additionnal bugs10:14
seb128jeromeg: ok10:14
pittiseb128: abiword> not today, I'm afraid; dx team packaging, meeting, 8th anniversary with my wife this evening..10:14
seb128pitti: oh, happy anniversary ;-)10:14
seb128pitti: yeah, busy day for me too, new GNOME, dx team, meeting ... doh need to send activity report!10:14
pittiseb128: queue> weird, I uploaded it, and no reject mail so far10:15
seb128pitti: still not there but there is one less item now so maybe somebody else is cleaning10:15
pittiwell, I should have gotten a NEW mail10:15
pittiah, there it is10:15
pittigot caught in the :15 run10:16
seb128ok, it's in the queue10:16
* seb128 fetchs it10:16
mvompt: 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:20
seb128pitti: ok, package looks all fine to me, accepted10:21
mptmvo, that's more of a managerial sort of decision10:22
pittiseb128: thanks10:22
seb128pitti: the .schemas is weird but I will ask ted about that later that's a detail10:22
mptmvo, 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 to10:22
* mvo looks up "managerial"10:22
mvook10:22
jeromegseb128: could you possibly move xfce4-notifyd and xfswitch-plugin out of new ?10:22
mptmvo, 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
mvoyeah :)10:23
mvoI guess I make it two days for now10:23
seb128jeromeg: 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 ones10:23
mptmvo, so if you're quite confident of the code that makes updates weekly, then make it daily during the testing period10:23
mvoso that the interval codes get testing10:23
mptah, good idea10:23
jeromegseb128: we took them from debian svn, it should be safe10:24
mvodo 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
mptmvo, and set yourself at least one reminder alarm to change that period before the freeze :-)10:24
jeromegseb128: Corsac will upload them to debian in the next few days10:24
mvompt: reminder> yes10:25
mptmvo, I don't know. Are there examples of external repositories that change very often? I suppose heavily-in-development PPAs might.10:25
mvompt: 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-devel10:26
mvompt: to gather some data on it10:26
seb128jeromeg: xfswitch-plugin accepted, xfce4-notifyd is not good10:27
seb128jeromeg: xfce4-notifyd sources a GPL2 and the COPYING in GPL310:27
seb128a -> are10:27
jeromegarg10:28
seb128" *  This program is free software; you can redistribute it and/or modify10:28
seb128 *  it under the terms of the GNU General Public License as published by10:28
seb128 *  the Free Software Foundation; version 2 of the License ONLY."10:28
jeromegseb128: ok, thank you very much for the review10:28
seb128you're welcome10:28
jeromegI'll fix this asap10:28
seb128thanks10:28
seb128tseliot: SimpleGladeApp.py is LGPL in xorg-options-editor-gtk and the tarball has no LGPL copy and the debian copyright doesn't list this one10:30
asacbryce: 330108 -> please ack this sponsoring10:39
tseliotseb128: what do you suggest that I do? Shall I add another license file or simply add LGPL to the current COPYING file?10:48
tseliotseb128: and maybe explain it all in the README?10:48
seb128tseliot: add a COPYING.LIB or similar which has the LGPL copy and list in the debian copyright10:49
seb128tseliot: you need to ship the texts for the license you use and the copyright needs to list those10:49
tseliotseb128: ok, I'll do it and I'll update my bzr branch10:50
seb128thanks10:51
jeromegseb128: about xfce4-notifyd, if I patch COPYING with upstream's agreement, is that enough ?12:13
seb128jeromeg: can't you get them to roll a new tarball with a fixed license?12:17
jeromegseb128: I'll see what I can do12:18
seb128jeromeg: if they fix it to their vcs I guess patching for the current version until the next tarball come is ok12:18
jeromegok, that should be easier :D12:18
seb128well if they want their software distributed they should be conciliant and roll a new tarball ;-)12:19
seb128pitti: is your ssh agent working again with the gnome-keyring uploaded yesterday?12:20
jeromegseb128: sure12:20
fta2seb128, thanks for gwibber. i'll clarify that with upstream12:23
seb128fta2: you're welcome12:23
fta2seb128, could I re-up with a fixed tarball but using the same upstream version? or will it be rejected because of md5 mismatch?12:24
pittiseb128: "again"? It never stopped working12:26
seb128pitti: I though it broke for you during the sprint when I uploaded the version which fixed the timeout issue12:26
seb128pitti: we got several bugs about the ssh agent being broken in 2.25.9012:27
seb128asac: ^ does it work for you now?12:27
seb128fta2: you can reupload the same version, the other one has not been accepted or published12:27
asacseb128: dont have 64bit system at hand right now. dholbach also saw this12:28
seb128asac: that was 64b specific?12:28
asacit always worked on 32bit12:28
asacseb128: yes i think so12:28
seb128asac: ok, you didn't tell me that or I didn't note the information ;-)12:29
pittiseb128: oh, during the sprint, yes12:29
pittiseb128: it has worked again for a long time12:29
asacseb128: sorry. i think dholbach noted that in the bug12:29
seb128pitti: ok12:30
seb128asac: I've pinged dholbach and mdz who had the issue too12:31
mvompt: 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:34
mptmvo, the "restart required" is update-notifier, correct? that should come up automatically12:35
mptDoes apport use notification bubbles?12:35
mptI didn't notice that12:35
mvompt: apport uses a notiifcation icon for crashes that happened for system processes12:38
mvompt: or that happend while noone was logged in12:38
mptmvo, just an icon and no bubble? That's fine for now12:39
mvompt: so when the user clicks on it he may get a gksu style dialog first to access the crash12:39
mvompt: it also contains a bubble that just tells about the crash report12:39
mptergh12:40
mptWhat's the exact text of the bubble?12:40
mpt(Thanks for thinking of that case!)12:40
mvohttp://paste.ubuntu.com/119190/12:40
mpt"Click on the notification icon to "12:41
mptrats12:41
mptAnd we can't stuff explanatory text into the gksu dialog, can we?12:42
seb128you are not suggesting auto-opening a gksu dialog right?12:42
mptprobably not :-)12:42
seb128ok good ;-)12:43
mvompt: I guess we could but it would be a bit inconvinent to login and get a dimmed screen12:43
mptexactly12:43
mpthm12:44
mptmvo, what would be the impact of nuking both the icon and the bubble?12:46
mpt-> not providing graphical access to crash reports of system processes12:47
mpt-> ...? Who uses that?12:47
mvompt: nuking the bubble woudl make it less discoverable, nuking the icon means we don't get bugreports for this type of crashes anymore12:47
seb128lot of users looking at launchpad12:47
seb128all the installation issues are reported this way12:47
mpthm, ok12:48
seb128mvo: I would not say no to less installation issues bugs though ;-)12:48
* seb128 runs away from mvo quickly12:49
* mpt thinks seb128 is confusing bugs with bug reports ;-)12:49
mptI guess it should be a preliminary alert that segues into the gksu one, ugh12:49
mptuntil we have a nice Crash Reporter utility thingy12:49
mptok, I'll write this up12:50
mvompt: 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:53
mptmvo, do you have an alternative suggestion?12:54
mvompt: 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:54
mvompt: please still draw the suggestion you have, but its going to be difficult to meet the deadline12:55
mptmvo, ok, the icon only would be tolerable12:55
mptI'll mock up the alert now12:55
mvothanks12:56
mptmvo, maybe bratsche could take care of apport instead13:02
asacmvo: so does the user see partner apps in update-manater?13:06
mvoasac: sure, why not?13:06
mvompt: sure, the code is in update-notifier bzr: src/crash.c - the recent commits should be good templates in what needs to be changed13:08
mvompt: I will leave that change out and upload what I have now and let him add the required code13:08
mptthanks mvo13:09
mvompt: 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 well13:09
mvo?13:09
mptmvo, wait, src/crash.c is in update-notifier? Not in apport?13:09
mvompt: correct, update-notifier acts as the messanger, it detects the files and calls apport13:10
mvo(update-notifier should really be named event-notifier)13:11
mptok13:11
asacmvo: i am not sure why not. because its not enabled?13:17
asacmvo: so are the partner apps visible in update-manager or not? ;)13:17
mvoasac: partner apps are only visable when the partner repo is enabled and a partner app is installed13:20
mvoasac: but then they will show up just fine13:20
asacmvo: ok13:20
jcastroseb128: looking for me?14:12
seb128jcastro: hello14:13
seb128jcastro: could you create a gnome-python component on launchpad? ;-)14:13
jcastroyessir!14:14
seb128thanks ;-)14:14
jcastroI have something for you seb12814:14
jcastrohttps://code.edge.launchpad.net/lp-upstream-tools14:14
jcastroI am announcing this on the bugs list later today14:14
jcastroit will let you mass open upstream tasks14:15
seb128cool, will try that later14:16
seb128I'm busy with GNOME updates right now14:16
jcastrono worries14:16
seb128hey tedg14:17
tedgseb128: Good morning.14:17
seb128tedg: 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 review14:17
tedgseb128: Cool.  I'll look at it.14:17
seb128thanks14:17
pittihey tedg15:04
tedgpitti: Morning, going through your mail :)15:05
seb128vuntz: gnome-panel 2.25.91 fixes the vertical notification area issue (and a similar one with the clock applet when showing the weather)15:22
calcseb128: is there a known issue with gnome panel locking up when attempting to access the clock applet?15:24
calcseb128: its happening to me all the time :\15:24
seb128calc: yes,   http://bugzilla.gnome.org/show_bug.cgi?id=57076515:24
ubottuGnome bug 570765 in Calendar "gnome panel hangs after clicked on the clock applet" [Critical,New]15:24
calcseb128: ok thanks15:24
seb128calc: 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 issue15:25
seb128calc: that's a one line and I will probably upload to jaunty later today15:25
seb128vuntz: ^ do something!15:25
calcseb128: ok, i'm pretty busy today but if i have a chanse before its uploaded i will look at it15:27
pittihey calc15:33
pittiugh, our gpm package is a patch swamp15:36
vuntzseb128: what can I do if it's an eds bug?15:36
seb128vuntz: well whatever e-d-s do the clock should not hang, no?15:38
seb128vuntz: there is an e-d-s bug for sure but the clock not handling e-d-s crashes is a bug too15:38
seb128pitti: talk to tedg ;-)15:38
vuntzseb128: it's a bug in the library part of e-d-s15:40
seb128vuntz: well, shouldn't those calls be async in the clock code?15:40
brycemorning15:40
vuntzseb128: if you read my comment, you can see that I asked: "why don't we have an async version of this function?"15:41
vuntzseb128: so, hrm, what can I do? :-)15:41
seb128vuntz: debug eds? ;-)15:41
vuntzseb128: that's your job ;-)15:43
seb128vuntz: ok, so your job is to make it on a gnome-2-26 targets list15:43
crevetteI was to propse that15:45
crevetteI think it could be a good candidate15:45
vuntzseb128: see, crevette can handle that part ;-)15:46
vuntzit's just a matter of changing the GNOME target in bugzilla15:46
seb128vuntz: well if that's just changing the target and having nobody to care about it then15:46
seb128nobody seems to consider using the clock applet freezing the session as an issue15:47
vuntzseb128: oh andre will care, don't worry ;-)15:48
jeromegseb128: I finally managed to get rid of my ln issues, I attached my improved package to bug #31844415:48
ubottuLaunchpad bug 318444 in abiword "[need-update] abiword to latest stable version 2.6.6 in Ubuntu 9.04" [Wishlist,Triaged] https://launchpad.net/bugs/31844415:48
seb128jeromeg: ok thanks15:48
jeromegseb128: should fix at least 10 bugs on LP15:48
seb128cool15:48
jeromegsome of which were due to our packaging15:49
brycebrb16:03
mvojames_w: hi, do you have a moment?16:14
mvojames_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 now16:14
rickspencer3desktop team meeting in 15 minutes16:15
rickspencer3https://wiki.ubuntu.com/DesktopTeam/Meeting/2009-02-1716:15
james_wmvo: sure, for you anything16:15
mvojames_w: bzr-buildpackage -e gives me a strange layout with a "PaxHeaders" direcotry16:16
mvojames_w: do you have any idea what might be wrong here?16:16
james_wmvo: aha16:16
emberwe already tried to repack the tarball, same error16:16
james_wis this a git export generated tarball?16:17
james_whttps://bugs.launchpad.net/bzr-builddeb/+bug/30393116:17
ubottuUbuntu bug 303931 in bzr-builddeb "Doesn't handle tar extensions" [Medium,Fix committed]16:17
james_wI assume it is that16:18
mvojames_w: hm, that sounds likely, could we have a compat mode? I assume it uses python tarfile =16:20
mvo?16:20
mvoso compat would just run subprocess.call()16:21
mvo?16:21
mvoheh :)16:21
mvokees already did that16:21
james_wmvo: "Fix Committed"16:21
james_w:-)16:21
* mvo hugs james_w16:21
emberheh16:21
james_wlp:bzr-builddeb if you want to use it locally to get going now16:21
mvojames_w: thanks, you are my hero of the day. getting it now16:22
james_wthere are probably a few dragons hiding in that branch though16:22
james_wplease kick me if something doesn't work16:22
mvoheh :) will do16:23
mvoI'm not afraid of dragons, I got a chainmail+2 and a good sword, what could possibly go wrong?16:23
james_wheh16:23
mvobzr-buildpackage is now much happier16:25
james_w\o/16:27
* asac thinks its meeting time16:29
asac@time16:30
* rickspencer3 hammers gavel on table16:30
rickspencer3is everyone here?16:30
asachmm no bot here ;)16:30
ArneGoetjeI am16:30
seb128hey rickspencer316:30
calchi16:30
pittio/16:31
rickspencer3ArneGoetje: asac: bryce: Riddell: pitti: calc: let's go!16:31
ArneGoetjerickspencer3: I'm here16:31
brycealrighty16:31
Riddellhola16:31
rickspencer3First, I know that some of us are under a lot of pressure over the next couple of days, so feel free to ...16:31
rickspencer3work issues off list if you think it will help the meeting go faster16:32
* kenvandine waves howdy16:32
* rickspencer3 wave to Ken16:32
Riddellhi kenvandine16:32
asacmeeting wiki is: http://wiki.ubuntu.com/DesktopTeam/Meeting/2009-02-17/16:32
asachi kenvandine16:32
asacwelcome to the team16:32
rickspencer3outstanding items - bryce, anything on https://launchpad.net/bugs/30948216:32
ubottuUbuntu bug 309482 in xserver-xorg-video-nv "jaunty: Kubuntu OEM enduser setup fails with black screen (nv driver fails)" [Undecided,Incomplete]16:32
rickspencer3while bryce is working on that ...16:33
rickspencer3pitti: graphical installer for server is a non-issue, right?16:33
pittirickspencer3: sorry, forgot about mailing that; please keep it as an action item for me16:33
pittibut it's certainly not jaunty matter16:34
rickspencer3k16:34
kenvandineasac: thx16:34
rickspencer3before we go on, any agenda items to add?16:35
pittiwe'll walk over the specs list, I assume16:36
rickspencer3pitti: yes, I want to review work items for feature freeze readiness16:37
brycerickspencer3: looks like we have a backtrace now; I'll investigate further today16:37
rickspencer3bryce: ack16:37
rickspencer3pitti: do you want to say a few words about Dx integration status?16:37
bryceI 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 more16:37
pittieek, a glibc was detected!16:37
pittiso, today we got the "go!" for the IM indicator stuff16:38
asacrickspencer3: those numbers are wrong right?16:38
rickspencer3the ones on the table, where I have note that says they are wrong ;)16:38
pittiI uploaded three packages related to that, and a patch, seb will look on two other patches to fix notifications16:38
pittiI'm still waiting for the new notification daemon16:38
pittithere are still some open questions wrt. upgrades and automatically enabling them16:39
pittithat'll still require some work16:39
rickspencer3is there an eta for having that figured out? Anything anyone could be doing to help?16:39
seb128I'm discussing some issue with the patch for gsd but that should be uploaded soon16:39
pittirickspencer3: I was promised "today"16:40
pittifor the notification daemon16:40
pittino ETA for migration issues, just got one round of discussion16:40
rickspencer3will the migration issue block FF in your opinion?16:41
pittiit'll need a (minor) FF exception IMHO16:41
pittibut it's borderline16:41
rickspencer3ok16:41
pittibut we can certainly get that16:41
pittiwe have similar code in intrepid for fusa16:41
tkamppeterhi16:41
rickspencer3ok16:41
rickspencer3moving on16:42
rickspencer3let's quickly touch on status with regard to FF, round table style16:42
rickspencer3ArneGoetje: is the language selector on track for Feature Freeze?16:43
ArneGoetjemaybe need a few days more16:43
rickspencer3ArneGoetje: there are no more days16:43
rickspencer3FF is Thursday16:43
pittiwhat's still left? features or just UI changes?16:43
pittiUIF is two weeks later16:43
pittiPKification etc. would need to land by Thursday16:44
pittithrowing around the .glade still has some grace time16:44
ArneGoetjebasically debugging. GUI is done, just the code is not fully workable yet.16:44
Riddellwe don't care about bugs yet :)16:45
rickspencer3so sounds like that is on track for FF16:45
pittiArneGoetje: is it realistic to get something uploaded by Thursday then, even if it's still buggy?16:45
ArneGoetjewell, it's not usable yet16:45
pittioh, hmm16:45
rickspencer3I'm afraid that is at risk for missing Jaunty then16:45
ArneGoetjehow about a FF exception?16:46
pittiwell, if it's just another week, a FFE is realistic16:46
asacfor important building blocks we had the mean of FFe in the past16:46
pittiand for changes that are relatively confined as well16:46
rickspencer3pitti: can you follow up with ArneGoetje tomorrow and make the call?16:46
pittirickspencer3: ack16:47
rickspencer3asac: what do you have for FF? just flash repos?16:47
pittino asac on https://blueprints.edge.launchpad.net/ubuntu/jaunty/+specs16:48
asacrickspencer3: all i had is done ... but not on the worklist either because there was no spec16:48
rickspencer3asac: so sounds like you're all good for FF16:48
rickspencer3bryce: xorg options editor?16:48
asacrickspencer3: i uploaded new pppd and new network-manager and connman today/yesterda16:48
asacconnman awaits archive admin push16:48
rickspencer3asac: ack16:48
asacrickspencer3: all those are not on that list ;)16:49
brycerickspencer3: I uploaded it last week, although it got rejected so I think there must be some additional paperwork necessary16:49
rickspencer3hmmm16:49
rickspencer3no Qt version, right? That was handled differently in Kubuntu16:49
bryceunfortunately no details were given in the reject email so I'll have to do some research16:49
pittireally16:49
pittiI saw the reject mail, and alberto's reply on the u-archive list, I thought16:49
pittisome missing license file16:49
bryceah, I'm not on u-archive16:50
pittisounded easy16:50
bryceok cool16:50
pittibryce: no, the uploader get's CC:ed16:50
pittiwhich was tseliot, I suppose16:50
bryceah16:50
pittiwell, s/uploader/person in changelog/16:50
seb128tseliot already fixed it in bzr16:50
rickspencer3bryce: could you work with tseliot to get it done tomorrow?16:50
pittibut sounds as if it's on track16:50
seb128it just needs to be sponsroed16:50
brycerickspencer3: sure thing16:50
seb128sponsored16:50
pitti  aspectj |    1.5.4-1 | unstable/contrib | source, all16:50
pittisorry, ECHANNEL16:50
tseliotyes, I fixed it16:51
brycetseliot: ready for another upload now?16:51
tseliotbryce: sure16:51
pittiok, next16:51
rickspencer3bryce: what about xtesting infrastructure16:51
pitticalc:16:51
pittiyou didn't have any jaunty spec, so you are off the hook in that regard :)16:52
brycexsmoke is implemented.  I want to run through it a few times before calling it done though16:52
calcpitti: ok :)16:52
bryceit's not FF critical since it's not going into ubuntu proper16:52
pitticalc: anything you are planning/working on right now which smells FF relevant?16:52
calcpitti: 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 night16:52
pitticalc: split build is for jaunty+1, though, I assume?16:53
calcpitti: yes, assuming it works well, though there are other issues to discuss probably by that point :)16:53
pittibryce: radeon-change-xaa-to-exa is a done deal, I think16:54
pittibryce: what's missing for "implemented"?16:54
brycepitti: yep, it's basically done16:54
brycepitti: we're just giving until alpha-5 for reporting regressions16:54
brycehowever there haven't really been many so it's just a formality at this point16:55
pittibryce: but we certainly won't revert it past FF?16:55
pittiwell, "hopefully", I think16:55
pittiok, great16:55
brycepitti: correct, there seems no reason to revert it at this point16:55
pittiRiddell: kubuntu-jaunty-gap-analysis -> this sounds like some parts are done, and some might get deferred?16:56
Riddellpitti: yes16:56
Riddellsome bits are deferred16:56
Riddelland some bits done16:57
pittishould they be moved to a new blueprint, to not forget about them, and call the jauty bits done?16:57
pittiwell, I'm fine with leaving it open and retitling it karmic as well, depends on what you prefer16:57
pittiRiddell: kubuntu-jaunty-package-manager sounds like a more atomic issue; how's PK doing so far?16:58
Riddellhard 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 copy16:58
pittiRiddell: right, please feel free to do that16:58
Riddellpitti: kpackagekit is in and doing well16:58
pittigreat to hear16:58
pittiRiddell: adept is still in main, should it?16:58
Riddellpitti: 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 best16:59
brycetseliot: 0.2 uploaded16:59
Riddellpitti: adept can go, I need to fix the depends on update-notifier-kde first16:59
pittiRiddell: ok; that doesn't seem to be a FF matter then16:59
Riddellpitti: so the 'simple Add/Remove interface for Apps' is likely deferred in favour of doing it properly upstream16:59
pittiRiddell: kubuntu-jaunty-setup ?16:59
pittiRiddell: *nod*16:59
pittiI think the PK GUIs are not exactly hard to use either16:59
Riddellkubuntu-jaunty-setup is all done16:59
pittiin fact they rather lack features than usability IMHO17:00
pittiRiddell: so "good progress" -> Implemented or "beta avail"?17:00
pittiah, saw the description update17:00
RiddellImplemented I guess, although we might make tweaks depending on feedback for various settings17:00
pittiso in terms of features this is by and large done17:01
Riddellyep17:01
pittikubuntu-jaunty-setup is a gain a conglomerate17:01
pittiRiddell: ^ same split handling as kubuntu-jaunty-gap-analysis ?17:02
pittiin the meantime: pitti -> apport-retracer-maintenance -> all done, and by and large doing what we want; also not FF relevant, since it's infrastructure17:03
Riddellpitti: I don't think there's anything to be carried over for kubuntu-jaunty-setup17:03
rickspencer3pitti: do you think the vanilla session thing needs to be done for FF?17:03
* Riddell committed his first line of code to apport today17:03
pittirickspencer3: oh crap, completely forgot about that; I think we should get some bits, yes17:04
pittirickspencer3: this also involves changing the dx packages17:04
pittiI don't think it's realistic to get done by thursday, though, so we'll need an FFE for that17:04
pittiwe should have a blueprint for that, though17:04
pittiRiddell: \o/17:05
rickspencer3we could a) push to get it done, b) try to postone it to Karmic, c) try to work on exception17:05
pittiRiddell: ok, thanks for the update; Kubuntu progress looks well, congrats17:05
pittirickspencer3: first we need to write down the goal and implementation design, though17:05
rickspencer3pitti: I started a blueprint and assigned it to you, but due to several bugs in launchpad, it's in "launchpad" instead of "ubuntu"17:05
seb128pitti, 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 changes17:06
pittirickspencer3: eww17:06
rickspencer3I thought we discussed this, as you had a much better name for the feature than I had :)17:06
pittiseb128: FF covers new packages, though, and it's still an Ubuntu feature17:06
pittirickspencer3: straciatella? :-)17:06
seb128pitti: no chance for me to work on that this week17:06
pittirickspencer3: let's fix the blueprint after the meeting17:07
pittiseb128: ack17:07
rickspencer3that's the name! but I called it "vanilla chocolate chip" or something lame like that17:07
pittiseb128: gdm-upgrade -> migration code can be done post-FF IMHO17:07
pittibut the package itself is there and works17:07
seb128pitti: yes, dx team has no really interest in the new gdm right now and almost nobody replied to my call for testing17:07
brycerickspencer3: 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
pittiseb128: I saw one happy reply, and I tested it too17:08
seb128right17:08
seb128I've been running it for a while too, I came back to the normal gdm to do bootcharts though :-)17:08
pittiok, I think that's it17:08
pittiso except for that straciatella session we should be able to make it, with some extra efforts17:09
pittinot too many FFEs17:09
* pitti hands the mike back to rickspencer317:09
rickspencer3shweet17:09
rickspencer3btw pitti: nice job getting all your spec work done so early17:10
rickspencer3looks like we are in decent shape for FF, which is great17:10
pittiwell, it wasn't so much this tim e:)17:10
rickspencer3Next is a discussion topic regarding Main Inclusion17:10
brycewhoa, in-place bug title editing.  sweet.17:10
pittiI did the devkit bits, but those were easy as well17:11
rickspencer3I think in the interest of time I will move that to email17:11
pittibryce: ajax FTW17:11
brycepitti: I like17:11
pittirickspencer3: MIR?17:11
pittirickspencer3: for OLS? done17:11
rickspencer3pitti: btw, looks like they fixed the bug that kept me from retargetting the blueprint17:11
rickspencer3pitti: it's more about Main Inclusion guidelines, but I think we should defer the discussion until after FF17:12
pittiright17:12
rickspencer3staffing17:12
pittihooray!17:12
rickspencer3Ken VanDine starts tomorrow!17:12
kenvandinewoot!17:12
rickspencer3Ken, look for a "getting started mail" from me later today17:13
pittirickspencer3, seb128, kenvandine: can we have a phone call on Friday to discuss how to get you started?17:13
brycewelcome aboard kenvandine!17:13
rickspencer3pitti: of course17:13
calckenvandine: looking forward to meeting you in May :)17:13
seb128pitti: if it's not after european work hours yes17:13
pittithe getting started tasks, plus diving into the wiki and doing some Debian packaging tutorials should keep you busy until Friday, I guess ;)17:14
rickspencer3ACTION: rickspencer3 to schedule pitti kenvandine seb128 call for Friday17:14
pittiseb128: just post-FF, since we all have our hands full, I think17:14
seb128pitti: right17:14
kenvandinei am sure17:14
rickspencer3heh17:14
rickspencer3ok, welcome to the team ken17:14
pittikenvandine: sorry, it's just an unfortunate timing, and I want to take some time for the call and get you started17:14
pittikenvandine: oh, and please install current jaunty somewhere :)17:15
kenvandinesure, i am sure i can stay busy :)17:15
kenvandinepitti: i have :)17:15
pittikenvandine: and you are still online? w00t :)17:15
seb128kenvandine: welcome, feel free to ask any question on this channel if you have some btw17:15
rickspencer3pitti: I think it's good to give Ken a couple of days to get his basics in place, so timing is good17:15
kenvandinepitti: giving me a high level of confidence here :)17:15
rickspencer3hehe17:15
rickspencer3next topic: release bugs17:16
rickspencer3I'm not sure there is much to discuss there, but I want to make sure that everyone is hyper aware of these week to week17:16
pittihttps://wiki.ubuntu.com/DesktopTeam/ReleaseStatus17:16
pittiright, I don't think it makes much sense to discuss17:16
pittiI already bothered everyone with them last Friday, before the release team meeting17:17
pittiand they aren't really tied to FF (but urgent anyway)17:17
pittisome are utterly hard, though, and/or depend on upstream actions17:17
bryceI'm a bit concerned about -intel performance17:17
brycewe seem stuck between a rock and a hard place17:17
pittibryce: EXA being slow?17:18
brycepitti: right17:18
bryceupstream recommends moving to UXA.  Their reply to my concerns about its instability is to forward bugs to them and they'll take a look17:19
brycewhich I guess would work well for them but I'm not confident we'd get enough fixed to make it worth the effort17:19
rickspencer3ok17:20
LaserJockdoes the desktop team take care of abiword?17:20
calcbryce: is this something that will likely be stable by 10.04 ?17:20
calcbryce: otherwise we might have to be their bug testers :-\17:21
brycecalc: oh it pretty well better be ;-)17:21
pittiLaserJock: we should, primarily a manpower issue17:21
pittiLaserJock: but there's a pending update to be sponsored17:21
seb128LaserJock: we are in a middle of a meeting and no the xubuntu does usually17:21
calcbryce: 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
calcbryce: and by that time EXA support may be completely unusable, heh17:21
seb128I think we should rather go for stable and slow than faster and buggy17:22
brycenot sure, but fedora does tend to run pretty close to bleeding edge17:22
* calc just wants to make sure we don't end up broken on a LTS17:22
rickspencer3moving on17:22
rickspencer3pitti: release status, anything to discuss there?17:23
pittiwe covered it pretty well17:24
pittistill blocking on getting the notification stuff17:24
rickspencer3Riddell: tkamppeter: I still don't have activity reports from you guys for this week, please resend17:24
tkamppeterrickspencer, I have posted it on the meeting page.17:24
rickspencer3pitti: dbarth says that you should be able to upload any minute now17:24
rickspencer3tkamppeter: ack17:25
* pitti needs to run in 5 minutes17:25
rickspencer3Any other business?17:25
pittiI'll do it tomororw morning, first thing17:25
* rickspencer3 rubs temples17:25
pittiseb128: I reviewed their PPA packageging branch it's fine now, BTW17:25
pittiso if anyone urges you, it's just branch, clean changelog, go17:25
pittior anyone else17:25
seb128pitti: which one?17:25
pittiseb128: notification daemon17:26
seb128ah ok17:26
rickspencer3seb128: may I ask dbarth to ping you when he is ready?17:26
seb128ok noted17:26
seb128rickspencer3: yes sure17:26
* rickspencer3 waves goodbye to pitti (who probably has his coat on) ;)17:26
pittithanks all17:26
pitti8th anniversary today17:27
asacpitti: congrats17:27
pittiI really shouldn't be late17:27
brycepitti: congrats!17:27
pittilest it would be my last :)17:27
* asac hugs pitti 17:27
ArneGoetjepitti: hurry up!17:27
rickspencer3pitti: yeah, see you tomorrow, and run~17:27
tkamppeter8th anniversary of what?17:27
kenvandinecongrats pitti17:27
pittitkamppeter: knowing my wife17:27
seb128pitti: have fun, see you tomorrow!17:27
pittibye everyone17:27
asacare we done ?17:31
kenvandinesounded like it to me17:32
asacseems so. thanks all17:32
asackenvandine: when is your official first day?17:32
kenvandinetomorrow17:32
asacnice ;)17:33
kenvandinelooking forward to it :)17:33
jeromegLaserJock: I packaged the abiword update17:33
brycekenvandine: enjoy the sunlight while you still can17:34
kenvandinehehehehe17:34
kenvandinei plan to spend the afternoon outside with the kids :)17:34
LaserJockjeromeg: ok17:34
LaserJockSugar needs to do some work on Abiword17:35
asackenvandine: enjoy your last day off ;)17:35
kenvandine:)17:35
LaserJockbut I wanted to find out who would be good to work with and who would care if we broke it ;-)17:35
jeromegLaserJock: I fixed some packaging issues, but there are still a lot remaining17:35
jeromegLaserJock: as it's shipped by default in Xubuntu, I guess they would not be happy17:35
LaserJockjeromeg: yeah, that was my guess :-)17:36
LaserJockwe need a libabiword package split out17:36
LaserJockand python bindings built17:36
jeromegI've seen the bug report17:36
LaserJockjeromeg: you have any thoughts on that?17:37
jeromegI think we should work on this with the debian folk17:37
jeromegor maintaining this will become a pain17:37
LaserJockright17:37
LaserJockbut we've also got 2 days until FF17:38
jeromegtrue17:38
LaserJockjeromeg: are you connected with Debian at all?17:38
LaserJockthe abiword maintainers that is17:38
jeromegthere is one maintainer17:38
jeromegI'm writing him a mail at the moment to share a patch or two17:39
LaserJockjeromeg: would you mind also asking about this issue?17:39
jeromegbut I don't have any special contacts with him17:39
jeromegLaserJock: will do17:39
LaserJockjeromeg: awesome, thanks17:40
jeromegno problem17:40
jeromegLaserJock: if you give me your email adress, I can CC you17:40
LaserJockjeromeg: laserjock@ubuntu.com17:41
jeromegLaserJock: ok, cool17:42
jeromegLaserJock: I've something to do right now, but I'll make sure it's sent within two hours17:42
LaserJockjeromeg: np, thanks a lot17:44
jeromegLaserJock: sent17:59
LaserJockjeromeg: great18:01
=== bluesmoke_ is now known as Amaranth
jeromegLaserJock: I did not insist insist on the freeze, I thought it would be a bit unpolite for a first mail18:02
=== spinus is now known as Spinus
LaserJockjeromeg: of course18:07
jeromegseb128: upstream is ok with me repackaging the tarball for xfce4-notifyd18:44
seb128good18:44
jeromegShall I put a higher version number ?18:44
jeromegie 0ubuntu2 ?18:45
seb128no18:46
seb128just fix and reupload using the same number18:46
jeromegseb128: my sponsor would like to know if you want me to add a +dfsg to the version ?18:58
chrisccoulsonseb128 - there was a recent stable update to gnome-power-manager (2.24.4). do you want me to prepare an update for jaunty?19:18
=== andreasn_ is now known as andreasn
jcastrowelcome kenvandine!19:28
kenvandinejcastro: woot!19:28
kenvandinewow the flood of PMs19:28
pochukenvandine: and you're lucky the meeting is here and not in #ubuntu-meeting ;-)19:29
pochukenvandine: welcome, btw19:29
kenvandinehehe19:29
didrocksjcastro: hey!19:31
didrocksjcastro: seb128 wanted to ping you because we can't push a branch ~whathever/gnome-python/ubuntu for instance19:32
=== asac_ is now known as asac
jcastrodidrocks: I created a gnome-python this morning19:33
jcastrodidrocks: have you tried pushing recently?19:33
didrocksjcastro: great, let me try to push my branch now19:33
didrocksjcastro: not today :)19:33
didrocksjcastro: it works now, thanks :)19:34
jcastro<319:34
* didrocks hugs jcastro ;)19:34
ftaseb128, for gwibber, should we ask upstream to mention BSD in COPYING, or is it enough if we fix d/copyrights?19:42
seb128fta: usually you need to have a copy of the license you use in the tarball19:43
seb128didrocks: jcastro fixed it apparently so great19:44
seb128jcastro: thanks19:44
seb128jeromeg: dunno, who is you sponsor, aren't you supposed to figure those details? I've no clue about abiword and how it's packaged uusually19:44
seb128chrisccoulson: yes feel free to do it thanks19:44
seb128I will be back in half an hour if somebody has questions or comments19:46
didrocksseb128: yes, I added the new branch19:46
didrocksseb128: 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 done19:46
seb128didrocks: do you still have work to do or are you looking for updates?19:46
didrocksthen, I will upload the updates19:46
seb128didrocks: ok19:46
didrocksseb128: I have the lib you gave me, but if there is something else, no problem :)19:47
ftaseb128: 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 maintain19:47
seb128ok, that should be enough to keep you busy until I'm back19:47
didrocksseb128: do I had gnome-python-extras in a branch? We won't upload it at ~ubuntu-desktop because it's in universe19:47
seb128fta: I'm not a license expert, I just apply what I've been told when I joined the archive admin team in ubuntu19:47
seb128fta: I guess that's ok if you mention it in the copyright, do that and upload and I will check with pitti tomorrow19:48
ftaok :)19:48
ftathanks19:48
seb128didrocks: you can use bzr for packaging and review if you want19:48
seb128didrocks: it's not universe19:48
didrocksseb128: yeah, you're right, I have mixed with something else probably :)19:49
seb128ok, be back in half an hour19:49
didrocksok19:49
didrockshuats: !!!20:36
didrockshuats: I really need libgda :)20:37
huatsdidrocks: I know20:37
huatsI am working on that right now20:37
huatsseb128: I was looking for you !21:01
didrocksseb128: I am not able to split only the merge as I had already began the update :/21:01
huatsand didrocks was waiting for me to see you :)21:01
didrocksseb128: so, I will update the merge + upgrade when libgda will be ready21:02
seb128hello frenchies21:02
seb128didrocks: ok21:02
seb128didrocks: it's annoying to be blocked on huats isn't it? ;-)21:02
huatsbug 33072021:03
ubottuLaunchpad bug 330720 in libgda3 "Please sponsor libgda4 3.99.11 into jaunty" [Wishlist,New] https://launchpad.net/bugs/33072021:03
jeromegseb128: I was speaking about the xfce4-notifyd tarball, I don't have a sponsor for abiword, I still have to find one21:03
jeromegbut I'll sort the xfce4-notifyd issue with my sponsor21:03
seb128jeromeg: what was the question again?21:03
seb128jeromeg: oh, +dfsg? no need for that, the issue is not a dfsg one but a license one21:04
didrocksseb128: really, the merge was done on 24/01 and it's difficul for me to remember of it :/21:04
jeromegok21:04
huatsseb128: the thing I am the least sure on that is the need of adding conflicts/replace ....21:04
jeromegseb128: thanks21:04
seb128jeromeg: you're welcome21:04
seb128didrocks: it should just build once libgda is ready?21:04
seb128huats: let me look21:04
huatsthis is really a frenchy place here : seb128, didrocks, jeromeg, myself :)21:04
huatsseb128: sure21:05
seb128oh, jeromeg is french too?21:05
huatsyep21:05
jeromeget ouais21:05
didrockshuats: that's for sure :)21:05
didrockscrevette: ?21:05
didrocksyep crevette is there too \o/21:05
huatsanother one :)21:05
seb128don't forget vuntz21:05
huatsfor sure :)21:05
didrocksfree hl for vuntz :)21:05
crevetteyes I am21:06
seb128huats: you added a suggests on libgda4-jdbc which seems to not be available anywhere where did you find this one?21:11
huatsoh crap21:11
huatsI forgot to remove it on some point...21:11
huatsOK, I'll clean that21:12
huats(that is didrocks fault who pushes me...)21:12
huats;)21:12
seb128huats: it had been hard to find something to complain about there ;-)21:13
seb128the update looks pretty good21:13
huatsok21:13
huatsbut there was something :(21:13
seb128I just read the diff, I'm building it now21:13
didrockshuats: :p21:13
seb128huats: why did you remove the flex build-depends too btw?21:14
* huats worships seb128 aka "the man who reads the diff"21:14
seb128huats: lol21:14
huatsseb128: because it has been removed from the configure checks, if I remember well21:14
seb128rickspencer3: 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 client21:16
didrockshuats: during this time, you can update ubuntu-fr.org/telechargement page :p21:16
rickspencer3seb128: lol21:16
rickspencer3I replied to the last one so that I didn't have to copy certain things over again21:16
huatsseb128: I have corrected the suggest and put it on LP21:17
seb128rickspencer3: you send the reminder for activity report the same way I guess because it does the same ;-)21:17
rickspencer3thanks for the heads p21:17
seb128;-)21:17
rickspencer3seb128: yeah, thanks for letting me know21:17
seb128that's alright, just a detail21:17
seb128I was just curious to know why it was listed as a follow up to the previous one21:17
huatsrickspencer3: you'll notice that seb128 always find something to correct... or is it just when I do something ? ;)21:17
rickspencer3huats: no critising seb128 for attention to detail!21:18
rickspencer3we 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
huatsrickspencer3: I am just teasing seb128. I am really happy with his comments :)21:18
rickspencer3huats: I know, I was teasing you for teasing him21:19
huatsthey are always really helpful :)21:19
seb128huats: 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 those21:23
huatsyeah that is what I noticed21:24
huatsbut I was not really confident...21:24
huatsdidrocks: sounds good to you ;)21:24
didrockshuats: hope that :)21:25
pochuhuats: don't forget about lool too21:26
pochuthis should really be #ubuntu-desktop-fr ;)21:26
huatspochu: how can I forget him... sorry lool :)21:27
huatsseb128: I will tackle anjuta next21:28
huats:)21:28
pochuor #ubuntu-ordinateur-de-bureau :)21:28
huatsdo you want me to tackle libgdl too ?21:28
huatspochu: :)21:28
didrockspochu: :)21:28
huats(it will be tomorrow)21:29
didrockstomorrow… or later :p21:29
seb128huats: tackle any of those as you want21:29
seb128didrocks: do you still have work to do or do you want updates?21:29
didrocksseb128: I can handle some stuffs tomorrow :)21:30
seb128didrocks: ok ping me tomorrow then21:30
didrocksseb128: oki21:30
* lool waves21:32
loolFolks, I need some help for some C# updates21:32
loolevolution-sharp and tasque namely21:33
loolI have prepared the updates and am looking for a reviewer21:33
* pochu stares at slomo ;)21:34
loolYeah, well I was hoping to not hit poor slomo again!21:34
loolslomo: Hey!21:34
pochulool: RAOF also does C# stuff. He's in -motu21:35
pochuand directhex21:35
loolslomo: 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
loolslomo: 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 fine21:36
loolI have issues with tasque, but that's another topic21:36
loolslomo: 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 why21:37
loolslomo: Also, I would rather have a second pair of eyes before starting this mini-subtransition21:38
loolslomo: The packages are in my ppa21:38
seb128lool: you can ask to directhex on the next chan too21:38
seb128lool: he has been doing most of the C# work in jaunty21:38
loolOk21:38
seb128didrocks: still there?21:46
didrocksseb128: yes :)21:46
seb128didrocks: what do you mean by using the jaunty libtool? what else libtool do you expect to use on jaunty?21:46
didrocksseb128: most of time, you can use autoconf from intrepid one. I guess that most of users who are still on intrepid does21:47
seb128didrocks: jaunty upgrades should be built and tested on jaunty ;-)21:47
didrockshere, it's just to explicitely tell that only jaunty libtool (thx to Keybuk update) works on it21:47
didrocksseb128: even when only autoconf ?21:48
seb128didrocks: what do you mean? well it's normal to build using the current toolchain, the code might not be new-gcc friendly or something21:48
didrocksseb128: yes, but when you use pbuider, most of time, people are on stable release and I guess they use autoconf on it…21:49
didrocksand not in the chroot21:49
seb128didrocks: there is not lot of GNOME jaunty packages building on intrepid21:49
seb128didrocks: there is many requesting a new glib or new gtk, etc21:50
didrocksseb128: it's not about building, just about executing autoconf21:50
seb128didrocks: 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 sense21:51
seb128didrocks: 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:52
didrocksseb128: 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:53
seb128didrocks: I assume the previous version was correct and diff the configure to see requirement changes21:54
didrocksseb128: yes, we can assume from that :)21:54
didrockss/from//21:54
seb128didrocks: 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 nothing21:54
didrocksseb128: I think that I will try this for next release21:55
seb128well 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 builds21:56
seb128but that's an orthogonal issue to the jaunty use21:57
seb128you still need a jaunty environment to do the update and test it21:57
didrocksyes, that's for sure, and a local repository to update them in the VM…21:57
seb128didrocks: gnome-games uploaded22:10
didrocksseb128: thanks libgtop2 is on the road22:10
seb128didrocks: I uploaded the new libgda too which should unblock you tomorrow22:10
didrocksseb128: great! I hope I made not too much error because the merge was not trivial and I did it some time ago22:11
didrocksseb128: libgtop ready: bug #33075122:14
ubottuLaunchpad bug 330751 in libgtop "Please, sponsor libgtop 2.25.91 into jaunty" [Wishlist,Triaged] https://launchpad.net/bugs/33075122:14
didrocksenough for today. Normally, the new gnome-python-extras is ready. Juste have to testbuild and install tomorrow :)22:15
seb128ok, have a good night and see you tomorrow22:17
didrocksseb128: thanks, have a good night too ;)22:17
seb128thanks22:17
seb128chrisccoulson: want to do the gnome-session update?22:25
chrisccoulsonyeah, i can do that22:25
seb128thanks!22:25
chrisccoulsonnp22:26
seb128Laney: there?22:31
Laneyseb128: hi, just got back in22:31
Laneygood timing22:31
seb128good ;-)22:31
seb128Laney: 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
LaneyI have no idea about that package22:32
Laneygot a bug #?22:32
seb128bug #31940022:33
ubottuLaunchpad bug 319400 in ubuntu "[needs-packaging] evolution-mapi " [Wishlist,In progress] https://launchpad.net/bugs/31940022:33
huatsseb128: I am back for a few seconds... as I said, I'll tackle the anjuta and the libgdl update tomorrow22:34
huatsyou should go to bed btw :)22:34
seb128huats: ok thanks!22:34
seb128huats: I should yes but there is still a bunch of sponsoring I want to do before22:35
huatsok :22:35
huats:)22:35
huatsI let you work then22:35
seb128huats: good night!22:36
huatsseb128: thanks !22:36
Laneyseb128: Looks like james_w is on the initial review22:36
Laneyif it gets advocated in the next day or so then I can do the second one22:36
seb128Laney: well there is no activity recently and feature freeze is this week22:36
seb128Laney: do they use revu for reviewing it or something?22:37
Laneythe review was yesterday22:37
Laneyyeah22:37
LaneyJames made some comments there22:37
seb128ok good22:37
LaneyI subscribed to it22:38
Laneyso if there's any movement I'll kno22:38
Laneyw22:38
Laneyalso if we really need it in Jaunty there's always FFe possibilities22:38
seb128right22:41
seb128I can grant those for desktop so that's no issue22:41
seb128but it's time to get it some testing now22:41
Laneycool22:41
seb128it's to allow evolution users to user recent exchange 2007 servers22:42

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!