=== Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk [04:49] Hi, I've set a team (A) to be the owner of another team (B), when non-members (not A, neither B) visit team B's page and click "Contact this team's owner", the email will send to team A's owner (a single person), but not the whole team. If I would like such emails send to all members of team A, what should I do? [05:18] happyaron, i think there's a checkbox on the team page to turn that on [05:35] poolie: is it a setting? or the user who send email should check it? [05:44] one of the team admins should check it [06:18] poolie: cannot find it, could you tell me where is it? [06:35] like https://launchpad.net/~bzr-packagers/+contactaddress [06:36] insert your team name as the first part of the path [06:36] happyaron, ^^ [06:36] if you go to the bottom left of the team page, click 'mailing list' then you can click through to this [06:36] poolie: thanks, let me try [06:58] poolie: does not make sense [06:58] what doesn't? [07:00] I tried to fill in a different contact address in the box (team B), and login to another account which is not a member of that team, then visit the team's page, and click "Contact this team's owner", it still send email to team A's owner, rather than all members in A [07:01] hm [07:01] i don't know [07:01] it may just be a bug [07:01] see [07:01] hm, so actually [07:01] which teams are you talking about here? [07:02] A: ubuntu-china-admins, B: ubuntu-l10n-zh-cn [07:02] ok, and so A is a list? [07:03] and you put the address of that list into the "another address" box in https://launchpad.net/~ubuntu-l10n-zh-cn/+contactaddress [07:05] poolie: I requested a mailing list for ubuntu-china-admins, and try to add it to "another address" of ubuntu-l10n-zh-cn, then it says "ubuntu-china-admins@lists.launchpad.net is already registered in Launchpad and is associated with Ubuntu China LoCo Teams Admininistrators." [07:13] sorry, this is getting past the limits of what i know about how this works [07:21] thanks anyway, :) [09:33] would it be the right thing to do to replace all occurances of "maverick" with "natty" in the debian/changelog to do another build/upload to my ppa [09:34] to support both series? [09:42] thorwil: only the topmost entry in debian/changelog has to be for natty [09:44] geser: so could as well copy the topmost, make that one change and go? to repeat that for every release of my package? [09:45] thorwil: yes (and don't forget to also modify the package revision as you can only successfully upload each revision once) [09:48] but changing the revision would not reflect what happens, as the switch between maverick/natty would be the only change [09:49] does your maverick package need to be recompiled for natty? [09:50] even if you upload the same package to maverick and natty, both need a slightly different package revision (e.g. by appending ~maverick and ~natty to the package version) [09:50] geser: it's a python package which makes me suspect: no, though perhaps a change of the default python version or a dependency might become interesting? [09:52] if the dependencies don't need to be changed at all, you could also copy the package from maverick to natty over the LP interface for it [09:52] * thorwil has no clue regarding the lack or presence of compatibility issues with .pyc files [09:53] .pyc files will be generated during install time (if you packaged it right) [09:53] ah, ok then. [09:53] geser: thank you [09:54] your package should only have the .py files [09:55] i see, it has === doko__ is now known as doko [10:45] danilos, hi, did you get my email? [12:03] fta, yeah, I did, but a bit jetlagged atm, will probably get to it later today [12:40] is possible to access ppa repositories using ftp (or https) instead of http ? [12:42] no [12:45] is it on the roadmap ? [13:46] good morning. [13:47] i keep getting rejected upload mails from soyuz (for PPAs) with a very vague error message [13:47] here is an example message: http://fpaste.org/CO63/ [13:47] (i also tried with a non-zero version number more recently. it didn't help.) === Ursinha-afk is now known as Ursinha [13:49] desrt: That's a pretty poor error message, but I'm guessing that it's because Soyuz doesn't allow 3.0 (git) source format [13:50] ah. that might explain it. [13:50] you're sure that it doesn't support 3.0 or you suspect that it is the case? [13:50] It allows 3.0 (native) and 3.0 (quilt) [13:51] (For karmic and later, that is) [13:51] maybe i can get away with native. i'll try that. [13:56] maxb: woo. accepted! [13:56] now we see if it builds :) [14:43] hey [14:43] i would like to know more about ReportingAPI (https://dev.launchpad.net/Translations/Specs/ReportingAPI) [14:44] hi tiagoscd [14:44] David tell me that I can found help on this channel [14:44] tiagoscd, the better channel is actually #launchpad-dev [14:45] thanks danilos === bac` is now known as bac === mbarnett` is now known as mbarnett === Lcawte|Away is now known as Lcawte === henninge_ is now known as henninge [15:31] Hrm. This is bizarre. I have a PPA, in which, for karmic, a recent lpia build has not been published [15:32] Or rather, arch-all [15:34] maxb: can you point me at the ppa/build and I'll take a look [15:34] https://launchpad.net/~bzr/+archive/proposed/+packages?field.name_filter=python-fastimport&field.status_filter=published&field.series_filter=karmic [15:35] I am just writing up a question [15:36] Logged as https://answers.launchpad.net/launchpad/+question/142682 [15:38] maxb: hmmm that's odd === Ursinha is now known as Ursinha-lunch === beuno is now known as beuno-lunch === deryck is now known as deryck[lunch] [16:17] I'm pleased to say feedback@launchpad.net should be working again [16:21] mrevell: woot. thanks. === yofel_ is now known as yofel === beuno-lunch is now known as beuno === matsubara is now known as matsubara-lunch === deryck[lunch] is now known as deryck === Ursinha-lunch is now known as Ursinha === matsubara-lunch is now known as matsubara === Ursinha is now known as Ursinha-brb [19:14] hey all, I know how to copy binaries/source from one PPA to another, but is there a way to copy say, https://launchpad.net/ubuntu/+source/foobar/0.1-1 to a PPA? [19:15] midtown: the easiest way is to use the API === leonardr is now known as leonardr-afk [19:15] the web UI is not designed to browse large archives so it times out [19:16] bigjools: oh okay, but the API does provide a way to go from ubuntu archive to PPA? [19:16] yes, you need to get 2 Archive objects and call syncSource() on one of them [19:18] ^^ you need the sourcenames of the packages btw to do API calls [19:23] what is the valid URL for bazaar if I want to import code from cvs sf.net? my command is 'cvs -z3 -d:pserver:anonymous@nvclock.cvs.sourceforge.net:/cvsroot/nvclock co -P nvclock' [19:24] thanks bigjools, shadeslayer, found the docs for that. do either of you know of any source that has an example of using 'archive' or syncSources? the usage isn't obvious to me from reading the docs [19:36] midtown: http://bazaar.launchpad.net/+branch/hydrazine/view/head:/lp-promote-ppa [19:36] ari-tczew: CVS does not use URLs. You need the cvsroot and module from the command line you showed [19:39] maxb: could you help me? how can I reproduce it? http://paste.ubuntu.com/557802/ [19:40] I do not understand what you are asking [19:41] maxb: I want to import cvs to bazaar. [19:42] but LP couldn't push it because: ":pserver:anonymous@nvclock.cvs.sourceforge.net:2401/cvsroot/nvclock" is not a valid URI [19:44] ari-tczew: Write :pserver:anonymous@nvclock.cvs.sourceforge.net:/cvsroot/nvclock instead [19:44] And be sure you're not accidentally trying to enter a CVS root in the Subversion import fields [19:45] maxb: ":pserver:anonymous@nvclock.cvs.sourceforge.net:/cvsroot/nvclock" is not a valid URI [19:45] Exactly where are you entering this? [19:45] maxb: in my branches [19:45] Please give the exact URL of the Launchpad page you are on [19:45] maxb: https://code.launchpad.net/~ari-tczew/+addbranch [19:46] Ah, you're in the wrong place [19:46] See the text under the field "This is the external location where the Bazaar branch is hosted." [19:46] You're not importing a Bazaar branch [19:46] maxb: thanks, got it working! [19:46] maxb: ok, how can I resolve it? [19:47] ari-tczew: You want to be here instead: https://code.launchpad.net/+code-imports/+new [19:48] maxb: project doesn't exist :( [19:48] Code imports need to be associated with a project [19:54] Does Launchpad support custom domains a la DNS CNAME, or do we require HTTP redirection? [19:55] It does not support pointing custom CNAMEs at i [19:55] *it === leonardr-afk is now known as leonardr [20:45] lifeless: btw, pages like https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted actively mention the ~launchpad-recipe-beta team, not ~launchpad-beta-testers [20:46] maxb: ah, sounds like I was wrong then :P === Ursinha-brb is now known as Ursinha [21:09] hello [21:10] just a quick question [21:10] what should I do to test the recipes on lp ? [21:13] qwebirc44278, see https://help.launchpad.net/Packaging/SourceBuilds/GettingStarted [21:13] i think that says how to test them locally [21:13] oh, I've already found - needed to join ~launchpad-recipe-beta team [21:14] yea, I did test locally, but I wanted to test it on the launchpad itsels [21:14] *itself [21:14] thanks for the help anyway [21:14] cya! :) [22:04] poolie: skype me when you are ready [22:06] flacoste, won't be long [22:15] flacoste, actually, can we skip it and try for tomorrow? [22:15] still otp [22:15] poolie: tomorrow's is busy for me, either next week or in 48hr? [22:16] 48h (or 47h) is ok with me === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Ursinha is now known as Ursinha-afk === Ursinha-afk is now known as Ursinha === Lcawte is now known as Lcawte|Away [22:36] I'm trying to build two different releases of a software package. I uploaded the first, it got scheduled to build. Then I upload the 2nd and the 1st build was aborted with "Build for superseded Source". Is there a way around this? [22:41] That is not how Debian/Ubuntu package archives work. If you explain a little more about why you're trying to build two different releases, people here can probably suggest how that best fits into the model. [22:43] I've got a stable pnp4nagios-0.6.10 package and a development pnp4nagios-0.6.11 package. I want to build both. Perhaps I need to some how have sub sections in my PPA like I've seen in some other PPAs? [22:44] To offer your users a "stable" and "beta/dev/test" choice, you want to use two separate PPAs. Your users then choose which one to use. === Ursinha is now known as Ursinha-afk [22:56] I've seen copy and delete packages, is there some way to move that development package to my unstable PPA or do I have to delete and possibly wait a long time? [23:02] maxb: thanks, now nvclock trunk is available via bazaar ;) [23:49] bdrung pokes poolie (and dobey in #ubuntu-desktop) to look at bug #524680 [23:49] Launchpad bug 524680 in ubuntu-dev-tools (Ubuntu) "[lp-project-upload] not really ubuntu specific" [Wishlist,Triaged] https://launchpad.net/bugs/524680