=== fta_ is now known as fta [00:36] wgrant: maybe you could help me, can I somehow force stripping in PPA build? I need dbg libs for Project Neon :) [00:36] Quintasan: Not really... but I was working on that over the weekend, as it happens. [00:37] gah [00:38] It's mostly done. [00:39] wgrant: well, I'm doing that via dh_strip --dbg-package=project-neon-qt-dbg [00:40] I guess that works. [00:40] But it'll be automatic and less awful soon. [00:40] yeah, I thought it would work in PPA too [00:40] :S [00:41] It doesn't? [00:41] Why not? [00:41] dh_strip --dbg-package=project-neon-qt-dbg [00:41] dh_strip debug symbol extraction: disabling for PPA build [00:41] dh_strip debug symbol extraction: not doing anything since NO_PKG_MANGLE is given [00:43] Hmm. [00:43] Well. [00:43] I guess pkg-create-dbgsym's overridden dh_strip doesn't work like that. [00:44] I wonder if it would work if you used dh_strip.pkg-create-dbgsym (the actual debhelper version) instead. [00:45] wgrant: huh, I can't find that command [00:47] Quintasan: It only exists when pkg-create-dbgsym is installed. [00:47] pkg-create-dbgsym diverts the original dh_strip. [00:47] wgrant: I should add that to build-depends as well? [00:48] Quintasan: It's already installed in the buildd chroots, so there's no point. Perhaps get debian/rules to call dh_strip.pkg-create-dbgsym if it exists, but otherwise call plain dh_strip. [00:48] Of course, this may not work at all :) [00:49] wgrant: well, I'll try that, thanks. Better this than nightly builds with no dbg libs [00:49] :S [00:49] Well, you could have a convenient checkbox on the PPA page in a month, if all goes well. [00:50] oh, month is a looong time [00:50] I think I will get the builds ready by then [00:57] wgrant: if priority never changes on a build and the queue stays full - what are the changes of me waiting for days to get the amd64 versions built? [01:00] lamont: Why does i386 have so many builders, and amd64 so few? [01:01] luck of the draw, pretty much [01:01] lamont: Can I remove the slave's architecture and just make it believe the master, so this can be fixed by clicking a couple of buttons in LP? [01:02] once you fix LP so that the buildd uses the LP answer as gospel, instead of having its own hardcoded copy of the answer.... [01:02] there's a bug about that [01:02] I've been waiting about 9 hours now for a build that will just be superceded right away - It wouldn't bother me if I had some indication that it'll eventually get there - like the priority going up. [01:03] wgrant: that is, we have some buildds that could do amd64/i386/lpia, and some that can do i386/lpia [01:04] lamont: I have a branch to do that... I should get it merged. [01:07] so no lp staff showed up yet? [01:08] bp0: how so? [01:08] help contact i guess it is called [01:08] i was told there would be one here at 4 [01:08] but it is 7 now [01:08] bp0: I replied to you not two second after you left the channel :( [01:09] 08:42:01 -!- bp0 [~bp@unaffiliated/bp0] has quit [Quit: Leaving] [01:09] 08:42:03 < wgrant> bp0: The Launchpad developers are all in Prague at the moment, so there won't be anyone around right now. [01:09] What's the issue that you're having? [01:09] heh [01:09] alright [01:09] i was trying to post a bug and it times out [01:09] always [01:09] not possible to post bugs [01:09] Against Ubuntu, or something else? [01:10] against gnome-control-center [01:10] In Ubuntu? [01:10] package in Ubuntu [01:10] Right. [01:10] Try using a shorter summary to start with. Once it gives you the list of duplicates, you can put the whole summary back in. [01:11] That may work around it. [01:11] But I haven't seen this issue for quite some time. [01:11] bp0: any reason apport won't work? [01:12] wgrant: if a project is private, should anyone be able to pull the bzr branches? [01:12] or better yet.. see the branches [01:12] MTecknology: There's no such thing as a private project (yet). Projects can have private branches, however. [01:12] i dont use apport [01:13] bp0: Why not? [01:13] wgrant: how do you set a branch to be private? [01:13] I don't like it [01:13] MTecknology: You need an admin to do it, or to configure your project to have private branches by default. [01:13] bp0: You need a very good reason to not use it. [01:13] wgrant: I thought if you did the commercial thing then anything in the project was private [01:13] It is the way Ubuntu bugs are meant to be filed. [01:14] wgrant: thanks for the info - definitely an oversight on my part [01:14] wgrant: and I suppose you can't do it for me? [01:15] MTecknology: I've no special privileges, no. [01:16] filing a bug in launchpad is straightforward, apport uses mystical questions that are never accurate enough, its always guessing, and then it attaches unnecessary information [01:16] not liking it is a good reason. [01:17] bp0: there are (probably) millions of bugs in the database for the ubuntu project. When you're filing a bug it searches through every one of those to find a duplicate. [01:17] bp0: The questions are there for a reason. [01:18] launchpad also tries to do that, but it always times out [01:18] wgrant: I still wish I was smart enough to get that pretty white hat.. [01:18] well not always, i've seen it happen once or twice [01:18] that it gives a list of possible duplicates === fta_ is now known as fta === fta_ is now known as fta === yofel_ is now known as yofel === fta_ is now known as fta [03:08] bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/~exarkun/pyopenssl/trusted/". [03:08] I reckon it is though. [03:08] It was a few minutes ago at least. [03:09] Oh no. My mistake. In my haste to complain about launchpad bugs I missed the extra "ed" on the end. It really isn't a branch. My apologies. === fta_ is now known as fta [04:19] what do I need to do to make a branch private? [04:19] mtaylor: Is your project set up for them? [04:20] wgrant: it's set up as non-free and has a payment voucher applied to it [04:20] wgrant: is there another step? [04:21] mtaylor: An admin needs to set up a branch privacy policy. [04:21] I'm not sure if that's done normally. [04:21] ah. lovely. probably my bad for not pinging someone then - I thought it was automatic [04:22] wgrant: should I file a question? [04:22] spm: What's the process for this? === fta_ is now known as fta === lifeless_ is now known as lifeless [05:06] mtaylor: wgrant: it's usually done automatically (manually, but) as part of getting a commerical whatsit [05:06] spm: can you fix PPA builders? [05:07] maybe... [05:07] spm: https://edge.launchpad.net/builders/shipova [05:08] woo. no, can't fix that. aiui, that needs a serious h/w level power stab [05:11] micahg: however, I can ask someone who can stab. that should be happening RSN. :-) [05:11] spm: thanks :) [05:11] spm: It should resolve itself if you disable it, let buildd-manager run through a whole iteration (normally a few seconds, but currently several minutes), then reenable it. [05:12] Since that will fire the reset trigger. [05:12] wgrant: really? that's worth a try. [05:12] Indeed. I think it's worth a test, if it means you don't have to poke GSAs as much in future... [05:14] for sure! [05:15] wgrant: hrm. is 'disabled' == to Not builder state ok, or Not Active? I assume the former. [05:15] spm: The former. Unchecking 'active' just hides it from the listings. [05:15] heh, I thought so, but... well.. this *is* soyuz. :-) [05:16] I will be interested to see if this works. It depends on how badly the builder is wedged. There's a case or two that won't work yet. === fta_ is now known as fta [05:26] spm: You can try flipping it back on now, since buildd-manager has finished with it. [05:26] We are up to >11min cycles :/ [05:26] heh, was just about to - we're tailing the log in great interest :-) [05:27] Ah, yes, that capability could be handy. [05:27] I've found it so, now and then. :-D [05:27] So, it should be trying to abort the build now. [05:27] That might work. [05:28] Oh, well, when it gets around to that builder again, I guess... [05:28] 10-15 minutes. :-) [05:28] Only 180 times slower than it's meant to be :) [05:32] is there any value in restarting the buildd-manager? or is the problem elsewhere in some way shape or form? [05:33] No point doing that. It'll just start the cycle from the start again. [05:33] bleh. [05:40] spm: so... [05:49] 010-07-13 05:45:06+0100 [-] Builder 'shipova' rescued from '7fc224047f7daec3ad6ec408fd4e039814fe2665': 'No job assigned to builder' \o/ [05:50] spm: awesome, thanks [05:50] spm: It remains to be seen whether the builder will respond. [05:50] But it was responding to queries before, so there's a good chance it will. [05:51] We really should make it hit the reset trigger when aborting a virtual build, but the architecture makes that somewhat difficult :/ === fta_ is now known as fta === fta_ is now known as fta === Ursinha is now known as Ursinha-afk [08:00] Launchpad should set the status of a bug to 'fix committed' once it is fixed in the devel focus branch. Opinions? === Ursinha-afk is now known as Ursinha [08:25] bilalakhtar: it depends :) [08:27] spiv: Atleast, there should be an option for project maintainers to enable such a feature [08:28] That would be nice. === fta_ is now known as fta === Meths_ is now known as Meths [12:09] Hey guys, I've tried multiple times, but gpg is reports errors every time I try to decrypt the validation email sent to me. I'm on Maverick atm. [12:09] At the moment, the error is: gpg: CRC error; 89342B - DC3893 [12:09] gpg: quoted printable character in armour - probably a buggy MTA has been used [12:12] Just tried revalidating, now the error is "gpg: malformed CRC. gpg: quoted printable character in armour - probably a buggy MTA has been used" [12:13] malcolmci: How are you decrypting it? [12:13] It's being sent to my Gmail address, from which I'm selecting "Show Original" (text version), then copying the text from and including ----BEGIN to ---END into a text file using gedit, then running "gpg --decrypt test.txt" [12:14] Does "Show Original" show the message source? [12:14] You shouldn't be using the source. You should be using the text in the message itself. [12:14] It just shows the text version of the email, so yeah headers and all [12:15] no, it's not showing markup if that's what you mean [12:15] There is HTML markup, since it is a text message. [12:16] But the source is an encoded version of the text. === Ursinha is now known as Ursinha-afk [12:18] OK, that's strange. Didn't know about that behaviour. Copied the text from directly from the email this time, now gpg is telling me 'You need a passphrase to unlock the secret key for..' [12:18] oh wait sorry [12:18] didn't notice the prompt [12:18] Thanks wgrant :) [12:43] do the buildds support the "[linux-any]" limitation in the build-dependencies? [12:47] I saw discussion of that on debian-devel last week. I suspect not. [12:47] I meant to check. [12:47] * wgrant tries acpid. [12:48] wgrant: when I read http://launchpadlibrarian.net/51835076/buildlog_ubuntu-maverick-amd64.glib2.0_2.25.11-1ubuntu1_FAILEDTOBUILD.txt.gz correctly, the buildds don't support it [12:49] geser: dpkg-checkbuilddeps: Unmet build dependencies: libselinux1-dev [12:49] That doesn't look related... [12:49] libselinux1-dev [linux-any], [12:49] Oh, right. [12:50] but the buildd installs "libgamin-dev [!linux-any]" from some reason [12:50] does it believe it is !linux-any? [12:50] It is. [12:50] It's far too old. [12:50] Both Soyuz and launchpad-buildd need support. [12:50] unstable's acpid source is not uploadable. [12:50] (it's Architecture field is linux-any) [12:54] do you know if there is a bug for it? Didn't see one on launchpad-buildd (or soyuz) [12:54] There's no bug, no. === fta_ is now known as fta [12:55] * geser files one [12:56] It needs two. [12:56] One for Soyuz, one for lp-buildd. They're different issues. [13:00] bug #604981 for the lp-buildd issue [13:00] Launchpad bug 604981 in Launchpad Auto Build System "The buildd doesn't support [linux-any] in build dependencies (affected: 1, heat: 6)" [Undecided,New] https://launchpad.net/bugs/604981 [13:01] what's the soyuz issue? I'd file a bug if I'd know the problem [13:02] geser: Some sources (like unstable's acpid) are 'Architecture: linux-any' === Ursinha-afk is now known as Ursinha [13:15] geser: At least the sbuild side should be pretty trivial. === fta_ is now known as fta [13:49] I think there's a bug in the LP Login [13:50] I can't log in at all [13:52] I can log into login.launchpad.net but can't get from there to launchpad.net [13:55] I really hate Perl. [13:55] then replace it with Python [13:55] It's sbuild :( [14:03] wgrant: bug #605002 for the soyuz issue [14:03] Launchpad bug 605002 in Soyuz "Soyuz doesn't accept upload with "Architecture: linux-any" (affected: 1, heat: 6)" [Undecided,New] https://launchpad.net/bugs/605002 [14:04] geser: Thanks. [14:22] So.. I have a project with private branches. I'm not able to push to those branches anymore. I'm told 'You can't create branches in "~team/project" [14:25] I'm in the team that owns the project.. I should be able to push to it.. right? [14:36] need help from launchpad team, i have private branch that doesn't work, it's well known bug i already had in the past, you need to fix it manually [14:36] we already did that fix in the past [14:41] alopenerp: what's your issue with the private branches? [14:42] impossible to create private branches [14:42] they are public, it's a known bug [14:42] any link to the bug report? I'm having that issue too [14:42] i have two project one that works one that doesn't [14:43] I'm trying to push a new (private) branch to a project, my first time [14:43] loook it should display this [14:44] https://code.launchpad.net/openerp-security [14:44] New branches you create for OpenERP Security are private initially. [14:44] if it doesn't it need manual fix from launchpad team [14:44] https://code.launchpad.net/openerp-int here it doesn't [14:48] MTecknology: what is your project name ? [14:48] alopenerp: sounds like we're both having issues at the wort possible time. LP guys are busy with a summit I think. [14:48] alopenerp: https://code.launchpad.net/kalliki [14:48] alopenerp: when I try to create a new private branch I get told I'm not allowed to [14:49] danilos: did you come here to help us out? [14:49] You don't have the notice at the top it wont work, same bug [14:50] look this one is ok https://code.launchpad.net/openerp-security [14:50] cause it has the notice on top [14:50] see that ? [14:50] we already had the problem in the past, but they fixed here from here [14:50] alopenerp: I don't see any notice like that [14:51] http://dpaste.com/217688/ [14:54] MTecknology: ah then you only see it when loggued [14:55] MTecknology: but you should see such a notice on your own project page [14:55] alopenerp: alrighty, I'm sure someone will be around to help us soon :) [14:56] depending on various definitions of soon :P [14:56] MTecknology: :) [15:00] * alopenerp a few centuries later... [15:08] MTecknology, I didn't, but I can try :) [15:08] MTecknology, what is the problem you are having? [15:09] MTecknology, (we are all together in a big room having a meeting, but I am sure I can find someone who can help you if I can't :) === fta_ is now known as fta [15:26] danilos: I can't push to a private branch [15:26] danilos: alopenerp was having the same issue - she said there's supposed to be a notice about branches being pushed being private ont eh code.lp.net/project page [15:27] abentley, rockstar, thumper: hey, can you guys help MTecknology and alopenerp? [15:28] danilos: thanks, I actually only bugged you because you came in with a LP hostmask :P [15:28] MTecknology, not to worry :) [15:29] MTecknology: which branch, and what is your lp id? [15:29] thumper: I'm trying to push new branches to https://code.edge.launchpad.net/kalliki - my id is MTecknology [15:32] thumper: The branches were just made private by default yesterday [15:34] wow... Start 2010-07-14 (2505) [15:34] MTecknology: I can see why [15:34] thumper: did I break something? [15:34] MTecknology: who should be able to push branches for kalliki [15:34] MTecknology: no it wasn't you :) [15:34] MTecknology: the policy hasn't been set up right [15:34] thumper: anyone in the ~kalliki team [15:34] oh [15:35] MTecknology: done now [15:35] thumper: Yay :) - thanks [15:35] np [15:36] thumper: was it setup for just me to be able to - but then I couldn't either because i wasn't part of the team? [15:36] MTecknology: just not set up properly [15:36] ok [15:36] you don't want to know the details :) [15:36] alrighty :P [15:37] thumper: is it possible to also have blueprints and answers kept private or how does that work? [15:37] MTecknology: not yet [15:37] thumper: ok- thanks [15:37] thumper: you say alopenerp having the same issue? [15:38] MTecknology: was it for the same project? [15:39] no it was for https://code.launchpad.net/openerp-security i think [15:40] thumper: oh.. I was also going to ask - I thought it was possible for PPA builds to get a little extra priority for projects that are being paid for - am I wrong about that? [15:40] it's possible [15:41] we just don't have a policy [15:41] oh, I thought I read something about that in the build queue wiki [15:43] 36 hours is a long time for a build queue... [15:44] I take it the builders that weren't building yesterday were taken offlline [15:44] Someone needs to throw some of the i386 builders back onto amd64. [15:44] Oh, all the builders are gone now. [15:45] MTecknology: are you involved with the openerp projects? [15:45] thumper: no, that person just came in here with the same problem shortly after me [15:45] * thumper nods [15:45] ok [15:46] wgrant: my package will take less than 10min to build once it starts building :P [15:46] wgrant: the good news is that they're keeping full - there's no builders just sitting idle for long [15:47] except for the two armel [15:48] thumper: "Building private source" - That's what I was thinking of. I'm guessing a private ppa costs either more money - or needs to have a specific reason? [15:48] MTecknology: I don't really know, but I didn't think so [15:49] * thumper looks at bigjools [15:49] bigjools: :) [15:50] * bigjools speaks to thumper in person [15:51] MTecknology: if you have the private voucher thingy, you can have a private ppa [15:51] btw we're down on builders temporarily [15:51] MTecknology: you need to make a ppa and before you upload anything, we have a losa mark it private [15:51] or me :) [15:51] bigjools: any chance you could do that for me? [15:51] sure [15:51] I'll make one for this quick [15:52] once private, always private BTW [15:52] you can't switch gto [15:52] argh [15:52] you can't switch to public [15:53] bigjools: alrighty - I just made a ppa for private specifically - https://edge.launchpad.net/~kalliki/+archive/internal [15:54] MTecknology: ok it's private now [15:55] bigjools: thanks :D [15:55] This is an exciting day for me :P [15:55] I no longer need to try to manage our own code and bug server [16:04] bigjools, hi [16:05] hello [16:05] bigjools, is it possible to remove old build in the ppa system, like this one https://edge.launchpad.net/~mono-testing/+archive/ppa/+build/1516923 [16:06] bigjools, in this current builders-situation they are very annoying and it seems there are several build like these present which are over one year old [16:07] one year? [16:07] bigjools, this build was published on 2009-05-31 [16:08] bigjools, https://edge.launchpad.net/~mono-testing/+archive/ppa/+packages [16:08] hmmm interesting [16:08] and seems to be building over and over again [16:08] ah [16:09] there are more like this [16:09] It's not depwaiting on debhelper 7, is it? [16:09] Lots are doing that. [16:09] yes, it is [16:10] so builds like these should be marked failed or something to stop this [16:10] Well, we should fix the bug that causes them to be retried every hour. [16:11] indeed [16:11] they're not supposed to get dispatched until deps are met [16:11] Basically, debhelper 7 is in hardy-backports. The retry script notices this, so tries to rebuild your package. [16:11] ah THT bug [16:11] But the script doesn't realise that your PPA doesn't use -backports. [16:11] Oh, sorry, I thought you knew it. [16:11] I did, I'd forgotten [16:12] grar [16:12] it is not my ppa, i just wanted to point out this thing which uses ressources [16:12] so what do we do when -backports is not available, leave it getting checked for dependencies forever? [16:12] bigjools: It retries every time the script runs. [16:12] when I fix the script I mean [16:13] Right. [16:13] it'll still get considered [16:13] It will. [16:13] Along with lots of other stuff. [16:13] Until the series goes obsolete, I guess, although I'm not sure that even that's excluded at the moment. [16:14] someone can't have noticed that it's waiting for a year now [16:14] There are quite a few builds around like it. [16:14] wgrant, just curious, how many? [16:14] I could change the script so that if it's been depwaiting for > N days, then kill it [16:15] bigjools: If you do that to the primary archive, people will be most displeased. [16:15] how big does N need to be? [16:15] surely it's not infinite, even for Ubuntu [16:15] I don't know. I'd first be checking if it's actually a performance issue yet. [16:16] 30 days? [16:16] We can obviously exclude obsolete series for primary and PPAs, and non-development Release pockets for primary archives. I'm not sure if either of those are in place at the moment. [16:16] You guys know of anything that could teach me python in a retardedly simple and easy way? [16:17] Ah, so it already skips obsolete series. [16:17] bigjools: Is it really slow? [16:17] MTecknology: google diveintopython [16:18] wgrant: yes, it hammers the DB every hour [16:18] which makes all of LP slower [16:18] I shifted a load of the queries onto slaves. but still ... [16:19] How many builds are there that it considers each time? [16:19] sh^Wa lot [16:19] It currently materialises a whole lot of extra stuff, since it doesn't exclude Release pockets in the initial query. [16:19] indeed [16:20] bigjools: thanks :) [16:21] too much stuff to fix, not enough lifetimes to do it in [16:22] bigjools: indeed, for rund 2 I think I'm going to take it easy :P [16:22] when you know Python, come and fix some Soyuz bugs :) [16:23] Yes, JOIN US! [16:23] [16:24] * StevenK belts wgrant with the Free Software song [16:24] Also known as "Assilimation doesn't hurt a bit ... *twitch*" [16:25] bigjools: I've been wanting to help with LP dev [16:26] I also need to learn a little bit of C to finially finish another year lkong project - it's beeno no the back burner about 11mo [16:26] StevenK: Ow. [16:28] wgrant: Which bit? :-) [16:28] StevenK: D) All of the above. [16:31] You guys use vim/emacs for writing python or something else? [16:32] Vim! [16:33] MTecknology: Both, mostly vim [16:33] wgrant: any special plugins that make it easier or not so much? [16:33] https://dev.launchpad.net/UltimateVimPythonSetup [16:34] yay === mpt_ is now known as mpt [16:38] * bigjools chuckles at StevenK's mis-spelling [16:39] wgrant: are you using the vim pyflakes plugin? [16:39] bigjools: No. Where's that? [16:40] wgrant: on vim.org [16:40] it's the best plugin I have for vim [16:40] I've yet to actually us a vim plugin.. [16:40] Hmm I need someone to witness a bug [16:40] https://launchpad.net/gcc-linaro/4.4 [16:40] in 4+ years of using it :P [16:40] See the milestones [16:40] The same milestones is listed twice, instead of listing the two milestones we have [16:41] I fear this is a cache issue [16:41] I see -0 and -1. [16:41] So yes, probably caching. [16:41] lool: heh.. I've seen this too - and it was cache [16:41] MTecknology: I started with vi, 21 years ago. :o [16:41] bigjools: I was 1 then [16:41] lool: Looks perfectly fine to me? [16:42] bigjools: Your vi skills are older than me :( [16:42] In the list of milestones below [16:42] Not in the graph [16:42] lol [16:42] Milestones and releases section [16:42] I see the -0 one twice [16:42] after reloading as hard as I can [16:42] but not with w3m, sigh [16:43] i guess i've been using emacs for about 2/5ths of my life now [16:43] lool: ya... I would file a bug at least, I've seen that before - it's not just firefox - anything thata caches has that issue [16:47] LP #605061 [16:47] Launchpad bug 605061 in Launchpad itself "Wrong cached milestone information (affected: 1, heat: 6)" [Undecided,New] https://launchpad.net/bugs/605061 [16:57] Night all. === beuno is now known as beuno-lunch [17:15] I'm working with Bazaar on Launchpad and was wondering how the branch, change, commit, merge process goes? Currently I am pulling from the branch, working on it, then pushing it back, is this 'best practice'? [17:18] wgrant: http://www.vim.org/scripts/script.php?script_id=2441 (pyflakes.vim) [17:21] JoshBrown: depends [17:21] JoshBrown: is it just you? if so, that's probably fine... if you're aiming on working with a team of folks there are some other ways you can address this? [17:28] mtaylor: I'm working in a small team ( lp:codemonkey ), what's wrong with this method for a team? === warp10 is now known as warp10-captato === fta_ is now known as fta === beuno-lunch is now known as beuno === fta_ is now known as fta === fta_ is now known as fta [18:44] https://code.edge.launchpad.net/~vcs-imports/kdelibs/kde4 << can someone help with that ? [18:45] the import fails for some reason [18:59] james_w: I have asked about this earlied but I can't remember why it is like this. I'm using {revno} in my recipe, the directory name still contains {revno} but the tar.gz is created with proper revision number, I can't do source format 3.0 like this. Is there a known workaround for this or I have to manually copy it and create a .orig.tar.bz2? [18:59] Quintasan: source format 3.0 (quilt)? [19:00] yes [19:01] james_w: ^ [19:02] Quintasan: bzr-builder only supports native packages currently, so I don't think you can do it === Ursinha is now known as Ursinha-afk [19:03] there's a typo in the "Subscribe someone else" button, move your cursor on it (without clicking it) and you will see "Launchpad will email that person whenever this bugs changes", s/bugs/bug === fta_ is now known as fta [19:38] any here from the lanuchpad support team ? [19:41] alopenerp, what's up? [19:42] i need somebody from launchpad team to fix my project, it's a known bug and we already ahd it in the past, it's a paid propritary project, and there no way to create a private branch, i know that you have to tweak something to make it work [19:43] bac, you around? [19:43] project https://launchpad.net/openerp-int doesn't work, i also have https://code.launchpad.net/openerp-security this one work, you see the difference, there are no notice on the code page [19:44] alopenerp, the launchpad team is having a team-wide sprint at the moment [19:44] both are paid, https://code.launchpad.net/openerp-security you see a notice about private branches, https://code.launchpad.net/openerp-int no notices [19:45] let me see if I can find someone who knows about this subject [19:45] otherwise I'll have to deflect you to a support email [19:45] beuno: i know but it is supposed to have somebody on duty for such kind of problem [19:45] beuno: they say that irc is preferred over email [19:45] right, except for the one week a year they all sprint [19:45] but, hold on a minute [19:46] flacoste, ^ [19:46] beuno: ok i can send a mail [19:46] last time they fixed it from this channel [19:46] that's why i come here [19:46] alopenerp, let me see if I can find someone [19:46] beuno: thanks [19:47] beuno: are you part of that sprint ? [19:48] alopenerp, no, which is why it's taking me a little while :) [19:54] grr [19:54] Quintasan: hello are you from launchpad team ? [19:55] alopenerp: nope, but I'm angry at LP [19:55] :P [19:55] Quintasan: about ? [19:56] Quintasan: they are all busy with the summit right now [19:56] Quintasan: a launchpad sprint/summit happening this week [19:56] yes, I know that === MTeck is now known as MTecknology === fta_ is now known as fta === mm-mysql is now known as mark|autoconnect [20:33] hi all, trying to submit a bug, yesterday and today, but I get Timeout erros oll the time (Error ID: OOPS-1655A1315) [20:33] https://lp-oops.canonical.com/oops.py/?oopsid=1655A1315 [20:38] rduivenvoorde: try putting a shorter title initially [20:38] rduivenvoorde: you can change it once it's filed [20:38] ah, that's possible :-) I kind of trying to be a little verbose ... [20:39] some duplicate searches trigger bad performance in the query [20:52] alopenerp: you should be set-up now [21:02] flacoste: thanks this worked, additional question: how to add multiple files as attachment? [21:02] I see reports in which all files are in one comment, but I can just add one file per comment [21:06] flacoste thank you i hceck [21:09] rduivenvoorde: you can only add one attachment at a time through the web UI [21:09] rduivenvoorde: the web API can be used to bundle multiple files in a comment, but it's not exposed in the UI [21:09] the reports you see were likely filed through apport [21:09] which makes use of the underlying API [21:09] ah, clear [21:10] flacoste: You are not allowed to create branches in OpenERP-int [21:11] flacoste: tried from web, and bzr push [21:15] flacoste: even worse than before because we could create branche althought only public ones :) [21:16] hi beuno [21:16] hola bac [21:17] hi beuno! make it quick the hotel internet is crap [21:17] bac, it's all taken care of [21:17] so thank you [21:17] bac: can you fix my private branch problem ? [21:17] beuno: ok. [21:18] alopenerp: perhaps. can you tell me what the problem is/ [21:18] bac: both are paid, https://code.launchpad.net/openerp-security you see a notice about private branches, https://code.launchpad.net/openerp-int no notices [21:18] bac: impossible to create private branches in openerp-int [21:18] bac: openerp-int was paid recently (2 weeks ago or something) [21:19] bac: last time we had a paid project we also had a problem and it was fixed from here [21:23] bac: mbarnett is on the issue [21:23] mbarnett: both are now Private only [21:23] bac, alopenerp: both projects are now Private branches only [21:23] alopenerp: that's how openerp-security is setup [21:23] alopenerp: do you want to be able to create public branches on openerp-int? [21:24] flacoste nope i want to push a private branch [21:25] alopenerp: do you want only to push private branches? [21:25] flacoste: yes bzr push bzr+ssh://bazaar.launchpad.net/~openerp-dev/openerp-int/test [21:25] flacoste: gives: [21:25] flacoste: bzr: ERROR: Permission denied: "~openerp-dev/openerp-int/test/": : You cannot create branches in "~openerp-dev/openerp-int" [21:25] alopenerp: that i get [21:26] my question is do you want to be able to create public branches in addition to private branches on that project [21:26] now it's setup for Private only [21:26] flacoste that's ok [21:26] we need to investigate why you are denied permission [21:26] flacoste we have many other projects for public branches [21:26] flacoste: thanks [21:26] gnight [21:26] makes sense [21:27] good night lifeless [21:27] flacoste: most of our work is publis only a small subset must be private, that's why we need openerp-int for internal stuff [21:38] hi alopenerp [21:39] bac: hi [22:08] *blink* [22:08] wow [22:08] 11 active mercurial code imports, 499 active git code imports === Ursinha-afk is now known as Ursinha [22:15] what's the difference between those two merge requests: https://code.launchpad.net/~lfaraone/ubuntu/maverick/memtest86+/4.10-1ubuntu1/+merge/28594 and https://code.launchpad.net/~serge-hallyn/ubuntu/lucid/qemu-kvm/memleak-fix/+merge/28645 [22:16] i can change the status for the first one, but not for the second one. I am member of the ubuntu-sponsors team [22:21] alopenerp: heya, so, you can't create branches against openerp-int? [22:22] mbarnett, is this maybe a project vs a project group thing? [22:23] I *think* you can't create branches in project groups [22:23] flacoste or sinzui would know [22:27] beuno: no, that's not related [23:02] This has been in the build queue for 15 hours how... [23:02] now* [23:04] And only 3 hours to go.... which is what it said this morning... [23:04] what the heck is going on? [23:04] oh.. priority is STILL only 2505 - it's supposed to increase as it sits in the queue ?? [23:21] mbarnett: fixe by bac [23:21] mbarnett: fixed by bac [23:21] alopenerp: did he subscribe the correct teams to the project? [23:21] mbarnett: beuno; it's now working, bac did the manual setup [23:22] excellent [23:22] mbarnett: yes i tested it ~openerp-dev and ~openerp [23:22] perfect. [23:22] mbarnett: thank you for worrying about me :) [23:22] heh, np [23:23] alopenerp, we all worry about you! === Ursinha is now known as Ursinha-afk