/srv/irclogs.ubuntu.com/2010/05/20/#bzr.txt

igcmorning00:30
spivGood morning.01:05
igcmorning spiv01:07
lifelessspiv: feeling better ?01:29
spivlifeless: yes, thankfully.01:30
spivI can't guarantee I won't brainfade in the afternoon again... but so far so good, and without cold&flu pills!01:31
cody-somervilleugh01:37
cody-somervilleI just did a merge of two trees of the same codebase that have no revision ancestry. There are very little differences between the two trees but bzr conflicts on all the files because the year in the copyright statement at the top of the files were all updated.01:39
cody-somervillewill trying a different merge method help or bzr just won't be able to figure this out on its own?01:41
lifelessyou could write/adapt/improve jams copyright plugin01:43
lifelessspiv: would like to talk gil stuff with you at some point01:43
lifelessok, really popping out for these chores/lunch01:43
spivlifeless: ok01:44
=== joerg_ is now known as joerg
spivWe're starting to get on top of the review backlog from the sprint :)03:07
lifeless\o/03:07
lifelesslosa ping03:18
spmyo03:19
lifelesscan you check balleny's bzr 2.1 branch03:19
spmlifeless: sure, in what sense check tho?03:19
lifelessI think the xmlrpc server fell down went boom just as pqm went to do the 2nd-phase push03:19
spmahh. right.03:19
lifelessso there will be another commit in that branch vs lp03:19
spmmanually push the sucker?03:20
spmlifeless: https://pastebin.canonical.com/32485/ so yeah, looks to me like '42 missed03:21
lifelessplease sir may I have another03:21
spmlifeless: Pushed up to revision 4842.03:22
lifelessthanks a lot03:23
spmnp03:23
lifelessnow I can do -> bzr.dev03:23
lifeless:)03:23
spmheh03:24
lifelessgarh, bzr-search not-quite-fixified.03:33
lifelessspiv: does bzr merge --weave still call NEWS helper ?03:38
cody-somervilleugh03:43
cody-somervillelets say I have two branches03:43
cody-somervillethe second branch is a branch of the first branch03:43
cody-somervillein the second branch, I've moved files using bzr move03:44
* lifeless waits for launchpad03:44
lifeless6 ppm03:45
lifeless:<03:45
cody-somervillewhy is that if I make modifications to those files I moved under the original name in the first branch that when I merge the first branch into the second branch I get a text conflict for the original filenames?03:45
spivlifeless: I don't recall, I *think* so03:45
lifelesscody-somerville: you shouldn't03:46
lifelesscody-somerville: please file a bug03:46
spivcody-somerville: in the situation you just described, you shouldn't.  Either there's a bug, or the situation isn't as you described.03:46
cody-somervillelifeless, I can only assume that maybe I didn't use bzr move when I thought I did?03:46
spivYou can look at the file-ids03:47
lifelesshave a look at bzr log filename03:47
cody-somervillehow do I do?03:47
lifelessin branch203:47
spive.g. "bzr file-id FILENAME"03:47
lifelesswith -v03:47
lifelessif it shows the rename, you used bzr mv03:47
cody-somervillesighs03:49
cody-somervillewasn't moved03:49
cody-somervillebecause I merged the first branch into another branch to initial create the 'second branch' and that was a bzr-git import and it shows the files were deleted and then added with new name.03:50
cody-somerville*initially03:50
cody-somervilleAny way I can give bzr the extra meta-data?03:51
lifelessno, this is a hole.03:52
* cody-somerville sobs.03:53
lifelessor rather, not trivially.03:54
lifelessyou can probably rebase, if you hit things hard enough03:54
lifelessthere is a file id mapping feature in that plugin03:54
lifelessdamned if I know how to use it though :()03:54
cody-somervilleI'm trying to manage two series of a codebase03:54
cody-somervillebut upstream decided to create a new git branch (or w/e its called in git) for the new series.03:55
=== tchan1 is now known as tchan
lifelessjam: bzr in C ? I've got a few libraries you might want04:35
lifelessjam: that are slowly building up towards that04:35
lifelesse.g. libvfs04:35
=== timchen1` is now known as nasloc__
lifelessanyone want to keep CHK1/CHK2 formats around?04:44
spivI wouldn't think so04:44
spivThere are always old releases if someone does.04:45
lifelessbleh04:48
lifelessRan 24411 tests in 1013.377s04:48
lifelessFAILED (failures=1, errors=72, known_failure_count=47)04:48
echo-areahello, I got error "Invalid url supplied to transport" when doing bzr checkout svn+http://url04:53
echo-areawhat's the problem?04:54
echo-areathanks04:54
spivecho-area: do you have the bzr-svn plugin installed?  (check the output of 'bzr plugins')04:54
=== Toksyury1l is now known as Toksyuryel
echo-areaspiv: yes, if I do bzr checkout svn+ssh://other-url, I am prompted to input the password.  But I can't, since the subversion repository is not accessible by ssh for me04:55
spivecho-area: odd.  pastebin the entire error?04:56
echo-areaok04:56
=== davidstrauss_ is now known as davidstrauss
=== lifeless_ is now known as lifeless
=== FryGuy_ is now known as FryGuy-
echo-areaspiv: http://pastebin.com/khtwepfF05:02
lifelessback soon05:34
echo-areadoes somebody have an explaination to my bzr-svn problem?07:14
spivecho-area: I don't, sorry07:17
echo-areaspiv: no problem, thank you07:21
echo-areadoes bzr-svn require pycurl?  I found it mentioned here: https://answers.launchpad.net/bzr-svn/+question/1129907:22
lifelessbzr bzr plugins07:22
lifelesssorry07:22
lifelesscheck the output of 'bzr plugins'07:22
lifelessI suspect its not loading, and the error will be in bzr.log07:22
echo-area(to support svn+http)07:22
vilaecho-area: It's not *required* AFAIK, but used if available07:23
echo-arealifeless: http://pastebin.com/khtwepfF  <--  output of bzr plugins is pasted here07:23
lifelessvila: bzr-svn uses the svn http core, can't use anything else07:24
lifelessecho-area: and is svn in the list ?07:24
vilalifeless: the current run on pqm says (lifeless) Merge 2.1 into 2.0, you meant 2.0 into 2.1 right ?07:24
lifelessblah 2.1 to trunk07:24
echo-arealifeless: yes, it is "16.svn 1.0.2"07:24
lifelessok07:25
lifelesscheck your .bzr.log just in case there is an error there07:25
vilalifeless: it still uses any available bzr client for some operations (can't remember which but at least OPTION is involved and jelmer asked me to support that directly far too long ago)07:25
lifelesssure07:26
vila" blah 2.1 to trunk" cool !07:28
echo-areaI've updated the pastebin content.  An exception is thrown when the plugin tries to connect the server07:29
echo-areahttp://pastebin.com/xsj7q0Ca07:29
echo-areait's here07:30
echo-areaI guess the problem is in subvertpy, let me check07:33
vilaecho-area: try using 'bzr plugins -v' the paths used will displayed and may help you detect a problem in your setup, and as lifeless mentioned, check your .bzr.log ('bzr version' will tell you where it is located))07:37
echo-areavila: done; the content of .bzr.log reflected the error has been pasted.  Btw, when bzr-svn calls subvertpy functions, is the "svn+" part of url stripped off?  I.e., at line 249 of transport.py of bzr-svn, does the url parameter begin with "http://" or "svn+http://"?07:41
spivI'd expect stripped.07:42
spivBut ICBW.07:42
echo-areaI don't have experience using python before, and I want to change subvertpy's code, so I need help: in this expression _ra.RemoteAccess(url, *args, **kwargs), which field of the definition in the C code of _ra.RemoteAccess is the function gets called?07:53
vilaecho-area: before modifying code, have you tried using -Dtransport as an additional parameter to the command ?07:55
vilait should output more debug stuff to .bzr.log07:55
echo-areavila: no, let me try now.  Do you mean bzr co -Dtransport svn+http://...?07:56
vilayup, it may give you what you are after with this code modification with a bit of luck07:56
echo-areavila: sadly there's no more output I've not seen.07:59
spivecho-area: that Python expression will invoke ra_new in subvertpy/_ra.c (via a little bit of indirection)08:06
=== radoe_ is now known as radoe
echo-areaspiv: yes, and I've located the PyTypeObject "_ra.RemoteAccess" in _ra.c, but that definition does not give me any clue which function to look further08:09
spivecho-area: see around line 2071, PyTypeObject RemoteAccess_Type = {08:11
spivecho-area: which defines various builtin operations that can be done with a Type object, and also defines the methods and members of that type.08:12
spivecho-area: specifically, the constructor for that type roughly corresponds to the tp_new slot (right at the bottom of that struct definition)08:12
spivecho-area: and arrays like ra_methods defines the methods instances of that type will have08:13
spivecho-area: so _ra.RemoteAccess(...) is calling the _ra.RemoteAccess constructor, which as I said before will mean the ra_new function in that file.08:14
spivecho-area: does that help?08:15
echo-areaspiv: yes, that's enough knowledge for me to dig deeper.  Thank you!08:15
spivecho-area: great :)08:16
spivecho-area: any luck?08:42
echo-areaspiv: no, I was interrupted and am doing other things now.  I expect myself solving this problem before the weekend09:56
echo-areas/solving/explaining/09:56
=== mrevell is now known as mrevell-lunch
LorHi. If I have a directory hierarchy with several branches under it, synchronizable across machines easily with multi-pull or repo-push, is there any way to easily synchronize changes to the actual hierarchy layout?12:59
LorBefore nested trees are production quality, that is.12:59
=== dcoles_ is now known as dcoles
=== joerg is now known as Guest86
=== mrevell-lunch is now known as mrevell
=== Guest86 is now known as joerg
LorAlso, why must the shared repository of a branch always be located in a parent directory?14:11
LorSeems like it wouldn't be very complicated to simply record the location of the repository in branch.conf14:11
jjannHi. Is there some way to colorize bzr diff output? (similar to what git and hg offer)14:39
bialixjjann: look at cdiff command from bzrtools14:49
jjannbialix: that's perfect, thanks14:49
=== tchan1 is now known as tchan
guijemontjelmer_: vila: ping15:55
guijemontI have a bzr-gtk branch that implements collapsing with which I am quite happy now15:57
guijemontshould I do a merge request through launchpad?15:58
guijemontor a bzr send to the ml?15:58
guijemontor something else?15:58
=== deryck is now known as deryck[lunch]
vilaguijemont: a merge request with a cover lettter explaining if and how you share code with qbzr would be the best16:01
vilaguijemont: did you tested it with a mysql or emacs branch ?16:02
guijemontvila: my branch still uses ye olde linegraph()16:02
guijemonthmm, i didn't, good idea16:02
guijemontI tested it with itself, and with lp:elisa16:02
vilatrying with bigger branches may help unless you're into adding automated tests (which are painfully lacking so far)16:05
guijemontI think it will make sense to add some automated tests when the code is refactored to use the qbzr graph generation stuff16:10
vilaguijemont: hehe, TDD is about doing it the other way around i.e. write tests first :-)16:12
vilaguijemont: but it's harder to do TDD with an existing code base and no tests16:12
guijemontvila: yeah, and with a code base that doesn't separate things well16:13
fullermdOh, no, it's much easier.  Your changes never break tests   :p16:13
vilafullermd: you're on the right path young jedi, the next step is to realize that the only that should be written is one that fix a test :)16:14
vilas/only/& code/ mandatory typo...16:15
cbzwhen i access a svn repo with bzr can it track renames?16:15
cbzas it seems to stop displaying history for a file at the point at which it was renamed16:15
fullermdErgo, bzr-gtk is already perfect.  QED   :)16:15
vilahaaaaa, that's why it's so hard to ehance code without tests, I should have think about that sooner :)16:16
=== IslandUsurper is now known as IslandUsurperAFK
vilawow, time travel again... I see files created in the future... (5mins and 1.5hours)16:26
fullermdMaybe you're just slow   :p16:27
vilathe really weeird thing is that 'date' displayed value seems correct16:27
guijemontreminds me of today's smbc16:28
guijemont(or was it yesterday?)16:28
vilanope, all on the *same* system, no mounted fs involved (that would be too easy :)16:28
guijemontyeah, today16:28
guijemonthttp://www.smbc-comics.com/comics/20100520.gif16:29
vilaarf, no samba there :)16:29
vilaguijemont: :)16:29
=== davidstrauss_ is now known as davidstrauss
guijemonthmm, I have a few "maximum recursion depth exceeded"16:52
guijemontthe code looked good when using recursion :/16:52
jelmer_guijemont: what do you recurse on?16:52
guijemontdon't remember16:53
guijemontI might do that in more than one place16:53
guijemontI'll have a look at the backtraces in more detail16:54
=== deryck[lunch] is now known as deryck
guijemonthmm, actually, the place where I get this is weird16:55
guijemonti think i need a break before plunging into that16:56
GaryvdMHi bialix16:59
GaryvdMJust landed stable scroll for qannotate \o/16:59
vilaGaryvdM: Really ? Is it really what I think it is ?17:00
GaryvdMHi vila, I think it is what you think it is.17:01
vilaGaryvdM: that's awesome !17:01
vilaGaryvdM: you rock :)17:01
mgzBut is it what I think you think he thinks it is?17:01
=== Chex_ is now known as Chex
GaryvdMlol17:01
* GaryvdM thinks about landing lp:~garyvdm/qbzr/annotate_find. Does it really matter if the ui is inconsistent for a while?17:03
vilaGaryvdM: doesn't matter to me :)17:03
vilamgz: I think I see what you mean...17:03
vilaboom, maximum recursion depth exceeded in discussion17:03
vilaGaryvdM: what matters though, is that some bindings should be defined there :-P17:04
GaryvdMvila: I don't understand17:05
vilareturn should be bound to next by default17:06
jamhi vila and GaryvdM17:07
LorIs there a recommended way to put multiple branches under a single working directory?17:07
Lor(With the intention that the working directory is used to switch between the branches)17:07
vilawhen I enter text the 'Find:' field, I'd like 'return' to give me the next match without touching my mouse17:07
GaryvdMvila: ok17:07
GaryvdMvila: You and Craig both gave me some feed back. I will go through that first.17:08
vilaLor: I don't use that setup myself, but AIUI, lightweight checkouts and the switch command OR the bzr-colo plugin are different ways to achive that today17:14
LorAh, didn't know about bzr-colo.17:15
LorIs it some sort of a hack to simulate nested trees until they are fully supported by the core?17:15
LorAh, no.17:16
LorRight.17:16
GaryvdMLor: Not nested trees. Rather collocated branches.17:19
GaryvdMLor: Like git17:19
LorRight, I'm reading the docs now.17:19
LorIt's just an alternative directory layout convention for lightweight checkouts?17:19
LorDoes it work with bzr-pipeline?17:20
=== beuno is now known as beuno-lunch
GaryvdMGoing out for a bit. bbl17:24
cbzjelmer_: are you there?17:29
=== IslandUsurperAFK is now known as IslandUsurper
LorIs there really a performance overhead for storing multiple unrelated projects in the same shared repository?17:41
jelmer_cbz: hi17:50
cbzjelmer_: does bzr-svn track renames? it appears that it's history of files i renmamed stops at the point i renamed them18:00
jamLor: "bzr init-repo --no-trees project; cd project; bzr init branch1; bzr co --lightweight branch1 work18:03
jamLor: from there you can do: 'bzr branch --switch ../branch1 ../branch2"18:03
jamor18:03
jam"bzr switch -b branch2"18:03
LorI was asking about how to put branches under a _working directory_.18:04
Lorbzr-colo seems to provide a sensible convention and tools to make its usage easier18:04
jamLor: well, you can do:18:05
jamtouch work18:05
jamcd work18:05
jambzr init-repo --no-trees .18:05
jambzr init _a_branch18:05
jambzr co --lightweight _a_branch .18:05
jamIt is a bit weird to put the branches in the same dir as the working tree18:05
jamso aside from that, bzr-colo18:06
LorYes, that's one convention.18:06
LorBut it's a bit funny to have the branch directly under the root of the working directory, since there's then nothing to immediately distinguish between a branch directory and a workingtree subdirectory.18:06
Lor.bzr/branches seems like a more sensible place to put the branches18:06
LorIt also seems to work ok with bzr-pipeline.18:07
LorSo I'm all good.18:07
LorActually, pipeline+colo=loom?18:10
=== oubiwann_ is now known as oubiwann
jelmer_cbz: yes, it can track renames18:17
jelmer_cbz: but it won't infer renames from copy + delete in svn18:18
jelmer_cbz: so it will only work for revisions pushed from bzr into svn18:18
cbzokay18:18
cbzcan't it use whatever information svn uses to work out what has been renamed?18:18
LeoNerdSVN doesn't store renames.18:23
LeoNerdSVN stores a revision that deletes a file, but adds a new file by copying history from the old one.18:23
LeoNerdThat isn't quite a "rename"18:23
mgzugh, setuptools makes me feel unclean18:26
=== beuno-lunch is now known as beuno
cbzbut it stores enough meta information for tortoisesvn to work out that a rename/copy has taken place18:30
idnarthe mismatch is that bzr doesn't support copies18:35
cbzoh18:37
LorSuppose I have a network connection available only for a limited while. I want to get new revisions from upstream, but my working directory is currently a mess so I don't want to merge right away. What's the best way to do this?18:46
LorThe obvious solution is just to branch upstream into a local copy and then merge that local copy into my working branch later on.18:46
LorBut I'm wondering if there is a way that doesn't require creation of a temporary local branch.18:47
jelmer_Lor: not that I can think of18:56
LorWell, in principle it's possible to do a merge, then revert before committing. This does bring in all the revisions into the local repository. But after the revert there is just pointer to them so it's not trivial to redo the merge.18:57
Lorjust _no_ pointer to them18:57
LorBut a branch is a cheap thing.18:58
LorActually, one of the reasons why the colocated branch convention is good is that you always get a shared repository so branches are always cheap.18:59
LorIncidentally, could someone explain the point of shelves?19:05
LorIt seems kind of silly that when we have full version control available, a separate system is used to store temporary changes.19:06
TresEquisLor: back out a part of the uncommitted changes in the working directory19:06
TresEquisto make it possible to to more focused commits19:06
TresEquise.g., with simple commit messages19:06
LorIf you want to back out some changes that you want to later bring back, why not commit, then revert those changes, then do what you want, then merge rest of the stuff from the commit?19:07
TresEquisBecause I don't want them in the "public" history yet19:07
Lor"public"?19:07
LorIt's your own branch!19:07
TresEquisbut I'm going to push it somewhere public19:07
TresEquise.g., if I'm evaluating a patch which supplies both a testcase and a fix19:08
LorThat seems like a problem with your workflow.19:08
TresEquisI apply the patch, shelve the fix, and ensure that the testcase fails19:08
TresEquis(note I haven't committed anything)19:08
TresEquisthen unshelve the fix and commit both together19:08
TresEquisor if I have made "janitorial" changes to one part of a file while making substantive changes to another part19:09
LorI forgot: after the commit, uncommit back to the previous revision but revert the working tree only partly (those parts you don't want to shelve).19:09
TresEquisI want to commit the two parts separately19:09
Lorbzr-pipeline seems like the right tool for that.19:09
Lor(or loom)19:09
TresEquisno, those are too complex19:10
LorOnly if you think that a branch is a big thing.19:10
TresEquisno19:10
TresEquisI'm done trying to explain how I use it -- I don't need to defend it19:10
LorI'm not saying there's necessarily anything wrong with shelves, they just seem orthogonal and redundant.19:13
elmoaborting commit write group: OSError(24, 'open: Too many open files')19:13
elmobzr: ERROR: [Errno 24] open: Too many open files: '.'19:13
elmoseriously?19:13
LorSorry, _un_-orthogonal.19:16
GaryvdMelmo: On what os?19:17
elmoGaryvdM: Ubuntu, Lucid19:17
jamelmo: I've only seen that when using bzr-svn19:18
jamthe code that actually reads the content does have a try/finally:f.close()19:18
jamso we shouldn't be leaking from there19:18
elmojam: this is straight bzr, managing /etc19:19
elmoroot@carpobrotus:/etc# bzr st | tr -d @ | grep -v "^[a-z]" | grep -v " postgresql/8" | grep -v /hook | awk '{print $1}'| wc -l19:19
elmo126819:19
elmo^-- that's the number of files I'm trying to commit19:19
elmoI'm basically doing bzr ci -m "commit message" $(<the bzr st horror above>)19:19
elmo(without the wc, obviously)19:19
jamelmo: hmm... I still haven't seen us have a problem with that, but we can certainly try to investigate19:20
jamI assume it is perfectly reproducible for you?19:20
jamand 'bzr --version' is?19:20
elmojam: yes, reproducible19:20
elmojam: 2.1.119:20
elmo2.1.1-1 to be precise19:21
elmoI suspect I can reproduce with a dumb testcase and that the trigger is listing files on the command line19:21
elmoI'm sure I've commited trees with more changes before but I don't often specify the files on the command line19:21
elmobut I'm guessing19:21
elmoyeah19:24
elmoI'll file a bug, it's got a trivial test case19:25
jamelmo: thanks, I'm trying to reproduce now19:27
elmojam: http://paste.ubuntu.com/436872/19:27
jamelmo: so, I can reproduce something weird with "bzr st `cat big_list.txt`"19:29
elmoreported as https://bugs.launchpad.net/bzr/+bug/58346819:30
ubot5Launchpad bug 583468 in Bazaar "bzr commit will break when given too many files as arguments (affected: 1, heat: 0)" [Undecided,New]19:30
elmojamnice19:30
elmojam: nice - even19:30
elmojam: that looks like a related/similar problem19:31
jamelmo: seems like it is actually a problem with the command line being too long19:31
jamand that is getting masked somehow19:31
elmojam: I don't think so?19:32
elmo'ls *' works, for example19:32
elmoso 'bzr st *' should too19:32
jamelmo: now i'm seeing "permission denied"...19:33
jamelmo: so I'm pretty sure it isn't the commit code, but actually the "what has changed" code that is at fault, still investigating19:43
elmojam: ok, thanks for looking.  FWIW, it's not urgent though I do appreciate you looking into it19:43
jamelmo: Yeah, if you "mv  _readdir_pyx.so _readdir_pyx_old.so" it works19:43
jamthe issue is something in there is opening file descriptors and not closing them19:43
jamI know we do "open(directory)" so we can do "chdir(old_dir_id)" but we seem to properly (close(old_dir_id))19:44
jamelmo: any chance you can test on something other than lucid?19:44
elmojam: like what?19:44
elmosomething newer?19:44
jamor older19:45
jamsomething different19:45
elmosure, I can test hardy trivially19:45
jamin case it is something like OS not actually releasing handles on open(directory) or a problem with opendir()/closedir() etc19:45
jamthanks19:45
jamI've only got a Lucid VM here19:45
jamso you don't need commit, 'bzr st *' should trigger it just fine19:46
jambut it probably has to be a bunch of files and not their containing dirs19:46
jambecause the code filters (if you supply dir/ and dir/foo, we only use dir/)19:46
elmojam: hardy with 2.0.4 exhibits the same behaviour19:47
jamelmo: thx19:47
jamelmo: submitting a bug, hopefully I can track it down19:49
jambug #58348619:51
ubot5Launchpad bug 583486 in Bazaar "_readdir_pyx.so leaks file descriptors (affected: 1, heat: 0)" [High,Confirmed] https://launchpad.net/bugs/58348619:51
elmojam: ah, I guess I should dupe my bug into that then?19:54
elmojam: (done)19:54
cr3is there a way to either revert to a tag or determine the revision corresponding to a tag?20:22
mgzlaunchpad-bugs-owner@lists.canonical.com "Your message was rejected" huh?20:34
mgzthat's surely not expected behaviour from submitting a merge proposal, sending me email complaining about it.20:35
=== khmarbaise_ is now known as khmarbaise
LorWait, what? Are plugins allowed to store data into bazaar.conf?21:17
GaryvdMLor: yes21:20
LorThen it's not really a configuration file?21:21
jpdscr3: bzr tags ?21:21
cr3jpds: yep21:21
Lor(In the unix sense, meaning: managed only by the user, can be set read-only)21:21
jpdscr3: Err, that was the answer to the latter part of your question.21:21
GaryvdMLor: What plugin are you looking at ?21:22
Lorbzr-bookmark21:22
GaryvdMLor: Well, the user *configures* their bookmarks21:22
LorArguably, yes.21:23
luksbzr itself modifies bazaar.conf21:23
LorI'm not saying this is wrong, but it is confusing not to have a clear idea exactly where bzr will touch, and where the user is in control.21:24
luksI think providing UI for configuration files is nothing special21:24
Lorhm, when I do bzr co bm:foo, the bound_location gets the _expanded_ bookmark location, instead of just bm:foo21:27
LorI was hoping to use bookmarks as a layer of indirection so that if the upstream location moves someplace else, I just need to do a single reconfiguration and everything will keep on working.21:28
lifelessmoin21:29
Lor(Basically I'm wondering whether I should use bookmark locations as part of something I'm doing, or cook my own thing, even though it would be slightly similar)21:31
Lorbazaar.conf doesn't support include directives?21:35
LorI'd like to use the same configuration on multiple machines, except for some site-specific bits.21:36
=== SimonK_ is now known as SimonK
jamelmo: found the bug22:15
jamwhen you pass in a path22:15
jamwe open() the current directory so that we can chdir() back to it22:16
jambut if it is a file and the 'chdir(path)' fails, we were not closing the descriptor22:16
jamsimple one-line fix22:16
lifelessgrah22:16
lifeless+122:16
elmojam: awesome, ta22:16
jamlifeless: do you want me to clean up the code a bit, I get some warnings under pyrex. Otherwise I can just do the minimal one-line fix22:16
lifelessjam: we want to land in 2.022:16
jamlifeless: sure22:16
jamI'll start small :)22:16
lifelessjam: so - one liner, for SRU niceness. Cleanup in trunk after mergnig forward.22:17
=== blueyed_ is now known as blueyed
jamelmo, lifeless: Theres the one-line fix22:22
jamhttp://paste.ubuntu.com/436938/22:22
lifelessyeah, doit22:22
mtaylorit would be great if I could say bzr push $parent22:26
mtaylorexcept without the $parent part22:26
mtaylorI mean - if it was something good and not $parent22:26
* mtaylor is babbling22:26
mtaylorbzr push `bzr info | grep parent | awk '{print $3}'`22:27
mtayloris what I'm trying to say22:27
jammtaylor: bzr push :parent ?22:28
mtaylorjam: wow. is that a thing?22:28
jammtaylor: yes22:28
mtaylorjam: see... you anticipate my needs before I even know them :)22:28
jammtaylor: bzr help location-alias lists 6 shortcuts22:29
TresEquisborrowing guido's time machine, are we?22:29
mtaylorwoot22:29
AfCBazaar for dapper in the PPA doesn't install "bzr: Depends: python-configobj but it is not installable"22:50
AfC(yes, dapper. I need Bazaar there to get *off* of that system, heh)22:50
AfCSo should I... install Bazaar manually?22:54
jelmer_AfC: uhm22:55
AfCjelmer_: that's what I said :)22:55
jelmer_AfC: Or perhaps just run it unpacked from your home directory?22:55
AfCjelmer_: as in from tarball?22:55
AfC[if so, that's kinda what I was thinking, actually; I realize that's not what I said]22:55
jelmer_AfC: well, unpack the tarball first, but yeah :-)22:55
TresEquis$ sudo python setup.py install --root=/opt/bazaar22:56
jelmer_bzr will also work fine without installation though22:56
AfCWeill it work, or will I need this python-configobj thing manually? too22:57
jelmer_AfC: no, you won't need to install python-configobj in that case22:58
jelmer_we just remove that for the debian packages because we'd like to avoid duplication on the system22:58
AfCjelmer_: if I don't "install" it, should I still `make` (or whatever) to build the C stuff? Presumably!22:58
jelmer_AfC: it's not necessary but it will help with performance22:59
TresEquisAfC:  setup.py build_ext --in-place, I think23:00
AfCthis is horrid. Pyrex not in dapper.23:00
jelmer_AfC: you can use bzr without the extensions, it'll just be slower23:01
jelmer_is the repository you're trying to use very large?23:01
AfCjelmer_: 250 MB, 4500 files23:01
jelmer_so I guess the question is whether it will take more time to install pyrex first or to just use the slower bazaar :-)23:02
AfCyeah, I'm trying it now23:02
jamAfC: If you are extracting the tarball, you shouldn't need pyrex, the extensions shoul dbe there23:02
jamshould be23:03
AfCjam: that's what I thought, but `make` failed with horrible errors23:03
jamAfC: care to pastebin?23:03
jamand 'python setup.py build_ext -i' is correct23:03
AfCjust working through it23:03
AfChm23:03
AfCbzrlib/_annotator_pyx.c:4:20: error: Python.h: No such file or directory23:03
AfClet me guess. a build-dep23:03
jamAfC: python-dev IIRC23:04
jamand zlib1g-dev23:04
mgzyou... can just, not build the extensions23:04
jamI think thats about it23:04
jammgz: yes, he can skip it, and it will "work". But for a 250MB repo, he may be quite a bit happier with the extensions built23:04
mgzhm, yeah, depends on what he means by "get *off* of that system"23:05
mgzjust pushing a branch to somewhere else is generally network-bound23:05
AfCmgz: of course23:06
AfCmgz: but in this case I need to capture the changes that have happened out there first23:07
AfCjam: built ok23:08
AfCthank you23:08
=== Adys_ is now known as Adys
jamglad it worked23:08
AfCand if I'm being rude to this system, just ./setup.py install --root=/usr ?23:09
lifelessjam: hi23:09
lifelessdirstate stuff23:09
AfCor, failing that, what's the option to specify the remote bzr location?23:10
* AfC is RTFM, honest :)23:10
lifelessbzr help env-variables23:11
lifelessfound via bzr help topics | grep env23:11
donriBest way to uncommit a pushed commit?23:11
jamAfC: "INSTALL" says "python setup.py install --home=~"23:11
jelmer_lifeless: it's not mentioned in the man page, while most of the other variables are23:11
jamdonri: Aside from "bzr uncommit" ?23:12
donriDuno, is uncommit good enough?23:12
lifelessjelmer_: it would be nice for the man page to pull it from the help23:12
jam(and potentially push --overwrite, but I would probably use 'bzr uncommit" on the remote site as well)23:12
jelmer_lifeless: I agree23:12
jelmer_lifeless: this is the moment where one of us tells the other to write a patch.23:12
AfClifeless: ah, duh, I didn't think of an environment variable. Thanks23:12
jelmer_:-P23:12
donrijam: Don't I want to make a new commit that reverses the changes?23:12
jamdonri: depends what you need to do23:12
lifelessjelmer_: actually, I was going to say file a bug ;)23:12
jamyou *can* just uncommit, and push that around23:13
jambut people tracking you may get confused23:13
lifelessdonri: if you want to pretend it never happened, uncommit23:13
donrilifeless: Even if pushed?23:13
lifelessdonri: if other people have it already, commit something that reverses it23:13
donriI'd like that if someone pulls, they don't have the effects of that commit.23:13
jamthe alternative is: bzr merge -r X..X-1; bzr commit -m "Reverse what happened in X"23:13
donriRegardless of the log.23:13
jamwell23:13
jambzr merge . -r X..X-123:13
lifelessdonri: how long ago did you push it ?23:13
lifelessdonri: minutes/hours/days ?23:14
donriI use Bazaar to deploy so the production server pulls from Launchpad23:14
donriWhich is automated, so, yea.23:15
lifelessso, someone will have it already : you need to commit the reverse change23:15
donriThanks, merge worked wonderfully.23:16
AfCjam, mgz, jelmer_, lifeless: thanks for your help23:18
jamlifeless: I'll try to respond to your dirstate email tonight or tomorrow, I'm off for now23:18
lifelessjam: oh, I wasn't prompting for an email23:18
lifelessif you're back later, we could chat23:20
pooliehi all23:26
lifelesshi23:27

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