[12:23] <vedic> Hey friends, I am learning bzr. I want to setup repository on a remote server. From that server, my friends will pull the updates and push their work. Also want to ensure that no body else other than friends (total 5) should be able to pull or push to that repo. How to setup such a bzr repo
[12:24] <vedic> I also don't want to give access of remote server (i.e. they should not be able to get ssh access to the server)
[12:25] <vedic> Any tutorial or blog post will be very helpful
[12:35] <fullermd> You can do stuff in ssh config to restrict what commands a user is allowed to run.
[12:35] <vedic> fullermd: ok
[12:36] <fullermd> Of course, in extremis, a user can certainly abuse bzr to read arbitrary stuff on the server.  And possibly pull off enough gymnastics to run stuff.
[12:37] <vedic> fullermd: Then you mean to say I create user accounts on that server and for each user I create public/private key and restrict access to certain thing using ssh config?
[12:41] <fullermd> Yeah.  Just know that if they really, really, really want to, they can probably break out of jail.
[12:44] <vedic> fullermd: Ok, tell me if I am doing write: 1) I logged into remote server. Into my home directory (say /home/f1) I created a shared repo as: bzr init-repo projectx; bzr init projectx/trunk; Now how should I allow others to pull and push from this repo? If I create f2, f3, f4, f5 users then they all will have access to their home directory. How will they access /home/f1/projectx/trunk?
[12:45] <vedic> *right*
[12:45] <fullermd> Generally by putting them all in a group, and chgrp/chmod/etc'ing the repo.
[12:46] <vedic> I see
[12:46] <fullermd> Another possible way is to have a single shared account that owns it, and have everybody ssh in as the same user (probably with different keys, for management dolphins)
[12:49] <vedic> fullermd: That is much better
[12:49] <vedic> So there also I can limit the commands for each key?
[12:50] <fullermd> Yeah, there's some syntax in the authorized_keys file for it.  'd have to check the openssh docs.
[12:50] <vedic> ok
[12:59] <vedic> fullermd: I am going ahead with creating multiple users: sudo useradd -r -s /bin/false USERNAME
[12:59] <vedic> Instead of keys
[13:00] <vedic> And will soft link the repo in my home to /usr/local/projectx/trunk
[13:00] <fullermd> Setting shell to false probably won't work; I think ssh generally needs a "real" shell of some sort to be able to execute programs remotely.
[13:03] <vedic> fullermd: http://doc.bazaar.canonical.com/bzr.dev/en/admin-guide/security.html#using-ssh
[13:04] <vedic> I think there he explains the same thing you suggested
[14:58] <vedic> Is bzr loosing ground? http://www.stationary-traveller.eu/pages/bzr-a-retrospective.html
[14:58] <vedic> People are switching or opting git and hg
[14:59] <vedic> Why is so? can anybody tell?
[15:00] <LeoNerd> Network effect
[15:00] <LeoNerd> Everyone does, so everyone else does
[15:01] <vedic> LeoNerd: Just a network effect?
[15:01] <fullermd> Canonical stopped developing it, and nobody else has started.
[15:01] <vedic> IRC of bzr has 78 users but for git has 1000+
[15:01] <vedic> fullermd: I see
[15:02] <vedic> for the fate is unknown
[15:02] <vedic> *so*
[17:32] <DarkLinkXXXX> I tried building bzr, but I got an error with cython.
[17:34] <DarkLinkXXXX> bzrlib/_dirstate_helpers_pyx.pyx:1815:36: undeclared name not builtin: cmp
[17:35] <DarkLinkXXXX> Anyone know something about this?
[17:37] <Enlik> maybe you are using Python 3 instead of Python 2?
[17:37] <Enlik> (my guess after seeing the name; I may be wrong)
[17:40] <DarkLinkXXXX> Oh.I thought bzr supported python 3.
[17:40] <DarkLinkXXXX> My bad.
[17:49] <jelmer> there is an attempt to add python3 support, but it's nowhere near finished