[00:29] <wgrant> yofel: Everything should be running OK again.
[00:29] <wgrant> yofel: Problem identified, and bug filed.
[00:30]  * yofel hugs wgrant
[00:30] <yofel> :D
[05:35] <MTecknology> Under "Destination PPA:" for copying/rebuilding packages for a different series - what's the point of having "This PPA" an option?
[05:35] <MTecknology> It can't be done..
[05:36] <MTecknology> Or is it just me?
[05:36] <MTecknology> ok.. I can do it in one ppa - but not another
[05:48] <SpamapS> MTecknology: its for copying between different series
[05:49] <SpamapS> MTecknology: so you can just copy your maverick package ot lucid for instance, and it will rebuild w/ lucid's libraries
[05:49] <micahg> SpamapS: no you cannot, you can't have the same version twice in teh same archive
[05:50] <SpamapS> Err.. you sure?
[05:50] <SpamapS> I thought it was in the same "archive+series"
[05:51] <micahg> SpamapS: no, you can't "upload" the same version twice, so when it would get rebuilt in another series it would fail to upload
[05:53] <SpamapS> so why does that option exist.. seems rather silly
[05:53] <SpamapS> If you have "This PPA" selected, it shouldn't allow you to choose Rebuild.
[06:04] <wgrant> SpamapS: Right. But there's no JS to disable the option.
[06:04] <wgrant> Copying to another series with binaries is fine.
[06:04] <wgrant> And often done.
[06:07] <MTecknology> wgrant: that's what I'm trying to do
[06:08] <MTecknology> wgrant: https://edge.launchpad.net/~mtecknology/+archive/sysapps/+copy-packages
[06:08] <MTecknology> wgrant: copy Lucid->Maverick
[06:09] <micahg> MTecknology: are you copying exinsting binaries?
[06:09] <MTecknology> micahg: ya
[06:10] <wgrant> MTecknology: Does it not work?
[06:11] <wgrant> There is a bug where in some obscure situations after a copy, further copies will be impossible.
[06:11] <micahg> wgrant: maybe that's it, it seems like it was copied once already
[06:11] <MTecknology> The following source cannot be copied:
[06:11] <MTecknology> * lal 1.1-0ppa2 in lucid (binaries conflicting with the existing ones)
[06:11] <wgrant> MTecknology: Did one of the builds in the original series fail?
[06:12] <wgrant> Or does the new series have more architectures (eg. lpia?)
[06:12] <MTecknology> wgrant: It's been so long I can't remember..
[06:13] <MTecknology> wgrant: I'll assume that's what happened
[06:13] <MTecknology> wgrant: Don't you love me? I have to be about the biggest thorn in your side..
[06:13] <wgrant> Don't worry, there are much larger ones :P
[06:13]  * StevenK waves
[06:14] <StevenK> (At wgrant, specifically)
[06:14] <wgrant> GET OUT OF MY SIDE!
[06:14] <MTecknology> :P
[06:15] <MTecknology> I upgraded to 10.10 - and wiped all the extra mackages it wanted to isntall. It's a laptop - if I ever get over 600 packages installed on it I get antsy
[06:15] <MTecknology> My custom kernel makes things wanna work that much better
[06:17] <cody-somerville> moo
[06:17] <MTecknology> cody-somerville: heya, how ya been?
[06:17] <cody-somerville> not too shabby
[06:17] <cody-somerville> went for a run tonight
[06:18] <cody-somerville> need to buy new running shoes :(
[06:18] <MTecknology> sounds like a fun time
[06:19] <MTecknology> I miss being able to run. I can finally take brisk walks again
[06:19] <StevenK> % dpkg -l | wc -l
[06:19] <StevenK> 2157
[06:19] <StevenK> Hm.
[06:20] <MTecknology> doh.. I need to install less
[06:20] <MTecknology> swoody: you know dpkg -l adds a spiffy header, right?
[06:20] <StevenK> MTecknology: Which is about 3 lines, and?
[06:21] <StevenK> Given the number of packages is over 2,100, an extra 3 lines doesn't affect it much
[06:21] <MTecknology> StevenK: looked like 5 to me
[06:21] <MTecknology> true..
[06:21] <StevenK> *About* 3
[06:21]  * StevenK beats MTecknology with a stick of semantics
[06:22] <MTecknology> StevenK: You apparently don't know me "that" well yet
[06:22] <StevenK> Likely
[06:22] <MTecknology> StevenK: I have 598 installed. I'd have a lot less if I didn't compile things, use cvs, git, bzr, and a few other heavy utilities
[06:23] <MTecknology> This is the only system I have - it's a laptop - I Like to keep it light
[06:23] <MTecknology> build-essential is actually a pretty small package for what it does..
[06:23] <MTecknology> s/does/has/
[06:24] <MTecknology> ok.. beddy bye time
[08:21] <harpreet> hi every one
[08:24] <harpreet> i had a problem in logging in to lanuchpad, so i reported it (by clicking on the "https://login.launchpad.net/FClnWqj37rhpBCZd/+decide" link at the bottom of the page), it logged an issue in canonical, now i have recieved a mail in respoce to the issue, and i want to update it with screenshots.
[08:24] <harpreet> So the question here is how to see that issue again , i mean the link i am not able to search it.
[10:32] <lool> bigjools: Heya, can you help creating a sparc build record for glib2.0?  I've removed the Pas entry, but Launchpad doens't create missing build records when that happened
[10:34] <bigjools> lool: I don't have any way of doing that, the easiest route is to upload a new version
[10:35] <bigjools> we have a script that adds builds for PPAs, you could file a bug to extend it to use for Ubuntu
[10:35] <lool> bigjools: lamont mentioned a script which would do that, but said it was creating way too many build records
[10:35] <lool> I'll upload a new version then   :-/
[10:36] <bigjools> lool: I'm not sure what lamont is referring to
[10:36] <wgrant> queue-builder.
[10:36] <bigjools> ah that
[10:37] <bigjools> talk about the sledgehammer approach ...
[10:37] <wgrant> Well, it used to the The Way.
[10:37] <wgrant> s/to/to be/
[10:38] <bigjools> yeah and it shared a lock file with the old slave scanner!
[10:38] <wgrant> Heh.
[10:38] <bigjools> madness
[10:38] <wgrant> There's still more code there that I need to delete :(
[10:38] <bigjools> we need to delete the security upload stuff too
[10:39] <wgrant> I was wondering if we wanted to preserve mixed upload support at all.
[10:39] <wgrant> I guess not.
[10:39] <bigjools> it's totall redundant
[10:40] <wgrant> I guess that even means that the build creation logic can be put out of its misery.
[10:40] <wgrant> Excellent.
[10:42] <bigjools> wgrant: regarding the bug about resume trigger, URGH.
[10:42] <bigjools> wgrant: handleTimeout should not be trying to reset the builder
[10:42] <bigjools> because it'll get reset the next time we try and dispatch anyway
[10:43] <wgrant> bigjools: But we won't dispatch unless it's available, will we?
[10:43] <bigjools> notice that it just fails non-virtual builders
[10:43] <wgrant> Right.
[10:43] <bigjools> wgrant: it's still available isn't it?
[10:44] <wgrant> bigjools: This is the case where it's not responding.
[10:44] <wgrant> We want to make sure it's not completely dead before we try to dispatch to it.
[10:44] <bigjools> so it might be a brownout, the next dispatch will try and reset it *asynchronously*
[10:44] <wgrant> Yes, it's probably not a completely sane way of doing it.
[10:44] <wgrant> But it's not entirely wrong either.
[10:45] <bigjools> and if that fails we mark it down
[12:41] <lamont> bigjools: I kind of came to the conclusion that it was a bit of a sledgehammer
[14:05] <paultag> Hey Launchpad. Is there any way I can be set to the bug supervisor for ubuntu/+source/fluxbox? I'm a co-maintainer, and the only ubuntu guy, I'd like to manage the bugs ( since the maintainer does not )
[14:05] <paultag> PTS -- http://packages.qa.debian.org/f/fluxbox.html
[14:10] <gmb> paultag, It's not possible to set the bug supervisor for a source package; that's inherited from the distribution.
[14:11] <paultag> gmb: I was afraid of that :) -- is there any way to set that field to a team and override or something? I just hate to not be able to close bugs that I fix / won't fix :)
[14:12] <gmb> paultag, Well, it's inherited from the distro and the distro's bug supervisor is the Ubuntu Bugs team. If you were a member of that team you would have the necessary permissions.
[14:13] <paultag> gmb: OK. Thanks :)
[14:13] <gmb> np
[16:02] <czajkowski> aloha
[16:03] <czajkowski> Omahn: :)
[16:04] <Omahn> czajkowski: Hello! :-)
[16:04] <Omahn> https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/489142
[16:05] <Omahn> I would like to mark that bug as fixed since Lucid and then indicate that earlier releases still have an issue. Do I achieve this by setting status to 'fix released' and then using 'nominate for release' to show the versions that still have the bug present?
[16:15] <czajkowski> no LP admins?
[16:15] <Omahn> I'm sure someone will answer eventually :-)
[16:20] <Omahn> I think I've found the answer to my question: https://wiki.ubuntu.com/StableReleaseUpdates?highlight=%28nominate\+for\+release%29
[16:26] <czajkowski> mrevell: my dear are we all confirmed?
[17:13] <mrevell> czajkowski, PM
[17:37]  * czajkowski hugs mrevell 
[17:39] <mrevell> :)
[18:18] <Green00000> hi
[18:19] <Green00000> i have a question of deleting my launchpad-account.
[18:20] <Green00000> i deleted my account, but the login is just active.
[18:21] <Green00000> ???
[18:28] <Green00000> hello??
[18:31] <Green00000> zZZZZ
[19:02] <xnox> do daily builds trigger only on changes in the base branch or *any* of the branches which are part of the packaging?
[19:03] <xnox> (my recipe has "packaging" as base with "upstream" code nestted in subdirs)
[19:39] <nhandler> Hmm...Can anyone help me confirm another strange chromium + rosetta potential bug? Simply go to https://translations.edge.launchpad.net/classbot/trunk/+pots/classbot and check if the columns show a — or a 0. Chromium shows a —, but my iPod touch showed a 0
[19:45] <paultag> Hey LP. I'm playing with recipes. my debdir is set up for 3.0 quilt, and I think that's wrong. What should it be set up to do?
[19:45] <paultag> pbuilder failure here -- http://pastebin.com/8XF19Rve
[19:49] <shadeslayer> paultag: wrong file path?
[19:49] <shadeslayer> line 10
[19:49] <shadeslayer> fix your rules
[19:49] <paultag> shadeslayer: it's not calling autogen
[19:50] <paultag> shadeslayer: because I think it's not in 3.0 format and it wants it to be done manually
[19:50] <shadeslayer> oic
[19:50] <paultag> shadeslayer: path is right, but out of order
[19:50] <shadeslayer> erm...
[19:50] <shadeslayer> paultag: pastebin rules file
[19:50] <paultag> shadeslayer: sec. it's a mess
[19:51] <shadeslayer> quickly im going to drop dead any sec now :P
[19:51] <paultag> shadeslayer: http://pastebin.com/iAVTUAKF
[19:51] <paultag> shadeslayer: that's from my upstream builds. Works fine when I do it by hand :)
[19:52] <shadeslayer> my god....
[19:52] <shadeslayer> PACKAGE = fluxbox << new for me
[19:52] <shadeslayer> see this is precisely why i use KDE :P
[19:52] <paultag> shadeslayer: yeah yeah yeah. I've been meaning to fix it. In all fairness it works fine :)
[19:52] <paultag> "works"
[19:53] <paultag> as seen on http://git.debian.org/?p=collab-maint/fluxbox.git;a=blob_plain;f=fluxbox-1.1.1%2Bgit20100807.0cc08f9/debian/rules;hb=ea395692f5426b541a08c49cfc0c1226472eb8eb <-- ;)
[19:54] <shadeslayer> so it works for debian
[19:54] <shadeslayer> but not on LP ?
[19:55] <paultag> shadeslayer: yes, but from what I can see, since it's in src3, it looks for the orig.tar.gz, fails to find it and borks
[19:55] <paultag> shadeslayer: it looks like it's falling back on 1.0 and might require explicit calls, but I was wondering if this was just the way I've been seeing it, or if it actually is
[19:55] <paultag> shadeslayer: also note it's recipes off a few git branches
[19:56] <shadeslayer> no idea
[19:56] <paultag> Oh wtf
[19:56] <paultag> the build farm is throwing a different error
[19:58] <paultag> thanks for your help shadeslayer
[19:58] <shadeslayer> paultag: whut help? :P
[19:58] <shadeslayer> i didnt do anything :)
[19:59] <shadeslayer> anyways im off to sleep, so ciao
[19:59] <paultag> ciao
[20:06] <yofel> shadeslayer: afaik recipes only accept '3.0 (native)' as source format, (quilt) requires a .orig.tar.* which native doesn't create
[20:26] <flacoste> morning lifeless
[20:35] <jelmer> yofel, shadeslayer: Yeah, we don't support non-native packages just yet (see https://dev.launchpad.net/LEP/SourcePackageRecipeBuilds)
[21:18] <lifeless> hi flacoste
[21:19] <flacoste> hi lifeless, on the phone
[21:20] <lifeless> flacoste: de nada, just replying to your hi earlier ;)
[21:40] <bilbo-the-hobbit> hello
[21:41] <bilbo-the-hobbit> can someone help me here ?
[21:41] <bilbo-the-hobbit> i try to merge a team that i am owner with my profile because its easier
[21:42] <bilbo-the-hobbit> i succeded one time with another be can't remember how ?
[21:42] <ahasenack> hey guys, I reset the password for a private ppa I have access to and got a new one. That was more than 10min ago. Now both passwords (the old one and the new one) work, not just the new one
[21:52] <maxb> bilbo-the-hobbit: You definitely cannot merge a team with a person
[21:53] <bilbo-the-hobbit> maybe i explain wrong but i'am the debian maintener of the gosa/goto package suite in debian and was able to merge the two set under my
[21:53] <bilbo-the-hobbit> launchpad account
[21:53] <bilbo-the-hobbit> i want to do the same with the ofed packages for whom i'am also responsible
[21:54] <bilbo-the-hobbit> look at my page
[21:54] <bilbo-the-hobbit> https://launchpad.net/~benoit-mortier
[21:54] <maxb> bilbo-the-hobbit: Sorry, I don't understand what you're trying to do? Is there some page in Launchpad you can point to as an example?
[21:54] <bilbo-the-hobbit> yes its fusy for me also ;-)
[21:54] <bilbo-the-hobbit> https://launchpad.net/~benoit-mortier
[21:54] <bilbo-the-hobbit> this is my page
[21:55] <maxb> ok....
[21:55] <bilbo-the-hobbit> you can see that in the email you have both mine and gosa-pkg
[21:55] <maxb> right
[21:56] <bilbo-the-hobbit> i want to do the same for this group
[21:56] <bilbo-the-hobbit> https://launchpad.net/~pkg-ofed-devel
[21:56] <bilbo-the-hobbit> so i can see all my package in one place
[21:56] <maxb> erm... what does the email address have to do with seeing packages?
[21:57] <bilbo-the-hobbit> i remember that when i take the ownership of the gosa-pkg i got presente a page asking if i wanted to merge
[21:57] <bilbo-the-hobbit> but not in the case of pkg-ofed .. or maybe i have done something wrong this time
[21:58] <maxb> I think it is wrong and confusing to have the team email address gosa-pkg@oss.gonicus.de associated with a person
[21:59] <bilbo-the-hobbit> its easier for me
[22:00] <maxb> Well, it's still a misrepresentation of the truth
[22:00] <bilbo-the-hobbit> maxb: ????
[22:00] <maxb> It's not your email address, it's a team email address
[22:00]  * bilbo-the-hobbit doing the packaging on debian so its me
[22:00] <maxb> It's factually incorrect
[22:01] <bilbo-the-hobbit> please just tell me if i can do what i need or not ...
[22:09] <bilbo-the-hobbit> ok moving ....
[22:26] <lvh> hey. I'm reading https://help.launchpad.net/YourAccount/Karma, but I don't understand why karma for a new project appears to cap out at 100
[22:26] <lvh> how does that work?
[22:26] <wgrant> lvh: It doesn't. What suggests that?
[22:27] <lvh> Oh.
[22:27] <lvh> I have my own little pet project, I did a bunch of stuff, got to 100 karma very quickly, added some extra blueprints and a bug, and I'm still at 100 karma.
[22:27] <lvh> Maybe it's just taking long to update?
[22:28] <wgrant> It's meant to be updated daily, but it's possible that something's gone wrong and it's happening less frequently at the momnet.
[22:28] <lvh> Aha. Okay, thanks.