[02:52] <AfC> Hi
[05:05] <jelmer> Amoz: that issue should be fixed in unstable
[07:09] <vivekimsit1> Hii, Everyone :)
[07:10] <vivekimsit1> I am new to bazaar and looking forward to use it for and my projects, But first of all I want that there are some existing projects which I would like to convert into the bazaar repository but when I do bzr init-repo it creates a new repository!
[07:26] <lifeless> vivekimsit1: hi, that is what init-repo is meant to do. What were you expecting ?
[07:26] <vivekimsit1> lifeless: init-repo is creating a new dir!
[07:28] <vivekimsit1> lifeless: but I want that the I have one project folder already and I would like to convert it into the bzr repo
[07:29] <lifeless> 'bzr init' on its own will bzr-ise an existing directory
[07:35] <vivekimsit1> lifeless: ok! let me conform, Go to the existing directory run the command bzr init inside it and this will make the parent directory a bazaar repo..! am i right?
[07:39] <lifeless> yes; you might like to read the manual, it give a guided introduction
[07:40] <lifeless> vivekimsit1: e.g. http://doc.bazaar.canonical.com/latest/en/user-guide/starting_a_project.html
[07:46] <vivekimsit1> lifeless:Thanks :)
[08:33] <vivekimsit1> How can I know how many repositories I have
[08:33] <vivekimsit1> or how to see the list of all the repos
[08:36] <wilx> repositories are just directories
[08:36] <wilx> If you want to bzr'ize a single directory, that means you will want to create a stand alone branch.
[08:36] <wilx> Just cd ~/mycode and then bzr init .
[08:36] <wilx> bzr add .
[08:36] <wilx> bzr commit .
[08:36] <wilx> Done.
[08:37] <wilx> I am pretty sure the basics are well enough described in the docs.
[09:50] <vivekimsit1> Is there any doc related to launchpad?
[10:02] <wilx> help.launchpad.net
[10:02] <wilx> ?
[10:24] <vivekimsit1> ok'
[10:59] <goddard> can some one explain something to me
[11:00] <goddard> if I am creating a new branch and then I use bzr-upload
[11:00] <goddard> it will upload that branch
[11:00] <goddard> what happens if i create a new branch?
[11:35] <wilx> goddard: Then you will have two? :)
[11:35] <wilx> I have never tried bzr-upload.
[11:36] <wilx> I see, it is pure copy upload.
[11:37] <wilx> Why don't you use bzr branch/push instead?
[18:06] <Amoz> jelmer: so that issue is already taken care of? will it be automatically synced to build in LP?
[19:21] <M-Boy> Hello all
[19:22] <M-Boy> is there somewhere I can chat with ?
[19:22] <M-Boy> someone*
[19:22] <M-Boy> sorry
[19:22] <jelmer> hi
[19:22] <M-Boy> for instance; I know the "don't ask to ask" rule but every time I come over and just ask I see all people are dead so am checking first ^^
[19:22] <M-Boy> Hi jelmer what up ?
[19:22] <M-Boy> I mean how are you...
[19:23] <jelmer> alright, how are you?
[19:23] <jelmer> Amoz: hi
[19:23] <jelmer> Amoz: let mec heck
[19:24] <M-Boy> jelmer, I got a straight forward question. I am looking for a "tool" that would replace the linux shell in order to administrate and manage bazaar branches :/
[19:25] <jelmer> M-Boy: what do you mean with replace the shell, what would you like to do?
[19:25] <M-Boy> launchpad is a hell therefore I cannot really manage to clone it on my private server, hence I am looking for something else
[19:25] <M-Boy> jelmer, let's see I have set up a quick dev environement for a team of 3 developers
[19:26] <M-Boy> we have agreed on a straight forward version control workflow: Local branches map on remote branches + 1 remote branch (so called mainline) for global merges
[19:26] <M-Boy> the issue is that we keep struggling with permissions...
[19:26] <M-Boy> I litteraly spent the whole afternoon trying to figure out how to achieve the best organization but each time I keep fighting with folders' permissions
[19:41] <M-Boy> jelmer, any advice?
[19:43] <jelmer> M-Boy: what have you set up exactly?
[19:43] <jelmer> M-Boy: how are you sharing the branches?
[19:43]  * jelmer back in ~15 min
[19:45] <M-Boy> jelmer, I am using bzr+ssh
[19:45] <M-Boy> I simply created /bazaar/project_repositoru/branches...
[20:25]  * jelmer is back
[20:26] <jelmer> M-Boy: you might want to adjust the permission mask that's used for those users
[20:26] <jelmer> so that the group automatically gets write access to new files
[20:26] <M-Boy> jelmer, so there is nothing that does this for me through a simple user interface for example?
[20:27] <M-Boy> i only found bazaar explorer and it doesn't
[20:32] <wilx> Can I remove an entire branch on bzr+ssh:// repo?
[20:32] <wilx> Remotely.
[20:45] <M-Boy> nvm
[20:45] <M-Boy> see ya
[20:52] <jelmer> wilx: yes, "bzr rmbranch" can do that
[21:53] <kbulgrien> say I want to have --no-recurse whenever I add a directory.  Is there an easy way to set stuff like that up?
[21:56] <Kamping_Kaiser> kbulgrien: you can add aliases to ~/.bazaarbazaar.conf
[22:00]  * kbulgrien reading up on alias
[22:01] <kbulgrien> bleah. As with other VCS, don't much care for personal alias because it makes you not know how to do things native.
[22:02] <kbulgrien> If I go somewhere my aliases aren't set up, that is a pain.  I'd rather know how to do it without an alias.
[22:02] <kbulgrien> (It's also a pain that --no-recurse has no shortcut)
[22:04] <kbulgrien> Tho I guess its the same if I have to do something else to set up a different default.
[22:20] <jelmer> kbulgrien: I guess we could add a short option for it, but I think it's generally not used very often
[22:22] <AfC> jelmer: I'd vote for a short option; --no-recurse is something I use a great deal and yeah, it's a pain to type.
[22:23] <kbulgrien> Use it heavily ... coming to bzr from other vcs, this is a great pain.
[22:24] <kbulgrien> It at least needs a short option, IMO.
[22:24] <jelmer> is this --no-recuse for 'bzr ls', 'bzr add', 'bzr status' or all?
[22:24] <AfC> jelmer: I personally am describing my use of add
[22:25] <kbulgrien> Mostly add is where it bugs me the most.
[22:25] <kbulgrien> but if added, I'd probably vote for consistency.
[22:26] <jelmer> yeah, I agree if we add it we should add it consistently
[22:26] <AfC> jelmer: my complaint is that in the case of add (one of your first experiences with bzr,) would be more along the lines that most Unix commands require you to specify ls -R or grep -r to make it recursive.
[22:26] <AfC> jelmer: but it is what it is
[22:27] <kbulgrien> AfC: I agree
[22:27] <jelmer> AfC: I think one of the issues there is also that all other VCS tools seem to be recursive by default
[22:27] <jelmer> and other bzr commands are recursive by default
[22:27] <kbulgrien> jelmer: also agree, but short option then.
[22:28] <AfC> jelmer: {shrug} then bzr has to be. Put another way, bzr was recursive before any of the others :)
[22:28] <jelmer> bug 945904
[22:28] <jelmer> AfC: not before svn (or CVS?)
[22:28] <AfC> modern 3rd generation DVCSen
[22:28] <kbulgrien> CVS was recursive, but not for add
[22:28] <kbulgrien> of directory
[22:28] <kbulgrien> recursive add of all directory contents is bad imo
[22:28] <kbulgrien> very bad
[22:29] <kbulgrien> recursive for anything I'm largely okay with.
[22:29] <kbulgrien> (else)
[22:29] <kbulgrien> but to add new stuff recursively to the vcs is a big giant pain more often than not.
[22:30] <jelmer> why would you have non-versioned and non-ignored files under a VCS directory?
[22:30] <kbulgrien> many reasons
[22:30] <AfC> jelmer: it's incremental;
[22:30] <AfC> jelmer: as you're building a new project
[22:31] <AfC> jelmer: you add a little bit at a time; and I am constantly surprised that "oops!" it went deep.
[22:31] <kbulgrien> exactly
[22:31] <AfC> jelmer: especially when you're being careful trying to add the bits you know you should have under version control
[22:31] <kbulgrien> now try to vcs your OS
[22:31] <kbulgrien> bzr add etc
[22:31] <kbulgrien> oh crap
[22:31] <AfC> jelmer: the END RESULT is yes, you might have added everything, but that's not a conclusion you immediately come to
[22:32] <AfC> jelmer: also things like "yes, I should add the log/ directory as an empty stub... ooops, oh crap"
[22:32] <AfC> anyway
[22:32] <kbulgrien> AfC: you and I think alike.  yes. stubs is another reason.
[22:33] <AfC> I doubt you will be able to change the default behaviour, but a short alias would indeed be lovely.
[22:33] <jelmer> AfC: bug 945904
[22:33] <AfC> jelmer: already subscribed :)
[22:37] <kbulgrien> svn is -N for the same thing
[22:37] <kbulgrien> not that I think we should copy svn
[22:37] <kbulgrien> btw, lest it be seen I popped in to complain, I have been looking for new vcs for a long time. bzr is it.
[22:37] <AfC> kbulgrien: it's a good choice.
[22:37] <jelmer> ... and branch attached
[22:38] <jelmer> we just need to wait for a bzr reviewer to approve it now, and it will be in 2.6
[22:38] <kbulgrien> :-)
[22:38] <kbulgrien> Am slated to convert my work over sometime in not too distant future.
[22:40] <kbulgrien> of all the newfangled vcs, bzr is the most natural progression imo. All others have made me work to adopt. bzr just fits like a glove.  A bit uncomfortable, but just what it seems a vcs should be.
[22:42] <kbulgrien> uncomfortable primarily just like anything new with a lot of stuff in it is uncomfortable, not bad kind of discomfort.
[22:43] <AfC> kbulgrien: our contribution to getting people going on using bzr with our project was http://java-gnome.sourceforge.net/HACKING.html You might find some useful tidbits there.
[22:47] <kbulgrien> bookmarked
[22:49] <kbulgrien> I tried git for a few weeks and borked things up several times while learning and it was hard all the way.  one night I tried to do something I was used to doing in another vcs.  After a long time I found git will not do it.
[22:49] <kbulgrien> I started reading and found probably hg wouldn't either.
[22:49] <kbulgrien> I d/l bzr and it was done in 15 minutes.
[22:49] <kbulgrien> None of the pain of git at all.
[22:50] <kbulgrien> I had never used distributed vcs before.
[22:50] <wilx> Hg and Bzr seem largly equal though.
[22:50] <kbulgrien> treating dirs as explicit versioned resources.
[22:51] <wilx> I have picked Bazaar over Mercurial mainly because the ecosystem seems stronger.
[22:51] <kbulgrien> hg didn't used to.  maybe they changed.
[22:53] <kbulgrien> i didn't even have to look in the manual... what I wanted to do "just worked" when I figured out what to type from built in help.