/srv/irclogs.ubuntu.com/2008/04/18/#bzr.txt

jmlpoolie: good morning!00:08
pooliehello jml00:11
=== mw is now known as mw|out
=== BasicMac is now known as BasicOSX
* ToyKeeper discovers, after typing a very long change log, that Escape means "abort NOW" in "bzr gci"02:33
ToyKeeper... poor fingers can't unlearn "esc :w"02:33
lifelessouch02:33
* ToyKeeper files a bug about it02:34
i386_hey lifeless02:40
lifelesshi i386_02:42
i386_lifeless: good news - as of next week im an Apache committer :)02:42
i386_and we need you over for dinner02:42
lifelessindeed02:42
gotgenes`bzr checkout`ing from a Subversion repository that has only a trunk and then unbinding is effectively a full migration of the repository to Bazaar, right?02:49
lifelessyes02:49
lifelessyou may as well just bzr branch :P02:49
gotgenesah02:50
gotgeneseven better02:50
gotgenesthanks lifeless02:50
ubotuNew bug: #218986 in bzr "Escape aborts 'bzr gcommit'" [Undecided,New] https://launchpad.net/bugs/21898602:56
* i386_ wants to use bzr over at this apache project03:01
i386_hows the svn plugin these days?03:01
RAOFi386_: I like it very very much.03:02
i386_Works well?03:02
RAOFi386_: I'm using it to track banshee development & do some hacking, and it works just fine there.03:02
i386_cool03:02
i386_how does it deal with repositories with huge histories ?03:03
RAOFSlowly on the initial branch (obviously), and then just fine from there.03:04
RAOFBanshee is on svn revision > 10K, IIRC. (I don't know, my checkout is on bzr revision 1024 :))03:04
i386_RAOF: can you push back to svn?03:05
RAOFi386_: I _believe_ so, but I don't have banshee svn acces, and I haven't tried with anything else.03:05
gotgenesi386_: by default commits occur like SVN commits, immediately sent over the network to the SVN repo03:05
i386_RAOF: we suffer from a slow checkout time03:05
RAOFgotgenes: Really?  I suppose that depends on how you checked it out, though, since it didn't seem to try for me.03:06
gotgenesRAOF: I did a bzr checkout and it's acting as a bound branch03:07
gotgenesI think that's the right term03:07
RAOFgotgenes: Oh, of course it would, since that'd be the behaviour for checking out a bzr branch.03:08
RAOFgotgenes: I did 'bzr branch', and my commits are local.03:08
gotgenesRAOF: I assume you just do a bzr push to get the commits out to SVN?03:09
RAOFgotgenes: Yes.  If I had write access to that repository.03:09
gotgenessure03:09
jdobrie1how long does bzr branch lp:bzr usually take?03:27
jdobrie1nm i'll just get from my branch03:29
jdobrie1would there be a reason why this works fine: bzr branch http://bazaar.launchpad.net/~bzr/bzr/trunk03:33
jdobrie1but lp:bzr just sits03:33
spivWhat about "bzr branch bzr+ssh://bazaar.launchpad.net/~bzr/bzr/trunk" ?03:34
spivIs that the same as lp:bzr?03:34
spivIf so, it's nothing do with lp:bzr, it's just poor progress reporting when using the bzr protocol rather than plain HTTP.03:35
jdobrie1i will check it out when this download ends.03:35
mwhudsonoh yes, who do i punch about that03:35
* mwhudson downloaded a 400 meg branch from launchpad over bzr+ssh yesterday03:35
jdobrie1ouch03:35
mwhudson'watch du -s' is not really a good progress bar :)03:36
jdobrie1yeah...should break out into metallica videos or something03:36
spivmwhudson: bzr -Dhpss ...  +  tail -f ~/.bzr.log    ;)03:37
jdobrie1with SSH...bzr: ERROR: Connection closed: please check connectivity and permissions (and try -Dhpss if further diagnosis is required)03:37
jdobrie1problem on my config03:38
mwhudsonspiv: not much better03:38
spivOh, bzr+ssh://YOUR-LP-USER-NAME@bazaar.launchpad.net/~bzr/bzr/trunk, sorry.03:38
jdobrie1<------i should have noticed that03:38
spivAssuming you have your SSH public key in your launchpad account (and assuming you have a launchpad account)03:38
spiv(I just have my ~/.ssh/config set use the right username for bazaar.launchpad.net automatically, so I keep forgetting that bit)03:39
jdobrie1no...with username i get the same ...just sits03:40
jdobrie1need to check config and ssh03:40
bob2is there a plugin around that lets you interactively select hunks to commit (ala shelve in reverse)?03:40
jdobrie1somehow we need to do something about google search03:42
jdobrie1type lauchpad bzr and you get massive bug listing03:42
jdobrie1not good PR03:42
spivWell, that's like typing 'bugzilla gnome', really :)03:44
jdobrie1ouch03:44
jdobrie1but true03:44
spivAlthough when I 'launchpad bzr' into google, I don't get bug reports.03:45
jdobrie1add ssh03:46
spivAh, some bugs start appearing.03:47
jdobrie1nevermind i found the problem...it was between my keyboard and chair03:49
jdobrie1forgot to register my new keygen03:50
xenoterracideI'm trying to use the bzr fast-export plugin. I have bzr fast-import installed... but I have this error03:59
xenoterracidebzr: ERROR: unknown command "fast-export"03:59
xenoterracidefast-export is a sub of fast-import03:59
xenoterracideany ideas?03:59
igcxenoterracide: bzr-fast-export.py is a script bundled with the fast-import plugin04:37
igcyou want something like ~/.bazaar/plugins/fastimport/exporters/bzr-fast-export.py ...04:38
igc(no promises that path is correct but you get the idea I hope)04:38
xenoterracideso I should just run the file directly?04:38
igcyes04:38
igcI ought to turn it into a proper command but that's how it is right now04:39
xenoterracideigc: hmm... I'm not that familliar with bzr (or how git fast-import works) I'm in the bzr checkout dir and I know the name of the branch I checked out... running bzr-fast-export.py branch |git fast-import ../project doesn't seem to work04:55
igcxenoterracide: let's take it one step at a time04:56
igcyou should be able to redirect the output of bzr-fast-export.py04:56
igcand check that it looks right04:57
igcI'd have to read the git-fast-import man page but ...04:57
igcyou probably need to be in the dir holding the .git directory?04:58
xenoterracideI'm not sure... looks docs over04:59
igcthere's some notes at the top of the python file too04:59
igci.e. the top of bzr-fast-export.py05:00
xenoterracideright. I totally hate sounding like an ungrateful ass, but these progs really, really need better docs05:02
igcxenoterracide: true05:02
xenoterracideI'll have to write something up once I figure it out05:03
xenoterracide:P05:03
igcplease do - thank would be good05:03
xenoterracidewhat does --export-marks=marks.bzr doe the name matter? or is it just a file?05:04
igcjust a file05:04
igcsee the git-fast-export man page for an explanation05:05
igcsorry - git-fast-import05:05
xenoterracidewaits... hopefully thats working05:09
xenoterracideok... export seems to have went well now I have an import error05:35
xenoterracidequestion is where is the problem05:35
xenoterracide http://vim.pastey.net/85948 git import who should I be bugging the bzr repo owners? git? or the bzr-fast-export maintainer05:42
igcxenoterracide: my guess is that the bug is most likely in bzr-fast-export05:54
xenoterracideso who do I complain at? you?05:54
igcdato was the original author of it, though it's now part of bzr-fastimport so probably me05:55
igccan you raise a bug in lp?05:55
igcthe project should be bzr-fastimport05:56
xenoterracidelp=launchpad?05:56
igcyes05:56
igceither james_w or myself will look into it for you05:56
igcothers might too05:57
xenoterracideigc: yeah I've filed a couple hundred bugs before. but never where I had 3 possible parties who could be at blame...05:59
xenoterracideactually 406:00
igc:-)06:00
xenoterracidealthough I have one that I've yet to file thats worse06:00
xenoterracideit affects every browser in linux06:00
xenoterracideand most programs, except a few...06:00
xenoterracidecould be the font yet some programs handle it correctly06:01
xenoterracideso who's problem is it06:01
igcyuk06:01
xenoterracideI really should report it to mozilla because it crashes ff 100% of the time06:01
xenoterracidebut no browser renders it right06:01
xenoterracidebut OOo and the font browsers handle it fine06:02
xenoterracideoh and it only affect *nix systems06:03
xenoterracidewindows ff does it fine06:03
xenoterracidebut was reproducable on mac06:03
xenoterracidewho would you bother first?06:04
igcwho's most likely to care about getting it fixed?06:05
xenoterracideI don't know...06:06
xenoterracideigc hmm... it says project doesn't exist in gentoo.... this may rank as my new top crappy bug tracker06:08
mneptokxenoterracide: does it crash Epiphany? Konqueror?06:09
xenoterracidewait I figure lp out06:09
xenoterracidemneptok: doesn't crash konq or opera but it is rendered improperly06:09
xenoterracideI haven't tried epiphany06:09
mneptoksounds like X font rendering, killing Gecko and not playing nicely with KHTML. can the font be used locally in, say, OO.org docs without issue?06:10
xenoterracideyep06:11
mneptoknot X06:11
xenoterracideI haven't tried X directly06:11
mneptokit's broswer rendering. report the crasher against Gecko if it kills Epiphay.06:11
mneptok(now *there's* some half-assed triaging!)06:12
* mneptok flexes06:12
xenoterracidewell it wasn't just browser I had a problem in another kde program06:12
* xenoterracide doesn't remember which one06:12
xenoterracideprolly kwrite06:12
mneptokwell, to be fair, it's not a bzr issue, so ...06:13
xenoterracideI know06:14
xenoterracidejust talking about haywire bugs06:14
mneptokand i supposedly quit working 2h ago.06:14
mneptokand now, i shall. g'night xenoterracide. hello PS3.06:14
xenoterracideheh06:15
xenoterracidehttps://bugs.launchpad.net/bzr-fastimport/+bug/219042 poof06:18
ubotuLaunchpad bug 219042 in bzr-fastimport "fast-export doesn't export right" [Undecided,New]06:18
xenoterracide;P06:19
igcnight mneptok06:21
TFKylethe crashing stuff could be pango, though if it doesn't crash normal gtk apps maybe not directly06:58
TFKyle(and I'd expect it to crash the gnome font viewer if it was pango too)06:58
TFKyleoops, he's gone06:58
pooliespiv: how is the patch for the line delta bug?07:07
spivpoolie: just pushed a new version of it, was about to send to the list after selftest passes.07:08
spivget_revision_file returns a KnitVersionedFile where delta=True, which is wrong.  So the patch just forces delta=False, and teaches insert_data_stream how to convert a line-delta record to fulltext if not self.delta07:09
spivThis fixes the bug with the test branch, as well as giving a local repo with a clean (i.e. all fulltext) revision knit.07:10
spivI don't have tests in my patch yet, but the approach is still reviewable without that, so I'll send to the list first before worrying about that.07:11
poolieok, thanks07:15
pooliei'll look at it07:15
spivOk, selftest with the existing suite passes, bundle sent to the list.07:23
pooliei'm just writing a mail about 1.4,07:23
pooliei think we should merge these things and do a 1.4rc2 this afternoon07:24
pooliebut leave final for next week07:24
pooliewhat do you think?07:24
spivI'm inclined to agree.07:24
igcpoolie: I agree. I think we need an rc2 for 1.4. We want those people who went back to 1.3.1 when they found problems to kick the tires again.08:07
igcor "tyres" in the case of us Aussies :-)08:08
=== quicksil1er is now known as quicksilver
poolieigc, thansk08:29
poolieigc, spiv, i don't think i'll have time to make it today though, i have a commitment with stephane08:30
pooliei will try to do it on the weekend08:30
igcpoolie: ok. I'm heading off rsn also fwiw08:30
spivpoolie: ok.  enjoy your weekend (well, the non-work bits at least :)08:31
matkor_Hi ! What is  submit branch: in bzr info ?08:46
pooliematkor_: it's the public url of the branch you want to merge into08:47
poolietypically the main branch of your project08:47
matkor_poolie: Hmm, I do not remember me merging into remote branch ... usually I merge to local checkout of main branch, resolve conflicts and commit ... How could I create it ?08:49
pooliematkor_: iirc the submit branch just controls the default for bzr send08:50
matkor_poolie: Thnx a lot ! I will read on about bzr send08:51
igcnight all - have a good weekend08:53
pooliehello james_w08:57
poolie(leaving soon)08:57
james_whi poolie08:57
james_whave a good weekend08:58
datoigc: I'm happy to look at bzr-fast-export bugs too09:26
datoigc: though if you prefer to look into this one, I'm happy to. the problem seems to be that we're instructing git-fast-import to rename a directory, when we shouldn't be doing that.09:28
james_whi dato09:31
datohello james_w09:31
james_wif that is the issue then it may be worth talking to Shawn, as it seems that possibly should be allowed.09:32
james_wwell, git should just ignore it, but I don't see why it should reject it.09:32
datouhm, no, I'm mistaken09:36
datopath/dir1 was renamed to path/dir2, and it seems that was accepted (of course)09:36
datoand then path/dir1/fileX was renamed to path/dir2/fileY, and that boomed09:37
james_wso a directory rename is recursive to git-fastimport?09:38
datowell, it is to bzr as well, ain't it?09:39
james_wI'm not sure how it's represented internally09:40
james_wI would expect bzr-fastimport to do that though09:40
datomaybe bzr-fast-export should do some ordering, I'm not sure09:43
jelmermwhudson: hi10:46
jelmermwhudson: should pydoctor work on .so files?10:46
bjesushey, i had a bzr server to which we did 'bzr update' and 'bzr commit' every once in a while11:02
bjesusbut it's down, so i got a new one11:02
bjesusand i have the last commit on my computer11:03
bjesusso i coppied it to the new server11:03
bjesusand now i want everyone to 'bzr update' from it and 'bzr commit' to it.11:03
bjesusthe thing is - it always tries to connect to the old server11:04
bjesusand since the old server is down, i can't seem to use the new one.11:04
datobjesus: try `bzr unbind; bzr bind new_server_address_and_path`11:05
bjesushow can i make a directory created from a 'bzr checkout' and 'bzr update' to something i can checkout and update from?11:05
bjesusthanks i'll try11:05
bjesus'bzr unbind' gives me a long error ending with:11:06
bjesusRuntimeError: maximum recursion depth exceeded11:06
bjesusi can't even see where it's starting11:06
bjesusthe thing is - if 'a' is the old server, 'b' is my user pc, and 'c' is the new server - b used to do checkouts and updates from a, but what if c wants to checkout and update from b? is that possible? to change the centeral location?11:08
datoc wants to update from b?11:08
datoI thought you wanted b to update from c...11:09
bjesusbasically yes, but it seems like simply copying the directory doesn't work, so if i'll update c from b, i'll surely be able to afterward update b from c, and every other computer from c11:10
bjesusit seems like it's all about changing the central server, since if i could make the latest-updated-computer a new server, i could checkout it from everyother location and then make the new location the new server.11:13
=== mrevell is now known as mrevell-luncheon
=== mrevell-luncheon is now known as mrevell
jdobrienlarstiq: i had a couple of questions so i could proceed working on the bug i'm working on13:28
LarstiQjdobrien: shoot13:28
jdobrienwhat commands should the change i am making effect?13:30
jdobrienstatus is obvious, diff too?13:30
jdobriencat?13:30
jdobrienlarstiq: nm not cat13:32
LarstiQjdobrien: ignore perhaps13:34
jdobrienlarstiq: other question is, you mention <someone> may have already created some unit tests. can't remember who you said and not sure where to look for them13:34
mwhudsonjelmer: ?13:35
mwhudsonnot here though, send email13:35
jdobrienk13:35
LarstiQjdobrien: can't find it at the moment, but it wasn't much13:36
LarstiQjdobrien: I'd focus on status first though13:36
jdobrieni was relying on the online log and we apparently were in a private chat when you gave me the name :-/13:38
jdobrienk13:38
jdobrieni was going to create a separate test for the expected behaviour first, then i would assume i should mod the existing tests for status13:39
jdobrienlarstiq: opinion?13:41
LarstiQjdobrien: previous tests might not be needed to modified13:43
LarstiQjdobrien: bzrlib/tests/blackbox/test_status.py is where I'd add them13:43
jdobrienk13:43
jdobrienso no reason to create 'new' tests13:44
jdobrienjust put them in the status black box testing13:44
jdobrienlarstiq: thanks. im still obsorbing python so i appreciate the patience.13:46
LarstiQjdobrien: at first, for testing that the commandline status output is what you expect, certainly in the status blackbox13:46
LarstiQjdobrien: np, have a look at the rest of the tests to get an idea13:46
jdobrienyeah i have been13:47
LarstiQcool13:47
jdobrienlarstiq: im used to using nunit/junit so it's not a big leap13:47
jdobrienlarstiq: the diff between staticmethod & classmethod had me spinning for a few hours last night...different behaviours in c#13:49
=== ja2 is now known as jam
=== mw|out is now known as mw
ubotuNew bug: #219246 in bzr "exceptions.KeyError on log" [Undecided,New] https://launchpad.net/bugs/21924616:20
dwtHey, guys, how can I see what will be pushed to a remote location when I say "bzr push"?16:53
dwtwithout pushing it16:54
grutte_pierisn't there a option to do this?16:54
datodwt: bzr missing --mine-only16:54
dwtseems to work16:55
dwtgreat!16:55
dwtthanks guys17:00
=== weigon_ is now known as weigon
VSpikeIs there any good solution for pushing code from a bzr branch to a webhost via ftp?  I've been looking at rsync and lftp, but rsync has to use curlftpfs which is not reliable, and lftp depends on date stamps, which bzr trashes.  I seem to remember mention of a plugin?17:15
Verterokmoin17:20
=== kiko-afk is now known as kiko
=== mario_ is now known as pygi
james_wVSpike: bzr can push to ftp17:32
james_whowever it doesn't update/create the working tree, meaning your files won't be visible on disk, you'll only see a .bzr17:33
james_wthere is a plugin to work around that, but it uses ssh, so you're back to square one if you need it.17:33
VSpikejames_w: ah yeah, that's my problem in a nutshell17:45
VSpikeso, no way around it at present?  I guess I just have to ftp up everything every time.17:48
Stavroshello17:50
Stavrossuppose there is a branch to which i only have read-only access, but i want to add a patch, would it be feasible/sane to keep a local copy with the patch indefinitely and still merge the changes from the remote branch in it?17:51
beunoStavros, you should be able to just branch17:53
beunoadd your path17:53
beuno*patch17:53
beunoand keep on merging indefinitely, yes17:53
Stavrosah, great17:53
beunomany of us do it on a daily basis17:53
Stavroswould this be easy?17:53
Stavrosor would every patch need manual adjustments?17:53
Stavroserr17:53
Stavrosevery merge17:53
beunoStavros, nope, you should be fine17:53
Stavrosah, that's great17:53
beunoI do regular:  bzr merge && bzr ci -m'Merge from trunk'17:54
beunoyou might have occasional conflicts17:54
Stavrosthat solves the big problem of adding features to various 3rd party packages17:54
beunobut you might not  :)17:54
Stavroswell yes, true17:54
Stavrosbut overall, it sounds much easier17:54
beunoStavros, yeap, I think that's one of the ideas behind DVCS17:54
Stavrosgreat great17:55
beunonot needing write access to the main branch to work on it and use version control17:55
Stavrosyes, i was more worried about the "indefinitely" part :P17:55
beunoyou'll just have to merge n commit instrad of pulling17:55
beuno*instead17:55
beunoisn't too painful17:55
Stavrosyes17:55
Stavrosi agree17:56
Stavrosgreat great17:56
Stavrosi love bzr17:56
beunowelcome to the club  :)17:56
Stavrosi have been a member for a while :p17:56
Stavrosi use it rather exclusively17:57
Stavrosdoes bzr-svn with authentication work in linux?17:57
beunoStavros, I don't use it, but AFAIK, yes18:04
beunojelmer would know more about this18:04
Stavrosah, thanks18:05
[cliff]hi all!18:09
[cliff]is it possible to use, or somehow simulate, nested branches with bzr?18:10
beuno[cliff], LarstiQ is the man to answer that18:10
[cliff]so I'll have: branch1, which contains references to branch2 and branch318:11
beunohe hides sometimes, but if you win the waiting game, you'll eventually get a good answer for that  :)18:11
[cliff]thanks beuno18:11
[cliff]lol18:11
[cliff]thanks18:11
beuno[cliff], alternatively, you can email the list18:12
[cliff]yeah, but I was trying to avoid subscribing to yet another mailing list :-)18:12
beuno[cliff], right, then "waiting game" seems like your best option for a good answer18:14
[cliff]right... subscription is it :-)18:26
[cliff]cheer-io-s18:26
LarstiQright, right18:36
beunoLarstiQ, don't hate me  :)18:36
LarstiQbeuno: I don't :)18:37
LarstiQbeuno: more myself really18:37
jamLarstiQ: well, it was unclear if he was willing to "fake" it, or if he needed the real thing18:37
LarstiQjam: right. But regardeless of what he wants, it still needs to be done18:38
beunoLarstiQ, it's just a recurring ping to either iron out the remaining failing tests, or start merging parts of the code so someone else could potentially take over  :)18:38
LarstiQbeuno: thank you for doing that18:39
beunoLarstiQ, it's a selfish thing, I've got a use case for it at work  :p18:39
LarstiQjam: I believe you sent a mail related to it? I haven't yet looked at that18:47
LarstiQbeuno: that's ok18:48
jamI don't remember sending anything but a ping18:48
tolstoyFolks!  Is there a way to merge a bunch of commits into one commit?18:48
LarstiQjam: ok18:49
tolstoyIn other words: bzr branch local, commit 1, commit 2, commit 3, then merge those as one big commit/patchset?18:49
LarstiQtolstoy: and you're not meaning a regular merge? :)18:49
jamtolstoy: depends what you think that is18:49
jamtolstoy: generally a regular merge will add 1 new commit to signify the joining18:49
jamand 'bzr log --short' will only show that.18:49
jamIf you want to completely remove commits 1,2,3 from the history you can:18:50
jambzr revert --forget-merges18:50
jamafter the merge18:50
jamso it looks like it was all freshly done18:50
jamor you can18:50
tolstoyI could make lots of little "daily back up commits", then branch at some early point, and merge a big diff and commit that, and toss the original, but was wondering if there was something less clever.18:50
tolstoyjam: forget merges, ah, okay.18:50
jamcommit 1, 2, 3; bzr uncommit -r -3; bzr commit -m "this is the new tip for 1,2,3"18:50
jamtolstoy: you probably want 'uncommit' then18:50
tolstoyjam: Oooo, I like that. Cool.18:51
asabilis there a way to change the email used in previous commits ?19:17
beunoasabil, unfortunetly, no19:17
beunothe previous commits are immutable19:17
asabil:/19:17
beunoasabil, I'm working on bug 215334 to try and avoid committing with the wrong info19:18
ubotuLaunchpad bug 215334 in bzr "Bzr shouldn't permit users to commit without setting author info" [Wishlist,Confirmed] https://launchpad.net/bugs/21533419:18
asabilbeuno: that's the not the problem19:19
asabilI really think that bzr needs something like git-filter-branch19:19
beunoasabil, right, then it's a different use case  :)19:19
beunoI think the versioned properties bit would be what would solve this19:20
beunosome work was done towards it19:20
beunobut I'm not sure what the status is19:20
asabilok :/19:20
lifelessbeuno: how would versioned properties solve this?20:17
beunolifeless, unless I'm completely lost on what it is, wouldn't the committer be a property which could be changed, with the change being versioned so we still have the original information preserved20:19
beunoIIRC, something like this was discussed in the sprint, although I might be confused  :)20:19
ubotuNew bug: #219334 in bzr "Texinfo version of the documentation" [Undecided,New] https://launchpad.net/bugs/21933420:21
lifelessbeuno: this is exactly why I object to 'generic versioned properties'20:22
lifelessbeuno: the answer is no, because its a chicken and egg problem20:22
lifelessbeuno: revisions contain the committer; the revision graph describes the tree20:23
lifelessbeuno: log would be at least twice as slow if every lookup had to indirect back into the tip revision tree; and the proposed single file property store would fall over cold on something like ooo20:24
beunolifeless, I see. In which cases would versioned properties be applied then?20:24
lifelessbeuno: I don't know of any other than eol; and I don't htink its a good fit there.20:25
lifelessbeuno: I want eol badly; I just think this generic versioned property is a dead end introduced because 'svn has them' back at some point in design discussions20:25
beunolifeless, seems reasonable. Although, the issue about changing previous commits comes up too often for us not to look into some kind of workaround. There might not be any, but still, we should keep on trying20:26
beunolifeless, right, I think it's an overkill too, if it's just going to be used for EOL20:27
lifelessbeuno: if we want to allow changing of commits we just add another authoritative timeline20:27
=== mw is now known as mw|lunch
lifelessone that is not human derived; but this adds massive complexity in design (e.g. which attributes can be edited; is there security; how to deal with conflicts)20:28
lifelessas well as performance considerations, and the issues of explaining that this is going on20:28
beunoright, a heap load of work20:28
lifelessthis is why none of darcs/git/monotone/hg allow it20:28
beunoand there are much important issues ATM20:28
beunolifeless, I'm working on being more verbose to people about what info they are committing with20:30
beunoto try and narrow that down a bit20:30
lifelesscool20:30
lifelesswell 5:30, I am going to take a couple of panadol and try to sleep20:30
beunobut I suspect this will just keep coming up  :)20:30
beunoheh20:30
beunook20:30
beunosleep well!20:30
lifelessthe generic answer to 'I want to rewrite my history' is 'ok rewrite your history'20:31
lifelessbye20:31
asabilbeuno: I wasn't asking really about changing the previous commits20:31
asabilbut about creating a new filtered branch from the original one20:31
beunoasabil, right, but in order to change previous authors, you change the commit metadata, so it's more or less the same. You might be able to use rebase plugin and some other black magic to do that, but this is really out of my knowledge  :)20:33
asabilthanks anyway for the tips20:34
beunoasabil, :)20:34
foomthe problem with "ok rewrite your history" is that afaik you can't do that without screwing over all your developers. it would be nice to be able to rewrite your history and not have it blow up everyone's checkouts. If the history you're rewriting doesn't end up affecting the current revision, that should at least be theoretically possible.20:38
* beuno wonders where jelmer is with the new bzr-gtk release20:52
lifelessfoom: well21:00
lifelessasabil: I think a filter branch command might be useful; it does need to rewrite the graph though as in git21:01
lifelessfoom: indeed; thats why rewriting history isn't part of regular bzr workflows, and why looms does not do it.21:01
asabillifeless: yes I think so as well21:01
lifelessbeuno: I think you've got the wrong end of asabil's stick.21:01
foomlifeless: a solution to the "Nuclear Launch Codes" problem would be nice, though...21:01
lifelessbeuno: asabil means 'create a new branch with history derived from the old one (synonymous graph, but different ids), and some other arbitrary differences besides'21:02
lifelessfoom: indeed. I believe heavy radiation is the cure :P21:02
beunolifeless, right, so they become different branches. It's different from what I meant21:02
beunoI was looking at preserving it for other derived branches to keep working21:03
asabilI don't minds having different branches21:03
* beuno wonders how long lifeless's panadol takes to kick in :)21:03
asabilas long as the filtered one retain the time stamp and the commit messages21:03
lifelessbeuno: its failing to21:03
beunolifeless, double or nothing?  :p21:04
lifelessbeuno: anyhow, consider the problem of indexing a database with two different values for the same unique key :P21:04
lifelessshortly, you'll be sharing my headache21:04
beunohehe21:04
beunoright21:04
beunoI like it on this side of the fence for now  :)21:05
=== mw|lunch is now known as mw
beunoso, if I understand this correctly, asabil might be able to pull off what he wants, with some python and bzrlib knowledge. Would be a nice plugin too21:05
=== Kinnison_ is now known as Kinnison
VantageHi all, does anyone know of any strategies for converting and merging cvs modules into one bzr shared repo?21:42
asabilVantage: https://launchpad.net/bzr-cvsps-import21:44
asabiland http://bazaar-vcs.org/BzrFastImport21:45
Vantageasabil: Converting isn't a problem, but because the CVS tree was all modules, I end up with 15-20 shared repos.  I now want to try and merge them into one tree (that is itself a shared repo)21:46
Vantageor rather one new top level repo with all history21:47
asabilnot sure I understood what you want exactly21:48
asabilyou meant 15-20 branches21:49
asabilnot 15-20 shared repos21:49
asabilno ?21:49
=== doko_ is now known as doko
ubotuNew bug: #219357 in bzr "UnboundedLocal error when trying to bundle revisions for a branch" [Undecided,New] https://launchpad.net/bugs/21935721:51
Vantageasabil: when you use cvsps-import it generates a no-trees repo with all the branches and history.  So I have 15-20 of those21:52
Vantageeach with their own branches and history converted21:52
asabiloh right21:52
asabilVantage: you can maybe bzr init-repo21:54
asabiland then bzr branch <branch>21:55
asabilinside the repo21:55
asabilfor each branch in the other repos21:55
Vantageasabil: our original cvs repo used nested trees to build a codebase and share modules around, etc.  Since bzr doesn't support that, we have to figure out another way to do it.  The easiest seems to be to just get rid of the modules and merge it all into one tree21:55
Vantageasabil: Hrmm that could get quite tedious.  I suppose it could be scripted though21:56
asabilI see21:56
Vantageasabil: Unless you know of a better approach?21:56
asabilyes, a small shell script should do21:56
asabilunfortunately not, but I am not used to importing from cvs21:56
asabilor rather, am not used to repository administration at all :)21:57
asabilmaybe you can just wait for someone who is more knowledgeable about it :)21:57
asabilsorry21:57
Vantageasabil: no problem.  Thanks for the advice21:59
cpintohey all22:20
cpintojohn meinel around?22:20
cpintojam, we were exchanging emails on the bzr ml22:21
cpintoabout nested projects and co'ing project subdirs22:21
jamyou changed your name, weren't you [cliff] before22:21
jam?22:21
cpintoyeah22:21
cpinto[cliff]'s a legacy handle :-)22:22
cpintoanyway, what I was looking for was for a way to be able to work around a python issue (actually it's a non issue but i'm stuck with it)22:23
cpintoso I have about 5 different bzr repositories22:23
cpintoand all of them have the same directory, let's call it metapackage. each repository then tracks different code in the metapackage, so in repo-a I have metapackage/a, in repo-b I have metapackage/b, etc.22:24
cpintowhat I wanted was to be able to branch repo-master which contains metapackage, and inside of my local branch to be able to branch repo-a's metapackage/a, etc22:25
cpintoso in the end22:25
cpintoi'd have, metapackage/a and metapackage/b22:25
cpintobeing metapackage developed in one repository, a in another and b in yet another22:26
cpintocurrently, the best I can have is metapackage and metapackage/metapackage/a, metapackage/metapackage/b22:26
jamcpinto: can you use symlinks?22:27
jamalternatively, you could look into python .pth files22:27
jam(i think that is what they are), they control the search path22:27
cpintoor, as you suggested, just symlink the directories but I'm a bit wary of that. can you explain a bit further how bzr handles symlinks (ideally picking up my example)22:28
jamor you can hack into "metapackage.__path__" to change the search path22:28
cpintoyeah, I've though of .pth too22:28
cpintoyeah, I've thought of .pth too...22:28
pekujaI'm having some trouble figuring out the BzrEclipse plugin23:31
beunopekuja, what seems to be the problem?23:32
pekujahmn...23:32
pekujawell that's weird, it's working now...23:32
pekujaone thing that I did find weird though is when I'm enabling Bzr for a project, pressing "Finish" apparently initializes the repo, but the window stays open23:33
pekujawhich was a little confusing23:33
beunopekuja, could you file a bug for that?23:33
pekujayeah23:33
beunothe developer is not currently here23:33
beunoso the best way to get it solved is to report bugs  :)23:33
pekujaalso, the Bzr menu was disabled... it doesn't seem to be disabled now though23:33
pekujaso I'm not sure I can provide useful data on that now23:34
beunopekuja, I believe it has to detect the project has an actual branch to be enabled23:34
beunoso it might have taken a bit longer for it to detect it23:34
keithyheel os there an installer for tiger23:35
keithyhello, is there an installer for tiger23:35
keithy?23:35
beunokeithy, it seems that only for PPC:  http://bazaar-vcs.org/Download23:35
pekujabeuno, by the way, is the Bzr-menu the way I'm supposed to use the plugin? nothing wrong with that, it just seems a little rudimentary I guess23:35
beuno(tiger is 10.4, right?)23:35
pekujaor do you use it yourself?23:36
keithythat'l do nicely23:36
beunopekuja, what do you mean? What would be the alternative?23:36
pekujabeuno, heh, frankly, I'm not sure. one thing for example that would be nice if it showed be what files I've changed since the last commit in the project view23:37
beunopekuja, AFAIK, it does23:37
beunowith decorators23:38
beunobut I don' currently have it installed23:38
beunodid you download the latest release?23:38
pekujamaybe I need to enable it separately23:38
pekujaI had to do that for the Bzr menu23:38
pekujahmn, I guess that would also be a bug report / feature request for me23:38
pekujait doesn't really expose a lot of its functionality by default23:38
beunopekuja, check out: http://bazaar-vcs.org/BzrEclipse/Screenshots23:39
beunopekuja, yes, I do think you have to manually enable it23:39
pekujayeah, I found where... it doesn't seem to be working though23:40
pekujaalso, yeah, I have the latest release I think23:40
pekujait's from the update site23:40
beunopekuja, I don't really know what could be causing it.  I haven't had issues with that myself23:41
beunoare the files versioned?23:41
pekujayes23:41
pekujait seems like Eclipse is not finding BazaarLightweightDecorator23:41
beunopekuja, sounds like a bug report to me  :)23:42
pekujahmn, I think I'm going to try reinstalling the plugin just in case23:42
beunopekuja, I'm pinging the developer now to see if he's bored enough to drop by here   :)23:43
pekujaheh23:44
pekujanice23:44
beunopekuja, meet Verterok23:45
VerterokHi, pekuja23:45
Verterokbeuno: thanks ;-)23:45
beunoVerterok, :)23:46
* Verterok reading the irc log23:47
pekujahi23:48
Verterokpekuja: could you check the Error log view?23:54
pekujayes, it says "java.lang.NoClassDefFoundError: org.vcs.bazaar.eclipse.ui.decorator.BazaarLightweightDecorator"23:55
pekujaI think I might have just fixed that though...23:55
Verterokpekuja: huh, thats weird. that class is from the ui plugin23:56
pekujaI was able to make the error go away by adding ~/.eclipse/org.eclipse.sdk.ide/updates/eclipse/plugins to the Plugin path of the Bazaar plugin23:57
pekujain Preferences->Team->Bazaar23:57
Verterokpekuja: thats not the idea of that config field :)23:57
Verterokpekuja: it's for bazaar plugins23:57
pekujahmm, nope, I'm getting the error again23:57
pekujayeah23:57
pekujait didn't really seem to make much sense23:57
pekujaI also get "Problems occurred when invoking code from plug-in: "org.eclipse.jface"." before the NoClassDefFoundError23:58
Verterokpekuja: which OS, Jvm version and eclipse versiĆ³n are you using?23:58
Verterokpekuja: also bzr and bzr-xmloutput versions :)23:59
pekujahmmmm23:59

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