Bazaar Won't Commit or Update

[Wichmann, Mats D]

On Wed, Sep 28, 2011 at 1:21 AM, A. S. Budden <abudden at gmail.com> wrote:

>
> > If you are missing one, you can just "mkdir obsolete_packs/" and
> > "mkdir upload/", and probably the same for lock/. For the others, if
> > they are missing, you've lost critical data.
>
> As you correctly surmised, it was the upload directory that was
> missing: creating this directory fixed the problem.  All of the rest
> of the entries (except no-working-trees and shared-storage) were
> present.
>
> > I would also recommend trying to investigate why an empty directory
> > might be being deleted by your OS/whatever. Otherwise this will just
> > happen again.
>
> Indeed: this does concern me slightly, but I don't know that it's
> going to be straightforward to work out how it happened...
>
>

Is there a way to diagnose this sort of problem a little more cleanly than
fishing for advice on the mailing list?  I remember now I fell into this
trap once
a long while ago; I had a bunch of branches sitting on a storage-limited
device (in fact, a virtual machine where "disk" was preallocated and I
hadn't anticipated how I'd use it).  I figured one way to save space was
to remove the obsolete_packs, which after all were just a backup in
case the pack operation failed (Is that right?).  I guess I assumed the
directory would just be recreated on need and so its absence would be
no problem, but indeed I broke the branches instead... all my fault,
but bzr's reporting was "not useful" either nor do I understand why that
particular situation needs to be a fatal error.

(now of course I know to only remove the /contents/ of obsolete_packs
if I have this need)

-- mats
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/bazaar/attachments/20110928/3b657f11/attachment.html>