[00:53] <lucas> hi
[00:54] <lucas> I created a mailing list for a team. it seems people outside the team cannot send mail to it. is that correct? is there a way to change that?
[01:23] <JoshBrown> "<Penguin_Guy> Is the bug email interface guide ( https://help.launchpad.net/Bugs/EmailInterface ) correct? I tried changing the status using the method in that guide and the text appeared in my post (https://bugs.launchpad.net/codemonkey/+bug/589177/comments/1)."
[01:23] <JoshBrown> ...
[01:23] <JoshBrown> "<Penguin_Guy> bac: The only thing I could think of was if the guide was wrong or out of date. That's why I was looking for someone who uses the email interface regularly. I'll try some more Google searches and see what I can find. Thanks for the help."
[01:23] <JoshBrown> "<bac> Penguin_Guy: ok.  if you would, follow up with me here if you figure it out and i'll update the doc if needed."
[01:24] <JoshBrown> Well I've done some testing and it looks like the email commands appear in the original post, and then are executed automatically in a second post. This seems like strange behaviour and should either be reported as a bug or be commented on in the documentation (the documentation indicates that the commands are be executed in the same post, and that the commands themselves do not appear in the post).
[01:27] <wgrant> JoshBrown: The email commands do appear, yes.
[01:27] <wgrant> It's not a second post, though -- it's just how the UI displays it.
[01:28] <wgrant> The former is expected behaviour.
[01:28] <wgrant> I didn't know about the latter, though,.
[01:28] <wgrant> It's not clear if that's intentional.
[01:30] <JoshBrown> wgrant: Oh, I thought the UI displayed it as it was and the email interface batched the emails.
[01:30] <JoshBrown> wgrant: Do you know the reason for including the commands?
[01:30] <wgrant> JoshBrown: I don't know. The email interface hasn't changed significantly in 5ish years.
[01:31] <wgrant> Somewhat before my time.
[01:32] <wgrant> But it was probably modelled on the Debian BTS, which does the same thing.
[01:32] <JoshBrown> bug #424849 (Launchpad should batch attachment notification emails) has been quite active recently
[01:32] <wgrant> Right. That's just for attachments, though.
[01:38] <lifeless> lucas: non subscribers sending mail to the list address should have their mail moderated
[01:39] <lifeless> JoshBrown: please don't do testing on launchpad - use staging.launchpad.net instead.
[01:39] <JoshBrown> lifeless: Yeah, just been told
[01:39] <JoshBrown> lifeless: He started it :P
[01:42] <davidstrauss> TooManyConcurrentRequests: The medium 'SmartSSHClientMedium(bzr+ssh://davidstrauss@bazaar.launchpad.net/)' has reached its concurrent request limit. Be sure to finish_writing and finish_reading on the currently open request.
[01:44] <thumper> davidstrauss: what were you doing?
[01:44] <davidstrauss> thumper, committing
[01:45] <thumper> davidstrauss: you have a checkout?
[01:45] <davidstrauss> yes
[01:45] <thumper> why?
[01:45] <thumper> hmm....
[01:46] <davidstrauss> thumper, oh, this was an issue with my ssh key
[01:46] <thumper> #bzr might have more answers
[01:46] <davidstrauss> thumper, but it shouldn't give a backtrace like that
[01:46] <thumper> davidstrauss: it was?
[01:46] <thumper> you are right, it shouldn't give a backtrace like that
[01:47] <JoshBrown> Committing straight to a  remote branch? Usually people commit to a local branch then push the local branch to the remote branch.
[01:47] <thumper> JoshBrown: bound branches are a great way to enforce "lock-step" developing, like svn
[01:47] <thumper> JoshBrown: often used for trunk branches
[01:48] <davidstrauss> thumper, we also use them for teams working on feature branches
[01:50] <wgrant> Bound branches are great for a team working closely on trunk without using branches for small things.
[01:54] <JoshBrown> Ah.
[02:04] <lifeless> or just for a team to do merges of other contributors stuff
[02:05] <lifeless> it provides coordination on stuff landing in trunk
[02:08] <lucas> lifeless: is it possible to allow non-subscribers to send email without being moderated? or should I ask for a @lists.ubuntu.com list instead so I can configure it?
[02:09] <bdrung> i can change the status for merge request that target ubuntu/<package>, but i can't change the status for merge request that target ubuntu/<series>/<package>. is this a bug? if yes, against which project should i file the bug?
[02:10] <wgrant> bdrung: Which MPs in particular?
[02:10] <lifeless> lucas: I don't know, sorry.
[02:10] <lifeless> lucas: but, separately, *all* ubuntu lists are meant to be on l.u.c anyway
[02:12] <bdrung> wgrant: for example https://code.launchpad.net/~serge-hallyn/ubuntu/lucid/qemu-kvm/memleak-fix/+merge/28645
[02:14] <lifeless> bdrung: it will be because lucid is released, I suspect.
[02:14] <lifeless> bdrung: please file a bug
[02:14] <bdrung> lifeless: against which project?
[02:14] <lifeless> launchpad-code
[02:15] <lifeless> it would make sense to me that you be able to retarget it to lucid-proposed, or maverick, as appropriate.
[02:16] <wgrant> Right, there's a known issue with that. You can't easily propose against lucid-proposed, because it doesn't have a branch until it has its first change.
[02:16] <wgrant> I don't think anybody knows the right way to solve this for UDD.
[02:17] <lifeless> so, a) file a bug
[02:17] <bdrung> wgrant: my problem is, that these merge proposals will be shown in the sponsors list
[02:23] <bdrung> lifeless: opened bug #612391
[02:23] <lifeless> thanks
[02:24] <bdrung> lifeless: np - that's my part to get it fixed
[02:25] <jeremiah> So launchpad is open in the sense that I can run a separate instance, correct?
[02:26] <bdrung> yes
[02:26] <jeremiah> I'd like to build AMR v7 debs - that should be no problem correct?
[02:26] <jeremiah> i.e. I understand there are some particular binary blobs from various vendors, i.e. Freescale et. al.
[02:27] <bdrung> isn't an own instance of launchpad an overkill for that?
[02:27] <jeremiah> bdrung: Yeah, maybe.
[02:27] <jeremiah> The thing is, we'd be setting it up for the GENIVI consortium
[02:27] <bdrung> jeremiah: why not setup pbuilder or sbuild or something similar for that task?
[02:27] <jeremiah> bdrung: sbuild might be the way to go
[02:28] <jeremiah> The thing is, debian doesn't build for ARM v7
[02:28] <jeremiah> And I thought that there was some secret sauce in launchpad or Ubuntu that enabled an ARM v7 build
[02:28] <bdrung> jelmer: for what do they build?
[02:28] <jeremiah> But I'm happy to be disabused of that notion
[02:28] <lifeless> jeremiah: http://www.genivi.org/ ?
[02:28] <jeremiah> lifeless: Yes.
[02:28] <lifeless> jeremiah: you might want to talk with the lenovo folk
[02:29] <jeremiah> bdrung: If you were asking me, Debian builds for ARM v4 and v5
[02:29] <lifeless> jeremiah: they are putting a bunch of work into launchpad for deployments in the lenovo partners
[02:29] <jeremiah> Lenovo?
[02:29] <jeremiah> Hmm, didn't know that.
[02:29] <lifeless> bah
[02:29] <lifeless> EBRAINFAIL
[02:29] <jeremiah> :)
[02:29] <jeremiah> ENOTENOUGHBACON
[02:29] <lifeless> http://www.linaro.org/
[02:29] <lifeless> linaro of course
[02:29] <jeremiah> Ah, yeah, Linaro
[02:32] <wgrant> jeremiah: There's nothing magical about Launchpad's build system at all.
[02:32] <wgrant> It's just a hacked version of sbuild.
[02:32] <wgrant> We build for v7 merely because Ubuntu's toolchain does.
[02:32] <wgrant> Nothing to do with LP.
[02:33] <jeremiah> wgrant: Ah, okay. Thanks.
[02:33] <jeremiah> You can tell I am a tiny bit confused.
[02:36] <jeremiah> So, what would I have to do to build ARM v7 sources?
[02:36] <jeremiah> I can run sbuild locally, I'm kind of familiar with debian's toolchain
[02:36] <jeremiah> So that shouldn't be an issue
[02:37] <jeremiah> I just want to ascertain the delta between debian's ARM v5 toolchain and Ubuntu's ARM v7
[02:37] <wgrant> I don't know. You'd have to ask the Ubuntu ARM or toolchain people.
[02:38] <jeremiah> okay, is there a #ubuntu-arm channel?
[02:38] <wgrant> There is indeed.
[02:38] <jeremiah> w00t
[02:51] <nigelb> wgrant: poke?
[02:51] <wgrant> nigelb: Hi.
[02:51] <nigelb> PM?
[02:51] <wgrant> Sure.
[08:33] <bilalakhtar> wgrant: I suppose there is a problem with the diff-generating system again
[08:33] <wgrant> bilalakhtar: Howso?
[08:34] <bilalakhtar> wgrant: see https://code.edge.launchpad.net/~bilalakhtar/ubiquity/fix-492825
[08:34] <bilalakhtar> wgrant: for some reason, it is scanning the branch from a long time and the merge proposal is also extracting diff from a long time
[08:34] <wgrant> bilalakhtar: How long ago did you last push the branch?
[08:35] <bilalakhtar> wgrant: 5+ minutes
[08:35] <wgrant> The lack of diff is probably because it hasn't been scanned yet.
[08:35] <bilalakhtar> wgrant: but, its scanning since the last 6 minutes or so
[08:35] <wgrant> That's abnormally long, but not yet cause for panic.
[08:36]  * bilalakhtar will ping wgrant if it keeps scanning for another 5 minutes
[08:37] <spm> bilalakhtar: probably best not to ping wgrant, he can't actually fix anything directly[1]. :-)  [1] indirectly is a different issue
[08:37] <wgrant> Right, I can only whinge at LOSAs. :P
[08:37] <wgrant> Very loudly, mind you.
[08:37] <spm> and we all have wrant on ignore; so win-win all round :-P
[08:38] <wgrant> bilalakhtar: You pushed the branch up normally?
[08:39] <bilalakhtar> wgrant: yes
[08:39] <bilalakhtar> wgrant: but, the branch is not in the same repo format as the one on which it is stacked
[08:41] <bilalakhtar> wgrant: is that a cause of concern?
[08:41] <spm> looks like the merge-proposal job has re-suffered bug 605772
[08:41] <wgrant> spm: really? That's not the main problem here.
[08:41] <wgrant> bilalakhtar: Yes, that branch is broken.
[08:42] <wgrant> bilalakhtar: I'm surprised it even let you push it.
[08:42] <spm> wgrant: it's been wheel spinning for about 2.5 hours.  may not be THE problem, but is a problem.
[08:42] <bilalakhtar> wgrant: see this paste
[08:42] <spm> wgrant: oh dear, now it's working on one of yours. we're doomed.
[08:43] <wgrant> spm: Heh.
[08:43] <wgrant> bilalakhtar: Which paste?
[08:43] <bilalakhtar> wgrant: just a minute, I paste it to pastebin
[08:43] <wgrant> It seems to be 2a stacked on something non-richroot.
[08:43] <wgrant> Which is not going to work.
[08:45] <wgrant> spm: Ah, that explains why my MP mail is lagging too, I guess.
[08:45] <spm> wgrant: probably
[08:46] <spm> hrm. that /ignore thing doesn't seem to be working.... how odd.
[08:46] <wgrant> Heh.
[09:10] <bilalakhtar> wgrant: spm: the paste is here http://pastebin.com/n0vkTCGg
[09:11] <wgrant> It's probably a bzr bug that it let you do that.
[09:18] <bilalakhtar> wgrant: so, what should I do? delete branch and push again?
[09:19] <wgrant> bilalakhtar: If you want the branch to be merged, you'll have to recreate it in another format.
[09:19] <bilalakhtar> wgrant: so I should push it, standalone this time?
[09:19] <bilalakhtar> wgrant: would that do it?
[09:20] <bilalakhtar> wgrant: g2g
[09:20] <bilalakhtar> .quit
[09:20] <wgrant> Well.
[09:20] <wgrant> Handy.
[11:57] <maxo> is there a way to grab code off launchpad without having to branch it using bazaar?
[11:59] <maxb> Only if the project in question is making release tarballs available
[12:00] <maxo> maxb: i'm trying to use bazaar, but where I work the ISA server is blocking it. I get - Unable to handle http code 407: Proxy Authentication Required ( The ISA Server requires authorization to fulfill the request. Access to the Web Proxy service is denied.  ) - which is strange, because I'm using Windows and generally it's set up so all software can get thru
[12:01] <maxb> hmm. sounds like a weird evil microsoft issue :-)
[12:02] <maxb> What's the exact URL you're branching?
[12:18] <maxo> maxb: yes it's typical non-standardised evil microsoft stuff :-( was trying to get lp:xibo/1.0
[12:18] <maxb> maxo: Right, it's possible the problem is in the xmlrpc request to resolve the lp: url rather than the bzr transfer itself
[12:19] <maxb> You should try manually looking up the full name of the branch in the web UI and bzr branching http://bazaar.launchpad.net/~whatever/xibo/something
[12:20] <maxo> maxb: yes I tried with http://bazaar.launchpad.net/~xibo-maintainers/xibo/halley/files but had the same problem
[12:20] <maxb> uh
[12:20] <maxb> no /files
[13:18] <dolmen> Hi
[13:19] <dolmen> I have a login problem: "Your account has been deactivated"
[13:20] <dolmen> My account: <myircnick>@users.sourceforge.net
[13:38] <dolmen> Any launchpad admins there?
[13:39] <dolmen> Will I have more chance later? In which timezone are the LaunchPad admins?
[13:50] <Ursinha> hi dolmen
[13:50] <Ursinha> I'll check
[14:06]  * shadeslayer hugs jelmer
[14:06] <shadeslayer> jelmer: dude... thanks :)
[14:08] <jelmer> shadeslayer: you're welcome :-)
[14:08] <shadeslayer> jelmer: now we can haz kde neon builds \o/
[14:08] <shadeslayer> ( in case your a KDE fan :P )
[14:14] <jetienne> q. how can i know the eta for a ppa build ?
[14:16] <bigjools> jetienne: it tells you on the build page
[14:17] <jetienne> https://launchpad.net/~jerome-etienne/+archive/neoip/+builds <- bigjools is this the 'build page' ?
[14:20] <maxb> jetienne: Now click on an individual build
[14:20] <jetienne> i386	4	 931 jobs (three days) <- ok :) i guess i wont know if my package is good anytime soon  :)
[14:20] <maxb> jetienne: Actually, that's the time until the queue empties.
[14:21] <maxb> Because some things in the queue may have different priority scores, its not necessarily a good guide when an individual build will happen
[14:21] <maxb> although in this case, it seems accurate :-/
[14:21] <jetienne> yep 3 boxs to build i386 is not a lot
[14:21] <jetienne> 4
[14:22] <maxb> They've all been stolen for Maverick alpha 3 testing
[14:28] <Ursinha> dolmen, hi, still there?
[14:28] <dolmen> yes
[14:29] <dolmen> Ursinha: yes
[14:30] <dolmen> Ursinha: I discovered I have the capability of ressetting my password. Unfortunately, I don't have access to my e-mail now (blocking proxy). Will have to try later.
[14:30] <Ursinha> dolmen, so, here's what you need to do: go to https://answers.launchpad.net/launchpad/+addquestion and do a request to reactivate the account
[14:30] <Ursinha> ah
[14:31] <Ursinha> ok, so, you can try that, and if you have no luck, file the question and I'll assign it to an admin
[14:32] <shadeslayer> jelmer: err... it failed...
[14:32] <jelmer> shadeslayer, it hasn't landed yet
[14:32] <shadeslayer> ohhh
[14:32] <shadeslayer> jelmer: when will it? :)
[14:32] <jelmer> shadeslayer: it should work with a local copy of bzr-svn, but launchpad hasn't rolled out the new release yet
[14:32] <shadeslayer> ah so when lp rolls out a new release...
[14:34] <jelmer> yep, that - that should be next week
[14:38] <shadeslayer> awesome
[14:49] <jetienne> q. if i uploaded one version into PPA, then deleted this version, can i upload the same version after that ?
[14:50] <bigjools> jetienne: https://answers.edge.launchpad.net/soyuz/+faq/990
[14:51] <jetienne> bigjools: so everytime i upload a bogus package i have to artificially bump the version number ? which version format is ok for this ?
[14:51] <shadeslayer> jelmer: no
[14:51] <shadeslayer> err
[14:51] <MichealH> I anyone having issues with Launchpad + emails?
[14:51] <shadeslayer> bad tab complete
[14:52] <MichealH> Lanchpad "sent" me a email and I havent gotten it
[14:52] <shadeslayer> jetienne: ok usually : ~distro1~ppa1
[14:52] <shadeslayer> jetienne: like ~lucid1~ppa1
[14:52] <bigjools> jetienne: PPAs are not a build testing service, so I hope you're not having to upload many versions.  Ideally you will use pbuilder to test your package locally first.
[14:52] <shadeslayer> or just ~ppa1
[14:52] <jetienne> bigjools: and it does
[14:52] <jetienne> shadeslayer: ok thanks
[14:52] <bigjools> great
[14:52] <shadeslayer> AND what bigjools said :)
[14:53] <shadeslayer> jetienne: maybe its because of pkgbinarymangler
[14:53] <jetienne> shadeslayer: well no other possibility to know if it is accepted and built, than to upload it
[14:53] <shadeslayer> but we can only ascertain that after looking at build log
[14:54] <MichealH> Launchpad was sending me email about verifying my PGP key but I havent had that email
[14:56] <MichealH> Can anyone aswer my question?
[14:58] <MichealH> Itwas a problem with my address... sorry
[15:10] <jcastro> I think I broke lp.
[15:10] <jcastro> I am trying to add a group to the ubuntu-beta-font-testing ppa
[15:11]  * bigjools hides
[15:11] <jcastro> oh wait, nm, it took the change
[15:11] <jcastro> it was just angry
[15:11] <sense> Could someone merge the account 'sense-ubuntu' with 'sense' manually for me? I've been trying to do it myself for several weeks now and it keeps timing out. It prevents me from associating my @ubuntu.com address with my main account.
[15:18] <coffeedude> deryck, ping.
[15:23] <michaelforrest1> Does launchpad OpenID support returning a user's email address to the authenticating service?
[15:26] <maxb> IIRC, it does, but only to a list of sites which is administratively configured in the canonical login service
[15:26] <sense> Another question: is the refusal of the WordPress plugin 'OpenID' (and that of many other websites) to recognise Launchpad as a valid OpenID provider a bug in those websites and plugins, or an error on Launchpad's side?
[15:29] <maxb> Uh, can you give any more info on that?
[15:29] <michaelforrest1> maxb: thanks
[15:29] <michaelforrest1> what are the chances of getting a hash of the email out I wonder
[15:29] <maxb> A hash?
[15:29] <michaelforrest1> I just wanna show gravatars :)
[15:29] <deryck> *sigh* my network connection hates me today.
[15:29] <deryck> hi coffeedude.  What's up?
[15:30] <maxb> Whilst we're talking about OpenID... anyone around who can explain what the exact relationship betweek login.launchpad.net and login.ubuntu.com is?
[15:31] <sense> I think Launchpad is consuming the Ubuntu SSO.
[15:32] <michaelforrest1> Yeah I think it's more of a branding thing
[15:33] <michaelforrest1> we did a bit of user testing of Ubuntu One in the design team and launchpad was a bit unexpected when users were expecting Ubuntu stuff
[15:33] <beuno> maxb, they share the same DB
[15:33] <sense> I had to change my email address in the Ubuntu SSO before it was changed in Launchpad, even though I had changed my main contact email address there beforehand.
[15:52] <fale> hi
[15:53] <fale> I would like to learn more about private PPAs, is there a webpage with all the info?
[16:03] <pmatulis> shouldn't the owner (reporter) be able to change bug status from 'won't fix' to something else?
[16:09] <micahg> pmatulis: no
[16:10] <micahg> pmatulis: just bug supervisors AFAIK
[17:33] <Laney> Is it possible for mailing lists to not require subscription?
[17:33] <Laney> or can certain addresses be whitelisted?
[17:49] <jetienne> q. when i upload a source package with "Architecture: all", it is queued in i386 building.... isnt "all" meaning independant from arch ?
[17:50] <bigjools> jetienne: it has to build on something, and we use i386 to build those
[17:51] <jetienne> bigjools: ok
[18:02] <Laney> no joy? Is LP unsuitable for such open mailing lists?
[18:03] <Laney> Here we're after a list to set as maintainer for packages in Debian
[18:03] <Laney> so the Debian archive/BTS/… has to be able to send it mail
[18:50] <jetienne> when "maverick RELEASE" build gonna be over ?
[18:53] <shadeslayer> jetienne: well.. we just uploaded the whole of KDE
[18:53] <shadeslayer> so its going to be a while
[18:53] <jetienne> shadeslayer: it was 3days this afternoon, it is 5days now
[18:53] <shadeslayer> jetienne: oh thats the PPA
[18:54] <shadeslayer> after alpha 3 some of the builders might be transfered to ppa's
[18:54] <shadeslayer> *might*
[18:54] <jetienne> shadeslayer: whena alpha3 is over ?
[18:54] <shadeslayer> when it will be released?
[18:55] <jetienne> shadeslayer: you got no schedule ?
[18:55] <shadeslayer> jetienne: https://wiki.ubuntu.com/MaverickReleaseSchedule
[18:55] <shadeslayer> august 5th
[18:55] <jetienne> shadeslayer: thanks
[18:55] <shadeslayer> so after that :P
[18:56] <shadeslayer> right now im getting spammed by kde build failiures :P
[18:56] <jetienne> :)
[19:15] <[Dmitry]> hello
[19:16] <[Dmitry]> How long does the application for removal of packages from the repository?
[19:17] <[Dmitry]> I applied, but packages are still there. I need urgently to remove them
[19:18] <[Dmitry]> For the package name here and there has not changed and build the beta version. In the end, everyone broke everything when  upgrade
[19:18] <[Dmitry]> ...
[20:08] <maxb> [Dmitry]: The packages should be removed from the indices, so that APT will not be aware of them, in ~20 minutes or so. They will not disappear from disk promptly
[20:35] <sshaw> are the 32bit build machines down?
[20:36] <sshaw> all my 32bit builds are set to build in 4 days
[20:36] <[Dmitry]> :)
[20:36] <sshaw> 64bit builds seem to be working
[20:39] <beuno> sshaw, not down, just super busy
[20:39] <sshaw> oh, I was really hoping it was down :(
[20:39] <sshaw> that would been the queue wasn't sooo long ;)
[21:32] <jacob> thanks to whoever just added more i386 ppa builders :D
[21:33] <micahg> \o/ we have the PPA builders back
[21:33] <[Dmitry]> wat?
[21:33] <[Dmitry]> !?
[21:33] <jacob> [Dmitry]: https://edge.launchpad.net/builders
[21:33] <jacob> there are 20 i386 now instead of 7
[21:34] <[Dmitry]> o_O
[21:34] <[Dmitry]> Hooray!
[21:35] <[Dmitry]> When you said that it would be more builders, I thought well, for 2 or 3. But 20. Thank
[21:37] <geser> hopefully they stay long enough to help with the queue before they vanish again because the machine is needed for something else
[21:39] <jacob> i'd imagine they'd be here until the queue is down quite a bit, it was previously at a 5 day wait earlier today
[21:39] <[Dmitry]> geser: You want to say that this is not always be as many machines?
[21:39] <jacob> there are more amd64 builders too, 13
[21:40] <jacob> [Dmitry]: I've noticed the extra builders are usually brought online when the queue is backed up
[21:40] <geser> the machines get rescheduled for other tasks as needed, apparently they are free currently for PPA builds
[21:42] <james_w> jacob: post hoc ergo propter hoc :-)
[21:42] <jacob> james_w: just making guesses :P
[22:46] <ari-tczew> how can I import git to bzr?
[22:46] <ari-tczew> create a mirror
[22:49] <wgrant> ari-tczew: Which project?
[22:49] <ari-tczew> wgrant: kadu
[22:49] <wgrant> ari-tczew: https://edge.launchpad.net/kadu/+new-import
[22:51] <ari-tczew> wgrant: ok, I choose Git field. What adress it require? git:// or http:// ?
[22:52] <wgrant> ari-tczew: I'd use the former. But I think the latter works.
[22:52] <ari-tczew> wgrant: former?
[22:52] <wgrant> ari-tczew: Try the git:// URL.
[22:53] <jelmer> http URLs generally work but are significantly slower
[22:53] <jelmer> also, because of the differences between web servers and the fact they're less widely used they have more issues.
[22:55] <ari-tczew> wgrant: This foreign branch URL is already specified for the imported branch ~vcs-imports/kadu/master.
[22:55] <ari-tczew> wgrant: look at https://code.launchpad.net/~vcs-imports/kadu/master
[22:56] <wgrant> "Has submodules which bzr-git and bzr do not currently support."
[22:57] <ari-tczew> :/