[01:58] <thumper> ok...
[01:58] <thumper> how do I get the bugs for a project?
[01:58] <thumper> I'm obviously brain dead
[01:58] <thumper> because what I'm trying isn't working
[01:58] <lifeless> well
[01:58] <lifeless> what are you trying
[01:58] <thumper> lp.bugs.search(project=udp)
[01:59] <thumper> where udp == lp.projects['unity-distro-priority']
[01:59] <thumper> I've also tried with project=  the string value
[01:59] <lifeless> udp.searchTasks()
[01:59] <thumper>  OOPS-0afa8a389ada3e4afbf779e05f2ee47f
[02:26] <thumper> hey
[02:26] <thumper> I'm trying to add a bug tag
[02:26] <thumper> not sure if it worked or not
[02:26] <thumper> the web page isn't showing it
[02:26] <thumper> but I'm wondering if that is just replication lag
[02:26] <thumper> bug.tags.append('foo'), followed by bug.lp_save()
[02:27] <thumper> will that work?
[02:29] <thumper> wgrant, lifeless: can you edit bug tags with the api?
[02:30] <wgrant> thumper: That's unlikely to work, but you can edit them.
[02:30] <wgrant> I think you have to set the whole thing.
[02:30] <wgrant> Possibly as a list, or possibly as a string.
[02:30]  * wgrant checks.
[02:31] <thumper> wgrant: thanks
[02:31] <wgrant> thumper: Set a new list and it should work.
[02:31] <thumper> wgrant: ok, I'll try that
[03:46] <george_e> Question: can I set up automatic sync. of translations for a specific branch?
[03:46] <george_e> I know I can get it set for a specific series.
[04:11] <george_e> Here is a slightly better explanation: http://askubuntu.com/q/105801
[04:13] <wgrant> george_e: I don't think that's supported.
[04:13] <wgrant> Code and translations are normally in the same branch.
[04:14] <george_e> wgrant: I tried that with an earlier branch and it was no end of headaches.
[04:14] <george_e> Launchpad just dumped the .po files in the root directory of the branch.
[04:14] <wgrant> The vast, vast majority of projects have them in the same branch.
[04:14] <wgrant> It will export them to the path with which they were imported.
[04:15] <george_e> wgrant: It will?
[04:15] <george_e> ...and where will it put new translations?
[04:17] <wgrant> Actually, are you talking about imports or exports?
[04:18] <wgrant> Launchpad will only *import* from a series branch, but you can tell it to export to any.
[04:18] <wgrant> I'm not quite sure how the path determination works; I don't know that much about Launchpad Translations.
[04:18] <wgrant> but eg. if you look at http://bazaar.launchpad.net/~stellarium/stellarium/auto-po/revision/5124 you'll see it normally exports to sensible paths.
[04:28] <george_e> wgrant: I didn't realize the two operations were independent.
[04:28] <george_e> I've set up automatic export to that branch now.
[07:24] <ESphynx> hey guys... could someone guide me with translations?
[07:50] <sagaci> ESphynx, what kind of guidance do you need
[07:50] <ESphynx> sagaci: our layout i sort of organized the .mo way, which launchpad is saying it doesn't support :(
[07:51] <ESphynx> we already have a Chinese and Spanish translation mostly done, and I can't figure out how to make it work :P
[07:52] <ESphynx> within our repository, we have project subfolders where .pot file get automatically generated at the root... and within the ecere folder for example, we have e.g. locale/zh_CN/LC_MESSAGES/ecere.po
[07:53] <sagaci> ESphynx, you could try http://jarfil.net/convert/msgunfmt.php
[07:53] <ESphynx> i'm wondering what changes would be required for things to work smoothly with launchpad?
[07:53] <ESphynx> sagaci: I have the .pot/.po files that's not the problem
[07:53] <ESphynx> the problem is the directory structure
[07:54] <ESphynx> lanuchpad seems to want ecere/zh.po
[07:54] <sagaci> ah ok
[07:54] <ESphynx> I have loacle/zh_CN/LC_MESSAGES/ecere.po
[07:54] <sagaci> fair enough
[07:57] <ESphynx> I could move ecere.pot into locale/ and keep the source translations as zh.po, es.po ...
[07:57] <ESphynx> but there would be many locale/ subfolders throughout the project , e.g. ecere/locale/zh.po , ide/locale/zh.po
[07:57] <ESphynx> I'm wondering whether that would work or not
[07:57] <sagaci> shouldn't be too hard to reorganise
[07:57] <ESphynx> i'm reluctant to have ecere/ecere/zh.po or ecere/locale/ecere/zh.po
[07:58] <ESphynx> i'm just wondering what would work
[09:01] <czajkowski> Good morning
[09:23] <czajkowski> StevenK: you didn't like the - :)
[09:26] <StevenK> I did not. :-)
[09:26] <StevenK> I needed an extra one for my smile.
[09:57] <rye> ohai, is the task to process the reports being submitted via ubuntu-bug working now? I am filing about about unity and it has been 10 minutes, still on processing stage
[09:59] <czajkowski> rye: yes ubuntu-bug works fine here
[10:00] <araujo> hello, the multi-projects bug feature (https://help.launchpad.net/Bugs/MultiProjectBugs) is available for projects that are hosted in different launchpad instances too?, probably across different networks?
[10:01] <apw> did launchpad just die ?
[10:01]  * apw is getting 'Uh oh!' messages
[10:01] <rye> ah, now 503 error
[10:01] <rye> czajkowski, your ubuntu-bug killed launchpad, booo
[10:01] <odony> apw, rye: 10:00 - 10:05 is database update window I think
[10:01] <rye> and we are back, still not filing a bug
[10:02] <apw> oh is it ... hmmm
[10:03] <rye> odony, sorry, i wonder whether it could affect the bug filing @ 15-25 minutes ago
[10:04] <odony> rye: don't think so
[10:04] <czajkowski> rye: stil having issues?
[10:04] <rye> interesting, second ubuntu-bug unity is pretty much doing the same
[10:05] <czajkowski> sure it's not just unity hanging ?
[10:05] <czajkowski> and searchign the queue of bugs?
[10:05] <rye> czajkowski, i mean when the bug report web page is opened, it says that bug report is being processed,  oh, nevermind, the second attempt completed successfully
[10:06] <czajkowski> ok so lp does go down for a short period each day for maintenace
[10:06] <czajkowski> perhaps you got in the middle of that window
[10:06] <rye> czajkowski, oh, and the first one completed too. Next time please kick me from the channel and say to come in 20 minutes if the problem still persists
[10:07] <czajkowski> rye: it's fine
[10:07] <czajkowski> :)
[10:07] <wgrant> rye: We turn cronjobs like that off for about 15 minutes around database outages (which we just had, as czajkowski said).
[10:10] <rye> wgrant, ah, then this explains my issue completely
[10:20] <ESphynx> i'm back :)
[10:20] <ESphynx> anyone had suggestions regarding my translations?
[10:26] <czajkowski> ESphynx: what translations?
[10:35] <ESphynx> czajkowski: the ones for Ecere hehe
[10:35] <ESphynx> within our repository, we have project subfolders where .pot file get automatically generated at the root... and within the ecere folder for example, we have e.g. locale/zh_CN/LC_MESSAGES/ecere.po, i'm wondering what changes would be required for things to work smoothly with launchpad?
[10:35] <ESphynx> I could move ecere.pot into locale/ and keep the source translations as zh.po, es.po ...but there would be many locale/ subfolders throughout the project , e.g. ecere/locale/zh.po , ide/locale/zh.po, I'm wondering whether that would work or not...
[10:36] <czajkowski> ESphynx: hmm honesly I'm not sure, but if you give me your email address I'll find out for you and let you know  if you like
[10:36] <czajkowski> I need to fined jtv and see if he knows
[10:36] <jtv> Found him, you have
[10:37] <czajkowski> jtv: morning wasn't sure if youw ere about and was going to mail you if you're busy re ESphynx question above
[10:37] <jtv> Morning :)
[10:37] <jtv> ESphynx: two things
[10:38] <jtv> First is a sidenote: "zh.po" won't work, because there are two very different versions of written Chinese that are both arguably the "standard' version.  Always say either zh_TW (for Traditional Chinese) or zh_CN (for Simplified Chinese).
[10:39] <jtv> We'd better note that because otherwise you might get everything else right and it might be completely unclear why the PO files weren't being imported.  :-)
[10:40] <jtv> Second is the actual answer to your question.  :-)
[10:40] <jtv> In Launchpad, the standard directory structure is as described in https://help.launchpad.net/Translations/YourProject/ImportingTemplates
[10:41] <jtv> (May take some clicking from there to get to the right bit — please hang on, I'm looking for it)
[10:42] <ESphynx> jtv: The problem is, we have our own directory structure in the project... e.g. we already have Spanish and Chinese.
[10:42] <ESphynx> and we use our own i18n system, which uses the gettext format, but our own tools...
[10:42] <jtv> There are one or two alternative directory structures that will also work, but they're a bit brittle and poorly understood.
[10:42] <ESphynx> So the .pot files get automatically generated in each project's folder... e.g. we have sdk/ecere/ecere.pot for the ecere project (sdk/ecere) and sdk/ide/ide.pot for the ide project (sdk/ide)
[10:43] <jtv> That structure for the templates is perfect for launchpad.
[10:43] <ESphynx> and the source .po files should be somewhere under sdk/ecere/ , prefereably under sdk/ecere/locale/
[10:43] <ESphynx> for the translations
[10:43] <ESphynx> right now, our translations for ecere are in sdk/ecere/locale/zh_CN/ecere.po
[10:44] <jtv> The standard naming scheme would be sdk/ecere/zh_CN.po
[10:45] <jtv> (So: one template per directory, PO file in the same directory as the template, and the PO file's name consisting of <language>.po
[10:45] <jtv> )
[10:45]  * czajkowski ha a lot to learn about .PO
[10:46] <czajkowski> jtv: ESphynx has 12 imports in the queue
[10:47] <jtv> ESphynx: there are other ways to do this, but they're nowhere near as convenient.
[10:47] <ESphynx> jtv: that's what I don't want, all the translations at the top of the project...
[10:47] <jtv> I see.
[10:47] <ESphynx> jtv: sdk/ecere/locale/zh_CN.po would be "ok"
[10:47] <ESphynx> PoEdit automatically changes .po to .mo when saving though, which is why I'd have preferred the file being called "ecere.po"
[10:47] <ESphynx> would save from having to copy stuff around...
[10:48] <jtv> Would it be doable to move the template down the tree?  So for example, sdk/ecere/locale/ecere.pot?
[10:48] <ESphynx> yes that is possible.
[10:48] <ESphynx> but then the subfolder is locale/
[10:48] <ESphynx> so wouldn't that confuse launchpad?
[10:48] <ESphynx> having ecere/locale/ecere.pot and ide/locale/ide.pot ?
[10:50] <jtv> Should be fine; about the worst I can imagine is if these come from a bzr branch, and the branch approver might get confused.  But there's ways to deal with that:
[10:51] <ESphynx> we have a git->bzr auto importer
[10:51] <ESphynx> there's no way to have sdk/ecere/locale/zh_CN/ecere.po hey?
[10:51] <jtv> If the branch import approver tries to pick the "locale" part as the domain name, it won't approve anything because they'll all be called "locale."  But you can work around that by manually approving the templates, and then the approver will just note "hey I know this file — and so I know where it goes."
[10:52] <ESphynx> that's what I was worried about :|
[10:52] <jtv> If this is indeed a problem, you'll need to deal with it only once per new template per release series.
[10:53] <jtv> After that, the template's path will be remembered.
[10:53] <ESphynx> per new template?
[10:53] <jtv> Yes, every time you add a template.
[10:53] <ESphynx> ah ok. that shouldn't be often so that's not a problem
[10:53] <ESphynx> but then it will know where to find the .po?
[10:53] <jtv> Right.  There is also a way to have sdk/ecere/locale/zh_CN/ecere.po, but it's not as nice.
[10:53] <jtv> The .po should be in the same directory as the template.
[10:53] <jtv> That's how it finds .po files.
[10:54] <jtv> So any given directory with translation files will have a <name>.pot and a bunch of <language>.po files.
[10:54] <ESphynx> hmm ok.
[10:54] <jtv> es.po, zh_CN.po, and so on.
[10:54] <ESphynx> what's the way though?
[10:54] <ESphynx> it's so much easier to just save the .po file and get the .mo file :) (which we embed within the application resources)
[10:55] <jtv> You can do it in one of two ways:
[10:56] <jtv> (1) manually approve each PO file (so that's once for every language for every template in every release series), specifying manually which template the translation is for.  Launchpad will remember where the file with that exact path should go.
[10:56] <jtv> (2) Upload the translation not to the release series, but on the page for either the template or that exact language.
[10:57] <jtv> In case (2), there are two dangers to bear in mind.
[10:58] <jtv> First: if you upload just an individual PO file, your browser won't tell Launchpad its path, just its name.  So it'll be called something like ecere.po which is no help at all in figuring out which file goes where.
[10:59] <jtv> Second: if you upload the PO file as part of a tarball, make sure there are no other translations in that tarball because Launchpad will take whatever you upload to (for example) the "es" translation of the "ecere" template as being a Spanish translation for ecere.
[10:59] <jtv> If your uploads come from a branch, none of that will affect you of course.
[11:00] <jtv> With uploads from a branch, the branch import approver won't know what to do with your naming scheme and so give up.  The files will stay on the queue as Needs Review, and later the "regular" approver (part of what we call the translations import queue gardener) will come along and try its own rules for matching the file to a known translation.
[11:01] <jtv> The gardener will notice if the release series had exactly 1 translation file with this exact path, and take the upload as an update of that file.
[11:02] <jtv> It'll slow things down, and you'll have to approve the first upload for each language/template/series manually.  But it would work.
[11:02] <ESphynx> uploads from a branch... what id we do all through git that then goes to-> bzr hehe
[11:02]  * czajkowski is rather glad jtv was here 
[11:02] <jtv> czajkowski: next week you can do a harder one.  :-)
[11:02] <jtv> ESphynx: oh, you mean move the files around?
[11:03] <jtv> Actually, some softlinks in the branch _might_ work.
[11:03] <czajkowski> jtv: I'm copying this for fugure reference and so I can re read it over and over to learn
[11:03] <ESphynx> jtv: I mean, all uploads done through git ...
[11:04] <jtv> That's no problem.
[11:04] <jtv> I guess you've got the bzr branch set up to import from the git repo; shouldn't make any difference.
[11:05] <ESphynx> yes that's i've got
[11:05] <ESphynx> so hmm.. anyways to just get Launchpad to realize i've got Spanish and Chinese translations already? hehe
[11:05] <ESphynx> right now the .pot files are not uploaded because they are generated on building the projects
[11:06] <ESphynx> but I could add them, say in ecere/locale/ecere.pot ide/locale/ide.pot
[11:06] <ESphynx> and the CHinese translation is in ecere/locale/zh_CN/LC_MESSAGES/ecere.po
[11:06] <ESphynx> that's really what I'm hoping for: having current translations show up on Launchpad, and interest Launchpad translators in contributing :)
[11:06] <jtv> I'm not completely sure but I think the branch importer would pick up any .po file in the branch and upload it.
[11:08] <jtv> The way it normally works is: you update your .pot or .po, commit, push the change to your git repo; Launchpad pulls in the change, mirrors it into your bzr branch; the translations system picks up the changed .pot/.po file and puts it on the import queue; one of the two automated approvers figures out which language and which template it's for; the importer processes the file; and the UI updates.
[11:08] <ESphynx> yeah. that's what I'm hoping happens :) So I would definitely have to add the .pot files, right?
[11:09] <jtv> Yes.  There is a capability for building gnome-intltool templates internally, but I'm not sure we'll keep it.
[11:10] <jtv> (That capability means that projects that are set up in just the right way can push a _code_ change and Launchpad's translation UI will pick up the changes in translatable strings.)
[11:12] <ESphynx> jtv: what I've done is added the $"string" and $"context"."string" syntax in eC
[11:12] <ESphynx> So Launchpad probably won't ever support that :P hehe, I've manually uploaded the .pot files earlier though... but I don't know what that will do, if anything at all :P
[11:12] <jtv> eC?
[11:12] <ESphynx> jtv: Yes that's the language the SDK is written in and is for writing :P
[11:12] <jtv> Ah!
[11:13] <jtv> If there's a pretty "deep" toolchain between your source tree and your gettext files, maybe you should just generate the translation files to a separate branch.
[11:13] <ESphynx> jtv: i'm OK with just committing the .pot files in locale/
[11:14] <jtv> OK, that keeps things simple.  :)
[11:14] <ESphynx> but would translations in locale/zh_CN/LC_MESSAGES/ecere.po  be found then?
[11:14] <jtv> I think a test run should work on staging.launchpad.net, by the way.  Might be worth playing with it there.
[11:15] <jtv> locale/zh_CN/LC_MESSAGES/ecere.po *might* fit an alternative directory layout that we have some legacy code for...  Not sure.
[11:16] <jtv> But that code is old and we'd love to clean it up — which might affect what layouts will or won't work.
[11:16] <ESphynx> How about locale/zh_CN/ecere.po  ?
[11:20] <ESphynx> How does staging.launchpad.net work?
[11:22] <jtv> ESphynx: it's a copy of the real thing that we wipe and re-initialize periodically.
[11:22] <jtv> We also deploy our changes there for testing, before they go to the production server.
[11:22] <ESphynx> ah ok ;)
[11:22] <jtv> It doesn't run _all_ the services that the real launchpad runs, of course.  In particular, not outgoing email.  :)
[11:23] <ESphynx> https://translations.staging.launchpad.net/ecere/trunk/+imports
[11:23] <ESphynx> the whole review process thing is what worries me... why isn't it automated?
[11:24] <jtv> There's lots of automation, but there are cases where we need a human to decide.
[11:24] <jtv> That used to be a privileged operation, and so we never really got around to making that process more friendly and efficient.
[11:25] <jtv> This file contains the logic behind the gardener's import approval: http://bazaar.launchpad.net/~launchpad-pqm/launchpad/devel/view/head:/lib/lp/translations/model/translationimportqueue.py
[11:26] <jtv> (You may have to reload that page if it fails)
[11:27] <jtv> ESphynx: I guess that upload on staging was done manually — as you can see we don't get the full file path.
[11:28] <ESphynx> jtv: it was... i guess there's no way to match the .po file manually right
[11:28] <jtv> ESphynx: in that source file I just linked to, search for _guess_multiple_directories_with_pofile — it documents some "legacy" directory structures it should support.
[11:29] <ESphynx> thansk
[11:29] <jtv> Yes, you can match the .po file manually.  Click the "pencil" icon next to "No import target selected yet."
[11:29] <ESphynx> oh, I can do it myself?
[11:29] <jtv> (If you see no icon, you may need to log in separately to the staging server)
[11:29] <jtv> Yes, you can do that yourself.  Used to be privileged, but now I think you just need to be one of the project owners.
[11:29] <ESphynx> I don't mind doing things manually, but i was worried this had to be  done by someone at Launchpad hehe
[11:29] <jtv> Or maybe even the uploader.
[11:30] <jtv> No, used to be that way — thankfully it isn't any more.  But we'd love it to be more user-friendly!
[11:30] <ESphynx> that would be perfect.
[11:30] <jtv> You'll note that you can edit the path on that approval form.
[11:30] <ESphynx> though I might still move the .pot to locale/ and have it committed
[11:30] <jtv> That would definitely be best.  Save you a lot of delays and manual work.
[11:31] <ESphynx> UI rant: that pencil to me looks like an Exclamation part.
[11:31] <jtv> Getting fast feedback can be really helpful.
[11:31] <ESphynx> exclamation point*
[11:31] <jtv> Yes, it takes some getting used to.
[11:31] <jtv> Problem is, we need it in so many places that it gets hard to insert something clearer (and larger) every time.
[11:31] <ESphynx> how long does it take for bzr to pick up git stuff?
[11:32] <jtv> Erm…  don't know.  Maybe jelmer would know.
[11:32] <jelmer> 'morning jtv, ESphynx
[11:33] <jelmer> ESphynx: once the import is created it usually takes only a couple of minutes for the import to start. You should see progress on the page while the import is running.
[11:33] <jtv> ESphynx: just as an experiment for the approval, try pretending that ecere.pot is a PO file; use the dropdown at the top.  Then you'll see that a translation also gets a dropdown to let you select what language it's for.
[11:33] <ESphynx> it's quite a bit delayed... my last commit from hours ago isn't there yet
[11:33] <ESphynx> jelmer: I mean to wake up and do it?
[11:33] <ESphynx> I set up the import months ago
[11:33] <jelmer> ESphynx: if it's an existing import, it will be updated every 4 hours
[11:33] <ESphynx> 4 hours ah ok thanks
[11:33] <jelmer> ESphynx: you can also hit "Import Now" on the web page for the import
[11:34] <ESphynx> oh you can! awesome.
[11:34] <ESphynx> I'll give all this a try right now then
[11:34] <ESphynx> jtv: thanks a lot for the help :)
[11:34] <jtv> np — good luck!
[11:34] <ESphynx> btw hwat's with Wayland???
[11:35] <ESphynx> I'll have to support that for my GUI toolkit to run on Ubuntu?
[11:35] <jelmer> ESphynx: as far as I know Wayland is still some time away
[11:35] <jelmer> ESphynx: but the Ubuntu channels are probably a better place to ask about that than here.
[11:36] <ESphynx> ah yes. hehe, just curious.
[11:36] <ESphynx> hmm, would here be a good place to ask for help getting Ecere into Ubuntu?
[11:37] <ESphynx> e.g. the project has a 'need-packaging' tag hehe
[11:40] <jelmer> ESphynx: my guess would be that #ubuntu-packaging or maybe #ubuntu-devel are better places for that.
[11:41] <ESphynx> thanks :)
[12:33] <ESphynx> "No header found in this pofile" -- my .pot files need headers? :|
[13:02] <ESphynx> Line 315: Unexpected keyword: msgctxt ?
[13:02] <ESphynx> Launchpad doesn't support msgctxt?
[13:04] <ESphynx> or msgctxt should be before msgid ...
[13:52] <ESphynx> hmm... Spanish (Spain) translations don't seem to show up when showing Spanish :|
[13:54] <hrw> hi
[13:54] <hrw> will launchpad finally get sortable tables?
[13:55] <hrw> https://code.launchpad.net/~linaro-maintainers has 111 branches and no way to sort them alphabetically...
[13:55] <czajkowski> mrevell: might know more about that
[13:57] <mrevell> hrw, I'd *love* to do that but we don't have a plan to do it just yet. There are a number of similar UI issues I'd like us to address in the code.lp.net
[13:57] <hrw> mrevell: is there any public list of planned things to do in launchpad (other then 'who knows, maybe in 2031' :)
[13:58] <czajkowski> hrw: patches are always welcome :)
[13:58] <mrevell> :)
[13:58] <ESphynx> just 'Spanish' seems to work
[13:59] <hrw> czajkowski: prefer to waste time in other projects ;d
[13:59] <mrevell> hrw, Some parts of the Launchpad team are focusing on projects other than Launchpad for the next few months, so there's nothing public right now.
[13:59] <hrw> mrevell: ok
[13:59] <hrw> thanks for info
[14:00] <mrevell> No problem.
[15:13] <MoonMaker> Hi!
[15:13] <MoonMaker> I wanted to request a code import
[15:13] <MoonMaker> but the url already exists.
[15:13] <MoonMaker> https://code.launchpad.net/~deejay1/sparkleshare/master
[15:14] <MoonMaker> what can I do in order to get the latest code import from sparkleshare?
[15:15] <MoonMaker> any ideas?
[15:15] <jelmer> MoonMaker: there already is an import - just use that import
[15:15] <MoonMaker> but this import is suspended
[15:15] <MoonMaker> since 2011
[15:16] <jelmer> MoonMaker: looking at the details, it seems like Launchpad can't import this branch since it uses git submodules
[15:16] <MoonMaker> ahh ok, yes sparkleshare is using it
[15:17] <MoonMaker> thank you very much for your help. I wanted to create a daily package....thats life
[15:43] <jelmer> MoonMaker: it's not very useful to request another import unless the history has been rewritten to remove the submodules.
[15:44] <MoonMaker> hmm, I thought maybe its possible to change the format in github
[15:44] <MoonMaker> so I started a fork
[15:45] <jelmer> MoonMaker: no, you'd have to rewrite the history to exclude the submodules.. there is only one git format
[15:45] <MoonMaker> k, and you dont know if it is possible automaticly with github?
[15:46] <MoonMaker> automatically
[15:46] <jelmer> MoonMaker: no, github doesn't have a way to do that for you
[15:46] <MoonMaker> k, then we have to delete this import. Sorry for extra work.
[15:47] <jelmer> np
[18:51] <gotwig> hey
[18:51] <gotwig> Pls help me, how can I use dput with active ftp instead of passive ftp ? http://askubuntu.com/questions/105957/how-may-i-upload-my-source-package-with-active-ftp-over-dput-to-launchpad
[18:52] <mgz> gotwig: try a url in the form aftp: rather than ftp:
[18:54] <gotwig> mgz: Unknown upload method: aftp
[18:56] <mgz> gotwig: may not be possible then
[18:59] <gotwig> mgz: wtf o.0?
[19:16] <lifeless> mgz: man dput.cf
[19:20] <mgz> lifeless: I'm not the one who was asking
[19:21] <lifeless> mgz: I know
[19:21] <mgz> feel free to post that response to his askubuntu link I guess
[19:21] <lifeless> mgz: but if you're going to answer, you may as well know the answer ;P
[19:23] <mgz> 'd misread the question as relating to bzry things, not being misc debian
[19:24] <lifeless> fair enough
[19:32] <jono> hey, is it possible using launchpadlib to determine if someone has contributed a merge proposal /patch successfully to a particular branch?
[19:59] <Ampelbein> jono: Hmm, I guess you could iterate over the successful merges and check the associated project? Like "for merge in lp.people(me).getMergeProposals(status="Merged")" and check if merge.target_branch.project == the project you want to compare against?
[20:00] <jono> Ampelbein, sounds good, many thanks :-)
[20:29] <lifeless> jono: Ampelbein: note that this could take a very long time :)
[20:29] <jono> lifeless, is there a faster way to do it?
[21:10] <jodh> Hi - could someone re-score the 2 builds waiting in my ppa here:
[21:10] <jodh> https://launchpad.net/~jamesodhunt/+archive/bug-935585/+packages ? I'd
[21:10] <jodh> like to get some feedback on an upstart update overnight from affected users.