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