/srv/irclogs.ubuntu.com/2007/12/23/#bzr.txt

jelmerVerterok: But you wouldn't necessarily want to display all revision properties00:00
Verterokjelmer: right, because of that show_properties isn't implemented in the core, bzr-svn should provide it's own LogFormatter implementation to handle it's own properties ;)00:01
jelmerVerterok, Right, but I would want to hook into the default LogFormatters00:01
Verterokjelmer: ok, so this isn't going to work for you00:04
Verterokthanks, I'll keep thinking how this could be done00:04
jelmerVerterok: Thanks00:05
Verterokjelmer: np :-)00:06
jmlwow. I just typed bzr st on a svn branch by accident00:19
jmlnow it appears to be recalculating something expensive00:19
Verterokjelmer: maybe my proposed solution can be used after all. I just found that registered LogFormatter can be removed from the registry00:25
Verterokso, bzr-svn can override the default formatter if it provides a show_properties or similar hook00:25
jelmerjml: Ah, yep, it would be caching some revision metadata00:25
Verterokjelmer: but I'm not 100% sure of what I'm saying...I'm going to try to implement it and see if it works :P00:28
jelmerVerterok, that would block others from registering custom handlers though no?00:28
Verterokjelmer: it depends on how and  when bzr-svn take control.00:31
* Verterok getting bzr-svn to look how it works00:31
bitmonkjelmer: i'm having a hell of a time getting python svn support to work on osx leopard, know of any handy guides?00:33
bitmonkhave spent some time in #svn00:33
jelmerbitmonk: you may want to talk to mwh, he has compiled svn on MacOSX afaik00:34
* bitmonk nods00:34
bitmonki have as well, just not in a while.00:34
jelmerI don't have a Mac myself so I don't have any experience with it00:34
Verterokjelmer: y're right, it will block all others :-(00:40
aadisdoes bzr-svn work with 1.0?00:42
jelmeraadis: yes00:42
Verterokjelmer: another (and last for today) approach: plugins can register it's own show_properties(dict) and it's stored at class level in the LogFormatter. This way a LogFormatter can have n show_properties00:44
jelmerVerterok: Yes, I think something like that would work00:45
Verterokjelmer: ok, I'll make a proof of concept00:48
jelmercool00:49
aadisanyone had any success with bzr 1.0, rich-root, trac+bzr ?00:53
jelmeraadis: what errors are you getting?00:56
aadisjelmer: one sec, i'll paste00:56
aadisjelmer: sorry, that took a while01:13
aadisi'm getting this: "TypeError: can't compare datetime.datetime to float"01:13
aadisunder "Browse Source"01:14
aadisi'm assuming trac+bzr works for repos created with: --rich-root-pack --no-trees01:15
jelmeraadis, I think that's an old error01:15
jelmerand unrelated to rich-root-pack01:15
jelmeror rich-root01:15
aadisah, mixing 0.10 and 0.11 plugins. i see.01:17
aadisbut now this "ZipImportError: bad local file header in /usr/lib/python2.5/site-packages/TracBzr-0.2-py2.5.egg"01:20
aadisi just built and installed the plugin, fresh checkout. weird.01:20
Verterokjelmer: I have a working implementation of the show_properties for 'log --long', I can upload it to a server if you want to take a look and see if it's the right approach01:43
* Verterok dinner01:52
=== Verterok is now known as Verterok_
jelmerluks: ping02:32
jelmerVerterok_, ah cool02:44
jelmerVerterok_, yeah, that'd be nice02:44
=== Verterok_ is now known as Verterok
Verterokjelmer: ok, it's a patch against the latest bzr.dev, get it from: http://freeshells.ch/~guillo/code/properties_log.patch03:01
jelmerVerterok, cool03:27
jelmerVerterok, I'll have a look tomorrow, thanks!03:27
Verterokjelmer: ok, tell me then what do you think about it.03:27
VerterokI'm leaving too03:27
* Verterok heading to bed03:28
Verterokseeya03:36
=== Verterok is now known as Verterok_
MattCampbellHas anyone integrated bzr with the Roundup issue tracker?04:27
=== pcapriotti__ is now known as pcapriotti
``Cubejelmer: ping12:17
``Cubejelmer: what's with the icons?12:19
=== pcapriotti_ is now known as pcapriotti
``Cubejelmer: ???13:46
``Cubeyou there13:46
PengHe was there...ten hours ago.13:52
``Cubehehe ;=14:09
``Cubejelmer: you here now?14:09
PengOhhh. The `` in your nick kept making me think you were using /me.14:10
``Cubelol14:44
``Cubehello16:02
``Cubeanybody there?16:02
jelmer``Cube: Hi16:04
``CubeWOW16:05
``Cubehello jelmer!16:05
``Cubebeen seeking you for 5 hours now16:05
``Cubenevermind, what about the icons?16:05
``Cubejelmer: !!!!16:07
jelmer``Cube: Sorry, no news on that yet16:08
jelmer``Cube: I haven't even sent mail to the list yet16:08
``Cubehmm16:08
``Cube...16:08
``Cubeok16:08
``Cubewhen will you do that?16:08
``Cubejelmer16:09
jelmerI'll send an email right now - should I cc you?16:09
``Cubeyea, would be cool16:14
``Cubejelmer: ill give you the email in private chat16:14
jelmerok16:14
``Cubejelmer: sent?16:24
=== bigdo1 is now known as bigdog
=== Verterok_ is now known as Verterok
``Cubejelmer: and?19:08
``Cubedoes anyone here know DANIEL SCHIERBECK?19:11
``CubeI think he works for bazaar19:12
jelmer``Cube: Sorry, got distracted by some other things19:16
jelmer``Cube: Will send the email within the next hour19:16
``Cubeuh19:18
``Cubeok19:18
``Cubecan you tell me one thing:19:18
``Cubecan I start with tangofing the current high resolution bazaar icon?19:18
jelmer``Cube: yes, I think that would be a good idea19:21
jelmer``Cube: did you get bzr-gtk running?19:21
``Cubejelmer: I got the icons ready, I have a 192x192, 144x149, 48x48 and working on the 32x32, 22x22 and 16x16 will come20:41
jelmerCool!20:41
``Cubeyea20:41
``Cubedo you want to see them?20:41
``Cubemaybe they're totally crap20:41
``Cubesorry for that language20:41
``Cubewould you like to check'em out?20:41
``Cubeor not, jelmer20:42
``Cubeand could you give me the IRC name or daniel schierbeck20:42
jelmer``Cube: Please20:42
``Cubecool, ill upload them, one second20:42
jelmerhis IRC nick is schierbeck usually20:42
``Cubeoh ok, thanks!20:42
jelmer``Cube: I've just sent that email. Sorry it took so long.20:43
``Cubeeh, no problem20:44
``Cubehope ill be allowed to make them20:44
``Cubeand I hope they'll be good enough20:44
jelmer``Cube: Btw, I have another request, somewhat related.. any chance you could do an icon for bzr-svn?20:44
``Cubewell, one thing to keep in mind: even if you think they're totally bad, don't just say no: I can change them completely20:44
* jelmer looks forward to seeing them :-)20:45
``Cubeeh, I think that belongs to the icons I should do? (= sure!)20:45
``Cubehttp://cubibubi.cu.funpic.de/tango/bazaar/20:47
``CubeAND KEEP IN MIND WHAT I JUST SAID PLEASE20:47
``Cubethere can be changed so much...20:47
``CubeI'm really looking forward to your first impression...20:47
``Cubehope it's going to be positive20:47
jelmerw00t20:48
jelmeryep :-)20:48
``Cubeheh20:48
``Cubereally?20:48
``Cubeyou like them?20:48
jelmerYeah, they look great :-)20:49
``Cubeheh20:49
``Cubeanything I could add/change, something that you don't like 100%?20:49
jelmerThe logo is meant to look like a traffic sign20:50
``Cubeah20:50
``Cubeso, more metallic look? not so much glow?20:50
jelmercould you remove the line between the head and the tail of the "road" on the sign?20:50
``Cubeoh, :P yes should be easy, I knew that wouldn't be correct20:51
``Cubeill remove it, gonna take up to 5 minutes for all sizes20:51
``Cubewell, I intentionally created a 192x192 (for launchpad) and 144x149 for your size (bzr20:51
batomscan anyone do a bzr upgrade for me at bazaar.launchpad.net/%7Ebauble/bauble/trunk/21:28
batomsbazaar.launchpad.net/~bauble/bauble/trunk/21:28
jelmerbatoms: better ask in #launchpad21:30
batomsjelmer: i did but no response21:31
jelmerbatoms: I think they're all on their christmas break atm21:37
batomsjelmer: well maybe santa will bring me some patience for xmas21:39
unenoughis it possible to merge two projects? e.g: use the theoretical r0 shared revision as a common ancestor22:05
fullermdSure, I do it all the time.22:05
unenoughreally? How (and why? :-) ?22:05
fullermdAll the files are different, of course.22:05
unenoughYeah, why do you happen to have to merge projects a lot?22:05
fullermdBecause I keep some commonly-used code in its own branches, then I can merge it into projects that use it.22:06
unenoughand how do you merge?22:06
unenoughbzr merge refuses22:06
fullermdTry with "-r0..-1".22:06
unenoughgreat, thanks. Why doesn't -r0 work?22:07
unenoughwhat does 0..-1 mean?22:08
fullermdWell, '-r0' means "merge from the common ancestor up to rev 0", which is kinda a double-meaningless.22:08
fullermd0..-1 means "from 0 through the head"22:08
unenoughoh ok, thanks!22:09
fullermdNo problem   :)22:10
ubotuNew bug: #178353 in bzr "Memory error on branch from launchpad" [Undecided,New] https://launchpad.net/bugs/17835322:16
unenoughthere doesn't seem to be a "blame" for directories?22:27
unenoughI want to know which revisions touch some directory or anything in it...22:27
LeoNerdbzr log --line path/to/dir22:31
fullermdEr.  That doesn't do what you might hope it does...22:32
LeoNerdHrm.. oh yes.. :/22:32
LeoNerdOK... what about  bzr log --line `find path/to/dir -type f`22:32
fullermdNor does that.22:33
LeoNerdHrm...22:33
LeoNerd(off top of my head) find path/to/dir -type f | xargs -n1 bzr log --line | sort -r | uniq22:33
fullermdlog only takes one file.22:33
fullermdUff.  Call me next week when THAT finishes running   :p22:34
LeoNerdAh. That works for me :)22:34
LeoNerdBut then I just tried a tiny tree of 6 files and 7 revisions22:34
fullermdMmph.  Not so comfortable with a few hundred files and thousand revisions...22:35
LeoNerdYa.. I imagine perhaps not so22:35
unenoughthanks, I'll try that :)22:35
fullermdOr for those of us who don't like --line   ;)22:36
unenoughit took about 2 seconds on my repo :-) Thanks!22:36
unenoughhmm, I am trying to make a retroactive removal of files in my repo, by creating a new repo and merging selected revisions from the original one (ignoring the ones I don't want carefully)22:47
unenoughAnd I caused bzr 0.90.0 to get an assertion error22:47
unenough    assert len(history) == revno, '%d != %d' % (len(history), revno)22:48
unenoughAssertionError: 47 != 122:48
* fullermd blinks.22:48
unenoughI basically used:    bzr merge ../old-branch -r0..46 ; bzr commit22:49
fullermdThat's...   intersting.22:49
unenough(on a new branch)22:49
fullermdOh.  Hm.22:49
unenough(because I want to kill revision 47)22:49
fullermdThe surprising thing, I guess is that merge let you do it, not that commit failed.22:49
fullermdTry branching rev 46, then working from there.22:49
unenoughI plan to later merge 48..X then X+2..Y and so on22:49
unenoughif I branch from 46 I will still need to merge the revision ranges after, will those work?22:50
fullermdWell, those merges can't really be merges formally speaking, since you're missing a rev.22:50
fullermdWhat you really want to do is sorta re-make those commits on top of the tree.  There might be a plugin to help automate that...22:51
unenoughhmm, can't I merge revision ranges from another branch to me, if those have a gap?22:52
unenough(a gap between my last and his first)22:52
unenoughin other words, my technique for retro-active killing of revisions/files will not work?22:52
fullermdWell, merge will bring over the changes.  But it won't record it; sorta the equivalent of diff | patch (with some smarts on conflict avoidance)22:52
unenoughwon't it also record the diffs of the individual revisions in the range into my new history?22:53
fullermdDepends on the definition of 'work'.  But your new rev 47 (old 48) won't have any relation to your old 48.22:53
fullermdNo, because the individual revisions won't be pulled in.22:54
unenoughI see, indeed I lose the history.. so what are my best options to do retro-active removal of files?22:54
fullermdWell, what you want to do is replay each rev's changes on top of the tree, skipping certain revs/files.22:54
fullermdI think there was at least part of a plugin that could do it.  It's sorta the guts of rebase, with some filtering capabilities.22:55
fullermdBut I don't know of any existing automated way.22:55
unenoughmaybe I'll create one then, thanks22:55
fullermdThere used to be a 'graft' plugin, I think; that might be close.22:55
fullermdTry digging that up, or corner jelmer about what could be done with rebase.22:56
unenoughwhat is rebase?23:00
unenoughbut if I use graft or any other commit-based method, won't I lose all the merging/branches information? All I get a serial linear list of commits23:01
fullermdWell, for any commits post the commit you're losing, that's kinda unavoidable (without a whole lot of smarts, anyway)23:02
unenoughI could selectively delete revisions in the past....23:03
fullermdAll the revs past that points are necessarily defunct, since they depend on something you're not gonna have.  So they all have to be remade.  It would be an interesting exercise to try and remake the full topology...23:03
fullermdI guess there's no theoretical reason it would be impossible (at least, in the general case).  Take a fair hunk of work, though.23:05
unenoughWell, i guess for now i'll just lose the history (i'll have it in the old repo, anyhow)23:05

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