[00:07] <maco> how do i cancel a build on a ppa?
[00:09] <maxb> maco: you can't
[00:10] <maco> if i delete the source package, does that count?
[00:10] <maxb> If the built hasn't started yet, probably
[00:43] <meoblast001> hi
[00:44] <meoblast001> how long should this be processing for https://code.launchpad.net/~mysticgalaxies/amethyst-mm/devel
[00:48] <ia> hello. i have a question about PPA - could you tell me, please, how can i (if that possible) upload the same package with the same version in different destination series?
[00:52] <mwhudson> ia: i don't think you can
[00:52] <mwhudson> ia: you can upload it to one and copy it to the others though
[00:52] <mwhudson> meoblast001: what do you mean by processing?
[00:52] <mwhudson> meoblast001: if you mean the delay between pushing and your revisions appearing, around two minutes
[00:52] <meoblast001> mwhudson: it finished... i thought it was taking too long and there might be a problem
[00:53] <meoblast001> mwhudson: it took longer than usual
[00:53] <mwhudson> maybe someone pushed a large branch just before you or something
[00:53] <mwhudson> meoblast001: anyway, glad it's working...
[00:53] <meoblast001> ha
[00:53] <meoblast001> thanks
[00:59] <ia> mwhudson: well, i've tried to copy, but i've got error message - "the following sources cannot be copied: same version already has published binaries in the destination archive".
[01:00] <ia> and another question - when i run "dput ppa *.changes", how deciding for which destination series packages will be uploaded? for example, if i have a package for karmic, but in my ppa exists only jaunty as destination series, what should i do if i want upload this package for karmic? i will be very appreciate for any clues.
[01:01] <mwhudson> ia: that bit is controlled by the debian/changelog file
[01:01] <mwhudson> (i think, /me is a bit of a packaging newbie)
[01:02] <james_w> ia: your PPA will accept any series that LP knows about, it doesn't matter that you only have jaunty packages in there so far
[01:02] <james_w> ia: and as for your other question, it's not possible
[01:03] <james_w> you need to change the version number
[01:09] <ia> james_w: so, please, correct me if i wrong - dput uploads package in LP series (even if it doesn't exist in ppa yet), which provided in debian/changelog first line "package (X.Y-KubuntuL~ppaZ) series; urgency=low", right?
[01:09] <james_w> yep
[01:13] <lifeless> jml: I just messed up another review by mail
[01:14] <jml> lifeless: the 'review' vs 'status' thing?
[01:14] <lifeless> no, the leading space
[01:14] <lifeless> https://code.edge.launchpad.net/~therve/txaws/status-eu-support/+merge/6138
[01:14] <jml> ahh, yeah.
[01:14] <lifeless> I don't understand status yet
[01:14] <jml> lifeless: istr you file bugs by email a fair bit -- I guess the leading space for those things is muscle memory
[01:15] <lifeless> so I'm not even trying to set those things
[01:15] <jml> lifeless: I don't think Launchpad understands it very well either.
[01:15] <lifeless> in particular 'resubmit' seems very confused
[01:15] <lifeless> the leading space is for bugs yes, bb doesn't have it and I have a lot of bb muscle memory
[01:16] <lifeless> I'm not aware of any other mail driven system needing the leading space, FWIW
[01:16] <lifeless> Not claiming this should be changed, just giving you the feedback you are asking for
[01:17] <jml> yeah, thanks.
[04:09] <tansell> well, it looks like the amd64 builders are catching up - any ideas on what is happening with the i386 builders? they are still 13 or more hours behind
[05:43] <savvas> how do we remove members of a team?
[05:45] <spm> savvas: go to the members page, and access the "!" beside their name (right hand side of line) - if you have the access to do so naturally. eg: https://edge.launchpad.net/~canonical-losas/+members
[05:46] <spm> then click on the 'deactivate' button. == removed.
[05:46] <savvas> that sets them in former members - any way to remove their name from that list too? :)
[05:46]  * wgrant points out that that doesn't actually remove them - it just deactivates the membership.
[05:46] <wgrant> savvas: No.
[05:46] <wgrant> This is stupid.
[05:47] <spm> wgrant: are you saying that they still have rights/access pertaining to that membership/team? Once deactivated?
[05:47] <wgrant> spm: No, but they appear on the membership list.
[05:47] <wgrant> Which is often undesirable.
[05:48] <wgrant> For both parties.
[05:48] <savvas> I agree, from my point of view at least
[05:48] <savvas> can I ask for the complete removal from the team?
[05:49] <savvas> at answers.l.net I mean
[05:49]  * wgrant hasn't heard of that before, although it would be technically simple.
[05:50] <savvas> the list could also be hidden from the public eye, maybe that would be better hehe
[05:50] <spm> savvas: you can ask, but we don't have any sql-fu (yet) to easily make it so. Do make it very clear you want a full purge, not just a deactivate - and perhaps even why... :-/
[05:51] <savvas> well the guy wants a full purge, he (user hub) was added by a mistake that I made: https://launchpad.net/~gnote/+members
[05:52] <savvas> and showing him as deactivated in a team for his app is kind of silly :)
[05:53] <savvas> well, his and tomboy's to be copyright-correct :P
[05:53] <ajmitch> ah, hub
[05:53] <ajmitch> so why does he want no association whatsoever with the team?
[05:54] <savvas> never asked, since I added him in the first
[05:54] <spm> savvas: sounds fair - put that in a Q and that we (losa's) plz to need some SQL fu to make it so. ;-)
[05:54] <savvas> *place
[05:54] <wgrant> spm: You're not allowed to work out the SQL yourself?
[05:54] <savvas> will do!
[05:55] <spm> wgrant: can. but my sql is rusty as, and following LP development is not a good use of my time - better to ask those who know and work with daily to do so
[05:55] <persia> spm, Is the use of questions to resolve these situations generally accepted, or is it to be reserved for rare cases?
[05:56] <wgrant> spm: That's true.
[05:57] <spm> persia: accepted. very accepted. we may do some serious head scratching internally: but no-ask, no get. This way helps "us" to think about stuff that may have been passed on originally for various reasons.
[05:57]  * spm afk for a bit. bbs.
[05:58] <persia> spm, Thanks.  I'm "deactivated" in a couple groups as a result of confusion on joining.  It's not painful, but it's also not really accurate.  I'll file some questions.
[05:58] <spm> persia: in that case - there may be scope to make this a bug - once is accidental, twice is an issue that needs solving. IMHO of course. :-D
[05:59] <stub> You should only show up as deactivated to team admins btw.
[05:59] <wgrant> Right, there needs to be a way to distinguish between somebody leaving a team, and somebody never really being a member at all.
[05:59] <persia> Oh, it's certainly not uncommon, but most people just live with it.
[05:59] <wgrant> stub: 'Should' as in 'do'?
[05:59] <stub> As in 'it might be a bug if you do'
[06:00] <wgrant> stub: Deactivated memberships have shown to everybody forever.
[06:00]  * persia hunts an example page, believing it to be visible to those not even logged in
[06:00] <wgrant> It is useful in some circumstances to be able to see it.
[06:00] <stub> Yes - just checking. Might want to file a bug - not sure of the use case for displaying deactivated members.
[06:01] <persia> stub, I can see myself listed (incorrectly) at https://edge.launchpad.net/~canonical-arm-dev/+members and I've *never* logged in at edge.
[06:01] <stub> To non-teamadmins anyway.
[06:02] <persia> Well, use case is for looking at turnover, or looking at what people used to do.
[06:03] <persia> Something to honor those who did before, even if they aren't doing it any longer.  It's just there's a difference between "former member" and "never really a member".
[06:03] <wgrant> persia: Exactly. But I'm not sure that can be automatically determined.
[06:03] <persia> Perhaps the bug is that one shouldn't be able to unilaterally make someone else a member of a group, without the subject's approval.
[06:03] <stub> Yer - maybe the registry team can figure out the best fit.
[06:03] <wgrant> It is a very useful distinction to make.
[06:03] <persia> It works that way now for teams, so that one invites a team, but an admin of the invited team has to accept.
[06:05] <savvas> ah that would work as well :)
[06:06] <persia> Anyone else have an opinion on the nature of the bug?  I'm happy to file a bug, but I want to avoid confusion over usecases.
[06:09] <lifeless> well
[06:09] <lifeless> my 2c are that some folk will infer more from 'deactivated' than it means, team admin or not.
[06:09] <lifeless> and that we should be clear in the ui and db about 'joined and left' and 'was never here'
[06:10] <wgrant> Certainly - but how do you determine which?
[06:10] <savvas> the invitation proposal would be great, you invite someone to a team, not forcefully adding them
[06:10] <lifeless> wgrant: let the act of leaving ask?
[06:11] <wgrant> lifeless: Mm, perhaps.
[06:13] <savvas> if anyone wants to take this request it's at https://answers.edge.launchpad.net/launchpad/+question/69833
[06:16] <persia> lifeless, But what about the case where the user never had any interaction to join or leave a team.  In my example case above, everything happened without me interacting with LP.
[06:18] <lifeless> persia: the person that removed you would presumably say 'never here'
[06:23] <persia> OK.  Two potentials for the bug then: 1) users should be asked to confirm when invited to join teams, or 2) The interface for deactivating a member from a team should provide a choice as to whether the member should appear in "Former Members".
[06:24] <persia> Any other proposals?  Voices towards one or the other?
[06:25] <jmarsden> (1) seems more consistent with the way other things in LP work.  BTW, you could do both (1) and (2), they are not mutually incompatible.
[06:26] <lifeless> persia: I'm not proposing solutions
[06:27] <lifeless> persia: my 2c were solely that there is a difference
[06:27] <persia> lifeless, I'm confused.  Have I misinterpreted "lifeless> wgrant: let the act of leaving ask?" ?
[06:27] <lifeless> yes
[06:27] <lifeless> wgrant asked for solutions
[06:28] <jmarsden> Other proposals: show how long they were a member before deactivation... if < 1 day, one infers "mistake" ?
[06:28] <lifeless> my 2c were completed before that; I haven't thought about the problem deeply enough to propose solutions
[06:28] <jmarsden> This would help with existing cases, whereas (1) and (2) only deal with future cases.
[06:29] <persia> jmarsden, Well, that doesn't really cover the mistaken identity issue, often a result of namespace collisions.
[06:30] <jmarsden> True, but it covers the case that started the current discussion, at least.
[06:30] <persia> jmarsden, Well, consider the case where I invite you to a team, and you're on a three-day-weekend, and you get back, and >1 day has passed, and you say "I don't want to be on that team".
[06:31] <jmarsden> That's fine, (1) covers that already.  (3) is an additional way to get an idea, for existing pre-(1) memberships, whether someone "really" was part of a team... at elast for some subset of such mistaken memberships.
[06:32] <persia> I think cleanup is probably better handled through questions.  I'm more interested in fixing the future.
[06:32] <jmarsden> Then (1) should do it.
[06:36] <persia> Which appears to be bug #239909
[06:38] <jmarsden> Agreed.
[06:48] <persia> (2) appears to be bug #121380
[06:48]  * persia stops digging through LP bugs, as (3) isn't likely to be there without an implementation of either (1) or (2)
[07:06] <savvas> hm.. builds take quite a long time, is there anything that halted the queue for i386? https://edge.launchpad.net/~medigeek/+archive/experimental/+build/985758
[07:10] <jmarsden> savvas: I think a bunch of build machines are still doing duty as download servers for Jaunty?
[07:14] <wgrant> savvas: jmarsden is right. See https://launchpad.net/builders.
[07:15] <wgrant> Most of the buildds are currently serving releases.ubuntu.com.
[07:19] <savvas> ok thanks :)
[08:15] <mrooney> Does anyone know if loggerhead can work with subversion?
[08:25] <jml> mrooney: only via bzr-svn
[08:30] <mrooney> jml: interesting, do you know if it has to maintain a "copy" of the entire repository in bzr format to work?
[08:31] <jml> mrooney: you point it at a branch
[08:31] <jml> mrooney: it'll work if the branch is at a remote site
[08:31] <jml> mrooney: but with reduced performance
[08:32] <mrooney> jml: so I can just point it at a subversion branch with a bzr-svn address and it magically works?
[08:32] <jml> mrooney: maybe! I've never tried that.
[08:32] <mrooney> I better tomorrow
[08:33] <mrooney> jml: if you just point it at a branch, does that mean it has a polling interval?
[08:33] <jml> mrooney: no, it gets information as needed AIUI
[08:34] <mwhudson> it should work
[08:34] <mrooney> jml: well I mean unless you connect it via a commit hook, it would seem that it has to poll
[08:34] <mwhudson> but performance might be awful
[08:34] <jml> mrooney: no, it could also get information per HTTP request
[08:34] <mwhudson> mrooney: no, loggerhead opens the branch on each request
[08:34] <mrooney> oooh I see
[08:34] <spm> mrooney: fwiw, if you're looking at just svn repo's you may find websvn to your liking or not? http://websvn.tigris.org/
[08:34] <mwhudson> if the branch url is a subversion url, it'll do the bzr-svn thing each time
[08:35] <mwhudson> mrooney: tell us what happens, i'm curious :)
[08:36] <mrooney> oh okay interesting, is there caching or is it loaded on demand each time?
[08:36] <jml> there's some caching.
[08:36] <jml> also bzr-svn does some (different) caching
[08:37] <mrooney> I am looking for some perhaps alternative to fisheye, and I like using loggerhead on launchpad
[08:37] <mrooney> anyway I shall attempt to report in tomorrow
[08:38] <jml> I look forward to it.
[09:10] <savvas> hm that's odd
[09:10] <savvas> I made a glabels build and it's missing the -data package
[09:11] <savvas> https://edge.launchpad.net/~medigeek/+archive/experimental/+sourcepub/606399/+listing-archive-extra
[09:11] <savvas> pbuilder-dist command works fine locally
[09:12] <wgrant> savvas: It's because i386 hasn't built yet.
[09:13] <wgrant> I presume the -data package is architecture-independent. If it is, it will only be built on i386.
[09:13] <wgrant> (but published on all archs, when it's done)
[09:13] <savvas> ah right :)
[09:18] <soren> Didn't branches used to have a whiteboard?
[09:19] <savvas> they still do when you link them with bugs
[09:20] <savvas> (at the bug page I mean)
[09:20] <wgrant> soren: They were removed, along with branch summaries, in Launchpad 2.2.4.
[09:24] <soren> wgrant: Ah, ok. Thanks.
[09:26]  * soren tries the merge review feature instead.
[09:27] <wgrant> soren: That was said to be the main alternative to the whiteboard.
[09:27]  * maxb wonders if there's a buildd admin around
[09:27] <maxb> molybdenum needs a kicj
[09:28] <maxb> *kick
[09:28] <wgrant> maxb: It'll live for now, but the relevant sysadmin will be up in a few hours.
[09:56] <tansell> are "all" arch ppa's by default built by the i386 builder?
[10:01] <wgrant> tansell: Architecture: all binaries are built by the i386 build. If a package has only Architecture: all binaries, it will only be built on i386.
[10:01] <wgrant> So, yes.
[10:01] <wgrant> Exccept without the 'default' bit.
[10:05] <Hamaryns> hi,
[10:05] <Hamaryns> can I import bugs from my old Trac bug database?
[10:05] <Hamaryns> The server is going to be shut down, I want to import it into Trac totally
[10:27] <savvas> Hamaryns: I am not sure, but from what I can read it's a manual action: https://answers.edge.launchpad.net/malone/+question/18921
[10:28] <savvas> things might have changed though, so please stick around for a little while, maybe someone knows
[10:29] <savvas> otherwise, I think you have to ask for it at http://answers.launchpad.net/malone for such import
[10:32] <Hamaryns> cheers, I have filed a question there already
[10:43] <ripps> The Launchpad sysadmins awake yet?
[11:36] <nicoInattendu> Hello, I'm littyle confuse on the 'meaning' of release in under launchpad. I have to create one when i start a new evolution of my project or when i finish it . I thought it was finishiing but the 'Milestone' seems its at begining.
[11:54] <wgrant> gmb: Bug #371517, which you just triaged, looks to be a duplicate of bug #249532.
[13:18] <thanx54_> hy
[13:18] <thanx54_> german?
[13:19] <thanx54_> hello
[13:19] <thanx54_> ???
[13:19] <thanx54_> p
[13:19] <thanx54_> p
[13:19] <thanx54_> p
[13:19] <thanx54_> p
[13:19] <thanx54_> p
[13:19] <thanx54_> p
[13:19] <thanx54_> p
[13:19] <thanx54_> p
[13:19] <thanx54_> pp
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <noodles775> hallo thanx54_ ? Haben Sie eine Frage?
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> pp
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> pp
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <topaxi> ...
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <wgrant> My German isn't that good, but does 'p' translate to 'I want to get kicked?'
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> pp
[13:20] <noodles775> wgrant: seems so...
[13:20] <topaxi> i think so
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> p
[13:20] <thanx54_> pp
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <wgrant> noodles775: You have access.
[13:21] <thanx54_> pp
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <wgrant> Oh, wait, you don't have a cloak.
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> pp
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:21] <thanx54_> p
[13:22] <thanx54_> nein bloß sind hir
[13:22] <thanx54_> bye
[13:22] <thanx54_> tschüs
[13:22] <topaxi> bye thanx54_
[13:22] <topaxi> :P
[13:22] <noodles775> *phew*
[13:22] <wgrant> How very odd.
[13:22] <topaxi> idiot :>
[13:23] <noodles775> Maybe s/he just had a sticky 'p' key ;)
[13:23] <topaxi> no reason to push return...
[13:32] <bac> hello
[13:33] <rowinggolfer> I see that thanx54 connected from a phone?
[13:34] <rowinggolfer> hey bac
[13:34] <bac> hi rockstar
[13:34] <bac> oops, hi rowinggolfer
[14:16] <thekorn> leonardr, hi, i wanted to report the failed test in lazr.restfulclient, but https://bugs.edge.launchpad.net/lazr.restfulclient/+filebug is not yet enabled, can you open bugs for this project, or should I send you the logs of buildout per mail?
[14:18] <beuno> leonardr, ^
[14:18] <leonardr> thekorn, you should be able to file a bug now
[14:18] <thekorn> yes, thanks
[15:02] <maxb> bac: Hi, could you have someone take a look at molybdenum? It seems to have a stick build. Thanks!
[15:03] <bac> maxb: ok.  thanks for the heads up.
[15:05] <bac> maxb: cprov is looking into it
[15:06] <cprov> maxb: I can't act on a official builder, let me ping someone else.
[15:08] <ripps> cprov: Hey, any word on when we'll get some extra servers to take care of that huge backlog on i386 PPA's
[15:09] <cprov> ripps: not really, I'm sorry :( I will ask that too
[15:20] <cprov> ripps: extra PPA builders (borrowed from other areas) will be available again tomorrow (or Wednesday)
[15:21] <ripps> cprov: okay. Here's another question: why can't we move one of the lpia servers to i386? They seem to have the most free time of the arches
[15:21] <cprov> maxb: pitti is looking at the issue with the source stuck in molybdenum (it seems to be a general problem striping translations in karmic).
[15:23] <maxb> Thanks. (And uhoh. Guess it's lucky it has only bitten once.... so far)
[15:23] <cprov> ripps: maybe, if the situation persists we can look at it.
[15:23] <ripps> cprov: okay, thanks
[15:24] <maxb> Here's a thought I'm having for a potential Soyuz feature request: Have PPAs build into an "incoming" pocket and automatically copy/delete from there into the release pocket when the build succeeds on all archs
[15:25] <maxb> Problem at the moment is that one of the PPAs I maintain was uninstallable for a large chunk of a day after an upload, since it contains a source building an arch-specific and an arch-all package which depend on each other.
[15:26] <maxb> I've worked around this for myself by creating a staging PPA mirroring each primary PPA
[15:26] <cprov> maxb: the 'staging' PPA works fine, IMO. What's the problem with it ?
[15:26] <maxb> However that means there's going to be two copies of my packages on ppa.launchpad.net, which can't help the diskspace situation if everyone starts doing it
[15:26] <cprov> maxb: it's not wasting any resource.
[15:27] <maxb> oh, magic happens behind the scenes so that different URLs on http://ppa.launchpad.net/ hit the same physical file?
[15:27] <cprov> maxb: well, it is sort of wasting space in the staging PPA when it gets released to the 'release' one.
[15:28] <cprov> maxb: no, both files exist on disk.
[15:29] <maxb> Right, so for my packages it doesn't really matter, but if people pulls that trick with openoffice, etc., you need to go buy more disks :-)
[15:29] <cprov> maxb: right
[15:30] <cprov> maxb: it seems like we need 'Move' in addition to the current 'Copy' action.
[15:30] <cprov> maxb: would it make more sense ?
[15:31] <cprov> maxb: of course having pockets on PPAs also sort this out (-proposed vs release)
[15:33] <maxb> Move would also be helpful
[15:33] <cprov> maxb: please file a bug with this feature-request, let's see what other people think about it.
[15:34] <maxb> Will do
[15:37] <maxb> cprov: Do you feel like investigating an oops trying to call archive.syncSource ? OOPS-1220EA124
[15:38] <cprov> maxb: oh, yes, that's on Julian's plate, but he is sick. We know what the problem is. I fix it ASAP.
[15:38] <maxb> Excellent news, thanks :-)
[15:39] <maxb> Meanwhile, I shall screenscape the web-ui :-)
[15:39] <maxb> *scrape
[15:46] <cprov> maxb: yes, copies including binaries never worked.
[16:00] <lorenzosu> HI all. There's some problem in a bug thread I'm subscribed to. How to report?
[16:00] <Pici> I'm not sure where to report this, but it looks like https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/300023 has a lot of inadvertant email comments/spam on it.
[16:00] <lorenzosu> Pici I was here exactly for the same reason!
[16:01] <Pici> lorenzosu: Heh, someone in another channel was just talking about it, thought I'd let #launchpad know.
[16:01] <lorenzosu> I'm actually subscribed to that...
[16:01] <lorenzosu> Today there was a whole chain going on :|
[16:02] <lorenzosu> I wish there was some kind of moderation. Isn0t there a bug asignee?
[16:02] <lazermouse> Hey everyone, I am getting some *spam* email from canonical
[16:03] <Pici> lazermouse: I just reported the issue.
[16:03] <lazermouse> ok
[16:03] <lazermouse> Thanks Pici, you're a good mate :)
[16:03] <lorenzosu> lazermouse Are you subscribed to https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/300023 as well?
[16:03] <lazermouse> I'll see...
[16:03] <lazermouse> yeas
[16:03] <lorenzosu> That's where I'm getting the spam/junk mail
[16:04] <lazermouse> are you?
[16:05] <lazermouse> Pici: where can I see the details of the report?
[16:05] <Pici> lazermouse: I just mentioned it here, I don't know if theres a more formal method.
[16:05] <lazermouse> ok
[16:06] <lorenzosu> lazermouse I was also searching for a "report spam" or something like in other fora but couldn't find it
[16:06] <lazermouse> Yea
[16:07] <lazermouse> I have the exact same problem
[16:07] <lorenzosu> I think this is quite some security threat... if you see that it also lists all bug subsceribers
[16:07] <lazermouse> are you getting the email from guyheavensent@yahoo.com
[16:09] <lorenzosu> lazermouse No
[16:09] <lazermouse> who are you getting it from?
[16:10] <lorenzosu> I got a whole bunch of junt starting from a mail by prasopsuks@gmail.com
[16:10] <lazermouse> lorenzosu: want to start a blog about ubuntu?
[16:11]  * lazermouse just put out the weirdest question ever :)
[16:11] <lorenzosu> It's all logged in the report on the link I sent
[16:11] <lorenzosu> lazermouse Pardon?
[16:11] <lazermouse> em... nothing ;)
[16:11] <lorenzosu> I thought there supposed to be people 'on duty' in this room?
[16:12] <lazermouse>  a sure
[16:12] <Ursinha> lorenzosu, /topic says who's the one
[16:12] <lazermouse> wait
[16:12] <Ursinha> bac is
[16:12] <lazermouse> Yes, we need help here
[16:12] <Ursinha> lazermouse, so ping him :)
[16:12] <lazermouse> bac: could you please help us?
[16:12] <bac> hi lazermouse
[16:12] <lazermouse> k i did
[16:12] <lazermouse> hi bac
[16:12] <lorenzosu> hi bac
[16:12] <bac> sure, let me read up and see what's going on
[16:13] <lazermouse> just read a bit befor this post
[16:13] <lorenzosu> There's some spam/junk going on on this bug https://bugs.launchpad.net/bugs/300023 at least since 30 April
[16:13] <lazermouse> im tired of getting spam email
[16:14] <lazermouse> i have no filter or blacklist
[16:14] <lorenzosu> bac Is there no "report abuse" style system?
[16:14] <bac> lorenzosu: we generally get user feedback here or via the Answers section.
[16:14] <lazermouse> I say ban the user that has this email address guyheavensent@yahoo.com
[16:15] <lazermouse> he is spamming
[16:15] <lorenzosu> bac Ok. thank you. I'm sure you have recognised the problem and know how to take care of it.
[16:16] <lorenzosu> lazermouse I'm sure the launchpad staff will know how to handle it now they've been told.
[16:16] <bac> lorenzosu: i see the spam from praveen.
[16:17] <lorenzosu> bac To me it looks like spam started by prasopsuk on 30 April
[16:17] <lazermouse> yes
[16:17] <lazermouse> if i get more spam email, I'll be back here :\
[16:17] <lazermouse> =-O
[16:17] <lorenzosu> I was mislead at first, thought the slides had something to do with the bug but hadn't actually followed the link, then today there was a huge mass of emails and I actually saw the problem
[16:18] <lazermouse> i already have six messages
[16:18] <bac> so, what's the issue with guyheavensent?  he doesn't seem to be disruptive
[16:18] <lazermouse> he's the one sending me the email
[16:19] <lazermouse> i had a pastebin of the message
[16:19] <lazermouse> http://pastebin.com/m39aff13c
[16:20] <lorenzosu> Yes I think he's just reacting to all the spam and is a little p***** off.
[16:21] <lorenzosu> The 'real' spam/disruption started with prasopsuks@gmail.com
[16:21] <lazermouse> ban them
[16:28] <bac> lazermouse: yes, i think you're correct.
[16:28] <lazermouse> do it as quick as possible :)
[16:28] <lorenzosu> bac Ok I take it you are dealing with the problem. Thanks for the help
[16:28] <bac> lazermouse , lorenzosu: but there isn't much we can do if people continue to reply to the bug email.  hopefully it will calm down soon
[16:29] <lorenzosu> bac No one can 'administrate' the bug and remove the irrelevant emails?
[16:29] <lazermouse> just delete their launchpads accounts
[16:30] <lazermouse> and ban thier ip's
[16:30] <bac> lorenzosu: the inappropriate comments can be hidden but that won't quell the 'reply all' email storm.
[16:30] <lorenzosu> bac Would it be wise to have some 'moderation' mechanism for replies?
[16:32] <bac> lorenzosu: i was just thinking about that.
[16:33] <lorenzosu> bac I guess though that would make it harder to actually do the reporting
[16:33] <bac> lorenzosu: a way to temporarily suspend bug mail would be nice in these situations until everyone calmed down
[16:34] <bac> lorenzosu: care to file a bug against launchpad for such an administrative feature?
[16:35] <lorenzosu> bac not sure I can do it right now, but sure if you point me to where to do it and maybe a little advice on how
[16:43] <bac> lorenzosu: that's ok.  i'll do it.
[16:43] <lazermouse> id love to be able to deal with spammers on launchpad :D
[16:43] <lorenzosu> bac thanks
[16:44] <bac> np
[16:47] <lazermouse> yes, thanks bac
[17:50] <Demophobie> Hi!
[17:51] <Demophobie> "Oops"-Bugs on the Launchpad Site will be fixed without reporting?
[17:52] <Demophobie> i have some oops-bugs on my translation site on launchpad
[18:19] <Jeruvy> sorry if this sounds like a troll, but is launchpad always slow or is it just me?
[18:23] <exarkun> Jeruvy: It sounds like a troll because you haven't actually provided enough information for anyone to give you a meaningful answer.
[18:24] <exarkun> Give more detail about what you find to be slow.
[18:26] <Jeruvy> :) fair enough.  Well I click on a link in a email,  then the browser opens a tab, and I wait 30 secs for it to load, sometimes it times out (site taking too long).
[18:27] <exarkun> Links to any part of Launchpad?  Or just links to one part, like to bugs in the bug tracker?
[18:28] <Jeruvy> Doesn't matter where, overview, bugs, answers.   I am pretty much just in the ubuntu area, sometimes I wander tho.
[18:29] <exarkun> The front page loads in less than a second for me.  Sometimes bug pages take a couple or a few seconds.  How long does it take you to load this page?  https://bugs.launchpad.net/pyopenssl/+bug/322813
[18:30] <Jeruvy> 8.5 seconds, that was pretty good.
[18:31] <exarkun> That's only a little bit slower than it loads for me, so at least for that page, your experience seems normal.
[18:32] <exarkun> Do you have an example of a link that takes much longer to load for you?
[18:33] <Jeruvy> ok, thanks for confirming it's normal.  Not at the moment, I'd say 8ish seconds is about the average wait for me today
[18:36] <qball> Hi, I am looking for some help with importing of a template. I have added it a while back, but it still idles in the queue. (project gmpc, template gmpc-dynamic-plugin)
[18:43] <mrooney> If I want to give loggerhead a look-see, does anyone know if I should use 1.10 or trunk?
[18:45] <rockstar> mrooney, I'd say trunk.
[18:49] <mrooney> Hm ./serve-branches is telling me this svn+http:// address is not a directory
[18:50] <mrooney> maybe I'll see if #bzr knows of this!
[18:54] <Nafallo> interesting... when I'm logged in to edge and click a URL somewhere that brings me to prod I'm not logged in :-(
[18:54] <Nafallo> but if I alter the URL to be edge again I'm suddently logged in.
[18:55] <beuno_> flacoste_afk, kiko, I've been getting that same behaviour  ^
[18:55] <beuno_> (ie, no redirects)
[18:56] <flacoste> beuno: well the login on prod is separate from edge
[18:56] <flacoste> but i think they were messing with the redirect
[18:56] <flacoste> the automatic redirect that is
[18:56] <flacoste> might be related
[18:57] <beuno> flacoste, right, that's expected. Not being redirected isn't
[18:57] <kiko> flacoste, AFAIK that RT was not actioned yet
[18:57] <flacoste> so this is not a new behaviour
[18:57] <kiko> flacoste, or are you talking about something else?
[18:57] <flacoste> no that's what i was talking about
[18:58] <flacoste> beuno, Nafallo: we only redirect from prod to edge once you are logged on prod
[18:58] <beuno> flacoste, it's odd that this happened to us at the same time, no?
[18:58] <Nafallo> dooh.
[18:58] <beuno> I had to log in last night to production after...  4 months?  5?
[18:58] <beuno> doesnt
[18:58] <beuno> doesn't prod look for an edge cookie?
[19:00] <Nafallo> nice. my password isn't firefox-saved on production
[19:00]  * Nafallo goes to find it
[19:01] <elmo> Nafallo: err, your edge one is the same?
[19:03] <Nafallo> elmo: sure. but I think firefox saved them either per domain or per URL, so I normally doesn't need to type in my 40+ char passphrase :-)
[19:04] <Nafallo> found it thou, and I'm logged in and re-directed.
[19:12] <Jeruvy> exarkun: hmm some insight, I've noticed that gmail's redirector seems to be incurring most of the delay.  Once the proper URL is loaded it's good and fast.
[19:40] <kiko> beuno_, the sessions seem to have been expired
[19:41] <beuno> kiko, ah!  makes sense
[19:41] <kiko> beuno, I had to relogin as well this weekend
[19:42] <beuno> kiko, so expiries are server-side?
[19:42] <kiko> if we clear the session DB.. yeah
[19:43] <beuno> ah
[19:43]  * beuno learns stuff
[20:31] <Demophobie> Hey - Are there Launchpad statistics anywhere? Most commit's etc?
[20:54] <bac> Demophobie: there are not individual stats.  it's all rolled into the mysterious karma.
[21:04] <Mez> has LP recently changed to not allow you to login with your alternate emails ?
[21:19] <mthaddon> Mez: I believe it now auto logs you in - try manually logging out and you should then be able to login fine
[21:20] <mthaddon> Mez: auto logs you in *if you've logged in previously* that is :)
[21:26] <rowinggolfer> 22 minutes ago I pushed revision 50. how come bzr update on laptop no 2 still reports Tree is up to date at revision 49.???
[21:26] <rowinggolfer> when I use ~bzr update
[21:26] <rowinggolfer> what am I missing?
[21:26] <mwhudson> rowinggolfer: you probably want bzr pull
[21:27] <rowinggolfer> cool... that's done it
[21:27]  * rowinggolfer hangs head for using a subversion command
[21:27] <beuno> mwhudson, there have been a few reports on the mirroring taking much longer than before the rollout
[21:27] <beuno> may or may not be related
[21:28] <beuno> ask statik about it  :)
[21:28] <statik> whos on fire?
[21:28] <Snova> It does seem to (noticed it yesterday), but I don't think it takes *that* long.
[21:28] <mwhudson> beuno: mirroring or scanning?
[21:28] <beuno> mwhudson, mirroring
[21:28] <statik> mwhudson: yeah, scan after push used to be pretty snappy, but this last week or so it's been like 15 minutes or more sometimes
[21:28] <mwhudson> hmmm
[21:29] <mwhudson> i wonder if people have been pushing lots of openoffice branches :)
[21:29] <mwhudson> nothing really should have changed here in the rollout, fwiw
[21:30] <mwhudson> statik: can you give me the name of a branch you've had this problem with?
[21:30] <mwhudson> (and some idea of when you had the problem would be great too)
[21:34] <Mez> mthaddon: no, I was trying to login using the normal login details I use, but it wouldnt let me in unless I used the primary email.
[21:34] <Mez> (though edge did)
[21:41] <epsilon_0> hi, i commited a revision to launchpad, and then i "uncommit", but now i see it was only local , i could i uncommit the latest revision in the server?
[21:41] <epsilon_0> *how
[21:42] <beuno> epsilon_0, push again
[21:44] <epsilon_0> i tried
[21:44] <epsilon_0> it says i must merge
[21:44] <LarstiQ> epsilon_0: push --overwrite
[21:44] <epsilon_0> oh, ok
[21:44] <epsilon_0> let me try
[21:45] <exarkun> epsilon_0: note that anyone who checked out your branch after you did that commit will be sad, after you do this
[21:45] <epsilon_0> its ok, im working solo for now
[21:45] <epsilon_0> which is also sad
[21:47] <rowinggolfer> epsilon_0: what are you working on, out of interest
[21:47] <epsilon_0> im working on a launcher for Windows, called MightyBox
[21:47] <epsilon_0> screenshots: http://www.flickr.com/photos/37627929@N03/
[21:48] <epsilon_0> what do u think
[21:49] <rowinggolfer> pretty
[21:49] <epsilon_0> :)
[21:49] <epsilon_0> u work on Windows?
[21:49] <rowinggolfer> nope.
[21:49] <epsilon_0> i figured :)
[21:49] <epsilon_0> u guys have Do
[21:50] <rowinggolfer> I am an ubuntu fanboy 110%
[21:50] <epsilon_0> i am too actually
[21:50] <epsilon_0> Ubuntu is awsome
[21:50] <rowinggolfer> so why are you making the windows desktop a nicer place?
[21:51] <epsilon_0> lol, well. as a student i work on Windows, its much easier, with Word, skype, messenger, and not the parallels which does not equal
[21:52] <epsilon_0> and if i am successful with MightyBox, ill defenitly port it to Linux
[21:52] <epsilon_0> the core is much more advanced than gnome d
[21:52] <epsilon_0> do
[21:53] <rowinggolfer> well good luck!
[21:53] <epsilon_0> thanks
[22:02] <Demophobie> someone here who can help me with languages?
[22:43] <statik> mwhudson: sorry about disappearing on you there. one of the branches was lp:~statik/ubunet/open-folder
[22:44] <statik> within the last couple of hours
[22:44] <mwhudson> statik: thanks
[22:48] <persia> bac, Do you need information from me on my team merge question, or just LOSA action?
[23:19] <wgrant> cprov: Is gina not working? The Debian import seems out of date.
[23:22] <cprov> wgrant: yes, last run was 14:00 BST (2x a day still)
[23:23] <cprov> wgrant: on a mirror from 12:52:44 UTC
[23:24] <wgrant> cprov: Hrm, let me check the archive indices. There's a package from a month ago that hasn't been imported yet.
[23:25] <cr3> if I integrate my site with launchpad openid, how can I have a nice label in the login interface instead of the URL for my site?
[23:25] <wgrant> cr3: Ask a Question, I believe.
[23:25] <wgrant> cprov: It seems gina is fine, but there are packages in the Debian pool that aren't in the right place in the indices that I can see.
[23:26]  * wgrant hunts.
[23:26] <wgrant> cprov: Sorry for the noise.
[23:26] <cprov> wgrant: you mean the debian indexes are broken ?
[23:27] <cprov> wgrant: better, pool/index mismatch ?
[23:28] <poolie> beuno: (if still awake) what do you think of the ui proposal in https://bugs.edge.launchpad.net/malone/+bug/277352
[23:28] <poolie> i wish for this all the time...
[23:28]  * beuno looks
[23:28] <wgrant> cprov: It looks like it was improperly automatically removed a week after it was published (nearly a month ago), but is still sitting in pool because there are binaries.
[23:29] <wgrant> cprov: Soyuz's UI makes this more obvious!
[23:29] <beuno> poolie, I think it's a good idea
[23:29] <beuno> will triage saying so
[23:29] <cprov> wgrant: YAY, there is a first time for everything :)
[23:29] <wgrant> cprov: Odd that gina didn't pick it up in the 5 days it was sitting in unstable, though.
[23:30] <wgrant> (xserver-xorg-input-synaptics 1.1.0)
[23:30] <cprov> wgrant: we had a period of failure ...
[23:30] <wgrant> cprov: Aha.
[23:31] <cprov> wgrant: right after the 2.2.3 rollout (for few days)
[23:31] <wgrant> cprov: That makes sense then. Thanks!
[23:31] <cprov> wgrant: cool, np.
[23:40] <poolie> jml, do you know off hand if there's a bug for wanting an edge codehost? i can't find one
[23:42] <jml> poolie: there is no bug
[23:43] <jml> poolie: it's not the sort of thing we can solve by coding.
[23:43] <jml> poolie: there's an RT ticket.
[23:43] <poolie> do you mind if i open one as a handle for it?
[23:43] <jml> poolie: a little.
[23:43] <poolie> ok
[23:43] <jml> poolie: can we just subscribe you to the RT ticket?
[23:44] <poolie> i don't know! good question :)
[23:44] <poolie> i'll try
[23:44] <poolie> apparently i don't have the number for it
[23:45] <poolie> it's not a big deal
[23:45] <ripps> When package is in status: Dependency waiting, will it automatically resume when the dependency is added to the ppa?
[23:46] <wgrant> ripps: Yes.
[23:47] <ripps> wgrant: so it's safe to add a git version to a source packages build-deps? Ex. (0.18.1+git090504)
[23:47] <ripps> I don't want to wake up in the morning and have to restart it.
[23:48] <poolie> kiko, still busy?
[23:48] <wgrant> ripps: There's nothing special about git versions, so yes.
[23:49] <ripps> wgrant: well some packages of mine are going through some api changes, and this kill some plugin packages if they're compiled to an older version of the original package
[23:49] <wgrant> ripps: Right, but Soyuz knows nothing about that.
[23:50] <wgrant> It just knows what you tell it in the Build-Depends line, so will obey whatever you put there.
[23:50] <ripps> okay, cool now I can be sure the plugins build to a specific package, and I don't have to wait until the original package is published to upload the plugins
[23:51] <wgrant> ripps: Yep. That's a useful feature.
[23:57] <bac> persia: the losas have it.