On Jun 20 2017, joseph via s3ql <[email protected]> wrote:
> jessie has s3ql 2.11.1, stretch has 2.21.
>
> NEWS.Debian.gz seems to indicate I need to upgrade via the intermediate
> version 2.14, is this correct?
No, this should work out of the box. Debian ships a special patch to
enable backwards compatibility with jessie.
> root@ns3022725:~# s3qladm upgrade
> s3://echo-maher-org-uk-backup/
>
> Getting file system parameters..
> ERROR: Uncaught top-level exception:
> Traceback (most recent call last):
> File "/usr/lib/s3ql/s3ql/common.py", line 564, in thaw_basic_mapping
> d = literal_eval(buf.decode('utf-8'))
> UnicodeDecodeError: 'utf-8' codec can't decode byte 0x80 in position 0:
> invalid start byte
Hmm. That looks like a bug.
Are you confident that the filesystem was unmounted cleanly the last
time it was mounted? In that case you can try a workaround: temporarily
move the "s3:=2F=2Fecho-maher-org-uk-backup*" files from ~/.s3ql/
somewhere else and re-try the upgrade. Does that help?
Do you still have access to a jessie system? If so, can you reproduce
the problem with a freshly created file system?
Best,
-Nikolaus
--
GPG Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
