[00:07] how do i cancel a build on a ppa? [00:09] maco: you can't [00:10] if i delete the source package, does that count? [00:10] If the built hasn't started yet, probably === abentley2 is now known as abentley [00:43] hi === spm_ is now known as spm [00:44] how long should this be processing for https://code.launchpad.net/~mysticgalaxies/amethyst-mm/devel [00:48] 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] ia: i don't think you can [00:52] ia: you can upload it to one and copy it to the others though [00:52] meoblast001: what do you mean by processing? [00:52] meoblast001: if you mean the delay between pushing and your revisions appearing, around two minutes [00:52] mwhudson: it finished... i thought it was taking too long and there might be a problem [00:53] mwhudson: it took longer than usual [00:53] maybe someone pushed a large branch just before you or something [00:53] meoblast001: anyway, glad it's working... [00:53] ha [00:53] thanks === abentley1 is now known as abentley [00:59] 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] 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] ia: that bit is controlled by the debian/changelog file [01:01] (i think, /me is a bit of a packaging newbie) [01:02] 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] ia: and as for your other question, it's not possible [01:03] you need to change the version number [01:09] 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] yep [01:13] jml: I just messed up another review by mail [01:14] lifeless: the 'review' vs 'status' thing? [01:14] no, the leading space [01:14] https://code.edge.launchpad.net/~therve/txaws/status-eu-support/+merge/6138 [01:14] ahh, yeah. [01:14] I don't understand status yet [01:14] lifeless: istr you file bugs by email a fair bit -- I guess the leading space for those things is muscle memory [01:15] so I'm not even trying to set those things [01:15] lifeless: I don't think Launchpad understands it very well either. [01:15] in particular 'resubmit' seems very confused [01:15] the leading space is for bugs yes, bb doesn't have it and I have a lot of bb muscle memory [01:16] I'm not aware of any other mail driven system needing the leading space, FWIW [01:16] Not claiming this should be changed, just giving you the feedback you are asking for [01:17] yeah, thanks. === abentley1 is now known as abentley === savvas_ is now known as savvas === deadoomik is now known as deadoomik|sleep [04:09] 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 === abentley1 is now known as abentley [05:43] how do we remove members of a team? [05:45] 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] then click on the 'deactivate' button. == removed. [05:46] 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] savvas: No. [05:46] This is stupid. [05:47] wgrant: are you saying that they still have rights/access pertaining to that membership/team? Once deactivated? [05:47] spm: No, but they appear on the membership list. [05:47] Which is often undesirable. [05:48] For both parties. [05:48] I agree, from my point of view at least [05:48] can I ask for the complete removal from the team? [05:49] at answers.l.net I mean [05:49] * wgrant hasn't heard of that before, although it would be technically simple. [05:50] the list could also be hidden from the public eye, maybe that would be better hehe [05:50] 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] 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] and showing him as deactivated in a team for his app is kind of silly :) [05:53] well, his and tomboy's to be copyright-correct :P [05:53] ah, hub [05:53] so why does he want no association whatsoever with the team? [05:54] never asked, since I added him in the first [05:54] 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] *place [05:54] spm: You're not allowed to work out the SQL yourself? [05:54] will do! [05:55] 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] spm, Is the use of questions to resolve these situations generally accepted, or is it to be reserved for rare cases? [05:56] spm: That's true. [05:57] 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] 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] 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] You should only show up as deactivated to team admins btw. [05:59] 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] Oh, it's certainly not uncommon, but most people just live with it. [05:59] stub: 'Should' as in 'do'? [05:59] As in 'it might be a bug if you do' [06:00] 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] It is useful in some circumstances to be able to see it. [06:00] Yes - just checking. Might want to file a bug - not sure of the use case for displaying deactivated members. [06:01] 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] To non-teamadmins anyway. [06:02] Well, use case is for looking at turnover, or looking at what people used to do. [06:03] 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] persia: Exactly. But I'm not sure that can be automatically determined. [06:03] 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] Yer - maybe the registry team can figure out the best fit. [06:03] It is a very useful distinction to make. [06:03] 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] ah that would work as well :) [06:06] 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] well [06:09] my 2c are that some folk will infer more from 'deactivated' than it means, team admin or not. [06:09] and that we should be clear in the ui and db about 'joined and left' and 'was never here' [06:10] Certainly - but how do you determine which? [06:10] the invitation proposal would be great, you invite someone to a team, not forcefully adding them [06:10] wgrant: let the act of leaving ask? [06:11] lifeless: Mm, perhaps. [06:13] if anyone wants to take this request it's at https://answers.edge.launchpad.net/launchpad/+question/69833 [06:16] 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] persia: the person that removed you would presumably say 'never here' [06:23] 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] Any other proposals? Voices towards one or the other? [06:25] (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] persia: I'm not proposing solutions [06:27] persia: my 2c were solely that there is a difference [06:27] lifeless, I'm confused. Have I misinterpreted "lifeless> wgrant: let the act of leaving ask?" ? [06:27] yes [06:27] wgrant asked for solutions [06:28] Other proposals: show how long they were a member before deactivation... if < 1 day, one infers "mistake" ? [06:28] my 2c were completed before that; I haven't thought about the problem deeply enough to propose solutions [06:28] This would help with existing cases, whereas (1) and (2) only deal with future cases. [06:29] jmarsden, Well, that doesn't really cover the mistaken identity issue, often a result of namespace collisions. [06:30] True, but it covers the case that started the current discussion, at least. [06:30] 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] 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] I think cleanup is probably better handled through questions. I'm more interested in fixing the future. [06:32] Then (1) should do it. [06:36] Which appears to be bug #239909 [06:36] Launchpad bug 239909 in launchpad-foundations "Team Administrator can arbitrarily add members without any action from the LP user" [Undecided,Confirmed] https://launchpad.net/bugs/239909 [06:38] Agreed. === savvas is now known as medigeek === medigeek is now known as savvas [06:48] (2) appears to be bug #121380 [06:48] Launchpad bug 121380 in launchpad-foundations "Deactivated/expired members show up on Members page forever" [Low,Triaged] https://launchpad.net/bugs/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] 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] savvas: I think a bunch of build machines are still doing duty as download servers for Jaunty? [07:14] savvas: jmarsden is right. See https://launchpad.net/builders. [07:15] Most of the buildds are currently serving releases.ubuntu.com. [07:19] ok thanks :) [08:15] Does anyone know if loggerhead can work with subversion? === jamesh_ is now known as jamesh [08:25] mrooney: only via bzr-svn [08:30] jml: interesting, do you know if it has to maintain a "copy" of the entire repository in bzr format to work? [08:31] mrooney: you point it at a branch [08:31] mrooney: it'll work if the branch is at a remote site [08:31] mrooney: but with reduced performance [08:32] jml: so I can just point it at a subversion branch with a bzr-svn address and it magically works? [08:32] mrooney: maybe! I've never tried that. [08:32] I better tomorrow [08:33] jml: if you just point it at a branch, does that mean it has a polling interval? [08:33] mrooney: no, it gets information as needed AIUI [08:34] it should work [08:34] jml: well I mean unless you connect it via a commit hook, it would seem that it has to poll [08:34] but performance might be awful [08:34] mrooney: no, it could also get information per HTTP request [08:34] mrooney: no, loggerhead opens the branch on each request [08:34] oooh I see [08:34] 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] if the branch url is a subversion url, it'll do the bzr-svn thing each time [08:35] mrooney: tell us what happens, i'm curious :) [08:36] oh okay interesting, is there caching or is it loaded on demand each time? [08:36] there's some caching. [08:36] also bzr-svn does some (different) caching [08:37] I am looking for some perhaps alternative to fisheye, and I like using loggerhead on launchpad [08:37] anyway I shall attempt to report in tomorrow [08:38] I look forward to it. [09:10] hm that's odd [09:10] I made a glabels build and it's missing the -data package [09:11] https://edge.launchpad.net/~medigeek/+archive/experimental/+sourcepub/606399/+listing-archive-extra [09:11] pbuilder-dist command works fine locally [09:12] savvas: It's because i386 hasn't built yet. [09:13] I presume the -data package is architecture-independent. If it is, it will only be built on i386. [09:13] (but published on all archs, when it's done) [09:13] ah right :) [09:18] Didn't branches used to have a whiteboard? [09:19] they still do when you link them with bugs [09:20] (at the bug page I mean) [09:20] soren: They were removed, along with branch summaries, in Launchpad 2.2.4. [09:24] wgrant: Ah, ok. Thanks. [09:26] * soren tries the merge review feature instead. [09:27] 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] molybdenum needs a kicj [09:28] *kick [09:28] maxb: It'll live for now, but the relevant sysadmin will be up in a few hours. [09:56] are "all" arch ppa's by default built by the i386 builder? [10:01] 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] So, yes. [10:01] Exccept without the 'default' bit. [10:05] hi, [10:05] can I import bugs from my old Trac bug database? [10:05] The server is going to be shut down, I want to import it into Trac totally [10:27] 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] things might have changed though, so please stick around for a little while, maybe someone knows [10:29] otherwise, I think you have to ask for it at http://answers.launchpad.net/malone for such import [10:32] cheers, I have filed a question there already [10:43] The Launchpad sysadmins awake yet? [11:36] 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] gmb: Bug #371517, which you just triaged, looks to be a duplicate of bug #249532. [11:54] Launchpad bug 371517 in malone "say "you're not logged in" not "you are not the bug assignee..." when applicable" [Medium,Triaged] https://launchpad.net/bugs/371517 [11:54] Launchpad bug 249532 in malone "Bug report says "You are not the assignee nor the maintainer", when you are or that's not relevant" [Undecided,Confirmed] https://launchpad.net/bugs/249532 === stub1 is now known as stub [13:18] hy [13:18] german? [13:19] hello [13:19] ??? [13:19] p [13:19] p [13:19] p [13:19] p [13:19] p [13:19] p [13:19] p [13:19] p [13:19] pp [13:20] p [13:20] p [13:20] p [13:20] p [13:20] p [13:20] hallo thanx54_ ? Haben Sie eine Frage? [13:20] p [13:20] p [13:20] p [13:20] p [13:20] p [13:20] p [13:20] pp [13:20] p [13:20] p [13:20] p [13:20] p [13:20] pp [13:20] p [13:20] p [13:20] ... [13:20] p [13:20] p [13:20] My German isn't that good, but does 'p' translate to 'I want to get kicked?' [13:20] p [13:20] p [13:20] p [13:20] p [13:20] pp [13:20] wgrant: seems so... [13:20] i think so [13:20] p [13:20] p [13:20] p [13:20] pp [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] noodles775: You have access. [13:21] pp [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] Oh, wait, you don't have a cloak. [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] pp [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:21] p [13:22] nein bloß sind hir [13:22] bye [13:22] tschüs [13:22] bye thanx54_ [13:22] :P [13:22] *phew* [13:22] How very odd. [13:22] idiot :> [13:23] Maybe s/he just had a sticky 'p' key ;) [13:23] no reason to push return... === bac changed the topic of #launchpad to: https://launchpad.net/ | Help contact: bac | Join https://launchpad.net/~launchpad-users | Channel logs: http://irclogs.ubuntu.com | karma count change: http://blog.launchpad.net/general/karma-where-did-mine-go [13:32] hello [13:33] I see that thanx54 connected from a phone? [13:34] hey bac [13:34] hi rockstar [13:34] oops, hi rowinggolfer [14:16] 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] leonardr, ^ [14:18] thekorn, you should be able to file a bug now [14:18] yes, thanks [15:02] bac: Hi, could you have someone take a look at molybdenum? It seems to have a stick build. Thanks! [15:03] maxb: ok. thanks for the heads up. [15:05] maxb: cprov is looking into it [15:06] maxb: I can't act on a official builder, let me ping someone else. [15:08] 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] ripps: not really, I'm sorry :( I will ask that too [15:20] ripps: extra PPA builders (borrowed from other areas) will be available again tomorrow (or Wednesday) [15:21] 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] 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] Thanks. (And uhoh. Guess it's lucky it has only bitten once.... so far) [15:23] ripps: maybe, if the situation persists we can look at it. [15:23] cprov: okay, thanks [15:24] 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] 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] I've worked around this for myself by creating a staging PPA mirroring each primary PPA [15:26] maxb: the 'staging' PPA works fine, IMO. What's the problem with it ? [15:26] 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] maxb: it's not wasting any resource. [15:27] oh, magic happens behind the scenes so that different URLs on http://ppa.launchpad.net/ hit the same physical file? [15:27] maxb: well, it is sort of wasting space in the staging PPA when it gets released to the 'release' one. [15:28] maxb: no, both files exist on disk. [15:29] 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] maxb: right [15:30] maxb: it seems like we need 'Move' in addition to the current 'Copy' action. [15:30] maxb: would it make more sense ? [15:31] maxb: of course having pockets on PPAs also sort this out (-proposed vs release) [15:33] Move would also be helpful [15:33] maxb: please file a bug with this feature-request, let's see what other people think about it. [15:34] Will do [15:37] cprov: Do you feel like investigating an oops trying to call archive.syncSource ? OOPS-1220EA124 [15:38] 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] Excellent news, thanks :-) [15:39] Meanwhile, I shall screenscape the web-ui :-) [15:39] *scrape [15:46] maxb: yes, copies including binaries never worked. [16:00] HI all. There's some problem in a bug thread I'm subscribed to. How to report? [16:00] 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] Launchpad bug 300023 in sun-java6 "package sun-java6-jre None [modified: /var/lib/dpkg/info/sun-java6-jre.list] failed to install/upgrade: subprocess pre-installation script returned error exit status 1" [Undecided,Invalid] [16:00] Pici I was here exactly for the same reason! [16:01] lorenzosu: Heh, someone in another channel was just talking about it, thought I'd let #launchpad know. [16:01] I'm actually subscribed to that... [16:01] Today there was a whole chain going on :| [16:02] I wish there was some kind of moderation. Isn0t there a bug asignee? [16:02] Hey everyone, I am getting some *spam* email from canonical [16:03] lazermouse: I just reported the issue. [16:03] ok [16:03] Thanks Pici, you're a good mate :) [16:03] lazermouse Are you subscribed to https://bugs.launchpad.net/ubuntu/+source/sun-java6/+bug/300023 as well? [16:03] Launchpad bug 300023 in sun-java6 "package sun-java6-jre None [modified: /var/lib/dpkg/info/sun-java6-jre.list] failed to install/upgrade: subprocess pre-installation script returned error exit status 1" [Undecided,Invalid] [16:03] I'll see... [16:03] yeas [16:03] That's where I'm getting the spam/junk mail [16:04] are you? [16:05] Pici: where can I see the details of the report? [16:05] lazermouse: I just mentioned it here, I don't know if theres a more formal method. [16:05] ok [16:06] lazermouse I was also searching for a "report spam" or something like in other fora but couldn't find it [16:06] Yea [16:07] I have the exact same problem [16:07] I think this is quite some security threat... if you see that it also lists all bug subsceribers [16:07] are you getting the email from guyheavensent@yahoo.com [16:09] lazermouse No [16:09] who are you getting it from? [16:10] I got a whole bunch of junt starting from a mail by prasopsuks@gmail.com [16:10] lorenzosu: want to start a blog about ubuntu? [16:11] * lazermouse just put out the weirdest question ever :) [16:11] It's all logged in the report on the link I sent [16:11] lazermouse Pardon? [16:11] em... nothing ;) [16:11] I thought there supposed to be people 'on duty' in this room? [16:12] a sure [16:12] lorenzosu, /topic says who's the one [16:12] wait [16:12] bac is [16:12] Yes, we need help here [16:12] lazermouse, so ping him :) [16:12] bac: could you please help us? [16:12] hi lazermouse [16:12] k i did [16:12] hi bac [16:12] hi bac [16:12] sure, let me read up and see what's going on [16:13] just read a bit befor this post [16:13] There's some spam/junk going on on this bug https://bugs.launchpad.net/bugs/300023 at least since 30 April [16:13] Launchpad bug 300023 in sun-java6 "package sun-java6-jre None [modified: /var/lib/dpkg/info/sun-java6-jre.list] failed to install/upgrade: subprocess pre-installation script returned error exit status 1" [Undecided,Invalid] [16:13] im tired of getting spam email [16:14] i have no filter or blacklist [16:14] bac Is there no "report abuse" style system? [16:14] lorenzosu: we generally get user feedback here or via the Answers section. [16:14] I say ban the user that has this email address guyheavensent@yahoo.com [16:15] he is spamming [16:15] bac Ok. thank you. I'm sure you have recognised the problem and know how to take care of it. [16:16] lazermouse I'm sure the launchpad staff will know how to handle it now they've been told. [16:16] lorenzosu: i see the spam from praveen. [16:17] bac To me it looks like spam started by prasopsuk on 30 April [16:17] yes [16:17] if i get more spam email, I'll be back here :\ [16:17] =-O [16:17] 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] i already have six messages [16:18] so, what's the issue with guyheavensent? he doesn't seem to be disruptive [16:18] he's the one sending me the email [16:19] i had a pastebin of the message [16:19] http://pastebin.com/m39aff13c [16:20] Yes I think he's just reacting to all the spam and is a little p***** off. [16:21] The 'real' spam/disruption started with prasopsuks@gmail.com [16:21] ban them [16:28] lazermouse: yes, i think you're correct. [16:28] do it as quick as possible :) [16:28] bac Ok I take it you are dealing with the problem. Thanks for the help [16:28] 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] bac No one can 'administrate' the bug and remove the irrelevant emails? [16:29] just delete their launchpads accounts [16:30] and ban thier ip's [16:30] lorenzosu: the inappropriate comments can be hidden but that won't quell the 'reply all' email storm. [16:30]