/srv/irclogs.ubuntu.com/2012/06/18/#bzr.txt

gourmorning07:43
gouri've few programs for which i keep their config files under dvcs...now we are going to switch to bzr and wonder whether you recommend to use lightweight checkouts for 'working trees' and keep repos separately with --no-trees ?07:44
mgzmorning08:10
jelmerhi08:17
* jelmer is having fun fighting with pbuilder chroots09:36
mgzand I thought you had debian packaging entirely tamed jelmer... are the chroots defeated yet?10:29
jelmerish10:29
jelmerthe fact I'm running quantal seems to be breaking me up :)10:29
jelmermgz: what mischief are you up to?10:29
jelmeralso, we still seem to have a fair number of issues with encodings in 2.6 :(10:32
mgzthe usual silliness, and seeing what hacks need fixing or documenting before I can post the mp I promised last week10:32
mgzjelmer: just need to merge all our branches up I think10:32
jelmermgz: from where?10:33
mgz2.2->2.3 and 2.5->2.6 and some of the ones inbetween10:34
jelmerk10:35
gour  /q10:50
mgzjelmer: I see you've started the merge up, but 2.3 doesn't seem to have landed and you've got 2.3->2.4 up?11:18
=== zyga is now known as zyga-food
abentleyjam, is anyone patch-piloting?  I have a couple MPs I'd like reviewed.13:59
jamabentley: I think we're watching the queue, but nobody is specifically focused on it. You're welcome to request reviews.13:59
=== zyga-food is now known as zyga
=== yofel_ is now known as yofel
gouri just played a bit with bzr's lightweight co-s emulating "Switching a lightweight checkout" section (http://doc.bazaar.canonical.com/bzr.dev/en/user-guide/reusing_a_checkout.html) and i had a feeling that this feature should enable me to create sandboxed directory wich is goingto be populatd by different working trees based on the 'switch' command15:21
gournow i see that it works this way :-)15:21
gourbut i must say that the code example was (is) a bit misleading to me...so i propose the following one...15:22
gourhttp://pastebin.com/cRi6vYgB15:25
gourconclusion: treeless branches in (no-tree) shared repo, feature branches, lightweight checkouts...easy switching between them...great stuff and we love bzr's simplicity & power :-)15:27
mgzgour: note also `bzr switch -b NAME` to create sibling feature branches is handy15:31
gourmgz: hmm, does it mean, if i'm e.g. on master branch, that bzr switch -b feature1 branch will 'clone' a master branch into feature1 and switch on it?15:33
mgzyup.15:35
gourvery handy...thumbs up15:35
gourit seems to me that bzr is really nicely designed despite changing its format (too) often in the past, so understanding why so many people are enamored  by git is well beyond me :-}15:37
LeoNerdFormat changes should have been prettymuch invisible to users, though15:40
gourLeoNerd: well, it was a bit irritating in the past16:04
LeoNerdEh.. it was a mild inconvenience at times but I don't recall ever being actually uspet by it16:05
jelmergour: the last format change is more than three years ago at this point16:08
gouri know that 2a is stable and do not complain...just sayign that16:13
gourforamt changes in the past created a feeling that bzr is not stable...that's all16:14
gourotherwise i wouldn't be here today ;)16:14
mgzjelmer: bug 1014626 / 1014627 should still be dupes of bug 966934 I think, were they from after you did the 2.5 merge to dev?16:32
ubot5Launchpad bug 1014626 in Bazaar "UnicodeEncodeError formatting translated message during merge" [Medium,Triaged] https://launchpad.net/bugs/101462616:32
ubot5Launchpad bug 966934 in Bazaar "[i18n] bzr commands affected working tree crashed with unicode error in non-english locale" [High,In progress] https://launchpad.net/bugs/96693416:32
JordiGHHow do you checkout/update to a past revision?17:38
mgzuse -r, see `bzr help update`17:40
JordiGHI did see it, but I couldn't figure out what -r meant.17:40
JordiGHAm I using the right word?17:40
mgzdepending on exactly what you're trying to do, you may want revert instead.17:40
JordiGHI want my working tree to be at a specified revision.17:41
mgzdid you try it?17:41
JordiGHYeah, but I don't know if it worked.17:41
JordiGHHow do I know at what revision I'm currently in?17:41
mgz`bzr revno --tree`17:41
JordiGHOkay, is that done with revert or update? I did both.17:42
mgzrevert changes the state of the tree (files on disk), but not the branch, update changes both17:43
mgzso, after a revert, `bzr st` will tell you stuff has changed from the current branch state17:43
JordiGHBut update seems to try to merge changes...17:44
JordiGHI ended up with merge conflict markers.17:44
JordiGHI don't want that.17:44
mgzdid you have local changes?17:44
mgzchanging the tree always means you may get conflicts17:45
mgzif you're sure there's nothing in the current state you want keep, a plain bzr revert will throw everything out17:46
JordiGHI didn't make any, but I don't know if bzr decided I had changes because there's been updates and reverts.17:47
mgzperhaps, if you're not sure, you can always look at your .bzr.log to see exactly what happened17:47
mgz`bzr version` will tell you where to find it.17:48
=== zyga is now known as zyga-afk
JordiGHOoh, nice feature.17:48
mgzand you can always get a copy of an older revision cleanly by creating a new tree, `bzr checkout --lightweight -r-6 . ../old_rev` for instance17:48
JordiGHSo, just to make sure I have the right terminology...17:49
JordiGHif I do "bzr update -r foo" that means change the state of the current directory to whatever is stored in that branch?17:50
JordiGHWhat happens if you commit there? Do you just painlessly branch off?17:50
JordiGHWait, what is a "branch" in bzr?17:50
JordiGHIt's not a path in the DAG, is it?17:50
JordiGHIt's also a working directory?17:50
mgzsee <http://doc.bazaar.canonical.com/beta/en/user-guide/core_concepts.html>17:51
mgzif you try to commit it will prevent you from doing so by default17:53
mgzwhat you probably want is two branches, but just work in the one directory17:56
mgzas that's what I imagine you're used to with other tools17:57
mgzif you describe the actual task you're trying to do, rather than just the step, that might help17:58
JordiGHNo, what I'm used to with hg is to commit wherever I want and for things to branch off naturally.18:17
JordiGH"branch" in bzr also seems to mean "working tree".18:17
JordiGHOr directory.18:17
jelmerJordiGH: a branch is a line of history18:18
JordiGHDoes "branch" also mean "clone" in bzr? You even use the branch command when you want to clone a repo.18:25
jelmerJordiGH: a branch and a clone are the same thing at the moment18:34
jelmerJordiGH: since each control directory usually holds a single branch, and not multiple like in git or hg18:35
JordiGHAlright.18:36
JordiGHSo how do you branch off at a past revision?18:36
JordiGHYou update to a past revision, and you do a special kind of commit?18:37
jelmerJordiGH: update the branch to a past revision or update the working tree state to the same state as in a past revision?18:44
jelmer"bzr up -rREV" for the first, "bzr revert -rREV" for the latter18:44
JordiGHSo "update the branch" means... what?18:45
jelmerJordiGH: resetting the branch to an older revision18:45
jelmerI guess the equivalent in git would be "git reset COMMITTISH"18:45
JordiGHAnd "the branch" means the working directory?18:45
JordiGHI don't do git.18:45
jelmerJordiGH: no, the branch is the history18:45
JordiGHSo reset the history?18:46
jelmerJordiGH: so "bzr up -rREV" would make the branch look like the history ended at REV18:46
JordiGHHow do I see the DAG?18:48
jelmerJordiGH: bzr log18:48
JordiGHThat's just the log entries.18:48
JordiGHHow do I see what's an ancestor of what?18:48
jelmeror for a more graphical one, "bzr qlog" or "bzr viz"18:48
JordiGHbzr: ERROR: unknown command "viz"18:48
JordiGHBut qlog seems to be doing something...18:49
jelmerJordiGH: the log will show that (right hand side ancestors are shown indented)18:49
JordiGHStarting Qt?18:49
jelmerJordiGH: viz is part of the bzr-gtk plugin, qlog is part of the qbzr plugin18:49
JordiGHSo it's like git that when you update to an earlier revision, it looks like later revisions disappear?18:49
jelmerJordiGH: well, that's if you use "bzr up -rREV"18:52
jelmerif you just want to reset the working tree to the same state as in a previous revision, use "bzr revert -rREV"18:52
JordiGHBut then bzr st thinks I modified all files.18:52
jelmerJordiGH: right, because the last revision didn't have those changes18:53
jelmerJordiGH: and bzr st by default shows the changes between the working tree and the last revision18:53
jelmerif you just want to create a new revision that resets the state of the tree, just commit chose changes18:54
jelmere.g. bzr commit -m "Revert back to rREV."18:54
JordiGHHow does bzr keep revisions centralised?19:28
JordiGHheh, idgi19:28
jelmerJordiGH: they're in the control directory (.bzr/repository)19:31
santagadaI want to see a graph of two branches, what they have in common and what differs in terms of commits, how can I do that with bzr?19:42
jelmersantagada: bzr missing19:50
santagadajelmer: thanks19:51
santagada:)19:51
santagadajelmer: docs don't mention missing... or I didn't find it19:51
santagadabut thanks a lot if really did solve my problem19:54
santagadanow I will slowly merge revisions that are missing19:54
JordiGHA pull also updates, right?20:18
JordiGHAnd an update also merges, right?20:18
jelmerJordiGH: in the hg terminology, pull indeed also updates the working tree20:18
JordiGHHow can you pull revisions without touching the working directory?20:19
MvGHi! IWe've got a Windows machine here with TortoiseBzr which reports a lot of x-bit changes for a working tree. I'm a bit confused about this, as I didn't think Windows NTFS had such a thing. I guess most regular Windows users would be even more confused. Can someone around here tell me what could give bzrlib the idea of such changes?22:25
mwhudsonis there some cute way i can suppress this message:22:25
mwhudson<doanac> I also finished the conversation with some advice I told him I realized he didn't have to pay attention to.22:25
mwhudson<doanac> i said - if i were you, I'd focus on making zach happy (even in spare time), because that's the best thing you could do for your career right now22:25
mwhudson<doanac> he said he understood, but I don't think he can resist this urge.22:25
mwhudson<mwhudson> heh22:25
mwhudson<mwhudson> he really is a strange guy22:25
mwhudson<doanac> I think he's wanting to create an entirely new community that's a "fork" of LAVA22:25
mwhudson<doanac> I asked "fork"? he said - well, a rewrite is a kind of fork22:25
mwhudson<doanac> i found that part a bit amusing22:25
mwhudson<doanac> its not like anybody can stop him, but I had to be clear he can't use "lava" in the branding of what he does22:25
mwhudson<mwhudson> good idea22:25
mwhudson<doanac> and maybe we'll come crawling back to him some day. as he said, finishing up the rest of porting stuff to lava-core was easy :)22:25
mwhudsonoh ffs22:25
mwhudson!22:25
mwhudsonYou have not informed bzr of your Launchpad ID, and you must do this to22:25
mwhudsonwrite to Launchpad or access private data.  See "bzr help launchpad-login".22:25
lifelessmwhudson: which message :P22:31
mwhudsonlifeless: the one about launchpad :(22:31
lifelessbzr launchpad-login mwhudson, I think.22:32
mwhudsonlifeless: without doing that22:32
lifelessdon't use lp: urls.22:32
mwhudsonlifeless: i have been using bzr and launchpad for a /little/ while after all...22:33
mwhudsonyeah, that might be easiest22:33
lifelessor use bzr's library22:38
lifelesswhats the use case ?22:38
mwhudsonlifeless: just avoiding spam when running a script22:38
mwhudsonlifeless: just half a thought that there might be some config option i could set22:38
=== jelmer is now known as Guest12454
Guest12454mwhudson: you can set launchpad_username ?22:58
mwhudsonGuest12454: i want to use the http transport, but don't want to be nagged about it22:59
Guest12454ah22:59
Guest12454we discussed having a lp+http:// URL scheme at some point22:59
Guest12454but that never emerged22:59
=== Guest12454 is now known as jelmer
mwhudsonjelmer: ok23:01
mwhudsonjelmer: i guess if that itch strikes again i know what to do...23:01

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!