/srv/irclogs.ubuntu.com/2008/06/27/#bzr.txt

rick_h_is htat a differnet plugin?00:00
LarstiQrick_h_: no, that's in bzr-dbus00:00
igcmorning00:01
lifelessLarstiQ: sydney00:02
lifelessLarstiQ: http://www.slug.org.au/node/10200:02
lifelessLarstiQ: not my graphs. ask Pilky00:02
lifelessawmcclain_: uhm, jam: ^ awmcclain_ wants g+w branches ? I don't remember the voodoo00:03
lifelessPieter: hi, interesting00:03
Pilkylifeless: did you see what I said earlier to jam, turns out that the 1.3-1.5 results must've been done on my iMac not my MacBook (which really confuses me)00:03
lifelessPilky: no, I didn't00:03
lifelessmy adsl went offline overnight00:03
Pilkyah00:03
rick_h_LarstiQ: where are you getting a bzr-dbus README?00:04
rick_h_the only files I have are here:http://bazaar.launchpad.net/~jamesh/bzr-avahi/devel/files00:04
lifelessrick_h_: thats bzr-avahi :)00:05
PilkyI thought I'd done all the benchmarks on my MacBook as I remember taking it back to 1.3 to test the speed, but the results I did from 1.3 today don't match up00:05
lifelessPieter: can you ls . and .. and also do bzr info?00:05
rick_h_right, what I'm saying. The error seems dbus related which is why I asked if that was a seperate plugin00:05
Pieterlifeless: http://pastie.org/22300700:06
LarstiQlifeless: cool00:06
rick_h_ok, checked out the bzr dbus plugin, but now I have two plugins that don't load00:07
lifelessrick_h_: :X00:07
lifelessrick_h_: can you pastebin the error from ~/.bzr.log please00:07
LarstiQrick_h_: ah sorry, I read 'python-dbus' as 'bzr-dbus', sorry :/00:08
rick_h_lifeless: http://paste2.org/p/4275200:08
rick_h_I'm tring to use this to get bzr avahi http://blogs.gnome.org/jamesh/2008/02/19/bzr-avahi/00:09
rick_h_it looks like it's saying no module named dbus, but "python-dbus is already the newest version."00:10
lifelessPieter: ah00:11
lifelessPieter: what is pwd?00:11
LarstiQrick_h_: ok, now that you have bzr-dbus, did you follow the instructions in the bzr-dbus README?00:11
Pieterlifeless: /Users/pieter/m/bzr/working00:11
lifelessLarstiQ: this:00:11
lifelessFile "/home/rharding/.bazaar/plugins/bzr_dbus/activity.py", line 31, in <module>00:12
lifelessLarstiQ: should give you an answer00:12
rick_h_ah, ok...working on it. This seems like a pita00:12
lifelessrick_h_: you should name the bzr_dbus dirctory 'dbus' in ~/.bazaar/plugins00:15
LarstiQlifeless: doh00:15
* LarstiQ hangs his head in shame.00:15
lifelessLarstiQ: ah you see it now?00:15
LarstiQlifeless: the non python symbol naming of the plugin? yeah00:16
* LarstiQ was too focused on the org.thingy00:17
rick_h_crap, that broke everything now00:19
rick_h_ok, now I'm getting AttributeError: 'BranchHooks' object has no attribute 'install_named_hook'00:20
LarstiQI think, some code may have bitrotted a bit.00:21
beunomwhudson, got a minute?   I'm can't decide on how to approach something in the new theme00:23
mwhudsonbeuno: not really, but let's hear it00:23
lifelessPieter: some lag here sorry; on the phone00:24
lifelessrick_h_: thats a version issue; what bzr version do you have ?00:24
rick_h_1.3.1-1ubuntu0.100:25
beunomwhudson, heh, well, here goes.  For the diffs, now, as opposed to the current theme, it fits the screen and wraps lines. So we don't have a horizontal scrollbar pushing everything away. This is a problem when long lines of codes don't have spaces to wrap over, because the texts gets hidden under the next div.00:25
beunothat leaves me two roads00:26
beunoa) add an html tag that will allow me to wrap on some characters like /00:26
mwhudsonoh, because the diffs have spaces replaced with &nbsp; right?00:26
beunob) don't do this anymore, and push everythign off-screen00:26
mwhudsonis there a concept of "space that doesn't collapse but still wraps" ?00:26
beunomwhudson, no, no &nbsp; anymore. They make files too big. I'm using <pre>00:27
mwhudsoni think in the spirit of "not trying to fix everything at once", i favour (b)00:27
mwhudsonbeuno: oh00:27
beunothe problem is with lines like: &lt;p class="expand"&gt;&lt;a href="#"&gt;&lt;img tal:attributes="src python:branch.static_url('/static/images/treeCollapsed.png')"00:28
beunono spaces00:28
mwhudsonmm00:28
beunoI can force wraping by adding a tag after each /00:28
beunowhich would solve it00:28
mwhudson<wbr/> or whatever?00:28
beunoless work, should look better then off-screen pusing00:28
beunoexactly00:28
mwhudsonwell, but that's a total hack though00:28
mwhudsonwhat if the long text was long_package_name.long_module_name.long_function_name?00:29
beunoright. CSS3 has a fix for this, but we can't use that for few years  :)00:29
lifelessmwhudson: so, whats needed to merge bzr-search-integration to lh trunk?00:29
mwhudsonlifeless: me not having two critical issues to fix today00:29
beunomwhudson, well, we can pick a few characters,  / \ _ .00:29
lifelessmwhudson: what issues?00:29
beunolifeless, and, I need to make it less invasive if search isn't installed  (ie, not show the div if no results)00:30
mwhudsonlifeless: codebrowse using too many file descriptors and the ssh server performance problem00:30
lifelessbeuno: I don't think the div is such a big issue :P but you're the dev00:30
lifelessmwhudson: ooh, fd leakage?00:30
mwhudsonlifeless: well, not strictly leakage00:31
beunomwhudson, b) takes longer because I have to re-structure everything00:31
beunoa) makes the file a bit bigger, which is a but sucky00:31
mwhudsonlifeless: loggerhead currently keeps a branch object around for every branch it has ever seen00:31
beunobut I did remove all those &nbsp;, so we still win00:31
mwhudsonlifeless: when you're accessing branches over http, this keeps a connection open00:32
mwhudsonlifeless: so, once enough branches have been browsed, you bump into limits00:32
mwhudsonbeuno: it sounds like you're arguing for (a)00:33
beunomwhudson, I can also add <wbr/> after X characters, which would probably take up less space. On the other hand, it may wrap in less-then-optimal places00:33
beunomwhudson, yes, I like a) right now00:33
mwhudsonbeuno: the general assumption is that it's source code00:33
mwhudsonbeuno: so the whole idea of wrapping it is a bit goofy anyway00:34
mwhudsonbeuno: so i really wouldn't worry about trying to be too perfect here00:34
beunoright, I agree from that point of view. On the other hand, a side-by-side view that goes off-screen isn't useful at all00:35
beunook, so after X characters it is  :)00:35
Verteroklifeless: is there any chance that you can install eclipse-3.3?00:35
awilkinsVerterok: Darn, SaveableCompareEditorInput is 3.3 specific00:35
lifelessVerterok: are there packages?00:36
lifelessVerterok: hardy is the most recent release...00:36
Verteroklifeless: I don't think so :(00:36
beunomwhudson, that's the last big item on my list, so it should be reviewable on monday. Along with search branch, once lifeless makes it work with bzr.dev00:36
awilkinsThere's no hardy package newer than 3.2 (not in official package repos anyway)00:36
Verterokawilkins: yes, do you depends on 3.2?00:37
awilkinsVerterok: Is there an older choice for SaveableCompareEditorInput?00:37
Verterokawilkins: write it by hand :(00:37
awilkinsVerterok: Alas, yes, the release of the UML modeller we use is 3.2 specific.00:37
* mwhudson has to go away for a bit00:37
beunomwhudson, thanks for the input00:37
awilkinsVerterok: I may just clip it out, I've been using Beyond Compare for merge editing00:38
Verterokawilkins: I can make a ugly but temporal solution of copy/paste the implementation00:38
lifelessbeuno: search with bzr.dev is orthogonal to merging to loggerhead00:38
lifelessbeuno: because most folk will have 1.5 or 1.6b2 of bzr00:38
beunolifeless, not if I'm trying to find ways to buy time00:38
lifelessbeuno: pfft00:38
beuno:)00:39
beunoand it breaks everything I have indexed00:39
* awilkins opens Eurpoa00:39
awilkins*Europa00:39
Verterokawilkins: Ok, if you need the compare feature, I can try to make it a separate plugin00:39
beunobut I suppose I can revert...00:39
Verterokawilkins: s/need/not need/00:40
=== edcrypt_ is now known as edcrypt
Verteroklifeless: "installing" eclipse-3.3 it's just unzip it in some place00:41
awilkinsVerterok: Our comparing is nasty because all the documentation is smunged onto a single line by the tool ; I have an external converter than unpacks it to an HtmlTidy-ed CDATA span and then repacks it after editing00:41
awilkinsVerterok: Plus the modeller drops dead on files with conflict markers because they aren't valid XML ; so I'm making my users edit conflicts outside the IDE at the moment00:42
lifelessVerterok: really? ok I'll look for it then00:43
lifelessVerterok: why doesn't http://bazaar-vcs.org/BzrEclipse say 3.3 and where to get it ?00:44
Verteroklifeless: the current published plugin is 3.2 compatibly00:44
Verterokcompatible00:44
Verterokbut the trunk isn't any more00:44
Verterokas awilkins said, it's caused by the compare editor00:45
Verteroklifeless: so if you download the "official" plugin, it still works with 3.200:46
Verteroklifeless: http://mirror.calvin.edu/eclipse/downloads/drops/R-3.3.1.1-200710231652/index.php00:46
Verterokit's a mirror of the 3.3 download page00:47
Verterokyesterday, the eclipse folks released 3.400:47
Verterokso, 3.3 download page is gone :P00:47
awilkinsVerterok: Ouch, if you start dropping it it cascades at least as far as the commit dialog... which I obviously can't do without.00:50
Verterokawilkins: the commit dialog too? mmm...that's odd. what is the dependency?00:51
awilkinsIt sets up a diff action00:51
awilkinsLine 400 : DiffOperation.openDialog00:52
awilkinsDiffOperation uses SaveableBazaarCompareEditorInput00:53
Verterokawilkins: I think we can put that in an interface, and create a extension point for it, toughts?.00:54
awilkinsThat seems fair ; what does it use for 3.2?00:55
awilkinsI don't think it's a saveable one, but I remember a diff view00:55
Verterokawilkins: SyncInfoCompareEditor00:55
Verterokawilkins: it's hack and a bit ugly compare editor, but it works :P00:57
lifelessargh00:58
lifelesshttp://mirror.calvin.edu/eclipse/downloads/drops/R-3.3.1.1-200710231652/download.php?dropFile=eclipse-SDK-3.3.1.1-linux-gtk-x86_64.tar.gz is not the download00:58
lifelessits actually a page about the download. garh garh00:58
lifelessVerterok: how do I find out if I have a 64 bit vm ?00:59
Verteroklifeless: give me a min. I'll come back with the direct link :)00:59
lifelessVerterok: I've found it00:59
lifelessVerterok: but I need to know if I have a 32bit for 64 bit vm00:59
Verterokok00:59
Verteroklifeless: output of 'java -version' ?01:00
lifelessrick_h_: sorry for going silent01:02
lifelessrick_h_: bzr 1.4 has that function01:02
lifelessVerterok: thanks01:02
rick_h_lifeless: ah, ok. So is there some method I should use to pull plugins for the hardy versoin?01:02
rick_h_or am I fubar'd unless I update bzr to 1.4?01:03
lifelessrick_h_: 'apt-get install' is the usual one :)01:03
lifelessrick_h_: some plugins have version specific branches; I don't know if bzr-avahi does01:03
lifelessjamesh: ^01:03
rick_h_ok, is there a ppa for bzr I can pull 1.4 with?01:03
lifelessmarkh: did you end up chatting to zou_ about installer builds?01:03
lifelessrick_h_: http://bazaar-vcs.org/Download01:03
markhhi lifeless - not sure who zou_ is :)  I've chatted with Alexander who made the last oens01:04
markhI've got a nice new binary build here too, that include the little of tortoise that works01:04
lifelessmarkh: zou_ is a gnash developer, they just switched to bzr01:04
lifelessmarkh: release it!01:04
markhyeah, I'm literally finishing it now :)01:05
markhso - dumb user question: I've a branch of dvr.dev with a few changes that I'd like to public (ie, not quite ready to propose for merging).  What is the best way to do that?  What would happen if I tried to publish the branch to Launchpad - would it try and upload the *entire* branch?01:06
markhbzr.dev obviously :)01:06
lifelessmarkh: well, stacking hasn't landed yet, so yes, yes it will01:06
markhso just put a bundle up on some server for people to grab?01:06
lifelessnormally we'd just upload the branch01:07
markhoh - fair enough then - I'll do that!01:07
awilkinsVerterok: Should the diff use the merge viewer attached to the org.eclipse.compare.contentMergeViewers extension point?01:16
Verteroklifeless: another thing, you need the xmlrpc branch of xmloutput plugin01:16
Verterokawilkins: I don't fully understand the question, as I remember bzr-eclipse don't  use rg.eclipse.compare.contentMergeViewers extension point01:18
* Verterok checks01:18
lifelessVerterok: eclipse is nearly downloaded01:18
lifelessVerterok: what next01:18
Verteroklifeless: install xmloutput plugin, but not the trunk, the xmlrpc branch01:19
awilkinsIt doesn't use it, but my question is, should it be just getting the merge viewer from the platform which knows which viewer goes with which kind of file, rather than using the same one all the time.01:19
Verteroklifeless: https://code.launchpad.net/~guillo.gonzo/bzr-xmloutput/xmlrpc01:19
awilkinsSince there is an extension point for defining which viewer is used (and it's in 3.2 --- 3.4 at least), this may resolve the version-compatibility issue and also make it more flexible (since it should use the best available viewer for a given filetype)01:20
Verterokawilkins: ahh, now I get it, thanks :). yes the comapre editor don't do the content comaprsion/merge, they delegate to the platform01:21
lifelessVerterok: should it be called xmloutput or xmlrpc in ~/.bazar/plugins?01:21
Verteroklifeless: gooood question :D xmloutput01:21
Verteroklifeless: once eclipse is up and running, follow the steps in http://bazaar-vcs.org/BzrEclipse/Installation until step 601:23
Verteroklifeless: the url of the update-site should be replaced with: http://guille.beuno.com.ar/bzr-eclipse/bzr-search-site/01:24
Verterokawilkins: do you have a link to that extension point?01:25
awilkinshttp://help.eclipse.org/stable/topic/org.eclipse.platform.doc.isv/reference/extension-points/org_eclipse_compare_contentMergeViewers.html01:25
Verterokthanks01:25
lifelesswow, the plugin has lots of history/content :P01:26
Verteroklifeless: xmloutput or bzr-eclipse?01:28
lifelessxmloutput01:28
lifelesstook ages to branch01:28
lifeless380K01:29
lifelesssomething freaky going on here01:29
Verterokthat's a lot01:30
lifelessVerterok: oh01:30
lifelessVerterok: upgrade your branch dammit01:30
* Verterok check his xmloutput branch01:30
lifelessbzr info https://code.launchpad.net/~guillo.gonzo/bzr-xmloutput/xmlrpc01:32
lifelessStandalone branch (format: dirstate or knit)01:32
lifelessyou want 'bzr upgrade sftp://bazaar.launchpad.net/~guillo.gonzo/bzr-xmloutput/xmlrpc'01:33
Verterokindeed, doing it ATM. thanks!01:33
lifelessVerterok: so, the tarball I downloaded01:35
lifelesshas an eclipse dir01:35
lifelessoh, it fails, its good now01:35
Verteroklifeless: it should have a eclipse executable inside01:36
lifelesseuropa01:36
StyXmanhi all01:38
Verteroklifeless: hardy comes with the java vm from sun or the gcj?01:38
VerterokStyXman: hi01:38
StyXmanhow can I do a bzr diff while editing the message for bzr ci? it tells me it can't lock...01:38
lifelessVerterok: typo: 'Remainin portions'01:39
beunoStyXman, bzr ci --show-diff?01:39
lifelessStyXman: currently you can't, but as beuno says01:39
StyXmanbeuno: wonderful01:39
* beuno curses simpletal01:39
Verteroklifeless: in the install guide?01:39
lifelessin the licence01:40
Verterokthanks, fixed01:41
lifelessunterminated entity ref ...StringReader@6c618821)01:41
lifeless^ what does that mean01:41
Verterokups, xmloutput not working?01:42
lifelesswhen I click ok after setting the bzr executale to use01:42
Verterokwhen you choose ok, it tries to execute 'bzr xmlplugins'01:43
VerterokI missed to check if the output is actually xml01:43
lifeless just ran that in concole01:44
lifelessit did not error01:44
lifelesshowever01:44
lifelessI have plugins that include " in their strings01:44
VerterokI'm using the same version here, let me check01:45
lifelessand it doesn't seem to be using CDATA01:45
lifelessbzr xmlplugins | xmllint -01:45
lifeless-:127: parser error : xmlParseEntityRef: no name01:45
lifeless   lan-notify &``. ``lan-notify`` is very useful in local LAN collaboration to01:45
lifeless               ^01:45
lifelessback in a little, moar caffeine needed01:46
Verterokmm...so I should use CDATA for the description01:46
lifelessPieter: ping, when you can, I'm interested in 'pwd' from the checkout please01:47
lifelessVerterok: well01:47
StyXmanmoar coffee indeed :)01:47
Pieterlifeless: I already pasted that :)01:47
Pieterlifeless: /Users/pieter/m/bzr/working01:47
lifelessVerterok: its not escaping everything properly; either escape or CDATA01:47
lifelessPieter: sorry, ETHREADLIMIT :)01:47
lifelessPieter: oh! I know01:47
lifelessPieter: 'merge URL' and 'switch BRANCH' dont, unfortunately, share a lookup function01:48
lifelessPieter: I did the switch logic too see how people would like it; they seem to :)01:48
Pieterah.. this is a bit unexpected behaviour though ;)01:48
StyXmanktxbye01:48
lifelessPieter: so 'merge 5.1' found '.' as the branch to merge from01:48
lifelessPieter: Totally, I'm filing a bug01:48
Verteroklifeless: y'r absolutely right...01:48
Verterokapplying bzrlib.xml_serializer._escape_cdata01:49
lifelessVerterok: I know I am :)01:50
Verterok:)01:50
Verteroklifeless: pushed to lp (and the branch is upgraded)01:52
lifelessI'll repull for kicks01:53
lifelessigc: something you might find fun to do; write a 'bitch about knits' patch, like the current 'bitch about weaves' one.01:54
lifelessVerterok: 25 seconds01:54
lifelessVerterok: vs minutes01:54
Verteroklifeless: nice! :D01:54
lifelessVerterok: now I get01:54
lifelessXMLRPC based client is not available01:54
awilkinsmoar caffeine : Mother Of All Roasts01:54
lifelessVerterok: its lint clean now though which is better :)01:55
lifelessoh caffeine. be right back01:55
lifelessPieter: and please, get a callgrind file on _anything_ that is slow (after checking here that its not just a case of asking bzr to do lots)01:55
igclifeless: as in grumble if people aren't running with packs?01:55
Verteroklifeless: let me think but in the meantime just for the sake of try, restart eclipse :P01:55
lifelessPieter: your slow switch or merge _should_ be faster, its definitely worth gathering data on01:56
lifelessigc: yes, packs or something better01:56
lifelessigc: which is why just grumble on knits:)01:56
igc:-)01:56
* fullermd looks at all his knit branches...01:57
lifelessVerterok: I restarted01:57
lifelessXMLRPC based client is not available01:57
lifelessback soon01:57
lifelessback02:06
* Verterok just found a bug...in the xmlrpc java client02:06
Verteroklifeless: a new build in tic02:06
lifeless:P02:06
lifelesscool02:06
lifelessdon't you love new users02:06
* Verterok have a headless build...so sit and relax02:07
lifelessPieter: bug 24338602:07
ubottuLaunchpad bug 243386 in bzr "url lookups should be able to use the same heuristic switch does" [Undecided,New] https://launchpad.net/bugs/24338602:07
Verteroklifeless: absolutely :D02:07
thumperhey guys02:14
thumperhow many windows users do we have here?02:14
thumperjust raise hands02:14
* markh ducks02:14
thumperfeel free to point at windows users02:16
lifelessjam02:17
lifelessmarkh02:17
lifelesszou_ who is in #gnash02:17
* Verterok thinks that bzr-eclipse need more users....and bug reports02:20
Verteroklifeless: new build uploaded to the update site02:21
Verteroklifeless: Help --> software updates --> find and install --> search for new features to install02:21
Verteroksimilar to the install, and avoid the check for updates of all plugins02:22
lifelessstill says02:23
lifeless"Remainin portions "02:23
Verteroklifeless: yes, I fixed that in trunk :P02:23
lifelessVerterok: ok02:25
lifelessnow its been 5 years since I used eclipse in anger :)02:25
lifelessI want to point it at bzr.dev, which I have indexed02:25
lifelessand try it out02:25
Verteroklifeless: works?02:26
lifelessdoesn't complain in the setup box now02:26
Verterokgreat02:26
lifelesssearch window has 'file, java, plug-in' tabs02:26
Verteroklower left --> customize02:27
lifelesshow do I tell it which breanch to search02:27
Verterokyou must have it in eclipse, as a project02:27
=== cprov is now known as cprov-out
Verterokif you don't want to branch,  it can be imported02:28
Verterokcreate a new empty project02:28
lifelessbzr is python :)02:28
lifelessdoes that matter?02:28
Verteroknope :)02:29
Verterokeclipse treat .py as text files (in case PyDev isn't installed)02:29
lifelessso branch as new project02:29
lifelessuse existing02:29
lifelessempty list02:29
Verterokthere is no previous branch location used from eclipse (no integration with locations.conf yet )02:30
Verteroklifeless: you can branch or you can take a shorcut :)02:31
lifelessVerterok: k, well - take the things I try as user feedback to consier :P02:32
lifeless(it doesn't say 'used from eclipse' :)02:32
lifelessVerterok: what should I do?, I can't seem to edit the list ..02:32
* Verterok fires up a text editor...and start taking notes02:32
Verteroklifeless: there should be two options02:33
beunomwhudson, so...  it turns simpletal converts < and > to html, no matter how much I yell at it02:33
mwhudsonbeuno: even CDATA ?02:33
mwhudsonbeuno: that sucks :/02:33
lifelessbeuno: monkeypatch?02:33
Verterokcheck "initialize a new branch location"02:33
Verteroklifeless: wait, you want to use the already indexed bzr.dev?02:34
beunolifeless, I'm trying to avoid that. Though mwhudson would know a magic way around it, that neither me or google did02:34
beunos/Though/Thought02:35
zou_bzr commit file1.h file2.cpp02:36
Verteroklifeless: to avoid re-indexing the branch, you can go to: File --> new --> Project --> General --> Project and specify a location02:37
zou_got message: "bzr: ERROR: Selected-file commit of merges is not supported yet: file1.h file2.cpp"02:37
zou_what should I do then?02:37
=== mw is now known as mw|out
lifelessVerterok: sweet thanks02:41
lifelesszou_: you've done a merge from somewhere02:41
lifelesszou_: you should just 'commit'02:41
=== edcrypt__ is now known as edcrypt
zou_lifeless: you mean just "bzr commit"?02:42
lifelessyes02:42
zou_hmm, but I want to control what I am going to commit.02:42
lifelessyou've done a merge though02:43
lifelessso you already have some other work going in02:43
lifelessbzr will link to say that that work was merged02:43
zou_yes. here is what I did:02:43
lifelessbut we don't [yet] allow you to merge just some files from that merge, because the graph of merges is done at the revision level, not per-file.02:44
zou_(1)I made some local changes on Gnash yestoday (2)I did a "bzr update" today.02:44
zou_Now I want to commit my local changes with "bzr commit file1.h file2.cpp"02:44
lifelesshad you committed those changes locally?02:45
zou_yes. I'v done "bzr commit --local"02:45
lifelessso, can I ask why you don't want to commit some of your changes?02:45
lifelessoh, markh meet zou_02:46
zou_some changes are important. others are just trivial work, eg. indent the sources and add some debugging lines.02:46
lifelesszou_: ok. why does that matter though ?02:47
zou_I just want to commit the "important changes".02:47
lifelesszou_: is it for review? or because some aren't ready? or ... ?02:47
markhzou_: hi!  Please don't get your expectations up too far for a first tortoise release ;)02:47
lifelesszou_: because all your work is /already/ committed locally02:48
markhbut its looking quite nice and I hope to have a binary up in a day or so...02:48
zou_I don't want to make a new revision for a file without any meaningful change.02:48
lifelesszou_: ok. so I would merge all the things in because you have committed them02:49
lifelesszou_: but I can help you untangle things if its real important02:49
zou_markh:  file marks + update + diff + commit should be enough at the moment.02:50
lifelesszou_: and I think you probably want to start using a separate branch to do your own work, because 'commit --local' on trunk is for *things you want on trunk*02:50
lifelesszou_: but what you are saying to me is 'I have committed things I didn't want on trunk yet' - and thats an ideal situation to be using a branch02:50
zou_markh: and make the installation easier for me, hopefull a single TortoiseBzr.exe would work:)02:51
zou_lifeless: I just thought "commit --local" was safe, eg. doesn't interrupt the work of the others.02:52
zou_So I "commit --local" a lot without carefull consideration.02:53
lifelesszou_: its for offline work on a shared branch, the intent is that what you did becomes part of trunk at the earliest possible opportunity - which is now02:53
markhzou_: first cut will have icon overlays but no functinging context menus - so checkins etc are still from the cmdline02:53
lifelesszou_: for doing stuff without care, use a branch. Branches are easy to make and work with02:53
zou_But before a real commit(commit to remote branch), I have to think for the others.02:53
markhit shouldn't take too long to wire that up,m be we decided an earlier release without out it was better02:53
lifelesszou_: exactly. you want a branch for this, not commit --local02:54
markhOne task will be to wrap up the pygtk "worker" applications in a py2exe environment02:54
zou_lifeless: OK, step1: bzr branch bzr+ssh://myname@bzr.savannah.gnu.org/gnash02:55
zou_step2: local changes.02:55
lifelesszou_: or even bzr branch . ../localwork02:56
zou_then what should do after that? what are the commands?02:56
lifelesszou_: in the new branch, commit to do a commit02:56
lifelessmerge $TRUNKURL + commit, to get updates from trunk02:57
lifelesscd $TRUNK; bzr update; bzr merge $LOCALBRANCH; bzr commit02:57
lifelessto take something you did locally and put it in the trunk02:57
lifelessyou probably want to have your localbranch be the one that your build trees point at02:58
lifelesszou_: we can get more sophisticated, but $learning curve02:58
zou_what is the URL of my local branch?02:58
lifelesszou_: well, if you ran 'bzr branch bzr+ssh://myname@bzr.savannah.gnu.org/gnash' then it would have made a new branch at ./gnash02:59
lifelessif you ran 'bzr branch . ../localwork' it would have made it at ../localwork02:59
zou_This is what I did:  bzr co bzr+ssh://myname@bzr.savannah.gnu.org/gnash/trunk.  so it's not a branch?03:01
lifelesszou_: that does a checkout03:01
lifelesszou_: checkouts operate like cvs - when you commit it goes to the thing you checked out03:01
lifelesszou_: for clarity - are you talking about the *existing place you were doing commit --local*, or a new one made during this conversation ?03:02
zou_yes, but for a cvs rep., I can always use "cvs commit file1.h file2.h" and leave "modifiedy file3" alone.03:02
lifelesszou_: yes, and you can in bzr too; but you *already committed* this stuff with --local03:03
lifelesszou_: so lets make you a new branch and get you hacking again03:03
lifelesszou_: cd to the checkout03:04
zou_lifeless: I am taking about the "existing place"03:04
lifelesscd to the existing place03:04
zou_done03:04
zou_and then?03:04
lifelessrun this command:03:04
lifelessbzr branch . ../local-branch03:04
lifelessthat should be very fast; if its not we can make it faster in future but don't worry about that right now03:05
zou_doing now, wait it to be fininshed.03:05
zou_finished.03:06
lifeless(when I say we can make it faster, I mean that its local configuration, not code-writing, to make it faster)03:06
lifelessok03:06
lifelessthis new place - local-branch - is where you should do changes and write code03:06
zou_cd local-branch03:07
zou_so I can do "bzr commit file1 file2" and leave modifidy file3 alone now?03:07
lifelessyes, we need to recover the work you don't want to commit first03:07
lifelessthis needs  alittle python, because I just found a bug in the command that would normally make it real easy03:08
lifelessyou're on windows aren't you ?03:08
zou_yes. Cygwin + windows.03:08
lifelesswell, lets see if we can use python, otherwise we'll peek at a file quickly on disk03:09
lifelesspython03:09
lifeless>>> import bzrlib.workingtree03:09
lifelessif that errors, we'll need to peek on disk03:09
lifelesslet me know if it worked or errored03:09
lifeless(no output is worked)03:09
zou_lifeless: I'v typed import bzrlib.workingtree03:10
lifelessok03:10
lifelessnow03:10
lifelesstree = bzrlib.workingtree.WorkingTree.open('../trunk')03:11
zou_still after ">>>" ?03:11
lifeless(replace ../trunk with the path to your checkout - I am guessing at the relative path)03:11
lifelesszou_: yes, the >>> is the python prompt03:11
zou_done03:12
lifelesstree.lock_read()03:12
lifelessprint tree.get_parent_ids()[1]03:13
lifelesstree.unlock()03:13
zou_done03:13
lifelessthe print statement will have printed out a GUID03:13
lifelessexit python now03:13
lifelessyou should be in local-branch still03:13
lifelessrun bzr pull -r revid:$GUID ../trunk03:13
lifelessthis will restore your local work so we can pick and choose bits of it for trunk03:14
zou_it prints "zoulunkai@gmail.com-2008xxxxxxxxxxxxx"03:14
zou_should I write down the GUID before exit python?03:15
lifelesszou_: yah, put that in the bzr pull commit - so 'bzr pull -r revid:zoulunkai@gmail.com-2008xxxxxxxxxxxxx ../trunk' (or whatever it printed)03:15
lifelesszou_: if your window will go away yes - or just copy and paste03:15
zou_bzr pull -r  revid:zoulunkai@gmail.com-2008xxxxx   ../trunk03:18
zou_got message:03:18
zou_bzr: ERROR: These branches have diverged. Use the merge command to reconcile them.03:18
lifelesszou_: are directory are you in ?03:19
zou_I am under the local-branch dir.03:19
lifelesscool03:19
lifelessadd --overwrite to the command line03:19
zou_ok, finished. got message: " ....  All changes applied successfully, Now on revision 9425"03:20
lifelesscool03:20
lifelessnow, local-branch has what you were working on before you updated03:20
lifelessone last thing to do -03:21
lifelesscd to trunk03:21
lifelessand run bzr revert03:21
zou_I am still under "local-branch" dir. you mean "cd ../trunk"?03:21
lifelessyes03:22
zou_done "bzr revert"03:22
lifelessright03:23
lifelessnow, to get some changes from local-branch into trunk03:23
lifelessyou can get them all by doing a merge03:23
lifelessbut you only want some03:23
lifelessso I'm going to teach you how to do a 'cherrypick'03:23
lifeless(this is all in the manual btw)03:23
zou_ <lifeless> now, to get some changes from local-branch into trunk03:24
zou_how to do that?03:24
lifelesscd to the trunk03:25
lifelessand do 'bzr missing ../local-branch'03:25
lifelessthis command tells you about commits that can be merged03:25
lifeless(it tells you in both directions)03:26
zou_got message:  "you have 13 extra revision(s): ....   you are missing 1 revision(s)"03:28
zou_I want to commit some of my local changes. Can I use the local-branch dir to do that?03:29
zou_commit to the remote branch.03:29
lifelessyes03:30
lifelessso, from the look of it you've only done one local commit, but you commited several things03:30
lifelessso the we have to merge the files you want across:03:31
lifeless'bzr merge ../local-branch/file1.h'03:31
lifeless'bzr merge ../local-branch/file2.cpp --force'03:31
lifeless'bzr merge ../local-branch/file3.cpp --force'03:31
lifelessetc03:31
lifelesswhen you are happy, bzr commit03:31
zou_bzr update03:33
zou_then haven't the changes from remote branch already be merged to my local branch?03:33
zou_the merge command is confusing.03:34
lifelesszou_: could you rephrase the question, I'm not sure what you mean03:34
zou_by using cvs, "cvs update" merges changes from remote rep. to my local rep. automatically.03:35
zou_I am not sure when I need a "bzr merge" command.03:35
zou_after "bzr update remote_branch"?03:36
lifelesszou_: you need merge to move changes between your local 'trunk' directory and your 'local-branch' directory03:37
lifelesszou_: the way merge works, is it moves some changes, and then you use 'commit' to record them permanently03:38
zou_ok.03:39
lifelesszou_: so you need merge in 2 places: after you do 'bzr update' in the trunk directory, you should cd to the local-branch directory and run 'bzr merge ../trunk ; bzr commit -m "merge trunk"' to move changes to the local branch03:39
lifelesszou_: and when you have finished some work in local branch and want to put it in the trunk you should do:03:39
lifelesscd trunk; bzr update ; bzr merge ../local-branch; bzr commit -m 'details of what you are committing to trunk'03:40
zou_very clean, thanks:)03:40
zou_clear03:40
lifelesshappy to help03:41
lifelessyou guys are taking a big step from CVS to distributed in one step03:41
lifelessfeatures like offline commits involve most of the complexity of full distribution, which is why you ran into the wall today03:41
zou_another question:03:42
zou_ 'bzr merge ../local-branch/file1.h'  'bzr merge ../local-branch/file2.cpp --force'03:42
zou_why I need the '--force' option?03:43
lifelessso the first merge merges one file03:43
lifelessand leaves you with pending changes03:43
lifelessmerge will stop and refuse to operate by default when you have pending changes, because its easy to get conflicts-on-conflicts and other such confusion03:43
lifelessso the --force says 'allow me to merge the other file please'03:43
zou_I have a 'trunk' dir and a 'local-branch' dir. what is the pending change?03:44
lifelesswell you are in trunk03:44
lifelessand you merge one file - file1.h - from local-branch03:45
lifelessthat becomes a pending change in trunk03:45
zou_yes03:45
lifelessbecause you haven't yet run 'commit' to record it permanently03:45
lifelessfile1.h is the pending change :)03:45
lifelesswhy don't you try it and see what happenes03:46
zou_so, I select the files I want to commit at the "merge" stage instead of "commit" stage, right?03:46
lifelesszou_: yes, when you are picking individual changes03:46
lifelesszou_: _normally_ most people merge the entire directory - e.g. 'bzr merge ../local-branch', because thats what you usually want03:47
zou_No, for Gnash, I do selective "cvs commit" everyday. (cvs commit all_files is dangerous)03:48
zou_I touched lots of files during debugging, but many of them are not worthy for committing at all.03:49
zou_It's difficult to track back if there are too much revision numbers.03:50
beunomwhudson, ignore my previous comment, you can print html, although it complicates everything for me. It's going to be a few python lines just to print out <wbr/>...03:50
zou_lifeless: thanks a lot for you time!03:51
lifelesszou_: ah, there are plenty of tools we have to help you here though03:51
lifelesszou_: firstly, I didn't say that people _commit_ everything all the time - but that they _merge_ everything03:51
lifelesszou_: another thing that you may like is the 'shelve' plugin03:52
lifelessthis lets you put some changes aside that are not ready to commit (or imappropriate, like debugging stuff)03:52
zou_I think windows users need a TortoiseBzr which behaves like the TortoiseCVS, GUI helps me think better:)03:55
lifelesszou_: to some degree we will have that soon03:56
lifelesszou_: but there are _substantial_ differences in a full-tree system, which is what git/bzr/hg/monotone all are03:57
lifelessok, I'm heading lunch and poolies I think04:00
lifelesspoolie: see you 3ish ok ?04:00
zou_I think I could expect that "selective merge", "selective update", "selective diff" would be very intuitive within the windows file explorer04:01
lifelesszou_: well, selective update doesn't exist as a concept in the system; selective merge does but with some caveats; selective diff does04:02
lifelessgotta run04:02
zou_select the file with your mouse and right click it to choose a context menu to do your action:)04:02
* igc lunch04:04
zou_are all files share the same revision number of a bzr branch?04:11
poolielifeless: 3ish is fine04:12
zou_eg. for a cvs-head branch, we can have revsion 1000 for file1, 800 for file2, 2000 for file3.04:13
zou_do we have a similar concept for a bzr-head branch? Or all files for a bzr-head branch share the same revision number?04:14
mwhudsonzou_: a revision in bazaar is a snapshot of the entire tree04:16
zou_got it. so we don't have "revision for a single file"04:17
mwhudsonso, more the second of your two options, but the answer is more "neither"04:17
mwhudsonzou_: right04:17
zou_thanks. Then I understand why I cann't do "selective commit" better.04:18
PengEek, LH's traceback didn't go in the log.04:30
mwhudsonPeng: hmm04:32
mwhudsonsounds like a bug04:32
PengHuh.04:33
PengWant me to file a bug against LH?04:38
mwhudsonPeng: well, probably04:41
mwhudsonPeng: what was the traceback?04:41
Pengmwhudson: That's another matter. Googlebot has been having lots of fun going through my LH instance today, and certain annotation pages traceback with a NoSuchId in tree None.04:42
mwhudsonman wtf, _that_ sort of traceback should be in the log i'd have thought04:42
mwhudsonPeng: interesting04:43
* Peng shrugs.04:43
PengI'll file a bug.04:43
mwhudsonPeng: are they reproducible, in that when you visit the urls do they traceback?04:44
Pengmwhudson: Yes.04:44
mwhudsonok, good (probably)04:44
mwhudsonPeng: is this public code?04:44
Pengmwhudson: URL where it happens: http://snurl.com/2p8ye Traceback: http://paste.pocoo.org/show/77818/04:45
beunoah, that reminds me, I have Peng's patch for broken atom links.  Off to trunk...04:45
PengThere are at least 2 pages that cause it to happen.04:45
Pengbeuno: :)04:45
mwhudsoni wish googlebot sent referer headers :/04:46
PengHeh.04:46
beunomwhudson, I've been meaning to run a custom spider script I have on LH with a bigg-ish branch, just haven't found the time04:47
mwhudsonPeng: so i guess the question is: is this a url that should render and explodes, or a link we shouldn't have generated?04:47
PengAnd I don't have an answer.04:48
beunofrom the traceback, it seems it blows up in bzrlib, LH seems to pass on an incorrect fileid04:49
beunoPeng, how many branches are you serving from LH?04:50
mwhudsonindex.txt-20071121073725-0corxykv5irjal00-104:50
beunoit would be good if we could know which one had index.txt04:50
Pengbeuno: Um. Maybe a little over 30.04:50
beunoand what it's real fileif is04:50
beuno*fileid04:50
PengIt's in the URL.04:50
PengHm.04:51
beunoPeng, can you run bzr ls --show-ids in that branch?04:51
beunoah, wait a minute...04:52
beunois not present in the tree None04:52
beunothe tree should probably no be None...04:52
mwhudsonthere's no file with that file id in bzr.dev it seems04:53
mwhudsoni don't know how you can tell if there ever was such a file id04:53
mwhudsonconvert the branch back to knits? :)04:53
PengThat revid is r3231 of my branch, and probably bzr.dev.04:53
* mwhudson types the fileid into google04:53
Pengyeah04:54
PengThere wasn't such a fileid in that revision.04:54
mwhudsonthe file id was fora  file called index.txt in the root afaict04:55
beunomaybe bzr-search can help in that area?04:55
PengHeh.04:55
PengWant me to file a bug about the logging thing?04:55
beunoplease  :)04:56
mwhudsonand it was removed in r3067 it seems04:56
mwhudsonah hah04:56
mwhudsonok, this is quite a good one04:57
mwhudsonin the changelog view04:57
mwhudsonwhen a file is removed04:57
mwhudsonwe link the filename to ...04:57
beunoaaaaaaah04:57
beunolol04:57
beunointeresting  :)\04:57
pooliehello beuno04:57
beunohey poolie04:58
pickscrapeI'm trying to debug bug 56680 (diffstat), but I'm struggling to get bzr to even add the file given in the zip attached to the bug04:58
ubottuLaunchpad bug 56680 in bzr-diffstat "uncaught exception: bzr: ERROR: exceptions.UnicodeDecodeError:" [Low,New] https://launchpad.net/bugs/5668004:58
pickscrapeIt is complaining thus: BzrError: Parameter ''Lekt\xfcre'' is unsupported by the current encoding.04:58
pickscrapeAny idea how I get my encoding right to allow bzr to add it? I'm not too familiar with locales etc.04:59
Verterokpickscrape: your terminal encoding don't support ¿utf-8 maybe?04:59
mwhudsonbeuno: should be easy to fix i hope04:59
beunomwhudson, so we should either remove the link, or point to the previous revision04:59
Verterokpickscrape: linux + bash?04:59
pickscrapeLANG is en_US.UTF-804:59
pickscrapeVerterok: Yes, Ubuntu Hardy.04:59
Verterokpickscrape: try this: python -c "import sys; print sys.getdefaultencoding()"05:00
pickscrapeVerterok: ascii05:01
Verterokpickscrape: and sys.getfilesystemencoding()?05:02
pickscrapeUTF-805:02
VerterokI get ascii and utf-8 for each one05:02
Verterokit "should" work (I recently fixed a similar bug in xmloutput)05:02
pickscrapeI'm not even at the point of fixing diffstat yet :)05:03
pickscrapeIt's getting it added by bzr that is currently falling over.05:03
Pengmwhudson: So..you figured out where the tracebacks were coming from?05:03
mwhudsonPeng: yes05:03
mwhudsonPeng: look at http://bzr.mattnordhoff.com/loggerhead/bzr/configobj-4.5.2/changes/306705:04
Verterokpickscrape: the diffstat command class should have a encoding_type attribute05:04
mwhudsonPeng: expand the first revision, click the link to index.txt05:04
beunomwhudson, linking to the previous revision is probably what the user expects (actually being able to see the file)05:05
Pengmwhudson: Okay. That was quick. :)05:05
pickscrapeVerterok: I don't want to start trying to fix diffstat until I can reproduce the problem, and I can't do that without having a file with unicode characters in its filename already recognised by bzr05:05
mwhudsonbeuno: or just have it not be a link05:05
beunomwhudson, well, that's easier, just would be interesting to know what the user expects05:06
beunoPeng?  :)05:06
Verterokpickscrape: I understand, but I think you are hitting a new bug :)05:06
pickscrapeYay :)05:06
Pengbeuno: ?05:07
pickscrapeVerterok: Bug in bzr itself?05:07
beunoPeng, what would you want/expect LH to do when a file is removed?05:07
Pengbeuno: I think linking to the previous revision would be most useful.05:07
PengBut having no link at all would be easiest code-wise, obviously.05:08
Verterokpickscrape: I hit a similar problem with the 'annotate --xml' command in xmloutput plugin and it was related to the encoding_type attribute05:08
beunoof course, moving the user to a previous revision will be very confusing if they want to navigate from that page...05:09
beunohow about both?  no link, link beside it, "See index.txt in revision X"05:09
pickscrapeencoding_type in diffstat is currently05:10
pickscrape'replace', but I'm having this problem with bzr add05:10
Pengbeuno: That sounds good to me.05:11
beunoI'll file a bug for it05:12
Verterokpickscrape: do you have a traceback?05:13
pickscrape!paste05:14
ubottupastebin is a service to post multiple-lined texts so you don't flood the channel. The Ubuntu pastebin is at http://paste.ubuntu.com (make sure you give us the URL for your paste - see also the channel topic)05:14
Pengbeuno / mwhudson: Thanks for you help. :)05:15
* Peng points out that tracebacking on bad input is also bad.05:15
pickscrapeVerterok: http://paste.ubuntu.com/23238/05:15
mwhudsonPeng: oh yes, there should be a bug for that too05:15
mwhudsonloggerhead is very bad at validating its input05:16
* beuno files a bug for that too05:16
Verterokpickscrape: indeed it looks like a bzr or env. problem05:18
pickscrapeVerterok: thanks, I'll raise a bug. Either way it will be either fixed or the solution documented :)05:18
beunoI wonder how this removed bug hasn't surfaced through LP05:19
beunoanyway, Peng, thanks for all the bugs, and, especially, patches  :)05:20
PengLP has a very restrictive robots.txt, so it won't get triggered by them.05:20
Pengbeuno: :)05:20
mwhudsonhm, so i'm little surprised that paste doesn't send uncaught exceptions to _some_ logger05:24
pickscrapeVerterok: thanks for your help. I need to go to bed now. :)05:24
Verterokpickscrape: np, sorry I can't give you more pointer on where to look05:24
mwhudsonshould be easy enough to write some middleware for that though05:25
beunoPeng, commit 179 removes the link  :)05:35
Pengbeuno: Cool. :)05:36
beunobut of course, mwhudson deserves the credit for being so smart05:36
PengI'm sure this will make Googlebot happy.05:37
* beuno goes off to tweak loggerhead-serach a bit better before lifeless's presentation05:37
mwhudsonPeng: it will keep on requesting those urls for a few years i guess05:39
mwhudson:)05:39
PengHeh, true.05:39
PengWell, then, I'm gonna go to bed. Good night, and thanks again. :)05:42
beunog'night Peng05:43
beunolifeless, pushed my loggerhead search changes, UI is a bit better, so I may even try and put it for review tomorrow06:01
beunoanyway, that's it for me today. Good night folks06:03
lifelessnight beuno06:04
lifelessbeuno: coolness06:04
beunolifeless, good luck with your presentation, and blog about it so we know how it went  :)06:05
mwhudsonbye beuno06:05
beunomwhudson, good luck with those file descriptors. I'm interested to see what you come up with06:06
mwhudsoni'm not going to get to it today :(06:07
lifelessmwhudson: how have you gone with the ssh server?06:19
mwhudsonlifeless: we think we have it beat06:19
lifelessexcellent06:20
ToyKeeperMaybe this is crazy, but is there any way to branch a remote repo to a local one, without the complete history?  (perhaps only the past 50 revisions or somesuch)06:41
ToyKeeperI keep seeing people complain that they don't want to download a project's entire history before making changes.06:42
spivNot crazy at all.06:42
spivlifeless is working on smoothing off the rough edges of a feature to do exactly that.06:42
* mwhudson gets ready to stop for the week06:42
lifelessmwhudson.suspend()06:43
AfCAre we still calling that "shallow branches", or has that become a feature of "stacked branches", or ... ?06:44
* ToyKeeper tells the users to be patient, since the feature is in progress :)06:45
lifelessAfC: its being touted as stacked06:45
lifelesswhich makes me think entirely non appropriate thoughts.06:45
AfClifeless: that seems ... a less than ideal choice, given that "shallow" creates the impression of minimalism, whereas "stacked" means, well, nothing to do with thin. I can imagine you are thinking inappropriate thoughts :)06:52
lifelessAfC: :)06:54
lifelessJc2k: is it git-svn that makes http://bzr-mirror.gnome.org:8080/gtk+/trunk/changes show just a list of names and dates?06:54
AfClifeless: replying on Jc2k's behalf: I don't think so. Contrast revno 1603206:57
AfClifeless: most of the people who hack on GTK whack their ChangeLog entry into the commit message, and so the first line thereof is, well, the usual. The translators seem to not do that, but then there are also GTK hackers who don't either.06:58
AfC(whether any one group is or isn't using git-svn to facilitate this behaviour I can't tell you)06:58
=== zou_ is now known as zou_away
markhshould the bzr binaries for windows set the PyOptimize (sp?) flag, or should I stick with __debug__ mode?07:10
markhiirc, most assert statements are gone07:11
markhI should see if the test suite completes any faster with binaries built with that flag...07:12
vilamarkh: *all* assert statements should be gone by now, there is even a test for that to ensure they don't come back07:12
lifelessAfC: ok07:12
markhso there's no good reason to not set that flag?07:12
lifelessmarkh: indeed07:13
markhlifeless: thanks07:14
ToyKeeperHmm, I wonder how best to handle svn->bzr conversion.  The tags/ dir has 90% of the files.07:15
ToyKeeperI suppose I could just convert trunk/, and manually tag based on when people copied trunk to tags/.07:16
=== prateeksaxena is now known as prtk
AfCToyKeeper: that would probably work07:27
ToyKeeperYeah, except there's some stuff in branches/ too, and I'd lose that if I only did trunk/.07:28
ToyKeeperIt's probably better than pulling in tags/ and then having to delete it all though.  :)07:29
=== gour is now known as gour|afk
markhso, finally worked out my ssh problem!  I'm guessing support for plink is new, as that is the problem.  If I disable plink and let it fall back to paramiko, it all works.08:29
mark1so it seems we do prefer plink over paramiko even when paramiko exists.08:45
mark1(did my last message about my ssh problem make it before I was disconnected?)08:45
=== markh is now known as Guest66607
=== zou_away is now known as zou_
=== mark1 is now known as markh
sabdflno revisions to pull!09:18
RAOFIs there a tarball of a bzr.dev repository somewhere?  My connection just refuses to branch bzr, either from launchpad or bazaar-vcs.org.09:49
KinnisonIIRC you can rsync it from bazaar-vcs.org09:50
KinnisonOtherwise, get a tarball of a recent bzr and then branch bzr.dev with that09:50
Jc2klifeless: thats just one of the braindead ChangeLog things we have to deal with09:53
Jc2ksome people put a copy of the changelog entry in the commit09:54
Jc2ktranslators don't, hence the rev AfC pointed out09:54
james_wRAOF: is there a bug in bzr you are hitting, or is it just your connection?09:58
RAOFjames_w: I'm not entirely sure.10:00
RAOFWhen I try to branch bzr I end up getting unknown host errors, so it's probably my connection.  On the other hand, these errors always appear to occur at abount the same point in the branch process.10:02
RAOFKinnison: You'd rsync http://bazaar-vcs.org/bzr/bzr.dev, right?10:03
RAOFOf course you wouldn't.  That's not how rsync works :/10:04
bob2no, that's http :)10:04
bob2rsync -r bazaar-vcs.org::bazaar-ng/bzr/bzr.dev .10:05
RAOFThanks.10:05
* RAOF was stocastically converging on that.10:06
Kinnison:-)10:08
=== cprov-out is now known as cprov
=== gour|afk is now known as gour
whshttps://bugs.edge.launchpad.net/bzr.webdav/+bug/24349113:06
ubottuLaunchpad bug 243491 in bzr.webdav "bzr push ask my password multiple times" [Undecided,New]13:06
=== kiko__ is now known as kiko
aa_hi, any doc for using the revision of a branch in a python application as the "version" ?13:15
james_waa_: there is the "version-info" command13:16
james_w"bzr version-info --python > _version.py"13:17
james_wfrom _version import version_info13:17
james_wversion = version_info['revno']13:17
james_wor some variation on that.13:18
aa_yeah, looks great, thanks13:18
gouraa_: hello. how is pida doing?13:18
jelmerluks: you rock13:18
aa_gour: ! hello, pida is doing fine, thanks13:18
gouraa_: cool. i moved to emacs...13:19
aa_gour: pida does emacs too :)13:23
gouraa_: are the patches applied upstream?13:24
gouraa_: i use cvs version13:24
gouraa_: ..and moved to bzr13:25
luksjelmer: umm, I do? :)13:26
jelmerluks, automv13:27
luksoh13:27
james_woh yeah, I agree with jelmer, you do.13:27
awilkinsHow do you merge two folders that have been added independantly in different branches under tha same name13:34
jelmerI don't think you can since they would have different file ids13:34
awilkinsWhen you merge, one gets moved, you want to move files from the usurper into the .moved folder and ditch the usurpoer13:34
awilkinsI'm finding it a little tricksy13:34
awilkinsOk, sorted13:38
awilkinsMoved the files from the usurper, trashed it, move dhte old one back, resolved13:39
fdvHi. "bzr: ERROR: exceptions.KeyError: 'pop(): dictionary is empty'" on a 'bzr st' is a known error, right?13:47
james_wfdv: sounds familiar13:47
james_win tsort.py?13:47
fdvyep13:47
james_wyeah, would you like me to find the bug?13:47
fdvjames_w: that's ok, I think I've seen it13:48
fdvthen I'll just scrap that repo and create a new one13:48
fdvbut thanks :)13:48
=== mw|out is now known as mw
=== prateeksaxena is now known as prtk
jelmerjam: ping14:22
jelmerlifeless: ping14:22
jamjelmer: ??14:29
jelmerjam: Hi!14:29
jamdoes everyone know the moment I log in ?14:29
jelmerLucky guess (-:14:30
jelmerjam: I was going to ask you about something but already forgot what it was14:32
jamjelmer: well, I'm merging your setup.py change if that was it14:32
jelmerI should've asked you about that as well, but that wasn't it14:33
jamthough you are missing the Copyright and other headers14:33
* jelmer tries to revive his short-term memory with some coffee14:33
jamalso, do we want to force "python2.4" what if they have 2.5 installed?14:33
jamI realize it is avoiding 2.3...14:33
jelmerIn my defense it was copied from bzr-email so it's all Roberts fault :-P14:34
jelmerYeah, just using python makes sense now14:34
jelmerThere's very few systems around anymore with python2.3 as default python14:34
jamjelmer: though honestly, I always run with "python setup.py" rather than "./setup.py"14:38
jambut I suppose some people do it the other way14:38
jelmerYeah, most people seem to do that14:38
jelmerI always get annoyed by setup.py's that aren't executable14:38
KinnisonIf you're worried about 2.3, do the sys.version hack at the top?14:39
jam*I'm* not worried14:49
jamsome people might be14:49
jambut they can just do "python2.4 setup.py"14:50
Kinnisonkay14:51
jamof course, I didn't even have a setup.py script14:52
jamI don't believe in needing more than "bzr branch" :)14:52
asabila small question some git fanboys have been asking, and I don't really have an answer15:14
asabilwhy does bzr not use the same repository format as git ?15:14
james_wbecause it doesn't used hash based naming for stuff15:14
jam"it" being bzr15:14
jamWe could use it as a layer, but we would still need a layer on top of it15:15
jamIt also doesn't store anything like "per-file graphs" etc.15:15
jamIt just stores "content blobs"15:15
james_wthe indexes for git packs are better than what we have, mainly because they have fixed length names.15:15
asabilhmm oki, thanks :)15:16
awilkinsHow does git reassemble hunks into files, anyone know?15:18
awilkinsDoes it just have "make me a file" hunks?15:18
james_wawilkins: it doesn't split files15:19
awilkinsjames_w: Yes, but it has to be able to write files to disk15:19
james_wit's "blobs" are full texts.15:19
james_wI'm not sure I understand the question then, sorry.15:19
awilkinsI think it's good that it can do things like track content that was split out of one file into multiple, but what I was wondering is how it knows which file to write the content into15:20
james_woh, it doesn't track that15:20
james_wit just guesses after the fact.15:20
awilkinsIf you view the content as one great big stream, are there hunks in the stream that correspond to "swtich context to this file" for exapmple15:20
awilkinsIt can't just guess, or the kernal source would come out as a big blob when you checked out.15:21
james_wso if you annotate a file it will also search in other files for the hunks when they disappear (moving backwards through history) and then link them up.15:21
awilkinsHmpph, I shall just have to look at the docs if I ever get the time15:22
awilkinsOr start using it15:22
jamawilkins: everything maps sha1sum => content object15:27
jamsome of these will be xdelta15:27
jamwith a marker that "I'm based on *this* sha1sum"15:27
jamat the top level you have "inventory" blobs15:28
jam(I think the git term is "tree")15:28
jamAnd then you have "commit" blobs which reference tree blobs, which reference raw file content blobs15:28
awilkinsKnew it had to be in there somewhere15:28
awilkinsSo it's hierarchical and not stream based15:28
jamawilkins: that is my understanding15:28
jamand the reason git repack --as-hard-as-you-can actually works pretty well15:29
awilkinsI'll trust that more than the back of a cereal packet :-)15:29
jambecause it just does an xdelta against 50-or-so likely-to-be-close sha1sums15:29
jamand grabs the smallest.15:29
jamsmallest delta15:29
jamI don't specifically know how that effects performance on *extracting*15:29
jamas it could lead to arbitrarily long chains (unless that is also capped somehow)15:30
lifelessjearl: pong15:30
lifelessjearl: sorry15:30
awilkinsjam: It's the kind of realm where speculation is useless and test implementations are everything15:30
lifelessjearl: I wanted jelmer how has loged out15:32
wingo-tpgreetings.15:54
wingo-tpi have more traceback nasties.15:54
wingo-tphttps://bugs.launchpad.net/bzr/+bug/24353615:54
ubottuLaunchpad bug 243536 in bzr "bzr log fails" [Undecided,New]15:54
mware any bzr developers planning to attend http://guadec.expectnation.com/guadec08/public/schedule/detail/81?15:55
wingo-tpi will be there but i am not a bzr dev.15:56
mwthe feeling i get is that git will be railroaded through, which would be unfortunate15:56
wingo-tpthe topic seems a bit out of date: there already are git and bzr mirrors.15:58
Jc2kmw: there will be 4 at least bzr/canonical guys there, and mark afaik15:58
mwjc2k: ah, excellent15:59
wingo-tpeither one would be fine imo...15:59
Jc2kim just amazed at the kinds of arguments the pro-Git people are making16:00
Jc2kand they even admit they havent tried anything else16:00
capiscuas19821 question, one member of my team is trying to push in my bzr branch, is that possible? or it must be a team branch16:00
capiscuas1982$  bzr push lp:subdownloader16:01
capiscuas1982Enter passphrase for key '/home/leggewie/.ssh/id_dsa':16:01
capiscuas1982bzr: ERROR: Cannot lock LockDir(lp-146781388:///~capiscuas/subdownloader/trunk/.bzr/branchlock): Transport operation not possible: readonly transport16:01
capiscuas1982i don't know how to give him write access to ~capiscuas branch16:01
Jc2kwingo-tp: i would be happy to keep subversion, as bzr-svn does a wonderful job16:01
radixcapiscuas1982: yeah, you'll need to create a team16:02
radixcapiscuas1982: if you want multiple people to be able to push to the same exact branch16:02
radixcapiscuas1982: alternatively he can push to his own branch location and you can merge it into your branch16:03
james_wJc2k: it may be that svn would be better that git, as I doubt bzr-git could do as good a job as bzr-svn.16:03
capiscuas1982team is already created at ~subdownloader-developers16:03
capiscuas1982how can I copy from my branch ~capiscuas into a new branch ~subdownloader-developers ??16:03
radixcapiscuas1982: bzr push lp:~subdownloader-developers/subdownloader/trunk16:04
capiscuas1982radix: i got this bzr: ERROR: Transport operation not possible: http does not support mkdir()16:05
Jc2kjames_w: my day job is (sadly) to make "libgitcore", (http://git.codethink.co.uk/?p=git;a=shortlog;h=libgitcore). im hoping that might help bzr-git, but im not going to take that route until after GNOME has picked a DVCS16:05
radixcapiscuas1982: run "bzr lp-login <your username>"16:05
radixfirst16:05
radixyou should only need to run that once16:06
capiscuas1982radix: thks16:06
james_wJc2k: yep, it probably would help, but the friction between the two models might make it difficult anyway. Or perhaps it just needs someone smarter than me to work on it.16:07
capiscuas1982radix: it worked, but i'm surprised it didn't ask for my password in launchpad16:08
radixcapiscuas1982: authentication works with your ssh key16:08
capiscuas1982oh yeah16:08
capiscuas1982right16:08
wingo-tpso16:11
wingo-tpanyone have an idea about #243536?16:11
mwJc2k: yeah, they mostly started using git because somebody famous wrote it, suffered hugely for months, finally came to grips with it, and now claim to have no time for anything else16:11
mwand now say "oh, but it makes perfect sense once you read 'Git for Computer Scientists'16:12
wingo-tpcould it be the same as 239499 ?16:12
wingo-tpdifferent repos, but both arch-imported...16:12
wingo-tpin this case i can't even do a bzr log, which sucks.16:13
wingo-tp(jam? :)16:14
wingo-tpthis is becoming urgent16:15
jamwingo-tp: I think it is fixed in 1.6b2 if not there in b3, abentley had the fix16:16
wingo-tpjam: it's not16:16
jamwingo-tp: I'm checking quickly about it16:17
jamhopefully it isn't a huge repo16:17
wingo-tpnot huge, no; a few hundred revisions16:18
wingo-tpthanks for taking a look16:18
walkerajSome clarification.  If I don't use init-repo --no-trees, then each time a branch is created it gets its own copy of the entire working tree, correct?16:30
jamwingo-tp: sorry about the delay... "bzr log --short -r -10..-1" works fine :)16:37
wingo-tpheh ;)16:38
wingo-tptx jam :)16:38
wingo-tpbut... hm. we still have a problem :)16:38
jamwingo-tp: actually, 'bzr log --short -r 1..-1' also works fine16:38
jamYeah, I see the problebm16:38
jamjust slowing working out the "outer boundary" of it16:39
wingo-tpinteresting16:39
wingo-tpcool16:39
jamthe problem is pretty much *just* that the first revision claims to have a parent, but it is a ghost16:39
jamso "revision_history" tries to walk off and hits that16:39
wingo-tpah.16:39
jamso... oddly enough, we have this "trap" for it:16:40
jamself._extend_partial_history(stop_index=last_revno-1)16:40
jamwhich is what abentley did16:40
jamah, ok, so it is now breaking in a different location16:41
jamweird, I could have sworn it was breaking there16:42
jamanyway, now it is breaking in "tsort" for log --long16:42
jamso "bzr log --long -r 2..-1" works, because it doesn't try to include that problematic 1st revision16:42
guilhembijam: hi! I posted on the support issue. Need to run16:42
guilhembibbl16:42
walkerajHmm, did my last message come through?  This is my first attempt using pidgin for IRC, and I am leery.16:44
bpetersondoes anybody offer free Bazaar hosting (ie github.com or freehg.org) aside from Launchpad?16:59
PengI'm not sure.17:00
PengOn the upside, bzr can work with dump HTTP and SFTP, so you can host it basically anywhere, but that doesn't get you a slick interface.17:01
awilkinsbpeterson: Cheap hosting by anyone who provides a web host with sftp or ftp uploads :-)   ?17:01
bpetersontrue. So I could I setup it up easily using the SF webspace?17:01
Pengyes17:02
PengThe only setup required is "mkdir bzr", then just push over sftp.17:02
bpetersonnice although I might just bite the bullet and use launchpad17:02
PengLaunchpad is pretty nice.17:02
bpetersonIt's a pity it doesn't have a wiki, though.17:03
jamwingo-tp: well, the quick fix is to edit your ".bzr/branch/last-revision" file and tell it that you only have 138 revisions instead of 139, but I don't know how that will work long term.17:07
jamtesting17:07
wingo-tpinteresting17:09
wingo-tpi guess i should fix the history at some point, no?17:09
jamwell, we should support this sort of thing as well17:09
jamfor example "bzr reconcile" has some code to fix incorrect last revision info, but it fails because of the ghost in your history.17:10
jamalso, after my "fix" doing "bzr log -r 1" seems to return the first revision as revno 217:10
jamwhich is just weird17:10
* vila cries17:48
vilaftp... I hate you17:48
vilathe protocol is messy, the servers interpret it with a crystal ball, trying to run then without being root is a dream, TDD nightmare :-(17:49
vilas/then/them/ even17:49
jamvila: then don't use ftp :)17:55
Kinnisonvila: ftp sucks17:56
vilajam: Ooooh, *I* don't use it :-) I wanted to add chmod support in bzrlib so that bzr-upload users can enjoy it...17:56
vilaKinnison: I know why now :)17:56
jamas you wish vila, as you wish.... I've jumped ship a while ago :)17:57
jamI honestly appreciate that you are willing to work on it17:57
vilajam: I can see that :-/ But well, I have a patch nearly correct, a single test is still failing because it's damn hard to recognize errors....17:58
jamvila: both ftp and sftp have *awful* error handling17:58
jamyou basically can't trust that you'll get anything better than "Failed"17:58
vilayeah, that's a shame, I'm now to the point where I wonder if the best solution will not be to issue *more* commands to get better diagnostics which is kind of weird when trying to avoid LBYL...17:59
jamwell, you could LAYL17:59
jam(look after you lept)17:59
vilayeah, my point17:59
jamthough failed is generally failed, even if users want more18:00
jamtell them to use something that doesn't suck if they want that18:00
vilathat could help raising NoSuchFile or DirNotEmpty instead of PathError18:00
PengNice, Googlebot has used 360 MB of bandwidth spidering Loggerhead, and LP has used 78 MB.18:00
jamnext you'll be telling me that you will be supporting servers that don't have APPE18:00
vilathe other problem I have is that the test suite covers more than is strictly needed... so it's a bit hard to decide when a failed test is really relevant :-/18:01
vilajam: not worth the effort18:01
vilaI was hoping that adding ftp servers to the local_test_server plugin will be as easy as http, but... root access required sucks18:02
vilaI think I will leave that percolate a bit, I'm too much in anger against that mess right now :-)18:03
vilaI sepdn the whole week on it (part time of course, but yet, several couples of hours) and the conclusion is that, anyway, there are so much requests sent that the performances will always suck18:04
vilaand all of that to finally implementing chmod in our own test server in a couple of minutes...18:05
vilajam: do we really have users for ftp ?18:06
jamvila: yeah, we do18:06
jam:(18:06
vilaWell, at least that means our implementation is correct...18:07
vila...correct for our needs :)18:07
vilajam: anyway, sorry for the rant, I needed to tell it to someone :-)18:08
jamthe only bit I've been seeing is the APPE stuff18:08
jamrant away18:08
jamI didn't like *my* time in the ftp code either18:09
jamI'm happier being an ear to rant towards than being the one doing the work :)18:09
vilajam: hehe18:09
vilaI'll get back to preparing my submission :)18:09
=== kiko is now known as kiko-fud
=== thekorn_ is now known as thekorn
=== prateeksaxena is now known as prtk
=== mw is now known as mw|food
mkanatWhat branch format should I be using for new branches that only I am going to be using?19:26
jelmermkanat: rich-root-pack may be a good choice, that's going to be the default in the near future19:27
mkanatjelmer: Okay.19:27
jelmerotherwise, the default (pack-0.92) should work fine as well19:27
=== mw|food is now known as mw
PengIf you use pack-0.92, you can upgrade to rich-root-pack later..20:06
PengHow does upgrading to a rich-root format work? Does it pick a random file ID for the root? If two people upgrade the same branch, will they use the same ID?20:07
jamPeng:  I think it standardizes on "TREE_ROOT" as the file id for the root20:15
jamso all trees share the same root at that point.20:15
PengOh.20:16
PengOkay.20:16
abentleyjam: it uses whatever root id was already the root id, but 99.9% of the time, that's TREE_ROOT20:19
PengThere's a root ID when you're not using a rich root format?20:23
jelmerPeng: only that implicit one20:30
PengAh.20:31
vilajam: regarding _can_roundtrip_unix_modebits, did your review implies that we will use it only for our tests and never as part of bzrlib ?22:12
vilajam: the underlying question being: can I put it into the test classes instead so that I can query the server too ?22:13
vilato be able to test against server with and server without chmod support ?22:13
vilahmm, not there anymore, no urgency, since you voted tweak, I can do that in a later patch22:14
jamvila: I only "_can_roundtrip" be used in the test suite22:42
jamI only *see* ...22:43
jamAnd for example in chroot we do:22:43
jamdef _can_roundtrip_unix_modebits(self):22:43
jam    return self.server.backing_transport._can_roundtrip_unix_modeb22:43
jamso you could conceptually do 2 returns based on whether the server can/can't support it22:43
jamBut logically, it just enables the tests for that action22:43
jamif you say "False" then we skip all the related tests22:43
vilayeah, I can't imagine using it in bzr anyway, what if it returns False ? :)22:43
jamSo I don't think there is an advantage to testing across that22:44
jamvila: it is just for the test suite, so we can assert that it really does what we want when we pass a mode bit22:44
jamIf the transport can't support it, it just gets ignored.22:44
vilahmmm, I see. So the tests are structured to test the mode bits last so that all other features are already tested.22:45
jamvila: right22:46
jamif they were *good* tests they would have separated them out22:46
vilaBut, if the server doesn't implement it the tests will fail anyway if we say can_roundtrip22:46
jamI wrote them, though, so you are stuck with what you get :)22:46
vilajam: good point, now that you said it, I thought about separating them at one point :)22:47
jamvila: be my guest22:47
jamI think I wrote that code 2-3 *years* ago22:47
vilaok, so no problem in putting can_roundtrip into the tests classes instead of the transport classes ?22:47
vilaso that the server can be queried too if needed22:48
jam       john@arbash-meinel.com-20060116213637-2f4cc1c55769f464 |     def test_unicode_paths(self):22:49
jamSo it seems I wrote it in Jan, 200622:50
jamabout 2.5 years ago22:50
jammy TDD was not as good then :)22:50
vilaHa ! Of course I'll have to write a true ftp.stat() first :-/22:50
vilaWhich demonstrate that you're better TDD hacker now :)22:51
vilas/better/a better/22:51
vilajam: Do you think that patch can still find its way into bzr-1.6 or is it too late ?22:54
jamvila: At this point, I have very little idea of when 1.6 will land22:54
jamso if you merge it *today* I think it will get in :)22:54
vilahmm, same here :-/22:54
jamI can't say much outside of that22:54
jamVersionedFiles and stacking is almost done22:55
jamthe bulk of it has landed.22:55
vilaOk, last thing before I go to sleep then...22:55
jelmerlifeless, ping23:32
krowHi!  So I just pushed a new tree to Launchpad. I then go and do a bzr branch lp:name from it.23:42
krowThen I do a bzr merge /tmp/patch23:42
krowThat merge pukes on this:23:42
krow[brian@piggy drizzle]$ bzr merge /tmp/\[MERGE\]\ bzero\ to\ memset.txt23:43
krowbzr: ERROR: Revision {('brian@localhost.localdomain-20080625052913-\xc2\xa06upwo0jsrl4lnapl',)} not present in "<bzrlib.knit.KnitGraphIndex object at 0x7f89830956d0>".23:43
krowSo...23:43
krowI know the patch was generated from the recently created tree.23:43
krowWhat am I, and I suspect it is me, screwing up?23:43
=== kiko__ is now known as kiko-afk
lifelessjelmer: pong23:52
lifelesskrow: hi23:53
jelmerlifeless: So, I've got --stacked working with your shallow-branch branch23:53
jelmerexcept...23:53
jelmerit fetches all revisions23:53
jelmers/working/passing tests/23:53
lifelesskrow: you created a cherry pick patch, but the reference branch, the one that is expected to be common to anyone applying the patch, has more history than the one you are applying the patch too23:54
lifelessjelmer: ok23:54
lifelessjelmer: uhm, merge in aarons stuff too23:54
jelmerlifeless, where's that?23:54
* jelmer looks on bb23:55
jelmerRe: [MERGE] Stacking policy   ?23:55
lifelesskrow: so, what (exact) command did you use to make the patch?23:55
lifelessjelmer: yes23:55
jelmerah, that includes two of the fixes I had already made locally23:56
jelmerlifeless, nope, that doesn't appear to help (though it doesn't break the tests either)23:59
jelmerI suspect a bug in one of my FakeVersionedFiles implementations..23:59

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