[00:02] <persia> Looking at bug #162510 : there is a mention of an "admin merge" with a longer timeout.  How is such a thing requested?
[00:04] <spiv> persia: file a question at https://answers.launchpad.net/launchpad I think
[00:04] <persia> spiv, OK.  So what happened for https://answers.launchpad.net/launchpad-registry/+question/119712 ?
[00:05] <persia> That seems to indicate the user should just press the button a couple hundred more times, which seems unlikely to be successful.
[00:06] <spiv> persia: I agree, that doesn't look promising at all.  But Curtis is certainly much more of an authority than me.
[00:07] <persia> Hrm.  I wonder how it works then.  Maybe the question needs to be asked before a merge is attempted?
[00:11] <wgrant> persia: The suggestion is mainly based on the expectation that the DB servers will eventually have everything cached, so there will be no disk reads required, and it might eventually complete in time.
[00:13] <persia> wgrant, Do you know if an "admin merge" is impossible now?  I wonder if that would help.  After 120 tries, I'd think as much as would cache would be cached.
[03:31] <wgrant> lamont: adare, ross, and probably a few other non-virt builders need a restart (they're stuck ABORTING due to buildd-manager breakage).
[04:53] <lamont> wgrant: ta
[05:14] <lamont> wgrant: several of the virtualized ppas fell back over after a reset and marking ok.  on that note, bedtime
[05:17] <wgrant> lamont: Yeah, known.
[05:17] <wgrant> lamont: The new buildd-manager is a bit broken.
[05:17] <wgrant> Needs DB surgery.
[05:17] <lamont> ya think?
[05:19] <lamont> ew.  which tells me that I definitely want to go to bed now
[05:20] <wgrant> Yeah.
[05:20] <wgrant> We can hopefully keep it alive until we work out what's wrong.
[08:55] <vish> hi, I'm trying to forward mails from a gmail account to a team mailing list, but it seems the confirmation mail does not reach the team, how do it do this forwarding?
[08:56] <vish> for the https://launchpad.net/~papercuts-ninja team
[08:56] <vish> i could not find any way to add filters to the mailing list and i thought that setting a gmail account as the contact addy and then forwarding from the account would help with the filters problem..
[09:50] <shadeslayer> so if launchpad goes for maintainence, does that mean builds also go offline?
[09:50] <shadeslayer> seems so...
[09:51] <shadeslayer> what happens if i upload new sources?
[09:51] <wgrant> shadeslayer: No new builds will be dispatched, but existing builds will continue.
[09:51] <shadeslayer> ohk
[09:51] <wgrant> They'll be picked up when the upgrade is finished.
[09:51] <shadeslayer> that is awesome
[09:54] <shadeslayer> wgrant: what about package publishing?
[09:54] <wgrant> shadeslayer: That's disabled during the upgrade.
[09:54] <shadeslayer> ohk
[10:18] <jetienne> ppa.launchpad.net is out or is it just me ?
[10:19] <jetienne> Uploading to ppa (via ftp to ppa.launchpad.net):
[10:19] <jetienne> Connection failed, aborting. Check your network [Errno 111] Connection refused
[10:20] <wgrant> jetienne: Launchpad is offline right now for a database upgrade.
[10:21] <jetienne> wgrant: ok, any eta ?
[10:21] <shadeslayer> jetienne: 2 hours
[10:21] <jetienne> thx
[10:21] <wgrant> jetienne: 90 minutes or so.
[10:22] <bigjools> and it's in the topic ...
[10:24] <shadeslayer> i cant even branch stuff... :(
[11:14] <LinuxJedi> builders work affecting bzr too?
[11:38] <jetienne> ppa.launchpad.net is back
[14:11] <fta> is sftp://people.ubuntu.com dead?
[14:47] <fta> anyone for sftp://people.ubuntu.com ??
[14:51] <abentley> fta: I'm not sure what you're asking.
[14:52] <fta> abentley, it's rejecting connections (started a few hours ago, probably related to the maintenance window)
[14:53] <abentley> fta: works for me.
[14:54] <fta> abentley, http://paste.ubuntu.com/533480/
[14:54] <fta> same on 3 of my boxes where it usually works
[14:55] <vish> sinzui: hi, re: the team mail filters question,  Wouldnt it be the same problem when mail is forwarded from a different service? or do the lp filters only look at the 'From' addy and not the 'X-forwarded-to' or 'X-forwarded-for'
[14:56] <abentley> fta: (publickey) usually means it hasn't got the right ssh key or user id, so that seems like more than just rejecting connections.
[14:56] <sinzui> Mailman is only looking at the From header. It uses the email address to look up the person or team in Lp
[14:57] <sinzui> ^ vish
[14:57] <vish> hmm.. now i need to find such a service, i dont think there would be any service which does that.. :s
[14:57] <vish> sinzui: or could we just add a temporary whitelist for that id till lp bugs team fixes the filter?.. :D
[14:57] <fta> abentley, as i said, it's a regression, and nothing changed on my side
[14:58] <sinzui> vish, we do not control mailman. We cannot reconfigure it. making a small change requires a release
[14:58] <fta> abentley, ..so it has to be something on the server side
[14:59] <abentley> fta: it seems that only lftp is not working.  commandline sftp and Nautilus both work.
[14:59] <vish> sinzui: oh! np.. thanks.. :)
[14:59] <sinzui> vish, have you talked to deryck or gmb about when you can subscribe to new and closed bugs only
[15:00] <sinzui> vish, the feature has been in Lp for years, but it was never enabled. The enabling work is happening now
[15:00] <vish> sinzui: not yet, i was asking you directly here, since the question's task changed and you'd probably no longer get the mail..
[15:00] <fta> abentley, oh, someone just fixed it seconds ago
[15:00] <deryck> sinzui, vish, you can do it now, if you're in the alpha testing team for malone.  Would either of you like in? :-)
[15:00]  * vish crosses fingers.. :)
[15:01] <vish> deryck:  not yet, i'll look for that team now.. :)
[15:01] <sinzui> I certainly do. I will subscribe ~registry to stop the bug mail coming from the 1000+ projects that do not use Lp to track bugs, but Lp seems to think I want the email anyway
[15:01] <deryck> ~malone-alpha, I think.
[15:01] <deryck> restircted team, but apply and I'll approve.
[15:03] <vish> deryck: oh, its restricted, so cant apply. members need to be added there..   my lp id is : "vish"
[15:03] <deryck> vish, ok, I'll add you.
[15:03] <vish> deryck: awesome thanks.. :)
[15:03] <deryck> np
[15:05] <deryck> gmb, can you add ~vish and ~registry (per sinzui's request above) to malone-alpha team?
[15:11] <deryck> oh gmb is away today
[15:11] <deryck> vish, sinzui, I've got a note to get you guys added when gmb is available again.
[15:12] <vish> deryck: thanks..
[15:12] <deryck> np
[16:01] <shadeslayer> so ... i cant upload to a PPA
[16:01] <shadeslayer> its timing out
[16:01] <shadeslayer> is it because im uploading alot of packages at once?
[16:01] <bigjools> shadeslayer: is it hanging with 1k to go on a large package?
[16:01] <shadeslayer> nope.... theyre all translations
[16:01] <shadeslayer>   Uploading kde-l10n-gl_4.5.3-0ubuntu1~lucid1~ppa1.debian.tar.gz: 235k/1005k
[16:01] <shadeslayer> its stuck there
[16:02] <bigjools> are you using plain ftp?
[16:02] <shadeslayer> yes
[16:02] <shadeslayer> wait it started
[16:02] <bigjools> can you try sftp
[16:02] <shadeslayer> its back up :D
[16:02] <shadeslayer> bigjools: its on a loop... i dont want to stop the loop because that will mean i  wont know which were uploaded and which werent
[16:30] <shadeslayer> is there a command to copy all the packages from one ppa to the other? or do i do it via the Web UI?
[16:30] <bigjools> web ui or use the webservice
[16:30] <shadeslayer> bigjools: web service?
[16:30] <bigjools> api
[16:30] <shadeslayer> ahh ....
[16:31] <shadeslayer> via lp shell?
[16:31] <bigjools> you need to specify package names though
[16:31] <shadeslayer> will it take regex? :D
[16:31] <bigjools> no :)
[16:31] <shadeslayer> bah :P
[16:31] <bigjools> it will take substrings IIRC
[16:31] <shadeslayer> the ppa has 88 packages
[16:31] <bigjools> you won't be able to copy them all at once anyway, it will time out
[16:32] <shadeslayer> yeah
[16:32]  * shadeslayer prepares for major copies
[16:46] <kostja_osipov> hello launchpad team! may ask a question here? I've read the manual but found no answer there. I initially registered at launchpad with my email kostja@sun.com. This email is no longer valid. So I changed my primary email to kostja.osipov@gmail.com. However, this new email can not be used to log in to launchpad. Whenever I log in, I must use kostja@sun.com as the login email, and after that launchpad keeps suggesting to add kostja@sun.com to the l
[16:46] <kostja_osipov> Can this be fixed?
[16:52] <kiko> kostja_osipov, yes, I can fix it for you
[16:53] <kiko> kostja_osipov, give me 10 minutes because I'm on the phone though :)
[17:05] <smoser> i'm currently unable to get a bug opened on launchpad
[17:05] <smoser> timeout error
[17:05] <smoser> Trying again in a couple of minutes might work.
[17:05] <smoser> (Error ID: OOPS-1782H1745)
[17:11] <kostja_osipov> kiko: thanks, would be much appreciated
[17:12] <kiko> kostja_osipov, okay I'm off
[17:14] <joey> deryck: I'm sending over vanhoof to talk to you about some bug subscriptions on private projects
[17:15] <joey> deryck: He's got a little of a problem with them and I can't easily puzzle out the answer.
[17:15] <allenap> smoser: There's an INSERT in that OOPS that's being cut off because it's taking too long, ~17s, but it's an insert that should happen near instantaneously.
[17:15] <deryck> joey, gotcha.  will help him out.
[17:15] <joey> thanks deryck
[17:15] <deryck> np
[17:17] <kiko> kostja_osipov, can you give me a URL to your launchpad page?
[17:17] <kostja_osipov> launchpad.net/~kostja
[17:41] <allenap> smoser: I can't find any evidence of database problems, but then stub isn't around and he's really the one I would have wanted to ask. Can you try again? Whatever was blocking you before might have gone of its own accord or been reaped by one of stub's special automated database warriors.
[17:41] <smoser> well, it seems fixed.
[17:41] <smoser> but it was out to lunch for 15 minutes or so, multiple attempts at the time.
[17:43] <allenap> smoser: Mmm. I'll file a bug about this - if I can :) - in case stub is able to diagnose in retrospect.
[18:33] <joey> leonardr: around?
[18:34] <joey> leonardr: is there a better way to get all the members of team?  I am occasionally getting a result which is missing members using this:  canonical_members = lp.people['canonical'].members_collection
[18:34] <joey> leonardr: it's intermittent
[18:34] <joey> leonardr: some days, nobody is missing, today I have 3 missing
[18:38] <leonardr> joey: is the membership changing frequently?
[18:38] <joey> leonardr: don't think so.. it's ~canonical  we do hire from time to time though :-)
[18:39] <joey> leonardr: I do that one association at the start of the script and keep it in memory for the rest of the execution
[18:39] <leonardr> joey: it's also possible the people are shifting around in the list due to changes in their sort order
[18:40] <leonardr> joey: you might have better result setting canonical_members = [m for m in lp.people['canonical'].members]
[18:40] <leonardr> otherwise you'll go to the server every time for a brand new list
[18:40] <joey> leonardr: ok, I'll give that a try, thanks!
[19:08] <joey> leonardr: that worked like a charm brother. Spend up the script execution by an immense amount.
[19:09] <joey> s/spend/sped/
[19:09] <leonardr> great
[19:54] <nuclear_eclipse> hi, I'm trying to use `equivs-build` + `dput` to post some metapackages on my PPA, but the builds get rejected for being "mixed" source/binary, but I'm not sure if/what I can do to resolve that
[20:00] <maxb> nuclear_eclipse: I am unfamiliar with equivs-build, but you need to tell it to build only a source package
[20:01] <nuclear_eclipse> maxb: that's the problem, I'm not sure how to do that, and the manpage doesn't really shed any light
[20:02] <nuclear_eclipse> maxb: do you know of anything else that can turn a simple control+changelog into a metapackage ready for dput/ppa?
[20:03] <nuclear_eclipse> I just didn't want to go through the normal process of creating all the normal debian package structures when equivs can make it dead simple
[20:03] <maxb> Let me set up a dummy equivs package here so I can see what it does
[20:04] <nuclear_eclipse> it seems to just build source + all by default, but I don't see any way to tell it to only build source
[20:04] <nuclear_eclipse> only a way to specify to build i386 or amd64 instead of all
[20:05] <maxb> So, you are using equivs-build --full?
[20:05] <nuclear_eclipse> yes
[20:06] <maxb> It seems to me you have two options:
[20:06] <maxb> 1) Slightly modify the equivs-build script itself
[20:06] <maxb> 2) Mangle the .changes file slightly after it has been built
[20:06] <maxb> Option 1) would involve adding the -S option to the dpkg-buildpackage invocation
[20:06] <nuclear_eclipse> #2 means mangling the .changes and then resigning it manually I suppose?
[20:07] <maxb> Option 2) would involve editing the Architecture field to just source, deleting all the lines referring to .deb files, and then using debsign to resign the .changes
[20:07] <maxb> You probably should also rename it from ending in _amd64.changes (etc.) to _source.changes
[20:08] <nuclear_eclipse> ok
[20:09] <nuclear_eclipse> hmm, I think change equivs-build would be the easiest option...
[20:09] <nuclear_eclipse> but I don't like updating scripts that aren't mine :x
[20:10] <nuclear_eclipse> maxb: trying option 1 first, just to see if that works...
[20:11] <maxb> nuclear_eclipse: Clearly the solution is to add an option and send the fix upstream to Debian :-)
[20:11] <nuclear_eclipse> maxb: ;)
[20:12] <nuclear_eclipse> the question is where to submit the patch to, the equivs package doesn't list a site...
[20:13] <maxb> The equivs package is a Debian native package, meaning that Debian *is* upstream
[20:13] <maxb> So patches should go to the Debian bugtracker, at severity wishlist, tagged patch
[20:14] <nuclear_eclipse> ah, right, thanks
[20:16] <nuclear_eclipse> maxb: success!
[20:16] <nuclear_eclipse> maxb: thank you for the guidance
[20:19] <maxb> np
[21:02] <weather15> Hello Everyone
[21:25] <viraptor> hi all, I'm looking for an answer... if I install launchpad locally, do I also get the ppa building environment too, or is that a separate launchpad.net-only part?
[21:26] <soren> viraptor: If all you want to do is have a way to build packages, installing launchpad locally is unlikely to be something you want to do.
[21:26] <soren> viraptor: launchpad is massive.
[21:27] <viraptor> soren: what I'm really looking for is the ppa environment itself - some setup that has package-building, signing, publishing already solved... I know there are things like sbuild and wanna-build, but they're... let's say - interesting to work with ;)
[21:28] <soren> viraptor: You will find the same is true for Launchpad. Only much moreso.
[21:29] <wgrant> Setting up a working development PPA instance is far easier than dak + wanna-build... as for production, that's probably a bit harder.
[21:29] <wgrant> But why can't you use Launchpad.net?
[21:29] <viraptor> auch... do you know any other projects I could look at? I'd be happy with something that integrates pbuilder + reprepro + apache... web interface completely optional
[21:32] <soren> wgrant: You can get a ppa system running as a standalone thing? You don't need to set up all the rest of launchpad?
[21:33] <wgrant> soren: You need to run the webapp, but you don't need to run codehosting or any of that other stuff.
[21:33] <wgrant> soren: It's not easy, but it's not quite on the level of dak and wanna-build and buildd...
[21:33]  * soren is surprised
[21:33] <soren> That's great!
[21:34] <viraptor> wgrant: is there any article about it? or do I just follow the standard launchpad installation and try to figure it out? ;)
[21:35] <wgrant> viraptor: I wrote https://dev.launchpad.net/Soyuz/HowToUseSoyuzLocally
[21:36] <viraptor> wgrant: thanks a lot :) that looks a lot like what I needed :)
[21:37] <viraptor> also, can I somehow force ppa to build packages for debian? (is the ubuntu requirement only for running launchpad, or also for build environment?)
[21:37] <ecanto> hello.
[21:39] <wgrant> viraptor: It's actually pretty easy to get Launchpad running on Debian, and it's simple to get it to build against Debian (until you want to build against -p-u or security or backports or something).
[21:40] <wgrant> viraptor: The main difficulty is that Launchpad assumes that it controls the distribution's primary archive.
[21:40] <wgrant> So you need to adjust the way it generates the build's sources.list.
[21:40] <viraptor> that's good news - https://dev.launchpad.net/Getting scared me away from debian deployment :)
[21:41] <wgrant> I'm not sure many have done it, but I've published Debian PPAs on Launchpad on Debian just to check that it worked.
[21:42] <wgrant> You need to hack some Ubuntu-specific stuff out of rocketfuel-setup (mainly the universe/multiverse check, IIRC), and manually install python-tickcount and ubuntu-keyring from Ubuntu. Then rocketfuel-setup should work OK on Squeeze.