A compatibility question

[Mark Hewitt]

Currently, main will not save to an older bup server - I was just
wondering what the migration path was likely to be - either to insist
upon updating servers (which will presumably support older clients) or
have a fallback operating mode for later bup clients to support older
servers.

Of course, it may be that this is just another of those pesky __del()__
assertions that could be ignored with a warning, but has not yet been
tackled in main!

This is what I see when testing a remote save to an older (0.33.10) bup
server with a client built from main:

> # /usr/local/bin/bup
> --bup-dir=/bupsys/var/bupcache/remote-bupman/local.bup/disker.bup save
> --verbose --commit --compress=9 --name=disker-root
> --indexfile=/bupsys/var/bupcache/remote-bupman/indexes/disker-root.index
> --verbose
> --remote=bup@bupman:/bupsys/data/External-013/bupdata/repository/disker /
> error: server does not appear to provide config-get commandException
> ignored in: <function RemoteRepo.__del__ at 0x7fffa5825a80>
> Traceback (most recent call last):
>   File "/usr/local/lib/bup/bup/repo/remote.py", line 47, in __del__
>     def __del__(self): assert self.closed
> AssertionError:
> Exception ignored in: <function Client.__del__ at 0x7fffa580c220>
> Traceback (most recent call last):
>   File "/usr/local/lib/bup/bup/client.py", line 352, in __del__
>     def __del__(self): assert self.closed
> AssertionError:
> Exception ignored in: <function Client.ViaSsh.__del__ at 0x7fffa57ffb00>
> Traceback (most recent call last):
>   File "/usr/local/lib/bup/bup/client.py", line 217, in __del__
>     def __del__(self): assert self._closed
> AssertionError:
> Exception ignored in: <function BaseConn.__del__ at 0x7fffa60693a0>
> Traceback (most recent call last):
>   File "/usr/local/lib/bup/bup/helpers.py", line 431, in __del__
>     def __del__(self): assert self._base_closed
> AssertionError:
> #

--
Mark J Hewitt

[Greg Troxel]

Mark Hewitt <mjh.br...@gmail.com> writes:

> Currently, main will not save to an older bup server - I was just
> wondering what the migration path was likely to be - either to insist
> upon updating servers (which will presumably support older clients) or
> have a fallback operating mode for later bup clients to support older
> servers.

Does it really not save, or just save and emit a pesky assertion?

I would say that it is a requirement that main can save to 0.33.x.
Users would see it as a serious regression if not. But I think it
actually can.

> Of course, it may be that this is just another of those pesky
> __del()__ assertions that could be ignored with a warning, but has not
> yet been tackled in main!
>
> This is what I see when testing a remote save to an older (0.33.10)
> bup server with a client built from main:

I see this too.