[00:01]  * mwhudson afk for a couple of hours (but working, at least a bit)
[00:03] <lifeless> hi thumper
[00:04] <lifeless> solved world peave yet?
[00:24] <masom> Hi, any tips or howto properly setup launchpad for a local use (non-hosted)? It kinda runs fine with the debug branch but is there anything that should be modified to have a ... let say not devel launchpad instance?
[00:35] <intellectronica> masom: there isn't really any reason to run launchpad in any capacity other than for development, so nobody puts any effort into that
[00:36] <masom> intellectronica: thats what i figured out since nobody made a howto on how to host it by himself.
[00:36] <masom> intellectronica: but technically, from dev to "production", the main changes are in the config files?
[00:36] <masom> intellectronica: (such as the ability to actually send outbound emails)
[00:38] <intellectronica> masom: the production environment for launchpad is a _very_ complex affair (consider that there are several administrators and engineers working full-time just to keep launchpad.net going). it's the configuration and a setup of quite a few machines and many running processes
[00:39] <intellectronica> masom: it's not impossible to replicate it if you're willing to commit the same resources, but it would seem a pointless exercise, given that launchpad.net is already there for you to use, and that you can help develop it, it being free software
[00:40] <masom> intellectronica: yeah, i understand that :) But it's just for the kick of actually having it running as the real deal. If nobody outside canonical is able to reproduce it, its dangerous.
[00:41] <intellectronica> masom: there's nothing stopping you from running 'the real deal'. many people run it locally for development, and it's essentially the same software
[00:42] <masom> intellectronica: yeah thats what i figured out when it launched locally, i just wanted to poke around to know how hard it would be to make the devel react like the launchpad.net deployment. And i'm glad that it looks like its mostly config files to modify.
[01:28] <lifeless> does anyone else find that malone bug pages run _very_ slowly once you have 30 to 40 open?
[01:28] <lifeless> just typing in the comment field feels like molasses
[02:02] <masom>  mmm stupid question, what would trigger this: lazr.config.interfaces.ConfigErrors: ConfigErrors: launchpad does not have a localhost http key. ?
[03:01] <masom> Oh also a very weird thing
[03:02] <masom> make run_all with a differnt host (let say dev.local instead of dev), apache tries to connecto port 8086, moving apache to proxy 8085 works, any reason why it's attempting to use 8086 ?
[03:14] <lifeless> any new on the red border problem?
[03:17] <lifeless> [6 edits so far on this bug summary :(]
[06:58] <al-maisan> Good morning
[09:02] <thumper> hi hi
[09:04] <mrevell> hi
[09:07] <thumper> mrevell: dude, you're across the table!
[09:07] <mrevell> :)
[09:19] <jtv> spm: system reboot, distractions...  I think we'll have to let the jp weirdness lie for the moment.
[09:19] <spm> jtv: :-) oki
[09:21] <jtv> spm: thanks though!
[09:23] <spm> jtv: anytime* (* subject to core hours, laptop availability and other terms & conditions. please see your contract)
[09:24] <jtv> spm: would that be the contract kept in the data centre managed by you untrustw^^^NO CARRIER
[09:24]  * spm returns the lart to it's place of rest
[09:24]  * jtv hates to think what place that is
[09:27] <spm> pile of shrunken pc's from devs that were .... larted
[11:41] <stub> >>> None < 44
[11:41] <stub> True
[11:41] <stub> Grrr...
[11:41] <lifeless> \o/
[13:22] <thumper> stub: ping
[13:22] <stub> thumper: pong
[13:23] <thumper> stub: it seems we are *still* missing a db permission https://lp-oops.canonical.com/oops.py/?oopsid=1368BM2
[13:23] <thumper> stub: I thought it was fixed
[13:23] <thumper> stub: can you add it to your pending branch and fix on production?
[13:24] <stub> We granted select permissions. looks like it is trying to update.
[13:24] <stub> (?)
[13:25] <stub> no....
[13:25] <thumper> huh?
[13:25] <thumper> outgoing email shouldn't update anything
[13:25] <stub> thumper: Is this the branchscanner?
[13:26] <thumper> stub: no this is the revision email sending script
[13:26] <stub> thumper: What db user does it connect as?
[13:26]  * thumper looks
[13:27] <thumper> send-branch-mail
[13:27] <stub> send-branch-mail?
[13:27] <thumper> yes
[13:28] <maxb> What bit of LP actually requires memcached? "make run" seems happy without
[13:28] <thumper> maxb: nothing just yet
[13:28] <stub> chicken/egg
[13:30] <stub> thumper: perms granted on production. Updating my branch now.
[13:31] <thumper> stub: thanks
[13:45] <poolie> thumper: http://bazaar-vcs.org/SmartPushAnalysis1.4
[13:45] <poolie> sudo tc qdisc add dev lo root netem delay 500ms
[13:45] <poolie> go on, paste in sudo commands from irc :)
[13:45] <poolie> you know it makes sense
[14:51] <Fly-Man-> Who handles the bugs related to the source pulls?
[14:54] <spiv> Fly-Man-: https://bugs.launchpad.net/launchpad-code
[14:55] <Fly-Man-> spiv: Is that also the place for this bug: rocketsetup has wrong keyserver mentioned ?
[14:55] <spiv> Just file a bug on the launchpad project for that, IIRC.
[14:55] <Fly-Man-> spiv: Already did
[14:56] <barry> reviewers and lurkers -> #launchpad-meeting in 4m
[15:06] <stub> How to I get the launchpad-developers-dependencies package rebuilt? I got a change landed to the branch meta-lp-deps branch but from there I am clueless.
[15:15] <Fly-Man-> ./rocketfuel-setup: line 372: 19632 Segmentation fault      bzr branch http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/ $LP_TRUNK_NAME
[15:15] <Fly-Man-> ERROR: Unable to create local copy of Rocketfuel trunk
[15:27] <Fly-Man-> Anyone want to elaborate on that one ?
[15:28] <Fly-Man-> This keeps happening over and over again with the bzr 2.0.0.1 from the ppa
[15:28] <barry> Fly-Man-: i've never seen that before.  can you gdb the core file and see what it says?
[15:29] <Fly-Man-> gdb-python or gdb itself ?
[15:29] <barry> Fly-Man-: gdb i'm not sure what gdb-python is
[15:29] <Fly-Man-> python variant
[15:30] <Fly-Man-> Any command lines I need to add ?
[15:30] <barry> Fly-Man-: actually, start with 'file core'
[15:31] <Fly-Man-> file core ?
[15:32] <barry> Fly-Man-: that will tell you which binary is crashing, though i'm going to bet it's python.  and if that's the case, it's almost certainly a bug in some bzr extension
[15:32] <barry> Fly-Man-: what platform are you on?
[15:32] <Fly-Man-> Vmware Jaunty 2 Gb mem, 15 Gb hard drive
[15:33] <barry> Fly-Man-: i'm on karmic now and bzr 2.1.0dev.  i'm having other problems but dumping core isn't one of them ;)
[15:34] <maxb> Random question: what exactly is rocketfuel? Is it just a cute name for devel?
[15:34] <barry> Fly-Man-: try running that bzr command manually at the shell and see what happens
[15:35] <Fly-Man-> maxb: it's the script that installs the devel branch on a machne and setup the dependencies
[15:35] <barry> maxb: basically yes.  it's historical
[15:36] <barry> maxb: the branch used to be called rocketfuel (get it, launchpad... rocketfuel... soyuz... there's a theme :) but the only traces now are in the setup scripts
 Who handles the bugs related to the source pulls?
[15:37] <maxb> Fly-Man-: In general, people don't handle bugs (on any open source project). Groups of people pick up various bugs depending on their availability. Hence the use of bug trackers. :-)
[15:43] <Fly-Man-> maxb: true
[15:46] <Fly-Man-> maxb:that's why ppl always are impatient when a bug is still not fixed ;)
[15:49] <maxb> stub: You build the package in the normal way of working with Debian source packages and upload it to the launchpad PPA. (Or, if you like, I'll do it and find someone in ~launchpad to copy it there)
[15:50] <stub> Given I don't know where to start with working with Debian source packages, you or someone who understands had better do that part.
[15:56] <maxb> stub: I'm afraid trunk doesn't build - the trailer line on your changelog entry is malformed
[15:56] <jtv> abentley: looking into the workaround for the branch commits... whaddya think, should I do it right there in DirectBranchCommits?  Or in the script that calls it, and add a check in DBC?
[15:56] <jtv> abentley: The advantage of the latter is that the branch conversion may take a while, and it's polite to keep it in a separate transaction
[15:56] <maxb> stub: There must be two spaces between the email and the date, and the date format must exactly match the format demonstrated in other changelog entries
[15:56] <abentley> jtv: Do what?  Convert to unstacked?
[15:57] <jtv> abentley: right
[15:59] <stub> maxb: fixed
[15:59] <abentley> jtv: I would do it in the script that calls it.  I'm not really happy with converting to unstacked, though.
[16:00] <jtv> abentley: I'm not completely happy about it either, but I think it beats alternatives like reverting to regular branch/commit/push or putting the burden on the user.
[16:00] <maxb> stub: not fixed - must be day month year, not month day year
[16:02] <stub> maxb: and again?
[16:09] <maxb> stub: that's good, built source, uploaded to ~maxb/+archive/launchpad, waiting for process-upload and build
[16:10] <stub> ta
[16:13] <Fly-Man-> barry: Strangely when I try it with the command line, it doesn't fail so far ...
[16:27] <barry> Fly-Man-: very weird!
[16:43] <jtv> abentley: I don't suppose you guys have a helper function to say whether a branch is stacked?
[16:45] <abentley> jtv: That information is stored in the database, and can be easily retrieved with bzrlib.
[16:45] <jtv> abentley: it turns out get_stacked_on_url is a very roundabout way of finding out.  :)
[16:46] <jtv> abentley: Branch.stacked_on is None, right?
[16:47] <abentley> jtv: Yes.
[17:01] <abentley> jtv: An alternative is to embrace "Easier to ask forgiveness than permission", and handle the exception generated by committing to a stacked branch.
[17:02] <jtv> abentley: wayyyy too much code for the "nothing's going on" case.  :)
[17:02] <jtv> I tried.
[17:05]  * Ursinha looks around for bugs people
[17:05] <Ursinha> intellectronica, hi :)
[17:05] <Ursinha> intellectronica, could you please set the importance on bug 439449?
[17:05] <mup> Bug #439449: On a bug, entering +edit page shows the wrong bug number <Launchpad Bugs:Triaged> <https://launchpad.net/bugs/439449>
[17:06] <Ursinha> thanks :)
[17:07] <intellectronica> Ursinha: done
[17:07] <Ursinha> intellectronica, thanks again
[17:07] <intellectronica> Ursinha: thanks for bringing this to my attention
[17:13] <Ursinha> intellectronica, no problem. I found this when trying to workaround bug 423924
[17:13] <mup> Bug #423924: Entity-body was not a well-formed JSON document when updating bug description <post-3-ui-cleanup> <Launchpad Bugs:Triaged by deryck> <https://launchpad.net/bugs/423924>
[17:37] <Fly-Man-> barry: It's stopping at the same place everytime
[17:53] <intellectronica> jtatum: rejoice, your patch has landed!
[17:53] <intellectronica> jtatum: thanks again for picking this up, you rock
[17:53] <jtatum> intellectronica: thank you very much! the celebrations have begun here in my lair. champagne for everyone.
[18:30] <ScriptRipper> hi kiko
[19:45] <Fly-Man-> barry: *ping*
[19:46] <barry> Fly-Man-: *ponngggggg!!!* :)
[19:46] <Fly-Man-> barry: What repo are you usin for 2.1
[19:46] <barry> Fly-Man-: bzr?
[19:46] <Fly-Man-> yes
[19:47] <barry> it's either:
[19:47] <barry> deb-src http://ppa.launchpad.net/bzr-beta-ppa/ubuntu karmic main
[19:47] <barry> deb http://ppa.launchpad.net/bzr-beta-ppa/ubuntu karmic main
[19:47] <barry>  
[19:47] <barry> or
[19:47] <barry> deb http://ppa.launchpad.net/bzr-nightly-ppa/ppa/ubuntu karmic main
[19:47] <barry> deb-src http://ppa.launchpad.net/bzr-nightly-ppa/ppa/ubuntu karmic main
[19:47] <barry>  
[19:47] <barry> probably the latter and i probably shouldn't be using the nightlies ;)
[19:50] <Fly-Man-> Let's see if that fixes the segmentation fault
[20:01] <Fly-Man-> barry: nope, same issue
[20:02] <Fly-Man-> wth is happening here
[20:02] <Fly-Man-> it worked with 1.16 and 1.18
[20:02] <Fly-Man-> then the ugrade to 2.x makes it shakey
[20:03] <barry> Fly-Man-: are you on a 64bit system perhaps? (i am tho and haven't seen this)
[20:03] <Fly-Man-> x86 machine
[20:03] <Fly-Man-> it's latest vmware
[20:03] <Fly-Man-> machine has 4 gb
[20:04] <barry> i can't imagine vmware has anything to do with it, but you never know
[20:04] <barry> Fly-Man-: you might ask around on #bzr though
[20:04] <Fly-Man-> They blamed the mem
[20:04] <Fly-Man-> the memory is brand new on that machine
[20:04] <Fly-Man-> build that machine 4 days ago
[20:05] <Fly-Man-> Hmm, and there's no tree where there's 1.18 bzr anymore ....
[20:22] <barry> i always get suspicious when the hardware is blamed.  so much more rare than a missing incref in my experience ;)
[20:44] <Fly-Man-> that's my idea as well
[20:44] <Fly-Man-> why would it work on 1.18
[20:44] <Fly-Man-> and not on 2.x
[20:46] <Fly-Man-> barry: Could you try something for me ?
[20:46] <Fly-Man-> Could you create a tarball from devel ?
[20:46] <Fly-Man-> or someone else
[20:47] <barry> Fly-Man-: why not try to grab the latest bzr trunk and build it from source?
[20:47] <Fly-Man-> I just pulled the nightlies
[20:47] <Fly-Man-> same segmentation fault
[20:47] <Fly-Man-> so it seems to be something in 2.x
[20:47] <Fly-Man-> which wasn't there in 1.18
[20:48] <barry> Fly-Man-: maybe abentley or rockstar knows?
[20:48] <Fly-Man-> Good idea, abentley , rockstar : Any ideas ?
[20:48] <rockstar> Fly-Man-, reading backchat
[20:48] <Fly-Man-> rockstar: Thanks
[20:50] <rockstar> Fly-Man-, the nightlies are working fine for me.  Upgraded just this morning.
[20:50] <Fly-Man-> rockstar: In short: I've been using Launchpad.dev for some time, until the latest release of the bzr 2.x. After that, during reinstalls the bzr just quits with a segmentation fault while trying to pull the latest
[20:52] <rockstar> Fly-Man-, what do you mean by "reinstalls" ?
[20:52] <Fly-Man-> rockstar: virtual machine reinstallations
[20:54] <Fly-Man-> Every 5 days I need to clean up Vmware machines
[20:54] <Fly-Man-> while the server is getting too burdened
[20:54] <Fly-Man-> so i cleaned up last Saturday
[20:54] <Fly-Man-> after that, it's a mess while trying to get the initial tree
[20:54] <rockstar> Fly-Man-, it might very well be "hardware" because VMware's memory is still software.
[20:55] <rockstar> Fly-Man-, I suggest branching bzr.dev, building the C extensions, and trying that.
[20:57] <Fly-Man-> rockstar: is there a trunk for that ?
[20:57] <rockstar> Fly-Man-, bzr.dev is trunk
[21:15] <Fly-Man-> rockstar: Same error
[21:15] <rockstar> Fly-Man-, try it outside a VM.
[21:16] <Fly-Man-> rockstar: I'll have a look when there's a machine available in the datacenter
[21:23] <Ursinha> hey cprov, are you there?
[21:25] <rockstar> barry, so, I think I'm the only one around for the AsiaPac reviewer meeting today.  Is it even worth having one?
[21:25] <barry> rockstar: probably not, the most meaningful thing we did in ameu was to wish cprov well :)
[21:26] <cprov> Ursinha: yup
[21:33] <Ursinha> cprov, hi :) can you help me with https://answers.edge.launchpad.net/launchpad/+question/84264, please?
[21:34] <cprov> Ursinha: sure, in a bit
[21:34] <Ursinha> thanks cprov
[21:47] <cprov> Ursinha: done
[21:52] <Ursinha> cprov, thanks :)
[21:57] <barry> bac: ping
[21:57] <bac> hi barry
[21:57] <barry> bac: hi, are you busy?
[21:57] <bac> barry: i'm always busy and productive.  but i have a few moments to spare.
[21:58] <barry> bac: ;) can we skype?
[21:58] <bac> sure
[21:58]  * bac launches
[21:58] <maxb> Thanks whoever copied launchpad-dependencies 0.55 :-) I was just about to send an email requesting it :-)
[21:58] <maxb> err
[21:58] <bac> barry: ready
[21:58] <maxb> whoever copied it to hardy, shouldn't have
[21:59] <barry> bac: calling...
[21:59] <barry> bac: bug 403606
[21:59] <mup> Bug #403606: ExpatError errors should be handled to not generate the OOPSes <oops> <Launchpad Registry:In Progress by barry> <https://launchpad.net/bugs/403606>
[21:59] <barry> bac: https://lp-oops.canonical.com/oops.py/?oopsid=1306XMLP2
[22:03] <barry> bac: http://paste.ubuntu.com/282468/
[22:08] <maxb> Hmm. The launchpad PPA for hardy is currently uninstallable.
[22:08] <maxb> Is there anyone who needs to know this?
[22:09] <barry> bac: eggs/zope.publisher-3.5.6-py2.4.egg/zope/publisher/xmlrpc.py
[22:09] <Fly-Man-> rockstar: *ping*
[22:10] <Fly-Man-> A new machine just got delivered in the datacenter
[22:10] <Fly-Man-> so I;m setting that one up with Jaunty now
[22:10] <Fly-Man-> to see if it works then
[22:14] <rockstar> Fly-Man-, if you continue to get the segfault, #bzr is going to be able to help much more than I can.
[22:15] <maxb> I wish the meta-lp-deps branches were somewhere I had write access :-/
[22:18] <maxb> Please can I enlist a member of ~launchpad to add this missing tag:
[22:18] <maxb> bzr tag -d lp:~launchpad/meta-lp-deps/trunk -r revid:maxb@f2s.com-20090910075602-i7m5vu8dicck9xcu 0.54
[22:19] <maxb> bzr tag --force -d lp:~launchpad/meta-lp-deps/trunk -r revid:stuart.bishop@canonical.com-20090930150127-02ubq4ceny88higo 0.55
[22:19] <maxb> also
[22:19] <maxb> and yes I do mean --force in the second
[22:34] <mwhudson> good morning
[22:46] <maxb> good evening :-)
[22:47] <maxb> To what extend do we care that the launchpad PPA is not currently installable on hardy?
[22:48] <mwhudson> maxb: it's pretty bad
[22:51] <maxb> I'm in no position test anything more than the installability of packages on hardy, but I could prepare something that is at least better than what is there.
[22:53] <maxb> Can I enlist you to run those two bzr tag commands from scrollback ~30 mins ago before they get forgotten about, or shall I email them to the list?
[22:56] <mwhudson> maxb: ok
[22:57] <mwhudson> maxb: what's the problem on hardy currently?
[22:57] <maxb> Someone copied the new jaunty/karmic launchpad-dependencies build to hardy too, but hardy was using a branched version
[22:57] <maxb> so the hardy-specific changes were removed
[22:58] <mwhudson> oh right
[22:58] <maxb> On a related note, we should probably change the description of the PPA to say that Intrepid is no longer supported.
[23:23] <maxb> OK, in two minutes, once it's published, please could someone copy-with-binaries 0.55hardy1 from maxb/launchpad to launchpad/ppa (hardy)
[23:24] <maxb> And also push lp:~maxb/meta-lp-deps/hardy into lp:~launchpad/meta-lp-deps/hardy
[23:25] <maxb> right, it's published
[23:29] <beuno> maxb, I think I have the power to do so
[23:29] <maxb> thanks
[23:32] <Fly-Man-> rockstar: It seems that there's an issue with the latest Vmware server
[23:32] <Fly-Man-> I have alerted the Vmware staff to have a look at it
[23:33] <beuno> maxb, done
[23:36] <maxb> Thanks, hardy lp devs will thank you :-)