[11:20] <czajkowski> Aloha
[11:50] <jussi> Hello all.
[11:51] <jussi> When using a poll, how do people in the team know about it? I mail them and tell them, but do I need to then give them a url? or?
[11:51] <apw> does anyone know how often the 'tarball' importer runs for 'series' in launchpad, for example: https://launchpad.net/linux/trunk
[11:51]  * apw has fixed the URL for it, and wondering when i might find out if i did it right
[12:25] <StevenK> apw: That's productreleasefinder, and I think it runs nightly.
[12:26] <apw> StevenK, thanks then i'll look again tommorrow :)
[14:17] <bullgard6> '~$ ubuntu-bug banshee' reports: "/usr/lib/python2.7/dist-packages/gobject/constants.py:24: Warning: g_boxed_type_register_static: assertion `g_type_from_name (name) == 0' failed;   import gobject._gobject; ERROR: hook /usr/share/apport/package-hooks//source_banshee.py crashed: Traceback..." What should I do?
[14:27] <czajkowski> .c
[14:32] <dobey> bullgard6: on what version of ubuntu?
[14:33] <bullgard6> dobey: Ubuntu 11.10 GNOME Shell 3.2.1.
[14:36] <dobey> bullgard6: did it pop up a dialog asking for a choice on what to report the issue on?
[14:37] <bullgard6> dobey: Yes. And I answered that I suppose that the banshee interface is the culprit.
[14:39] <dobey> bullgard6: that's why; the apport UI is runing under gobject-introspection, and that path imports static bindings for gconf/glib, which is causing a crash, it seems
[14:39] <dobey> bullgard6: so maybe you should file a bug against apport too :)
[14:40] <bullgard6> dobey:  I'll give it a try. --  Thank you for advising.
[14:40] <dobey> bullgard6: for banshee, choose the music store option, and comment on the bug that you couldn't choose the banshee option, because of the apport bug
[14:41] <bullgard6> I'll try.
[14:41] <dobey> bullgard6: and in future, apport questions are probably better asked in #ubuntu or #ubuntu-devel
[14:42] <dobey> someplace pitti might be ;)
[14:42] <bullgard6> Ah! I see.
[16:25] <jelmer> hmm, is it just me or is launchpad unusually slow today?
[16:34] <gmb> jelmer: I haven't noticed any slowness myself, but I'd like to have that question enshrined in crystal and set upon the mantlepiece at Launchpad towers. No-one would _ever_ have used the phrase "unusually slow" about Launchpad two years ago.
[16:36] <jelmer> gmb: :)
[16:36] <czajkowski> lol
[17:00] <hrw> hi
[17:01] <hrw> hmm I had an idea but more and more I think of it I see it useless or hard to make good use of it
[17:06] <hrw> I was thinking about page which would allow to choose which builds user wants to see. I have ppas, recipes and would like to see all builds in one place instead of opening few pages.
[17:07] <hrw> but how to limit amount? or set which to track? if user is member of ubuntu-dev then amount would be scary
[17:11] <bigjools> hrw: it would not be difficult to do a basic page, there's already a well-defined interface that objects have to implement if they want to show builds
[17:17] <micahg> hrw: are you familiar with this? https://launchpad.net/~hrw/+related-software (lacks recipies AFAICT)
[17:18] <hrw> micahg: yes, I am familiar with it
[17:18] <hrw> micahg: but it lacks recipes
[20:38] <psusi> bug #39846 shows the big red dash and says lp could not connect to the gnome bug tracker, but when you expand the task, it says it was updated 5 hours ago, and looking at the watch details, it completed successfully the last 3 polls, what gives?
[21:22] <allenap> psusi: It could be that a more recent attempt to contact the bug tracker failed, though I think bug watches are normally only meant to be synced once per day. If Launchpad is trying to sync comments too then they'll be checked more often.
[21:24] <psusi> allenap: it says that was the most recent attempt, next one is scheduled for tomorrow
[21:26] <allenap> psusi: Oh yes :) I guess it failed to connect 6 hours ago, so it keeps the status from the most recent successful sync. The recent activity list may only shows when there's a change.
[21:27] <psusi> it says it succeeded 6 hours ago...
[21:28] <psusi> ohh, nevermind... I guess not
[21:28] <psusi> usually when that happens the recent activity shows the red x with the failure report
[21:29] <psusi> then I guess the question is why does it keep failing to connect ( and not logging it )
[21:31] <Ampelbein> psusi: for the first part: bugzilla.gnome.org can be really really slow to respond so it may hit some kind of set timeout.
[21:33] <psusi> looks like it's been unable to connect for the last 10 months.. it loads right up for me in under a second
[21:35] <psusi> looks like an LP problem?
[21:38] <Ampelbein> seems so
[21:39] <dobey> or the xmlrpc on bugzilla is not working right
[21:40] <dobey> though an oops would be nice to see for sure
[21:42] <allenap> psusi: Other bug watches on b.g.o have succeeded more recently.
[21:45] <psusi> allenap: so why does this one keep failing?
[21:50] <allenap> psusi: Ah, I should go to bed, I keep missing things. Right, so the bug watch has the correct synced status - UNCONFIRMED - but the bugtask is showing New. Which, believe it or not, is correct. I would have guessed it would map UNCONFIRMED to Incomplete, but the code says it gets mapped to New.
[21:52] <EvilResistance> hmm
[21:52] <Ampelbein> allenap: bugzilla UNCONFIRMED == launchpad's new
[21:52] <EvilResistance> is there a reason i'm getting ppa.launchpad.net 404s in my aptitude update logs?
[21:52] <Ampelbein> allenap: to add to the confusion: bugzilla NEW == launchpad's Confirmed
[21:52] <allenap> The way the checkwatches/(external) bugtracker/bugwatch (often interchanged terms) works is arcane and not nearly transparent or obvious enough.
[21:52] <allenap> Ampelbein: Yes, that's right.
[21:53] <allenap> Ampelbein: Yes :)
[21:53] <Ampelbein> allenap: So the mapping is correct, launchpad INCOMPLETE would be bugzilla NEEDSINFO
[21:54] <psusi> allenap: sure, but why does it keep failing when it tries to update?
[21:55] <allenap> psusi: Has it been showing the red dash in the expanded bugtask for a long time? As in, days or weeks?
[21:56] <psusi> allenap: I don't know how long that's been there, but the log for the bug task says it has not had a successful update in 10 months
[21:56] <psusi> log for the watch rather
[21:57] <allenap> psusi: Where does it say that?
[21:57] <allenap> psusi: Do you mean https://bugs.launchpad.net/bugs/39846/+watch/30985?
[21:58] <psusi> allenap: yes
[21:59] <allenap> psusi: That doesn't seem to show the last check. I think that shows the last time something changed.
[22:02] <psusi> allenap: does it only show when things change, or when the check was successful?  I thought it was supposed to show all checks, whether they were changed, or the check failed
[22:04] <allenap> psusi: I'm trying to figure it out. This code is not nice!
[23:08] <cjohnston> do the build delays effect the diffs for MPs? its been 15 minutes since i pushed a branch and the diff hasnt updated.
[23:24] <poolie> cjohnston, no, it shouldn't
[23:24] <poolie> it shouldn't take that long either
[23:24] <poolie> cjohnston, ah, i think there are some bugs with the new feature of live updates to the diff though
[23:24] <poolie> try forcing reloading the page
[23:27] <cjohnston> poolie: still nothing
[23:29] <poolie> which one?
[23:30] <cjohnston> poolie: https://code.launchpad.net/~chrisjohnston/loco-team-portal/locale-teams/+merge/86300?
[23:33] <cjohnston> poolie: no matter what i do, i can't get it to show the new diff
[23:34] <poolie> cjohnston, it looks ok to me, eg it has the UpdateLocaleTeamForm definition
[23:35] <poolie> you don't see that?
[23:35] <cjohnston> I just now got the updated diff.. I refreshed right before I posted and it still showed the yellow waiting bar
[23:37] <poolie> hm i'm not sure then