[00:01] <jml> I can't see a way to contact them.
[00:10] <jml> yeager: out of curiosity, why do you want to contact them?
[00:13] <yeager> jml: he's translations are terrible bad and I need to give him some directions
[00:14] <jml> yeager: thanks. just in the process of filing a bug
[00:15] <yeager> thanks
[00:26] <ubotu> New bug: #179764 in launchpad "Some people are unable to be contacted" [Undecided,New] https://launchpad.net/bugs/179764
[02:11] <ScottAS> Hello All. I'm having a problem importing my OpenPGP key within my profile. I've uploaded my OpenPGP Key to KeyServer.Ubuntu.Com and it's listed as being present after having queried it but on entering my Fingerprint, I receive a message that my OpenPGP key couldn't be imported.
=== bigon is now known as bigon`
[07:02] <Fujitsu> \/win 12
[07:02] <Fujitsu> Oops.
=== fabbione is now known as thegodfather
[08:06] <carlos> morning!!
[08:19]  * Fujitsu watches the Canonical world slowly reawaken.
[08:28] <mwhudson> :)
[08:29] <jml> some of us have been awake all day already :)
=== gryc_ is now known as gryc
[08:59] <mpt> Gooooooooooooooooooooood morning Launchpadders!
[08:59] <mrevell> morning mpt and happy new year!
=== mrevell changed the topic of #launchpad to: Next developer meeting: Thu 10 Jan 2008, 1400UTC #launchpad-meeting | Help: https://help.launchpad.net | Channel logs: http://irclogs.ubuntu.com
[09:06] <mpt> mrevell, likewise :-)
[09:11] <Fujitsu> What an oddly short topic.
[09:20] <mpt> Yes, it's been refactored
[09:21] <Fujitsu> I'd be of the opinion that developer information shouldn't be in the topic, but that would make it *absurdly* short.
[09:23] <mrevell> Fujitsu: The next meeting announcement isn't really for the developers, though. it's so that everyone else knows where it is. HAppy new year, btw :)
[09:23] <Fujitsu> mrevell: Aha. Happy new year!
[09:23] <mrevell> Fujitsu: Perhaps calling it "developer meeting" makes it sound too exclusive.
[09:24] <Fujitsu> Considering most other aspects of LP development are completely closed...
=== mpt changed the topic of #launchpad to: Next development meeting (all welcome): Thu 10 Jan 2008, 1400UTC #launchpad-meeting | Help: https://help.launchpad.net | Channel logs: http://irclogs.ubuntu.com
[09:26] <mrevell> nice one mpt :)
[09:31] <Fujitsu> mpt: Thankyou. I have previously been unsure as to whether we're meant to avoid the channel during those meetings, and have often been mystified as to why they're not on irc.c.c.
[09:35] <mrevell> Fujitsu: We welcome anyone who wants to attend. We're trying it out in #launchpad-meeting, though, so that people can still ask for help in #launchpad without feeling they're getting in the way.
[09:45] <ubotu> New bug: #179816 in malone ""Unknown" importance should be unsettable if project uses Launchpad for bugtracking" [Undecided,New] https://launchpad.net/bugs/179816
[10:01] <ubotu> New bug: #179820 in malone "Default "Undecided" importance is below all the others, and that's odd" [Undecided,New] https://launchpad.net/bugs/179820
=== stu1 is now known as stub
[10:46] <mpt> whoo, bug feeds, nifty
[11:10] <Kmos> cprov: hi! next version of ppa will have an option to remove some package?
[11:11] <cprov> Kmos: probably, we are filtering 1.2.1 tasks right now.
[11:11] <Kmos> cprov: nice.. thanks =) good work
[11:12] <cprov> Kmos: you are welcome.
[11:23] <Kmos> cprov: bug 173866
[11:23] <ubotu> Launchpad bug 173866 in soyuz "When specific arch is not available at PPA, it should reject" [Undecided,New] https://launchpad.net/bugs/173866
[11:23] <Kmos> check this one when you got some time =)
=== silwo1 is now known as silwol
[11:31] <ubotu> New bug: #179835 in launchpad "All staging.ubuntu.com URLs return Launchpad "Page not found" errors" [Undecided,New] https://launchpad.net/bugs/179835
[11:31] <Fujitsu> mpt: What is staging.ubuntu.com's purpose? I didn't know it existed.
[11:32] <elmo> err
[11:32] <elmo> staging.ubuntu.com shouldn't even be in DNS
[11:33] <mpt> elmo, removing it would be one way of fixing the bug :-) ... but I came across it when reading a presentation about Soyuz
[11:33] <Fujitsu> Aha.
[11:38] <elmo> mpt: done
[11:42] <mpt> thanks
[11:54] <Hobbsee> Fujitsu: ping
[11:55] <Fujitsu> Hobbsee: Pong.
[11:55] <Hobbsee> Fujitsu: delayed again :(
[12:09]  * Hobbsee gives back gcc, and hopes that it builds.
=== mrevell is now known as mrevell-lunch
[12:32] <Hobbsee> cprov: you might want to actually fix the buildds.
[12:32] <Hobbsee> ppc all looks broken.  hppa, etc, probably are too
[12:33] <cprov> Hobbsee: check this with elmo or lamont, please.
[12:33] <Hobbsee> elmo: lamont it's broken again.  same as the original arches over christmas.
[12:34] <cprov> Hobbsee: is that the chroot issue we've got on i386/amd64 during xmas ?
[12:34] <Hobbsee> cprov: yes
[12:34] <cprov> Hobbsee: right, hppa/ppc/ia64 are missing the /fix/.
[12:35] <Hobbsee> cprov: wouldn't surprise me.  why so, and what was the final fix?
=== ``Cub1 is now known as ``Cube
[12:35] <cprov> Hobbsee: I don't know exactly, elmo did it.
[12:36] <elmo> Hobbsee: I did the arches the vast majority of people use, because I was short on time
[12:36] <elmo> Hobbsee: infinity will be fixing the rest later today when he gets up
[12:36] <Hobbsee> elmo: oh, i can understand that.  
[12:36] <Hobbsee> elmo: ah, cool :)
[12:36] <Hobbsee> elmo: was expecting the others to go on the todo list for when you got back
[12:37] <elmo> Hobbsee: the fix was simply upgrading the chroot (by installing libc6 tzdata first, then dist-upgrade)
[12:37] <Hobbsee> elmo: ah right, so it was what was thought.
[12:37]  * Fujitsu is glad that fix worked.
[12:37] <elmo> Fujitsu: yeah, thanks for your help, btw
[12:37] <Fujitsu> It looks like a very strange apt bug.
[12:37] <elmo> (I left a note in the RT ticket for Adam to talk to mvo about the apt behaviour)
[12:38] <Fujitsu> Aha, thanks.
=== ``Cub1 is now known as ``Cube
=== mrevell-lunch is now known as mrevell
[13:14] <markvandenborre> hi all, just wanted to say "keep up the good work on launchpad"
[13:14] <markvandenborre> I just noticed an option that's probably there since quite a while: user renewed team subscription, and it rocks
[13:15] <markvandenborre> a simple, but very effective way of helping our local volunteer group get organised
[13:15] <markvandenborre> thanks for that!
[13:16] <markvandenborre> and no, it's not because I need any fancy feature from you that I say this, just happy
[13:16] <markvandenborre> all the best in 2008!
[13:19] <Hobbsee> mpt: what was the rationale in killing off the separate rosetta list?
[13:20] <Fujitsu> To move all of the spam onto launchpad-users, or because it was only separate initially because it was the first component of LP to be public. One of them.
[13:20] <Hobbsee> Fujitsu: since when was rosetta public?
[13:20] <Hobbsee> as in, open?
[13:21] <Fujitsu> The first to be publicly visible/usable.
[13:21] <Hobbsee> ah right
[13:21] <mpt> Hobbsee, I don't remember, but it was explained at the time so it should be nearly the last message in the archives
[13:21]  * Hobbsee wonders if LP stuff can be tagged as translations or otherwise.
[13:22] <mpt> Hobbsee, depends what you mean by "stuff"
[13:22] <Hobbsee> putting in a global filter to ditch anything that says "translation" seems a little harsh.
[13:22] <mpt> We still use a separate "rosetta" project for categorizing Translations bugs, blueprints, etc
[13:22] <Hobbsee> mpt: the mail.
[13:22] <Hobbsee> mpt: the mail on lp-users
[13:22] <mpt> ah
[13:22]  * Hobbsee is bored of hearing abotu a section that she never uses, oddly enough.
[13:23] <mpt> Can you train your junk mail filter to recognize messages that are about translations?
[13:23] <Hobbsee> as, i suspect, are those who don't package, seeing all the constant mail about the ppas, including the mails where the OP clearly didn't read the previous mail a few days prior, which answers their question.
[13:23]  * Hobbsee can probably set something up that will check for the word "translation" and LP users
[13:23] <mpt> Should be fairly easy with the number of unusual terms (translations, po, pot, plural, mo)
[13:24] <Hobbsee> but that will knockout the generic "lp has grown these new features" mails for each release
[13:25] <ubotu> New bug: #179853 in launchpad "Purpose of "Renew their membership automatically" is unclear" [Undecided,New] https://launchpad.net/bugs/179853
[13:25] <Hobbsee> Having two separate lists splits discussion and may be confusing, 
[13:25] <Hobbsee> particularly as we no longer use the Rosetta name.
[13:25] <Hobbsee> meh.
[13:25] <Hobbsee> translations here.  non-translations there.
[13:27] <Hobbsee> i don't see why it wasn't renamed to the translations list, or something
[13:27] <Hobbsee> same thing for ppa, when it gets sufficient mail
[13:29] <Fujitsu> I see the user demographic for Rosetta as being very different from the rest of LP - the users are largely non-technical.
[13:29] <Hobbsee> true
[13:29] <Hobbsee> those using rosetta are quite unlikely to use anything else
[13:29] <Fujitsu> The other applications have users who might actually know what they're doing, how to write an email, how not to use a miling list.
[13:29] <Hobbsee> those using bugs are likely to be using specs, for eg, or ppa
[13:29] <Hobbsee> yeah, true
[13:45] <ubotu> New bug: #179857 in malone "Package sponsorships involve awkward bugtracker machinations" [Undecided,New] https://launchpad.net/bugs/179857
[14:02]  * lamont wanders through on his way to the office
=== cprov is now known as cprov-lunch
[14:35] <ubotu> New bug: #179868 in launchpad "apt:package-name URLs aren't auto-linkified" [Undecided,New] https://launchpad.net/bugs/179868
=== Ubulette_ is now known as Ubulette
[14:40] <ubotu> New bug: #179872 in launchpad "Translations tab inactive for individual projects inside Ubuntu" [Undecided,New] https://launchpad.net/bugs/179872
[14:43] <mpt> duplicate
[15:05] <ubotu> New bug: #179873 in soyuz "Can't report bugs on PPA packages" [Undecided,New] https://launchpad.net/bugs/179873
[15:07] <Hobbsee> mpt: personally, i'd like tos ee effective ways of stopping DOS's from people who upload broken pacakges, or lots of them whcih take ages to build, before being able to file bugs on packages.  but thatnks!
[15:07] <Hobbsee> mrevell: ping
[15:07] <mrevell> Happy new year Hobbsee!
[15:07] <Hobbsee> mrevell: somewhere in the documentation, you might want to point out that the buildds have no internet access during build, so downloading modules from cpan, etc, is inappropriate
[15:07] <Hobbsee> mrevell: happy new year to you too!
[15:07] <Hobbsee> mrevell: welcome to another year of ppa support!
[15:08] <mrevell> Hobbsee: Thanks for that.
[15:25] <mpt> Hobbsee, is the DOSing problem reported?
[15:25] <Hobbsee> mpt: the lack of cancelling builds.  yes.  the lack of build queue.  yes.  all deferred indefinetly.
[15:25] <Hobbsee> mpt: the documentation doesn't explicitly say "don't require internet connection during build" yet though.
[15:26] <Hobbsee> mpt: and you don't yet do automatic smashing over the head for violating that.
[15:27] <Hobbsee> mpt: you also don't appear to have your rt info handy at all.  the site, username and password don't seem to be in any clear location.  then again, you probably don't want random users bugging rt.
[15:28] <Hobbsee> mpt: if someone uploads a whole bunch of packages that take ages to build, or upload ones that require the internet, you've just managed to DOS the buildds that take them, sometimes for days.
[15:29] <Hobbsee> mpt: it's not judged important enough to fix soon, it appears.
=== \sh_away is now known as \sh
[15:30] <Hobbsee> mpt: i would assume that's because it only broadens the group who can fix broken buildds (at least, without needing to do stuff with the chroots themselves) to ~buildd-admins, rather than just the 2 people from rt.
[15:30] <Hobbsee> (and because that's not hundreds of people or something, doesn't get done)
[15:32] <elmo> Hobbsee: hang on it's not about requiring internet
[15:32] <elmo> Hobbsee: it's the fact that it went into a tight loop doing so
[15:33] <Hobbsee> elmo: granted.
[15:33] <elmo> Hobbsee: that kind of failure mode is hard to catch, always has been, always will.  dak buildd didn't cope well with that either
[15:33] <elmo> Hobbsee: also, it happened at a particularly bad time of year where Canoncial as a whole is shut down, but that's not the case 99.9% of the year
[15:33] <Hobbsee> elmo: true, hence i would have thought there should be a piece of documentation that says "please don't try this.  it makes $deity cry", and a way of cancelling any build that has had that, preferably with slugging the user in the head.
[15:34] <Hobbsee> elmo: also granted.  i'm not whining about how it took a few days - i'm  just pointing out the worst case there.
[15:34] <Hobbsee> elmo: and, as per murphy, this stuff is *always* going to happen around bad times (weekends, public holidays, etc)
[15:36] <elmo> Hobbsee: sure
[15:36] <Hobbsee> elmo: actually, i'm surprised that no one has appeared to try to upload stuff that grabs cpan stuff, in a ppa
[15:36] <Hobbsee> elmo: i'd just like an exit route that doesn't involve poking you guys, when you have other stuff to do, and may not even be there, every single time.
[15:37] <Hobbsee> (like, while you're asleep, weekends, etc)
[15:44] <mpt> Hobbsee, I don't remember you mentioning, in the bug report about cancelling builds, that it was related to alleviating DOSes
[15:44] <Hobbsee> mpt: this is true.  i think i reported the cancelling builds before someone DOS'd them.
[15:44] <Hobbsee> and i'd forgottena bout when people would do it to the ubuntu buildds
=== matsubara is now known as matsubara-lunch
[16:07] <Hobbsee> nice work with the subscribing someone else who isn't usually a part of hte project, btw
[16:07] <Hobbsee> much more sane :)
=== \sh is now known as \sh_away
=== matsubara-lunch is now known as matsubara
[17:31] <ubotu> New bug: #179893 in launchpad "Can't remove my preferred e-mail address" [Undecided,New] https://launchpad.net/bugs/179893
[18:19] <andresmujica> hi, i want to search for packages published in ppa for dapper, couldn't find how to do it...any pointers?  thanks in advance
=== \sh_away is now known as \sh
[19:00] <ubotu> New bug: #179913 in launchpad "OOPS editing project license" [Undecided,New] https://launchpad.net/bugs/179913
[19:40] <ubotu> New bug: #179921 in launchpad-bazaar "Error message in propose branch for merging form is hidden behind the Target branch field" [Undecided,New] https://launchpad.net/bugs/179921
[19:45] <ubotu> New bug: #179925 in launchpad "common infrastructure for shell calls" [Undecided,New] https://launchpad.net/bugs/179925
[19:50] <ubotu> New bug: #179926 in launchpad-bazaar "Propose for merging form is broken for junk branches" [Medium,Confirmed] https://launchpad.net/bugs/179926
=== bigon` is now known as bigon
=== cprov is now known as cprov-out
[20:33] <jcastro> Hi guys, I'm trying to get the Chandler guys registered in lp with a project page, but lp tells me it exists already, yet when I search for chandler I get nothing.
[20:39] <matsubara> jcastro, it's registered but it's inactive. you'll need a LP admin to re-enable that project for you.
[20:39] <jcastro> matsubara: I see, thank you!
[20:41] <matsubara> jcastro, you're welcome
[21:51] <jtholmes> does anyone here know who is the liaison is for gdm
[21:51] <jtholmes> ubuntu gdm
[22:06] <rlaager> I'm an upstream developer on Pidgin. I'm listing in whatever grouping is necessary for me to get all the bug mail for Pidgin bugs in Launchpad, but I apparently can't change the priority of Pidgin bugs in Ubuntu. What's the policy on that? I'd like to be able to set a bug to be wishlist at the moment and can't.
[22:13] <Fujitsu> rlaager: To do that, you must be a member of ubuntu-bugcontrol.
[22:14] <rlaager> Fujitsu: I suppose you don't want to do that for upstream folks in general, then?
[22:14] <Fujitsu> I believe that the current policy is that upstream should not always have control over Ubuntu bug priorities. And there's no other way to do it in LP at the moment.
[22:15] <rlaager> Fujitsu: I would agree with that in the general case. So, I should probably just comment on the bug asking someone to change it to wishlist?
[22:17] <Fujitsu> That probably won't achieve anything - we have a lot of bugs. You might ask that someone in #ubuntu-bugs change it.
[22:17] <Fujitsu> (or me, in this case)
[22:17] <rlaager> Fujitsu: https://bugs.launchpad.net/ubuntu/+source/pidgin/+bug/17300
[22:17] <ubotu> Launchpad bug 17300 in pidgin "Pidgin Evolution Integration plugin should allow opt-out per-contact" [Low,Confirmed]  - Assigned to Sebastien Bacher (seb128)
[22:17] <rlaager> heh, speaking of that... How should things that are upstream wishlist be assigned?
[22:18] <jcastro> is there a corresponding upstream bug?
[22:18] <rlaager> In theory, if I was actively working on it, I'd want both bugs to be assigned to me. But, in this case, I doubt I'll get to it soon if ever.
[22:18] <jcastro> I would just link them
[22:18] <rlaager> jcastro: I just re-filed an upstream bug. If it was linked (which I'm not sure), we lost the old SourceForge bug report when we moved.
[22:18] <jcastro> ah
[22:18] <rlaager> I'm trying to go through the remaining open gaim bugs and update them against Pidgin.
[22:19] <rlaager> in Launchpad, that is
[22:20] <jcastro> yeah I noticed the pidgin project page is kind of sparse (no link to upstream bugtracker), I can update that
[22:20] <rlaager> jcastro: http://developer.pidgin.im ... If you need any other information, I can help.
[22:20] <jcastro> rlaager: I'm the "work with upstream" guy
[22:21] <rlaager> jcastro: Interesting. ;) I was talking with Steve Alexander at Ubuntu Live about Launchpad upstream things. Do you know if/when it would be possible to automatically pull in all upstream bugs into Launchpad?
[22:21] <jcastro> rlaager: oh, I was @ UL, but wasn't working on this.
[22:22] <jcastro> rlaager: I'm not on the launchpad team just general "upstream" issues, so I am not sure when features are coming in.
[22:22] <jcastro> rlaager: kiko and I have been having discussions on how to make all that stuff easier for upstreams
[22:22] <Fujitsu> IIRC, they're about to do something like that for Debian bugs (well, it has been about to happen for months, and keeps getting deferred), so it shouldn't be too much longer until they can do that for anyone on request.
[22:22] <rlaager> jcastro: Fair enough. It's not a huge priority. I'm thinking it'd be nice for to have one place to work on these things, be they with Pidgin, GNOME, etc.
[22:23] <jcastro> yep, I agree!
[22:24] <jcastro> rlaager: ideally what I'd like to see is have upstreams be able to have finer control of their lp presence.
[22:25] <jcastro> But that's all been brainstorming discussion so far
[22:26]  * Fujitsu is glad that this stuff is being worked on.
[22:26] <jml_> thumper: ping
[22:26] <jml_> thumper: I'm having problems with my IRC proxy
[22:27] <jcastro> rlaager: if you have any upstream-related issues feel free to drop me a line: jorge@ubuntu.com
[22:29]  * Fujitsu doesn't like the status of bug #174038...
[22:29] <ubotu> Launchpad bug 174038 in soyuz "bad md5sum in Packages file" [Undecided,Won't fix] https://launchpad.net/bugs/174038 - Assigned to Celso Providelo (cprov)
[22:29] <Fujitsu> I'd say that this sort of thing *should* be investigated, as it really shouldn't happen.
[22:33] <thumper> jml_: ok
[22:37] <jml_> thumper: can't send priv msgs yet
[22:37] <jml_> give me a moment
[23:17] <rlaager> jcastro: Thanks. The biggest thing lacking for me at the moment is personal prioritization. I'd like to be able to sort bugs for myself, so I could have a nice TODO list that way.
[23:18] <Fujitsu> win 24
[23:18] <Fujitsu> Oops.
[23:18] <jcastro> rlaager: there's no reason an upstream shouldn't be able to prioritize bugs. 
[23:18] <jcastro> I'll bring it up with kiko
[23:19] <Fujitsu> jcastro: It was discussed a little while back on some Ubuntu dev list, and it was decided they shouldn't be able to.
[23:19] <rlaager> jcastro: Well, really there should be per-project priorities (Ubuntu vs. upstream) which we already have.
[23:19] <jcastro> hmmm
[23:20] <rlaager> jcastro: But I'm asking for per-user priorities. Ubuntu could consider some crasher in the AIM prpl the most important thing, which upstream could be most concerned about some new feature, while I personally won't be working on either.
[23:21]  * jcastro nods
[23:22] <rlaager> Right now, I have plenty of bugs in Pidgin assigned to me, but I was recently working on some bugs in another application where I'm not a developer. If I could prioritize within the bugs that I was subscribed/assigned, I could get a nice ordered TO DO list.