[01:10] <poolie> Mel which package you
[01:10] <poolie> *are you trying to build?
[01:10] <lifeless> there is no mel
[01:15] <james_w> lifeless, are there any storm-query-based matchers that you know of?
[01:16] <lifeless> james_w: not offhand, sorry.
[01:16] <lifeless> there is some stuff that looks at the queries we capture
[01:16] <lifeless> and the capturing is fixture + matcher based
[01:16] <james_w> that's ok, just wanted to avoid writing them if they were already available
[01:16] <james_w> I'm thinking more just
[01:17] <james_w> "one row is returned for this query"
[01:17] <james_w> sort of thing
[01:18] <james_w> pretty easy to write as just an assertEqual(1, query().count()) sort of thing, but matchers could give better error messages
[01:18] <lifeless> oh we have shiny for that
[01:19] <lifeless> check out
[01:19] <lifeless> BrowsesWithQueryLimit and HasQueryCount in lp.testing.matchers
[01:19] <wgrant> lifeless: Different thing.
[01:19] <wgrant> Not a query count limit, but result count limit.
[01:20] <lifeless> oh
[01:20] <lifeless> <- leetle out of it
[01:21] <james_w> yeah, sorry, slightly confusing overlapping of terms there
[05:24] <marvin2> Hi, we have a project on launchpad called willow-code; it's maintained and driven by a team called willowit-team; another team called willowit-view-team has access to branches hosted on this project through visibility policy settings set by you guys.
[05:25] <marvin2> Is it possible to create a new team that has (read/write) access *only* to specific branches under the project willow-code?
[05:25] <marvin2> willow-code is a proprietary project and we're working on private branches here.
[05:26] <lifeless> yes, create that team and have someone in it that is also in the willowit-view-team push a branch to lp://~newteam/willow-code/branchname
[05:27] <lifeless> you will need to subscribe ~newteam to the trunk branch
[05:28] <marvin2> lifeless: So members of newteam will not be able to view code in other branches?
[05:28] <lifeless> right
[05:28] <marvin2> lifeless: Perfect. I'll try that out now. Thanks!
[05:28] <lifeless> just trunk and any branch pushed into their ~team directory
[05:29] <marvin2> Great!
[05:29] <lifeless> you can give them view to other branches one by one using subscriptions
[05:29] <marvin2> I think that covers all our usage scenarios. Thanks again, lifeless.
[05:30] <lifeless> no probs
[09:02] <micahg> wgrant: are you around?
[09:31] <bialix> hi, I have question about bug mails subscription. I've received a request from James who is co-worker of Mark Brown (registered on lp) and he's asked me about removing subscription of Mark to bug https://bugs.launchpad.net/qbzr/+bug/680529. James said he received all Mark mails because Mark no longer works in the company. What should I recommend to James?
[09:40] <maxb> bialix: This concerns the ~mark-mailsolve account?
[09:40] <bialix> maxb: yes
[09:42] <micahg> wow, we get instant bug e-mail notifications now?
[09:42] <maxb> bialix: Well, two options. You could either file a launchpad question for an admin to remove the subscription, or if he receives all of marks mails, he could claim ownership of the launchpad account and do it himself
[09:43] <bialix> maxb: right
[09:45] <bialix> maxb: thank you, I'll forward this recommendations to James.
[10:46] <zyga> hi, I'd like to understand how soyz build the archive? assuming you want to rebuild _everything_ where is the logic that determines the order of packages to build
[10:52] <maxb> zyga: As far as I know, nowhere, because it never does that/
[10:53] <zyga> so how does archive rebuild work?
[10:53] <zyga> is it a manual process of uploading new source packages in the right order?
[10:53] <zyga> carefully managed by humans?
[10:53] <maxb> Utilizing builddeps from the source archive, I would think
[10:54] <maxb> I can't see how it could possibly work otherwise, since you need a C compiler to build a C compiler
[10:55] <zyga> maxb, but it's still not a simple problem to solve
[10:55] <zyga> maxb, (well in some way it might but since packages have complex relationship I don't want to be so bold to proclaim it's easy)
[10:56] <zyga> maxb, packages have conflict and require relationships and version comparison
[10:56] <maxb> I'm assuming it just builds all the packages in an arbitrary order, satisfying dependencies that haven't been built yet from the primary archive
[10:57] <zyga> maxb, I'm not sure how to write an algorithm that for a certain set of source packages, determines the correct order of building them and the also produces a list of packages you need to start with to be able to complete the process (like the c compiler required to build the c compiler)
[11:05] <micahg> an archive rebuild is generally meant to see what happens when you rebuild what's currently in the archive with what's currently in the archive (nothing from the rebuild is used in the building)
[11:14] <bigjools> there are different types of rebuild
[11:15] <bigjools> the basic case is where we just literally rebuild certain packages and it uses the existing main archive for dependencies
[11:15] <bigjools> the next case is where we rebuild that again but using packages just built in the rebuild, so rebuilt dependencies are used
[11:16] <bigjools> beyond that it gets complicated (scorched-earth rebuilds)
[15:43] <barry> any code hosting/bzr experts online that could do a quick mumble with mvo and myself?
[18:10] <nothingspecial> I'm trying to change my email address for launchpad/ubuntuone. When I enter the conformation code it says unrecognised. Am I missing something obvious?
[19:26] <highvoltage> hi! I deleted a ppa a while ago, but (as is normal) it still shows up on my LP page. I'd like to use it again now, is there a way I could re-create it? I tried to create a PPA with the same name but LP doesn't allow that.
[19:31] <benji> highvoltage: I believe the way you get that done is to ask a question on LP and the sys admins do it for you: https://answers.launchpad.net/launchpad/
[19:35] <highvoltage> benji: ok, will do. thanks.
[19:49] <maxb> highvoltage: I'm afraid what you want is not currently possible
[19:50] <highvoltage> maxb: ah ok. no problem. thanks for letting me know.
[20:01] <benji> now I know too
[22:36] <popey> lifeless: or any other lp person.. is it a known bug that a rejected mail for a package may have someone elses name in the subject?
[22:36] <popey> http://paste.ubuntu.com/623770/
[22:36] <popey> X-Launchpad-PPA: trevormosey
[22:36] <popey> I am not him.
[22:37] <popey> I appreciate that I had a badly configured (i.e. no .dput.cf) dput on this clean install of ubuntu, but I still don't expect to see someone elses ID in my mail
[22:37] <popey> i have now fixed the config snafu and my package has been accepted, the accept mail is fine, only the reject has an issue http://paste.ubuntu.com/623771/
[22:38] <bigjools> popey: not seen that before, file a bug
[22:38] <popey> ok
[22:39] <lifeless> popey: did you dput to their PPA ?
[22:40] <popey> no
[22:40] <bigjools> check his paste
[22:40] <popey> i typed "dput ppa foo.changes"
[22:40] <popey> but had no dput.cf
[22:41] <lifeless> fnu
[22:41] <lifeless> fun
[22:41] <popey> ah, i wonder if it took the /etc/dput.cf
[22:41] <popey> incoming                = ~%(ppa)s/ubuntu
[22:41] <popey> so yeah, it did
[22:43] <popey> bug 795757
[22:43] <popey> and now bed.. nn and thanks!
[23:07] <micahg> popey: sounds like a duplicate, idr the bug # ATM though