=== slank is now known as slank_away [03:56] * StevenK stabs the error handling for spr.addFile() [03:56] bpr.addFile() just checks filename.endswith(), spr.addFile() matches against a regex. [04:05] Can I forbid buildout from downloading stuff that isn't in the local cache? [04:05] It should be already [04:06] Not for LP. [04:06] https://pastebin.canonical.com/81106/ [04:06] install-from-cache = true [04:06] Is set in buildout.cfg [04:06] So it should already refuse to go to the Internet [04:06] Oh [04:06] That's not LP [04:06] That's auditor, isn't it? [04:07] [15:06] < StevenK> Not for LP. [04:07] 15:05:50 < wgrant> It should be already [04:07] 15:06:01 < StevenK> Not for LP. [04:07] :) [04:07] And yeah, it's auditor [04:08] Am I mistaking or is bug #517302 a dup of bug #496056 [04:08] <_mup_> Bug #517302: "1 branch dependent on this one." doesn't link to that branch or a list of them

< https://launchpad.net/bugs/517302 > [04:08] <_mup_> Bug #496056: Dependent branch list is empty < https://launchpad.net/bugs/496056 > [04:09] Indeed [04:09] Done [04:10] wgrant: Then I'm confused, since Django is in our download-cache [04:10] :-) [04:10] Indeed, 1.3.3 and 1.4 [04:11] StevenK: Is the flag set in order? [04:11] In auditor? [04:11] That flag was not set [04:11] The order in buildout.cfg matters? :-/ [04:12] No, I just replaced 'auditor' with 'order' because I'm doing too many things at once :) [04:12] As long as it's in the right section it should be fine [04:12] AFAIK [04:12] wgrant: I've set it locally [04:14] Hm, it does indeed try and slurp Django from the net with that flag unset. [04:14] It gets 1.4 from the download-cache with it set, and 1.4.3 from the net with it unset. [04:15] * StevenK stabs buildout for being silly. [04:17] StevenK: You don't have it locked in versions.cfg? [04:18] No versions.cfg [04:18] Patches welcome? :-) [04:18] Ah, that would be your mistake [04:22] wgrant: So it should grow a versions.cfg too? [04:22] Probably, or someone'll throw a new Django into download-cache and you'll die [04:23] wgrant: So grabbing LP's versions.cfg and putting it on a large diet with head and grep would be fine? [04:23] Nope [04:24] Set allow-picked-versions = false [04:24] Add stuff to versions.cfg until buildout unbreaks [04:28] Hmm [04:28] Why do we have two versions of setuptools in the cache? [04:28] There's only one [04:28] Different Python versions [04:29] I have a 2.6 and a 2.7 for 0.6c11 [04:30] Yes [04:30] One version [04:30] Two Python versions [04:30] They're built eggs, not source tarballs [04:31] Oh [04:31] I see what's happened [04:31] My cache has been polluted [04:31] -rw-rw-r-- 1 steven steven 326K Jan 4 15:13 setuptools-0.6c12dev_r88846-py2.7.egg [04:31] The timestamp is a clue [04:32] Ah, yes [04:32] bzr st [04:32] Yeah, removed them [04:33] * StevenK cleans, since buildout is still attached to the dev release [04:33] Getting distribution for 'setuptools'. [04:33] Error: Picked: setuptools = 0.6c11 [04:33] But setuptools = 0.6c11 is in versions.cfg :-( [04:34] Do you have versions.cfg registered in buildout.cfg? [04:34] I do now [04:35] Does it also work now? [04:35] It moved onto zc.buildout, so yay progress? [04:36] :) [04:37] Generated interpreter '/home/steven/production-auditor/bin/py'. [04:37] Fantastic. [05:19] Just here to complain about the expiring notices from LP. [05:19] I wish I could fix it. [05:20] Patches welcome. [05:22] lifeless: that android bug made me spit my lunch I laughed so hard [05:31] bigjools: the giraffe thing? [05:31] yes [05:31] :D [05:31] Is it a bug/ [05:31] I even recreated it [05:32] well, I wonder [05:32] Feels more like a easter egg. [05:32] yeah [05:46] bigjools: its pretty awesome isn't it :) [05:48] ah it is a bug in TTS [06:20] StevenK: https://code.launchpad.net/~wgrant/launchpad/divorce-bfj-and-bfjo/+merge/141856 [06:22] 159"""See `IBuildFarmJobOld`.""" [06:23] Oh, you aren't disposing of BFJO yet? [06:23] 286 + # Classes deriving from PackageBuild must provide various [06:23] 287 + # methods. [06:23] Does that fit on one line? [06:23] Not quite [06:24] On both counts [06:24] BFJO still serves a purpose, and it won't be directly touched by this refactor [06:24] Which is why I want the interfaces to not be arbitrarily interrelated without having any actual overlap :/ [06:25] wgrant: Minor niggle, but you didn't update the copyright in lib/lp/security.py [06:25] Other than that, looks great to me. [06:25] Fixed [06:25] Thanks [06:27] wgrant: To be clear, BFJO is marked for death and will be completly ripped out at some point? [06:27] It's been marked for death for about 2.5 years, but it'll be easier after my current work [06:27] So it might die within the next few months [06:34] \o/ [09:01] good morning [09:28] good morning all. I was wondering if someone could help me: in preparation for the phone launch I created a private project to contain the code for the tutorials on developer.ubuntu.com. And then I managed to lock myself out of it, so I cannot access the project anymore. As it does not need to be private anymore after the announcement, could someone with admin superpowers set it as a public project for me? It's https://launchpad.net/ubuntu-app-dev-cook [09:28] book [09:29] https://launchpad.net/ubuntu-app-dev-cookbook === almaisan` is now known as al-maisan [09:29] dpm: You should be able to see it now [09:29] It's still private, but you can make it public [09:30] wgrant, great, thanks! The same happened to the associated team: https://code.launchpad.net/~ubuntu-app-dev-cooks - can I regain access to it so that I can make it public as well? [09:31] dpm: That team's public and you're the owner, a member, and an admin [09:31] So I'm not sure what the issue is there [09:31] Are you referring to some branches owned by that team, perhaps? [09:32] wgrant, not sure, either. Before you did the magic with the project, if I went to the team's main page I got a "not allowed here" page. But now I seem to access the team's page, so I guess it's all good [09:34] Ah, Person.getAffiliatedPillars doesn't do privacy filtering [09:34] So the "Related projects" was causing the 403 [09:35] aloha [09:36] Bug #1095982 [09:36] <_mup_> Bug #1095982: Person.getAffiliatedPillars doesn't filter out inaccessible private projects <403>

< https://launchpad.net/bugs/1095982 > [09:37] Morning czajkowski [09:37] wgrant, ok, I managed to set the project as public, but I cannot figure out how to make https://code.launchpad.net/~ubuntu-app-dev-cooks/ubuntu-app-dev-cookbook/trunk public. If I click on the "This branch contains Proprietary information" link, the only choice I get on the popup that appears is "Proprietary". Any suggestions on how I can make the branch public? [09:37] dpm: https://launchpad.net/ubuntu-app-dev-cookbook/+sharing [09:37] You probably want to set bugs, branches and blueprints to public [09:37] Then you can make the branch public [09:39] wgrant, excellent, thanks. I set everything to public now. Do the settings on the table under "Who it's shared with" look sensible for a public project? [09:40] dpm: I'd revoke your direct access, but the rest looks sensible (apart from the "{policy_name}" bit, which is a bug that'll be fixed on Monday) [09:41] wgrant, ok, I'll remove my direct access. Two more questions: [09:42] 1) I still cannot set the branch to Public: on https://code.launchpad.net/~ubuntu-app-dev-cooks/ubuntu-app-dev-cookbook/trunk if I change it, the change does not get applied [09:42] i.e. the spinning thing keeps spinning forever === al-maisan is now known as almaisan-away [09:43] Um, that's a bit odd. What if you click "Change details" and use the old non-AJAX form? [09:44] Oh [09:44] then I only get a Proprietary option [09:44] It's because it's stacked on another branch owned by you [09:44] https://code.launchpad.net/~dpm/ubuntu-app-dev-cookbook/trunk [09:44] I guess you probably want to unstack the team branch, and delete your old personal one? [09:44] actually, that was my second question. I'd like to delete that branch (https://code.launchpad.net/~dpm/ubuntu-app-dev-cookbook/trunk) [09:44] how do I unstack the branch? [09:45] bzr reconfigure --unstacked lp:ubuntu-app-dev-cookbook [09:45] Then wait a minute or so for it to work out it's done, and you'll be able to delete the old branch and make the new one public [09:45] cool, let me give it a go, thanks [09:48] That looks more sensible :) [09:54] wgrant, that worked well, thanks. I still get two warnings, though: 1) on https://launchpad.net/ubuntu-app-dev-cookbook/+sharing I removed all direct subscriptions (yours and mine) and LP it's telling me "These information types are not shared with anyone: Proprietary". Is this something that can safely ignore? And 2) on the project's front page at (https://launchpad.net/ubuntu-app-dev-cookbook) I get "(Launchpad 30-day trial commercial license)" liste [09:54] d as a license. I chose it when I made the project private, but I'm no longer using a commercial license. Is there a way to remove it? [09:55] dpm: The Proprietary warning should go away a day or so after there are no proprietary bugs or branches left, I think [09:56] As for the licence, just edit the project's licence settings to no longer include Other/Proprietary [09:56] The subscription will stay there until it expires, but nothing bad will happen when it does [09:57] (if the subscription expires and your project is Other/Proprietary, your project will be disabled) [09:58] yeah, "Other/Proprietary" was already unmarked, but from what you're saying, I should just wait for the subscription to expire [09:58] thanks wgrant! [09:59] I can probably make the subscription expire right now if you really want, but it'll just naturally expire soon enough [09:59] wgrant, no worries, that's fine if it expires naturally, no need to create extra work [10:01] Great === yofel_ is now known as yofel === BradCrittenden is now known as bac === almaisan-away is now known as al-maisan === gary_poster|away is now known as gary_poster === bac changed the topic of #launchpad-dev to: http://dev.launchpad.net/ | On-call reviewer: bac | Firefighting: - | Critical bugs: <150 [14:13] rick_h_: you about [14:14] czajkowski: yep [14:15] if you are free for a few mins can you pop into #lp please [14:15] czajkowski: sure sec === al-maisan is now known as almaisan-away === slank_away is now known as slank === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === almaisan-away is now known as al-maisan === al-maisan is now known as almaisan-away === deryck is now known as deryck[lunch] === deryck[lunch] is now known as deryck