[00:07] asac, you really *are* a karma whore. [00:38] Does OpenJDK provide a Java Control Panel similar to the Sun JDK's? [06:57] Good morning [06:57] ArneGoetje: hi [08:14] hello there [08:31] * pitti has updated https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus [08:31] quite a number of new issues [08:32] I need a two hour block of intense hacking to work on my RC bugs; back later [08:32] robert_ancell: hi [08:33] robert_ancell: could you open your rhythmbox bug upstream too? ;-) [08:33] seb128: hey seb [08:33] * seb128 read emails from the night [08:33] yes, was going to do that... [08:33] * robert_ancell is bug juggling [08:36] hey mvo [08:36] robert_ancell: how was your day? what did you work on? [08:36] seb128: now I remember... You said not to confirm your own bugs so I was waiting for someone to do that. (which has now been done) [08:36] hey seb128 [08:37] robert_ancell: well you can open your bugs upstream directly though ;-) [08:37] robert_ancell: there is no point to have you open it on launchpad to get me to do the forwarding to bugzilla.gnome.org for example [08:37] opening directly to bugzilla is a win for everybody [08:38] seb128: I spent some more time on 300954 but haven't really made any more progress. I don't have good knowledge of this layer so making slow progress - any other eyes greatly welcome [08:39] robert_ancell: ok, don't spend to much time on it, it's sort of a corner case [08:39] seb128: other than that mostly triaging. Been trying to get vinagre bugs all upstream [08:39] robert_ancell: I got some other higher priority bugs on my list though if you want to have a look to some of those [08:39] robert_ancell: good ;-) [08:40] seb128: a list of bugs would be good. I still don't have a good overview of the problems out there so I'm kind of starting at the bottom hunting for bugs to fix (which is also good so I know which bugs are duplicates) [08:40] does anybody has gnome-sound-properties freezing? [08:41] seb128: regarding the rhythmbox issue: I opened that against Ubuntu because [08:41] seb128: a) I didn't have a GNOME checkout [08:41] seb128: b) It will affect other Ubuntu users [08:41] robert_ancell: https://bugs.edge.launchpad.net/~desktop-bugs, click on the advanced search and select milestoned 9.04 and you get a list of issues that would be nice to work on for jaunty [08:42] robert_ancell: right, I would advice to open on launchpad and upstream in those case or make a comment saying that you will forward upstream after investigation so bug triagers don't pick it up for you [08:43] robert_ancell: I usually don't bother testing on svn we have recent version (ie the current tarball is 2 weeks old) [08:43] but if you test with svn that's better ;-) [08:44] seb128: cool. will do in the future. [08:44] thanks [08:44] robert_ancell: do you have an ipod? ;-) [08:44] seb128: I have a 2nd gen iPod (somewhere) [08:45] robert_ancell: bug #312902 might be not too hard to fix, it's pretty well described in the upstream bug with the faulty code etc [08:45] Launchpad bug 312902 in rhythmbox "Rhythmbox asks to overwrite files during transfer to iPod" [Low,Triaged] https://launchpad.net/bugs/312902 [08:45] robert_ancell: that would be worth fixing if you want to have a look tomorrow [08:45] ok, will do [08:45] robert_ancell: it's just the filename randomization which is not random enough [08:46] it cames with several time the same filename for different track easily [08:46] thanks [08:46] I will add some bugs today to the milestoned list so feel free to watch that list daily too if you want to pick on new jaunty bugs to fix [08:47] seb128: question regarding .deb bug 39812 - is there anything else that can be asked to work out what failed? [08:47] Launchpad bug 39812 in libgnome "installation breaks with 'subprocess post-installation script returned error exit status 245'" [Medium,Invalid] https://launchpad.net/bugs/39812 [08:48] robert_ancell: well if the crash happened only one the odd are that either gconftool-2 or scrollkeeper-update crashed [08:49] that happens sometime but never when you try to valgrind it or not often enough for that [08:49] seb128: would that be logged anywhere? [08:49] no [08:49] the scrollkeeper-update bugs usually seems to be corruptions [08:49] we have the libc stacktraces but that's not useful [08:49] we would need a valgrind log [08:50] some of those issues are also local corruptions, faulty ram or disk errors [08:50] those bugs are either clear issues or weird cases [08:50] don't focus on weird cases [08:50] seb128: so what to do? Close out? [08:50] that one is closed yes [08:51] I usually ask if that happens every time, if "sudo apt-get -f install" still trigger the bug [08:51] and close the bug if it doesn't saying that was a glitch and that we lack informations to debug it [08:52] that's not optimal so if you have a better idea on how to debug those or ask for details feel free to do it ;-) [08:55] no, I have no ideas (except it would be nice if there was some more loggin) [08:55] indeed [08:55] that's probably not a priority for jaunty now [08:55] the rush is on fixing user visible issues [08:56] but we should work on that next cycle [08:57] seb128: another bug question - there are number of bugs like bug 212629 where the issue affects multiple ubuntu packages - how do you stop it affecting a package? For instance this bug was opened against vinagre, then linked to vino so it doesn't really affect vinagre now [08:57] Launchpad bug 212629 in vino "VNC should confirm granting control of desktop" [Unknown,Confirmed] https://launchpad.net/bugs/212629 [08:58] robert_ancell: usually better to change the component than opening a new task [08:58] robert_ancell: just mark the vinagre task invalid if there 2 tasks and only one is correct [08:58] ok [09:00] seb128: calling it a night here, any requests? I'll try and find some meatier bugs tomorrow [09:02] robert_ancell: no, don't spend too much time on side issues but look at the milestoned bugs and help triaging if you can ;-) [09:02] later all [09:12] james_w: hey, congrats you have broken gnome-panel ;-) [09:12] asac: python-xpcom is not installable, is that something we care about? [09:14] james_w: it's only on NX setups so no real worry, I commented on the upstream bug about that [09:14] ah, good to know, thanks [09:15] I assume we'll give it a few days to improve the patch, and then revert if necessary? [09:15] james_w: right [09:15] cool, thanks [09:16] np, thanks for the work on the bug ;-) [09:29] mvo: no [09:29] pitti: actually should be removed from archive together with all xul 1.8 [09:30] i asked lool about mobile-basic-flash, he said they dont need it. i will reconfirm that now ;) [09:30] oh lool is here ;) ^^ [09:56] pitti: https://bugs.edge.launchpad.net/bugs/352968 [09:56] Ubuntu bug 352968 in xulrunner "remove xulrunner 1.8 and all left over rdepend binaries from jaunty archive." [High,Triaged] [10:16] asac: I see; the archive admins will care for that, thanks [10:17] thx === asac_ is now known as asac [10:55] re the indicator applet, on all the other jaunty machines in the office people seem to get a little panel applet with an envelope in it. I don't (having added it to the panel). Is that because I'm using empathy and not pidgin, so nothing is talking to it so it's staying hidden? or should I file a bug? [10:56] Ng: it's meant to appear when pidgin or evolution are running [10:56] fair enough. I'll wait for the future to catch up with me and be Empathy ;) [10:56] thanks ;) [10:56] heh, no problem [10:59] so tracker is still completely broken? [10:59] i told him to index one folder only [11:00] that folder has only one file in it [11:00] still it indexes all the time :( [11:00] and no info given what its currently indexing either (e.g. no mouse hover info) [11:01] asac: open bugs on launchpad, upstream is tracking issues there [11:01] ok. those appeared to be so obvious that i wondered if its maintained at all ;) [11:01] is anyone using tracker here? or am i alone? [11:02] I don't, I don't think it does anything useful [11:02] and it does create io load [11:02] seb128: do we install it by default still? [11:02] no [11:02] ok [11:04] bryce: could you comment on why you think bug #337926 is ct-rev? [11:04] Launchpad bug 337926 in xfree86-driver-synaptics "vino: mouse cursor stays in upper left corner" [Medium,New] https://launchpad.net/bugs/337926 [11:05] asac - i used to use tracker but I stopped using it in Jaunty as my machine grinds to a halt when it's indexing [11:08] seb128: insufficient explanation why it was assigned in the first place [11:08] esp. with bugs that are med prior, you really need to justify why you assign to me, when there are so many high prio X bugs that need attention [11:09] chrisccoulson: yes. i think the problem is that its indexing full HOME ... no matter what [11:09] filed bug 353008 [11:09] Launchpad bug 353008 in tracker "tracker indexes all the time even though only "one" folder with "one" file configured for indexing" [High,Confirmed] https://launchpad.net/bugs/353008 [11:09] at this stage, even with high prio bugs, I am focusing my priorities on ones that have patches or for which a patch is pretty easy to figure out. [11:10] also bug 353010 [11:10] Launchpad bug 353010 in tracker "tracker applet doesn't show what directory/file it currently indexes" [Medium,Confirmed] https://launchpad.net/bugs/353010 [11:10] bryce_: it basically makes vnc unusable for synaptic users in jaunty apparently [11:10] *shrug* [11:10] asac - interesting, i'll try that when i get home. [11:11] i normally use tracker to index my entire home folder, so i didn't notice that [11:11] chrisccoulson: yeah. but even that is most likely just doing something wrong [11:11] i looked at statistics and even though it indexed for 3 days now (the folder with 1 file) [11:11] i only have a few files indexed [11:12] so it definitly makes a lot of noise for nothing [11:12] fixing that might also make indexing HOME better [11:12] that definately sounds like something is wrong [11:12] chrisccoulson: btw want to do the tracker update? [11:12] i think we want a desktop indexer at some point ;) [11:12] seb128 - yeah, i can work on that [11:12] chrisccoulson: there is a new bug fix version, debian did update already [11:12] chrisccoulson: thanks! [11:12] its a shame that it became worse since we first tried to get it installed by default [11:13] hmm [11:13] seb128: honestly I think there are worse X bugs... [11:13] chrisccoulson: if you need a sponsor let me know ;) [11:13] bryce: right, not a reason to drop the bug on the ground though [11:13] seb128: however if y'all uncover a patch I'd be happy to put it in. [11:13] asac - for me, i don't think it's entirely a tracker issue. anything that involves any moderate disk IO on my machine grinds it to a halt, to the point that the mouse cursor stutters and pauses for several seconds at a time [11:14] bryce: not likely I'm not using synaptic, would "downgrade the synaptic xorg package to the intrepid version" do? ;-) [11:14] seb128: how does "unassign myself" == "drop the bug on the ground"?? [11:14] chrisccoulson: yeah, but tracker infinitely grinding doesnt make things better ... even for your IO issues ;) [11:14] bryce: well that's what I meant ct-rev to mean == "not really something we care about" [11:14] i agree :) [11:14] seb128: want something to smile? [11:14] seb128: http://www.sofaraway.org/ubuntu/tmp/karma-seb128.png ;) [11:14] asac: always ;-) [11:15] lol [11:15] somehow makes all your 24/7 bug work voiud [11:15] but still funny [11:15] even me got a boost : http://www.sofaraway.org/ubuntu/tmp/karma-asac.png [11:15] ?? [11:15] asac: they count all the translations updates for the uploads you do [11:15] pitti: look at the ridiculous translation karma everbody gets for uploads [11:15] that's a bug [11:16] seb128: noticed that ;) [11:16] obviously yes ;) [11:16] (bug) [11:16] asac: I'm still beating you on the karma level so that's good :-P [11:16] damn ... [11:16] * asac searches for new tricks [11:17] the answer tracker seems to pay a lot too [11:17] let me reupload nm-applet like 100 times ;) [11:17] seb128: yeah. your answer work seems to carry fruits [11:17] true glory only comes from bug tracker karma ;-) [11:17] do you just move everything thats stupid to answer tracker? [11:18] bryce: previously true glory also came from translations [11:18] you had to translate like 100k strings to get 30k karma ;) [11:18] asac: yes [11:18] now you upload gnome apps and get a massive boost ;) [11:18] asac: bugs which are "nautilus doesn't work please fix it" -> answer tracker [11:19] seb128: i always feel a bit reluctant about doing that because i feel like i should actually make a real question out of it [11:19] and often its mostly like "nothing works here, help!" [11:19] but maybe i should just convert those things too [11:19] asac: days only have 24 hours and I get enough good quality bugs to be busy during those [11:20] seb128: do you follow how well those "stupid" bugs get resolved after making questions out of them? [11:20] there is no point to keep noise there [11:20] no, I just ignore those [11:20] ;) [11:20] the answer tracker guys manage to bounce that back as a bug if they figure that's one [11:20] otherwise I let them deal with answering to users [11:20] enough real bug emails to read [11:21] seb128: can someone make bugs out of them again? [11:21] yes [11:21] i think i had questions that suddenly reappeared as bugs [11:21] there is a convert to bug button there [11:21] ok so thats normal [11:21] the same way there is a convert to question on the bug page [11:21] seb128: can the reporter do that? [11:21] I think so [11:22] ok thats explains it [11:22] so convert to question is still not the "push into sink where reporter cannot come back from again" [11:28] chrisccoulson: are you doing bug triage on tracker a bit too? [11:28] chrisccoulson: almost all crashes are still private ... not sure if upstream sees them [11:28] asac: upstream is doing but they will probably not no [11:29] chrisccoulson: we should at least open them up for upstream ... or subscribe upstream [11:29] I expect most can be marked public, we just need to do that on a regular basis [11:29] maybe adding "tracker" project part would make them open for them? [11:29] shame that we don't get emails about apport-crash bugs [11:30] seb128: right. i am currently looking for someone who could do that regularly ;) [11:30] agree. emails would be nice to trigger bug triage interrupts [11:30] asac: tracker has been mostly rewritten this year, work paid by nokia apparently [11:30] asac: the current team is eager to fix the issue we have too [11:30] do we have that rewrite? === eeejay is now known as eeejay_hummus [11:30] yes [11:30] that 0.6.9n [11:30] that's 0.6.9n [11:30] hmm. so maybe thats the reason it appears like a regression to me [11:31] well there is people paid to work full time on it I think [11:31] so just make sure to open bugs [11:31] they rolled a new bug fix version some days ago [11:31] and they told me they watch launchpad to fix issues reported tehre [11:31] i dont have time for more bug work ;) ... i can do that sporadically, but not reliably ;) [11:31] right [11:31] seb128: thats great. (e.g. that they use launchpad) [11:31] I mean if it doesn't work for you don't hesitate to open a bug [11:32] do they look at ubuntu packages or only "tracker" tasks? [11:32] the ubuntu package I think [11:32] we really have to get crashes out of bug DB imo. if they are anonymized we can just open up and remove coredump after a month or so [11:33] yeah [11:33] well, it's after 3:30 in the morning, I've been working on bugs since 9am. Wife says it's time to go to bed. [11:33] bryce: sleep is for the weak ;) [11:33] bryce: looks like a deserved to get sleep indeed ;-) [11:34] *you* [11:34] bryce: ugh, still awake? [11:34] asac: I'll tell my wife that [11:34] bryce: 'night [11:34] * pitti hugs bryce [11:34] bryce: the problem about huge bug batches is that every mail you send triggers about 3 replies ;) [11:34] so if you sleep you will have a hard time to stay on top [11:34] pitti: sorry I didn't get to the patch you pointed out; it's in the queue though. Will get to it tomorrow. [11:34] bryce: sleep well ;) [11:34] bryce: which patch? [11:35] um... *rummage* [11:35] bryce: btw, I'll update my PPA with the watermark fix again, it got shadowed by your ubuntu4 [11:35] I hope I'll get some more testing feedback soon [11:35] https://bugs.freedesktop.org/show_bug.cgi?id=19304 [11:35] Freedesktop bug 19304 in Driver/intel "[i945 FBC] spontaneous black screen (major pipe-A underrun)" [Major,Reopened] [11:35] bryce: oh, I assigned that to me in Ubuntu [11:35] bryce: I updated the ubuntu bug and called for testing [11:36] ah ok great [11:36] bryce: I can handle that if you want me to [11:36] sure, that'd be a help [11:36] (have a test package in ppa) [11:36] bryce: sleep well! great work [11:36] * bryce --> Zzz [11:39] hi asac, i haven't been working on tracker specifically, but I can dedicate some time to go through some of the old bug reports [11:40] chrisccoulson: do you have access to crashes? [11:40] chrisccoulson: i am mostly concerned about the crashes ... that they get opened up [11:40] chrisccoulson: if you want i can give you a python script that removes CoreDump and open ups [11:40] tbh, a lot of the old crashers can probably be closed. the codebase has changed significantly between 0.6.6 and 0.6.90 and probably makes a lot of them obsolete [11:40] i can access the crashers, so i can probably go through some of them later [11:41] we should autoclose all the < 0.6.90 crashers [11:41] chrisccoulson: yeah thats true. crashers are usually only useless if done in a timely fashion ... but we should take care that that happens in future at least [11:41] asking to try again in jaunty saying it has been rewritten [11:41] s/only useless/only useful/ [11:41] yeah, i think we should probably close the old crashers now too [11:41] that's for tracker [11:41] i can maybe do some of that over my lunch break [11:42] I think we should also autoclose all the apport-crash bugs reported before hardy and which didn't get an update since they have been opened too [11:42] we have so much useless cruft there [11:44] indicator applet keeps losing evo. When I use alltray on evo [11:47] davmor2 - bug 345599? [11:47] Launchpad bug 345599 in indicator-applet "indicator applet disappears" [High,In progress] https://launchpad.net/bugs/345599 [11:50] chrisccoulson: no applet doesn't disappear only evolutions entry in it. [11:50] chrisccoulson: pidgin's stays in [11:52] might still be the same bug though. for me, they both disappear eventually, causing the applet to hide [11:52] chrisccoulson: Ah right thanks [11:57] mvo: do you know if scott richie is online somewhere/somtimes? [12:00] asac: YokoZar [12:00] in #ubuntu-devel [12:02] cool. great [12:18] asac: yes, what pitti said [12:24] * pitti hugs seb128 for nailing bug 325973 [12:24] Launchpad bug 325973 in nautilus "gnome-session keeps respawning nautilus when no desktop is drawed" [Medium,Fix released] https://launchpad.net/bugs/325973 === eeejay_hummus is now known as eeejay [12:50] seb128: when update-manager did its auto-launch dance, what gconf entry has "regular_auto_launch_interval" ? [12:57] * seb128 backs from lunch [12:57] * seb128 hugs pitti [12:57] mvo: no idea I didn't snapshot the system, it's set to 7 right now [13:02] seb128: but its very likely that it was 7 then too, you did not change it in between [13:02] ? [13:02] no I didn't change anything [13:02] I'm acting normal user on this box [13:02] davidbarth: hi [13:02] davidbarth: you forgot to push your notify-osd changes? [13:03] mvo: ahah, got the bug again! [13:03] mvo: I set the key to 0, used synaptic and [13:03] (update-notifier:8262): update-DEBUG: is_package_system_locked: 0 [13:03] (update-notifier:8262): update-DEBUG: interval_days from gconf: 0 [13:03] (update-notifier:8262): update-DEBUG: update_apt_is_running: 0 [13:03] that's "update-notifier --debug-updates" [13:03] seb128: by setting it to 0 this is expected, it will auto-launch every time something is there to update [13:04] mvo: well should it run after each package installed in synaptic? [13:04] mvo: I don't do an apt-get update or anything [13:04] mvo: the situation was similar the other day, the value was 7 and I had 7 days of non updates [13:05] mvo: it if I use synaptic 10 times today I will get update-manager auto opening 10 times [13:10] re [13:10] mvo: what debug flag should I be using? [13:11] seb128: --debug-updates --debug-inotify [13:11] ok, so I run it, update-manager starts, I close it [13:11] until there that's what I expect [13:11] now I open synaptic because I want to update jockey [13:12] I install jockey [13:12] update-manager opens again [13:12] is that expected? [13:12] seb128: that is with auto-open interval set to "0" ? then yes. in your 7 days case (yesterday) it should have noticed that dpkg was run and should not auto-open [13:12] bah [13:12] so that is not a good way to simulate the situation [13:12] what does it compare the 7 days to? [13:13] * seb128 kicks bzr too, stupid thing [13:13] stop telling me to use bzr upgrade, I did it 15 times now [13:13] seb128: gconf timestamp when u-m was run, /var/log/dpkg.log /var/log/apt/term.log [13:13] mtime and ctime [13:13] whatever is newer [13:14] that is what puzzles me :/ [13:14] that it shuld not happen (but then, bugs never should) [13:31] mvo: is there a way to change the ctime? [13:32] seb128: you want to change the ctime of a file? [13:32] pitti: yes [13:32] touch change the mtime and atime but not the ctime apparently [13:32] touch --time=ctime -r reference-file file [13:33] what is reference-file? [13:33] a file which has the time you want to set "file" to [13:34] seb128: if you need an arbitrary time, I'd recomend python -c 'import os; os.utime()' [13:34] ah no, doens't change ctime [13:35] hi, my syslog is flooded with messages from indicator-applet, is that expected? http://paste.ubuntu.com/142020/ [13:36] hey fta2, you only join this channel to report bugs nowadays ;-) [13:37] I would say that's a bug, open it on launchpad [13:37] fta2 - bug 346513 [13:37] Launchpad bug 346513 in indicator-applet ""dbus-daemon: Rejected send message" for indicator-applet spams /var/log/auth.log" [Medium,Confirmed] https://launchpad.net/bugs/346513 [13:37] seb128, i'm always there as 'fta'. all my other clones are bug reporters ;) [13:38] chrisccoulson, ok, thanks [13:38] seb128, i'm always there as 'fta'. all my other clones are bug reporters ;) [13:38] ah ;-) [13:39] i'm fta only on my main desktop at home [13:47] asac, what did you do with your gtk2 patch for ia32-libs? any progress? [13:48] asac, i'm still getting the infamous Gtk-Message: Failed to load module "canberra-gtk-module": /usr/lib/gtk-2.0/modules/libcanberra-gtk-module.so: wrong ELF class: ELFCLASS64 [13:48] let me check if i still have that [13:48] * asac hopes he didnt revert it to hack on something else [13:50] pitti - re bug 351122 - remember that the latest version of glib doesn't convert "%U" in to a URI now where a local path name exists (it substitutes with the local path name instead) [13:50] Launchpad bug 351122 in gthumb "gthumb doesn't work with gphoto (was please disable gphoto2 backend for Jaunty)" [Undecided,In progress] https://launchpad.net/bugs/351122 [13:50] i don't know if that messes up your fix, as I can't test it yet [13:50] but that behaviour is different from intrepid [13:51] chrisccoulson: right, that's why I reopened it [13:52] cool - i wasn't sure if you were aware of that or not, and i wasn't sure if that's what was causing the regression [14:01] hey rickspencer3 [14:01] hey seb128 [14:02] vuntz: do you know how the dbus session bus is started on opensuse? do you let gnome-session start it? [14:03] hey rickspencer3, good morning [14:03] * pitti crosses another 4 bugs from ReleaseStatus [14:09] pitti: woot! [14:39] seb128: I just checked, the code that checks the dpkg and apt log stamps was added 1 march - if the update-notifier running was older than that, that would explain the launching you have seen. I just used a little python script to unset my gconf launch time and the mtimes of the logs, but I did not get the auto launch madness that you had, it correctly read the timestamps from the logs [14:40] mvo: I've not been able to change the ctime to test, I might play with hwclock later [14:43] seb128: I hacked it to set ctime to a very old date iinside update-notifier (os.utime seems to just change mtime). but the effect should be the same [14:44] seb128: so no luck, sorry :( [14:44] mvo: don't worry that's a small issue [14:45] mvo: I'm sure I updated before going to London and I stopped the desktop the week I was not there [14:45] so I was running the mar 1 version or never for sure [14:45] I set it to 1 day now [14:45] I will try again tomorrow [14:48] seb128: maybe you can set the --debug options in the autostart file? so that those are captured in any case? [14:48] will do [14:50] thanks [14:55] pitti: I updated notify-osd to 0.9.8, let me know if I screwed again the bzr ;-) [14:57] pitti: the amd64 retracer crashed again on "KeyError: 'Stacktrace'", I removed the lock I think the retry worked yesterday without untagging [14:58] rickspencer3, good morning, do you have time for a call about package management? [15:31] mpt: I will later [15:32] prolly in an hour or so [15:32] rickspencer3, ok, I'll ask again in an hour :-) [15:35] seb128: hm, since yesterday or today, gnome-panel hangs for me on every startup; I need to open a terminal and killall gnome-panel [15:36] is that known? [15:36] no [15:36] or there is a similar bug but no useful informations there [15:37] ok, I'll give it some more attention then [15:37] get a stacktrace if possible [15:37] the only change yesterday was a patch to better handle multiple monitor situations [15:39] or it's indicator-applet causing a hang or so [15:44] seb128: notify-osd> looks fine! I usually add the changelog when merging from trunk, not in the commit after, but that's just nitpicking [15:44] pitti: ok good ;-) [15:44] pitti: thanks again for the explanations yesterday [16:07] pitti: hey! [16:08] pitti: do you know if it's sensible/possible for a distutils Command to return something from run()? [16:08] or is it supposed to return None always? [16:16] dobey: I don't think it makes sense to return something; you can save internal state in the command object, though [16:16] pitti: well i'm just wondering how to handle failures of things like pylint, pydoctor, unittest, trial test, etc... [16:17] pylint is a more special case i think though [16:19] dobey: raise DistutilsExecError perhaps? [16:19] or DistutilsSetupError [16:19] or a simple assert will probably do as well [16:20] pitti: can you sponsor indicate-python for me? [16:20] bug 344936 [16:20] Launchpad bug 344936 in indicator-applet "initial packaging of indicate-python" [High,In progress] https://launchpad.net/bugs/344936 [16:23] kenvandine_wk: can you please subscribe ubuntu-universe-sponsors and me? I'm quite busy ATM [16:23] I'll try to do it ASAP [16:23] sure [16:24] i already subscribed ubuntu-universe-sponsors [16:24] will add you [16:24] thx! [16:55] argh [16:56] rickspencer3, there was one more thing I needed to discuss [16:56] mpt: ok, I have a call in 3 mins :( [16:56] after that? [16:57] rickspencer3, and that is that either bug 333284 or bug 353195 really really should be fixed for 9.04 [16:57] Launchpad bug 333284 in compiz "With focus_on_map = FALSE, window still opens in front" [Unknown,Confirmed] https://launchpad.net/bugs/333284 [16:57] Launchpad bug 353195 in update-manager "When started automatically, should open minimized and request attention" [Undecided,New] https://launchpad.net/bugs/353195 [16:57] because otherwise, Update Manager grabs focus when you're running Compiz. [16:57]