[00:06] hey, how long does it usually take for packages to be published? The package here already waits 10h to be published https://edge.launchpad.net/~neon/+archive/ppa/+packages [00:07] yofel: It should be done within 5 minutes. [00:07] Let's see. [00:07] yofel: I was about to ask that === flacoste is now known as flacoste_afk === flacoste_afk is now known as flacoste [00:07] Quintasan: beat you :P [00:15] yofel: Can you visit https://launchpad.net/~neon/+archive/ppa/+edit and confirm that the 'Publish' setting is checked? [00:16] Quintasan: ^ [00:17] ahh [00:17] solved [00:17] wgrant: thanks [00:18] I really need to convince people that we should remove that checkbox. [00:19] it doesn't make sense for users to have access to it. [00:21] well [00:21] I can only agree on that [00:26] wgrant: You ever have a day where you've done a whole lot of work - but got nowhere? [00:27] MTecknology: Regrettably so. [00:27] wgrant: All I can think about is going to the bar - but I don't go there so it wouldn't make sense... [00:27] wgrant: you happen to know much about recipes? [00:28] MTecknology: A bit. [00:28] Why? [00:29] wgrant: I've been fighting them and maybe I'm missing some dumb thing [00:31] wgrant: I have this recipe that works perfect locally - http://paste.ubuntu.com/467253/ - but a recipe in LP can't use run [00:32] MTecknology: Couldn't you just use merge for the debian changes? [00:32] rinze: bzr: ERROR: Branches have no common ancestor, and no merge base revision was specified. [00:33] Give them a common ancestor. [00:33] how? [00:33] Base your packaging changes branch on your normal branch. [00:34] Any chance you could hold my hand a wee bit on this one? [00:35] as if it hasn't been held enough.... [00:35] MTecknology: Why isn't lp:~nginx/ninx/debian-changes-0.8 based on lp:~nginx/ninx/debian? [00:35] If it was, you could just merge it in. [00:36] I couldn't figure out how to base it on the branch [00:36] bzr branch lp:~nginx/ninx/debian debian-changes-0.8 [00:36] Make the changes. [00:36] Commit. [00:36] Push. [00:37] and if I only want to maintain the one file in that branch? [00:37] Why would you want to do that? [00:38] the more I think about that - the more it sounds like a better idea [00:38] I'll do that [00:41] Incidentally, I'm working on a change to recipes to allow merging files/directories from unrelated branches, but I think wgrant's advice here is good even if that work were finished and deployed. [00:42] spiv: I'm doing that now and finally clicked why that's a better idea [00:42] spiv: and incredibly awesome feature to add :) === mordred_ is now known as mtaylor [00:46] wgrant: so I'm taking the lp:~nginx/ninx/debian out of the recipe entirely? [00:48] MTecknology: It depends. [00:48] If you leave it in, you'll automatically get changes from that branch. [00:49] Which is probably what you want. [00:49] yup - which is why i thought I didn't need any files other than the ones i was changing [00:50] Remember that it's a merge, not a clobber. [00:51] so it'll look like this instead? http://paste.ubuntu.com/467258/ [00:52] I think so. [00:53] I'll try it out... [00:55] wgrant: do I love you, no... do I want to buy you a beer... yes [00:55] Hah. [00:56] wgrant: so if they change file xyz my branch will overwrite their change when I do the merge since it's something I changed? [00:57] MTecknology: It will follow normal bzr merge rules. [00:57] If you both change the same part of the file, it will conflict. [00:58] wgrant: oh... that'll happen every time [00:58] MTecknology: lp:nginx/ninx/debian changes regularly? [00:59] It's only your delta relative to lp:nginx/ninx/debian that matters. [00:59] wgrant: the file I changed will [00:59] I changed a file that they will change [00:59] Howso? [00:59] I'm horrible with understanding merge conflicts so my face blanks [01:00] changelog and a couple others that will be less frequently changed [01:00] You shouldn't be modifying the changleog. [01:00] bzr-builder does that for you. [01:01] except that it won't handle if your building a different version with the same changelog [01:01] Hm? [01:02] there's stable 0.7.x and development 0.8.x - both can use the exact same debian/ [01:03] But bzr-builder handles the new changelog entry for you. [01:04] how do I assign it the right version? [01:04] MTecknology: The deb-version bit in the first line of the recipe. [01:05] wgrant: I'd very much rather not have to change that for every single build but... doesn't sound like I have the choice [01:05] MTecknology: the deb-version can include things like {revno} [01:06] So you shouldn't have to change it every single build. [01:06] Exactly. [01:06] spiv: the version will change with every build [01:06] It'd be fairly useless for daily builds otherwise. [01:07] MTecknology: What do you mean? [01:07] the branches will only change with new versions [01:07] As in new stable releases? [01:07] yup [01:08] Hmm. I don't know enough about the version syntax to tell you how to solve that. [01:08] spiv: Do you know? [01:09] wgrant: I was saying earlier that {last_tag:branch_name} would solve this for me [01:09] wgrant: I can see no sign of the file that dpkg-source is whinging about in the uploaded archive [01:09] wookey: It must be a dpkg bug which has since been fixed. [01:10] wgrant: it just has {revno}, {time}, {revno:BRANCH-NAME} and {debupstream} I think [01:10] {debupstream} is what I was trying to get at [01:10] that's the exact string I want for 0.7.x [01:10] but not for 0.8.x [01:11] hmm, so given that I promised to upload this today, but the pristine source I gave to Debian won;t uplaod to my PPA, what do you suggest I do? [01:12] (the user who wanted it need a version rebuild on maverick because the libvtk is different on ubuntu) === Ursinha-dinner is now known as Ursinha [01:13] I can build it on my maverick chroot here but that will produe amd64 packages and he wants i386 [01:14] spiv: # bzr-builder format 0.2 deb-version {debupstream}-0ppa{revno} <-- I think that's right for 0.7.x - For 0.8.x I would need to have 0.8.34-0ppa{revno} and for every branch upload change the version.. [01:16] What's the recipe look like? [01:16] https://code.edge.launchpad.net/~nginx/+recipe/nginx-develpment [01:18] Won't the {revno} take care of that already? [01:19] spiv: It's the 0.8.34 that I don't like having to change every time I want to make a new build [01:19] spiv: I know I'm asking a lot from something that's still very beta.. [01:24] MTecknology: oh, I see. [01:25] MTecknology: it would be good to support that, although I'm not sure what a good mechanism for that would be [01:25] spiv: last_tag :D [01:25] There's no such concept in bzr. [01:26] "highest" tag, perhaps. [01:26] ya, that [01:26] Although that strikes me as pretty fragile, and dependent on details of how projects tag things. [01:26] I wonder if it could use pristine tar information instead. [01:27] Please file a bug on bzr-builder for this, but the solution isn't obvious to me. [01:27] In the meantime, perhaps just call your package 0.8? Or 0.8.x if debian allows that... [01:28] spiv: maybe you know this one... bug 608450 mentions having a branch you can merge that makes the changes [01:28] Launchpad bug 608450 in Launchpad Bazaar Integration "Can't use 'run' in recipe (affected: 1, heat: 6)" [Undecided,Invalid] https://launchpad.net/bugs/608450 [01:29] The rationale given there doesn't make sense, AFAICT. [01:30] We put in an awful lot of work to make sure recipe builds were as secure as PPA builds. [01:30] And they are. [01:30] So there's no security risk, unless we evaluate the recipe somewhere else. [01:30] MTecknology: I have a branch intended to permit merging debian/ from a branch with unrelated history [01:30] spiv: that one let lets you basically overwrite files? [01:31] MTecknology: no [01:31] But if you know there are files in an existing branch, well make a branch based on the existing branch and merge it in. [01:31] wgrant: It's kinda sad because I actually got excited when I maqde it run locally :P [01:33] I've also been considering just asking the deb maintainer to just had another svn branch in trunk for 0.8 :P [01:33] My patch is targetted to the 'parallel import' case, where Launchpad has essentially the same project in unrelated branches via code imports and package imports, and you'd like to make a recipe to e.g. package the latest upstream trunk using the same packaging that's already in ubuntu. [01:33] that sounds a lot like my use case [01:34] I don't think it is. [01:34] oh [01:34] maybe a use case matching what i had in my head [01:36] My patch (currently) adds a 'merge-part' instruction to recipes so that you can specify merging just part of a (possibly unrelated) branch, e.g. 'merge-part debian-from-parallel url://to/branch -1 debian/', IIRC [01:36] wgrant: far as the security things goes - I could see the point if rules didn't basically allow you to do the same thing [01:37] spiv: nice [01:37] MTecknology: Right. You can already execute arbitrary code, so the restriction is pointless. [01:39] wgrant: I guess this is just part of workign out the kinks :P [01:41] It's 19:40 and I got here at 07:40... I should continue working from home.. [02:45] wgrant: so.. I just emailed upstream about making a debian-dev - we'll see if she's up for that [03:20] Can I cross-reference a bug in project FOO in a bug report to a project BAR? If so, how? [03:21] tcr: So, it depends on how the bugs are related. Do you have two in particular for this case? [03:22] What do you mean by cross-reference, exactly? As a minimal option, you can write "See also bug 999999" in a comment, and it will be automatically hyperlinked. [03:22] Error: Could not parse data returned by Launchpad: 999999 (https://launchpad.net/bugs/999999) [03:23] spiv: The numbers are universally unique? I'd have thought they're unique per project only? [03:23] No, they're universally unique. [03:23] I had my account suspended, how do i find out why it was? [03:23] Oh that's cool, and news to me. [03:23] Unless your project has 600000 bugs. :) [03:23] launchpad account [03:23] thiebaude: which account? [03:23] lauchpad [03:23] launchpad [03:23] thiebaude: no :-) what was the name of it. [03:24] spiv: That's all I wanted. Thanks [03:24] launchpad.net/~thiebaude? [03:24] ok let me check 1 sec [03:25] yes it is thiebaude [03:27] thiebaude: ok, apparently your account was being abused to send spam back in April; and was duly suspended. [03:28] can i get it back [03:28] since i did't spam [03:30] thiebaude: I didn't mean to imply _you_ had; only that your account was. possibly your PC was trojaned or similar. You ain't the first, won't be the last. [03:30] ok thanks for that info:) [03:30] spm [03:30] i understand [03:31] what is the next step for me to get the account back? [03:31] thiebaude: I've reactivated it; but you'll need to go thru the 'forgotten password' steps [03:32] spm ,ok thanks i sure will, and thank you for helping me:) [03:33] np :-) [03:33] tc [04:34] Is it possible to add icons and screenshots to thing in my PPA for the software centre? [04:38] Muscovy: Not at the moment. But I believe the Software Center people are working on that sort of thing. [04:46] Ok, thanks. === Cepheus is now known as Cepheus|Away [05:23] spm: whois says you're around - any chance you could make me blink with joy? [05:47] MTecknology: whazzup? [05:48] thumper: I was hoping for a peak at an answer request [05:48] MTecknology: ah [05:48] thumper: Are you an LP admin? [05:49] MTecknology: alas, no [05:49] Seems there used to be a lot more than there are now [05:50] MTecknology: no... not really [05:50] oh, then my mind fooled me in the past :P [05:51] There were, but not for a few years now. [05:52] I've been using LP for a while now.. I can vaguely name a few I was pretty sure were on the list - back when I called 'em all rubber duckies [05:53] so.. what is the limit on number of times you can build a package for each release in a day? [05:54] 5, I believe. [05:54] It is a stupid restriction. [05:55] oh.. I thought I did a lot more than 5 today - I wasn't surprised to hit it :P [06:35] there's a restriction on #builds of a package? huh. didn't know that one. [06:36] spm: There's a new restriction on the number of builds per day of a recipe for each series. [06:36] It is the only such arbitrary limit in Launchpad, I believe. [06:36] Ahh I see. I'm aware of the new recipe stuff, but don't know too much about it unf. [06:37] Except for the PPA disk quota, I guess. [06:37] that one does make sense in a 'please clean up what you *really* want from what you don't; then ask for more' sense. [07:41] MTecknology: please file bugs on bzr-builder with your requests [08:00] https://help.launchpad.net/ReadingOpenPgpMail recommends using FireGPG for reading openpgp mails on Gmail. However, the FireGPG project is discontinued and the software no longer supports gmail [08:01] is this the correct channel to report this? [08:04] mistrynitesh: yeak [08:05] mistrynitesh: there has been some recent work on email authentication using DKIM (I think that's right) [08:05] mistrynitesh: so that may mean that email from gmail will be trusted as if it was signed [08:05] yes [08:06] * thumper just noticed the typo above [08:06] s/yeak/yes/ [08:06] although I probably was going to say yeah [08:06] ak isn't anywhere near s [08:06] thumper: It's actually landed. [08:07] So 10.08 will automatically verify emails from Gmail. [08:07] wgrant: but probably not live yet [08:07] Right. [08:07] wgrant: how goes the new semester? [08:07] last one right? [08:07] lifeless: morning, you there for the entire week? [08:08] thumper: i did not understand what you meant by "email from gmail will be trusted as if it was signed" [08:09] thumper: yea, GHM in den hag on the weekend then home on monday, get in wed [08:09] mistrynitesh: sorry I misread your initial question [08:09] mistrynitesh: is the email signed or encrypted? [08:09] encrypted [08:10] so I had to copy the mail to a text file and then read it on command line [08:10] I don't know an answer, perhaps a more general firefox forum could help === jtv changed the topic of #launchpad to: http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: jtv | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ [08:10] morning jtv [08:10] hi thumper [08:10] you going to Den Haag then? [08:10] sure, what I wanted to report is that the help page on launchpad should be updated with this development [08:11] mistrynitesh: ok, thanks [08:11] thumper: It starts Monday. And yes, it's the last one. [08:11] Then I have to find something to do. [08:11] jtv: thumper is in NZ again already [08:11] ah [08:13] * thumper wanders off === oubiwann-away is now known as oubiwann === dendro-afk is now known as dendrobates === persia` is now known as persia [12:19] james_w, wgrant, maxb: can something be done about that import -> https://code.edge.launchpad.net/~vcs-imports/kdelibs/kde4 failing? [12:21] Quintasan: Only by someone first fixing bug 579491 [12:21] Launchpad bug 579491 in Bazaar Subversion Plugin "iter_changes on caching logwalker supports only one prefix (affected: 1, heat: 4)" [Undecided,Triaged] https://launchpad.net/bugs/579491 [12:21] hi i would like to know if theres a way to make https://code.edge.launchpad.net/~vcs-imports/kdelibs/kde4 work [12:22] james_w, wgrant, maxb: can something be done about that import -> https://code.edge.launchpad.net/~vcs-imports/kdelibs/kde4 failing? [12:22] Quintasan: Only by someone first fixing bug 579491 [12:22] ah.. [12:22] i see Quintasan already asked :D [12:22] You two seem to come in pairs :P [12:22] well, we want Project Neon to move since I figured out how to build Qt :P [12:22] wgrant: were trying to get project Neon up and working [12:23] shadeslayer: wut, I'm the spokesperson for our project :P [12:23] wgrant: perhaps the idea is: if more people ask then it seems to be important and more likely to get fixed. would that work? [12:23] * shadeslayer thought it was a collaborative effort :( [12:24] shadeslayer: yeah, but repeating the same sentence over again won't help :P [12:24] well, let's increase the 'affects' count a bit in any case... [12:24] Quintasan: i didnt know you asked ^_^ [12:25] shadeslayer: http://paste.ubuntu.com/467466/ [12:26] ok :P [12:41] btw how come gitorious.org is not recognized by LP? [12:42] Not recognised? In what sense? [12:44] wgrant: for eg. when i login with the LP open id , i get a warning saying that gitorious.org is not recognised by launchpad open sign in service === mrevell is now known as mrevell-lunch [12:44] I don't know. Ubuntu/Launchpad SSO aren't actually part of Launchpad any more. [12:45] ah ok [12:45] But it just means it's not been explicitly configured yet. [12:45] I don't know why it tells you that. [13:04] spm: not still up are you? [13:10] merge packaging lp:~bzr/bzr/packaging << whats the role of the word 'packaging' here? [13:10] the first one... [13:10] shadeslayer, is this in a build recipe? [13:10] yes [13:11] im trying it out for rekonq first.. so that i can work on kdelibs [13:13] shadeslayer: It gives the branch a name in the recipe. You can then say {revno:packaging} in the version string. [13:14] wgrant: ok.. another question then,suppose im merging the 2 branches,and my packaging is in http://bazaar.launchpad.net/~rekonq/rekonq/rekonq-ubuntu/files [13:15] and im using merge packaging lp:~rekonq/rekonq/rekonq-ubuntu [13:15] would that work? [13:15] That should work, yes. [13:15] Assuming that the branches have a common ancestor. [13:15] common ancestor? :D [13:16] rekonq-ubuntu has to be based on the original branch. [13:17] theres no original branch [13:17] Hm? [13:18] You're merging the branch into something. [13:18] wgrant: this is the first import of rekonq packaging branch [13:18] shadeslayer: What is the base branch of your recipe? [13:18] wgrant: none... [13:18] uh [13:19] you mean the initial code import [13:19] You can't merge into nothing. [13:19] After the initial recipe header line, there is a branch name. [13:19] ohhh.. one sec [13:19] Then you have subsequent directives like 'merge blah lp:blah' [13:20] The base branch is retrieved, then the directives are followed on top of that. [13:20] wgrant: https://code.edge.launchpad.net/~rekonq [13:20] rekonq-ubuntu is packaging and rekonq/trunk is base branch [13:21] So, that's not going to work. [13:21] ok.. why? [13:21] rekonq-ubuntu isn't based on trunk. [13:21] So there's no way to merge them. [13:22] rekonq-ubuntu appears to be the contents of the debian/ directory? [13:22] YES [13:22] sorry for the caps [13:22] Why isn't it a full branch, with an added debian/ directory? [13:23] you mean it should be a branch with a debian/ folder and then it should be used? [13:23] I think you should create a new branch of trunk and throw the debian/ directory in there. [13:24] That's pretty much how the Ubuntu packaging branches work. [13:24] ohh i see [13:24] So your packaging branch is a complete extracted Debian source package. [13:24] It has the application source, and it has the debian directory. [13:24] wgrant: lemme show you something [13:24] shadeslayer: http://www.advogato.org/person/robertc/diary/130.html may be helpful [13:24] wgrant: https://code.edge.launchpad.net/~neon [13:25] same thing there... we have qt-ubuntu and qt-trunk [13:25] uh.. qt-kde [13:26] so qt-kde is our intial import [13:26] and qt-ubuntu is our packaging branch [13:27] Is there a reason you've done in that way? [13:27] wgrant: you would have to ask Quintasan :D [13:32] wgrant: well, if there is a debian/ directory inside a branch and nest requires a name of the dir [13:33] so it would look like: ./debian/debian/control [13:33] Quintasan: Why not make the branch look like a source package? [13:33] Just a branch of trunk, but with the debian/ directory added. [13:33] Then a plain merge is all that's required; no nest. [13:34] btw is the {date} plugin now available in recipes ? [13:34] wgrant: I don't get it, you want me to put debian/ to our kde-qt branch [13:34] ? [13:34] shadeslayer: date was available all the time O_o [13:34] ah ok [13:35] Quintasan: No. In a branch of kde-qt. [13:36] Rather than having qt-ubuntu as a standalone branch, have it be based on qt-kde, but with the added debian/ directory. [13:36] and how do I do that? [13:36] bzr branch qt-kde qt-ubuntu [13:36] cd qt-ubuntu [13:36] [13:36] bzr add [13:37] bzr ci -m "Add packaging." [13:37] bzr push [13:37] ill bbl [13:40] wgrant: and how the daily build will handle this? [13:41] Quintasan: The recipe that's there at the moment is for this kind of model. [13:41] It won't work with the qt-ubuntu branch that's up there now. [13:41] wgrant: http://pastebin.com/t9XE2wnv [13:41] that's the recipe I used to generate qt-kde source tarball === mrevell-lunch is now known as mrevell [13:43] Hey folks [13:43] I fucked up [13:43] Quintasan: Ah. I was looking at a recipe on LP, which has since been deleted. [13:43] Quintasan: Replace the third line with 'merge debian lp:~neon/project-neon/qt-ubuntu'. [13:43] I created a regular project and cant attach it to a project group now; I should have created it under the project group [13:43] Would some admin be able to fix that for me? [13:44] lool: Click 'Change details' on your project. [13:44] linaro-toolchain is the meta-project (group) and linaro-toolchain-misc is the project which should be attached to the group [13:44] Find the 'Part of' field. [13:44] wgrant: Gah, thakns [13:45] wgrant: worked fine [13:45] wgrant: well no need to place debian/ intro source then? [13:45] into* [13:45] Quintasan: debian/ will exist in qt-ubuntu. qt-kde won't have it. So you tell the recipe to merge qt-ubuntu into qt-kde. [13:46] great [13:46] That way you get the latest code from qt-kde, and the debian/ directory from qt-ubuntu. [13:58] bzr: ERROR: Branches have no common ancestor, and no merge base revision was specified. [13:58] wgrant: ^ [13:58] Quintasan: Sounds like you didn't branch qt-ubuntu from qt-kde... [13:59] from #openstack: you know, from an end-user perspective (someone looking for info or code for a project they're interested in), I've never liked launchpad, but I just did a merge proposal, and it was one of the easiest experiences I've had outside of maybe github. [14:00] nice :) [14:00] now let's fix the other bits [14:00] Well, some UI design might help... [14:36] GRR [14:38] wgrant: I have qt-kde (Qt source code) and qt-ubuntu (contains debian/) directories sitting in my home, doing bzr branch qt-kde qt-ubuntu = bzr: ERROR: Target directory "qt-ubuntu" already exists. and --use-existing-dir yields me error that qt-ubuntu is already a branch === Cepheus|Away is now known as Cepheus [15:05] I keep getting bug reports sent to me from launchpad and see no way to stop them or unsubscribe what should I do to unsubscribe from them [15:07] Are you receiving updates on one bug or lots of bugs for a project? [15:07] ocatacoo: the last line of the email should explain why you are receiving the email. [15:07] ocatacoo: there should be an explanation of how you're subscribed at the bottom of each email. [15:08] You received this bug notification because you are subscribed to [15:08] Hardware Certification. [15:08] thats why :) [15:08] but I am not subscribed [15:08] ocatacoo: un-subscribe from the h/w certification team/ML [15:10] thats not the bug kist but I am not subscribed to them either and not getting from the mailing list anyway [15:11] ocatacoo: Have you been to https://bugs.launchpad.net/hardware-certification to check what subscription options you get in the right-hand menu? [15:13] hi im getting this FBTFS with LP recipes http://launchpadlibrarian.net/52316355/buildlog.txt.gz [15:13] and i have no idea what it means... ive never seen that error before [15:14] it shows that I can subscribe [15:14] shadeslayer: I believe it means recipe builds are completely broken on maverick owing to changes in the default package seeding which no longer include aptitude in the chroot [15:15] :/ [15:15] hmm... [15:15] maxb: about that import bug, do you have someone working on it or you lack information? [15:15] maxb: how can we fix this? [15:15] hardware cert doesnt have a mailing list that I can find anyway [15:16] Quintasan: You sound like you think I'm officially associated with Launchpad :-) I'm not. [15:16] shadeslayer: I've not looked into it in detail, but I imagine the proper fix is to fix pbuilder to not assume aptitude is part of the base chroto [15:18] maxb: Well, you're running around answering everything, I assumed you are in some way :P [15:18] * maxb afk [15:18] Quintasan: Hi [15:18] jelmer: um, hello [15:19] Quintasan: what are you trying to do exactly? [15:19] Quintasan: it sounds like you're trying to clone a branch to a location where a branch already exists [15:20] jelmer: doesn't matter now, I'm not going to copy 300mb source tree just to replace a nest line with merge [15:20] not worth it [15:20] so where do I need to ask to unsubscribe? [15:22] ocatacoo: gmb may be able to help [15:22] jtv, ? whatis gmb ? [15:22] Quintasan: I think "bzr join" does what you were looking for, if you ever need it later [15:23] ocatacoo: he's a Launchpad engineer, gmb is his nickname on IRC :-) [15:23] ocatacoo: gmb is someone who may show up now that his name's been dropped :-) [15:23] shadeslayer: What is the related recipe? [15:24] jelmer: for rekonq? [15:24] shadeslayer: yeah - is that for which you just pasted the FTBS log? [15:25] yes one sec [15:25] jelmer: https://code.edge.launchpad.net/~rekonq [15:25] everything is there [15:26] rekonq-ubuntu is packaging branch [15:27] shadeslayer: you probably need to add a build-depend on aptitude [15:30] bigjools, I don't think that will work, pbuilder satisfies those depends, so pbuilder will already be running before aptitude is installed. === matsubara is now known as matsubara-lunch === sebi_` is now known as sebi` [15:39] jtv: I contacted him through launchpad , I just didnt want to file a bug because of something so trivial [15:40] abentley: it also should be up to the user to install aptitude because pbuilder happens to use it [15:40] has the dependency on aptitude in maverick perhaps been changed from Depends to Recommends? [15:40] the dependency of pbuilder on aptitude I mean [15:41] abentley, bigjools: Yeah, that looks like it: [15:41] jelmer, pbuilder never had a dependency on aptitude, but aptitude used to be in base. [15:41] ocatacoo: you can also file a question under Answers [15:42] ocatacoo: if it turns out to be really a bug, the question can be turned into one—although of course usually that's not the case [15:42] jelmer, the choice to use pbuilder is not the user's, so it shouldn't be up to the user to install aptitude. [15:42] abentley: It seems strange that it doesn't even recommend or suggest it even though it can generate scripts that use it. [15:42] abentley: Argh - that's what I meant to say, sorry [15:43] missing negation in that sentence [15:43] jelmer, yes, bugs have been filed about the lack of a dependency. However, when used as directed, AIUI, pbuilder's lack of a dependency is not a problem. [15:44] jtv: thank you I am sure that I just don't see something that I should , but I have looked , just obviously not in the right place... [15:44] abentley: ah, ok [15:44] jelmer, because the scripts install aptitude in the chroot and then run scripts in the chroot. [15:44] abentley: Ahh, of course [15:44] abentley: Please ignore me :-) [15:45] ocatacoo: it's not always easy with so many ways to get subscribed to something... I do know for a fact that it must be some kind of direct subscription in your case. If it were indirect (i.e. because you're a member of a team that's subscribed) then the message would say so. [15:45] ocatacoo: you're not registered as a bug reporting contact or somesuch either? [15:47] not that I can see but ...? [15:49] btw any idea if the svn import plugin will be fixed? [15:49] Have a good day... [15:49] Fixed in what way? the kdelibs thing? [15:49] maxb: yeah :( [15:49] were stalled for now [15:49] I gave the bug number. You can look at the history of it there. [15:49] Or maybe even try your hand at fixing it :-) [15:50] if only i knew python ^_^ [15:50] I know how to fix it, I just haven't had the time to spend on doing so. [15:51] jelmer: oh please please please fix it :D [15:51] ill send you cookies [15:53] (-: [15:53] also.. pbuilder needs fixing :/ [15:54] btw how come Quintasan's Qt build went through but not my build? [15:54] shadeslayer: Was he perhaps building for Lucid? [15:54] jelmer: nope..karmic build [15:55] shadeslayer: Ah, still.. karmic and lucid had aptitude in base, maverick doesn't [15:55] uh [15:55] IIUC [15:55] jelmer: s/karmic/maverick [15:55] shadeslayer: No idea then.. [15:55] abentley: do you know perhaps? [15:56] jelmer, know what? [15:57] abentley: why rekonq is FTBFS in maverick while Qt builds fine [15:58] shadeslayer, not yet. Can you give me some build URLs? [15:58] sure [15:58] abentley: https://code.edge.launchpad.net/~rohangarg/+recipe/rekonq-daily/+build/402 [15:58] thats rekonq FTBFS [15:58] which is due to aptitude not being in the base ubuntu chroot [15:59] abentley: http://launchpadlibrarian.net/52262923/buildlog_ubuntu-maverick-amd64.project-neon-qt_1.0%2B1200~ppa1_FULLYBUILT.txt.gz [15:59] thats Qt being built fine [16:00] shadeslayer, that looks like a binary build. [16:00] abentley: binary build? Quintasan ^^ [16:01] james_w: for being able to use 'run' I filed one and it was marked invalid - I'll add a bug for the latesttag [16:17] MTecknology: thanks === bigjools-afk is now known as bigjools === beuno is now known as beuno-lunch [16:38] mthaddon: You renamed ninx to nginx but I still see "Bazaar branches of Ninx" :S === fta__ is now known as fta [16:41] MTecknology: ok, fixed [16:42] Could someone help me to merge the imported account 'sense-ubuntu' into 'sense'? I've tried several times, but it timed out each time. The latest Error ID is OOPS-1664ED1753. I need to merge before I can get my new email address to associate with my account. [16:42] https://lp-oops.canonical.com/oops.py/?oopsid=1664ED1753 [16:43] mthaddon: was it just an easy to set variable? [16:43] yep [16:44] cool [16:44] mthaddon: oh, that stuff was removed if you want to disable the other one :) [16:45] MTecknology: ok, done [16:46] Either the PPA publisher is getting slower or I'm getting more impatient [16:46] it's slower than it used to be :( === matsubara-lunch is now known as matsubara === jtv changed the topic of #launchpad to: http://launchpad.net/ | Read https://help.launchpad.net/ for help | Help contact: - | Join https://launchpad.net/~launchpad-users | This channel is logged: http://irclogs.ubuntu.com/ | Launchpad is open source: https://dev.launchpad.net/ === beuno-lunch is now known as beuno === dendrobates is now known as dendro-afk === matsubara is now known as matsubara-afk === matsubara-afk is now known as matsubara === Ursinha is now known as Ursinha-nom [20:19] hello, who should I talk to about the ppa builder? [20:19] two of my build seen to have entered a loop [20:19] https://launchpad.net/~stoq-maintainers/+archive/unstable/+build/1885729 [20:20] kiko, ^ [20:21] romaia: entered a loop? [20:21] romaia: the one you posted just started [20:21] shadeslayer, yes, [20:21] +building [20:21] shadeslayer, try reloading the page. [20:21] the time counter restarts a few times, [20:21] than the status go back to queued [20:22] it has been like for amount an hour. [20:23] mmm [20:23] its back to started 7 secs ago [20:23] something is wrong it seems [20:23] https://launchpad.net/~stoq-maintainers/+archive/unstable/+build/1885704 [20:23] this one as well [20:27] StevenK, hey, could you take a look at the issue ^ please? anything wrong with the builder? [20:27] romaia: the second one seems to be fixed [20:27] shadeslayer, yes. [20:27] and the first one is now building [20:29] shadeslayer, any idea what happend? [20:29] is it worth filling a bug? [20:29] romaia: a) temporary issue b) someone fixed it [20:29] romaia: nah... [20:29] but if it makes you feel good,go ahead :P [20:30] if it happens again... [20:30] maybe it has something to do with the fact that I pressed the force rebuild button. [20:31] shadeslayer, thanks anyway [20:31] romaia: :D === Ursinha-nom is now known as Ursinha [21:36] What's going on here? bzr branch lp:~nginx/nginx/debian.mod_wsgi bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~nginx/ninx/0.8/". [21:39] oh! [21:40] lifeless: how can I unstack a branch? [21:41] bzr reconfigure --unstacked [21:41] thanks [21:41] * MTecknology corsses fingers [21:42] romaia: that's generating the same error - any ides how I can fix it - the project was renamed so the branch it was stacked on is gone [21:43] MTecknology, sorry, no idea. [21:43] I just know the unstacked commands since I use it quite often [21:44] I rarely use it but was hoping that'd be the ticket - I suppose it need sot know what it's stacked against before it can unstack though [21:46] Looks like the guys that can fix it are in a meeting [21:47] mthaddon: when you're back from your meeting could you take a peak at this? === dendro-afk is now known as dendrobates === dendrobates is now known as dendro-afk === dendro-afk is now known as dendrobates === dendrobates is now known as dendro-afk === matsubara is now known as matsubara-afk