[00:08] <andidog> Hi guys. Can anyone log in to staging.launchpad.net? I always get "Password didn't match" error in the OpenID form. I'm registered with launchpad for several days now.
[00:11] <wgrant> andidog: staging is currently running a copy of the production database from 11 days ago.
[00:11] <wgrant> Not sure why it's so old.
[00:11] <wgrant> andidog: If your account is newer than that, create a new one at login.staging.launchpad.net.
[00:12] <wgrant> It'll be overwritten when the next DB update happens.
[00:14] <andidog> wgrant: I thought I could only register on the production launchpad. Thanks for that hint ;)
[00:14] <wgrant> andidog: That used to be the case, but it's different now.
[00:23] <MrQuincle> Dear people, at https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted I found a great guide.
[00:23] <MrQuincle> To use recipes. It works locally.
[00:24] <MrQuincle> I was wondering, I have a public branch, but no option "Create packaging recipe" available on Launchpad.
[00:24] <MrQuincle> Do I have to do something for that?
[00:24] <wgrant> MrQuincle: What's the URL you're looking at?
[00:24] <MrQuincle> https://code.launchpad.net/~annevanrossum/robot3d/trunk
[00:25] <wgrant> MrQuincle: Recipes are still in beta, so they're only on the beta-testing server.
[00:25] <wgrant> https://code.edge.launchpad.net/~annevanrossum/robot3d/trunk
[00:25] <MrQuincle> Aha :) So I can push them locally from my own machine if I want to. And use a cron tab on my own machine too.
[00:25] <wgrant> Or just throw 'edge.' in before 'launchpad.net' in the URL.
[00:26] <wgrant> edge uses the same database, just with newer code and extra features turned on.
[00:26] <wgrant> So you can use it.
[00:26] <MrQuincle> Cool!!
[00:27] <MrQuincle> Thanks a lot! It is really great software!
[00:27] <wgrant> Recipe support still isn't perfect, but please report bugs if you run into any issues.
[00:28] <MrQuincle> I will, definitely.
[00:44] <ari-tczew> wgrant: do you maintain wiki.ubuntu.com?
[00:46] <MrQuincle> I guess when more and more things become automated you will need a large build farm.
[00:46] <MrQuincle> It is possible to contribute a machine or is that too difficult?
[00:47] <MrQuincle> I would be happy to add the possibility to use a VM at our company. Perhaps with some "bias" regarding our own packages. ;-)
[00:48] <askhl> Hi.  I've uploaded a po-file which has apparently deleted a large number of translation suggestions.  They are now translated as emptry strings by "me".  Apparently dpm and danilos weren't either.  How can this be undone?  This is pretty horrible.
[00:48] <MrQuincle> But I guess not, you don't want to risk builds on "unknown" VMs probably...
[00:48] <askhl> ...weren't aware that translation suggestions could be deleted like this, I mean.
[00:49] <askhl> In any case: Lots of translations were discarded, and this needs to be reverted.
[00:51] <askhl> In case nobody knows what do to, I would very much like to know who to talk to about it.  This is serious.
[01:00] <askhl> Bugger.
[01:07] <wgrant> ari-tczew: No... the Canonical sysadmins do.
[01:07] <wgrant> askhl: You'd be better asking on a European week day.
[01:07] <wgrant> It's very early Saturday morning for all the Translations devs.
[01:12] <askhl> wgrant: unfortunately also for me, being in Europe.  It's 2 AM.  Is there some kind of log from which previous translations can be retrieved?
[01:13] <wgrant> askhl: Translations is the one part of LP that I reallly don't know much about, sorry.
[01:15] <askhl> wgrant: thank you.
[01:15]  * askhl cries.
[01:39] <askhl> wgrant: say, when does 'staging' reset?
[01:40] <wgrant> askhl: It varies.
[01:40] <wgrant> It's been almost two weeks since the last one.
[01:40] <wgrant> Not sure when the next will be.
[01:41] <askhl> Well, this is a chance to get those strings back...
[01:41] <wgrant> They might just magically reappear if you revert your string changes, of course.
[01:42] <askhl> Revert how?
[01:46] <wgrant> I guess you really should talk to Translations people.
[01:46] <wgrant> But maybe try to export PO files from staging now, just in case?
[01:48] <askhl> wgrant: right.  The thing is, there are 600 paragraphs in ubuntu-manual which are *suggestions*, but have not yet been accepted (under review).  Some strings disappeared mysteriously, one thing led to another, some of the Powers That Be advised me to upload a previously exported po-file.  Now all suggestions are gone.  I'll accept all the suggestions as quickly as possible in staging and export a po-file.  Sounds like a plan?
[01:48] <wgrant> I'd be wary about making large changes on staging.
[01:48] <askhl> (as they still exist in staging)
[01:49] <askhl> Well, if I can export something from staging, I have it locally, and it cannot be lost.  Right?
[01:49] <wgrant> Well, but then you've accepted all the potentially bad translations.
[01:49] <wgrant> It'd be nice if we knew when it would next update.
[01:50] <askhl> wgrant: accepted in staging.  I can merge with other local files that actually contain the accepted ones.  It'll all work out *if* I can just export the sodding (excuse me) suggestions.
[01:50] <wgrant> I guess.
[01:50] <wgrant> Worth a try.
[01:51] <askhl> We'll know exactly what needs to be proof-read.  The only problem is what you can and cannot do in LP
[01:54] <wgrant> askhl: Ah, I guess if you have an export with the suggestions accepted and another without, you can work it out.
[01:54] <wgrant> So, yeah, do it.
[02:03] <askhl> Rather repetitive work, but luckily Adi Roiban implemented hot keys...
[02:10] <askhl> Only catch is, I'm not sure you can export po-files from staging...
[02:36] <askhl> Right, I'm running a script which wgets all 1647 single-string translation pages for the project.  Can't get it to export e-mails...
[02:37] <wgrant> Ah, true, the export script doesn't run automatically.
[02:38] <askhl> Well, I guess that's `just another day at the office' then.
[02:56] <askhl> wgrant: I think this will actually work.  We'll see on Monday if the ordinary suggestions can be restored, otherwise I'll do some grepping and restore them from the html files.  Good night
[02:57] <askhl> (or good <whichever time it is where you are>)
[02:58] <wgrant> askhl: Just hitting midday for me.
[02:58] <wgrant> Goodnight.
[12:06] <wzssyqa> how to build for armel on ppa?
[15:52] <maxb> Urgh. Build-Depends: git (>= 1:1.7.0.4-2) | git-core
[15:53] <maxb> and the buildds install gnuit, not git
[15:57] <shadeslayer> maxb: make it hard dep on git-core?
[15:57] <shadeslayer> see it takes the first thing it can find
[15:57] <shadeslayer> oh
[15:58] <shadeslayer> nvm me
[16:00] <wzssyqa> how to build for armel on ppa?
[16:04] <shadeslayer> wzssyqa: i think you need to specially apply for that
[16:06] <wgrant> It's only for Canonical projects at the moment, I believe. The builders are few and slow, and security is not sufficient to permit public access.
[16:07] <wzssyqa> wgrant: shadeslayer thanks
[16:08] <shadeslayer> wgrant: any idea if there was a new bzr-svn plugin release?
[16:09] <jelmer> shadeslayer: new is relative. Since when ? :-)
[16:09] <wgrant> shadeslayer: On Launchpad? I don't know.
[16:10] <shadeslayer> jelmer: when was the last release? :D
[16:10] <jelmer> shadeslayer: the last bzr-svn release was one and a half weeks ago I think.
[16:10] <shadeslayer> you told me that there was going to be a new release sometime this month..i think..
[16:10] <shadeslayer> ah ..
[16:10] <jelmer> shadeslayer: there is a difference between bzr-svn releases and rollouts of bzr-svn on Launchpad
[16:11] <jelmer> shadeslayer: launchpad does not roll out every single bzr-svn release, but sometimes we also deploy snapshots of bzr-svn (without an upstream release)
[16:11] <shadeslayer> jelmer: hmm.. so when was the last time a new bzr-svn landed in LP
[16:11] <jelmer> one and a half weeks ago as well
[16:11] <shadeslayer> :P
[16:11] <jelmer> shadeslayer: I'm upstream for bzr-svn, but not in the launchpad code team
[16:12] <shadeslayer> oh!
[16:12] <shadeslayer> i thought you were with lp code team as well :D
[16:13] <jelmer> shadeslayer: I'm in the Soyuz team
[16:13] <shadeslayer> jelmer: https://code.edge.launchpad.net/~vcs-imports/kdesupport/trunk << might just complete this time
[16:13] <shadeslayer> :P
[16:13] <shadeslayer> oh man
[16:14] <shadeslayer> well ... im off for now ... cya later
[17:14] <geser> maxb: your build-dependency problem could be bug 594916
[17:14] <maxb> ah yes
[17:17] <geser> changing the order so that git-core gets prefered should work around it
[18:11] <maxb> Anyone around who can abort a build?
[18:12] <maxb> I seem to have hung builds of dulwich on louvi and rhenium
[20:21] <lifeless> maxb: you can cancel your own builds, i thought?
[21:03] <jelmer> lifeless, nope
[22:34] <Muscovy> Is there a way to make bzr download a specific revision instead of the newest one?
[22:38] <shadeslayer> Muscovy: yeah
[22:38] <shadeslayer> bzr branch foo -r rev
[22:40] <Muscovy> Thanks.