[05:20] <lamont> wgrant: sorta here, passing through on the way to bed
[05:24] <wgrant> lamont: I'd like your blessing for https://code.edge.launchpad.net/~wgrant/launchpad/multi-arch-builders
[05:24] <wgrant> lamont: master + slave changes to allow the master to tell the slave which arch to be. At the moment the switch is manual, though.
[05:24] <wgrant> When you have a moment to look at it, that would be great.
[05:26] <lamont> wgrant: when I dig through the backlog tomorrow, I'll add that to the things to look at this week
[05:26] <lamont> thanks muchly - this would be a good thing for all of us
[05:27]  * lamont sleeps
[05:27] <wgrant> lamont: Thanks. LP 10.08 freezes on Friday, so it would be nice to have your blessing before then, if it's feasible.
[05:28] <lamont> I'll see what I can do.. digging out from 7 workdays gone, and stuff to have done before I travel again on saturdya
[05:29] <lamont> but I WANT this, so we'll see what can be made to fit in the day
[06:49] <bilalakhtar> shadeslayer: Hi, join #omg!ubuntu!
[10:48] <igi> hello
[10:48] <igi> i have some problem lately posting bug, related to referrer headers
[10:48] <igi> can anyone support me?
[11:46] <bpeel> can I make a package in a PPA that depends on packages in other people's PPAs ?
[11:46] <bpeel> or maybe I can just copy their packages into my ppa ?
[11:48] <bigjools> bpeel: click on the "Edit PPA dependencies" link
[11:48] <bigjools> and on the next page you can add someone else's PPA
[11:48] <bpeel> bigjools: oh neat, thanks
[12:12] <lamont> wgrant: merge conflict with top of /devel atm, but otherwise looks reasonably sane, assuming it's been locally tested and all that
[12:17] <wgrant> lamont: True. Conflict resolved.
[12:17] <wgrant> Thanks.
[12:20] <lamont> this would help greatly for swapping ppa builders around
[12:20] <wgrant> Exactly.
[12:20] <lamont> though the next step is that list of valid architectures for the DB
[12:20] <wgrant> Yep.
[12:20] <lamont> before that, I'll need to go through the builders and note which ones can never do 64-bit in the descriptions'
[12:21] <wgrant> I was thinking you could just update the display names with the real archs, yeah.
[12:22] <wgrant> I'm not sure whether having a list of supported architectures is best, or whether we should be able to declare compatibility between processors.
[12:37] <lamont> it's possible, I suppose, that we would have at least one builder that was amd64-only, though I'm having some challenges picturing when we would want that
[12:42] <wgrant> lamont: Right.
[13:26] <philip_stoev> guys, do you particularily care about the size of the files being uploaded as attachments to bug reports?
[13:26] <philip_stoev> I mean, Launchpad accepts attachment sizes into the tens of megabytes, are you OK with people uploading such attachments routinely?
[13:39] <deryck> philip_stoev, we have to allow large file uploads because of some of the files apport uploads to bugs it reports.
[13:39] <deryck> we could perhaps restrict large uploads to apport, though.
[13:39] <deryck> philip_stoev, do you have a concern about this?  Or just wondering?
[13:49] <philip_stoev> deryck: I am doing QA for the Maria project, which is a MySQL clone. So, I may need to file say a maximum of a dozen or so bugs a month with 100Mb attachments each
[13:50] <philip_stoev> deryck: and I wanted to know in advance if it will be OK with you, so that it does not turn out that we will need to delete attachments after the fact
[14:00] <deryck> philip_stoev, shouldn't be a problem.
[14:01] <philip_stoev> deryck: thanks
[14:01] <deryck> np
[14:33] <keith2392> Anyone having trouble pushing change to Launchpad?
[14:36] <jelmer> keith2392: It's working fine here for me, although staging appears to be down.
[14:36] <jelmer> keith2392: We're looking into what's going on with staging.
[14:36] <keith2392> jelmer: What does staging affect?
[14:37] <keith2392> I was able to push to my development branch just now with a problem, but am unable to push changes to our main trunk
[14:37] <keith2392> also noticed that source-code viewing is not functioning on lp.net
[14:37] <jelmer> keith2392: It's a test environment that can be used for demos, etc. It does not affect what you would be doing if you're not explicitly connecting to staging.
[14:37] <keith2392> at least for our project,
[14:37] <keith2392> ah okay. That should not affect us then
[14:39] <jelmer> keith2392: Are you getting an error pushing to trunk, or a timeout?
[14:39] <keith2392> oh wait
[14:39] <keith2392> it is working again
[14:39] <keith2392> strange,
[14:40] <keith2392> What was happening,
[14:40] <keith2392> was that it would begin the push, get to 29/45K, and then stall there until I forced it to cancel
[14:40] <keith2392> even after waiting 5 minutes
[14:40] <keith2392> I would then have to do bzr break-lock.. trying again would have the same result
[14:40] <keith2392> Perhaps it was just a temporary server issue..
[15:28] <lamont> wgrant: there's a part of me that wants the slave to notice what architectures it's capable of, and report that to the master.  another part of me wants to punch the first part in the face, though
[16:41] <oubiwann> bac: ping (maybe you're at lunch now...)
[19:58] <lamont> wgrant: the uploader's habit of stopping the world for eternities angers me.
[22:01] <mxpxpod> I've been noticing that some PPA owners are uploading with ~10.04 instead of ~lucid... when did that change go into effect and why can't I find documentation on it?
[22:02] <micahg> mxpxpod: it's subjective
[22:03] <mxpxpod> micahg: I figured both work ;) I was confused for a bit, though
[22:35] <wgrant> lamont: I believe jelmer has a fix for that.
[22:35] <jelmer> I do.
[22:41] <lamont> that fix will make me most happy
[22:47] <jenkins> why are pages such as https://translations.edge.launchpad.net/ubuntu-manual/+settings change able by anyone? Also is it possible to get e-mails when they are changed?
[22:47] <jenkins> and who chnaged the settings
[22:48] <wgrant> jenkins: They're not changeable by anyone.
[22:48] <jenkins> wgrant: what is the requirement to change them, before I was a group admin i could do it
[22:50] <wgrant> jenkins: You need to be in the owning team or a Launchpad Translations admin.
[22:51] <jenkins> so i guess its only possible to make it more restrictive by restricting the team entry? it keeps getting changed and we don't know who by.
[22:52] <jenkins> 448 members in the team
[22:53] <wgrant> Why does such a huge team own a project?
[22:54] <jenkins> thats just the way it has worked out, we are a popular team.
[22:54] <wgrant> It may indicate that your structure needs a rethink.
[22:54] <jenkins> is it possible to change it so that all those people can contribute but have a smaller team that owns it?
[22:57] <wgrant> In general, yes. What privileges do they need?
[22:57] <wgrant> It's not completely flexible, but it's not too bad.
[22:58] <jenkins> to be able to translate and push to branches
[22:58] <wgrant> Branch access is completely unrelated to the project owner.
[22:59] <wgrant> Anybody can push a branch, and they can write to an existing branch if they're in the team that owns it.
[22:59] <jenkins> thats what i thought, would it be the maintainer field on here https://edge.launchpad.net/ubuntu-manual that changes?
[22:59] <wgrant> For Translations, have a look at https://help.launchpad.net/Translations/YourProject/PermissionPolicies
[23:00] <wgrant> Yes, I believe so.
[23:00] <wgrant> The owner has privileges to change project metadata, basically. If only a few people need to do that, only a few people should be the maintainer.
[23:00] <wgrant> Normal contributions do not require those privileges.
[23:01] <jenkins> right thanks very much wgrantI will have a look and suggest a change