[00:00] this is what I got when I ran it: [00:00] $ bzr split src [00:00] bzr: ERROR: No WorkingTree exists for "file:///home/dave/Projects/dswc/src/.bzr/checkout/". [00:00] Where are you when you do that? [00:00] also, it's a 9 year old repository, so I had to upgrade the format to be able to do the split in the first place [00:01] I'm in the project root [00:01] so, home/dave/Projects/dswc [00:01] What's bzr info tell you? [00:01] Unshared repository with trees (format: pack-0.92) [00:01] Location: [00:01] repository: . [00:01] 'k, so you're not in a branch. [00:02] Gotta be in the branch/WT in question. [00:02] wait, that was inside src [00:03] bzr info in dswc says standalone tree and gives the expected information [00:04] Mmph. So you've got a repo _underneath_ a branch? That sounds like a recipe for surprises... [00:04] that's what happened after I did the split, afaik [00:04] Mmm. Well, that would be a little more expected... [00:05] Sounds like you've got some halfway stuff around. [00:05] halfway stuff? like uncommitted changes? [00:05] More like part of a split, or part of an init/init-repo, or whatnot... [00:06] Though, actually, I'm not sure pack-0.92 is even rich root, so that might cause weird failure too. [00:06] I'd make a fresh scratch branch nowhere near anything extant (in /tmp or the like, say), make sure it's 2a format, and try from scratch there. [00:06] ah, ok, I figured out what I did wrong :) [00:06] I should have done "bzr split ." from inside src [00:07] I did it all over again with that change and it appears to be working now [00:07] so, am I guaranteed not to have the ability to access commits from the rest of the project now? [00:07] it's a website that's has private sources, but I'm spinning off the scripts I use to generate it so I can release those publicly [00:08] Pretty sure none of the content will be in the new branch, no. [00:08] The commit messages would be the same, so stuff touching both inside and out may have stuff in the logs you want to hide. Or not, depending on your commit messages. [00:10] don't care about that. It's also not that big of a deal if old stuff gets out, but it's better to start with a fresh repo and no history than to have other people digging through my website sources ;) [00:11] ok, so I get something like this after the split (I'm only including a couple of lines of output) [00:11] $ bzr status [00:11] removed: [00:11] .bzrignore [00:11] .dswc_data/ [00:12] where .dswc_data is part of the original project, and there's a list of all the files that are gone now. [00:14] ok, last question. [00:15] Is this the expected behavior if I try to revert to a revision number from before the split? [00:15] $ bzr revert -r 257 [00:15] bzr: ERROR: Key src-20090728034756-vx3lt2pqch83qh4t-1 is already present in map [00:15] * fullermd frowns. [00:16] Well. I thought split made a new history, but I guess it doesn.t [00:16] So, let's agree I never said anything in the first place, so I look smarter. [00:16] well, it didn't actually do the revert [00:17] That's pretty likely a bug, from the somewhat weird post-split state. [00:17] Apparently all split does is rm a bunch of stuff and pivot the root. That root state is probably an edge case revert doesn't grok. [00:21] Maybe there's someting in the rewrite plugin that'll do the job? I don't really know it... [00:21] well, the .bzr directory is 54MB, which is consistent with it actually having all the other files in it [00:22] so, I guess I'll just export from bzr and start with a brand new repository? [00:23] Yeah, simplest. [00:24] well, thanks for the help. Have a good weekend. ;)