[12:16] launchpad list is private, right? [12:22] right [12:25] kiko: ping [12:26] is there any feauture planned to have a mailing list per group? [12:29] lucasvo: yes! would that be useful to you? [12:33] sabdfl: well, for coordinating efforts and discussion about development I think I would use it once there are more than 2 devs in my team [12:34] sabdfl: however I think working things out with malone and bazaar have higher priorities [12:34] agreed [12:35] (linking bugs to revision #, uploading bzr branches to product branches, and couple of other things) [12:35] ah yes, and maybe some syntax for bug fixing in ci messages would be cool [12:35] like: fixes bug # 22 [12:35] amen, brother [12:36] sabdfl: sorry, I can't really figure out what amen means in this context. ACK? agreed? [12:36] very much agreed [12:36] good to know :0 [12:36] :) [12:38] sabdfl: too bad it's not opensource. I started using LP because there were some rumors that it be opensourced. that was, what made me prefer it from trac and SF [12:38] trac is open source [12:38] sabdfl: yes, but it doesn't host the projects [12:39] right [12:39] not having to deal with svn permissions and making your ISP install trac is a great relief [12:40] do you (still) have in mind of opensourcing it? [12:40] yes [12:41] we want to refactor it and release it chunks at a time [12:41] it's not that I would want to set it up on my own server, but when I develop free software I want to develop it using free software [12:41] starting with the infrastructure that makes it possible, so that others can write web infrastructure like this too [12:41] we have GREAT infrastructure [12:41] what infrastructure? I've only seen the apache proxy error so far... :) [12:42] you'll see :-) [12:42] yeah [12:44] night all === sabdfl [n=mark@ubuntu/member/pdpc.silver.sabdfl] has left #launchpad [] === jinty_ [n=jinty@221.Red-83-58-174.dynamicIP.rima-tde.net] has joined #launchpad === Fujitsu [n=Fujitsu@c58-107-63-43.eburwd7.vic.optusnet.com.au] has joined #launchpad [01:43] Added a spec: https://launchpad.net/distros/ubuntu/+source/zope3/+bug/56853 [01:43] Malone bug 56853 in zope3 "Make it easier to build Zope3 + MySQL applications" [Unknown,Unknown] [01:43] https://features.launchpad.net/distros/ubuntu/+spec/better-zope3-support [02:23] https://wiki.ubuntu.com/Zope3onUbuntu [02:24] WebMaven: #launchpad isn't the best place for raising issues about ubuntu development [02:25] It's more of a Zope3 issue. I thought it would be of interest. [02:25] it's a request for ubuntu packages [02:25] Oh, you mean the stuff I pasted earlier. Sorry. OK. === jinty [n=jinty@221.Red-83-58-174.dynamicIP.rima-tde.net] has joined #launchpad === sevrin [n=sevrin@202.75.186.154] has joined #launchpad === Fujitsu [n=Fujitsu@c58-107-63-43.eburwd7.vic.optusnet.com.au] has joined #launchpad === haasteem [n=haasteem@209-161-233-25.dsl.look.ca] has joined #launchpad === haasteem [n=haasteem@209-161-233-25.dsl.look.ca] has left #launchpad ["Leaving"] === jinty [n=jinty@221.Red-83-58-174.dynamicIP.rima-tde.net] has left #launchpad ["Leaving"] === lakin [n=lakin@S01060013101832ce.cg.shawcable.net] has joined #launchpad === AM|R [n=gomo@Malaysian.Computer.Emergency.Response.Team.MyCERT.org] has joined #launchpad === AM|R [n=gomo@agensi.antidadah.kebangsaan.adk.gov.my] has joined #launchpad === dsas [n=dean@host86-129-12-65.range86-129.btcentralplus.com] has joined #launchpad === stub [n=stub@ppp-58.8.4.68.revip2.asianet.co.th] has joined #launchpad === Fujitsu_ [n=Fujitsu@c58-107-63-43.eburwd7.vic.optusnet.com.au] has joined #launchpad === Fujitsu_ is now known as Fujitsu === metze__ [n=savirc@xdsl-195-14-205-85.netcologne.de] has joined #launchpad === sabdfl [n=sabdfl@ubuntu/member/pdpc.silver.sabdfl] has joined #launchpad === cx [n=x@adll-15-244-206-196.marocconnect.net.ma] has joined #launchpad === dsas_ [n=dean@host86-129-12-65.range86-129.btcentralplus.com] has joined #launchpad === cx [n=x@adll-15-244-206-196.marocconnect.net.ma] has left #launchpad [] === doko [n=doko@dslb-088-073-102-098.pools.arcor-ip.net] has joined #launchpad === Fujitsu_ [n=Fujitsu@c58-107-63-43.eburwd7.vic.optusnet.com.au] has joined #launchpad === Fujitsu_ [n=Fujitsu@c58-107-63-43.eburwd7.vic.optusnet.com.au] has joined #launchpad === Fujitsu_ is now known as Fujitsu === glatzor [n=sebi@ppp-82-135-3-190.dynamic.mnet-online.de] has joined #launchpad [12:47] how do i see an OOPS? [12:49] sabdfl: hey, I'm trying to see the link you sent me but it's timing out ;-) [12:50] sivang: any spec listing will show it to you [12:50] sabdfl: right, cool, and thanks for the landing! [12:50] sure, thanks for the code :-) [12:51] sabdfl: hrm, can you access staging though? (even front page) [12:51] https://staging.launchpad.net/+graphics [12:51] sure [12:55] sabdfl: this page partially loads. But Staging just timeouts with an OOPS for me, is this knows / planned ? [12:55] sabdfl: https://devpad.canonical.com/~jamesh/oops.cgi/$OOPSID [12:55] OOPS-231S15 [12:55] https://chinstrap.ubuntu.com/~jamesh/oops.cgi/231S15 [12:56] sivang: staging may be under some load, i think there's work under way to open Edgy translations [12:56] which drives the db server nuts [12:56] they may be testing that on staging right now [12:56] jamesh: thanks! [12:56] ah right, makes sense, okay. [12:56] jamesh: great blog on the supermirror stuff [12:56] thanks. [12:56] i really want that experience to be very slick for people [12:56] should come down to: [12:57] bzr branch lp:///python my-branch [12:57] bzr commit [12:57] bzr push lp:/[some url indicating my branch] [12:58] and it should then be visible to everyone, under ~name/product/my-branch [12:59] with the smart server work by spiv and mpool, i think we can make the whole thing pretty fast [12:59] hmm, so each person can become a sort of LP "Instance" holding a world of products , packages, branches and so on of his own ? [12:59] well, packages probably fall under PPAs [01:00] yeah [01:00] sivang: yes [01:00] I wonder if the smart server would be able to automatically use other branches as a basis for the initial push? [01:00] cool! [01:00] i was just thinking the same thing [01:00] if it remembered the revision that came *from* the supermirror, in metadata, it could use that for the push [01:01] and I assume the plan is also to allow that from teams, as they basically could be treated like people ? [01:01] although perhaps doing repositories on the supermirror would get similar benefits [01:01] it could start the conversation with "hi, i am about to push a branch which started with revision X, and I happen to know you have that" [01:02] which could then create the repository and allow the new branch push to be really, really fast [01:04] so, you wouldn't even have to have had a previous push of this product yourself [01:04] just leverage a repository which can be created because you know which revision you last saw from the SM [01:05] since revision ID's are uuid's, knowledge of the revid implies knowledge of the branch itself [01:05] though we should probably enfore branch privacy over and above that [01:05] mpool: ^ ? === jinty [n=jinty@221.Red-83-58-174.dynamicIP.rima-tde.net] has joined #launchpad [01:33] sabdfl: when aaron's nested trees work is done, you should be able to identify a project by it's root-id === AM|R [n=gomo@agensi.antidadah.kebangsaan.adk.gov.my] has joined #launchpad [01:40] LarstiQ: that's pretty interesting - i'll chat with aaron about that [01:41] you still have the problem that everyone who branches off that has the same root-id, but it gives you an idea what branches to look at [01:42] but aaron can tell you more :) [01:42] LarstiQ: we have a DB with revision info for all the registered branches, so picking a closest matching branch is not an insurmountable problem [01:43] LarstiQ: just go back in the revision history til you get a match [01:45] jamesh: you'll need something more than just push then [01:45] or it will be installing old revision first, and that is what you want to speed up === LarstiQ has no idea how the smart server works though [02:02] sabdfl: the basic approach will be that you ask the smart server what you need to upload [02:02] sabdfl: so it may be possible - we've actually discussed this before [02:03] IIRC we felt it was best to have an explicit 'reuse this branch' api in it, which is not as transparent, but provides plenty of room for optimisation [02:06] LarstiQ: you cant id a project by the root - forked projects will share roots, just like revision ids will, and anyhow a revision id query is almost the same overhead [02:07] lifeless: right, I see forks as the same thing, but that has potential for huge mismatches in the revision history [02:07] also, all the existing projects have one root id [02:07] there is that small operational problem, yes :) [02:08] that is a particular id though? [02:08] yes [02:09] would you do a 'related branches:' by traversing the revision-history and looking up who has the same revisions, or would roots (bar the current one) be ok for that? [02:10] You'd need the former for branching visualisation anyway [02:13] so the problem with transparent branch cloning is revision pollution [02:14] if you use a launchpad wide repository? [02:14] or even a user/product wide one [02:14] if we ignore that, its basically a chatter back and forth to determine what revision the bundle to be uploaded should be made against [02:14] which is the exact same chatter that any normal upload to a branch will use [02:15] even on dumb transports? [02:15] except that there is no remote initial revision to match against [02:15] no, any normal hpss upload [02:15] ok [02:20] but a simple approach is to allow explicit cloning [02:20] 'branch remoteA remoteB, then push --overwrite remoteB' [02:20] I think we can make this seamless within the client for launchpad uploads [02:21] how do you determine remoteA? [02:22] query for 20 or 30 revision ids in the lp database, among the branches for the product being uploaded too that you have access to [02:22] the revision ids are exponential backoffs in the rev history [02:23] the tip, tip -5, tip -25, tip -125, tip -625, tip - 3K, tip -15K [02:23] sort of thing [02:25] anyhow, its all worth consideration [02:25] ok, that should work when you branch python-trunk and keep the same product when uploading === xenru [n=Miranda@85.192.12.254] has joined #launchpad === AM|R [n=gomo@agensi.antidadah.kebangsaan.adk.gov.my] has joined #launchpad === Keybuk [n=scott@syndicate.netsplit.com] has joined #launchpad === Nafallo [n=nafallo@ubuntu/member/nafallo] has joined #launchpad [04:36] lifeless: in many cases, the user will branch *from* launchpad and push *to* launchpad [04:36] so, it should be able to know at least a recent rev-id that is on the server === sfllaw [i=sfllaw@debian/developer/coleSLAW] has joined #launchpad === lfittl [n=lfittl@85-125-227-23.dynamic.xdsl-line.inode.at] has joined #launchpad === danilos [n=danilo@82.117.204.199] has joined #launchpad === sfllaw [i=sfllaw@debian/developer/coleSLAW] has joined #launchpad === jinty [n=jinty@221.Red-83-58-174.dynamicIP.rima-tde.net] has joined #launchpad === niemeyer [n=niemeyer@200-163-194-221.ctame7043.dsl.brasiltelecom.net.br] has joined #launchpad === BjornT [n=bjorn@213.226.190.253] has joined #launchpad === niemeyer [n=niemeyer@200-163-194-221.ctame7043.dsl.brasiltelecom.net.br] has joined #launchpad === Nafallo [n=nafallo@ubuntu/member/nafallo] has joined #launchpad === Spads [n=crack@host-87-74-18-227.bulldogdsl.com] has joined #launchpad === WaterSevenUb [n=WaterSev@195-23-238-140.nr.ip.pt] has joined #launchpad === danilos [n=danilo@82.117.204.199] has joined #launchpad === parsek [n=oikoi@dsl-roigw4-febbf800-121.dhcp.inet.fi] has joined #launchpad [10:49] is there a shipit channel, or can i ask here about it [10:56] you can ask here [10:57] do i have to make 2 orders if i want to order kubuntu and ubuntu [10:57] parsek: yes [10:58] does it cost me anything [10:58] parsek: no [10:58] i mean shiping [10:58] parsek: and they will get shipped together [10:58] parsek: no [10:58] thx [10:58] just login to shipit.ubuntu.com and afterwards shipit.kubuntu.org [10:59] well i`m doing it the other way [10:59] does it matter [10:59] first kubuntu then ubuntu [11:00] no [11:03] well, i dont know if here is any makers of kubuntu but i have to say that thx for making a great OS (works perfectly even with my 5 year old laptop) and thanks lucasvo [11:04] Bye! === AstralJava [n=jaska@cm-062-241-239-3.lohjanpuhelin.fi] has joined #launchpad