[00:05] <nigelb> 26
[00:05] <nigelb> grr
[00:55] <StevenK> wgrant: I have private bug with nothing, with subscriber and with structural subscriber, asserting on what getBugNotificationRecipients() returns. I'm obviously missing a bunch of scenarios
[00:56] <wgrant> There are three implicit subscriber cases: structural subscriptions, dupe subscriptions, and assignees.
[00:57] <wgrant> I'm not sure if dupe assignees and dupe structsubs also count.
[00:58] <StevenK> wgrant: So assignee sounds a good plan -- I've not thought about dupes yet
[01:25] <StevenK> wgrant: Blink.
[01:25] <StevenK> wgrant: IBug.markAsDuplicate() recalculates heat, but so does IBug._markAsDuplicate() which the former calls.
[01:27] <wgrant> StevenK: markAsDuplicate recalculates the heat of the new master, _markAsDuplicate recalculates the heat of the old.
[01:27] <StevenK> Ah
[01:38] <StevenK> wgrant: http://pastebin.ubuntu.com/1107437/
[01:54] <wgrant> StevenK: A good start, indeed.
[01:56] <StevenK> wgrant: Do you think it's worthwhile expanding out to public bugs?
[02:04] <wgrant> StevenK: Certainly
[02:04] <wgrant> StevenK: It is to be a thorough set of tests for getBugNotificationRecipients
[02:04] <wgrant> It's hardly comprehensive or thorough if it doesn't do public bugs too.
[02:15] <lifeless> gary_poster: nice mail :)
[04:15] <StevenK> wgrant: http://pastebin.ubuntu.com/1107562/  bugwatch is up next, and then subscribed to question linked to bug
[04:15] <StevenK> Then I might be done
[04:32] <StevenK> wgrant: So now that hilarity has passed, bugwatches?
[04:34] <wgrant> StevenK: How are watches involved?
[04:34] <StevenK> wgrant: sinzui implicates them
[04:35] <wgrant> Hm
[04:35] <wgrant> That's odd.
[04:35] <StevenK> wgrant: I don't know how they work. :-(
[04:36] <StevenK> Well, I know they link to an external bugtracker and checkwatches does something to some watches and then hangs.
[04:36] <StevenK> But can a watch have subscribers or impact on getBugNotificationRecipients()?
[04:40] <wgrant> No
[04:40] <wgrant> I don't believe they're relevant here at all.
[04:41] <StevenK> I shall ignore them, then
[04:41]  * StevenK moves onto working on how to staple a question and bug together
[05:17] <StevenK> wallyworld, wgrant: https://code.launchpad.net/~stevenk/launchpad/bugnotification-testcases/+merge/116402
[05:23] <wgrant> StevenK: Looking
[05:30] <wgrant> StevenK: https://code.launchpad.net/~wgrant/launchpad/faster-checkCanBeDeleted/+merge/116404
[05:32] <StevenK> wgrant: r=me, looks great
[05:33] <wgrant> Thanks.
[05:33] <StevenK> wgrant: What about my review? :-)
[05:34] <wgrant> StevenK: Looking
[05:34] <wgrant> What's + def test_public_bug_with_duplicate_same_pillar_subscriber(self):?
[05:35] <StevenK> wgrant: Both bugs are against the same pillar
[05:35] <wgrant> Yes, but why?
[05:35] <wgrant> How's it relevant as a separate case?
[05:36] <StevenK> The private case will be different, and I did the same cases for public bugs
[05:36] <StevenK> I can condense the two public duplicate tests if you wish
[05:36] <wgrant> I don't see how the private case is different.
[05:36] <wgrant> It's matters whether the subscriber has access
[05:37] <wgrant> Not whether it's a different pillar.
[05:37] <StevenK> wgrant: It will be -- give an APG against the pillar
[05:37] <wgrant> StevenK: Und?
[05:37] <wgrant> That's the case where there's an APG against the pillar
[05:37] <wgrant> Not the case where they're the same pillar
[05:38] <StevenK> wgrant: Right, so condense the four down to test?
[05:38] <StevenK> Down to two, rather
[05:38] <wgrant> Right
[05:38] <wgrant> Test things that should be tested because they make a difference.
[05:38] <StevenK> I split it out due to sinzui's mail
[05:39] <wgrant> Also, do the tests pass?
[05:40] <StevenK> They do
[05:41] <wgrant> Huh
[05:41] <wgrant> How does the question one work...
[05:41] <wgrant> Oh god
[05:41] <wgrant> Question.linkBug subscribes the question owner
[05:41] <wgrant> What could possibly go wrong.
[05:42] <StevenK> WCPGW, right?
[05:42] <StevenK> :-)
[05:42] <wgrant> Implicit access grants are bad, m'kay.
[05:42] <StevenK> Yes, I'm not sure the two question tests add value
[05:42] <wgrant> They don't.
[05:42] <StevenK> Bin them too?
[05:42] <wgrant> Yes
[05:42] <wgrant> Let me read sinzui's mail
[05:42] <wgrant> Ah
[05:42] <wgrant> So he
[05:43] <wgrant> probably speaks of the bug->question notification forwards
[05:43] <wgrant> I'm not quite sure how they work
[05:43] <wgrant> But they're separate from this
[05:43] <wgrant> So don't need to be considered here, at least not yet.
[05:52] <wgrant> StevenK: Are you sure that all of xx-initial-bug-contacts.txt is duplicated?
[05:54] <StevenK> wgrant: It was sinzui's suggestion that it be binned since much of the test will fail to be true in a few weeks with the bug supervisor and security team playing
[05:55] <wgrant> StevenK: Sure, but it covers a whole lot of stuff that's only barely related to what you're adding tests for
[05:55] <wgrant> Like setting the bug supervisor
[05:55] <wgrant> And the security contact being subscribed by default
[05:56] <StevenK> Bug supervisor is also dying horribly too?
[05:56] <StevenK> Security contact is also changing after we can filter on information type
[06:00] <wgrant> StevenK: Bug supervisor is not dying.
[06:00] <wgrant> Its role is changing.
[06:00] <wgrant> Security contact will probably die entirely.
[06:00] <wgrant> We will still need to be able to set the bug supervisor.
[06:01] <StevenK> I can shuffle that part into a browser test easily
[06:01] <wgrant> Rogjt
[06:01] <wgrant> Right
[06:01] <wgrant> But you can't just delete it
[06:01] <wgrant> Without confirming that it's been replaced, or replacing it yourself
[06:02] <StevenK> lib/lp/bugs/browser/tests/test_bugsupervisor.py:class TestBugSupervisorEditView(TestCaseWithFactory):
[06:02] <StevenK> Does that count?
[06:02] <wgrant> If it tests the same stuff, sure.
[06:08] <wgrant> Oops
[06:31] <StevenK> wgrant: Diff updated, I've added new tests for the Change bug supervisor link
[06:31] <StevenK> And I'm still 164 lines in credit
[06:48] <wgrant> StevenK: Thanks
[06:49] <StevenK> wgrant: Thanks. Did you see the branch I just landed?
[06:51] <wgrant> Aha
[06:51] <wgrant> I think only two of those were mine
[06:53] <wgrant> Yay
[06:53] <wgrant> Only one actual bug in bugsummary maintenance
[06:53] <wgrant> And one in the rebuild script
[07:32] <wgrant> StevenK: https://code.launchpad.net/~wgrant/launchpad/bug-1028279/+merge/116411
[07:32] <wgrant> StevenK: (yes, this is very similar to your thing which broke everything, but I like to live dangerously)
[07:44] <adeuring> good morning
[10:34] <Ergo^> morning
[10:35] <Ergo^> gary_poster, hello, im looking for some info on the position
[10:35] <Ergo^> http://blog.launchpad.net/were-hiring/were-hiring-software-engineers-to-work-on-cloud-projects-in-canonical
[10:35] <Ergo^> czajkowski, said i should be asking you about it
[10:35] <lifeless> or gmb
[10:36] <czajkowski> gmb: ping
[10:36] <lifeless> gary will be asleep right now (I hope!)
[10:36] <Ergo^> haha ok :]
[10:36] <czajkowski> Ergo^: mornign more of the developers are online now
[10:36] <czajkowski> and in fact gmb is on hols
[10:36] <czajkowski> wgrant: might you be able to answer some of Ergo^ questions on lp dev please, he's thinking of applying for one of the roles
[10:38] <wgrant> I'm trying to not be here :)
[10:38] <wgrant> 'cause it's getting late
[10:38] <czajkowski> I know but I cant find any EU folks up atm
[10:39] <wgrant> gmb can't be too far away
[10:39] <Ergo^> wgrant, carry on, i can ask later ;-)
[10:39] <czajkowski> adeuring: allenap ping are either of you about ?
[10:39] <jpds> wgrant: From where you are?
[10:40]  * adeuring is looking
[10:40] <wgrant> Heh
[10:40] <czajkowski> jpds: AU
[10:40] <czajkowski> although he never sleeps
[10:40] <czajkowski> adeuring: thanks
[10:40] <czajkowski> Ergo^: adeuring might be able to answer some of your questions
[10:40] <czajkowski> Ergo^: thanks for coming and asking though
[10:42] <adeuring> Ergo^: I think you should wait for gmb if you have more specific questions about the job.
[10:43] <adeuring> But we can of course anwser more generic questions about Canonical ;)
[10:45] <Ergo^> well, i would be interested to what i would work on and what kind of skill level would be expected for the position
[10:47] <Ergo^> adeuring, i've never worked for a IT organization that would have many employees, so im not sure what i would ask about :-)
[10:50] <adeuring> Ergo^: I don't know much what the the work is about aside from the general "cloudy" stuff... Regarding an org with "many" employees: I myself do not notice that much about the number of people employed by Canonical. You will work i a relatively small team, I assume. four or five people probably.
[11:05] <Ergo^> czajkowski, can i pm you ?
[11:10] <czajkowski> Ergo^: sure
[11:12] <allenap> Ergo^: gmb will be able to tell you more about the team's first project, but, like adeuring, there isn't the feel of "big company IT". We try to produce the best code we can, in a professional way; I have learnt *so* much about how to produce large pieces of software from working here. We're rigorous about testing, and we try to make decisions based on evidence and measurement. We don't always get it right, but we tend to see mistakes a
[11:12] <allenap> s an opportunity to learn rather than to blame.
[11:12] <lifeless> Ergo^: the new squad will be working on ceilometer initially.
[11:12] <lifeless> allenap: +1
[11:12] <czajkowski> lifeless: go sleep!
[11:13] <lifeless> one word: Cynthia.
[11:13] <allenap> Ha!
[11:14] <czajkowski> lifeless: awww
[11:15] <Ergo^> ok, well i work in environment where we dont write tests at all - they move more like early facebook - the boss doesnt want to budget for tests
[11:15] <Ergo^> but theres no problem to write tests
[11:16] <Ergo^> i would love to move to environment where i can learn new things
[11:19] <Ergo^> lifeless, so ceilometer - what kind of web stack will be used for the project? pylons/pyramid? something home brewed ?
[11:23] <lifeless> have a poke around yourself - https://launchpad.net/ceilometer
[11:25] <Ergo^> oh it uses webob
[11:25] <Ergo^> nice :]
[11:25] <Ergo^> and sqlalchemy, even nicer
[11:25] <Ergo^> i was expecting it would be using sqlstorm
[11:25] <rick_h_> Ergo^: hey howdy
[11:26] <Ergo^> ohai rick_h_
[11:26] <rick_h_> Ergo^: you were hacking on some of the min-webhelpers stuff right?
[11:26] <Ergo^> rick_h_, yeah ive made html.grid stuff
[11:26] <rick_h_> Ergo^: heh, not going to see much of the usual stack around :/
[11:26] <rick_h_> but really good dev practices, some stuff to learn for sure
[11:27] <Ergo^> rick_h_, well i would love that because i wont learn new things the place im at atm
[11:27] <Ergo^> different focus
[11:27] <rick_h_> Ergo^: definitely apply if you might be interested and chat with the guys. They're a really good group of smart peeps.
[11:27] <Ergo^> i would be, question is if they would be :P
[11:30] <Ergo^> rick_h_, well even if its not stack im used to it has some parts i know and love, so thats a good start
[11:30] <rick_h_> right, the launchpad stack is kind of strange, but you're allowed to learn it. I didn't know anything more than some articles of zope stuff
[11:30] <rick_h_> but most other things are django based
[11:31]  * Ergo^ knows nothing about django
[11:31] <rick_h_> heh, it's 'easy' :P
[11:32] <Ergo^> i would expect pylons/pyramid based wsgi apps, since i would expect its more flexible for this kind of environment
[11:32] <rick_h_> you'd think...but no. I've not won a battle on that front yet though there are some of us trying
[11:33] <Ergo^> rick_h_, i would expect mramm to help ;-)
[11:33] <rick_h_> hah, I'll have to ask him what his team's up to on that end I guess.
[11:34] <lifeless> go
[11:34] <lifeless> they are all about go
[11:34] <Ergo^> yeah he mentioned he writes in go right now last time ive asked
[11:35] <rick_h_> ah, he's over there
[11:47] <Ergo^> well, the ive browsed the code for ceilometer, it seems understandable and nice for me :]
[12:23] <rick_h_> czajkowski: looks like the report a bug link failure is fixed yay
[12:24] <Ergo^> rick_h_, when do you plan to add a human friendly interface to launchpad ? ;-)
[12:24] <rick_h_> Ergo^: heh, that's huw's job :P
[12:49] <Bert_2> Hi, I have setup an instance of launchpad with an actual domain (not launchpad.dev) and a clean db using wgrant's bootstrap-db-from-scratch and have added users using his user creationscript, now nor the admin nor regular users seem to be able to login into the subdomains of my instance (code, answers, blueprints), when I login with any account it redirects back to the page I came from but I'm still not logged in, does anyone know what'
[12:49] <Bert_2> s wrong ? Did I misconfigure something ?
[13:07] <Ergo^> gmb, ping
[13:11] <deryck> Good morning, all.
[13:17] <abentley> deryck: morning.
[13:18] <abentley> deryck: http://www.goodreads.com/quotes/14559-good-morning-said-bilbo-and-he-meant-it-the-sun
[13:28] <deryck> abentley, heh.  Great passage.
[13:28] <deryck> I knew there was a reason I normally typed only "morning" :)
[13:30] <abentley> deryck: Hehe.
[13:33] <deryck> adeuring, https://plus.google.com/hangouts/_/5c02c8b06ff0d06aaf9314c93315d217f5459977?authuser=0&hl=en
[13:57] <Ergo^> gmb, ping
[14:00] <czajkowski> Ergo^: he's not here. and won't be for two weeks
[14:01] <Ergo^> ah :]
[14:01] <Ergo^> rick_h_, so you say i should apply ? ;-)
[14:01] <rick_h_> Ergo^: give it a go and talk with them.
[14:08] <deryck> Ergo^ is a friend of rick_h_?
[15:49] <abentley> deryck: Currently, the mustache_model and the mustache_template from the server can be used by the javascript verbatim to render an identical result to the server-side rendering.
[15:49] <abentley> deryck: This is because the mustache_model includes control variables that affect the rendering, even though they're not logically part of the model.
[15:50] <deryck> abentley, ok.  are you wanting to change this where only the template can be rendered?  Or something else?
[15:51] <abentley> deryck: With the new pystache, we could remove all control variables from the mustache_model, which would be cleaner, but would break this property that the JS can use the model verbatim.
[15:52] <deryck> abentley, is there a downside to not using the model verbatim?
[15:52] <abentley> deryck: The downside is it's a bit more work to get an identical rendering between client-side and server-side rendering.
[15:53] <abentley> deryck: (but it's work we already do)
[15:54] <deryck> abentley, ah, I think I see.  We just do it via variables in the model, where as we need to specify those values at the call site now. right?
[15:55] <abentley> deryck: Yes, we need to inject the control variables at the call site, if they're not in the data sent by the server.
[15:57] <deryck> abentley, sounds fine to me.  Seems cleaner on both ends to me.  i.e. model is cleaner and rendering is explicit.
[15:57] <abentley> deryck: Cool.
[16:02] <Ergo^> heh i think i should install ubuntu :/
[17:20] <rick_h_> doh, forgot to put myself as ocr
[17:20] <rick_h_> and since I am... jcsackett can I bug you please? https://code.launchpad.net/~rharding/launchpad/lpclient_fix/+merge/116338
[17:24] <jcsackett> rick_h_: sure.
[17:24] <rick_h_> jcsackett: ty much kind sir
[19:05] <jcsackett> rick_h_: sorry, forgot to ping you when i finished reviewing your branch.
[19:05] <jcsackett> it is r=me.
[19:05] <rick_h_72> Thanks it's off to ec2. thanks again!
[19:32] <cody-somerville> Why are some versions listed twice under 'Releases in Ubuntu'? https://launchpad.net/ubuntu/precise/+source/thunderbird
[19:43] <Bert_2> wgrant: are you here ?
[20:00] <abentley> rick_h_: still around?
[20:01] <rick_h_> abentley: yep, what's up?
[20:01] <abentley> rick_h_: Could you please review https://code.launchpad.net/~abentley/launchpad/restore-queue-test/+merge/116534 ?
[20:02] <rick_h_> abentley: loading up now
[20:03] <abentley> rick_h_: Thanks.
[20:05] <rick_h_> abentley: what's task_init meant to do?
[20:06] <rick_h_> abentley: nvm, looking
[20:06] <abentley> rick_h_: It sets up a launchpad scripting environment.
[20:16] <rick_h_> abentley: couple of questions (side notes) r=me ty much
[20:16] <abentley> rick_h_: Thanks.'
[20:35] <rick_h_> jcsackett: ping
[20:35] <rick_h_> jcsackett: in your MP it says the 'helper method is removed' which I'm reading as userCanAccessUserData as being removed but it's not?
[20:39] <Bert_2> Does anyone know why I'm perfectly able to log in on the main section of my launchpad instance but not on the other sections like code and answers ? I don't get any errors but after supplying info to openid I just don't get logged in, any suggestions ?
[21:47] <sinzui> wgrant: StevenK: jcsackett: wallyworld: this is the non-published link of what I did today: http://youtu.be/Vq6VsKuFY_o
[22:04] <wgrant> Bert_2: Did you set cookie_domains to include your new domain?
[22:04] <wgrant> Bert_2: That controls how wildcardy the cookies are
[22:35] <sinzui> wallyworld: you are proposing to fix 3 or more of thses bugs https://bugs.launchpad.net/launchpad/+bugs?field.tag=bug-links
[22:38] <sinzui> wallyworld: http://blog.launchpad.net/general/bug-linking-part-2 "Linking existing bugs"
[22:46] <Bert_2> wgrant: where can I set the cookie_domains ?
[22:47] <wgrant> Bert_2: the development config inherits the default value from lib/lp/services/config/schema-lazr.conf. You can override it in your own config.
[22:47] <wgrant> # Session cookies being sent to a subdomain of the parent
[22:47] <wgrant> # domains listed here will be sent to the parent domain,
[22:47] <wgrant> # allowing sessions to be shared between vhosts.
[22:47] <wgrant> # Domains should not start with a leading '.'.
[22:47] <wgrant> cookie_domains: demo.launchpad.net, staging.launchpad.net, launchpad.net, launchpad.dev
[22:47] <Bert_2> so I shouldn't edit it inside schema-lazr.conf ?
[22:48] <wgrant> Probably not. The configs form an inheritance hierarchy, so you can just override the key in yours
[22:48] <Bert_2> so I would override from launchpad-lazr.conf in my custom configsdir ?
[22:48] <wgrant> Right
[22:49] <Bert_2> awesome, thx a ton :D
[22:49] <wgrant> np
[22:52] <sinzui> wallyworld: StevenK, wgrant: this is the one I was thinking of https://bugs.launchpad.net/launchpad/+bug/1004248
[22:52] <_mup_> Bug #1004248: hook to force page refresh on context url changing is not working <javascript> <regression> <ui> <Launchpad itself:In Progress by rharding> < https://launchpad.net/bugs/1004248 >
[23:10] <rick_h_> sinzui: something up with that?
[23:16] <sinzui> rick_h_: I was asking if a cache issue when a bug was marked a dupe related to that bug
[23:16] <sinzui> The conclusion was no
[23:16] <rick_h_> sinzui: ah ok cool. Wanted to make sure there wasn't anything up since I put that to ec2 today
[23:36] <Bert_2> wgrant: I just noticed that your bootstrap-db-from-scratch's bootstrap-lp-db script is missing the bug-watch-updater Celebrity, is that possible ?
[23:39] <Bert_2> (I have an oops page if you need more info)
[23:40] <wgrant> Bert_2: Yeah, if you look in the script where it creates the celebrities, you'll see comments instead of makeTeam/makePerson calls for some of them. I mainly just created the essential/interesting ones.
[23:40] <wgrant> You can alter the script or create the team manually to resolve it.
[23:40] <wgrant>     bazaar_experts = factory.makeTeam(
[23:40] <wgrant>         name='bazaar-experts', displayname='Bazaar Experts', owner=admins,
[23:40] <wgrant>         subscription_policy=TeamSubscriptionPolicy.RESTRICTED)
[23:40] <wgrant>     # bug_importer
[23:40] <wgrant>     # bug_watch_updater
[23:40] <wgrant>     buildd_admin = factory.makeTeam(
[23:40] <wgrant>         name='launchpad-buildd-admins',
[23:40] <wgrant>         displayname='Launchpad Builder Administrators', owner=admins,
[23:40] <wgrant>         subscription_policy=TeamSubscriptionPolicy.RESTRICTED)
[23:41] <wgrant> Some of the missing ones may be more essential now than they were when I wrote it.
[23:41] <wgrant> But the intention was that it'd get the web UI to work enough that you could create the rest if you needed them.
[23:42] <Bert_2> I see, so I'm missing the bug-watch-updater person then ?
[23:42] <Bert_2> it's apparently required to file a bug ;)
[23:43] <wgrant> Yeah. You can run the makePerson/makeTeam calls in bin/harness to fix that up
[23:44] <wgrant> In bin/harness, say eg. "factory.makePerson(name='bug-watch-updater', displayname='Bug Watch Updater', email='bugwatch@example.com')" then "transaction.commit()"
[23:44] <Bert_2> if you're interested: http://pastebin.com/yFzyDNCU it was on a call to bugs.[maindomain]/[project]/+filebug
[23:45] <wgrant> Ah right
[23:45] <wgrant> That is indeed a relatively recent change.
[23:45] <Bert_2> wgrant: why should I add it to bin/harness and not eg. make a utilities file for it and just execute that ? (just wondering)
[23:46] <wgrant> Well, you can update the script to do it too, but if it's a one-off it's usually easier to do it in bin/harness
[23:49] <wgrant> rick_h_: awk: cannot open build/js/yui-3.3.0/yui/yui.js (No such file or directory)
[23:49] <wgrant> rick_h_: Any idea on that build error?
[23:49] <wgrant> $ ls -l build/js/yui-3.3.0/
[23:49] <wgrant> total 0
[23:49] <wgrant> lrwxrwxrwx 1 wgrant wgrant 30 2012-07-25 09:49 yui-3.3.0 -> ../../../../build/js/yui-3.3.0
[23:50] <wgrant> It's a recursive symlink..
[23:51] <wgrant> rick_h_: Also, your yui buildout changes still use a predictable /tmp name
[23:52] <wgrant> StevenK: Can you build a fresh tree?
[23:52] <rick_h_> wgrant: yes, sorry. While we talked about it, webops didn't have feedback on that part and so only changed that which was required.
[23:52] <StevenK> wgrant: My devel build a few minutes ago worked
[23:52] <rick_h_> wgrant: I can make a follow up that will adjust that dir.
[23:52] <StevenK> wgrant: I can clean and then do a fresh make?
[23:52] <wgrant> StevenK: Try make clean_buildout build
[23:52] <rick_h_> we were tossing stuff at the wall at the time
[23:53] <wgrant> Heh
[23:53] <StevenK> rick_h_: May I suggest you not do that with our Makefile?
[23:53] <rick_h_> wgrant: added a card to move that dir in the morning
[23:53] <Bert_2> wgrant: so bin/harness is meant for one-off scripts ?
[23:53] <StevenK> wgrant: make clean_buildout build worked for me
[23:54] <wgrant> StevenK: Hmm
[23:54] <wgrant> Bert_2: It just gives you a Launchpaddy Python console
[23:54] <rick_h_> StevenK: heh, the sticking to the wall was guessing what issue my change had on qas not our makefile...and it's buildout.cfg now makefile :P
[23:54] <Bert_2> wgrant: I see
[23:54] <StevenK> rick_h_: Even worse, because buildout loves giving obtuse error messages.
[23:56] <rick_h_> StevenK: so think it's ok, will adjust the path to keep things inside of the build dir vs /tmp
[23:56] <Bert_2> wgrant: just so you know, same goes for bug-importer, apparently
[23:56] <wgrant> Yup
[23:58] <wgrant> StevenK, rick_h_: Hm, even 'make clean build' breaks
[23:58] <wgrant> Oh
[23:58] <wgrant> I don't have unzip installed
[23:58] <wgrant> It's nice that buildout doesn't actually notice or display the error
[23:59] <StevenK> [09:54] < StevenK> rick_h_: Even worse, because buildout loves giving obtuse error messages.
[23:59] <StevenK> wgrant: ^
[23:59] <wgrant> StevenK: It also loves not giving any error message at all, though
[23:59] <wgrant> Obtuse errors are fine :)
[23:59] <Bert_2> Does anyone know what the bugtask tasks and nominations table is ?