[02:03] <Cas07> im a bit confused about the translations section, it says that its open yet when i got to an individual item i cannot edit it. am i missing something?
[02:05] <wgrant> Cas07: Do you have "Not make translations in Launchpad" selected at https://translations.launchpad.net/people/+me/+licensing?
[02:05] <Cas07> https://translations.launchpad.net/deluge/trunk/+pots/deluge/es/+translate
[02:05] <Cas07> its the first item
[02:06] <Cas07> ooooh i see
[02:07] <Cas07> well aint that confusing
[02:07] <Cas07> wgrant: thanks :)
[02:07] <wgrant> Bug #604230
[02:08] <Cas07> is spam in the translations common?
[02:09] <wgrant> I haven't seen that much myself.
[02:09] <wgrant> But bad translations are all too common.
[02:15] <marvin2> Hi, we have a private project hosted on launchpad, with a specific team given access to the code.
[02:15] <marvin2> Nobody else can view/upload code to that project.
[02:16] <marvin2> Now, would it be possible to create a new user with just read-only access to code (bazaar) in that project?
[02:18] <marvin2> Anyone?
[02:22] <wgrant> marvin2: A particular branch, or all branches?
[02:33] <marvin2> wgrant: Didn't know we could restrict access to specific branches!
[02:34] <marvin2> wgrant: That'd be great. For now though, we'd like to give a specific user read-only access to all the branches in that project.
[02:36] <wgrant> marvin2: Giving access to particular branches is much easier (just create a user and subscribe it to the branch). All is harder, as they have to be in the team that is automatically subscribed. Do you currently have a single team that owns the branches and is subscribed?
[02:40] <marvin2> wgrant: I'll just create a new team to which you could give read-only access to the whole project.
[02:41] <marvin2> wgrant: Is that OK?
[02:41] <marvin2> wgrant: You gave a team read-write access the other day.
[02:42] <wgrant> marvin2: Yeah, that sounds like a good plan. Create a new team, add the existing team and the new user to that, then we can change the config to subscribe the new team instead.
[02:43] <marvin2> wgrant: I'd rather leave the existing team (with rw access) alone, and give this new team read-only access.
[02:43] <wgrant> marvin2: Write access is controlled by the branch owner, which is separate from the readability policy.
[02:44] <wgrant> marvin2: The owner is set by the URL (lp:~owner/project/branch)
[02:48] <marvin2> wgrant: Ah, I think I get it. Sorry for being so slow.
[02:50] <marvin2> So I'll just create a new team "Willow RO Team" and let you know
[03:27] <marvin2> wgrant: I've created a team called willowit-view-team. Could you please grant that team access to the project willow-code?
[03:28] <marvin2> I believe that would grant members of willowit-view-team read-only access to branches in willow-code owned by willowit-team.
[03:29] <marvin2> Please let me know if I understand this correctly.
[03:29] <wgrant> Let me change that.
[03:29] <wgrant> You may have to manually subscribe the team to existing branches, but it will affect all new branches.
[03:30] <marvin2> willowit-team will still have access to willow-code, won't it?
[03:30] <wgrant> It's easiest if we have just one team that has access to all of the branches. I'd advise adding willowit-team to willowit-view-team.
[03:33] <marvin2> So willowit-view-team has access to all of the branches. willowit-team will be part of willowit-view-team, thus having access to all branches. willowit-team will own the actual branches, thus having read-write access to the code.
[03:33] <marvin2> Am I correct?
[03:34] <wgrant> That's right. Owner provides read-write access, the visibility policy provides read-only access, and it's far easier for everyone if there's only a single team in the visibility policy.
[03:41] <marvin2> wgrant: Great. As long as I understand how the model works!
[03:47] <marvin2> wgrant: I don't see "Willow Code" on willowit-view-team's page.
[03:48] <wgrant> marvin2: It's shown on ~willowit-team because that team owns the project.
[03:48] <wgrant> willowit-view-team has no relationship to the project.
[03:51] <marvin2> So what next - I add willowit-team to willowit-view-team?
[03:51] <wgrant> Yup.
[03:52] <marvin2> ...and how do I ensure any member of willowit-view-team (who's not in willowit-team) gets to read any code in willow-code?
[03:52] <wgrant> I'll change the visibility policy to permit that.
[03:53] <wgrant> Once you've added willowit-team.
[03:53] <marvin2> Great.
[03:53] <marvin2> wgrant: Done
[03:57] <wgrant> marvin2: That should be set up for new branches now. You may need to manually susbcribe willowit-view-team to existing branches.
[03:59] <marvin2> wgrant: OK. Please let me check.
[04:20] <marvin2> wgrant: So who's the owner of willow-code now - willowit-team or willowit-view-team?
[04:29] <wgrant> marvin2: willowit-team. The owner is a separate thing from the visibility policy.
[04:30] <wgrant> You can change the owner if you want to.
[04:31] <marvin2> wgrant: So the visibility policy of "willow-code" explicitly allows both willowit-view-team and willowit-team access?
[04:32] <marvin2> Sorry for being pedantic.
[04:32] <wgrant> marvin2: Only willowit-view-team, but that includes willowit-team.
[04:32] <marvin2> Great, thanks.
[07:52] <geser> wgrant: Hi, do you have some time to fix the ownership of some package sets? the ones affected by bug 740892 (see also http://irclogs.ubuntu.com/2011/03/23/%23ubuntu-motu.html#t11:02)
[07:55] <wgrant> geser: Argh, yes, need to poke a LOSA about that.
[07:55] <wgrant> (the bug is fixed, though)
[08:17] <geser> wgrant: it's not urgent but how long does this usually take?
[08:18] <geser> wgrant: I've some packages to add to the zope package set and would like to know if I should wait on the fix of the ownership or mail the TB to add them
[08:19] <lifeless> geser: try and grab mthaddon in ~ 2 hours
[09:49] <fagan> Hey, whats going on with bug expiry at the moment I just marked a bug as incomplete and its not showing that its going to expire in 30 days
[09:49] <lifeless> its a per project setting
[09:49] <fagan> it should be on (it was working last week)
[09:49] <lifeless> whats the bug
[09:50] <fagan> lifeless: Bug #603132
[09:50] <fagan> its a really old one im cleaning the old bugs
[09:50] <lifeless> it has an assignee
[09:51] <fagan> oh so if it has an assignee it wont expire now last week it wasnt doing that im pretty sure
[09:51] <fagan> (or the week before)
[09:51] <lifeless> its been like that forever
[09:51] <wgrant> Indeed, that has been the case since the day expiry was introduced 3ish years ago.
[09:51] <lifeless> the docs are worth a read if you need a refresher.
[09:51] <lifeless> expiry could do with a facelift
[09:52] <lifeless> but it hasn't been changed yet :)
[09:52] <fagan> lifeless: I was sure my bugs were expiring before when I assigned them to myself
[09:52] <fagan> thats why I was puzzled
[09:52] <fagan> weird anyway thanks
[11:56] <fagan> hey again im trying to view the archives of a private list and its doig a openid loop
[11:56] <fagan> im a member and a mod so it shouldnt be a problem viewing it but its not letting me see
[11:57] <fagan> hmmmm its saying my url hasnt been granted access
[11:57] <fagan> :/
[11:57] <wgrant> fagan: Yeah, private list archives are not working at the moment.
[11:57] <fagan> wgrant: ahh ok
[11:58] <fagan> I was wondering
[12:05] <fagan> wow im having all sorts of fun today I just had a post comment button not work on a bug it fixed on refresh though
[12:06] <fagan> id say it was because I pasted something in and something didnt catch on that there was text in the box
[16:20] <microcai> hello, any one there ? Strange thing happend !
[16:20] <microcai> I've upload an package to ppa, dput say  upload success, but it doesn't appear on the list
[16:22] <jcsackett> microcai: did you sign the package with the gpg key you have on launchpad?
[16:22] <jcsackett> microcai: https://answers.edge.launchpad.net/launchpad/+faq/227
[16:24] <microcai> jcsackett:  yes
[16:25] <jcsackett> how long ago did you upload?
[16:27] <microcai> jcsackett:   3+ hours
[16:31] <jcsackett> microcai: does your changes file specify all of the headers? (e.g. "Files")
[16:32] <microcai> jcsackett:  no.  try to fix that. back later. tks
[16:32] <jcsackett> microcai: you're welcome. :-)
[17:48] <geser> mthaddon: Hi, do you have some time to fix some package set ownership in the database for me? The bug causing this is fixed but the data still needs fixing
[17:48] <microcai> jcsackett:  accepted
[17:48] <mthaddon> geser: I think you probably mean to "ping losa" rather than asking for me particularly
[17:49] <jcsackett> microcai: great. :-)
[17:50] <geser> mthaddon: lifeless mentioned your name earlier today when I asked about it
[17:52] <mthaddon> geser: I'm about to EOD, but if you ping losa someone should be able to help you (or point you in the right direction)
[17:54] <geser> mthaddon: ok, how do I "ping losa"? (never had to do it before)
[17:55] <jcsackett> geser: if you can file a question about it on answers.launchpad.net/launchpad, i can run down admins for you.
[17:55] <mthaddon> geser: just type that in channel, but jcsackett is also here to help and can see your request through as above
[18:05] <geser> jcsackett: https://answers.launchpad.net/launchpad/+question/154334 Do you need any additional data?
[18:08] <jcsackett> geser: that looks like enough to me. i'll assign to losas and let them know it's there. if they need more data they can comment on the question.
[18:08] <jcsackett> thanks. :-)
[18:22] <bulldog98> hi I get the No REFERER Header error. How can I fix this?
[18:28] <MTecknology> https://code.launchpad.net/~nginx/+recipe/nginx-nightly .. this thing hates me.. seems to break during build and I don't understand why... https://launchpadlibrarian.net/70458396/buildlog_ubuntu-natty-amd64.nginx_1.0.0-svn3185-ppa199~natty1_FAILEDTOBUILD.txt.gz
[18:29] <MTecknology> oooh
[18:30] <MTecknology> I need to merge in a few files.....
[18:30] <MTecknology> Is it possible to merge only a few files?
[18:31] <MTecknology> ah.. maybe nest-part will let me operate on files...
[18:57] <MTecknology> k... a little further... my recipe now is http://dpaste.com/535971/  I'm hitting this now... https://launchpadlibrarian.net/70460437/buildlog.txt.gz
[18:57] <MTecknology> nest-part configure lp:nginx auto/configure configure <-- I assume this is where it's breaking, but not sure what's wrong.. I'm trying to copy auto/configure to configure ..
[19:04] <MTecknology> GAH! Not being able to use basic shell commands in recipes is a bit of a bitch
[19:09] <MTecknology> helpful..... bzr: ERROR: The file id "configure-20110426180836-j91tkyjxnusqpk2m-1" is not present in the tree <bzrlib.inventory.CHKInventory object at 0x388d850>.
[19:15] <MTecknology> hm........ can nest-part not handle single files?
[21:27] <jaypipes> lifeless: around?
[21:30] <lifeless> jaypipes: sure
[21:31] <lifeless> MTecknology: that error probably wants a bug report
[21:32] <MTecknology> lifeless: :(
[21:41] <lifeless> jaypipes: done
[21:42] <jaypipes> lifeless: u rock man. cheers.
[21:42] <jaypipes> lifeless: and duly noted for the future :)
[21:44] <lifeless> jaypipes: no worries, happy to help
[21:58] <ChrisWoollard> Evening all. Do any of you know how i can export a list of contributors from launchpad? Specifically the Rosetta translation component.
[22:01] <lifeless> I thought we included that in the pot export
[22:03] <ChrisWoollard> do you
[22:03] <ChrisWoollard> i'll check
[22:09] <ChrisWoollard> It appears to be in the .po files
[22:17] <ChrisWoollard> hmmm. Actually it only contains the last translator
[22:18] <lifeless> for a given string?
[22:18] <ChrisWoollard> no, in the whole po file. So only one reference
[22:22] <lifeless> thmm
[22:24] <lifeless> I'm not sure, perhaps open a question at https://answers.launchpad.net/launchpad
[22:25] <ChrisWoollard> What a good idea. Thanks