[00:29] yofel: Everything should be running OK again. [00:29] yofel: Problem identified, and bug filed. [00:30] * yofel hugs wgrant [00:30] :D === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha [05:35] Under "Destination PPA:" for copying/rebuilding packages for a different series - what's the point of having "This PPA" an option? [05:35] It can't be done.. [05:36] Or is it just me? [05:36] ok.. I can do it in one ppa - but not another [05:48] MTecknology: its for copying between different series [05:49] MTecknology: so you can just copy your maverick package ot lucid for instance, and it will rebuild w/ lucid's libraries [05:49] SpamapS: no you cannot, you can't have the same version twice in teh same archive [05:50] Err.. you sure? [05:50] I thought it was in the same "archive+series" [05:51] 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] so why does that option exist.. seems rather silly [05:53] If you have "This PPA" selected, it shouldn't allow you to choose Rebuild. [06:04] SpamapS: Right. But there's no JS to disable the option. [06:04] Copying to another series with binaries is fine. [06:04] And often done. [06:07] wgrant: that's what I'm trying to do [06:08] wgrant: https://edge.launchpad.net/~mtecknology/+archive/sysapps/+copy-packages [06:08] wgrant: copy Lucid->Maverick [06:09] MTecknology: are you copying exinsting binaries? [06:09] micahg: ya [06:10] MTecknology: Does it not work? [06:11] There is a bug where in some obscure situations after a copy, further copies will be impossible. [06:11] wgrant: maybe that's it, it seems like it was copied once already [06:11] The following source cannot be copied: [06:11] * lal 1.1-0ppa2 in lucid (binaries conflicting with the existing ones) [06:11] MTecknology: Did one of the builds in the original series fail? [06:12] Or does the new series have more architectures (eg. lpia?) [06:12] wgrant: It's been so long I can't remember.. [06:13] wgrant: I'll assume that's what happened [06:13] wgrant: Don't you love me? I have to be about the biggest thorn in your side.. [06:13] Don't worry, there are much larger ones :P [06:13] * StevenK waves [06:14] (At wgrant, specifically) [06:14] GET OUT OF MY SIDE! [06:14] :P [06:15] 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] My custom kernel makes things wanna work that much better [06:17] moo [06:17] cody-somerville: heya, how ya been? [06:17] not too shabby [06:17] went for a run tonight [06:18] need to buy new running shoes :( [06:18] sounds like a fun time [06:19] I miss being able to run. I can finally take brisk walks again [06:19] % dpkg -l | wc -l [06:19] 2157 [06:19] Hm. [06:20] doh.. I need to install less [06:20] swoody: you know dpkg -l adds a spiffy header, right? [06:20] MTecknology: Which is about 3 lines, and? [06:21] Given the number of packages is over 2,100, an extra 3 lines doesn't affect it much [06:21] StevenK: looked like 5 to me [06:21] true.. [06:21] *About* 3 [06:21] * StevenK beats MTecknology with a stick of semantics [06:22] StevenK: You apparently don't know me "that" well yet [06:22] Likely [06:22] 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] This is the only system I have - it's a laptop - I Like to keep it light [06:23] build-essential is actually a pretty small package for what it does.. [06:23] s/does/has/ [06:24] ok.. beddy bye time === sebi_` is now known as sebi` === easter_egg|off is now known as easter_egg [08:21] hi every one [08:24] 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] So the question here is how to see that issue again , i mean the link i am not able to search it. === yofel_ is now known as yofel [10:32] 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] lool: I don't have any way of doing that, the easiest route is to upload a new version [10:35] we have a script that adds builds for PPAs, you could file a bug to extend it to use for Ubuntu [10:35] bigjools: lamont mentioned a script which would do that, but said it was creating way too many build records [10:35] I'll upload a new version then :-/ [10:36] lool: I'm not sure what lamont is referring to [10:36] queue-builder. [10:36] ah that [10:37] talk about the sledgehammer approach ... [10:37] Well, it used to the The Way. [10:37] s/to/to be/ [10:38] yeah and it shared a lock file with the old slave scanner! [10:38] Heh. [10:38] madness [10:38] There's still more code there that I need to delete :( [10:38] we need to delete the security upload stuff too [10:39] I was wondering if we wanted to preserve mixed upload support at all. [10:39] I guess not. [10:39] it's totall redundant [10:40] I guess that even means that the build creation logic can be put out of its misery. [10:40] Excellent. [10:42] wgrant: regarding the bug about resume trigger, URGH. [10:42] wgrant: handleTimeout should not be trying to reset the builder [10:42] because it'll get reset the next time we try and dispatch anyway [10:43] bigjools: But we won't dispatch unless it's available, will we? [10:43] notice that it just fails non-virtual builders [10:43] Right. [10:43] wgrant: it's still available isn't it? [10:44] bigjools: This is the case where it's not responding. [10:44] We want to make sure it's not completely dead before we try to dispatch to it. [10:44] so it might be a brownout, the next dispatch will try and reset it *asynchronously* [10:44] Yes, it's probably not a completely sane way of doing it. [10:44] But it's not entirely wrong either. [10:45] and if that fails we mark it down [12:41] bigjools: I kind of came to the conclusion that it was a bit of a sledgehammer === mrevell is now known as mrevell-lunch === matsubara-afk is now known as matsubara === MTeck is now known as MTecknology === Meths_ is now known as Meths [14:05] 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] PTS -- http://packages.qa.debian.org/f/fluxbox.html === fjlacoste is now known as flacoste === mrevell-lunch is now known as mrevell [14:10] paultag, It's not possible to set the bug supervisor for a source package; that's inherited from the distribution. [14:11] 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] 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] gmb: OK. Thanks :) [14:13] np === dendro-afk is now known as dendrobates === _martin is now known as m4rtin === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates [16:02] aloha [16:03] Omahn: :) [16:04] czajkowski: Hello! :-) [16:04] https://bugs.launchpad.net/ubuntu/+source/cacti/+bug/489142 [16:04] Launchpad bug 489142 in cacti (Ubuntu) "All scripts in /usr/share/cacti/cli have a wrong path to the include directory (affected: 3, heat: 30)" [Medium,Confirmed] [16:05] 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? === rmcbride_ is now known as rmcbride [16:15] no LP admins? [16:15] I'm sure someone will answer eventually :-) [16:20] I think I've found the answer to my question: https://wiki.ubuntu.com/StableReleaseUpdates?highlight=%28nominate\+for\+release%29 [16:26] mrevell: my dear are we all confirmed? === salgado is now known as salgado-lunch [17:13] czajkowski, PM === Ursinha is now known as Ursinha-lunch === jcsackett is now known as jcsackett|afk === matsubara is now known as matsubara-lunch === salgado-lunch is now known as salgado [17:37] * czajkowski hugs mrevell [17:39] :) [18:18] hi [18:19] i have a question of deleting my launchpad-account. [18:20] i deleted my account, but the login is just active. [18:21] ??? === matsubara-lunch is now known as matsubara [18:28] hello?? [18:31] zZZZZ === Ursinha-lunch is now known as Ursinha [19:02] do daily builds trigger only on changes in the base branch or *any* of the branches which are part of the packaging? [19:03] (my recipe has "packaging" as base with "upstream" code nestted in subdirs) === fta_ is now known as fta === jcsackett|afk is now known as jcsackett [19:39] 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] 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] pbuilder failure here -- http://pastebin.com/8XF19Rve [19:49] paultag: wrong file path? [19:49] line 10 [19:49] fix your rules [19:49] shadeslayer: it's not calling autogen [19:50] shadeslayer: because I think it's not in 3.0 format and it wants it to be done manually [19:50] oic [19:50] shadeslayer: path is right, but out of order [19:50] erm... [19:50] paultag: pastebin rules file [19:50] shadeslayer: sec. it's a mess [19:51] quickly im going to drop dead any sec now :P [19:51] shadeslayer: http://pastebin.com/iAVTUAKF [19:51] shadeslayer: that's from my upstream builds. Works fine when I do it by hand :) [19:52] my god.... [19:52] PACKAGE = fluxbox << new for me [19:52] see this is precisely why i use KDE :P [19:52] shadeslayer: yeah yeah yeah. I've been meaning to fix it. In all fairness it works fine :) [19:52] "works" [19:53] 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] so it works for debian [19:54] but not on LP ? [19:55] 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] 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] shadeslayer: also note it's recipes off a few git branches [19:56] no idea [19:56] Oh wtf [19:56] the build farm is throwing a different error [19:58] thanks for your help shadeslayer [19:58] paultag: whut help? :P [19:58] i didnt do anything :) [19:59] anyways im off to sleep, so ciao [19:59] ciao [20:06] shadeslayer: afaik recipes only accept '3.0 (native)' as source format, (quilt) requires a .orig.tar.* which native doesn't create === fta_ is now known as fta [20:26] morning lifeless [20:35] yofel, shadeslayer: Yeah, we don't support non-native packages just yet (see https://dev.launchpad.net/LEP/SourcePackageRecipeBuilds) === fta_ is now known as fta === fta_ is now known as fta === jamalta_ is now known as jamalta [21:18] hi flacoste [21:19] hi lifeless, on the phone [21:20] flacoste: de nada, just replying to your hi earlier ;) [21:40] hello [21:41] can someone help me here ? [21:41] i try to merge a team that i am owner with my profile because its easier [21:42] i succeded one time with another be can't remember how ? [21:42] 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] bilbo-the-hobbit: You definitely cannot merge a team with a person [21:53] 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] launchpad account [21:53] i want to do the same with the ofed packages for whom i'am also responsible [21:54] look at my page [21:54] https://launchpad.net/~benoit-mortier [21:54] 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] yes its fusy for me also ;-) [21:54] https://launchpad.net/~benoit-mortier [21:54] this is my page [21:55] ok.... [21:55] you can see that in the email you have both mine and gosa-pkg [21:55] right [21:56] i want to do the same for this group [21:56] https://launchpad.net/~pkg-ofed-devel [21:56] so i can see all my package in one place [21:56] erm... what does the email address have to do with seeing packages? [21:57] 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] but not in the case of pkg-ofed .. or maybe i have done something wrong this time [21:58] I think it is wrong and confusing to have the team email address gosa-pkg@oss.gonicus.de associated with a person [21:59] its easier for me [22:00] Well, it's still a misrepresentation of the truth [22:00] maxb: ???? [22:00] 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] It's factually incorrect [22:01] please just tell me if i can do what i need or not ... [22:09] ok moving .... === salgado is now known as salgado-afk [22:26] 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] how does that work? [22:26] lvh: It doesn't. What suggests that? [22:27] Oh. [22:27] 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] Maybe it's just taking long to update? [22:28] 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] Aha. Okay, thanks. === matsubara is now known as matsubara-afk === oubiwann-sick is now known as oubiwann === oubiwann is now known as oubiwann-away