I dug into this for the elpa branch. I'm pretty sure there is a bug in bzr when it encounters a file named TREE_ROOT. (It seems to be assuming it should be at the root of the tree ('', '', 'TREE_ROOT') would be the meta-node at '/'.)
There is a "TREE_ROOT" node, which is packages/f90-interface-browser.
If you simply change the file-id for that directory, 'bzr co' works fine again. So the workaround at least is:
bzr mv packages/f90-interface-browser x
bzr mkdir packages/f90-interface-browser
bzr mv x/* packages/f90-interface-browser
bzr rm x
bzr commit -m "change the file-id for f90-interface-browser"
After doing the above, I can checkout the elpa branch without any problems.
I'm guessing we have some compatibility code for upgrades/etc which *shouldn't* be triggering for elpa, but is triggering accidentally.
But the workaround is pretty easy, and will be perfectly compatible with all bzr clients (so you won't need a new bzr just to work with the elpa branch.)
I dug into this for the elpa branch. I'm pretty sure there is a bug in bzr when it encounters a file named TREE_ROOT. (It seems to be assuming it should be at the root of the tree ('', '', 'TREE_ROOT') would be the meta-node at '/'.)
There is a "TREE_ROOT" node, which is packages/ f90-interface- browser.
If you simply change the file-id for that directory, 'bzr co' works fine again. So the workaround at least is:
bzr mv packages/ f90-interface- browser x f90-interface- browser f90-interface- browser browser"
bzr mkdir packages/
bzr mv x/* packages/
bzr rm x
bzr commit -m "change the file-id for f90-interface-
After doing the above, I can checkout the elpa branch without any problems.
I'm guessing we have some compatibility code for upgrades/etc which *shouldn't* be triggering for elpa, but is triggering accidentally.
But the workaround is pretty easy, and will be perfectly compatible with all bzr clients (so you won't need a new bzr just to work with the elpa branch.)