/srv/irclogs.ubuntu.com/2010/06/19/#bzr.txt

=== lifeless_ is now known as lifeless
davidstrausslifeless: Is there a way to manually manipulate merge data?01:01
davidstrausslifeless: Like, let's say you commit a merge to a public branch. You can't uncommit, but you want to revert the merge *and* have the merge tracking data reflect that.01:01
fullermdNo, because there isn't "merge tracking data", there's only ancestry.01:04
davidstraussfullermd: Is it possible to "unzip" part of the ancestry?01:08
fullermdYeah, with uncommit   8-}01:11
davidstraussfullermd: but that works poorly for public branches01:15
davidstraussfullermd: other people's checkouts show the removed commits as "local commits"01:16
fullermdWell, that's the fallout.  You can't have something in your ancestry and not in your ancestry at the same time.01:21
fullermdAnd making ancestry somehow nontransitive would just be unutterably evil.01:21
davidstraussfullermd: ideally, we'd have a way to record the reversal01:25
fullermdWell, ideally a lot of things.  But that would be a very fundamental change.01:31
taxiliananyone here used the webdav plugin for bzr that might be able to help me figure out why I can't push or commit over webdav?  it keeps telling me that it can't obtain the lock03:52
taxilianand then sits there forever and dies03:53
lifeless4/quit04:58
=== nlisgo_ is now known as nlisgo
jelmertaxilian: vila is the best person to talk to about the webdav plugin10:16
=== khmarbaise_ is now known as khmarbaise
jjannHi. I have some checkouts of bzr and svn repositories in one of my repositories. I don't want to treat them special (ie use some externals mechanism or something), just add them with their repository meta-data, how can I do this?15:37
jjannright now, bzr status shows me the contained repos' top level directories as unknown but bzr add doesn't add them15:38
jjann(even a 'bzr add -v some_contained_repos_toplevel' just prints out nothing and some_contained_repos_toplevel/ just keeps showing up as unknown in bzr status)15:39
jjann(I'm using bzr 2.1.1 on lucid)15:39
jelmerjjann: hi15:42
jelmerjjann: if you want bzr to just treat the .svn directories as data, uninstall bzr-svn15:42
jjannjelmer: hm, I use bzr-svn on other repositories though. and what about the .bzr directories?15:43
jjannessentially you're saying I really should be using externals?15:44
jelmerjjann: I don't think there is any way to treat .bzr directories as plain data15:44
jjannok, bzr-eternals it is then, thanks15:45
jjannlet's hope I'll get by with this better than I did with mercurial subrepos :)15:46
jjannI'm confused. I installed bzr-externals, I deleted one of the bzr subrepos, I did 'bzr eadd lp:foo the_dir; bzr ci -m "add lp:foo"'15:54
jjannand after that, the_dir/ still shows up as 'unknown' in bzr status15:54
jjannok, seems to be some broken old state from previous attempt, doesn't happen in a fresh clone. sigh. :-)15:55
jelmerjjann: I'm not entirely sure if bzr-externals will do what you want15:56
jelmerit won't allow you to use 'bzr add' as far as I know15:56
jelmerit will will in a way similar to svn:externals15:56
jjannyeah, it uses 'eadd', which I did16:04
jjannI was just surprised that the newly added external shows up as 'unknown' in the status output16:04
jjannbut it seems similarly underused and underdocumented as hg subrepos. I keep wondering how most users seem to get by without such a feature. git really is the only one of the 'modern' DVCSes that takes this seriously :(16:06
jjann(but git was rejected quite early in our evaluations to find a replacement for svn for various other reasons)16:07
jelmerjjann: bzr-externals are a hack for the fact that nested trees aren't supported in bzr yet16:08
jelmerjjann: we've been planning that feature for ages but it keeps stalling because we haven't managed to design something that works well in all cases, scales and doesn't require a lot of special casing16:09
jjanninitially I was hoping to get by with adding the .svn and .bzr directories as plain data since bzr has the nice advantage of tracking directories as well as files (the lack of that feature is the reason that treating svn checkouts as normal data doesn't work in hg for example)16:09
jelmerjjann: alternatively  you can use the --no-plugins argument when adding .svn directories16:09
jjannthat still would only solve half my problem. I'm currently considering hacking my own super low-tech variant, just renaming .bzr and .svn repos pre and post update16:10
jjanns/repos/directories/16:10
jelmerjjann: is there any reason for wanting to keep the other repositories' control directories around, rather than merging them in?16:11
jjannjelmer: they are repositories that don't belong to me and that I want to be able to update easily during project lifetime (ie they are external library dependencies and somesuch)16:12
jelmerjjann: you would simply be able to merge in newer versions still16:12
jelmerjjann: as bzr remembers the common history with those projects16:13
jjannby keeping their meta-data around, I can browse their changelog, I always know what revision of them I have16:13
jjannhm16:13
jjanncan I merge a repo inside a sub-directory of my repo?16:13
jjannie bzr merge lp:foo libs/foo?16:13
jelmerjjann: yes, although it works a bit different from that16:13
jelmerjjann: you'd want to use "bzr join" to combine the two repositories originally16:13
jelmerafter that you can use "bzr merge"16:14
jjannoh, never even read about join, thanks!16:14
jjannI must admit I don't get how exactly join works (or what exactly it does) from its help output. the naive variant of 'bzr join lp:foo' doesn't work at least and I'm not even sure that's what I want16:18
jelmerjjann: if you want to have lp:foo live at lib/foo you would run something like:16:18
jelmerbzr branch lp:foo lib/foo; bzr join lib/foo16:18
jelmerbzr commit -m "Merge in lp:foo"16:19
jelmerAfter that "bzr merge lp:foo" will do the right thing and update just lib/foo16:19
jjannbrilliant, thanks16:19
jjannand it works perfectly with svn repos as well, nice16:23
jjannalso, I love the "revision folding" bzr does, with the nice folder-like feeling in qlog, fits perfectly here16:24
jjannI really must say, when I started evaluating bzr, hg and git, bzr was the one I had heard the most bad things about and still it keeps comming out on top now that I'm actually testing it myself16:25
jjannso there really needs to be some publicity work done I think ;)16:25
jelmerjjann: Great to hear, thanks :-)16:29
jelmerjjann: Our initial performance issues have caused a lot of harm I think.16:29
jjannright "it's too slow!" was one of the things I heard most. also "it changes it's repository format like every release, it can't be stable/good"16:30
abostromhum17:13
abostromhelp needed: i have committed three patches to my branch. if i do "bzr bundle", i get a single patch.17:14
abostromdo o need to send three bundles upstream if i want to preserve history? or are the patches hidden somewhere in the blob at the end?17:15
jelmerabostrom: they're in the blob at the end17:15
abostromok, but if i make a fresh branch and merge my bundle, i get only a single commit17:18
abostromtrying merge -r gives "bzr: ERROR: Cannot use -r with merge directives or bundles"17:18
abostromaaah17:20
abostrombzr log --include-merges17:20
abostromi see17:20
abostromthanks :)17:21
jelmernp :-)17:23
assadwhile doing a bzr diff between two branches: bzr diff --old ARG it says branch ARG , so how do i access the branch name? is it some relative addressing ?18:28
assadwhat is ARG equal to in that command18:28
=== radoe_ is now known as radoe
wamillsHi,  I'm new to bzr, but know git.  I am trying to create a branch from a lp tag.  Which of these commands does that?23:00
lifelesswhat do you mean by 'lp tag'23:04
jelmer'morning lifeless23:09
lifelesshi jelmer23:09
lifelesswamills: what do you mean by 'lp tag'23:09
wamillsOK I made a branch of gnome-terminal but it is the latest development.  I want to create a branch based on 2.29.6 tag. Like is used in the current Lucid package23:11
wamillsgit checkout -b my-fix 2.29.623:12
lifelesstags in bzr are a property of a branch23:14
lifelessso you need to know what branch the tag is in23:14
lifelessif you want a branch of the lucid package for gnome-terminal, you can do 'bzr branch lp:ubuntu/lucid/gnome-terminal23:15
lifelessand you can query the tags with 'bzr tags -d lp:ubuntu/lucid/gnome-terminal'23:16
wamillsOK, my first error was starting with the wrong base.  I guess lp:gnome-terminal is just tracking upstream yes?23:17
lifelessyes23:18
wamillsOK let me get to the right project.23:18
wamillsOK so 2.29.6-0ubuntu5 is the latest tag so I could make changes. commit & push to personal branch right?23:24
lifelessyes23:24
lifelessif you're making a patch for ubuntu you don't need to worry about tags at all though23:24
lifelessjust23:24
lifelessbzr branch lp:ubuntu/lucid/gnome-terminal (for making a patch for lucid)23:25
lifelesshack hack hack23:25
lifelessbzr commit23:25
lifelessbzr push lp:~USERNAME/ubuntu/lucid/gnome-terminal/BRANCHNAME23:25
wamillscool.  Thats good enough for what I am doing today.  I'll RTF(abulos)M for more.23:27
lifelessplease feel free to hop back in and asj23:27
lifelessits the weekend23:27
lifelessso a bit quieter than normal :)23:27
lifelessalso #launchpad for launchpad questions is pretty good23:27
lifelessand #ubuntu-motu or #ubuntu-packaging for packaging related things (like how to change a package version number etc)23:28
wamillsThanks!  Good suggestions.23:28

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