[00:47] hey all, is there a way to dput to my PPA without uploading the same orig.tar.gz? [00:48] which I've already uploaded in a previous dput, that is [00:48] radix: Just don't build with -sa... [00:49] wgrant: I didn't pass -sa [00:49] radix: What is the version string? [00:49] oh, never mind :) [00:50] Hm? [00:50] it didn't upload the same .orig.tar.gz [00:50] That could do it. [00:50] I don't know why I thought it would [00:51] er, crap [00:52] I guess I needed to upload it again after all [00:52] Why? [00:52] my first upload failed because I typoed the distroseries. now with my latest upload it can't find the orig.tar.gz [00:52] I guess it rejected the baby with the bathwater [00:52] A rejection is everything, yes. [00:53] If it rejects due to a bad sig, I don't really want the files to pollute my PPA. [00:53] understandable [00:53] so now I have the opposite problem, I guess :) [00:53] I guess I should debuild with -sa? [00:53] Correct. [00:54] Wait... [00:54] Why? [00:54] Why isn't it uploading it this time? [00:54] wgrant: so, my second upload did not upload the .orig.tar.gz, and I built ~ppa2 just the same as ~ppa1 [00:54] (debuild -S) [00:55] radix: Since it was rejected, you don't have to increment the version. [00:55] oh, okay. I thought I remember something about PPA blacklisting versions or whatever [00:55] I guess that's only for FTBFS instead of rejections [00:55] radix: that's if it actually only made it to your ppa in the first place. [00:55] It only blacklists accepted versions. [00:55] ok, so [00:55] radix: this got rejected before it reached your ppa. [00:56] I uploaded ~ppa2 and it didn't upload the source. I'd now like to upload ~ppa2 and include the source. [00:56] * wgrant uploads 9999:1 with a bad signature to Hobbsee's PPA, and cackles evilly. [00:56] wgrant: I see :) [00:56] radix: You could build with -sa, or decrement thee version. [00:57] * Hobbsee uploads ultamatix to wgrant's ppa, and uploads a new version of libc6 with ultamatix as a dependancy. [00:57] (with a similar epoch) [00:57] * Hobbsee cackles more evilly [00:57] Ok, I'll build with -sa since I know some people hate it even when you change a version that only ever saw your hard disk. [00:57] Damn. [00:57] Sounds good. [00:58] Hobbsee: I don't think Ultamatix can survive this. [00:58] wgrant: muhahahahaha :) [00:59] wgrant: you are, as always, most helpful. thank you. [00:59] Hobbsee: and thank you as well. [00:59] radix: you're welcome [00:59] radix: np [01:19] Hobbsee, o_o; [01:21] Hobbsee: ultimatix by default, should we propose that for jaunty ? :) [01:22] stgraber: only if you want to be impaled. [01:22] stgraber: Sure, once TheeMahn fixes mjg59's non-construcive criticism. [01:22] by multiple people :) [01:23] Hobbsee: I don't have upload rights, do you want to sponsor it ? :) [01:23] * wgrant is reminded of how Hobbsee fell for jdong's April 1st joke this year. [01:23] wgrant: bah, it's just a matter of using expect on apt instead of using --force-yes -y no ? :) [01:27] wgrant: that's true. but it was more fun to just have a go at him anyway. [01:35] stgraber: agreed, someone needs to upload it with Essential [03:50] hi [03:50] do PPAs build for Jaunty yet? [03:51] i'm guessing Jaunty is probably super unstable atm and the answer is no [03:53] poolie_: https://edge.launchpad.net/ubuntu/+ppas lists Jaunty as frozen, so I guess not [03:53] poolie_: if you submit jaunty builds now, they'll probably get processed once things get opened [03:53] (that's what happened for an intrepid build I submitted early last cycle [03:54] thanks [03:54] i wonder why my uploads aren't showing up there? [03:55] dunno [03:56] poolie_: that probably means that the distro "jaunty" exists, but no buildd tarballs exist for it yet [03:57] (although I note they do for regular builds, where they're still doing a toolchain) [03:57] I presume they will start existing when the archive is open for general uploads [03:57] mm [03:58] my upload will presumably either succeed or fail, so it was just general curiousity [03:58] i'd expect it'll just sit in needsbuild or something [03:58] and they're showing on that page now, which is nice [03:58] indeed! [03:58] so it doesn't look to be broken or anything [04:22] it'd be nice if feedback for builds was as responsive as for bazaar.launchpad.net ... [04:25] jamesh: yeah [04:33] spiv, 2/3 of them are done, i'm going to do the third review [04:34] but you don't need to land them right away or anything [04:34] Howdy all.. question.. how do I can my @ubuntu.com forward? === poolie_ is now known as poolie [04:36] lathiat: mail requests to rt@ubuntu.com and/or ask in #canonical-sysadmin. But as they're all asleep atm, rt@ is your best best. [04:36] thanks spm [05:32] jamesh: A distroseries' status doesn't affect PPAs. [05:32] THe reason uploads aren't working is that none of Jaunty's archs are enabled for PPAs [05:45] wgrant: ah. I assumed the "frozen" bit on the PPA page was related to no architectures being listed [05:45] * jamesh never played much with the PPA UI [05:45] jamesh: No, it's just that primary is frozen for toolchain changes. [05:45] So that bit of UI is misleading. [07:59] could it be that there are some problems with the Launchpad API login? [08:00] after the authorization page thingie I get a 401 Unauthorized [08:04] dholbach, ? [08:04] dholbach: Works fine for me (on edge) [08:07] ah ok... edge works for me too [08:32] If you use the "disable redirection to edge for 2 hours" button, can you turn the redirection back on, or do you have to wait for 2 hours no matter what? [08:33] Peng_: You should have a button on launchpad.net to reenable it. [08:34] OK, cool. :) === mtaylor_ is now known as mtaylor [12:27] hi -- I note that launchpad.net/nbd points to SF.net's CVS repository [12:27] nbd hasn't been using that repository for years, we've switched to svn ages ago [12:38] Hey, to get a super-project, do I need to set up a regular project first, or do I request the super-project and then edit the details? [12:39] (set up a regualr project and then ask for it to be made a super-project, I mean) === salgado is now known as salgado-brb === salgado-brb is now known as salgado === gary_poster changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Need help? Community help contact: gary_poster [14:34] hi. it's true: join #keyword on freenode and you're in the right place. [14:36] MisterN, you're spamming? [14:37] no. [14:38] i've got a question, but wanted to wait a few minutes before asking. anyways, here is the question: [14:38] is it possible to somehow integrate a git repository with launchpad? [14:38] i found https://launchpad.net/bzr-git but don't know if this actually works for launchpad [14:39] MisterN, not currently, no [14:39] :( === vince_ is now known as vvinet [14:43] beuno: what would you suggest? just wait until it is supported? === salgado is now known as salgado-lunch [14:44] MisterN, yeah, there's really nothing else to do for now. I Know there is some work being done to be able to import git branches [14:45] maybe jelmer knows more about this [14:45] i think it's important, as git starts to dominate pretty much [14:57] Stedevil: you asked about a code import problem for https://code.launchpad.net/~vcs-imports/freedroid/trunk on Saturday. We are aware of this problem. Please subscribe to bug 156744 if you'd like to keep up with progress. [14:58] Launchpad bug 156744 in launchpad-cscvs "bogus repository root detection" [Medium,In progress] https://launchpad.net/bugs/156744 [15:00] fta: you asked about a code import problem for https://code.edge.launchpad.net/~vcs-imports/googlechrome/trunk on Saturday. We are also aware of this problem. I do not have a bug number for you, unfortunately, but if you would like me to dig further for it, I will try. I am told that fixing this is in progress, but it will not land this cycle. [15:02] gary_poster: are you a bot? :) [15:02] MisterN: :-) no [15:02] MisterN: No, he's a cyborg assembled from the spare body parts of dead Zope devs. [15:02] lol === WelshDragon is now known as Guest81984 [15:16] hi all, is requesting a login token with launchpadlib for staging.lp.net known to be broken? [15:17] I try to use get_token_and_login() as usual, but always get a 401 error [15:18] and I'm wondering if it is launchpadlib beeing incompatible with recent changes on staging [15:18] of if it is an issue with the login (or whatever) system on staging [15:21] thekorn: I'll check into it right now and get back to you. [15:22] gary_poster, thank you [15:28] thekorn: i just tried using staging with a script that is know to work. i also got a 401 today. [15:28] gary_poster: ^^ [15:28] s/know/known [15:29] bac: good to know, thanks. I have pending question to mars and flacoste. [15:29] I managed to get an OOPS id, don't know if it helps: X-Lazr-Oopsid: OOPS-1038S23 [15:29] https://devpad.canonical.com/~jamesh/oops.cgi/1038S23 [15:30] thekorn: thanks. Not available yet, but I'll pass it along when it is. [15:36] gary_poster: Thanks, Ill subscribe to that bug :) [15:39] but gosh, it was reported >1 year ago... [15:42] cool :-) [15:45] Stedevil: I'm told it's in progress :-) I don't have it in front of me, but hopefully that status change (to "in progress") is relatively recent? [15:48] gary_poster: yeah, seems confirmed, assigned and work started all in the last 10 days [15:49] Stedevil: cool, good news then. :-) === salgado-lunch is now known as salgado [16:02] thekorn: no reply. I'll put a bug in so you can subscribe to it. [16:04] gary_poster, great, thanks === mpt_ is now known as mpt [16:08] thekorn: bug 293164 [16:08] Launchpad bug 293164 in launchpadlib "requesting login token for staging.lp.net generates a 401 error" [Undecided,Confirmed] https://launchpad.net/bugs/293164 === kiko is now known as kiko-fud === gary_poster is now known as gary_poster_lunc === Bac_ is now known as bac_ === kiko-fud is now known as kiko === boomer is now known as Guest88045 === Guest88045 is now known as boomer === boomer is now known as Guest69021 === Guest69021 is now known as boomer === boomer is now known as Guest16868 === Guest16868 is now known as boomer === boomer is now known as Guest7234 === Guest7234 is now known as boomer === boomer is now known as Guest74066 === Guest74066 is now known as boomer === boomer is now known as Guest89768 === gary_poster_lunc is now known as gary_poster [18:44] gary_poster, thanks (vcs-imports/googlechrome). an ETA would be nice, yet, it's not urgent. i'm just monitoring this branch (as there's not much for linux until now) [18:46] fta, is it on code.google.com? [18:46] fta: I'm told it won't be in the next release (i.e., within three weeks or so) but it *is* actively being worked on. My unofficial guess would be the release after that one (so, seven weeks-ish?) [18:47] kiko, yep sure, but i'm used to lp sending me patches [18:48] fta, oh, I know -- I'm just asking because googlecode's svn server is notoriously flaky [18:48] we almost never get an import of a large project from there [18:49] gary_poster, i'm also aware of that. i just wish we'll have something before uds === andrea-bs_ is now known as andrea-bs === matsubara is now known as matsubara-afk === epsy is now known as Mr === Mr is now known as epsy === epsy is now known as MrWordPress [19:17] when I look at my bugs on launchpad the list shows bugs multiple times if they are targeted to both debian and Ubuntu, or if Debian still has the bug open because they haven't applied the fix for two years... can I get rid of the entries for debian? [19:19] psusi: I'll ask for you and be back within 10 minutes with either an answer or a suggestion that you file a question in Launchpad. === matsubara-afk is now known as matsubara [19:24] psusi: from a bugs dev: "no - the best you can do is mark the debian task as invalid (if it is indeed invalid)" [19:24] damn... it isn't invalid, it's just that it's been two years now since I sent the patch to the debian bts and it has yet to be applied, and I'm getting tired of seeing it on my bug list [19:25] :-( understood [19:25] that, and the bugs that are still in progress on both show up twice on my bug list, which is just unneccesary [19:25] just makes it longer than it need be [19:26] If you see a reasonable, general-purpose Launchpad feature lurking here among the annoyances you are facing, maybe open a bug to suggest it. That's all I can suggest, I'm afraid. [19:26] Hello. I have a problem concerning ppa: A while ago, I dput ed a package to my new teams ppa, but hasn't arrived in the ppa yet; it is still empty. [19:27] homy: how long ago is a while? [19:27] gary_poster: about an hour [19:28] homy: ok. that's still conceivable that it hasn't processed yet, but I'll try to get some verification for you from a code dev. [19:29] If I try to dput the package again, dput tells me the package is already uploaded. [19:29] -f for force [19:30] or remove the .upload [19:33] ok, I'll try to re dput the package now. [19:36] nope. Pacakge is still not in the ppa. [19:36] homy: I'm told that it is likely that this will fail again, because it is likely that you signed it with a key that is not in Launchpad [19:37] So, verify that the key you are using is in Launchpad first [19:37] or not signed it at all [19:37] gary_poster: I didn't see that in the channel... [19:38] But ok, yeah, I didn't sign it. Thanks. [19:38] I homy: cool, np (thanks to bigjools actually ;-) ) [19:39] launchpad didn't ask for that prerequisite when enabling the ppa. Is all at https://help.launchpad.net/Packaging/PPA#Overview mandatory? [19:40] homy: looking [19:41] homy: unless your package is signed, it doesn't know who uploaded it [19:41] and yes the instructions are mandatory [19:42] homy, you were asking about the Ubuntero requirement, right? That appears to be the last thing. [19:43] that is, the only thing you haven't done, once you import your PGP key [20:01] now why on earth does this bug still show under my bug list? I am no longer subscribed or assigned, and neither is my team... I think it was targeted at dmraid in Janary and I retarted it to lvm since it had nothing to do with dmraid, yet it still shows me associated with the bug === salgado is now known as salgado-afk [20:16] Hey, thanks a lot for the help! Currently, my package I uploaded to ppa is building! Thanks! [20:27] I have another question about ppas: now, there is only an apt sources.list entry displayed for intrepid. Can it also be used with hardy or do I create a source package for hardy and upload that too? [20:28] you should create a package for hardy and upload that too I think [20:34] psusi: is that just the way it is meant, or does it also work without problems to just use the intrepid repos for hardy? [20:35] you can try the intrepid package in hardy by pointing your sources.list to the intrepid target, but problems might arise from it being build with a different libc and such [20:36] homy1: probably depends on what you are building against. I suspect psusi is right. [20:36] so better to retarget the source to hardy and upload it to be built on and for hardy [20:36] sorry, what do you mean with "what you are building against", gary_poster? Sorry, I'm kinda new. [20:36] psusi: ok. [20:40] ah, ok, I understood now. Thanks. [20:40] homy1: maybe "what you are compiling against"? If you build against a library in intrepid, the library is probably a different version in hardy, and your software will be looking in the wrong place for things, and you may get mysterious, very unpleasant errors. [20:40] thanks. [20:43] ppa/i386 997 builds waiting in queue ! ?? 997 ??? [20:44] the return of the evil lang packs ?? [20:46] fta: all i386 distribution build machines idle... [20:46] ppa [20:47] fta: yes, but I mean: couldn't, only when all distribution machines are idle, one of them be used for ppa? [20:49] homy1, er? i thought ppa machines were dedicated, up to a few days ago, there were far more machines dedicated to ppa, now, it's back to just 3 per arch :( [20:55] fta: I'm afraid I have no idea about the problem. Does it look like something is wrong, or just behind? [20:57] (where "too much behind" is a reasonable sort of "wrong," I suppose) [20:59] gary_poster, well, i've never seen a queue of 1000 packages in PPAs, and i use them a lot... except the lang packs that come in band of ~300 [20:59] is it possible to see the queue of ppas ? [20:59] i mean global queue, not per user [21:00] fta: I doubt it is exposed publicly. I'm going to ask about the queue; will be back. [21:00] gary_poster, i'm referring to https://edge.launchpad.net/+builds === bureflux is now known as afflux [21:03] fta: what good is the copy from ppa to another ppa function? [21:04] (oh, sorry, that was a general question, not just for fta) [21:04] homy1, ? [21:04] homy1, i'm not using it [21:13] when refreshing package lists after having added my ppa, I am told that there was a bad signature. But: it isn't created by my key, but by some generic "Ubuntu Archive Automatic Signing Key". Is there a way I can use a ppa without getting this warning and without trusting that generic key? [21:13] homy1, why don't you want to trust the key? [21:14] homy1: AIUI, no. That's how Launchpad signs the packages it built. [21:14] rockstar: because it's a generic key used for every ppa. [21:24] Can the copying packages function together with a different destination series and rebuilding the copied source be used to, eg, rebuild a hardy package for intrepid? === bureflux is now known as afflux [21:37] well, thanks anyway for all the help I got in this channel :). [21:37] bye. [21:40] hi folks [21:42] hi [21:45] and bye again, the answers link in the topic helped :) === Guest89768 is now known as boomer === boomer is now known as Guest27835 === gary_poster changed the topic of #launchpad to: https://launchpad.net/ | Channel logs: http://irclogs.ubuntu.com | Need help? Community help contact: none === MrWordPress is now known as epsy [23:46] I'm having an issue adding a bug watch to a debian bts bug. When I go to add the watch, it says "u'Package vzctl not published in Debian' (notice the u?) I know for a fact that vzctl is in Debian. Any ideas why I can't add the watch? [23:54] nhandler, what's the bug number? [23:55] matsubara: The Debian bug or LP bug? [23:56] nhandler, LP bug [23:56] matsubara: 293338