[00:08] <geser> anyone else seeing connection timeouts when accessing edge?
[00:09] <crimsun> periodically, yes
[01:36] <kermiac> The same user I & numerous others reported is still at it
[01:36] <kermiac> https://edge.launchpad.net/~ubuntunerd-nospammail/+karma
[01:36] <kermiac> he created more issues approx 5 hrs ago & another bug task just over 1 min ago
[01:37] <kermiac> [21:40:10] <kermiac> https://answers.edge.launchpad.net/launchpad/+question/100682
[01:47] <micahg> spm: can you take care of this ^^^
[01:50] <spm> kermiac: which bug has been modified?
[01:50] <spm> the most recent as in
[01:51] <kermiac> I'm not sure, must've been something I'm not subscribed to. Still looking atm. I just noticed he's been at it again, we're discussing it on #ubuntu-bugs atm
[01:52] <micahg> spm: bug 495361 is the latest 1 I have
[01:58] <kermiac> bug 446669 is from 6hrs ago - def after he received the warning
[01:59] <kermiac_> sorry, gotta afk for a while
[02:00] <persia> Um, we can't be sure that the warning was received, only that it was sent.
[02:00] <persia> Some people don't actually read email.
[02:01] <spm> And given the email address, I do wonder if it's been spam trapped or something
[02:02] <spm> persia: your thoughts? I'm about 90% inclined atm to suspend with a note that this is to encourage them to contact us asking why. ???
[02:03] <persia> spm: I'm unsure.  Had there not been an explicit time frame in the warning, I'd be all for suspending now.
[02:03] <spm> yeah. that's the other 10%... :-/
[02:03] <persia> As it is, I think that there would be benefit to sending another notice indicating that continued disruptive behaviour has shortened the timeframe.
[02:03] <spm> good idea; ta.
[02:04] <persia> But it seems to be the major topic of conversation in #ubuntu-bugs, which implies, to me, that it's keeping people from actually working on bugs, which is anti-productive.
[02:04] <lifeless> JFDI
[02:04] <persia> heh.  That was an easy 10% :)
[02:04] <lifeless> 48 hours is way to long to let an idiot continue being an idiot
[02:05] <spm> 1 person and a sense of fairness vs the needs of the many.... :-/
[02:05] <persia> RIght.
[02:05] <lifeless> the many carry bigger bats
[02:06] <persia> But it's probably worth changing the "How do we handle requests for account suspension" documentation to not give a timeframe, and then suspend either after some time without response of if a sufficiently of continued disruption occurs.
[02:06] <persia> Because once the "48-hour" mail is sent, it looks bad not to honor it.
[02:08] <thekorn> what will suspending this user mean? is it just deleting his account. or are there ways to ban him from launchpad?
[02:08] <spm> oki, suspended. In the hope that they do contact us, or read their email... to find out why.
[02:08] <spm> thekorn: suspension. basically locked out.
[02:09] <spm> delete is typically only used in extreme cases; eg obvious spammers for drugs etc
[02:11] <thekorn> ok, so he can get a new @nospam address, setup a new account and start spamming again, and it will take some time again until this attrackts our attention
[02:11] <thekorn> let's hope this does not happen
[02:12] <thekorn> thanks for takeing care of him
[02:12] <micahg> spm: do you know anything about the interaction between bugzilla.mozilla.com and LP?
[02:13] <spm> micahg: a little; it's a moderate source of pain.
[02:13] <micahg> spm: will it break anything in LP if the LP acccount in bugzilla is disabled until we fix syncing?
[02:14] <spm> micahg: no idea; my 2c - do what you need to do; we'll pick up the pieces if needs be.
[02:14] <micahg> spm: k, thanks :)
[02:15] <micahg> upstream was getting frustrated :)
[02:15] <spm> heh, at worst, it identifies a bug in how that process deals with such an event. :-)
[02:15] <spm> fair cop
[02:15]  * wgrant wonders why spamming other bugtrackers isn't a critical bug.
[02:18]  * micahg agrees with wgrant
[02:18] <persia> thekorn: There's no sane way to identify individuals: only email addresses.
[02:20] <thekorn> persia, I know, so my idea is not not supsend such spammers and find ways to handle/revert their changes, in this case we would know who is spamming,
[02:21] <thekorn> maybe permanently redirecting them to staging
[02:21] <persia> thekorn: That's an interesting idea, but probably requires a lot of deep plumbing.
[03:16] <kermiac_> ty spm
[03:17] <spm> np
[08:30] <lool> Hey
[08:30] <lool> I'm facing a weird bug with membership
[08:31] <lool> I got a your membership will expire email in a team I'm admin of
[08:31] <lool> And I can't renew it
[08:31] <lool> https://launchpad.net/~plymouth-dev/+members
[08:31] <lool> I'm supposed to contact one of the *other* administrators for some reason
[08:58] <noodles775> lool, that is weird... one of the registry guys should be around later, but if you've time it'd be worth a bug so it doesn't get lost.
[09:04] <Lord-Readman> Any translations admins or mods here?
[09:05] <noodles775> dpm: ^^?
[09:05] <lool> noodles775: I filed 520848
[09:06] <dpm> Lord-Readman, what's your question (I'm not an LP developer but I can manage the translations imports queue, if that is what you need)
[09:06] <Lord-Readman> well I have approved imports, but they are not imported
[09:07] <Lord-Readman> and usually they do it at the same time
[09:07] <Lord-Readman> what is the difference?
[09:09] <Lord-Readman> https://translations.launchpad.net/~robert-readman/+imports I have 4 approved
[09:09] <Lord-Readman> but not imported
[09:10] <Lord-Readman> if you could take a look dpm that would be great
[09:11] <dpm> Lord-Readman, ah, it's an Ubuntu import. I can take a look, but in the future you might want to ask at #ubuntu-translators where more Ubuntu people with admin rights on the imports queue can have a look at it as well
[09:12] <Lord-Readman> ah sorry
[09:12] <dpm> Lord-Readman, it's just as fine to ask here, no need to apologise :-)
[09:18] <dpm> Lord-Readman, it did not get imported automatically because the importer is trying to figure out the language. I've approved it manually, so no worries, but on subsequent imports I'd recommend changing the name of the PO files you upload to simply en_GB.po, which will speed up the process of them getting imported. In any case, the "Will be imported into English (United Kingdom) (en_GB) translation of virt-manager in Ubuntu Lucid package "virt-manager"" mes
[09:18] <dpm> sage in the imports queue entry shows that it would have been imported eventually
[09:19] <Lord-Readman> ah I normally just upload with the same filename as it gave on the download
[13:18] <edakiri> When searching for bugs within project usb-creator, i am unable to create a search returning bug #457721.  Am I doing something wrong or is there a bug in launchpad?
[13:21] <wgrant> edakiri: That's a bug in the Ubuntu package of usb-creator. Try searching at https://bugs.launchpad.net/ubuntu/+source/usb-creator
[13:39] <edakiri> is there a way to get from 'pick a project' to the +source part?
[13:40] <edakiri> "Search bug reports: One Project: Choose" is what i mean by 'pick a project' .  https://bugs.launchpad.net/
[13:41] <maxb> no
[15:24] <_stink_> hey folks.  i want to submit a feature request for LP, but if i go to https://bugs.launchpad.net/launchpad, there aren't any open bugs.  maybe they're all closed, but this makes me think i should be going elsewhere to submit this.  advice?
[15:43] <deryck> _stink_, we generally file bugs against the launchpad components, i.e. malone, rosetta, soyuz, launchpad-code, launchpad-registry, or launchpad-foundations.
[15:44] <deryck> _stink_, but if you can't work out where to file, you can file against /launchpad and we'll re-target it.
[15:44] <_stink_> deryck: rock on, thanks
[15:44] <deryck> np
[16:01] <lfaraone> Hi, can somebody add a redirect from ~dcteam to ~ubuntu-dc?
[16:01] <lfaraone> * ~ubuntu-us-dc
[16:48] <andrea-bs> lpRN]eIWRe>
[17:12] <persia> andrea-bs: You may want to check backscroll, and, depending on what you find, take some action.
[17:15] <andrea-bs> persia: oops! :-( thank you for the info
[17:16] <persia> andrea-bs: Sorry it took so long to notice :)
[18:21] <tlyu> Launchpad claims it pulls external bug status daily but it looks like #512459 hasn't updated since 2010-02-08 from its corresponding Debian bug. what's up with that?
[18:22] <lfaraone> tlyu: bug status is slightly borked from debian.
[18:22] <deryck> tlyu, we're doing lots of work on our bug syncing currently.  So it can be hit or miss currently.  By sometime in April, this should be solid again.
[18:23] <tlyu> thanks. will unlinking and relinking the bug cause it to update?
[18:23] <deryck> tlyu, no.
[18:24] <deryck> tlyu, the updates are processed offline from Launchpad.  This is part of what we're changing to, so that you can force an update from the UI.
[18:24] <tlyu> ok. if i want the Launchpad state to accurately reflect Debian, should i adjust it manually?
[18:31] <deryck> tlyu, you have to remove the bug watch to update manually.
[18:50] <deryck> jcastro, ping
[18:51] <jcastro> deryck, hi!
[18:55] <micahg> allenap: thanks for working on that syncing bug :)
[20:23] <lfaraone> hi, I'm trying to checkout launchpad using rocketfuel-setup, and bzr is consuming over 900MB, causing my computer to start swapping to disk.
[20:24] <lfaraone> is this *supposed* to happen?
[20:39] <maxb> lfaraone: yikes.... is it going over bzr+ssh or http?
[20:40] <lfaraone> maxb: the latter, I think.
[20:40] <lfaraone> maxb: uh, actually it might be http, I didn't give it my launchpad credentials..
[20:41] <maxb> Well, do you have a ssh key in launchpad, and that ssh key available locally? If not we can rule ssh out straight away
[20:41] <lfaraone> maxb: okay, it's not SSH then :)
[20:42] <maxb> right... well, I've found bzr's dumb http to be pretty awful about big branches
[20:43] <lfaraone> (currently using virt: 1162m, that's more ram than I have on the system!)
[20:43] <lfaraone> maxb: so this is a bug, I take it.
[20:44] <lfaraone> maxb: is there another transport I can use with launchpad, without putting an SSH key on the computer?
[20:45] <maxb> No, there isn't
[20:47] <maxb> I'm trying it here .... not only is it doing a dreadful job of saturating my bandwidth, it's swiftly heading in the direction of a gig of mem
[20:49] <maxb> I killed it because it was getting shockingly slow
[20:50] <maxb> huh, even bzr+ssh seems to have just stalled, too
[20:51] <maxb> This is ridiculous
[20:52] <maxb> I can now safely say that if I needed to branch launchpad afresh, I'm not sure I could, with it behaving the way it is
[20:52] <lifeless> lfaraone: what bzr version ?
[20:52] <lifeless> maxb: and yours ?
[20:53] <maxb> lp:bzr/2.1
[20:53] <lfaraone> lifeless: Bazaar (bzr) 2.0.2
[20:53] <lifeless> lfaraone: 2.1 is a lot better at memory in theory ;)
[20:53] <lifeless> maxb: C extensions built ?
[20:53] <lfaraone> lifeless: well, I'm using what's in the repos.
[20:53] <maxb> lifeless: yes
[20:53] <lifeless> maxb: file a bug please
[20:53] <maxb> So theory isn't being borne out in practice
[20:54] <maxb> lifeless: I'm assuming that "make" in the tree will have done the right thing?
[20:54] <maxb> It certainly looked like it did
[20:54] <lifeless> maxb: make will build the extensions, yes.
[20:55] <lifeless> maxb: if you have bzrlib/*.so numbering ~5 then it did
[20:55] <maxb> I have 14
[20:56] <lifeless> yeah thats fine
[20:58] <maxb> um. Is it expected that I have time to go make a cup of coffee whilst 'bzr heads' runs on my ~/launchpad/lp-branches?
[20:58]  * persia thinks it's the new bzr caffiene-level-check feature running in the background
[20:59] <persia> (or would that be "check-caffiene-level" to match the naming convention?)
[20:59] <lifeless> nothing is expected
[20:59] <lifeless> but I doubt heads uses the fast apis available in 2.1 yet
[21:00] <maxb> There's "fast" and there's "so slow the command might as well not exist" :-/
[21:00] <lifeless> get an lsprof dump of it and file a bug; we can go from there
[21:02] <lfaraone> hm. bazaar is still using 350~mb of ram in ssh+bzr transport mode.
[21:02] <lfaraone> which isn't *as* terrible :)
[21:03] <lifeless> it will be doing far fewer round trips too
[21:03] <lifeless> server side processing is much more efficient
[21:05] <persia> fewer round trips sounds lovely :)
[21:26] <maxb> lfaraone: success yet? :-)
[21:26] <lfaraone> maxb: "[#########\          ] 171815KB   556KB/s | Fetching revisions:Inserting stream                       "
[21:27] <maxb> mhm
[21:27] <maxb> The protocol is annoyingly inefficient
[21:27] <lfaraone> good news is it's only using 108m
[21:28] <maxb> An entire devel repo is only 155MB of data
[21:29] <lfaraone> maxb: uh, should I worry about "bzr: ERROR: Not a branch: "bzr+ssh://bazaar.launchpad.net/~launchpad-pqm/shipit/trunk/"."
[21:29] <maxb> No, that bit's Canonical-proprietary
[21:47] <lfaraone> maxb: now we're working! if only "make schema" were to work more quickly... :)
[23:05] <zobi1> Yesterday, I created a Launchpad branch for our translations to be exported to. Then, I created an empty bazaar branch on my local machine (bzr init) and finally pushed it to Launchpad (bzr push --use-existing-dir lp:wiserearth). I expected the transltion files to be exported to this branch since I associated the two. I still have an empty branch. What step am I missing?
[23:22] <lifeless> zobi1: you ran bzr init twice; don't do that for a single project
[23:22] <lifeless> zobi1: 'init' makes something brand new, what you want is 'branch' - make a new branch of something you've already got
[23:23] <zobi1> lifeless: I don't have anything I would like to put in. I would like to get an export of the translation files that are on Launchpad.
[23:23] <lifeless> hmm, I'm not sure enough of the code bits here sorry
[23:25] <zobi1> lifeless: when I set up the new branch on Launchpad as an export branch for the existing translation files on Launchpad, I expected the branch to be populated with those files. But for some reason that is not happening.
[23:26] <wgrant> It only happens once a day, I believe.
[23:27] <zobi1> For some reason the documentation assumes certain steps to be taken by the users, rather than walk you through.
[23:27] <zobi1> wgrant: I set this up 2 days ago.
[23:27] <zobi1> Anyway to find out what time of the day the export happens?