serious 'bug'?

[Steve Franks]

Something that's supposed to 'just work' is not supposed to eat my
files...I'm sure it's something I 'did' as opposed to an actual bug,
but all I did was commit a single changed file, so it's way over my
head.  Then again, things are transparently broken with zero error
messages, so maybe it really *is* a bug.  But I'm no expert, I'm an
EE, not a real coder.

This is really unbelievable.  I committed (successfully according to
my local terminal), and the next day I find out the folder I was
working in (couple levels down the tree) *disappeared* from the
'server'.  It's actually still there on the 'client', so it's not like
I was trying to remove it.  As far as the client knows, every thing's
still fine.  bzr status shows 100% match between working/client and
server.  I can go on the server as bzr and as root, and the folder
really is gone.  I can add the folder from the client, and it thinks
it's already there.  branch.conf is clearly pointing at the server
like always.  I can ssh to the server and the file isn't there.  The
file *was* previously on the server, because all the other client
boxes that I use show the folder as gone (they are actually more
confused, because they still expect the folder to be on the server and
it isn't, so they barf on commit).  Also, I'm the only one using this
repository (although from 3 or 4 locations), so there's no outside
sources of corruption.

I can't even fix this without going to a backup (maybe not even then),
cause all the boxes involved think their working copy is correct, but
none of them match.  It's a real pcloadletter kind of day.  I'm stuck
using gmail for version control.

Best,
Steve

"My version control software is the single most important application
I use.  It needs to be rock solid.  I thought it was until today.  I
can't just drive across the continent to 'pick up' a missing file when
I'm traveling."