[01:04] <thomi> Ordering bugs by age in the new bug UI seems really broken. I get 1 day old, 187 days old, 28 days old - in that order.
[01:16] <lifeless> thomi: it orders by task age, not bug age.
[01:16] <lifeless> yes, its confusing.
[01:16] <thomi> oh, ok.
[01:16] <lifeless> the squad doing it felt it was the least of several evils
[01:16]  * thomi needs to learn the difference between a task and a bug :)
[01:16] <thomi> fair enough :)
[08:57] <apw> https://launchpad.net/ubuntu/+source/pulseaudio
[08:58] <apw> ^^ do we have a problem with the per release links in the versions pages ?
[08:58] <apw> i assume we released something today
[08:59] <wgrant> apw: What's the problem?
[09:00] <apw> wgrant, ok i think it may be an old problem, as its possibly 'has an epoch' specific
[09:00] <apw> wgrant, try and click on the package versions next to the arrows >
[09:00] <wgrant> That's quite plausible, and it works fine for me.
[09:00] <wgrant> Which browser?
[09:00] <apw> this is chromium
[09:01]  * apw fires up firefox to compare
[09:01] <wgrant> Firefox here
[09:01] <apw> wgrant, ok so its ok in firefox, and ok on the linux package, but not pulseaudio which has an epoch ... /me pokes
[09:03] <wgrant> I remember a bug here.
[09:03] <wgrant> And it only affects some people.
[09:03] <wgrant> But I can't remember why.
[09:03]  * wgrant hunts.
[09:03] <wgrant> Bug #820174
[09:03] <wgrant> Hm
[09:03] <wgrant> But that's fixed.
[09:03] <apw> wgrant, yeah i think it must be a chromium bug as the source of the page looks all fine in its own 'view source'
[09:04]  * wgrant tries in Chromium
[09:04] <apw> wgrant, and its not the expander arrows, but the normal link on the name next to them thats the problem
[09:04] <wgrant> Oh
[09:04] <wgrant> What happens when you try them?
[09:04] <apw> they are invalid and nothing happens
[09:05] <wgrant> Ah
[09:05] <wgrant> Interesting
[09:05] <wgrant> Yeah, Chromium trims everything before the colon.
[09:05] <wgrant> How Windowsy of it.
[09:05] <apw> they are %31:1.1-0ubuntu14 stylee
[09:05] <apw>           <a href="1:1.1-0ubuntu14">
[09:06] <apw> but that is whats in the source
[09:06] <apw> hmmm, has to be a parser bug in chromium
[09:07] <wgrant> : is fine in URLs AFAICT
[09:07] <apw> wgrant, is it?
[09:07] <wgrant> As in in the RFC
[09:07] <apw> how is a browser supposed to know 1:foo is not protocol type 1 ?
[09:07] <wgrant> Ah, true.
[09:07] <apw> now it may be a protocol has to start with a letter or something
[09:08] <apw> and i be making it ./1: will fix it
[09:08] <wgrant> We can probably just quote the :
[09:09] <apw> wgrant, yeah that too
[09:09] <wgrant> apw: Care to file a bug?
[09:09] <apw> wgrant, aginst launchpad ?
[09:09] <wgrant> yeah
[09:09] <wgrant> bbs
[09:09] <apw> wgrant, no worries
[09:24] <apw> wgrant, https://bugs.launchpad.net/launchpad/+bug/973212
[11:12] <Phantomas> Is it possible to change the subscribing policy of a mailing list in Launchpad? I'd like everyone to be able to subscribe to our mailing list.
[11:14] <czajkowski> Phantomas: is it a LP mailing list?
[11:14] <czajkowski> Phantomas: people join a team on lp then join that's how it works.
[11:15] <Phantomas> czajkowski: If we talk about a project developers team, owning branches etc, I don't think it would be a good idea to allow everyone to become a member just to be able to subscribe to the mailing list
[11:16] <czajkowski> Phantomas: thats how lp lists work though.
[11:19] <Phantomas> alright, but I think this feature could become more flexible... The archives are public, so I think there is no reason to not allow subscriptions to everyone.
[11:20] <czajkowski> Phantomas: http://blog.launchpad.net/cool-new-stuff/contacting-teams-is-easier-and-more-reliable  that was done recently to help people
[11:21] <czajkowski> so they can contact the team
[11:22] <afiestas> hey there, I need to build a package from a different source repository and add the resulting package to our ppa
[11:23] <afiestas> I have been trying to figure out where to create a branch for it here: https://code.launchpad.net/~cyberspace (owned by cyberspace) but so far no luck
[11:23] <afiestas> I'm admin but not owner of the project, I can add members change details etc
[11:23] <afiestas> so I guess I should be able to add a branch right?
[11:25] <Phantomas> czajkowski: Yes, it's a nice feature, but it doesn't allow users to be informed on the development process and decisions made in the mailing list. They have to browse the archives.
[11:33] <lifeless> Phantomas: setup a second team
[11:33] <lifeless> Phantomas: one team for the list, one team for access controls.
[11:34] <Phantomas> lifeless: the team for the list would be a sub-team?
[15:30] <mpt> Come on Launchpad, all I want is a list of packages that have "policykit" in their names, it shouldn't be that strenuous...
[15:31] <czajkowski> mpt: are you breaking things ?
[15:31] <nigelb> mpt: Isn't it easier done with apt-cache search policykit?
[15:31] <mpt> czajkowski, https://launchpad.net/ubuntu/+search?text=policykit has timed out for me about six times in a row so far
[15:31] <mpt> nigelb, I didn't know that :-)
[15:31] <mpt> thanks
[15:31] <nigelb> :)
[15:32] <mpt> nigelb, except that they look like binary packages, whereas I was more interested in a source package I can report a bug on
[15:32] <mpt> (I know that it's not called plain "policykit", because that's a package that's been obsoleted by something else)
[15:33] <nigelb> ah
[15:33] <nigelb> mpt: alternative place to search is packages.ubuntu.com
[15:33] <czajkowski> I suspect there are either a lotta bugs with that tag or duplicates/people assinged to them and it's causing it to fail :/
[15:33] <mpt> https://launchpad.net/ubuntu/+source/policykit-1 << winner
[15:34] <nigelb> ha!
[15:34] <nigelb> did you get it off LP?
[15:34] <mpt> czajkowski, it doesn't involve Bugs at all afaict, purely package search
[15:34] <mpt> nigelb, no, by guessing from all the "-1"s in the apt-cache results
[15:34] <nigelb> aha! :)
[15:35] <nigelb> So, packages.u.c nails it straight away.
[17:02] <dobey> mpt: does ubuntu-bug not tab complete installed package names? :)
[17:04] <mpt> dobey, the textual detritus ubuntu-bug attaches to a bug report is seldom relevant to the kind of bugs I report, so I don't often use it
[17:06] <dobey> mpt: ah. apt-cache show tab completes through available binary packages, and you can |grep ^Source it to get the source package name, as well. and if there's no "Source" the source package name should be the same as the binary package name
[17:07] <mpt> ah
[17:07] <mpt> I don't use "^" in patterns often enough to remember that it's "^" and not something else
[17:07] <mpt> but thanks dobey :-)
[17:13] <dobey> heh, sure :)
[17:14] <rick_h> 761142
[17:39] <mgz> czajkowski: if you're not EOD yet,

[17:40] <mgz> favourite kind of ssh setup problem.
[18:26] <lifeless> Phantomas: if you want it to be, sure.
[19:09] <JanC> are there any rules/guidelines about how often the LP API can be queried?
[19:30] <dobey> JanC: "don't abuse it"
[19:34] <JanC> dobey: if you list info from LP with a "live" query on another site, others can do the "abuse"
[19:34] <JanC> either intentionally or not
[19:36] <JanC> "unintentionally" would be lots of visitors on the page that does the live query
[19:37] <dobey> JanC: you should do caching so that you only make a request to launchpad.net every N seconds or so, if that's the case
[19:38] <dobey> there's no point doing the same query 3000 times in the same second, for example
[19:38] <dobey> and several seconds of delay isn't a huge penalty when looking at the other site
[19:38] <JanC> right, that's what I thought, and I personally think 1 query / second is overkill already  ;)
[19:39] <JanC> dobey: so there are no general rules about this?
[19:39] <JanC> or hard limits ?
[19:39] <dobey> i have a site doing some queries to google docs, and cache it with a 90s timeout, but it's a low traffic site
[19:40] <dobey> JanC: i suspect it's "if you abuse it, you or your site will get blocked pretty quickly"
[19:41] <dobey> hopefully you're only doing anonymous api calls if it's from another site
[19:41] <JanC> most web APIs I know have hard rate-limits, that's also why I was asking (and I am gathering arguments to provide to somebody else who is making that site ;) )
[19:41] <dobey> i don't think there's any way to use the API with a token that isn't associated with a user
[19:42] <dobey> JanC: indeed, but a lot are also just "don't be stupid"
[19:42] <JanC> they are querying for team members
[19:42] <JanC> of about 10 (sub)teams
[19:42] <dobey> the google+ api is nice, as you can pass on the user's IP through, so that the limit is based on each IP, rather than your api token
[19:43] <JanC> dobey: so how does Google know those IPs are for real?  ;)
[19:43]  * JanC thinks they have some other monitoring going on too
[19:44] <dobey> because writing something that abused that would be a total waste of effort, really
[19:44] <dobey> so they probably don't really care
[19:44] <dobey> and there's no real reason to abuse it
[19:45] <dobey> anyway, cache it
[19:45] <dobey> team memberships don't change often enough not to
[19:47] <JanC> dobey: yeah, my argument too; even a 1h delay isn't really important for that IMO
[19:49] <dobey> indeed
[20:10] <astraljava> Apologies if this is a hot topic right now, but are there problems with LP right now? It seems roughly 10%, very recently even less, of my requests are being served. Times out almost all the time.
[20:12] <dobey> i haven't had any issues with it really, no
[20:13] <astraljava> So it's some sort of a routing issue, then. Thanks.
[20:13] <dobey> well, it could be something with launchpad
[20:14] <dobey> are you getting timeouts on launchpad itself (with an OOPS id printed out), or timeouts connecting to it?
[20:14] <astraljava> dobey: Connecting, and looks like a dns issue. $ tracepath https://launchpad.net
[20:14] <astraljava> gethostbyname2: Unknown host
[20:14] <astraljava> Sorry for the noise.
[20:15] <astraljava> err... no, apparently I just don't know how to use that. :)
[20:16] <astraljava> tracepath launchpad.net let's me up to hop 22: eth0.chenet.canonical.com
[20:18] <astraljava> ...and now it serves again. Again, sorry for the noise. I get me coat.