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

pooliehello jam00:01
jamhi poolie, a little late for "before the standup call" :)00:01
poolieyeah :)00:01
strkI have two branches in a repository. One I use for dev, standalone. Another I use for trackign trunk, bound upstream.00:15
strka working tree switches between the two00:15
strkbzr diff ../bzr-local-repository/trunk # shows nothing00:15
strkbzr diff ../bzr-local-repository/mybranch # shows nothing00:16
strkfrom the working tree00:16
strkis that enough to tell 'trunk' and 'mybranch' don't differ ?00:16
strkbzr diff ../bzr-local-repository/trunk ../bzr-local-repository/mybranch # gives me:00:17
strkbzr: ERROR: sorry, u'..' not allowed in path00:17
strkwhat does the << u'..' >> part mean ?00:17
strktypo in bzr code ?00:17
emgentheya00:18
spivstrk: the u'' is Python's way of indicating a unicode string.00:21
strkthx, any idea about previous question ?00:23
strki'm having troubles figuring out a good workflow, as it seems every merge puts my working tree in a non-up-to-date status00:23
strkeven if there's nothing to merge (apparently, since diff gives no diffs)00:24
spivWell, there are different types of differences :)00:24
spivThere's difference in content, that's what "bzr diff" does.00:24
strkit seems I basically got an 'empty' commit in mybranch00:24
spivThere's also difference in history.  "bzr missing" can report on that.00:25
strkwhich I guess is the commit that a merge to trunk is showing as a "pending merge" again00:25
strkthe two branches obviously have a different history00:26
strkif, from a trunk-bound tree I call 'bzr missing mybranch'00:26
strkI get that annoying missed revision00:26
strkmessage:   trunk merge ?00:27
strkthat's a commit after a merge of trunk to mybrach00:27
strkseems silly to merge back to trunk, as it came from trunk initially!00:28
spivYou might prefer "bzr merge --pull"00:28
strkkind of an egg & chicken00:28
igcmorning00:37
lifelessstrk: this is a bug actually;00:41
lifelessstrk: the graph fails to converge correctly00:41
strkis there something I can do to help tracking it ?00:42
lifelessuhm00:42
lifelessfor now00:42
lifelessif when you merge00:42
lifelessbzr st shows nothing other than pending merges00:42
lifelessjust revert00:42
strkI'm afraid I failed in that when merged trunk into mybranch00:43
strkhow can I check that ?00:43
strklike, how can I get bzr log tell me exactly which files were changed, if any ?00:43
spivbzr log -v00:43
strkouch00:44
strklooks terribly wrong00:44
strkhttp://rafb.net/p/yWqEyF12.html <-- bzr log -v -l 10 (from mybranch-bound working tree)00:45
lifelessspiv: this is gnash btw00:45
lifelessspiv: who have just migrated00:45
strkshouldn't the indented entries under revno: 9430 show "composition" of that commit ?00:45
strk(first rev)00:45
spivlifeless: ah, nice00:46
lifelessback soon; bacon and eggs are calling00:46
strkit seems that was my first backward merge00:46
strkso far I've always merged mybranch *into* trunk00:47
strkbut for the first time, to commit something to trunk w/out reverting or committing my changes ... I did the commit from another working tree00:47
mwhudsonbeuno: are you around?00:47
strkthen I tought I had to merge trunk to mybranch, and the log above shows what happened00:48
spivstrk: I'm not sure what you mean by "composition"00:48
strkspiv: I'm still trying to understand 'bzr log' output00:49
strkmy current interpretation is based on 'bzr log' output from trunk, which seems clearer00:49
strkby "composition" I mean a kind of commit trackback history00:50
strkfor example00:50
strkhttp://rafb.net/p/oatno492.html <-- thise is bzr log for trunk00:50
spivRight, so r9430 merged in trunk (which had 4 revisions you didn't have, which are shown indented).  The only text changed by the merge was .bzrignore00:50
strkhold on00:51
strkr9430 merged in mybranch00:51
strk*from* trunk00:51
spivstrk: you might find a graphical layout helpful, e.g. "bzr viz" if you have the bzr-gtk plugin installed.00:51
strkI'll get it immediately00:52
spivIn http://rafb.net/p/yWqEyF12.html it shows r9430 in mybranch is a merge from trunk00:52
spivNote that the revnos in different branches can and do point to different revisions.00:52
strkright, r9430 is a merge from trunk to mybranch00:52
strkr9430 in mybranch, that is00:53
* strk looking at 'viz' now00:53
strkmm... timestamps are all bogus (ok, let's forget about that now)00:54
strkok, the graph from 9425 on is pretty spaghetti :)00:54
spivYeah, I thought it would be :)00:55
strklemme see if the viz for trunk makes more sense00:55
strk:'(00:56
strkless spaghetti, but still unclear00:56
spivSo the first paste shows r9430 (of mybranch) merged in trunk, and at that time trunk had four revisions mybranch didn't.  Most of *those* revisions were merges from mybranch.00:56
spivSo, I'm not sure what specifically isn't clear to you atm.00:56
strkok00:57
strkthe point is, the four revisions mybranch had all00:57
strksee 942900:57
strkr9429 of mybranch00:57
spivmybranch's r9430 merged in the changes in trunk which were a) some merges from mybranch (and thus no changes vs. mybranch), and b) a change to .bzrignore00:57
strk"Fix missing libgnashplugin.so glib link...."00:58
spivSo I see it.00:58
strkok, my point is that (a) is confusing00:58
strkwhat does it mean to merge changes that were merges from here ?00:58
spivAh.00:59
strkthe missing libgnashplugin.so thing00:59
strkwas committed in mybranch00:59
spivLook at the bzr viz for mybranch again.00:59
strkyes, I'm looking at it now00:59
spivAnd/Oo try "bzr log --show-ids"00:59
spiv"And/or", rather00:59
strkthere I see that mybranch r9429 was...00:59
strkok, restarting with --show-ids00:59
spivThe history of a branch is a DAG00:59
strkbzr: ERROR: no such option: --show-ids01:00
spivstrk: bzr log --show-ids?01:00
strkhttp://rafb.net/p/3IJBae18.html (--limit 12001:01
spiv(you can already see the ids in bzr viz by clicking on a revision and looking at the information below the graph)01:01
spivA regular commit makes a branch with just one parent.01:02
spiv(so just one "parent:" line in the log --show-ids output, and just one downwards line in the bzr viz diagram)01:02
spivA merge adds another parent.01:02
spivSo when you commit a merge, you're not just recording what files were changed by the merge, but exactly which revision was merged onto another.01:04
strkmm01:05
spivThis is what lets bzr automatically figure out which revisions to process when you do "bzr merge".01:05
strkdo you have viz window in front of you too ?01:05
strkops, I guess you ca'nt wout access to mybranch ?01:05
spive.g. if you get conflicts, and resolve them, then that resolution is recorded.01:05
spivstrk: right01:05
strkI have a r9425.1.1 (branch nick:trunk)01:06
spivI see that in your first paste, yep.01:06
strkwhich was supposedly (I tought it was) the merge of a sum of 3 commits I made in mybranch01:06
strkspecifically, r9426,r9427 and r942801:06
spivIt was.01:07
strkthe 'giz' graph shows r9425.1.1 in trunk having 2 parents01:07
strkor, two lines ...01:07
spivRight 2 parents.01:07
strkone is r9428 and the other is r942501:07
spivHmm, make sure you turn off View->Show Compact Graph in bzr viz.01:07
spiv(not sure if that's on by default)01:07
strkis off01:08
spivIf you compare the graph of those two parent revisions, you'll see that there are three revisions in mybranch that aren't in trunk.01:08
strkuh ?01:09
spivIn fact, try this: "bzr viz -r 9426" in trunk.  the top revision will be that merge.01:10
spivAnd what you should see will look like this: http://rafb.net/p/1KTfVR17.html01:12
strkyes01:12
spivi.e. two lines going down out of that revision, that's two parents.01:13
strktrilling01:13
spivBut three revisions along the right-hand line that aren't on the trunk (which is always on the left-most side in bzr viz, just like log)01:13
strkis the graph info all trunk has about those 3 revisions ?01:14
spivIt has the full contents of those revisions in its repo.01:15
strkk01:15
spive.g. in bzr viz you can double click on any one of them and get the full diff.01:15
strkgreat!01:16
strkso, back to mybranch viz01:16
strkr9430 in mybranch brought in .bzrignore changes only01:16
strkwhich was r9425.1.4 in trunk01:17
strkwhat I don't understand is the graph I guess01:17
spivWell, the only changes in trunk that weren't already in your branch were the .bzrignore changes.01:17
strkin that it *seems* to have brought in also r9425.1.3,1.2,1.101:17
spivRight, those are new revisions, but those revisions don't have any text changes that mybranch didn't already have -- because those revisions were merges from mybranch.01:18
strkoh, maybe r9425.1.2 AND r9425.1.4 did actually get in01:18
strkthe other two didn't because they had revisions in branch as parents01:19
strknamely, r9425.1.3 (trunk) came from r9429 (branch)01:19
spivRight, .1.1 and 1.3 were merges from mybranch.01:19
strkand r9425.1.1 (trunk) came from r9428 (mybranch)01:19
spivAll good now? :)01:21
strknot yet :)01:21
strkif I now merge mybranch into trunk01:21
strkthere's somehting unclear01:21
strkstatus gives pending merges:   Sandro Santilli 2008-06-25 trunk merge ?01:22
strkbut no changes01:22
spivRight.01:22
lifelessthis is a case we should actually detect and cancel a merge on01:22
spivThat's because there's a new revision, but for this branch that revision has no new changes to merge.01:22
spivlifeless: +101:22
lifelesswith --force allowing it to be done anyhow01:22
spivlifeless: (probably allow --force to override)01:23
strkalright, I'll take that as a bug01:23
spivlifeless: snap!01:23
strkanother thing. 'viz' shows me info about things I tought I reverted01:24
strkr9422.1.2 in mybranch01:24
strkshown in 'viz' for trunk01:24
strkshown in cyan color01:26
strknever mind, too late to think ... 2:30 am01:28
strkthanks a lot for your time01:28
mdmkolbe|workI have a repository in my home directory at the departmental machines, how do I check out from my home machine?  (e.g. like svn's svn+ssh://host/path)01:35
mdmkolbeI have a repository in my home directory at the departmental machines, how do I check out from my home machine?  (e.g. like svn's svn+ssh://host/path)01:41
lifelessmdmkolbe: bzr co bzr+ssh://host/path01:41
mdmkolbecool, thx01:42
* mwhudson adds 'logging' to the pile of things loggerhead does appallingly02:03
lifeless:P02:04
mwhudsonlifeless: did you see https://bugs.edge.launchpad.net/loggerhead/+bug/242806 ?02:05
ubottuLaunchpad bug 242806 in loggerhead "log rotation actually doesn't save old logs (it truncates them)" [Undecided,New]02:05
PengHeh.02:05
lifelessmwhudson: rotfl02:06
mwhudsonin better news, i can run 'ab -n 10 -c 5 'http://localhost:8080/revision/158' on ubuntu-desktop-course-beta (which is a laaarge revision page) and have the loggerhead process use 300 megs at the end02:08
jmllifeless: is there a way to view a log of all commits made to a thread?02:09
mwhudsonwhereas with kid, just rendering that page once got the oom killer into action02:09
lifelessjml: 'bzr log'02:10
lifelessmwhudson: excellent02:10
jmllifeless: that shows messages from before the thread was created02:10
mwhudsonthat page is still a DoS on the user's browser of course02:10
lifelessjml: bzr log -r thread:..02:11
jmllifeless: that shows messages from the last merge from the lower thread.02:11
lifelessjml: how about this; rather than me guessing what exactly you mean, you pastebin something, and say 'I want X Y and Z from there, and nothing else'02:12
jmllifeless: ok. probably later though.02:14
lifelessk02:18
PengQuick!02:27
lifelessjam: still around ?03:07
jamlifeless: current waiting for leo to die (WW), but somewhat around :)03:07
lifelessjam: I'm onto annotate03:08
lifelessand I'm at a complete loss as to what to do03:08
jamoops.. :)03:10
jamthe code you care about is in knit.py03:10
jamif you want to do the simple thing03:11
jamjust feed the fulltexts into annotate.reannotate()03:11
lifelessI'm hesitant to touch it because I know its been performance tuned03:13
lifelessand I have no benchmarks or other things to check I don't break it entirely03:14
* igc lunch03:45
* lifeless goes looking for jml's test for stacking on remote repos04:12
jamlifeless: I was planning on letting you make it slow, in exchange for having it *work* :)04:16
lifelessjam: :). Its on my list; I'm getting the stacking repo stuff polished first04:27
lifelessas annotate is not as strict a blocker04:27
jamsure, I would have thought some tests would fail, but there may not be a lot of per-xxx annotate tests04:28
lifelesswell04:30
lifelessnone that know to setup a basis repository, do a shallow branch precisely cross history lines and then annotate04:30
lifelessthere is one XFAIL, that I wrote :P04:30
lifelessJc2k: is loggerhead up on bzr-mirror yet ?05:00
mwhudsonseems to still be on 987605:03
lifelessyay:05:20
lifeless:!bzr commit -m "Implement generic stacking rather than pack-internals based stacking."05:20
lifelessjml: ping05:22
jmllifeless: pong.05:23
lifelessdo you remember where you put the patch that tests stacking on bzr+ssh ?05:23
lifelesslike was it mail, a bug, or ?05:24
jmllifeless: I grepped around in my sent mail and couldn't find it.05:24
jmllifeless: I might have it on disk in a branch.05:25
jmllifeless: once I finish this review I'll look again.05:26
poolielifeless: yay, way to go05:31
pooliebeuno, if you're still up, that demo site is *amazing*05:32
lifelessand on the 7th day05:32
pooliewell done05:32
lifelesspoolie: the bzr-search one ?05:32
lifelessbeuno: also, the download link, for a dir, could output a tarball :)05:34
lifelessjml: march 5 I found an email that describes the problem05:35
jmllifeless: yes, I found that.05:35
lifelessthumper: there are branches being created in the web ui for the bzr project that appear to be pure noise05:39
thumperlifeless: unfortunately that happens, a question on launchpad-bazaar is one way if you get no response form the owner, editing the whiteboard to tell the branch owner that it isn't appreciated is another05:40
lifelessthumper: putting aside my preference for not having that feature; I would be happy if branches that 'have never been pushed too' didn't show up on https://code.edge.launchpad.net/bzr05:41
jmllifeless: so, I think the tests are uncommitted changes in a working tree :\05:41
lifelessjml: ><05:41
lifelesspastebinned ?05:42
jmllifeless: I'll do so now.05:42
jmlhttp://paste.ubuntu.com/22781/05:42
jmllifeless: I seem to remember you narrowing the test down on your laptop.05:43
jmllifeless: but the memory is not trustworthy.05:44
lifelessI loath the ui of paste.ubuntu.com05:44
lifelessargh05:45
lifeless:!bzr patch http://paste.ubuntu.com/22781/plain/05:46
lifelessbzr: ERROR: http://paste.ubuntu.com/22781/plain is permanently redirected to http://paste.ubuntu.com/22781/plain/05:46
lifelessabentley: where do you want bzrtools bugs?05:46
abentleylifeless: bugs.launchpad.net/bzrtools05:47
lifelessabentley: thanks05:48
lifelessjml: bingo:05:53
lifelessjml:  02: bzr: support (but failing, RemoteRepository is not a PackRepository)05:53
jmllifeless: is this in a local branch of yours?05:54
spivlifeless: pqm seems to be confused; it processes a request, the log in the web ui shows it succeeded, but no change happens to bzr.dev and I get no email.05:54
lifelessits shelved05:54
lifelessspiv: gpg key expired05:54
lifelesshangon05:54
spivlifeless: ah.  Thanks.05:55
lifelessspiv: resubmit05:57
* spiv presses the magic button05:57
lifelessjml: and it passes!06:03
jmlgsap06:03
lifelesswhich means, we're gtg06:04
jmlsweet.06:04
jmlthat makes the stuff I'm working on now all that more pressing.06:04
lifelesspoolie: you gotta relax a bit more :P06:05
* jml makes another coffee and dives to hacking level06:05
lifelessjml: pushing an updated loom06:05
poolielifeless: uh?06:05
lifelesspoolie: you were stressing about stacking this morning06:05
jmllifeless: cool. I won't be looking at your branch today unless I am suddenly endowed with the nine rods of eternity.06:06
lifelessnein rohds huh06:07
poolielifeless: oh ok06:08
pooliethat's an interesting comment but remind me of it over that beer sometime06:09
lifelessok06:09
lifelessI was intending to tease was all06:09
lifelessanyhow, I'm about to send in a final review request for Development106:09
jmllifeless: yeah06:09
lifelessI'm now, finally, completely happy to land it06:10
jmllifeless: of course, if that happens I may have more pressing concerns than fast distributed version control.06:10
lifelessthen I'm going to drink some caffiene, and look at making annotate stack correctly06:10
mwhudsonif you want to stream out a file's contents is some version of iter_file_bytes() your best bet?06:24
mwhudsonor is get_file_lines() likely to work well too?06:25
beunopoolie, thanks  :)06:25
mwhudsonhi beuno06:26
beunohey mwhudson06:26
mwhudsonbeuno: did you see https://code.edge.launchpad.net/~mwhudson/loggerhead/streaming ?06:26
beunolifeless, downloading tarballs is on the bug list :)06:27
beunomwhudson, I haven't. Let's take a peak06:27
beunomwhudson, oh, cool!  That will make big diffs and annotates seem more responsive  :)06:29
mwhudsonyeah, and it keeps memory usage under control a bit more too06:30
mwhudsone.g. it can render my 24 meg horror test case revision page with ~70 megs resident06:30
mwhudsonit's a bit slower on that page though06:30
beunomwhudson, looks very good. We should do some benchmarking before release to compare the improvements, but it sounds like it's going to be a pretty big leap06:32
beunoalso, our dependencies are down to python-paste and python-simpletal. How cool is that?06:33
mwhudsonyeah, i'm pretty happy about that06:35
mwhudsonthough really, the streaming is a hack in some ways, we simply shouldn't be generating 24 meg pages06:35
mwhudsonah, cool06:36
mwhudsonso it turns out a little bit of buffering is a good thing :)06:36
beunono, we shouldn't. I'd like to experiment a bit on not using templates to generate the diff text and annotate content when we're past 1.606:37
beunoshould be a lot faster and a lot smaller06:37
mwhudsonbeuno: <blink>+1</blink>06:37
poolie:)06:38
beunobut that can only be done with the new HTML. I'm scared of the current one06:38
mwhudsonsure06:38
mwhudsonand we should really be focusing on getting to a releasable state i think now06:38
mwhudsonthere's so many improvements in trunk...06:38
beunoyeah, next on my list is do something sensible with setup.py06:39
beunoand, well, get the new theme landed  :)06:39
ferringbbeuno: refering to loggherhead from above, or...06:39
mwhudsonbeuno: so with a little bit of buffering to send ~1k at a time to the browser (rather than ~10 bytes) my torture test completes in 28 seconds06:39
mwhudsonvs. ~40 on trunk06:40
beunomwhudson, 12 seconds is a *really* big improvement06:40
mwhudsonyeah, i'm amazed, tbh06:41
beunoferringb, I'm sorry?06:41
beunomwhudson, does it pass the tests?  :p06:41
ferringbbeuno: "mwhudson, looks very good. We should do some benchmarking before release to compare the improvements, but it sounds like it's going to be a pretty big" ...06:41
mwhudsonbeuno: yes :)06:42
ferringbasking if that's in reference to loggerhead (presume it) or something else06:42
beunoferringb, yes, Loggerhead06:42
mwhudsonat one point it was only transmitting ~1% of the data to the client but that was a simple typo :)06:42
beunohahaha06:42
beunoare we still removing whitespaces?06:43
mwhudsoni feel a bit sad at having to write this though: http://pastebin.ubuntu.com/22785/06:43
mwhudsonbeuno: er06:43
mwhudsonbeuno: probably not06:43
beunomwhudson, well, that gave us big savings on large files, but I'm not sure what the memory/cpu tradeoff was for that06:44
mwhudsonhm, i can probably do it on the 1k chunks reasonably06:45
krowQuick question... what is the command with bzr to remove all files from a directory which are not in source control?06:45
ferringbbzr clean-tree06:46
spivbzr clean-tree06:46
spivferringb: beat me :)06:46
krow[brian@piggy drizzle-1.0]$ bzr clean-tree06:47
krowbzr: ERROR: unknown command "clean-tree"06:47
krowNo wonder I did not find it in the help drop down :)06:47
ferringbpart of bzrtools then06:48
poolieis it in bzrtools?06:48
poolieyou should be able to apt-get install that, or follow the instructions on the plugin page06:48
pooliedepending on your system06:48
krowFedora, so no apt-get.06:49
pooliei think it is packaged06:50
krowThere is a python tool for grabbing the latest bzr right? I can never remember what it is.06:50
mwhudsonbeuno: seems to still be worth it06:50
pooliei think that's ezsetup?06:51
lifelessyum on fedora06:51
lifelessor apt-get if you install it06:51
beunomwhudson, does it shave off a few more seconds?06:51
krowNah... there is some python tool... I always forget its name... anyways. Thank for the help :)06:52
mwhudsonno, it takes a little longer06:52
mwhudsonbut makes the page 30% or so smaller for my torture test06:52
mwhudsonmore like 40%06:53
beunoyeah, worth it on 24mb pages  :)06:53
mwhudsonright06:53
lifelesshi beuno06:58
beunoevening lifeless06:59
pooliekrow: probably the easiest thing is06:59
pooliemkdir -p ~/.bazaar/plugins && bzr branch lp:bzrtools ~/.bazaar/plugins/bzrtools07:00
beunomwhudson, I get 53sec vs 41sec for my big diff in trunk vs streaming. And, more importantly, browsing seems much further07:01
mwhudsoni haven't dared load up my big one in firefox :)07:01
mwhudsonbut cool07:01
mwhudsoni mean, still ridiculously, insanely long to wait for a web page07:02
mwhudsonbut progress is progress07:02
beunoyeah, it comes up fairly quickly with streaming now, so, if we compare against 1.2, this is light years better07:03
mwhudsonoh man07:04
mwhudsonwith 1.2 your machine would have fallen over :)07:04
jamesh41 seconds for a web page wasn't so bad 10 years ago07:05
beunoahahah, that can be our tagline for 1.6  :p07:05
mwhudson:)07:06
mwhudsonbeuno: ok, https://code.edge.launchpad.net/~mwhudson/loggerhead/streaming is at revno 182 now07:08
mwhudsonbeuno: can you read through the diff and let me know what you think?07:09
beunomwhudson, yeap, pulling now07:09
mwhudsoni guess things will be messy if an error occurs mid-page render07:10
mwhudsonnot much we can do about that though07:10
beunonot really. And that is probably better than nothing at all07:11
beunomwhudson, diff looks good. Stripping whitespace on flush seems like a much better thing to do07:15
mwhudsonok to merge?07:16
beunoabsolutely07:17
mwhudsonbeuno: i see you found the logging bug -- that's a real laugh/cry dilemma07:17
beunomwhudson, hehe, yeah. Poor guy really thought it rotated07:17
marianomsorry to bother everyone, just gonna say hi to beuno :)07:18
beunohey marianom!  What are you doing up?07:18
marianomI bet you know! :)07:18
beunomarianom, :)  let me know if I can help07:19
marianomon my way to sleep now. see you tomorrow, beuno (everything's ok btw) good night everyone and keep the good bzr rocking!07:19
* mwhudson merges & pushes07:21
mwhudson... and stops07:21
beunomwhudson, sounds good07:22
beunobtw, did you roll out on LP today?07:22
beunoLH on LP is getting worse by the minute. I'm not sure what's been going on07:22
mwhudsonbeuno: erm, tricky question to answer :)07:22
beunoah, is it better at least?07:23
mwhudsonwe should rollout a new loggerhead tomorrow with good luck and a following wind07:24
beunothat would be with tg + simpletal I assume?07:25
mwhudsonthere will probably be a general launchpad rollout early next week07:25
mwhudsonedge has been back and forth repeatedly :)07:25
mwhudsonbeuno: nope, paste07:25
beunoyeah, storm issues I hear07:25
beunomwhudson, oh, very cool. Se that will be a good way to iron out any remaining peformance issues  :)   (good for us, don't know about users)07:26
mwhudsonyeah, i wonder about trying to wedge this latest branch in07:27
mwhudsonanyway, emma is back from work so really stoppoing now07:27
beunocya tomorrow mwhudson07:27
Jc2klo07:29
lifelessi07:30
lifelesshi07:30
beunomornin' Jc2k07:30
* Jc2k yawns07:30
Jc2kbeuno: i have a feature request :)07:48
Jc2kbeuno: show the author in loggerhead somehow07:49
beunoJc2k, where specifically?07:49
Jc2kthis i'm not sure of :)07:50
Jc2ki just want to blog about bzr-svn storing the author property, and loggerhead seems like the right thing to show it off07:50
beunoJc2k, LH already shows whatever you specify in --author07:51
Jc2kwhere abouts :O07:51
* Jc2k to work07:55
beunoJc2k, it shows that instead of the committer07:55
PengIs LH supposed to use any old-style classes?07:55
beunoin changelog/revisioview/annotate07:55
Jc2kbeuno: then bzr-svn must have failed..07:56
beunoPeng, not any new ones, no  :)07:56
beunoJc2k, it's fairly new in trunk, do you have the lastest and greatest?07:56
Pengbeuno: Well, it has 4, and loggerhead/controllers/__init__.py's BufferingWriter is new.07:57
beunoJc2k, http://bazaar.launchpad.net/~loggerhead-team/loggerhead/trunk/changes07:57
beunorevno 17007:57
PengHmm, thanks to the whitespace stripping, /changes went from 82 KB to 63, and gzipped it went from like 4.65 to 4.3.07:58
beunoPeng, can you file a bug and/or provide a patch for that?  :)08:00
beuno(old-style classes)08:00
Pengbeuno: All of them or just the most recent one?08:00
beunoPeng, all of them. We do want to start cleaning up our code base08:02
lifelessok, annotate across stacking boundaries working08:04
PengCrapcrapcrapcrap08:05
Peng(Entirely OT, but I just accidentally ran a blanket "commit" instead of one file")08:06
jmlbzr uncommit?08:06
PengIt was with hg, actually.08:06
PengAnd I pounded ctrl+c and I think I broke my repo a little.08:07
lifelessheh08:07
lifelessctrl-c isn't safe?08:07
Pengbeuno: http://bzr.mattnordhoff.com/bzr/loggerhead/trivial/new-style-classes08:09
Penglifeless: I think it was.08:09
beunoPeng, you rock!  thanks  :)08:10
lifelessPeng: it was safe, or it was not safe?08:11
Penglifeless: If you don't know, when you hg commit, it commits to the live repo. When you hit Ctrl+C, it aborts the transaction and truncates the file changes. But I hit Ctrl+C a bunch of times, and got some "failed to truncate file" messages. But it exited successfully, so hopefully it tried again.08:12
PengBTW, ack rocks. "ack-grep --python 'class [^(]+:'" :)08:14
lifelessack?08:15
Penglifeless: It's like grep, only in Perl, and with colors. http://petdance.com/ack/08:16
lifelessah08:16
lifelessapt-cache show ack-grep helped me :)08:17
Peng(Eh, seems grep has colors too.)08:17
Penglifeless: Heh, right.08:17
PengI tried it out just for fun. The "--python" thing is fun. (There are arguments for other languages too.) It's a lot shorter than "find . -name '*.py'".08:18
lifelessPeng: bzr search class :P08:19
PengHeh.08:19
PengAnother nice thing is that it ignores things like *~ files and .bzr and .svn by default.08:20
spivPeng: "grep -Irn foo *" is pretty close :P08:25
* spiv -> yoga08:25
poolielifeless: ready, call me?08:26
lifelesspoolie: it rang out08:29
pooliehuh08:30
lifelesstwice now08:30
visik7I've some problem with the new bzr-svn08:39
Penggo on08:40
visik7I got this error: http://dpaste.com/58999/08:40
visik7with an active bzr-svn branch (branched with an older version of bzr-svn)08:41
lifelessJc2k: ping08:51
lifelessPeng: I feel your pain re: data corruption08:52
lifelessPeng: is it your mozilla config branch?08:52
Penglifeless: Homedir.08:55
Penglifeless: The branch has already probably had some sort of corruption for months. I think this really may have made it worse though.08:55
lifelessPeng: time to try bzr again ? :P08:55
PengPerhaps.08:56
PengI've been liking "hg commit -X" though.08:56
lifeless-X?08:56
lifelessoh, auto-everything ?08:56
Pengexclude08:57
* igc dinner08:57
PengThere's one file I do version, but it changes frequently and I don't need to record each one.08:57
PengAnyway, like I said in #mercurial, I was gonna go to sleep too. Bad things always happen when I'm about to go to sleep. :(08:57
lifelessPeng: we should have exclude for diff and commit et al08:58
* Peng goes to bed.09:02
PengGood night, lifeless.09:02
lifelessnight Peng :)09:03
visik7I got that issue on all my svn-bzr branches09:07
visik7ok it's officially dead even with a clean branch09:12
visik7svn-bzr doesn't work here anymore09:12
visik7for example:  bzr checkout http://google-gadgets-for-linux.googlecode.com/svn/trunk/ gg4l09:13
=== harryr_ is now known as HarryR
lifelessjelmer: ^09:13
visik7it doesn't recognize anymore svn branches09:17
lifelessmwhudson: why do you use sqlite2 rather than 3?09:40
=== Trudi_du_Toit is now known as garyvdm
garyvdmHi. I'm having a problem pushing to a ftp site.09:49
garyvdmI'm getting this error:09:50
garyvdmbzr: ERROR: File exists: '/.bzr': 550 /.bzr: Access is denied.09:50
jelmervisik7: that works fine here09:50
jelmervisik7: when did it break?09:51
garyvdmI've checked the .bzr does not exist. So it seems that bzr is interperating the ftp incorrectly09:51
lifelessgaryvdm: what path are you giving bzr? that leading / suggests its trying to mkdir at the root09:52
garyvdmWhat is the best way to try and fix this?09:52
goureMBee: hi, any luck with bzr-gtk ?09:52
garyvdmlifeless: yes - Command used:09:53
garyvdmC:\Inetpub\wwwroot>bzr push ftp://usr:pass@www.squarepegs.co.za/ --use-existing-dir09:53
lifelessgaryvdm: so, I suspect you actually want something like ftp://usr:pass@www.squarepegs.co.za/home/garyvdm/public_html/xxx09:53
garyvdmI want to put the branch in the root, but I guess I can put it in a sub folder.09:54
garyvdmLet me try that.09:54
lifelessgaryvdm: the root may not be what you think it is09:55
lifelessif you ftp to www.squarepegs.co.za, and do ls / - does it show you your files, or something like 'usr', 'bin', 'lib' etc09:56
garyvdmI did check that. The root is the root of the website.09:56
lifelessgaryvdm: ok, then its likely that the ftpserver has a policy stopping you making .bzr09:57
visik7jelmer: today09:57
jelmervisik7: still there?09:57
lifelessgaryvdm: try pushing to /test09:57
visik7yes, today09:57
garyvdmOk09:57
lifelessgaryvdm: if that works, ftp in and mv test/.bzr .bzr09:57
visik7jelmer: on revno: 134509:57
jelmervisik7: bzr-svn shows up in "bzr plugins" ?09:57
visik7yes09:58
jelmervisik7: have you built it?09:58
visik7yes09:58
jelmerwhat happens if you prefix the http url with "svn+" ?09:58
jelmere.g svn+http://google-gadgets-for-linux.googlecode.com/svn/trunk/09:58
visik7same problem09:59
visik7 ERROR: Not a branch: "svn+http://google-gadgets-for-linux.googlecode.com/svn/trunk09:59
jelmeranything in ~/.bzr.lo g?09:59
jelmeranything in ~/.bzr.log ?09:59
visik7yes I'll dpaste it10:00
visik7http://dpaste.com/59005/10:01
=== yacc_ is now known as yacc
mwhudsonlifeless: it's what was installed on vostok at the time i think10:03
jelmervisik7: hmm, it should be impossible to get into that situation10:03
jelmertrain leaves10:04
jelmerbye10:04
visik7jelmer: I'm a lucky  man :)10:04
lifelessmwhudson: I've already given you a patch to upgrade :)10:06
lifeless3 is faster10:06
=== prateeksaxena is now known as prtk
visik7jelmer: so am I tfu ?10:07
garyvdmlifeless: I tried that. Unfortunatly it did not work.10:08
garyvdmhttp://pastebin.com/m7f8c0cf910:09
garyvdmFrom the pastebin you can see, I did a ls to check that /test does not work10:09
garyvdmThen I tried to push to /test, and it say /test exists10:09
garyvdmThen I tried to put to /test --use-existing-dir - and it says /test does not exits.10:10
garyvdmHuh?10:10
garyvdmOk  - time to download wireshark.10:11
lifelessoh, microsoft ftp server again10:11
lifelessgarh10:11
lifelessgaryvdm: can you try:10:12
lifeless"ls /"10:12
lifelessjust for my peace of mind10:12
garyvdmok10:12
garyvdmAh - ls / gives me a compleatly different list...10:13
lifelessI thought it might10:14
lifelessdo 'pwd'10:14
garyvdm"/ftptrudi" is current directory.10:14
garyvdmok push to /ftptrudi10:14
lifelessyes10:14
garyvdmIt's working now. Thanks lifeless.10:16
lifelessnp10:17
beunolifeless, bug #242035 fixed. Half a bug to go  :)10:34
ubott2Launchpad bug 242035 in loggerhead "[search] Javascript for searching isn't included in every page" [Medium,Fix released] https://launchpad.net/bugs/24203510:34
beuno(that would be half of #242034)10:35
beunoJc2k, I didn't quite understand where we stand on the --author bit.  Are you using past revision 170?10:36
lifelessbeuno: cool10:37
poolievila, are you here by any chance?10:40
Jc2kbeuno: i have r 262 of the branch for loggerhead + bzr search10:41
lifelessJc2k: 'bzr search author'10:41
Jc2keh10:42
lifelessJc2k: it will give you an answer quickly :P10:42
beunoJc2k, ah, so you're using search. Let me integrate the latest changes into it, and I'll push that10:42
beunoJc2k, pushed revno 26710:44
beunohas many improvements10:44
Jc2kcool10:44
beunospeed amongst one of them  (from mwhudson's streaming work)10:44
Jc2kwhats the URL again? parent isnt set10:44
beunoshould show authors and such10:44
lifelesslp:~bueno/loggerhead/bzr-search_integration10:45
beunoJc2k, not that I'm hurt or anything, but you haven't added the gnome theme on it...  :p10:45
beunoI can provide a branch with trunk + search + gnome theme, if that's what you've been waiting for10:45
Jc2kthat would make be a very happy GNOME beuno10:46
poolielifeless: vf bounced due to conflicts, i'm updating them10:46
lifelesspoolie: trivial stuff?10:46
lifelessJc2k: so, bugs for gnome10:46
lifelessJc2k: I'll file them I guess as you are busy with new job :)10:46
Jc2keh, awesome. cheers.10:47
lifelessJc2k: but the list - rebase -i; an in-place-branches mode; anything else ?10:47
pooliebasically just conflicts on the get_data_stream stuff10:47
Jc2kcrap, i thought of one in bed10:47
beunoJc2k, I'll push that in a minute for ya'10:47
lifelessJc2k: thats the idea, to capture them10:47
lifelessbug 24266110:48
ubott2Launchpad bug 242661 in bzr "Cherrypick without merge needed" [Undecided,New] https://launchpad.net/bugs/24266110:48
lifelessthat guy is having a conversation with himself10:48
Jc2klifeless: the stuff that bkor filed, and cleaern urls10:48
Jc2kcleaner10:48
lifelessneeds some response / love :)10:48
lifelessbkor: loggerhead changes are all in progress I think; I'm worried about CLI stuff not getting sufficient attention10:48
james_wlifeless: hi. I've read it a couple of times, but haven't understood it yet. I thought of asking them to have another stab on the mailing list.10:49
lifelessthough loom on its own is a pretty good answer to branch lists10:49
pygihi hi10:49
lifelessif you ignore 'record, up-thread and down-thread', then you get N branches at one spot with switch between them10:49
beunoJc2k, lp:~beuno/loggerhead/gnome_theme  should make you happier10:49
Jc2kthat confused me - its changed ports!10:51
Jc2kbeuno: http://bzr-mirror.gnome.org:8080/vcs-mirror/trunk/changes10:51
lifelessjames_w: I want: a bunch of bugs, in lp, tagged gnome, that if we solve will help address the various things gnome would like10:52
lifelessjames_w: both the misguided ones, and the good ones like bkor filed on lh10:52
james_wlifeless: was that one from a GNOME person?10:52
beunoJc2k, right, I think mwhudson set it back to 808010:53
beunojavascript/css not being added correctly, that's odd...10:53
Jc2kyeah..10:53
beunoJc2k, you're running this through apache, right?10:54
beuno/static/* dir isn't being exposed10:55
Jc2kbeuno: nope, mwhudson always told me to just run the serve-branches10:55
beunoah, right, 8080, missed that10:55
Jc2kso i should run it with mod_rewrite [P] foo?10:56
beunono, should work out of the box10:56
AfCI believe the correct term when it comes to mod_rewrite is "voodoo"10:57
beunoJc2k, branch works fine here:  http://200.127.6.219:8080/changes10:57
lifelessJc2k: was which one ?10:58
Jc2klifeless: ?10:58
lifelessJc2k: sorry, mt10:58
lifelessjames_w: was which one ?10:58
james_wlifeless: I was responding to your comment that 242661 needs some love10:59
Jc2kbeuno: i just branched the url you gave and ran the serve branches script10:59
lifelessjames_w: no, I don't think its a gnomer10:59
beunoah, it's doing something weird, by serving the static dir from each branch: http://bzr-mirror.gnome.org:8080/epiphany/trunk/static/javascript/collapse.js10:59
beunoJc2k, right, it's probably our fault. Let me debug this for a bit...10:59
Jc2kcheers11:00
poolielifeless: i realize you've finished, so rst this question if you wish11:00
pooliebut, you've deleted the get_data_stream_for_search and the Fetcher that calls it11:00
pooliei'm guessing that should just be carried across in the merge?11:00
poolieand then eventually a new form of something similar needs to be written?11:01
lifelesspoolie: that was my intent yes11:01
lifelesspoolie: its what I've been saying spiv should be looking into as a priority :P11:01
beunoJc2k, can you try branching trunk and see if the same thing happens?  lp:loggerhead11:01
beunoI can't reproduce the problem locally11:04
poolielifeless: yeah i thought so :)11:04
poolieeasy to resolve11:04
Jc2kbeuno: http://bzr-mirror.gnome.org:8080/vcs-mirror/trunk/changes11:04
beunoJc2k, ok, so it's something from trunk11:05
Jc2kare you using the serve-branches.py script? (looks like your using start-logerhead?_11:05
beunoJc2k, I'm not: http://200.127.6.219:8080/11:06
beunoor am  :)  (using serve-branches.py)11:06
Jc2klucky git11:06
beunoI don't understand why it misplaces the /static/ dir...11:07
lifelesspoolie: spiv may be unhappy at the recent optimisations being disabled :P11:08
beunoJc2k, this is a linux box it's running??11:08
beunopython 2.4 or 2.5?11:10
pooliei'll try to help him get them back11:11
lifelessbeuno: you know you don't need to call load_plugins to load a plugin :)11:11
lifelessbeuno: you can just 'import bzrlib.plugins.search'11:11
lifelessbeuno: load_plugins loads /all/ plugins11:11
beunolifeless, I didn't  :)11:11
Jc2kbeuno: debian etch, python 2.411:11
beunoJc2k, it works with 2.4 here too...  :/11:12
beunomwhudson, you're not still around and bored, are you/11:12
poolieok i'm going to sign off11:12
beunolifeless, thanks. Pushed revno 26811:15
beunoJc2k, I'm heading to the office, but I'll try and get to it in a while. It shouldn't be placing /static/ dir on each branch's dir11:15
beunoit has something to do with mwhudson's voodoo to generate that with serve-branches  :)11:16
lifelessbeuno: http://bazaar.launchpad.net/~lifeless/loggerhead/search11:28
thekornhi, I'm using the editor feature of bzr commit (running bzr commit opens my editor for me and let me write down my message)11:47
poolielifeless: it landed11:47
thekornis it possible to predefine a a text for the part above the ---bar---11:48
thekornso I have like a default message-body for all my commit-messages11:49
james_whi thekorn11:51
thekornhi james_w!11:52
james_wit's possible in bzrlib, but I'm not sure that there is any way to do it.11:52
lifelesspoolie: woo, the eagle is in!11:55
lifelessthekorn: as in a template ?11:55
thekornjames_w, ok, I just found the related functions, they are having a lots "TODO"s in __doc__, too bad11:56
thekornlifeless, best thing would be if it could list all my changed files there11:56
lifelessthekorn: well, TODO's just reflect bug plans :)11:56
thekornbecause I'm always starting my messages with the files I changed11:57
lifelessinteresting11:57
lifelessuhm, there might be a plugin already11:57
lifelesswhat I do is use --show-diff11:57
thekornand right now I'm copieing the part under the ---bar---11:57
lifelessbecause I copy various bits of details11:57
thekornand comment on each item11:57
lifelessthekorn: could you file a bug? It seems to me doing this would be a nice thing11:58
thekornok, will do11:58
thekornthanks lifeless, james_w11:58
lifelessthekorn: after the bug is filed, if you want to work up a plugin or patch, I'd be happy to make suggestions12:00
thekornlifeless, are there some docs on howto write a plugin somewhere12:01
vilapoolie: just arrived, but launch break in a few minutes12:01
lifelessthekorn: there are some; but not enough :)12:01
lifelessthekorn: docs/en/developers/plugins.txt I think is one spot12:01
lifelessthekorn: there are using bzrlib thigns on the wiki too12:02
lifelessthekorn: but for this, I think a patch to the core is entirely suitable12:02
vilapoolie: I just read you were about to sign-off though, so maybe in 10/12 hours ;-)12:02
thekornlifeless, ok, cool, I will have a look at the general structure of bzr and bzrlib and try to understand how such a patch could look like12:06
lifelessthekorn: In my head is something like a 'template' setting in the config for commits12:07
james_wthekorn: I added start_message to get_commit_message for doing exactly this12:07
lifelesse.g. %s would mean 'include status', %d would mean 'include diff' etc12:07
lifelessthekorn: but we can start with just what you need12:09
thekornok, cool, I will file a bugreport, think about it a bit, and come here again to discuss this further,12:11
thekornor directly on the bugreport, of course12:11
lifelesssure12:13
lifelessI'll see it if you discuss there too12:13
beunolifeless, cool, thanks. Mergeing now.12:17
lifelessbeuno: in my testing it makes a branch with no index work (but get no hits)12:18
beunolifeless, that's exactly the behaviour I want, so it's perfect. I have been puttin it off, so it's great12:19
lifelessbeuno: it should also do the same if the plugin is missing, but I didn't actually test that12:19
pypasbonjour a tous, Il y a t il des francophone sur le channel? (cause my english is too bad :(12:20
lifelessbeuno: *I* would like it to say what is wrong if there is no index/no bzr-search, but thats not something I know the best way to do offhand12:20
lifelessvila: ^ pypas12:20
beunolifeless, I'll test that before pushin. It should return no results because it can search other things (revnos, dates)12:20
pypaspetite question : puis-je supprimer un repertoire, commiter et au besoin faire un revert pour recreer les fichiers supprimes?12:21
vilapypas: oui12:22
pypasj'ai essayer la suppression via bzr delete : pas fonctionne puis en supprimant via mon explorateur et pareil, marche pas12:23
lifelessbeuno: hmm, bzr-search will be growing such searches too; in future perhaps I can change your mind :)12:23
vilaplus precisemment ?12:23
pypasla supression fonctionne mais c'est le revert qui ne recreer pas mes fichiers12:23
beunolifeless, sure, my mind is very changeable12:25
vilala suppression par 'bzr rm' ?12:25
vilapypas: que dit 'bzr st' avant et apres la suppression ?12:26
vilapypas: juste pour etre sur, on parle bien de supprimer des fichiers et/ou des repertoires qui sont deja connus de bzr (i.e. ajoutes et commites)12:27
pypasils sont deja connu et j'ai fait un bzr remove path/vers/mon/rep12:27
pypasbzr delete12:27
beunolifeless, works fine without bzr-search installed. Pushed.12:28
vila'bzr delete' c'est quoi ? Quelle version de bzr utilises-tu (bzr version) ?12:28
pypas1.512:29
vilabzr delete12:30
vilabzr: ERROR: unknown command "delete"12:30
pypastu es sous ng?12:30
pypasmoi pas12:30
pypasau temps pour moi, c'ets un remove que j'ai fait12:30
vilapypas: ouch, tu parles de 'baz' donc, pas de 'bzr'12:30
vilapypas: ghaa, 'bzr version' dis quoi ?12:31
pypas1.512:31
pypasmerci de ton aide vila mais je dois quitter, ma progeniture se reclame. je repasserais tantot12:31
pypasmerci encore12:32
vilapypas: pareil, a plus12:32
Sub_ZeroHey all. I had a (hopefully) easy question about bazaar. Essentially, I want to alias 'bzr reset' to 'bzr revert' and 'bzr clean-tree', but I don't believe bzr aliases support multiple commands. I'm hoping there is an easy way to do this.12:35
beunoSub_Zero, I suppose you could do a bash alias instead12:36
KinnisonAre bzr aliases core?12:36
lifelessbeuno: what else needs going to make the search branch mergable?12:36
KinnisonSub_Zero: I'd be tempted to write a plugin to do it12:36
KinnisonSub_Zero: given the two commands you want to combine take differing arguments12:36
=== kiko__ is now known as kiko-afk
Sub_Zerobeuno: Yeah, that does work. But I was hoping there would be a little more "integrated" way to do it.12:37
beunolifeless, off the top of my head, just the remaining javascript bit, and looking into what I can/should use of the new streaming feature12:37
beunoI suppose we're almost there  :)12:37
Sub_ZeroKinnison: I think the plugin is the way to go, but I don't know any phython :(12:37
beunoI do want to add some context to the search results, but I don't think it's worth waiting for that12:37
KinnisonSub_Zero: aah12:38
KinnisonSub_Zero: always a bit of an issue, given my other suggestion was going to be to modify the alias plugin :-)12:38
lifelessbeuno: sounds like 'merge it now' to me :)12:38
KinnisonDo it!12:39
lifelessbeuno: because the streaming thing can be done later; and the remaining javascript bit is not worse that the old search facility12:39
beunolifeless, well, one thing we do need to add, is for the <div> not to show if no results are returned, or search is not enabled12:40
Sub_ZeroKinnison: I've been meaning to sit down and get my feet wet in Python, but being mostly ignorant how hard would it be to write a plugin to execute those two commands?12:41
spivlifeless, poolie: well done!12:41
KinnisonSub_Zero: Not *certain* but I wrote commands for bzr reasonably easily, so I'd guess not too hard12:41
beunolifeless, that's the part that's worst then now. If my day isn't too hectic, I can probably get that done before mwhudson wakes up and can review it12:41
lifelessbeuno: I try to split 'need to' from 'want to'12:43
lifelessbeuno: if its not worse than the old code in any regard, I look for reasons not to merge, rather than reasons to merge :)12:44
lifelessspiv: thanks12:44
lifelessspiv: no excuses on looking at the new api now :)12:44
spivlifeless: :)12:44
spivI've *looked* at it...12:44
spivI just need to use it :)12:44
beunolifeless, agreed. I'll make the div behave sanely if bzr-search isn't present or no results are returned, and put up a merge request12:45
lifelessspiv: I will be in hornsby at 7am tomorrow for a physio visit12:46
beunoah, thought of one more thing. It doesn't search revnos now. That should be fixed too.12:46
lifelessspiv: that will probably finish around 8am; If you wanted to hack together I'm happy to stay around in hornsby for a few hours12:47
lifelessbeuno: as in '52' ?12:47
beunolifeless, yeap. Which is the only thing that currently works properly  :)12:47
spivlifeless: I'm tempted, but my flat looks embarrasingly like a bomb site at the moment.12:47
spiv(Even more than usual)12:47
lifelessspiv: so you've cloned my house?12:47
spivWorse :)12:48
lifelessspiv: we could sit at $pie_shop, drink caffeine and eat pie12:48
lifelessspiv: or I can just head home during rush hours12:48
spivThere's no decent pie shop anymore, but I'm sure we can manage something.12:48
lifelessspiv: how about - I give you a ring around 8:30, that should be close enough to civilised given the 9am stand-up; and I'll be esconced somewhere westfieldy12:49
lifelessspiv: and we can discuss go/nogo/details then ?12:49
spivlifeless: works for me12:51
lifelesskk will do then12:51
poolievila, i am signing off now, will mail you or try to catch you tomorrow12:59
AfCspiv, lifeless: it's too bad you're talking about Hornsby. I've been meaning to have you two over for lunch but with Robert fleeing the country I guess we're out of time. Andrew, the invitation is open.12:59
spivAfC: we should definitely arrange something on your side of the harbour one day13:05
vilapoolie: ok, no problem (just coming back from launch :)13:08
vilabeuno: ping13:08
beunovila, pong13:09
beunoI owe you a reply13:09
beunoI'm way behind on replies  :(13:09
vilabeuno: did you give a try to bzr-upload with the chmod bit handling ? Are you happy with it or do we need more ?13:10
vilabeuno: given that ftp doesn't work yet13:10
beunovila, I haven't gotten around to testing it yet. I'll stick it into my main server today and see if anyone complains  :p13:10
beuno(and, well, eventually do real testing)13:11
beunopast few days have been very crazy13:11
vilabeuno: ok, I have a patch for bzrlib to make ftp support chmod, I still need to test it against a real server13:11
vilabeuno: ok, no problem, I was unsure about taking your last reply as valid for my mail bombing or if I should be waiting for mor replies ;)13:12
beunovila, if you need an ftp/sftp server to test against, let me know, I'll set up an account for you on one of my webservers13:12
vilabeuno: thanks for the offer, but I'm close to have one test server available using te local-test-server plugin so I will quickly be in position to test against any ftp server I can install on Ubuntu13:13
lifelessAfC: I have another week; and would like to do something13:21
lifelessAfC: I've been unwell recently; I'm starting to feel human again13:22
AfClifeless: sooner rather than later would work well, actually13:22
lifelessAfC: are you GUADECing?13:22
AfClifeless: no13:22
=== weigon__ is now known as weigon
Sigmahi. I've got a little problem. "bzr push" says bzr: ERROR: These branches have diverged.  Try using "merge" and then "push".13:59
Sigmaon the other and, "bzr merge" says "Nothing to do." :-)13:59
Sigmas/and/hand/13:59
Sigmaany idea is welcome :-p14:00
beunoSigma, maybe your push location is different than your merge location?14:02
spivSigma: I think bueno is right.  Check the "bzr info" output.14:04
Sigmahmm actually they are, but, the source of merge should be up-to-date with my push location. let me check :)14:05
SigmaI'm merging from launchpad/http and pushing to launchpad/sftp14:06
beunoSigma, try "bzr missing"14:06
beunoand see what that says14:07
Sigmait says I have 1 extra revision14:07
beunoSigma, maybe try pushing and specifying the URL. It may be pushing somewhere else14:08
pypas|/commands|14:14
SigmaI've got this error when merging : bzr: ERROR: Revision {yann.hodique@gmail.com-20080601233200-8sufw6rintulemn6} not present in "KnitVersionedFile(sftp://yann-hodique@bazaar.launchpad.net/%7Eyann-hodique/%2Bjunk/dotemacs/.bzr/repository/knits/f4/195%408a708873-67e9-0310-be3a-b2333ca284a8%253atrunk%253alib%25252%2546icomplete%25252%2542.el)".14:17
beunoah, that doesn't look good14:17
beunoyou're using knits for starters. What version of bzr are you using?14:18
Sigma1.5, but this message relates to the storage in launchpad, no ?14:18
beunoyeah14:18
beunoit may be bug #20515614:19
ubottuLaunchpad bug 205156 in bzr "KnitRepository.insert_data_stream() copies data in improper order" [Critical,Triaged] https://launchpad.net/bugs/20515614:19
Sigmahmm14:19
beunohttps://code.edge.launchpad.net/~yann-hodique/+junk/dotemacs/14:19
beunoSigma, you have the full repository locally?14:20
beunoyou can probably to push --overwrite to fix that14:20
beunoand, I'd recommend upgrading the storage format with (but after we fix this)14:21
=== avc_lurk is now known as acuster
Sigmayes, I can overwrite, I'll try that14:25
beunoSigma, that sould fix it, and, after that, I'd recommend doing:  bzr upgrade && bzr reconcile14:25
beunoboth locally and remotely14:25
beuno(it may take a while to do it on LP)14:25
Sigmabut locally I'm already at the latest format14:25
Sigmaah ok14:26
beunoand, it's *much* faster if you use bzr+ssh instead of sftp14:26
beunoSigma, if you branched off LP, it probably brought in knits format14:26
SigmaStandalone tree (format: pack-0.92)14:26
beunocool14:27
beunothen, push --overwrite14:27
beunoand upgrade afterwards14:27
beunoshouldn't happen every again with packs  :)14:27
Sigmaok thanks14:28
Sigmabtw, when I re-branch from LP, I get Standalone tree (format: dirstate)14:31
poolieguilhem, https://answers.launchpad.net/bzr/+question/3730814:32
poolieguilhembi: ^^14:32
beunoSigma, right. You must of upgraded at some point, or used a shared repository. Upgrade in LP and it should all go away14:33
pooliethis is the person -> https://edge.launchpad.net/~xuekun-hu14:33
Sigmabeuno: how am I supposed to upgrade on LP ? a simple "bzr upgrade bzr+ssh://yann-hodique@bazaar.launchpad.net/~yann-hodique/+junk/dotemacs/" doesn't seem to do the job14:35
beunoSigma, ironically, for upgrades you need sftp14:35
SigmaI see :)14:35
beunobut, for the rest, bzr+ssh is much faster14:35
beunomorning jam14:36
jam'morning beuno14:36
LeoNerdI find it's a tough call sometimes between sftp and bzr+ssh14:36
LeoNerdAt home, I have a fast 100Mbit network to a slow server... sftp becomes faster, even though it has mmore network overhead, just because it's lighter on server CPU load.14:37
Sigmasince it's taking ages, I suppose it's working :) thanks a lot14:37
beunoSigma, you're welcome14:38
poolieSigma: do you get an error over ssh?14:39
guilhembijam: hi! Posted some test results of your latest bzr branch; and also: ha_ndbcluster.cc "false conflicts" is the most burning issue I believe14:39
poolieif you're going from knits to packs it will take a while14:39
pooliestatik: can we talk briefly?14:40
Sigmapoolie: bzr+ssh gives me "bzr: ERROR: The branch format Bazaar-NG meta directory, format 1 is already at the most recent format." which is quite confusing :)14:41
pooliehm ok14:41
pooliecould you file a bug please?14:41
Sigmayep, will do14:41
GaryvdMHi. I'm having a problem branching a branch. I'm getting this error:14:49
GaryvdMC:\Inetpub\wwwroot\squarepegs>bzr pull http://www.squarepegs.co.za/14:49
GaryvdMbzr: ERROR: No such file: 'http://www.squarepegs.co.za/.bzr/repository/indices/e07e8982d90a74ddd63781f8e3fb20a7.rix'14:49
GaryvdMThe branch was pushed with bzr 1.5 , and I'm an trying to branch it with a copy of bzr.dev14:51
Sigmahmm, the upgrade finally failed :/14:51
Odd_BlokeGaryvdM: Can you check if the file actually exists via non-HTTP means?14:52
GaryvdMOk14:53
beunoSigma, with what error?14:53
Sigmasame as before : bzr: ERROR: Revision {yann.hodique@gmail.com-20080601233200-8sufw6rintulemn6} not present in "KnitVersionedFile(sftp://yann-hodique@bazaar.launchpad.net/%7Eyann-hodique/%2Bjunk/dotemacs/.bzr/repository.backup/knits/f4/195%408a708873-67e9-0310-be3a-b2333ca284a8%253atrunk%253alib%25252%2546icomplete%25252%2542.el)".14:53
beunoSigma, and you already did push --overwrite?14:54
Sigmayes14:54
beunohmr14:54
beunojam, any idea on how to fix that  ^14:54
beunoit looks like bug #20515614:55
ubottuLaunchpad bug 205156 in bzr "KnitRepository.insert_data_stream() copies data in improper order" [Critical,Triaged] https://launchpad.net/bugs/20515614:55
GaryvdMOdd_Bloke: hmmm - it's working via ftp. But not accessible through http. I think my host has changed something.14:56
GaryvdMThanks14:56
Odd_BlokeGaryvdM: Yeah, that's probably a permissions issue.14:57
jambeuno, Sigma: Is this happening during a bzr upgrade? (Since otherwise I don't know why it would trigger in "repository.backup".14:58
Sigmabeuno: btw, it looks like my LP repository is now broken : Branched 0 revision(s). :/14:58
Sigmajam: yep14:58
jamI *believe* the appropriate answer is that you need to upgrade with <= 1.5 (maybe 1.4) and then do "bzr reconcile" with that version14:58
jamand then it will work with bzr.dev14:58
jamThe old fetch code could handle missing data14:58
jamthe new stuff can't14:59
jamso if you have missing stuff, you need to upgrade with the old code first14:59
jamand reconcile to fill in appropriately.14:59
jamAt least, that would be my 1-min recommendation.14:59
Sigmajam: sorry, I was not able to test it. the LP branch was not usable anymore after broken upgrade. I had to delete/recreate it. Thanks anyway :)15:09
jamSigma: well, you probably just needed to mv .bzr/repository.backup .bzr/repository, but as long as you are back to functioning15:09
Sigmayep. it looks like there is room for a feature in LP to upgrade formats via the web interface15:11
beunoyes, and probably a warning when the repo is in an old format15:13
LarstiQbeuno: do consider older clients15:19
beunoLarstiQ, well, it's just a warning, not a death threat  :)15:21
beunoit seems the bug requesting it was already filed as #17903515:21
beunomost users don't even know they're using knits, so informing them may push more upgrades15:22
beuno(in fact, Loggerhead was using knits until recently)15:23
Verterokmoin15:26
beunohowdy Verterok15:27
Verterokbeuno: morinin'15:27
* Verterok still sleepy15:28
beunoVerterok, I woke up at 3am, so I'm...  odd15:28
beunowent to sleep at 5pm, so I guess it's ok, but still, odd  :)15:29
Verterokbeuno: good timing to work with the australian folks ;)15:30
beunoactually, british folks, but yes, that worked out good too15:31
Verterokbeuno: right, (remember I'm still sleepy :-D)15:33
beunohahaha15:33
abentleyVerterok: I don't know if you saw, but I got the main BB instance onto Postgres this morning.15:33
beunoabentley, it seems much faster to me now. Especially when loading the merge requests15:34
Verterokabentley:  reading the mail ATM. yay!! :D15:34
abentleybeuno: I'm not noticing a great improvement, but for me it's about thread-safety and easier schema migration.15:35
beunoright, having it not hang frequently will be good15:36
abentleyVerterok: The gotcha I encountered was that the sequences for the primary keys weren't set properly.15:36
abentleySo it would try to re-use ids that had already been used.15:37
Verterokabentley: I was about to asking if you find glitches with the scripts15:37
abentleyVerterok: The main thing was just figuring out all the stuff outside the scripts-- creating the user, creating the db, creating the tables.15:38
abentleyAnd some server configuration stuff too.15:38
nanderssonVerterok: I'm just curious. Is your bzreclipse-plugin ready for Eclipse 3.4?15:39
Verterokabentley: I see, about the ids, I'll search if I can force the reuse using sqlalchemy15:39
Verterokabentley: regarding the configuration part, I can extend the README and add some guidelines about server configs, etc15:40
matkorwas fix "division by zero" fix commited to bzr-gtk trunk ? I got such impression but still having problem with comiting / updating ...15:40
abentleyVerterok: Also, you didn't do pkg_resources.require, so it didn't find the right versions of some packages.15:40
abentleyVerterok: I've merged your changes into trunk, and included written a script that does most of it.15:41
abentleyThe other glitch was that I had one listing that displayed items in database-insertion-order.15:42
abentleyAnd suddenly, that order changed.15:43
Verterokabentley: ups, I'll start fixing the first issues15:43
Verterokabout the ordering, I don't quite fully understand15:43
Verteroknandersson: it should work15:44
Verteroknandersson: I didn't test it, but it *should* work :)15:44
nanderssonVerterok: Thumbs up! I'm looking forward to try it out. Excellent job :)15:46
abentleyVerterok: Instead of sorting by date, I sorted by database-insertion-order.15:50
abentleyBut in the migrated version, database insertion order doesn't match the original, and doesn't correlate with date.15:51
abentleySo I changed it to sort by date.15:51
Verterokabentley: ah, ok15:51
nelsonDoes Bazaar really find lost socks?  Can it find lost gloves, too?15:53
Verterokabentley: I'll keep working on my branch to fix those issues, I'll send you a merge request when I'm done15:56
=== kiko-afk is now known as kiko-phone
abentleyVerterok: I suggest merging from trunk, since I did tweak a few things.15:56
Verterokabentley: ok, I'll :)15:56
nelsonDo CVS ''tags'' become Bazaar ''branches''  in principle?15:57
guilhembijam: hi! Don't know if this reached you: I posted some test results of your latest bzr branch; and also: ha_ndbcluster.cc "false conflicts" is the most burning issue I believe16:08
jamguilhembi: yeah, I saw that, are you done for the night?16:08
guilhembijam: ahah yes, I woke up a while ago :)16:09
=== ubott2 is now known as ubottu
jamguilhembi: yeah, timezones can be a pain. Anyway, hopefully I'll have something you'll like when you wake up.16:09
jamI can't guarantee that the false conflicts are actually false16:10
guilhembijam: if they are correct (which would be a pain), we'll need super-detailed explanations:16:14
guilhembi"this revision id changed this line from X to Y, and that revision id changed X to Z, and A was merged into B", etc.16:14
guilhembiOtherwise people will just do the gannotate analysis that I do and not understand why bzr conflicts.16:15
guilhembiand complain it's a bzr bug, and the sky will fall down or almost :)16:15
guilhembiThat is, most people at MySQL are on the line of: "if it was already merged I should not see it again".16:16
jamguilhembi: well, we might need to add a "--ignore-the-fact-that-people-actually-disagreed-here" flag for you16:20
guilhembi:)))16:21
guilhembijam: of course, if you can educate us, it's valuable. We're just users of RCS software, we can learn.16:22
guilhembibbl.16:22
mkanatIs there any way to see the actual commits made against this branch that weren't against an ancestor?16:23
mkanatOr even bundle them (that would be ideal)?16:23
mkanatHey, that's great about MySQL! :-)16:24
jammkanat: "bzr send ../ancestor" should create a bundle against that ancestor16:25
jam"bzr diff -r ancestor:../branch"16:25
jamor16:25
jambzr missing?16:25
mkanatjam: I'll try send.16:26
mkanatI'm porting a bunch of customizations from one branch to another, and I'd like to do them as their own commits.16:26
jammkanat: you should be able to use "-o" if you want to put the output in a file "-o-" puts it to stndout16:26
jammkanat: "bzr merge ../other/branch -r X..Y; bzr revert --forget-merges; bzr commit ?"16:27
mkanatjam: The customizations aren't a sequential series of commits.16:28
mkanatjam: Send seems to do it. :-)16:28
jammkanat: hence the 'x..y'16:28
jambut whatever works for you16:28
mkanatjam: Are those a literal X and Y?16:30
jammkanat: no, numbers16:31
mkanatThat's what I figured.16:31
mkanatYeah, send is easier.16:31
jamso you can select what patches you want included16:31
asabilanyone ever took a look at accurev UI for cherry picking and merging changesets from a branch to another ?16:34
asabilI think it would be really neat to have the same kind of tool in bzr-gtk16:34
beunoasabil, would you happen to have screenshots of that?  :)16:34
asabil1 minute16:35
asabillet me find it again16:35
mkanatjam: Yeah, that makes sense.16:35
asabilbeuno: http://www.accurev.com/images/screenshots/4.6/streambrowser.png16:36
asabilbasically you can drag and drop stuff :)16:36
beunoasabil, ah, so you would drop revisions into another branch?16:38
asabilbeuno: that's what I think can be done for bzr16:39
beunoasabil, could you file a detailed bug for it?  Sounds like a good idea, and I'd hate to loose it16:40
asabilbeuno: if you don't mind flash: http://www.accurev.com/virtualbooth/2min-demo/2min-demo.html16:40
asabilbeuno: I will try to do that later16:40
beunoasabil, thanks. That really looks very nice16:42
asabil:)16:43
sabdflseems we've regressed on status performance16:58
jamguilhembi: if you are still around, could you check which bzr you used to  do 'gannotate'?17:04
jamIf you used "bzr.dev" can you try my custom bzr? It annotates slightly differently and *might* provide a different insight17:04
quicksilvervila: ping?17:17
quicksilveranyone uses dvc/emacs with bzr?17:17
vilaquicksilver: pong17:18
quicksilvervila: you ever use emerge to resolve conflicts?17:19
quicksilverI have before.17:19
quicksilverI'm sure there was a way to run it on a dvc-conflict17:19
quicksilverbtu I can't find it now17:19
vilaI use smerge, it's triggered by just opening a file which contains conflict markers17:19
quicksilverah yes17:20
quicksilversmerge-ediff will launch emerge :)17:20
vilaonce the conflicts are resolved, don't forget M-x dvc-resolved17:20
* quicksilver nods17:20
vilaquicksilver: yup, but I find it less clear now that I'm used to read diffs... go figure17:20
quicksilverI'm happy reading diffs for simple stuff17:21
quicksilverfor some complex conflicts a side-by-side view is nice17:21
vilaYup,  but I rarely encounter really complex ones... In the worst cases, I'm happy to hack the most close version at hand17:22
vila.. without using two/three buffers screen estate :)17:23
=== kiko__ is now known as kiko
gourvila, quicksilver: so DVC is useful with bzr?17:25
vilagour: sure17:25
* vila thinks I *really* should update the wiki about my usage :-/17:26
vilagour: the most useful command is: dvc-diff17:27
gourit would be nice17:27
gourDVC docs is *cough* a bit...17:27
vilait presents you a buffer containing, roughly, the output of 'bzr st' and 'bzr diff'17:27
vilafrom there, on any line, doing C-c C-c jumps to the modified line in the file itself17:28
vilaso, hack, hack, hack, where am I: dvc-diff, Oh I see, let's go back to that part, hack hack17:28
gour:-)17:29
vilasince my workflow includes reviewing before commit, it just flows naturally and allows me to fix details with just one keystroke17:29
datohm, that's indeed nice17:30
jamvila: well, technically 2 keystrokes17:30
jamUnless your C-c C-c is different from mine :)17:30
gourcool, cool. i used to use darcsum when working with darcs 'cause DVC support for it is not the best. now, i believe DVC is tool-of-choice for emacs & bzr17:31
vilajam: :-) I tend to call any emacs command shortcut a keystroke, even if I should type 3 our 4 chrods :)17:31
vilachords ?17:31
jammost likely chords17:32
jamchrod sounds like a unix command17:32
vilaEscape Meta Alternate Control Shift ftw :)17:32
vilayou mean chroad which is a well know alias for bzr branch17:32
vilas/know/known/ damn typos ruining jokes !17:33
datoheh, chroad17:33
quicksilveryes, DVC is very useful17:34
quicksilverC-x V L and C-x V = and C-x V c ftw!17:34
quicksilverwhat does "M*" mean17:35
quicksilverin the output of update/pull ?17:35
vilamodified and x bit modified ?17:35
vilaquicksilver: wow, C-x V L .... never used that one :) I guess I've been bzr viz infected :)17:37
quicksilverC-x V L is annoying because it's the abbreviated log17:39
quicksilverI never want to see the abbreviated log17:39
quicksilvermerge messages matter17:39
quicksilverbut it's useful because you can hit "=" on any revision17:39
quicksilverand see the local diff17:39
=== kiko is now known as kiko-fud
vilacan you limit it somehow ? I tried C-1 C-2 C-x  V L but it still display the whole log17:40
quicksilverif you can't I don't know how to :)17:40
vilaquicksilver: yeah, '=' is double-click in bzr viz17:40
vilabut I think there is a plan to display it in the same window with a single click17:40
beunohow do I specify a different port for bzr+ssh?17:59
datobzr+ssh://host:port/path does not work?17:59
beunodato, it does, thanks   :)18:00
dato.ssh/config is also handy for that18:00
datonp18:00
bobesponjahi18:21
bobesponjais there a ruby lib to interface with bzr?18:21
jelmerI think somebody was working on one18:22
LeoNerdbzrlib is in python, but maybe ruby can use a simimlar trick to perl, and embed a python 'terp?18:22
LeoNerdI've been playing with using bzrlib from perl using Inline::Python lately.. it's quite fun :)18:22
beunobobesponja, or, you can use the xmloutput plugin to get data from bzr18:22
bobesponjaok, thanks for the info18:23
bobesponjaLeoNerd: what's a python 'terp? :)18:24
LeoNerd"interpreter" for people like me who often mistype long words18:24
bobesponjaok18:25
LeoNerdInline::Python is a perl module that pulls in libpython, and marshalls data between perl and python representations..18:26
fullermdHm.  Does that actually work well?18:26
LeoNerdThis makes it very easy to use python libraries from perl. Something similar may exist for ruby18:26
LeoNerdIsh...18:26
LeoNerdOne thing it doesn't do ((yet)) is object attributes.18:26
LeoNerdWhich is kinda essential to using bzrlib, since I notice various things use it18:26
LeoNerdSo where python could just use   revision.repository   I have to   getattr(revision, 'repository')18:27
james_wsomeone's adopted bazaar in Debian, so it looks like it's not going to be removed from lenny.18:27
LeoNerdThat being the 'baz' implementation of TLA, yes..?18:28
beunojames_w, and the FTBS?18:28
james_wfixed apparently18:28
james_wLeoNerd: yup18:28
beunojames_w, so now we have to pursuade that fellow to do the transition...18:28
james_wah to "baz" package name?18:29
beunoyes18:29
datojames_w: who adopted it?18:29
beunoand make that trickle down to Intrepid18:29
james_wbeuno: it's gone in Ubuntu.18:30
beunojames_w, I know, but lifeless wanted it so baz -> bzr repos could be migrated18:30
beunoAFAIK, removing it was a temporary thing18:30
james_wbeuno: the failure we saw was apparently due to "dash". A lot easier than we thought, but there were apparently other problems.18:30
beunojames_w, really?  Argh, we spent quite a while on it...18:31
beunoit would be cool to be able to do the transition18:32
james_wI'm going to send a mail to the bug report now.18:33
beunothanks  :)18:33
=== prateeksaxena is now known as prtk
bobesponjahttp://rubyforge.org/projects/bzrwrapper/18:35
bobesponja0.1  August 24, 200718:35
=== kiko-fud is now known as kiko-phone
dpmI've published a branch of an upstream project hosted at launchpad on my personal Launchpad page. The way I've been working is doing commits on my working copy and then pushing them to my LP branch. Now upstream has merged my changes and has made some new ones. What's the correct way to get the latest upstream changes now? 'bzr update' fetches the changes from my personal LP branch, not upstream. I've been using git in the past, which stores a refer19:11
dpmence to the remote repo which was initially cloned. Is there something similar on bzr, or do I have to explicitly give the upstream branch as in 'bzr merge lp:upstream'?19:11
james_wdpm: yup, but then you will only have to give the  url to "merge" once19:12
james_wit only stores a single URL though, so if you regularly merge from two different places it's a bit annoying.19:13
dpmok, I understand. Thanks19:13
jamabentley: a couple questions if you have time? I seem to be getting "foo.OTHER" rather than "conflict adding foo, moving existing foo => foo.moved". I'm probably doing something wrong, but if you have a hint as to what?20:01
abentleyjam: Give me a few minutes.20:01
jamnp20:02
jjcroftivHello - I am new to bazaar and have been using it for about a week.  So now I have a local repository with a number of revisions, and I a want to move this to a central server.  Can I simply tar up the whole repository, move it to the server, and continue to use it from there, or is there some other action required? TIA20:02
beunojjcroftiv, tar and movinf is perfectly acceptable20:05
beunoyou can push it to the remote location too20:05
jjcroftivbueno, thanks for the response:)20:07
abentleyjam: back.  I was implementing path_content_summary on TT, and it's not as simple as you might think.20:19
abentleyWe seem to have got switched around.  I work on the APIs you added to Tree, and you work on merge.20:20
jam:)20:20
jamSo I *think* what is happening is that the same file/directory got added by two different branches20:21
jamso when you merge them together, you get a path conflict20:21
jamand one of them gets .moved out of the way20:21
jamabentley: I'm trying to figure out why I would be getting a bath of "foo.OTHER" instead of a conflict and "foo.moved".20:22
jamWould you get that if it looked like a rename instead of an add?20:22
abentleyare both foo and foo.OTHER versioned?20:23
jamabentley: after the merge, yes20:23
jam+N  .bzr-mysql.OTHER/20:23
jam+N  .bzr-mysql.OTHER/default.conf.OTHER20:23
jam^- my code20:24
jamv- bzr.dev20:24
jam+N  .bzr-mysql/20:24
jam+N  .bzr-mysql/default.conf20:24
jamR   .bzr-mysql/ => .bzr-mysql.moved/20:24
abentleyOh.  I thought you were talking about bzr.dev the whole time.20:24
abentleyusing OTHER suggests it's happening in the merge code, not the filesystem conflict resolution.20:26
jamabentley: oh, and I'm cheating a bit about the criss-cross merge stuff. http://paste.ubuntu.com/22937/20:27
abentleyIf you have two files with the same name in your transform, and you do the conflict resolution, you'll get the .merged.20:27
jamabentley: you mean .moved20:27
jamBut why would I be getting .OTHER ?20:27
abentleyYes.20:27
abentleyNot sure yet.20:28
jamI believe some part of my code is wrong (earlier I was running into "no final name for XXX" a bit)20:28
jamsome of that turned out to be using something other than None to represent not there.20:28
jamsome of it was getting the ordering of from => to wrong in iter changes20:28
abentleyso I think foo.OTHER can be created if THIS deletes foo and OTHER creates it.20:31
abentleyNo, if OTHER keeps it.20:31
jamabentley: OTHER merges THIS and resolves it as a keep?20:31
abentleyIs this being listed as a contents conflict?20:31
jamabentley: yes contents conflict20:31
jamNow, it may be because of base selection20:32
jamwhy I'm getting .moved rather than .OTHER20:32
jamum, vice versa20:32
jamI'm now getting .OTHER because of a closer base20:32
jamoh... it could also be because of what I posted about the "cheating" and how I'm handling None in the bases.20:33
abentleyYeah, if BASE has the file, THIS doesn't, and OTHER changed it, then you might get foo.OTHER.20:33
abentleyThen if THIS added a new foo, you'd get foo and foo.OTHER.20:33
abentleyjam: The logic is in merge_contents@77820:34
jamabentley: the "contents_conflict()" section?20:35
jamabentley: ahh, I think I'm also screwing with it in a different way20:35
jamYou have:20:35
abentleyjam well, that doesn't decide to emit the conflict.20:35
abentleyIt just implements it.20:36
jamif this_pair == base_pair: elif this_pair == 'file' and other_pair[0]' == 'file'. else contents_conflict()20:36
abentleyjam, right.20:36
jamand I'm adding if not self._is_criss_cross  and this_pair == base_pair20:36
jamthough I don't think that specifically would be the problem20:36
abentleyIt sounds like this may not be a bug.20:37
jamabentley: maybe, though it doesn't help the mysql guys...20:37
jamthough guilhem may not realize that the alternative was to create a .moved20:38
abentleyIf you've got a non-None base.20:38
guilhembijam: you want me to retry annotate or gannotate? I could do diff between  "bzr annotate sql/ha_ndbcluster.cc" with bzr.dev and your bzr?20:38
jamguilhembi: that would probably be interesting, (welcome back, btw)20:38
jamit can be on the same merge20:38
jamjust do the annotate between the two20:38
* guilhembi starts that; results in 2*5 minutes20:38
jamguilhembi: I'm surprised it is that slow for you20:38
jamit is about 2min here20:38
guilhembiuh20:38
jamguilhembi: oh, you might also do "bzr annotate --show-ids"20:38
jamthat will help a bit20:39
jamit uses revision-ids rather than trying to work out "nice" values for it20:39
jambut they have about as much info20:39
guilhembijam: Intel(R) Core(TM)2 CPU         T7400  @ 2.16GHz 2GB RAM opensuse 10.220:39
guilhembi(laptop)20:39
jamguilhembi: laptop here as well20:39
jamT7500 @ 2.2GHz, 2GB20:39
jamIt might be the number of pack files in your repo20:40
jam$ time bzr annotate --show-ids sql/ha_ndbcluster.cc >/dev/null20:40
jamreal    0m19.441s20:40
guilhembiI use a shared repo, have several MySQL branches. But all of them are more or less included (as far as revision history) is concerned in 6.0-ndb, which is a recent branch.20:41
jamguilhembi: as you do commits, we create new pack files. Occasionally we autopack them together into larger ones20:41
jamhaving 1 large one is a lot faster than 20 small ones20:41
jam(at the moment our index code isn't scaling correctly with the number of packs, it should be log(N) at most, but it seems closer to N)20:42
guilhembiahah, so one could write a plugin which forces a pack?20:42
jamguilhembi: just run 'bzr pack'20:42
guilhembiwah wah20:42
jamWe expose it as a command20:42
jamwe *want* to fix the problem, but it is a decent workaround for the moment20:43
jamguilhembi: however, I'm trying to work out if my tree is properly treating that file20:44
jambut 20s is vastly different than 5 min20:44
guilhembiok, I do a pack...20:45
jamguilhembi: before you do, just do "ls .bzr/repository/packs | wc -l"20:45
guilhembitoo late20:45
jamor you can do it while it is processing20:45
jamit won't change until it is done20:45
guilhembijam: output is : 5220:46
guilhembi(ran this in shared repo)20:46
jamguilhembi: yeah.... that's pretty bad20:46
guilhembijam: that's a lot you mean?20:46
jamI start noticing around 10+20:46
guilhembiahah20:46
jamit is probably valid for the mysql tree and how many revisions you have20:46
jambut a pack should help quite a bit20:46
guilhembimaybe I should send this advice to my colleagues who have slow gannotate.20:46
jamguilhembi: well, try it first :)20:47
jamjust to give a bit of info, as a trade off between number of packs and how often we have to autopack, the code uses the 'digits' to figure out the pack layout. So if you have 53,281 revisions , then it tries to create 5 10,000 entry packs, 3 1,000 entry packs, 2, 100 entry, 8 10, and 1, 1.20:52
guilhembiI ran "bzr pack" in a 6.0 branch, took 5 mins, and now I am down to 40 packs.20:53
jamIn my mysql-repo, I see 61266 => 2120:53
guilhembiI should run this in shared repo directly, maybe20:53
jamguilhembi: can you do20:53
jamguilhembi: shouldn't matter, lets check something else20:53
jamgrep -a "len" .bzr/repository/pack-names20:53
jamThat is the "official" count20:53
guilhembilen=120:53
jamthere *can* be files present which aren't referenced20:53
guilhembiok, so official count is 1, I start annotate20:54
jamguilhembi: so there are some "cruft" files that won't be used, if you want you could get rid of them20:54
jamI'm a bit surprised it is that high20:54
guilhembibah, if they won't be used, they just take up space... no time...20:54
jamguilhembi: sure, it is just easier to remember the "ls" rather than the grep command :)20:54
guilhembijam: to get rid of them, what shall I do (won't do it right now) ?20:55
jamcat .bzr/repository/pack-names20:55
jamAt the end is the list of files that are being referenced20:55
jamrm the others20:56
jamyou may also want to clean them out of .bzr/repository/indices20:56
jamNote that they are called "<name>.pack" on disk, and just <name> in that file.20:56
guilhembimmm so somebody could write a plugin which does "bzr pack" + the procedure which you suggest...20:56
jamand there are NULLs in the file, but I don't expect that to cause you problems20:56
jamguilhembi: sure20:56
jamand if you did that, it would probably also want to delete the files in .bzr/repository/obsolete-packs so they are truly gone20:57
jamprobably after doing "sync"20:57
guilhembijam: Noted. Does it matter to "bzr pack" in one branch of the repo, or in the repo directly?20:57
jamto make sure you don't delete the last copy before the OS has a chance to write it out20:57
jamguilhembi: in a branch will pack the repo20:57
jamno difference20:57
guilhembijam: not sure I get the relevance of "sync" here, but no big deal20:58
jamguilhembi: you want to tell the OS to write out the new .pack file to disk, before you delete the old pack files20:59
jamthat is why we move them to 'obsolete-packs' rather than deleting them right away20:59
jamin case you lose power inbetween claiming the new .pack and getting rid of the old one20:59
jamOS don't always serialize actions the way we would prefer20:59
jameven sync isn't a 100% guarantee, but it is *better* than not doing it20:59
guilhembijam: now I understand (interestingly, I have coded log recovery in a storage engine of MySQL, so this rings a bell now :)21:00
jamguilhembi: right, you write out the "next" stuff, write out  what you are going to , sync, and then start doing it.21:00
guilhembiSo, first annotate finished, real 3m1321:01
jamguilhembi: I'm a bit surprised... is that with '--show-ids', with 'annotate' or 'gannotate' and bzr.dev or my bzr21:02
guilhembi show-ids, annotate, your bzr; running with bzr.dev now21:03
guilhembireal    0m20.485s21:03
guilhembiwow21:03
guilhembithis 20s was show-ids, annotate, bzr.dev.21:03
jamguilhembi: try again with my bzr21:04
jamoh, you know what21:04
jamYou didn't run "make" in my code, did you?21:04
jamYou don't have the compiled "diff" extension21:04
lifelessmoin21:04
jammoin lifeless, go back to sleep :)21:04
guilhembijam: man, no; I branched your branch, and bent the symlink I use, and off I go21:05
jamguilhembi: right, so go into that dir and run "make"21:05
jamIt should make annotate quite a bit faster21:05
=== mw is now known as mw|food
NfNitLoopwhat's that compile to?  .pyc? or is it C/C++?21:06
NfNitLoop(sorry, eavesdropping)  : )21:06
jamNfNitLoop: there is some Pyrex code which compiles to C => .obj21:06
NfNitLoopAh.21:06
jamPyrex being an intermediate between Python and C, (such that it has types, and can be "compiled" to raw C code to be compiled)21:06
NfNitLoopCool.21:07
guilhembigrmbl it's not mentioned in the INSTALL file, neither in "Run from source directory" in http://bazaar-vcs.org/InstallationFaq which is what I followed21:07
NfNitLoopSee, I just hang out in here and learn through osmosis.  : )21:07
jamThough technically, the "diff" code is just plain C formatted to become a python extension. There are *other* things we do in pyrex extensions21:07
jamguilhembi: well, they aren't *needed* just recommended, but I'll update that page21:08
guilhembijam: thanks; is "make" automatically done for people who use "python setup.py blah" ?21:09
jamguilhembi: The "Run from source directory" has a "% make" step21:09
jamguilhembi: yes21:09
guilhembiI'm trying to see how many colleagues would benefit from that...21:09
guilhembijam: indeed, I'm really blind21:09
guilhembijam: and now it's 20 secs for your bzr too.21:09
guilhembiSo, the annotate outputs have 266 different lines...21:09
jamgood to hear21:09
jamguilhembi: well, "bzr annotate foo" doesn't actually annotate the working copy either ... :(, unlike gannotate21:10
mwhudsonmorning21:10
guilhembijam: you wanted me to annotate the working copy? I used the clean 6.0-ndb file.21:10
jamguilhembi: well, we are trying to figure out why we are seeing this conflict, right?21:10
lifelessjam: physio appointment21:11
jamif you want to take me through how *you* do it21:11
lifelessjam: though I'd love to go back to sleep, I can't21:11
jamthat may be enlightening21:11
jamsorry to hear that lifeless, sleep afterwards then :)21:12
jamspeaking of which, what are you doing up guilhem?21:12
guilhembijam: it's only 22:14 here and I'm talking with a bzr dev to try to find out what's going on in a damn file merge21:13
jamsilly man21:13
guilhembiyes21:13
guilhembisure, I'll need to sleep, or waking up for kids' breakfast will be tough21:14
guilhembijam: so, I have now gannotate ha_ndbcluster.cc, with your bzr, under the eyes.21:14
guilhembilet's look at a conflict which I prententiously claimed to be false...21:15
guilhembiline 983621:15
guilhembijam: I look and look again, but all lines in MERGE-SOURCE in conflict starting from line 9836,21:17
guilhembiare from revs <= sp1r-frazer@forth.ndb.mysql.com-20080320110539-6261821:17
guilhembiwhich is in 6.0-ndb already.21:18
guilhembiAs MERGE-SOURCE is supposed to be what comes from 5.1-telco-6.2-merge and conflicts with 6.0-ndb text,21:19
guilhembithis is weird: all revs which form MERGE-SOURCE text have already been merged into 6.0-ndb.21:19
jamyeah, but if you are merging from different bases, it is still possible. I'll still try to look at it closer, I understand your confusion21:23
guilhembijam: Ok. I verified again: I copy-pasted all revision ids from gannotate for this MERGE-SOURCE text, and ran "bzr log -r" for each of them in 6.0-ndb: they are all there.21:25
jamguilhembi: bzr log -r revid: will always display the revision21:28
jamwhether it is merged or not21:28
jamIt just has to exist in the repository, not in the branch21:28
guilhembiuh21:29
jamThough if it has a revno, then it would exist in the branch21:29
guilhembijam: this behaviour of "bzr log -r" is probably confusing; "bzr help log" says21:29
guilhembi"  By default show the log of the branch containing the working directory."21:30
jamand in my check, the one you listed is in the ancestry21:30
jamthe frazer@forth revision21:30
guilhembiI looked again, and it printed revnos for all revids.21:30
jamI'm a bit curious, though, why it would give that merge revision as the last modified, are you using my bzr or bzr.dev?21:30
jammy bzr shouldn't give the merge revision, unless it actually modified it21:31
guilhembijam: actually (I just tested), asking for a revid which is in another branch than 6.0-ndb, when I am cd into 6.0-ndb, results in bzr: ERROR: exceptions.ValueError: list.index(x): x not in list21:32
guilhembiso it does not tell me about revs out of 6.0-ndb.21:32
guilhembijam: I'm using your bzr21:32
beunojam, specifying a revid that is not in the branch but is in the repo gived back a traceback. See bug #24199821:32
guilhembiand I'm using gannotate.21:32
ubottuLaunchpad bug 241998 in bzr "bzr log -r revid:nonexistentrevid throws traceback" [Medium,Confirmed] https://launchpad.net/bugs/24199821:32
beunos/gived/gives21:32
beunoexactly  :)21:32
beunoI tested it on bzr.dev21:33
jamguilhembi: one other interesting thing to try, is to use "-Dmerge" with "bzr remerge"21:37
jamIt should output a "filename.ext.plan" file21:38
jamWhich should hint as to how it arrived at its decision21:38
guilhembijam: bzr remerge -Dmerge?21:39
jamguilhembi: bzr remerge --weave -Dmerge sql/ha_ndbcluster.cc21:39
jamis what I would use21:39
guilhembijam: that would be interesting... but what if I left it to you? You may read the plan more easily than me, maybe spot a weirdness?21:40
jamguilhembi: well, what I'm seeing is some lines in "killed base" and then them showing back up again as "new-b".21:41
jamWhich means that in one of the common ancestors, the lines were changed21:41
jamand presumably in the others they are still there21:41
jamI'll try to draw a quick graph of what I think happened21:41
guilhembijam: I think this may be a rabbit hole; I still have trouble understanding how the principle that: "if it has been merged already, it should not be a conflict", can fall short. You might be able to convince me that it's false, but for the entire Engineering group of MySQL, there would be work...21:43
jamguilhembi: I'm guessing it is a discrepancy between the merge algorithm's annotations and how 'annotate' might do it.21:44
jamAs near as I can tell, the lines in question are considered "obsolete" by the time we get to the common ancestors21:46
jambut then 5.1-merge introduces them again anyway21:46
=== mw|food is now known as mw
jamguilhembi: do you have these in BK that you could do the merge and compare, or is the current stuff only bzr?21:48
guilhembijam: the chance that people messed lines around, committed, put them bacl, committed, is low.21:48
pygifolks, postgresql migrated to bzr, right?22:26
pygior was it mysql?22:27
Pieter'mysql22:27
Pieterpostregsql is in git afaik22:27
Pieteror not22:28
mwhudsoni think it might still be in cvs or something crazy...22:29
jamlast I checked postgres was still in cvs, and it is mysql that moved to bzr22:31
beunomornin' mwhudson22:33
mwhudsonbeuno: http://bazaar.launchpad.net/~bzr/bzr/trunk/files <- paste, zpt-templating, etc :)22:33
mwhudson(not streaming though)22:34
beunomwhudson, very cool!  how's the server load?22:36
mwhudsonok so far i think22:37
mwhudsonLH is also now running on a different machine from all the other codehosting stuff22:37
beunoah, so it's harder to compare22:38
beunoyay!  nicer urls!22:38
mwhudsonoh yeah!22:38
mwhudsonthat too22:38
jammwhudson: well, right now it is taking a while to load :)22:38
mwhudsonjam: which page?22:39
jammwhudson: the one you linked22:39
jamonce it came up, then it was reasonable the next access22:39
mwhudsonhmm22:39
jamit could be dns on my end, I don't really know22:40
jamanyway /away for about an hour22:40
pygijam, saw the mail from Packt about bzr book? :P22:41
pygiups, you went away xD22:41
beunomwhudson, you cerry-picked from trunk, right?  The order for dirs is still off22:42
mwhudsonbeuno: no, it's just trunk @ some rev22:42
mwhudsona few off tip22:43
beunomwhudson, I get timeout at: http://bazaar.launchpad.net/~bzr/bzr/trunk/revision/351022:43
mwhudsonbeuno: just after the wsgi merge22:43
mwhudsonbeuno: hmm22:44
mwhudsonbeuno: that's a big old diff i expect22:44
beunoI think it's like 20 big diffs  :p22:44
* thumper pats lifeless on the back22:44
thumperI like looms22:44
thumpermore and more22:45
beunomwhudson, this revno makes a good case for my ajax branch  :)22:45
beunoit will load the page22:46
beunoand let you see each diff individually22:46
mwhudsonit also makes the case for my streaming branch i expect :)22:46
beunoheh, yeah, that would be neat to see in production22:47
LarstiQbeuno: can I see that ajax branch in action somewhere?22:50
beunoLarstiQ, yeap, let me load it up on my machine22:51
* LarstiQ wants to show it to someone22:51
beunoLarstiQ, http://intranet.pentacorp.net:8080/bazaar/bzr_garbage/revision/346922:54
bkorelmo: was the ldif enough for now?22:58
elmobkor: I think so, yeah, lamont should have set up/be setting up accounts22:59
bkorelmo: good, as I think the port opening will take a while22:59
LarstiQbeuno: thanks22:59
elmobkor: ok22:59
LarstiQbeuno: I can't collapse the diffs?23:00
beunoLarstiQ, the UI needs some serious love, yes23:04
beunoI also need to merge that with trunk, since it's using old code23:05
beunoand, well, there's a shiny new theme on the way23:05
beunoso that will change everything. Again.23:05
Pieterit'd be nice if bzr diff had an option to ignore whitespace differences23:06
beunoPieter, file a bug  :)23:07
Pieteryeah I guess, but I hate bugtrackers23:08
mwhudsondiff --using 'diff -b'23:09
mwhudson?23:09
Pieteryeah, but who's going to type that?23:09
mwhudsonbzr alias diffws='diff --using "diff -b"'23:10
mwhudson?23:10
mwhudsonif that's too much, then there's no hope for you :)23:10
PieterI don't like having to create aliases and installing plugins to get basic functionality :)23:11
fullermdHeck with whitespace, I just wish it said something sensible about binary files   :p23:12
vilaPieter: 'bzr help alias' no plugin needed23:13
Pieterthat's not what I meant23:14
LarstiQPieter: but obviously it's not basic functionality ;P23:14
LarstiQPieter: I'm interested though, when do you find it useful?23:15
LarstiQPieter: and offtopic, are you going to Parkpop?23:15
vilaYou asked for an option, mwhudson gave you an option, you didn't want to type the option, he offered the alias, you said no plugin nor alias, I said no plugin. But, ok, bzr can't do what you want.23:15
vilag'night all23:16
LarstiQvila: night!23:16
PieterLarstiQ: if you have a python script that you changed to a class, so everything gets indented23:16
beunomwhudson, btw, do you know why this would be happening: http://bzr-mirror.gnome.org:8080/alleyoop/trunk/changes ?23:16
beunonight vila23:16
LarstiQPieter: aaah, good point23:16
Pieterif you then want to diff it against eg the same file on another branch, you need something that ignores whitespace23:16
LarstiQPieter: wouldn't you want to ignore just uniform indent changes?23:17
LarstiQfor that specific case23:17
mwhudsonbeuno: looks like url generation is fuxored :(23:17
Pietersure, anything that works :)23:17
PieterLarstiQ: and I'm not going to parkpop :)23:17
LarstiQPieter: awww23:17
LarstiQPieter: ok, I agree that ignoring something there certainly has merit23:18
beunomwhudson, yeah, I don't understand why. It's trunk + search, but he tried trunk alone, and same thing happened. I can't reproduce it locally23:18
LarstiQPieter: I'm not sure if python specific should be in core, but ignoring all whitespace could be23:18
mwhudsonbeuno: do you know if he's using a vanilla serve-branches.py ?23:19
mwhudsonJc2k: still awake?23:19
beunomwhudson, yeap, untouched23:20
Jc2khi guys23:20
Jc2ki considered patching serve-branches, but yeah, its a bit different to twisted.web2 :)23:20
Jc2ki'm around if you want me to do stuff, i just have to hit the pro Git guy on pgo over the head23:21
mwhudsonJc2k: hmm?23:21
Jc2kmwhudson: i was hoping i could add something to serve-branches to serve /static/ of the root to get things going until there was a proper fix, but its not twisted.web2 so i dont know where to poke so i left it :P23:22
beunoit should be serving /static/ from root23:23
beunothat's the default behaviour23:23
mwhudsonthe links to static things are all //staic23:24
mwhudsonwhich i guess is the problem?23:25
beunomwhudson, what's more interesting is that /static is served from: http://bzr-mirror.gnome.org:8080/epiphany/trunk/static/javascript/collapse.js23:26
beunoso it's not at the root23:27
mwhudsonbeuno: it's served from both places23:27
mwhudsonor at least, it should be23:27
beunomwhudson, doesn't seem to: http://bzr-mirror.gnome.org:8080/static/javascript/collapse.js23:27
jambeuno: there is that bzr_garbage again... you make me :'(23:28
mwhudsonJc2k: what versions of paste and paste-deploy do you have?23:28
Jc2kmwhudson: 1s23:28
Jc2kmwhudson: 1.0.123:28
mwhudsonJc2k: oh er ah23:29
mwhudsonJc2k: that's paste-deploy, right?23:29
Jc2koh23:29
mwhudsonif it's paste, i'm amazed anything works at all :)23:29
mwhudsonJc2k: can you try commenting out the stuff to do with PrefixMiddleware in serve-branches.py ?23:29
Jc2kfrom dpkg -l23:30
Jc2kii  python-paste               1.0.1-1                                  Tools for using a Web Server Gateway Interfa23:30
Jc2kii  python-pastedeploy         1.0-1                                    Load, configure, and compose WSGI applicatio23:30
mwhudsonholy crap23:30
mwhudsonwhat os are you running?  etch?23:30
Jc2ketch :)23:30
mwhudsonwell, try commenting out the PrefixMiddleware stuff23:31
beunojam, hahaha, it's an old branch  :p23:31
beunothere, killed the branch23:32
Jc2kmwhudson: http://bzr-mirror.gnome.org:8080/conduit/trunk/changes :)23:32
jambeuno: thanks :)23:33
jambeuno: you could call it "bzr_no_more_tears" if you prefer23:33
beunoJc2k, cool. Search even works!23:33
mwhudsonJc2k: that looks better23:33
mwhudsondependencies suck donkey balls23:33
beunojam, muahahaha, I'll grep my LH and do it!23:33
cjhurm...  '$ bzr branch lp:mysql-server' failed halfway through and now I can't 'bzr up' from the directory, and trying to re-run the branch command tells me:23:33
cjbzr: ERROR: Target directory "mysql-server" already exists.23:33
jamalso, my fingers keep wanting to type bueno, what's up with your name? :)23:34
cjI'm new here... can someone LART me?23:34
LarstiQjam: be-uno? :)23:34
beunojam, why would you want to type a full nickname?23:34
LarstiQnot kinderbueno23:34
beunolol23:34
mwhudsoncj: can you cd into the branch and 'bzr pull' ?23:34
jambeuno: because I start typing "bu^T" and it never works23:34
beunoLarstiQ, I see you've been present in one of the conversations of me trying to explain my nickname23:35
LarstiQbeuno: I haven't actually23:35
jambut.. that is mixed languages :)23:35
jamAt least if you just said it is a fixed typo of bueno, *that* I could understand23:35
beunoLarstiQ, then that's a pretty good observation23:35
LarstiQbeuno: I did ask you in London wether 'be-uno' was a correct way to pronounce it.23:36
beunojam, the explanation is pretty stupid, so I'm going to defer that until the next time I see you and there is enough beer  :)23:36
LarstiQso that helped in my confidence :)23:36
jambeuno: Well I'm as close to seeing you as I can now, and there is a reasonable amount of beers in the fridge, and the grocery store is 2 blocks away. I can't do much better than that :)23:36
beunolifeless, http://bzr-mirror.gnome.org:8080/conduit/trunk/changes    LH + search + Gnome theme in action!23:36
beunohmm, beer...23:37
beunoI should really have a fridge in the office23:37
jambeuno: well, following the "svn" link looks pretty bad: http://svn.gnome.org/23:37
jamAnd the font sizes keep changing23:37
jambut otherwise sexy23:37
jambeuno: of course, if you do something like search on conversion_exists, i would sort of expect the revisions to come back in more of a sorted order: http://bzr-mirror.gnome.org:8080/conduit/trunk/changes?q=conversion_exists23:38
beunojam, yeah. New theme is 90% complete, so I should be able to wedge that in before Guadec23:38
jam717, 87, 79, 111, 160, ...23:38
beunojam, blame lifeless  :)23:39
jamI've blamed him for too much already23:39
jamhe reached his quota for this week23:39
beunowell, I suppose we can blame Jc2k, since it's on his server23:39
beunodamn, font sizes do vary a lot23:40
Jc2kbeuno: O: ) i think the list of repos/branches being unskinned is the only thing stopping me doing a "OMG Bazaar/Loggerhead FTW" post23:42
beunoJc2k, that puts quite some pressure on me...  :p23:43
Jc2k:D23:43
beunoI'll get to that after I wrap up what I'm supposed to be doing now then23:43
Jc2k:D23:44
Pengjelmer: bzr-svn is currently tracebacking with bzr.dev because it can't import bzrlib.knit.make_file_knit.23:44
=== kiko-phone is now known as kiko
mwhudsonprettier directory listings really shouldn't be hard23:51
beunomwhudson, nah, I'll get that done today for sure23:53
beunoI also what to see if I can improve the font weirdness23:53
beunoseems both CSS files are clashing23:53
mwhudsonbeuno: cool23:53
blueyedI have a mainline dev branch.. a derived main.local branch with changes needed for local development and now a feature branch derived from main.local - how do I get only the feature into the main dev branch?23:57

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