[00:04] <igc> morning all
[00:04] <igc> hi jelmer
[00:09] <SamB> am I right in thinking that bzr selftest -E foo is supposed to put 'foo' in bzrlib.debug.debug_flags ?
[00:24] <poolie> lifeless: i see we have an Inventory and an InventoryCommon class
[00:24] <poolie> which i think is the antipattern we were talking about a while ago wrt RepositoryBase
[00:24] <lifeless> no quite
[00:25] <lifeless> InventoryCommon is the base; Inventory is really MutableInventory, or InMemoryInventory
[00:25] <lifeless> but there were enough uses of it that renaming would have been traumatic
[00:25] <poolie> why is that different?
[00:25] <lifeless> we've moved a lot of stuff to Common
[00:25] <lifeless> CHKInventory is immutable
[00:25] <poolie> i could equally say that Repository is really VFSBasedRepository
[00:26] <SamB> hooray for immutability
[00:26] <SamB> poolie: do you have some other kind?
[00:26] <lifeless> poolie: Repository long ago lost concrete code
[00:26] <poolie> RemoteRepository
[00:26] <lifeless> its not a leaf
[00:26] <lifeless> RemoteRepository is a leaf, as is Inventory, and CHKInventory
[00:26] <poolie> argh
[00:27] <lifeless> poolie: I could be wrong; but thats why I think the cases are different
[00:27]  * SamB wishes for a black board
[00:27] <poolie> i should be more precise
[00:27] <poolie> the issue is: things that sound like they should be base classes, actually are not
[00:28] <lifeless> poolie: oh right. Inventory is a really misleading name
[00:28] <lifeless> I would love to renamed it to (say) InMemoryInventory
[00:28] <lifeless> s/renamed/rename/
[00:28] <SamB> how about rename but leave an alias behind?
[00:28] <poolie> we could get there from here by either - inserting a new class called *Base or *Common
[00:28] <SamB> with a comment that it's there to avoid pain
[00:28] <poolie> or, changing the existing one
[00:28] <poolie> SamB: it's too hard wrt our api compatibility
[00:29] <poolie> i'm hoping that introducing different api break windows may make it easier
[00:29] <lifeless> SamB: do, or do not :).
[00:29] <poolie> it may still be traumatic even just within bzrlib though
[00:29] <SamB> well, at least that way people would see the right name if they repr'd it
[00:30] <poolie> btw re https://code.launchpad.net/~mbp/bzr/403523-status-crash/+merge/9739
[00:30] <poolie> do you object to me putting has_filename in the base class?
[00:30] <lifeless> so, to rename it, we could do it, use a factory as Inventory, which can issue deprecationwarning
[00:31] <poolie> anyhow, concretely
[00:31] <poolie> the thing to do is change RemoteRepository to inherit from Repository and see if anything breaks
[00:31] <poolie> or if anything should go into a LocalRepository
[00:31] <poolie> or some better name
[00:31] <lifeless> yes
[00:31] <lifeless> I'd just change RR to inherit from R and see what the fallout is
[00:32] <lifeless> +1 on that change
[00:32] <lifeless> has_filename is a little ugly though
[00:39] <igc> lifeless: that usertest run on OOo with your pending patches got done last night ...
[00:39] <igc> lifeless: 73.9 -> 1.8 seconds for selective commit
[00:39] <poolie> ! :)
[00:39] <lifeless> well, thats better than it was
[00:39] <lifeless> hows full commit?
[00:39] <igc> lifeless: and also interesting is ...
[00:40] <lifeless> [drum roll please]
[00:40] <igc> send -o dropping from 332 seconds to 69.6 seconds
[00:40] <lifeless> in my branch?
[00:40] <igc> lifeless: where 70 seconds still sucks, fwiw
[00:41] <lifeless> that would be the path2id improvement showing up
[00:41] <lifeless> igc: whats full tree commit in OOo?
[00:41] <igc> 1.8 seconds
[00:42] <lifeless> ok, so we're still dominated by something not addressed
[00:42] <lifeless> I'd love an lsprof of both incremental and full commits of a single file
[00:42] <lifeless> I suspect dirstate load/save
[00:42] <igc> shall do
[00:43] <igc> lifeless: if it is, I have a patch for that - still in review maybe
[00:43] <poolie> igc, i assume that send thing is with jam's ptach?
[00:43] <lifeless> poolie: I improved a code path send uses as well
[00:45] <igc> poolie: the 332 seconds is with bzr.dev rev 4593 - pretty recent
[00:45] <igc> poolie: but looking deeper, I'm not sure whether my 'pending' branch with robert's patches has it or not
[00:48] <poolie> spiv, does my last comment on bug 405251 make any sense to you? :)
[00:54] <thumper> does anyone use bzr with windows and launchpad here?
[00:54] <thumper> https://answers.edge.launchpad.net/launchpad/+question/79261
[00:54] <thumper> the question here is trying to work out why it isn't working
[00:54] <sidnei> thumper: occasionally
[00:54] <thumper> AFAICT it should work
[00:55] <thumper> so I'm guessing it has to do with getting bzr on windows to use his putty key
[00:55] <thumper> and I have no idea how to check that
[00:55] <spiv> poolie: "I wonder if this is related to binary modules not being built?" ?
[00:56] <spiv> Oh, there's a newer one now.
[00:56] <poolie> mm, maybe, or actually to something being stuck or inefficient in hpss protocols
[00:56] <spiv> It wasn't there when I first loaded the page.  email lag I suppose.
[00:56] <poolie> bit of a wild-ass-guess
[00:57] <sidnei> thumper: the steps he outlined seem correct generally. unless he messed up on step 5.
[00:57] <thumper> sidnei: is there any way for him to check?
[00:57] <sidnei> step 5 from the launchpad wiki, that is, the one that has a explicit warning about where it can get messed up
[00:57] <lifeless> igc: there are a few commits from trunk missing
[00:59] <sidnei> thumper: when you upload the ssh key to launchpad does it get used right away, or there's a time needed for it to sync somewhere?
[01:00] <lifeless> igc: its missing 4588
[01:00] <lifeless> which changes bundles as well
[01:00] <lifeless> igc: I'll merge trunk now
[01:01] <igc> lifeless: thanks. My 'pending' trunk is usually trunk + merges of stuff I want to benchmark but ...
[01:01] <igc> lifeless: I'd prefer to just benchmark you branch if it's up to date with trunk
[01:01] <igc> s/you/your/
[01:01] <thumper> sidnei: I don't know
[01:03] <lifeless> sidnei: its usable immediately, modulo db lag
[01:03] <sidnei> thumper: that's the only thing that comes to mind: he uploaded the key and expected it to work right away, but the key isn't immediately put in place on the server side. but i don't know if that is the case or not.
[01:03] <thumper> hmm..
[01:03] <lifeless> sidnei: the ssh daemon isn't openssh, so it just asks the db for the key, rather than waiting for it to be put on disk
[01:03] <lifeless> igc: pushed
[01:12] <igc> lifeless: is iter-changes-partial-parents enough yet? Or do I still need to follow that up with a merge from selective-file-commit?
[01:13] <lifeless> you need both
[01:24] <poolie> igc, any comments on kiko's vm mail?
[01:32] <igc> poolie: if we want continuous testing following a commit, we need it up most of the time I suspect
[01:32] <poolie> yeah
[01:33] <igc> poolie: perhaps a time out of a few hours would work though and ...
[01:33] <poolie> that's about $100/month, it shouldn't break the bank
[01:33] <igc> might result in it being down over weekend periods in particular
[01:34] <igc> poolie: if we go the mega-vs-simple installer route, ...
[01:34] <igc> poolie: then the testing only needs the standard simple installer or easy-install
[01:34] <igc> poolie: building the mega-installer will happen rarely
[01:42] <sidnei> hey igc, poolie
[01:42] <sidnei> not sure if vila let you guys know, but we have builds being run by kerguelen now
[01:43] <lifeless> excellent
[01:43] <lifeless> sidnei: have you seen hudson?
[01:43] <sidnei> matter of fact, i did
[01:43] <mwhudson> ...
[01:43] <sidnei> :P
[01:43] <lifeless> mwhudson: change your highlight rules ;)
[01:44] <mwhudson> lifeless: this one is in my brain, sadly
[01:44] <lifeless> mwhudson: I hear electroshock is much more refined these days
[01:44] <mwhudson> heh heh
[01:45] <kiko> poolie, igc: I'm outta that circuit now -- I have done what I can :-)
[01:45] <kiko> poolie, igc: again, for me bzr2 is the priority -- this is just something nice to have happen
[01:57] <poolie> kiko, thanks for connecting the circuit
[01:57] <poolie> a good 2.0 is the priority but getting good windows builds for it will help make it a good release
[02:08] <spiv> Hmm, test_pack_repository really ought to be renamed to per_pack_repository or per_repository_pack I think.
[02:12] <spiv> poolie: actually, that's something you might want to look at while looking at running tests with 2a as the default, test_pack_repository doesn't include 2a in its scenario list!
[02:13] <spiv> (also, the way the scenario definition duplicates a bunch of format strings etc rather than just grabbing them off the format objects is weird, I think.)
[02:15] <poolie> :/
[02:15] <poolie> could you file a bug assigned to me?
[02:16] <spiv> Sure.
[02:24] <jfroy> jelmer: is there some guide on using dpush?
[02:30] <lifeless> poolie: review sent
[02:31] <lifeless> bah
[02:31] <lifeless> spiv: review sent
[02:32] <poolie> for the delta branch?
[02:32] <lifeless> yes
[02:32] <lifeless> about 6 hours of reading and thinking
[02:36] <krisives1> Anyone know how I can get `bzr log` to output time and date?
[02:36] <lifeless> it does by default?
[02:37] <krisives1> It outputs date, but no timestamp
[02:37] <lifeless> timestamp: Fri 2009-08-07 01:03:20 +0100
[02:37] <lifeless> is what I see
[02:37] <lifeless> what are you seeing?
[02:37] <krisives1> Wait, nevermind
[02:37] <krisives1> I am using `bzr log --short`
[02:37] <krisives1> Hmm, I want the short but with the timestamp
[02:38] <krisives1> I suppose I can parse
[02:42] <spiv> lifeless: thanks!
[02:42] <krisives1> I know this isn't SQL
[02:42] <krisives1> Anyone know a good way to swap 2 primary keys?
[02:43] <lifeless> lunch
[02:43] <lifeless> if you need me, ring me, I'll be offline
[02:44] <krisives1> cheers lifeless
[03:59]  * igc lunch
[04:14] <emmajane> igc, noooo. no lunch!
[04:14] <emmajane> :)
[06:36] <spiv> Oof, reviews replied to.
[06:38] <poolie> lifeless: are you back?
[06:40] <poolie> epic review there
[06:40] <spiv> Yes, "epic" was exactly the word I was just thinking of :)
[06:41] <spiv> More epic than expected, really.
[06:41] <spiv> There are a few points still not 100% resolved, but I think it's probably good enough to land, and the last few nits can happen in a followup landing, I think.
[06:42]  * spiv makes a coffee
[06:53] <spiv> Yeah, with the aid of this coffee, I'm pretty comfy with the state of this branch, so I'll pqm-submit it now and send the last few fixes later.
[07:25] <vila> hi all
[07:27] <vila> poolie: I'd like to answer that mail about the win32 build machines but I miss the meaning of some TLAs: AWS, AMI ?
[07:29] <bob2> amazon webservices, amazon machine something (disk image)?
[07:30] <vila> ha right
[07:47] <poolie> hello vila
[07:49] <vila> poolie: hey !
[07:49] <poolie> hi
[07:49] <poolie> shall we talk about that?
[07:50] <poolie> i was just going to send mail
[07:50] <poolie> or maybe i should send mail and then we  should talk
[07:50] <vila> poolie: same here, mail nearly godd to be sent from here
[07:57] <poolie> vila what do you mean by "as long as we can be freed from the nightly ones"
[07:58] <vila> grr, freed "from the risk of regressions"
[07:59] <vila> wow, this sentence makes no sense at all, sorry :-/
[07:59] <vila> I meant to say: If the nightly builds gave us the benefit of catching the regressions sooner, the release builds should be hassle free and as such can be done by humans
[08:00] <poolie> ok, right
[08:00] <poolie> at least kicked off by a human
[08:03] <vila> poolie: 'kicked off' as in 'in a freshly started VM' ? Yes
[08:03] <vila> or any other valid host
[08:05] <spiv> Heh, "make check" fails on my branch due to "make docs" not liking the markup for the -DIDS:always debug flag.
[08:06] <poolie> spiv maybe eventually debug_flags should be a dict
[08:07] <poolie> i'd kind of agree for now it should be IDS_always but whatever
[08:12] <vila> spiv: 'IDS:' made it kind of obvious that the flags were exclusive... too bad :)
[08:14] <lifeless> vila: bob2: amazon web services, amazon machine image
[08:16] <spiv> I could take lifeless' suggestion and just not document them...
[08:17] <vila> spiv: >-/
[08:20] <poolie> no, they're fine
[08:52] <poolie> lifeless: in the context of https://code.edge.launchpad.net/~mbp/bzr/403523-status-crash/+merge/9739
[08:53] <poolie> what's the difference between test_inv and per_inventory?
[08:53] <poolie> it looks like they want to be the same thing?
[08:53] <lifeless> I think they do
[08:53] <lifeless> except
[08:53] <lifeless> perhaps
[08:53] <lifeless> per_inventory wants to be per_mutable_inventory
[08:54] <lifeless> and the tests at the top of test_inv - the parameterised ones, a small part of the file
[08:54] <lifeless> want to be per_immutable_inventory
[08:54] <lifeless> or something along those lines of separation
[08:56] <poolie> ok
[08:56] <poolie> then i might:
[08:56] <poolie> file a bug for this
[08:56] <poolie> rearrangement;
[08:56] <poolie> stick a test for has_filename into test_inv
[08:56] <poolie> and merge my change
[08:56] <lifeless> yup
[08:57] <lifeless> per_inventory only tests Inventory today
[09:46]  * igc dinner
[10:14] <spiv> lifeless: btw, if I just delete that if block from the per_interrepo fetch test the tests still pass.
[10:14] <spiv> lifeless: so whatever bug I had that prompted me to add it in is gone.
[10:15] <lifeless> \o/
[10:15] <spiv> Another problem solved by deleting some code!
[10:27] <Kinnison> huzzah
[10:27] <lifeless> spiv: uhm
[10:27] <lifeless> spiv: you should delete the if statement and undent the block, I think.
[10:27] <spiv> lifeless: right, that's what I meant.
[10:28] <lifeless> phew
[10:28] <spiv> run the assertions unconditionally.
[10:28] <lifeless> I thought that on first read
[10:28] <spiv> Sorry about the false alarm(s) :)
[10:28] <lifeless> then I read what you wrote.
[10:28] <spiv> Yeah, my bad.
[10:28] <lifeless> :)
[12:04] <OllieR> Hey, do symlinks work in bzr?
[12:07] <fullermd> In what sense?  bzr sill store and version symlinks, sure.
[12:33] <vila> sidnei: ping
[13:15] <jelmer> jfroy: not really, it's basically just like push
[14:10] <jelmer> igc: hi
[14:32] <igc> hi jelmer
[14:38] <jelmer> igc: I've proposed a merge for some foreign branch tests, I was wondering if you could comment on the general approach I've taken, so I know if I'm on the right track before doing a lot more of these tests.
[14:39] <jelmer> igc: (the merge proposal is at https://code.edge.launchpad.net/~jelmer/bzr/foreign-tests/+merge/9642)
[14:40] <igc> jelmer: I won't have time in coming days sorry, Maybe vila or jam could offer an opinion? If not, I'll take a look mid-to-late next week
[14:40] <igc> jelmer: sorry about that but I just have too much other stuff on my plate currently :-(
[14:41] <jelmer> igc: No worries
[14:43] <igc> night all
[14:43] <jelmer> g'night igc
[14:57] <dgoulet> hey people!, with bzrlib, is it better to use bzrlib.commit or bzrlib.builtins.cmd_commit() for a working tree?
[15:00] <dgoulet> anybody?
[15:03] <vila> dgoulet: cmd_commit is very close to the command line but may be harder to use than the command line itself
[15:04] <vila> bzrlib.commit may be harder to understand if you're not familiar with the bzr internals
[15:04] <jelmer> dgoulet: any reason for not using WorkingTree.commit()? That invokes bzrlib.commit
[15:04] <jelmer> moin vila
[15:04] <vila> jelmer: hi
[15:05] <dgoulet> no not at all, actually i'm getting deeper into bzrlib day after day and I'm wondering the best way to commit a working tree
[15:05] <dgoulet> i'm using cmd_commit right now but i was thinking that there might be a better way
[15:07] <vila> dgoulet: you should have a look at the commit tests and decide from there what suit your needs
[15:08] <vila> dgoulet: try 'bzr selftest commit --list' to get a taste
[15:08] <vila> but presumably jelemer is right, you awnt to use wt.commit()
[15:09] <dgoulet> hmm ok I look into that, very nice
[15:11] <dgoulet> another question while i'm here
[15:11] <dgoulet> i have a branch with NO tree (only .bzr)
[15:12] <dgoulet> what's the best way of getting that into a working tree to work on whitout a cmd_branch() ?
[15:15] <jelmer> dgoulet: BzrDir.open(path).create_workingtree()
[15:15] <meuserj> After upgrading bzr to 1.17, my integration with Redmine suddenly stopped working.  Did a little diving into Redmine to see what command is causing the issue, and bzr is indeed crashing on the command which redmine uses: http://pastebin.com/d58052ae2
[15:16] <meuserj> any fixes or workarounds available?
[15:18] <jelmer> meuserj: please file a bug report, this looks like a regression in bzr
[15:28] <meuserj> jelmer: a little more experimentation shows that it is the revno:-1 option which is causing the crash
[15:35] <meuserj> ah, and it only happens when I use bzr://.. other remote protocols, including bzr+ssh seem to work.
[15:57] <jelmer> meuserj: ah, odd
[15:57] <jelmer> meuserj: definitely seems like a bug then
[15:57] <jelmer> meuserj: the fact that it only occurs with bzr:// probably explains why nobody has noticed it before
[15:59] <meuserj> jelmer: yeah I assumed that bzr:// isn't used often.. the only reason I use it is that the machine hosting Redmine is different than the machine hosting the central repository, and it's easier to use the bzr server than try to set up ssh keys for the web server user.
[16:06] <dgoulet> from a working tree, if I want to revert a specific file to a lower revision, how can I make that happen because i'm having no result from wt.revert()... ?
[16:13] <meuserj> jelmer: wow.. yet another variable.. it only happens with repositories served via bzr-server, not individual branches
[16:21] <manuee> hi everyone, brand new user here... silly question: if i do bzr ignore dirname, is everything under that directory ignored recursively?
[16:21] <Tak> dgoulet: I'm using RevisionTree.revert()
[16:21] <vxnick> manuee: yes
[16:21] <manuee> ow awesome
[16:21] <manuee> i was wondering because olive lists the files under those dirs as unknown instead of ignored
[16:21] <manuee> so i was geting confused
[16:22] <vxnick> ah :)
[16:22] <manuee> thanks vxnick =)
[16:22] <dgoulet> yess that's what I though but when I try to get the RevisionTree from my WorkingTree, it always tell me that NoSuchRevision...
[16:22] <dgoulet> i'm doing something bad but I can,t figure it out
[16:22] <manuee> im planing on geting my drupal development under bazaar (soloing)
[16:22] <Tak> wait, my bad
[16:22] <dgoulet> from a RevisionSpec, how can I get the revision id ?
[16:23] <jelmer> dgoulet: the as_revision_id() method IIRC
[16:23] <Tak> I'm getting the rev from the revision tree, then using WorkingTree.revert() with that rev
[16:23] <dgoulet> :| how?
[16:23] <Tak> one sec, let me pastebin some code
[16:23] <manuee> ive got my repository setup here onmy local development machine, the next step would be to set it up on the production server,... any guides/howtos/tips on how to go about it so ican push changes to my server from my local machine?
[16:24] <manuee> i know its a broad question... perhaps i should study the manual a bit more
[16:24] <manuee> :X
[16:24] <vxnick> manuee: depends if you wanna use commit/update or push/pull
[16:24] <vxnick> I think the manual has a few examples which you might find helpful
[16:25] <manuee> yeh i should probably re-read that see if i figure things out
[16:25] <manuee> ow
[16:25] <manuee> server doesnt have bzr installed :X
[16:25] <vxnick> if you want to use push/pull you don't need bzr installed on the server
[16:26] <manuee> ooow nice
[16:26] <vxnick> you can do bzr push sftp://you@server.com/path/to/repo
[16:26] <manuee> push only uploads stuf ?
[16:26] <dgoulet> Tak: thanks!
[16:26] <manuee> i rtfm vxnick
[16:26] <Tak> http://paste2.org/p/366912
[16:26] <manuee> heheh bbiab
[16:26] <Tak> that's what I'm doing, which may not be The Right Way
[16:27] <Tak> err, remove that [0] from the first line
[16:27] <dgoulet> i figure ;) i'm trying it real quick
[16:27] <manuee> reading http://bazaar-vcs.org/BazaarForWebDevs atm--- it mentions to use the bzr-push-and-update plugin
[16:27] <vxnick> manuee: only if you have a remote working tree, which you prob don't need
[16:28] <manuee> ah right
[16:28] <manuee> ye only my local box will be having vc
[16:28] <manuee> thanks vxnick
[16:28] <vxnick> no probs
[16:29] <manuee> im tryin to just have a simple setup, im very new to vcs :X
[16:29] <manuee> =)
[16:29] <manuee> back to reading (getin excited)
[16:30] <vxnick> manuee: have you made the repo on your local machine already?
[16:30] <manuee> humm yes
[16:30] <manuee> i ran bzr innit
[16:30] <manuee> ignored everything but the custom code i want on vc
[16:30] <manuee> and added what i wanted
[16:30] <vxnick> committed?
[16:30] <manuee> i committed the first yes
[16:30] <manuee> i havent created a branch though
[16:30] <manuee> not sure how that goes :X
[16:30] <vxnick> do this:
[16:31] <vxnick> check the manual for bzr push - this will upload your repo to your server. If you want to get a copy of it on other machines, you use bzr branch on the URL
[16:32] <manuee> bzr info returns Standalone tree (format: pack-0.92)
[16:32] <vxnick> so when you make changes in future, commit then push again (you don't need to specify the server details each time), then others can use bzr pull to grab your changes
[16:32] <manuee> ok bzr help push --- reading...
[16:34] <dgoulet> Tak: it's working very well!
[16:34] <dgoulet> thanks a lot! I appreciate it!!
[16:35] <Tak> np
[16:35] <manuee> ow ok, bzr remove actualy deletes the files
[16:35] <manuee> lol good go know
[16:36] <vxnick> you can use --keep to keep them
[16:36] <manuee> ah awesome
[16:36] <manuee> im thinkin im only going to vc the theme for now
[16:36] <vxnick> you may as well do the whole thing, makes life easier :)
[16:37] <vxnick> and bzr revert should bring back those deleted files, if you want them
[16:38] <manuee> ah heheh
[16:40] <manuee> very handy
[16:46] <manuee> ok moment of truth
[16:47] <manuee> im using bzr push --creat-prefix sftp:/blabla --use-existing-dir
[16:47] <manuee> i hope it puts things into its place :X
[16:48] <vxnick> --use-existing-dir seems redundant as --create-prefix implies that you're pushing to a path that might not already exist
[16:48] <vxnick> but don't worry about it
[16:49] <manuee> i didnt use it the first time and it got me an error saying it doesnt have a valid .bzr directory
[16:50] <vxnick> ah, ok
[16:51] <manuee> "Created new branch."
[16:51] <manuee> looks like it worked no?
[16:51] <vxnick> you can test by branching it to another directory and making sure it pulls all the files
[16:52] <manuee> humm k i dont understand the whole branching deal it looks like
[16:53] <vxnick> branching means to copy the repository to another location
[17:09] <sohail|laptop> getting a wierd problem. I can use putty to connect to my host but when I do bzr+ssh, I get bzr: ERROR: socket.error: Socket is closed
[17:09] <sohail|laptop> the host that I am trying to bzr+ssh to is a mac
[17:09] <manuee> hmmm k it isnt working
[17:10] <manuee> i made a small change to a file to test, commited the change, ran bzr push, which looked ok, but the file didnt get updated on the server
[17:10] <sohail|laptop> hmm, sftp works
[17:10] <sohail|laptop> oh well
[17:11] <vxnick> manuee: the files don't actually end up on the server, just the contents of .bzr
[17:11] <manuee> ow
[17:11] <manuee> humm so im missing a step then?
[17:11] <vxnick> if you branch it though you'll see them :)
[17:11] <vxnick> nope you've done it correctly
[17:12] <vxnick> if you actually want the files to be uploaded to the server, look at the bzr-upload plugin
[17:15] <manuee> ow ok
[17:15] <manuee> thanks vxnick
[17:15] <vxnick> no prob :)
[17:17] <manuee> http://bazaar-vcs.org/BazaarUploadForWebDev =))
[17:18] <manuee> "No uploaded revision id found, switching to full upload"
[17:18] <vxnick> that's fine
[17:19] <manuee> ah its cause its the first time right
[17:19] <vxnick> yeah
[17:19] <manuee> oki
[17:24] <manuee> w00t its working
[17:24] <manuee> i dont htink i actualy need to push anything right
[17:25] <manuee> since im not versioning files over there
[17:27] <vxnick> you don't need to push it if your'e the only one using the repo
[17:29] <manuee> ah k, i think im starting to understand things
[17:30] <manuee> so to remove what i did using push, i just delete the .bzr directory on the server, and all is like before there
[17:30] <vxnick> yep
[17:30] <manuee> its nice it only adds it at one location, cvs is crazy like that (which is what the drupal proyect is under sigh)
[17:30] <vxnick> hehe
[17:30] <manuee> i can barely get my head around cvs to maintain a couple of proyects i have on there
[17:31] <manuee> everytime i have to look up the docs lol
[17:31] <vxnick> luckily bzr is a lot simpler :)
[17:31] <manuee> no doubt
[17:31] <manuee> thanks a ton for your help & patience vxnick
[17:31] <manuee> you helped a lot
[17:32] <vxnick> a pleasure
[18:28] <SamB> jelmer: so ... I pushed up some code to log SVN editor activity on lp:~naesten/bzr-svn/355143-replay/ ... I added it to PathStrippingDirectoryEditor and PathStrippingEditor. Not sure if that was the best place, thogh... what do you think?
[18:31]  * SamB wonders how to set a PDB breakpoint in code he can't/shouldn't edit without using the PDB shell ...
[18:35] <LarstiQ> SamB: edit code; import ipdb; ipdb.set_trace() ?
[18:38] <SamB> LarstiQ: I hesitate to do that to a module in the globally-installed standard library ;-)
[18:39] <LarstiQ> SamB: be fearless! ;)
[18:39] <LarstiQ> SamB: how about starting it with the pdb command then?
[18:39] <LarstiQ> you can set a break, and then continue
[18:40] <SamB> I guess I could do that
[18:40] <SamB> somehow I'd gotten it into my head that that would not work ;-)
[18:40] <SamB> say, where is debugging of bzr documented?
[18:42] <LarstiQ> SamB: HACKING I'd think
[18:42] <LarstiQ> SamB: you're aware of BZR_PDB and C-\ ?
[18:43] <SamB> LarstiQ: yeah
[18:43] <SamB> but it might be a good idea to remind folks that they can still use plain-old pdb?
[18:43] <LarstiQ> sure
[18:44] <LarstiQ> and the import pdb; pdb.set_trace() routine
[18:44] <SamB> LarstiQ: though the C-\ trick I picked up only by seeing sigquit listed somewhere related to BZR_PDB, and I think I found out that C-\ is the usual way to send one from wikipedia ...
[18:45] <LarstiQ> SamB: doh
[18:45] <SamB> maybe there should be an entry in the online help too?
[18:45] <SamB> it could even just say to look in some particular other place, for all I care
[18:45] <LarstiQ> SamB: it is mentioned in HACKING under Debugging
[18:46] <LarstiQ> SamB: right, good idea
[18:47] <SamB> oh, speaking of the online help ...
[18:48] <SamB> https://bugs.launchpad.net/bzr/+bug/408983
[18:51] <SamB> LarstiQ: does that not seem like a good idea?
[18:51] <SamB> like, practically essential even?
[18:52] <LarstiQ> SamB: not sure about essential, but I think it is a good idea too.
[18:52] <jelmer> this is why I don't like the online help system in bzr, we basically end up implementing our own documentation reader in the end :-(
[18:52] <SamB> jelmer: true
[18:53] <LarstiQ> jelmer: I'm fine with hooking up with `info`
[18:53] <jelmer> SamB: Thanks, I'll have a look
[18:53] <jelmer> sorry for answering in the wrong order :-)
[18:54] <SamB> jelmer: I'm not at all sure I've taken the right approach with that tracing, which is why I'm asking you to look at it
[18:55] <SamB> the more I think about it, the more I feel like it might be better to create a set of wrapper classes that, when the flag is enabled, wrap around the actual editors for tracing purposes
[18:56] <jelmer> SamB: right, that's what we do for transports
[18:56] <jelmer> SamB: see MutteringTransport
[18:56] <SamB> that was actually my first idea
[18:56] <SamB> ;-)
[18:57] <SamB> jelmer: so do you think I should go ahead and do that?
[18:57] <SamB> jelmer: and if so, where should I put them?
[18:58] <SamB> (and I really wish bzr had a concept of "interfaces", if only for documentation purposes ...)
[19:00] <SamB> jelmer: hmm ... what module is that in?
[19:00] <SamB> I found something a bit different-looking in bzrlib.transport.trace...
[19:04]  * SamB wishes bzr selftest could abbreviate test names like 'bzrlib.plugins.' => 'bp.'
[19:20] <SamB> hmm, would it be allowable for bzrlib to override unittest.TestResult._exc_info_to_string() ?
[19:23] <jelmer> SamB: sure, just put them in fetch.py
[19:24] <jelmer> SamB: technically, this is a subvertpy API
[19:24] <SamB> jelmer: point
[19:24] <SamB> I realized that pretty soon after mentioning that
[19:25] <SamB> but, if bzr used interfaces as defined by some standard and/or popular third-party library, subvertpy could too, couldn't it?
[19:25] <SamB> if only for documentation purposes?
[19:28] <SamB> jelmer: hmm, is bzr-svn considered to have a public API?
[20:32] <jelmer> SamB: other than the layout stuff, not really
[20:35] <jelmer> SamB: also, subvertpy._ra.Editor documents the Editor interface (just committed)
[20:53]  * SamB wishes one or the other of the python modes would highlight local variables somehow ...
[20:54] <SamB> heck, even highlighting variables name and attribute names differently would be helpful ...
[20:57] <SamB> jelmer: committed where exactly ?
[21:24] <RenatoSilva> how to rename tags?
[21:32] <SamB> doh. committed to subvertpy, duh ;-P ...
[21:37] <fullermd> RenatoSilva: No way, the name _is_ the tag.  But you can make a new tag with a different name pointing at the same place.
[21:41] <meuserj> The topic says that Launchpad is now open source... but I don't see anything about where to get it on launchpad.net...
[21:41] <RenatoSilva> fullermd: ok
[21:44] <beuno> meuserj, code.launchpad.net/launchpad
[21:45] <meuserj> duh.. it make sense that they would host their own card.
[21:45] <meuserj> err code
[22:24] <RenatoSilva> is there a way to search for a text that was added or removed in some commit? I have a new line which introduced a bug, and I want to remove it, but before I want to know why that line was inserted. So I want to find the commit which inserted that change. Any idea?
[22:26] <fullermd> annotate will tell you when a line was last changed (which may or may not be the insertion; you can step backward if it's not)
[22:26] <fullermd> Removed is obviously harder.
[22:32] <SamB> fullermd: I think he was hoping for a pickaxe
[22:33] <SamB> which would be seriously usefull, really
[22:37] <fullermd> I've got a splitting maul, is that close enough?
[22:39] <SamB> probably not
[22:51] <lifeless> RenatoSilva: bzr search can do that
[22:52] <RenatoSilva> it's a plugin, right?
[22:52] <lifeless> yes
[22:53] <lifeless> however, gannotate is probably best
[22:53] <RenatoSilva> is there a way to at least show a log including the diffs? Then I could use grep...
[22:53] <lifeless> as it can step through full lines
[22:53] <lifeless> log -p
[22:54] <RenatoSilva> Yeah, I just read this in the help, thanks!
[23:00] <RenatoSilva> lifeless: it was commit 1, and I discovered the reason it was added anyway..
[23:00] <RenatoSilva> thanks
[23:04] <SamB> jelmer: ... who is supposed to call close on an Editor ?
[23:40] <jelmer> SamB: whoever is reporting the changes
[23:41] <SamB> jelmer: well, I don't see it getting called on my tracing editors ...
[23:46] <Noldorin> LarstiQ: heya
[23:47] <Noldorin> LarstiQ: any news on the chmod issue?