[02:03] hmm.. can I clone bzr repo without ssh key? [02:03] clone it from LP [02:04] ah, using http instead of lp worked [02:16] kklimonda: lp: will resolve to http: if you haven't run bzr lp-login. [02:24] wgrant: I may have run lp-login at some point.. how can I check if I did (and restore the default behaviour)? [02:24] kklimonda: Check ~/.bazaar/authentication.conf [02:24] There will be a [Launchpad] section. === Tak|Work is now known as Tak_ === apachelogger is now known as darthlogger === darthlogger is now known as apachelogger [14:19] where's the best place to ask about build problems in a PPA? I have something that at least starts to build in pbuilder but will not build in my PPA (build-time dependency issues) [14:20] PPA in question: https://launchpad.net/~r0lf/+archive/isdn/+packages [14:22] from the build log: [14:22] After installing, the following source dependencies are still unsatisfied: libcapi20-dev(inst 1:3.12.20071127-0ubuntu6 ! << wanted 1:3.10) [14:23] I explicitly do not want to build against the Ubuntu package the (seemingly) older isdnutils package in that PPA [14:28] hi! I requested a merge request from my trunk repo to the master. at the Code page it says that "1 branch proposed for merging into this one.". I already approved it, how to actually merge into the master? [14:34] Laibsch: build depends on libcapi20-dev (<< 1:3.10) is your issue, not the PPA [14:34] akoskm, you need to manually merge it into trunk [14:35] usually, you branch trunk locally, cd into it, merge ../other branch, commit, push [14:40] micahg: Thank you for having a look. If it wasn't clear, that "issue" is intentional, of course. I want to build against the package from the PPA not the seemingly newer package from ubuntu repos. [14:40] that dependency seems to be picked up fine with pbuilder, a local repo and the official repos [14:41] beuno, thank you. I already merged it with trunk. Now I would merge trunk with master. [14:42] Laibsch: yeah, I don't know if you can do that in the PPA unless you reupload with a higher version than the archive one, and sorry, I read it twice and still got your intention wrong (my fault) [14:53] micahg: no problem, I'm sure it's a pretty unusual request to make [14:54] that isdnutils package has newer code in some parts but is mostly older than the ubuntu package [14:54] the capifax package needs the part where the code is newer and it needs the newest code [14:58] Laibsch: could you rebase those changes onto the Lucid package? You could also reupload with a slightly higher version number (1:3.12.20071127-0ubuntu6.is.3.9.20060704+dfsg.2-9) [14:58] well, isdnutils already is a mess ;-) [14:58] I'm working on fixing that [14:59] less packages and versions meant less overhead [14:59] s/overhead/headache/ [14:59] but maybe you're right and rebasing the lucid package is the best way forward [14:59] that will actually be easy to do [16:53] Hi, [16:54] I'm the owner of https://launchpad.net/~arabic [16:55] and an administrator of ~lp-l10n-ar and ~ubuntu-l10n-ar [16:56] I would like to use a mail-list of one of them instead of creating separate mail lists [16:56] is it possible? [17:16] As a general rule, a Launchpad team used as a mailing list should be an Open team that is not used in any way to grant permissions to anything [17:18] what about using this https://lists.ubuntu.com/mailman/listinfo/ubuntu-l10n-ara with all the teams? [17:18] or at least with ~arabic , it's open [17:18] Anything at lists.ubuntu.com is separate from Launchpad [17:19] I see. [17:19] I think I'll just order all new subscribers to any of these teams to join that mail-list. I think that would be easier. [17:20] That sounds like the right approach, if there already is a mailing list in existence for the purpose. [17:20] It would create confusion to have two lists for mostly the same topic [17:21] another question please. https://answers.edge.launchpad.net/launchpad/+question/108979 [17:22] Can we join the team as most of the owners agreed? [17:32] damascene: I think that will need to wait for official Launchpad people to be back after Christmas. But, given that all administrators of ~lp-l10n-ar and ~lp-l10n-ara have posted their consent on the question, it seems to me that it would be sensible to summarize that in the question [17:33] And explicitly ask for those two teams to be merged and the result appointed to the Launchpad translators group. === yofel_ is now known as yofel [17:34] Basically, summarize the current state so the official people with admin rights can see at a glance that the question is unblocked [17:34] OK, thanks for helping === Laibsch1 is now known as Laibsch [19:02] hi! after accepting a merge request in the "trunk" how can I merge it with the "master"? [20:13] SPAM detected: https://answers.launchpad.net/ubuntu/+source/alsa-driver/+question/139392 [20:15] /sigh [20:18] komputes: looks like a hijacked account [20:19] micahg: either that or they found a way to automate questions (question does seem quite short) [20:19] micahg: + very new acct === doko__ is now known as doko [21:24] why can't i access bug #690173? [21:24] Bug 690173 on http://launchpad.net/bugs/690173 is private [21:25] i am ubuntu developer and maintainer for vlc. [21:33] bdrung, Its probably a security bug. [21:33] cody-somerville: it is, but why doesn't i have access to it? [21:34] bdrung, because only the Ubuntu security team has access to unreviewed security bugs [21:34] ok, then i'll fix a security bug that i can't see. [21:35] bdrung, the security team will probably make it non-private if they deem it appropriate [21:35] bdrung, Do you know who the reporter is? You can ask them to subscribe you directly to the bug. [21:37] cody-somerville: i assume.