[02:21] <ianm_> if I move a .pot file into a subdirectory, will it affect existing translations?
[06:05] <aminpy> http://dpaste.com/593859/plain/ <- how can I fix this?
[06:07] <lifeless> aminpy: let me see
[06:08] <lifeless> aminpy: its working here, which means you probably have a firewall issue
[06:10] <aminpy> lifeless, my colleagues run it without any problem
[06:14] <lifeless> aminpy: that may mean they don't have a firewall on their machine, or have permissions on your corporate firewall, or something else.
[06:15] <aminpy> lifeless, can I run it with ssh or ...?
[06:17] <lifeless> that xmlrpc call is done to do directory service lookups
[06:17] <lifeless> very recent bzr's do not do it at all
[06:20] <lifeless> aminpy: it looks like that is a proxy failure
[06:20] <lifeless> aminpy: do you have http_proxy or https_proxy set in your environment ?
[06:20] <aminpy> lifeless, I tested it with proxy and without proxy
[06:21] <lifeless> CONNECT is used when connecting to https via a proxy
[06:21] <lifeless> the error means it could not connect to your proxy
[09:34] <figure002> hello. how are fuzzy translations currently supported on LP?
[09:35] <lifeless> with code and schemas
[09:41] <figure002> so fuzzy translations are supported? because it seems that fuzzies are marked as untranslated on LP translations.
[09:42] <lifeless> they get marked as needing review
[09:42] <lifeless> yes they are supported
[09:45] <figure002> strange, because i don't see my fuzzies appear as 'need review' on LP, am i missing something?
[09:45] <figure002> LP automatically imports my PO files from the bzr repo, but fuzzies appear nowhere
[09:48] <lifeless> you might like to ask a question on https://answers.launchpad.net/launchpad about this.
[09:48] <figure002> i already did: https://answers.launchpad.net/launchpad/+question/135487
[09:48] <figure002> but it is marked as solved by someone else, should i make a new question?
[09:50] <lifeless> are you roland or serrano ?
[09:51] <figure002> serrano
[09:51] <lifeless> ah, so you didn't ask the question :)
[09:51] <lifeless> yes, you should ask a new one.
[09:51] <figure002> nope, but i added a comment with a question :)
[09:51] <lifeless> on a closed ticket
[09:52] <lifeless> so it won't be in anyones queue for review or answering
[09:52] <figure002> yeah, that's what i thought, i should make a new question
[10:15] <figure002> new qustion posted: https://answers.launchpad.net/launchpad/+question/167923
[10:15] <figure002> thanks for the help lifeless
[10:22] <lifeless> no probs
[13:15] <penguin42> I'm getting a 'list something' message when clicking on an attachment in bug 825644   (the terminal messages at the bottom) - any suggestions?
[13:15] <penguin42> oops - 'lost something'!
[13:41] <wgrant> penguin42: That's a regression with attachments with names containing spaces or some other special characters. It'll be fixed on Monday.
[14:08] <penguin42> ok, thanks
[14:09] <penguin42> is there a way to retrieve that file?
[14:40] <penguin42> ah - grab-attachments manages it
[15:33] <Darxus> I've had daily builds of lp:spamassassin working for a while.  I'd like to set up two additional PPAs based on it.  One basically identical to the existing daily builds, but only built once a month, and the second containing copies of the first after they're a month old.
[15:33] <Darxus> So I can test snapshots for a month, and then make them available to everybody else after a month of testing on a regular basis.
[15:33] <Darxus> Can any of that be automated?  Is there even a way to get packages from one PPA to another at all?
[15:34] <tumbleweed> sounds like a cronjob that copies binaries is what you want
[15:35] <Darxus> Cool, thanks.  I was just wondering a cron job running on my server might be useful.
[15:35] <tumbleweed> note archive.syncSources https://launchpad.net/+apidoc/1.0.html#archive
[15:35] <Darxus> Blows my mind that the SA devs insist there isn't enough manpower available to do monthly releases when I'm already doing and using daily releases.
[15:35] <tumbleweed> so you should be able to easily do this with a python launchpadlib-using script
[15:36] <Darxus> Neat, thanks.
[15:37] <Darxus> I just played with launchpadlib for the first time a couple days ago.  I could use more documentation :)
[15:37] <tumbleweed> +apidoc is pretty much all there is (that and some wiki pages on help.launchpad.net)
[15:37] <Darxus> From looking at what you linked to I.. really can't even guess how I'd copy a package from one PPA to another.
[15:40] <Darxus> This might help more:  https://help.launchpad.net/API/Examples#Copy an old version of a package into your PPA for a newer release
[15:42] <tumbleweed> I'm guessing something like: lp.me.getPPAByName(name='testing').syncSources(from_archive=lp.me.getPPAByName(name='daily'), include_binaries=True, source_names=['spamassassin'], to_pocket='RELEASE')
[16:38] <evolv> htf did I get here?
[16:39] <penguin42> evolv: Something involving a late night bar and a large drink?
[16:39] <evolv> well, it was more like drinking at a buddy's place playing video games
[16:39] <evolv> then I magically ended up here
[16:40] <evolv> I'm not sure what the general purpose of this channel is
[16:41] <penguin42> evolv: Bug reports and help about the launchpad bug tracking/planning system used by canonical/ubuntu
[16:41] <evolv> oh
[16:41] <evolv> lol
[16:42] <evolv> well, it's been fun guys, but I definitely took the wrong turn here
[16:42] <evolv> [eace
[22:41] <DNS777> hi guys! those autogen builds got stucked somehow https://launchpad.net/~dns/+archive/gnu/+builds?build_text=&build_state=building , i wonder why, because the i386 lucid went fine
[22:43] <DNS777> would be nice if there would be a "stop build" button
[22:44] <TheEvilPhoenix> well
[22:44] <TheEvilPhoenix> the errors are right there
[22:44] <DNS777> yes i c
[22:44] <DNS777> but i mean teh machines are stucked too
[22:44] <TheEvilPhoenix> make: *** [build-stamp] Error 2
[22:44] <DNS777> ^_^
[22:44] <TheEvilPhoenix> dpkg-buildpackage: error: debian/rules build gave error exit status 2
[22:44] <TheEvilPhoenix> yes, probly there's no error handlers
[22:44] <TheEvilPhoenix> did you email the email it said to email?
[22:44] <TheEvilPhoenix> btw, your debian/rules seems to be screwed ;)
[22:44] <TheEvilPhoenix> at least the builders think so
[22:44] <TheEvilPhoenix> *shrugs*
[22:55] <DNS777> tbh it doesnt make so much sense to send an email if i cant see whole build log
[22:55] <DNS777> ;)
[23:01] <TheEvilPhoenix> well that's all there is
[23:01] <TheEvilPhoenix> if its hung up, they'd have to, i dont know, kill the build daemon or something
[23:02] <TheEvilPhoenix> which is indicative of a bug in the building daemons, no?
[23:03] <DNS777> not sure, but a button to stop would be fine (and can save resources)
[23:06] <DNS777> where i can send feature requests? at lp itself > bugs ?