/srv/irclogs.ubuntu.com/2009/07/10/#bzr.txt

dashCrud00:21
dashshelve ate my changes :(00:22
dashi'm using loom, I shelved some changes, then did down-thread00:22
dashafter doing up-thread and reverting the files, unshelve complains that a file id doesn't exist in the tree00:22
mwhudsondash: :(00:24
dashis there a way to read stuff out of a pack file00:24
dashor partially apply this shelf00:24
mwhudsonprobably00:34
dashthat's great00:34
dashi guess.00:34
jmldash, I don't think there's a way to partially unshelve from the UI.00:36
dashah well, it's only 7 conflicts anyway, i'll just redo it and be careful this time. :)00:37
lifelessdash: please file a bug00:55
lifelessdash: on bzr00:55
dashok00:55
ddaaHey there.01:03
ddaaIt seems reviewboard 1.0 has some trouble handling patches whose base is not in the main history of a branch.01:04
pooliehello ddaa01:05
ddaaHere, I'm submitting reviews with diffs produced by merging repo/feature into repo/trunk, and I base them in reviewboard on repo/feature.01:05
ddaaIt works okay the first time. Then I have a branch "cowbell" which gets an additional commit for review fixes,01:06
ddaaThen "cowbell" is merged to trunk (where a conflict is resolved). And a branch "moreso", initially based on "cowbell", merges trunk back.01:07
ddaaThen I cannot find how to give an updated diff to reviewboard for the changes in "moreso" over trunk.01:07
ddaapoolie: hello pal01:08
ddaaSo, anyone here has experience with reviewboard and could help me?01:08
ddaapoolie: What's up on down under?01:09
lifelessddaa: statik does01:11
* ddaa takes a kitty and rubs it on statik01:12
* ddaa loves to have fun with statik electricity01:12
lifelessddaa: I think he even wrote the reviewboard bzr stufff01:12
* ddaa tries pushing to moreso a merge from moreso into trunk.01:17
ddaaNope, I get again "The file id "None" is not present in the tree <Inventory object at b9a9c4cc... blah blah blah"01:21
ddaaI guess there might be a way to make it work by providing a parent diff, but in this case I have no idea what it should be.01:22
ddaaMh... I guess maybe statik in on the wrong hemisphere to be up at this time.01:24
lifelessis there a bug tracker for the reviewboard bzr plugin01:24
lifeless?01:24
ddaathere's probably launchpad01:25
ddaaactually, it seems not01:26
ddaaI guess it's sharing bug tracker with reviewboard itself.01:26
jmllifeless, can you please create a pqm-managed branch for the 1.17 rc?01:28
jmlor maybe http://doc.bazaar-vcs.org/bzr.dev/developers/cycle.html needs to be updated to say 'ask a losa'.01:28
ddaalifeless: I'm producing the diagnostic data you asked me a few weeks back.01:35
ddaaThe throughput appears to be a bit better now with 1.16.1 on both sides.01:36
ddaaBut it's still very variable.01:36
ddaano clear stalling though01:37
ddaamuch better, 4m9s real time01:38
ddaaComparing now to an upload of a tar of the .bzr in the repo01:39
ddaascp of tar of .bzr, 4m39s real time01:44
ddaameh... it's actually slower than bzr push01:44
ddaamy uplink officially sucks so much they could it in the LHC01:45
ddaalifeless: so nothing to see, bzr push in 1.16 with 1.9 format repo is as fast as uplink. Maybe it was a temporary internet problem, or something to with the structure of the repo just after fast-import runs.01:46
ddaaI guess you are not interested in the -Dhpss log then.01:47
lifelessjml: it should say losa preferentially02:02
pooliehullo jml02:34
poolieddaa, things are good here02:34
pooliebarcelona was nice02:34
lifelessddaa has logged :P02:34
poolieah, i have that squelched in irssi02:39
poolietoo noisy otherwise02:39
RenatoSilvaverterok: https://bugs.eclipse.org/bugs/show_bug.cgi?id=28222603:10
ubottubugs.eclipse.org bug 282226 in CVS "CVS feature abstraction" [Enhancement,New]03:10
* spiv -> lunch03:56
=== NfNitLoo` is now known as NfNitLoop
thumperabentley: ping04:31
thumperabentley: nm04:31
pooliehello thumper04:48
thumperhi poolie04:48
* thumper wishes quassel was smarter with tab completion04:48
abentleythumper: hi.04:50
thumperabentley: I was just wanting a reminder of the bzr send command to send relative to the pipe below, but I found it in my command history04:50
thumperbzr send -r branch::prev.. for those interested04:50
abentleythumper: It's also in "bzr help pipelines".04:51
abentleys/pipelines/pipeline04:51
abentleythumper: Well, the version for diff is.04:52
thumperabentley: right, that is what I wanted04:52
lifelessthumper: glad you like the idea05:10
lifelessthumper: it came out of a discussion with poolie about 'targetting' reviews05:10
lifelessthumper: I'm very keen to mae it easy for people to get engaged without us having to know a-priori who they are05:10
=== poolie_ is now known as poolie
lifelessargs05:24
lifeless(Pdb) locals()['args'][1]05:24
lifelessAssertionError(u"path_utf8 is not a str: <type 'unicode'> base/\u65e5\u672c\u4eba",)05:24
lifeless(Pdb) str(locals()['args'][1])05:24
lifeless*** UnicodeEncodeError: 'ascii' codec can't encode characters in position 46-48: ordinal not in range(128)05:24
lifelessso05:24
lifelesstest suite epic fail05:24
lifelessanother reason not to raise AssertionError - it won't always format sanely ><05:24
spivYeah, exception formatting in Python isn't perfect.05:33
abentleythumper: I'm thinking the "take-changes" command we talked about adding to pipeline should actually be "merge --interactive", i.e. part of core.05:34
thumperabentley: but I only want text changes not any merge revisions05:34
thumperas long as it does that05:35
thumperI'd be happy05:35
abentleythumper: when we do partial merges, we don't set pen ding merges, if that's what you mean.05:35
abentleys/pen ding/pending05:35
thumperwhat about an interactive merge that takes everything?05:35
lifelessI'd love to see that05:36
lifelessI did a hacky one for bzrtools but never wrote enough tests to get it accepted ;P05:37
lifelessthumper: it could ask about full merges05:37
abentleythumper: well, the theory is that it would set pending merges.05:37
lifelessthumper: why don't you want merge revisions though?05:37
lifeless(we plan to eventually record partial merges too, in some fashion, to aid reporting of cherrypicks)05:38
thumperabentley: jml has work in progress for a cleaned up merge interactive I believe05:39
spivThere's always bzr revert --forget-merges if you really don't want merges recorded.05:39
lifelessjml: did you get the branch made?05:40
poolielifeless: those decorator generators are kind of cute06:05
pooliemaybe almost too cute06:05
lifelesspoolie: we have many delta appliers06:07
lifelessI was hoping to structure things to allow reuse06:07
lifelessthey could be structed as 'here, check this list', but that then requires that we have a list06:08
pooliemm06:14
poolieso you could have an explicit 'fan out this iterable' function06:15
pooliethere may be one in itertools?06:15
pooliewhich calls some things for side effects and then yields the results of the original iterable06:15
pooliethis is essentially just to split out the 'for thing:... yield thing' from those functions06:15
poolieto make it clear they don't change06:15
pooliebut i'm not sure that's much better06:16
poolieanyhow, +106:16
lifelessthanks06:18
lifelessI have the test fallout fixed06:18
lifelesshttp://pastebin.ubuntu.com/214176/06:20
pooliek06:20
lifelessif you could eyeball that06:20
pooliei'm going back to bug 39141106:20
ubottuLaunchpad bug 391411 in bzr "want "reconfigure --unstacked" or --stacked-on" [High,In progress] https://launchpad.net/bugs/39141106:20
poolieoh ok06:20
lifelessI just got that done before saying 'thanks' ;)06:20
lifelessit corrects a couple of bugs in the validation code I added by testing against unicode entries, and cleans up some other tests that were expecting a different interface06:21
lifelessand removes a doctest error case that really wasn't very helpful where it was. I did some doc cleanup at the same time.06:22
poolieso in the 'parents = set()' thing06:22
pooliecan you explain in the comment which parents will be in this list06:22
lifelesssure. Its all of them.06:22
poolieall in the whole dirstate?06:22
poolieok06:22
lifelessall in the delta06:23
lifelesswe don't know parents for removed items06:23
lifelessI'll add some text06:23
pooliemaybe change dirname and basename to dirname_utf8 and basename_utf8, as they seem to be06:24
lifelessroger06:24
lifelesswill do the same in check_parents too06:24
lifelesspoolie: anything else? and I'll let you get back to 39141106:27
pooliestill reading06:31
poolielooks good06:32
lifelessthanks06:32
pooliei might put up a patch sometime that renames the other directories to per_workingtree etc06:33
pooliespiv, in bug 391411 i'm thinking about how to do reconfigure --unstacked to an hpss branch06:33
ubottuLaunchpad bug 391411 in bzr "want "reconfigure --unstacked" or --stacked-on" [High,In progress] https://launchpad.net/bugs/39141106:33
poolieit needs to fetch from the fallback repository into the to-be-unstacked one06:34
lifelesspoolie: I would like that; making them consistent again would be nice06:34
pooliei think, unless you know something really clever, i need a new Client06:35
pooliedo you know a tasteful way to get one?06:35
pooliek06:35
lifelessSmartServerClient?06:35
lifelessthey are coupled to the transport; the most robust way would be 'b2 = bzrlib.branch.Branch.open(self.base)'06:36
poolieyeah06:39
pooliethat's what i had in mind too - we don't implicitly share by url, so going back to a url should force a new connection06:40
lifelessI think you should be able to solve this without writing specific code in remote.py at this point in time06:40
pooliei think so too06:42
poolieas i said on the phone it would almost be possible to do it over one connection06:43
pooliebut simple=good06:43
lifelessI suggest a comment about the rationale06:45
lifelessfor review streamlining :)06:45
spivpoolie: yes, I think you need a new client, well a new medium really...06:46
spivpoolie: It might be nice to have a method on _SmartClient that can make a new connection for you, but as lifeless says taking the URL and constructing a new transport from that will work.06:47
GungaDinHow do I change the user to checkout stuff with?06:57
lifelessGungaDin: what do you mean?06:57
GungaDinmy account user is X and I'd like to checkout from the repository as user Y.06:58
poolieover ssh?06:58
lifelessyou can put Y@ into the url06:58
lifelessif its launchpad however, you should use groups to manage this sort of thing, rather than impersonation06:59
GungaDinyeah, alright.07:03
GungaDinit's working now.07:03
GungaDinthx07:03
lifelesshappy to help07:03
lifelesspoolie: EOD; ciao07:09
lifelesswell, nearly07:10
lifelessringing jml first07:10
pooliecheerio07:23
vilahi all07:35
pooliehi vila07:41
vilahey poolie !07:44
poolievila does bug 397716 ring any bells with you?07:50
ubottuLaunchpad bug 397716 in bzr "timezone-dependent annotation test failures" [High,Confirmed] https://launchpad.net/bugs/39771607:50
vilahmm, indirectly yes07:51
vilait's "It's yesterday in California" again :)07:51
poolieagain :)07:52
vilaso, I think there is a TZ arg somwehere that can be used (it was the case for log, not sure for annotate)07:52
pooliearguably we should just set it in the tests for the sake of isolation07:53
pooliehowever i think in some environments setting it after the program starts is not enough07:53
vilaI think the case you're encountering is only relevant in tests (it was the case for log when I saw that), if I'm not mistaken the problem here is that the TZ is not used coherently between commit and annotate, you can't do that from command-line07:55
* vila . o O ( TZ... Yet another interesting test farm variation...)07:56
vilawow, 'tranche' is used in English ?07:58
bob2yes07:58
vilaAnd it applies to ham as well as building houses ?07:59
poolielol07:59
poolie:)07:59
poolieit mostly applies to finance actually07:59
pooliebut it would be a nice word to use for ham07:59
pooliewhere did you see that?08:00
vilabzr.dev@4524 commit message :)08:00
vilano connection to money here :)08:00
vila"a portion of something " says my gnome-dictionary-applet... The french word come from "trancher" i.e. cut with a knive or sword, so I think literal translation should be slice :)08:02
poolieyes, i was just going to say that08:02
pooliei guess with the connotation that, perhaps, you eventually intend to eat all of it08:02
vilaReally ? Interesting, not the case in French :)08:03
fullermdDid somebody say 'eat'?08:03
* fullermd perks up.08:03
pooliemm, actually i do think that's why you'd use that word specifically08:03
pooliethat there are a small finite number and you expect them all to be taken08:04
vilawell, it's really used for ham and you really don't want to eat a full ham, 2 tranches, maybe 3 but no more :-)08:04
vilaha, yes, the set of tranches is expected to be all eaten :)08:05
* fullermd thinks you underestimate his stomach for swine...08:05
* vila wonders what happens when you feed fullermd after midnight....08:06
* poolie gets undistracted08:07
fullermdThat's where adjusting TZ helps, see  ;)08:07
vilapoolie: regarding bug 3977716, looking at test_annotate it looks like the timezone parameter get lost in the refactoring, good diagnosis08:07
ubottuError: Launchpad bug 3977716 could not be found08:07
vilawhat.. too much 7 ? Can't you just fix such obvious typos on the fly ? Come on... bug #39771608:11
ubottuLaunchpad bug 397716 in bzr "timezone-dependent annotation test failures" [High,Confirmed] https://launchpad.net/bugs/39771608:11
vilapoolie: I can reproduce the bug, are you working on it or should I assign it to me ?08:15
pooliei'm not now08:15
pooliei'm trying to finish 391411 before s gets home :)08:15
vilapoolie: ok, go !08:16
lifelesspoolie: interestingly, wiktionary has the finance definition as the 2nd meaning08:16
pooliebegone, forces of distraction08:17
lifelessits friday08:17
lifelessfriday night08:17
poolie:)08:17
vilayeah, they are stronger :)08:17
pooliewell, it is the more specific use08:18
pooliei think it's also the place you most commonly see it08:18
* vila just feels the difference since he changes its TZ to utc+10...08:18
poolienothing wrong with your use of course08:18
* vila blesses the one who removed ctrl-alt-backspace *default-and-hard-to-get-rid-of* shorcut that used to kill the X server, thank you, thank you, thank you08:38
pygivila: why lol? :D08:38
pygidon't be silly, shooting xserver is cool08:39
vilapygi: because the shorcut was too close to alt-backspace which I use a lot and killing my X server without confirmation (yeah I know, non-sense, but yet) and bringing down my http client, mail client, chat client, bunch of emacses just because I mystyped 'delete-word-backwards' is a not excessive for my taste08:41
vilas/not/bit/.... some typos... are... not understandable :)08:41
* vila looks its keyboard... yes io and bn are contiguous on qwerty... clap-clap-clap, well seen big brain :)08:45
vilas/its/his/08:45
pooliethat was quick :)09:01
vilapoolie: still there ? Regarding lp:~mbp/bzr/trivial into lp:bzr, let me know before leaving if you want me to do the tweaks and merge09:29
pooliehi09:47
pooliei am09:47
pooliei think i fixed 39141109:48
pooliethanks for reviewing it09:50
poolieoh you didn't need to spend so long making all those dittos09:51
pooliei probably should leave so if you'd like to sort them that would be nice09:52
pooliei actually have mixed feelings about sorting them as part of an otherwise-mechanical change09:53
vilapoolie: you actually have or had ? The intent of your patch is to be more coherent in naming IMO, that's good reason to *not* break another convention :)10:10
poolie:)10:10
pooliehave10:10
pooliejust in having less risk of breaking things10:10
pooliebut you're probaly right10:11
vilaha ! That should be guarded by a full test suite passing :)10:11
poolie:) true10:16
poolieok, good night10:16
=== sabdfl1 is now known as sabdfl
saedelaerehi, i'am completely new to bazaar and version control system. One thing i don't understand from the manual. I want to ignore to directories completely by "bzr add"12:01
saedelaereas i understood correctly i can use .bzrignore for this task. I tried for example "org_icons/*.*" but still files in that directory will be added. Where do i have to put the file ".bzrignore"? thank you!12:01
fullermd.bzrignore goes in the root of the tree.12:05
fullermdAnd you probably want 'org_icons/*' more, though I guess it likely doesn't make a huge difference in this case...12:06
lamalexHi, i just ran bzr upgrade on my repo and now I get this -> bzr: ERROR: The branch lp:do-plugins has no revision None.12:14
saedelaerefullermd. ok i think i got it12:15
saedelaerethank you12:15
lamalexthis is mm .. kind of serious12:16
lamalexwtfff I can do a merge frm lp:do-plugins but i cant branch12:23
vilalamalex:  I can branch lp:do-plugins without problem from here, what bzr version are you using ?12:27
lamalexvila: really?12:28
lamalexwhat does bzr info -v say for you?12:28
vilalamalex: do you always reply to a question by another question ?12:28
lamalexvila: almsost always12:28
lamalexBazaar (bzr) 1.16.112:28
vilawith bzr.dev I got a repository: Packs containing knits without subtree support, branch format 612:29
vilaand the remote branch has the same repo/branch characteristics12:30
lamalexhmm... what the hell12:30
lamalexi just bzr upgraded it to 1.6.1-rich-root12:30
vilaso that's pack-0.92, it's pretty old now, what did you upgrade from ? And when ?12:30
lamalexand now I can't branch, but you can, and you have the wrong format12:30
vilalamalex: ha, we are not seeing the same branch then, certainly due to the fact that you have write access, so I still see the old one because it hasn't been mirrored yet12:32
lamalexi wonder what wnet wrong12:33
* lamalex restores backup12:33
vilawhat is your .bzr.log saying ?12:33
lamalexvila: http://paste2.org/p/31425612:34
vila1) try without --stacked, 2) try with bzr.dev12:35
lamalexive tried without --stacked12:35
lamalexsame thing12:35
lamalexwill try bzr.dev12:35
lamalexwwait what is bzr.dev12:36
vilawith and without --stacked (although if you have a local mirror using --stacked doesn't gain you much compared to a shared repo)12:36
vilabzr.dev is lp:bzr12:36
vilalamalex: what OS are you using ?12:36
lamalexubuntu 9.04 with bzr ppa12:37
vilahmm, I can try to help you setup bzr from sources but you may prefer switching temporarily to the nightly ppa12:38
lamalexi just reverted it to the pack-0.9212:38
lamalexgoing to try this again..12:39
lamalexis there anything special i should know aobut upgrading?12:39
lamalexi've gotta be doing something wrong12:39
vilawhat did you do ? Why did you chose 1.6.1-rr instead of say --1.9-rr ?12:40
vilaor even 1.14-rr or --default-rr ?12:40
vilaand why do you want to upgrade to start with ? :-) Mainly curious but it may help understand the issue...12:41
lamalexwe want stacked branches12:42
vilalocally or on lp ?12:42
lamalexand we chose 1.6.1-rich-root because I think it was the greatest that jaunty bzr supported12:48
lamalexvila: on lp12:48
lamalexwould you say not to use 1.6.1?12:49
vilahooo, yes sorry, so used to ppas, I forgot about the version shipped with jaunty, but are you sure it's 1.6 that sounds really old...12:49
lamalexRAOF said 1.6, I didnt check myself. I trusted his opinion on 1.6.112:50
vilahttp://packages.ubuntu.com/jaunty/bzr says 1.1312:50
vilaRAOF ?12:51
lamalexa person12:51
vilaha, ok :)12:51
lamalexdoes our packaging, is generally more or less knowledgable about things like this12:51
lamalexso you think we should do 1.13-rr12:51
vilalamalex: no :-) that one doesn't exist but you can use 1.9-rich-root12:52
lamalexheh12:52
vilatry 'bzr help current-formats'12:52
lamalexwhats the advantage of rich-root over normal besides svn/git12:53
npoektopyo! is there a way to ignore executables in my code repository other than marking them with .exe (or smth) extension?12:54
lamalexnpoektop: .bzrignore?12:54
vilanone, but since you are migrating you'd better take the rich-root route once because it will become the default once we reach 2.012:54
lamalexvila: ok :)12:55
npoektoplamalex: how to ignore executables?12:55
vilathe problem is that converting to rich-root is a one-way street, you can't come back nor interoperate with non-rr12:55
lamalexso for upgrading- bzr upgrade --format=1.9-rich-root lp:do-plugins /should/ work?12:55
vilalamalex: yes12:56
lamalexhm12:56
* lamalex runs a check and a reconcile first just to be safe12:56
vilabut then you should also upgrade all branches you want to interact with it12:56
lamalexright, we know that12:56
vilagood reflex, sorry, should have mentioned it :-/12:56
vilathen you need to make sure the branch is mirrored (see #launchpad for that, I'm not sure what the right procedure is needed here)12:57
lamalexwill do12:57
vilasince you have write access to lp:do-plugins, you cant really see the mirror yourself (that's why we got different results)12:58
lamalexi can use a different account12:58
vilathat should do the trick as long as the other account doesn't have write access :)12:58
lamalexheh :)12:59
vilaIs there a LOSA around ? I've got a very stange failure on PQM, as if some old python modules were still present in the working tree... a make clean there may address that13:01
npoektophow to ignore executables in .bzrignore?13:03
vilanpoektop: by listing them either explicitly or by using a regexp, but there are no way to automatically recognize executables (so far)13:04
npoektopnow i mark them with .exe, but it looks ugly13:05
vilanpoektop: to you a lot of them ?13:05
vilanpoektop: do you a lot of them ?13:05
npoektopyes, i have ~/code with many small projects13:06
mzzwell, bzr does know which are marked executable (if you're on a filesystem that supports this) but there's no way to use that info in .bzrignore13:07
mzzI wonder if a plugin could add that13:07
npoektopgood idea13:08
=== kiko-fud is now known as kiko
amanicavila: did you want me to change that test or can I just go ahead and resubmit?13:30
amanica(I need to leave soon for the weekend)13:30
vilaamanica: just a sec, how long soon ?13:31
amanica20 minutes13:31
vilaamanica: it's ok, these tests could use more love anyway, if only to stop matching texts when we can use LogCatcher to get more precise comparisons13:35
amanicavila: I didn't mean to rush you, but thanks. yes that makes sense.13:35
vilaamanica: if you keep working on log, I'd really appreciate if you could try to put more tests in tests/test_log.py and less in tests/blackbox/test_log.py :-D Not a requirement, but I'll appreciate :)13:36
amanicavila, thats a pet peeve of me too13:36
amanicabut that sounds like a project on its own13:36
vilaamanica: no problem, nagging was perfectly reasonable here, I read the whole thread and then forgot that mentioned waiting for a feedback, sorry :-/13:36
vilaamanica: nahh, once test a time :)13:37
amanicacool13:37
vilaamanica: I'd like the log tests to be as concise as the ones I lastly wrote for push and send (if you're interested)13:37
vilatoo many tests try to test too many aspects of log, each time we tweak a particular aspect we have to fix a bunch of not directly related tests: that's a clear sign of bad defect localization :)13:38
amanicavila: cool, an new chalenge! I won't mind doing that if I get time13:38
vilaamanica: great !13:39
amanicait helps if someone is interested enough to review quickly.. thanks13:39
ddaastatik: ping13:39
vilaamanica: I know...13:39
amanicavila: if you have some thought you are welcome to write a short bug on this and assign it to me13:40
amanica/thought/thoughts13:40
vilaamanica: ok13:41
vilaamanica: I need to look at it again, but from memory, some tests can be refactored as is, some needs some refactoring of the code itself to better separate the various aspects, so I need to re-read some code, feel free to ping me again on the subject if I forget to file that bug13:43
amanicavila: cool, and you me13:43
vilaok :)13:43
amanica\me need to go soon13:44
amanicawhoops13:44
vilaamanica: enjoy your week-end !13:44
amanicavila: thanks, you too13:44
amanicabye13:47
=== vila is now known as vila-away
ddaaOk, I found a way to make reviewboard work with my branching and merging situation.14:06
ddaaIt something involving a "parent diff"14:06
ddaaIf I understand correctly, reviewboard expects to have all diffs in the same review to have the same base.14:07
ddaaSo. I have trunk-base as a common base.14:07
ddaaThen I have "feature" revision, and the first diff is trunk-base..feature.14:08
ddaaThen if I have a some more commits in trunk, leading to trunk-new.14:09
ddaaAnd I merge trunk-new in my feature branch, leading to feature-new.14:09
ddaaI must update the diff in the review by specifying the "feature" branch as repository path.14:09
ddaatrunk-new..feature-new diff as the new diff14:09
ddaaand the trunk-base..trunk-new diff as its parent diff14:10
ddaaGeez, that's so fricking complicated!14:10
ddaaIs there a simpler way to say the same thing?14:10
ddaa(jargon welcome)14:10
mzzI'm going to wildly guess you might be looking for "ancestor:" but I haven't actually parsed your problem description14:11
ddaamzz: half of my problem is that i find the procedure to make revie14:11
ddaato make reviewboard happy very difficult to explain.14:11
ddaaSo I'm looking for better ways of explaining it.14:11
npoektopthere is an option for commit: --unchanged, it makes it commit even if no changes in repository. i don't want to commit with no changes and i don't want to see the error message that no changes. it is for crontab task. i don't want to 2>&1 /dev/null because i want to see sufficient errors. how to do that?14:26
=== abentley1 is now known as abentley
lamalexnpoektop: why dont you do bzr stat -V first and only commit if there are changes?14:31
* npoektop reading docs14:32
=== mishok__ is now known as mishok13
npoektoplamalex: thanx14:33
rockstarjam, does TestCaseInTmpDir clean up after itself?14:44
jamrockstar: yes14:44
rockstarjam, great, thanks.14:44
rockstarjam, I should be more specific.  Does it remove the temp dir it creates?14:48
* ddaa still talking alone about reviewboard14:52
ddaaTo state it better, I think what's needed is providing branch-point..ancestor as the parent diff, and ancestor..last as the review diff.14:53
ddaaBut there does not seem to be a way to select the branch point.14:54
ddaaI need something that allows me to find the latest revision that common to the mainline of the current branch and another branch.14:54
ddaas/that common/that is common/14:55
LarstiQddaa: based on -rancestor: ?14:55
* ddaa thinks more... no actually I need something different.14:55
ddaaLarstiQ: kind of. I'm trying to figure a way to state how to feed diffs to reviewboard.14:56
ddaaBut common mainline ancestor does not work when the initial diff is feature-1->feature-2, and a later diff is trunk->feature-2-updated, because feature-1 was merged in trunk.14:58
=== vila-away is now known as vila
vilarockstar: with some help from atexit, yes15:03
rockstarvila, yes, but the TestCase registers that handler right?  I don't have to do anything special?15:04
vilarockstar: nothing special... except exiting from your python script :)15:04
vilarockstar: since you were more specific in your last question I thought you had special use case (or bug) in mind, so I tried to be extra-precise15:05
rockstarvila, thanks!  :)15:06
=== mishok__ is now known as mishok13
rockstarWhat version of bzr introduced HookPoint?15:50
rockstarjam, ^^  Which version did you need for your Windows work yesterday?15:51
garyvdmHi all16:02
jrwrenI'm having some weird issues. we use centralized workflow, and 1 person is having an issue when he does bzr up, he regularly gets conflicts that others don't get. On files that he has not touched at all.16:18
jrwrenmost recently its "file already exists" and moving them to .moved files and showing that as a conflict.16:20
jamrockstar: sorry about the delay.. I don't know what version introduced it. I'll check18:17
jam(I just installed bzr.dev because that was the easiest)18:17
rockstarjam, okay.  Not a big deal, we're just wanting to package a new Tarmac soon.18:18
jamrockstar: looks like bzr 1.13 add hooks.known_hooks18:18
rockstar(We're sprinting on Tarmac currently)18:18
jamreal sprinting, or virtual sprinting?18:19
al-maisanHello there, is there a way to go back a revision in a branch. I did a "bzr pull" but would like to go back to rev N-118:41
Takal-maisan: temporarily, or permanently?18:43
Takjrwren: does it still happen if he does a clean checkout?18:45
jrwrenTak: probably not, no.18:53
jrwrenbut finding why it happens at all would be more useful18:53
Takmy first WAG looking at the symptoms is that for some reason his checkout doesn't think it's on the same tree as upstream18:58
Takor maybe he reverted to some old revision and then updated from the server before reverting to head?18:59
* al-maisan has an idea: I can make another local branch and specify -r before:N19:12
Takor you can `bzr revert -r whatever`19:14
al-maisanah OK19:14
al-maisanThanks.19:15
ftahow do i specify a different email address for a directory containing a lot of branches?20:29
* SamB can't help but think of some kind of alist20:32
=== ddaa1 is now known as ddaa
RenatoSilvaverterok: hi Guillermo, I've answered your comment about bzr-java-lib test. I suspect you don't have UTF-8 set either :) maybe it's just using system's default just like me :) how about including the .project and other stuff in lp's branch?21:12
verterokRenatoSilva: Hi, I just got the email21:12
verterokRenatoSilva: yes, I'm using UTF-8 at a workspace level21:12
verterokRenatoSilva: the eclipse config files are generated by maven21:13
verterokRenatoSilva: I'll look how to force maven to set UTF-821:13
RenatoSilvaverterok: ok, but people could be using bzr-eclipse's new project wizard21:14
RenatoSilvaverterok: and forget to run mvn21:14
verterokRenatoSilva: heh, yes, but in the case of bzr-java-lib, executing mvn eclipse:eclipse is a requirement, it's in the README ;)21:15
RenatoSilvaverterok: ok :)21:15
RenatoSilvaverterok: the file .settings/org.eclipse.core.resources.prefs is the one which stores project encoding21:16
verterokRenatoSilva: oh, nice21:16
verterokRenatoSilva: ok, I'll look into that21:17
RenatoSilvaok21:17
verterokRenatoSilva: fwiw, I landed some branches yesterday in bzr-eclipse (also in the headless build branch) and bzr-java-lib21:19
RenatoSilvaok21:21
=== vxnick_ is now known as vxnick
=== abentley1 is now known as abentley

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