Hi,
I recently performed an upgrade from 2.12 to 2.14 (no 2.13 in between,
since that version never made it into the gentoo/funtoo tree), and
wanted to share my experience with others. First, 's3qladm upgrade'
was giving the following error.
>>>>>>
Requesting new access token
Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/lib/python-exec/python3.3/s3qladm", line 9, in <module>
load_entry_point('s3ql==2.14', 'console_scripts', 's3qladm')()
File "/usr/lib64/python3.3/site-packages/s3ql/adm.py", line 87, in main
with get_backend(options) as backend:
File "/usr/lib64/python3.3/site-packages/s3ql/common.py", line 260,
in get_backend
getattr(options, 'compress', ('lzma', 2)), raw)()
File "/usr/lib64/python3.3/site-packages/s3ql/common.py", line 340,
in get_backend_factory
backend.fetch('s3ql_passphrase')
File "/usr/lib64/python3.3/site-packages/s3ql/backends/common.py",
line 351, in fetch
return self.perform_read(do_read, key)
File "/usr/lib64/python3.3/site-packages/s3ql/backends/common.py",
line 107, in wrapped
return method(*a, **kw)
File "/usr/lib64/python3.3/site-packages/s3ql/backends/common.py",
line 314, in perform_read
fh = self.open_read(key)
File "/usr/lib64/python3.3/site-packages/s3ql/backends/common.py",
line 107, in wrapped
return method(*a, **kw)
File "/usr/lib64/python3.3/site-packages/s3ql/backends/s3c.py", line
307, in open_read
meta = self._extractmeta(resp, key)
File "/usr/lib64/python3.3/site-packages/s3ql/backends/s3c.py", line
715, in _extractmeta
raise CorruptedObjectError('Invalid metadata format: %s' % format_)
s3ql.backends.common.CorruptedObjectError: Invalid metadata format: raw
>>>>>>
This lead me back to Martin van Es' 1.19 to 2.14 upgrade thread from
last month, where an intermediate upgrade to 2.13 seemed to be
indicated...
On Wed, Sep 16, 2015 at 3:15 AM, Martin van Es <[email protected]> wrote:
> $ wget http://s3ql.googlecode.com/files/s3ql-2.13.tar.bz2
> || wget https://bitbucket.org/nikratio/s3ql/downloads/s3ql-2.13.tar.bz2
> $ tar xjf s3ql-2.13.tar.bz2
> $ (cd s3ql-2.13; ./setup.py build_ext)
> $ s3ql-2.13/bin/s3qladm <options>
When I tried this procedure, the s3qladm command gave the following error.
>>>>>>
Traceback (most recent call last):
File "s3ql-2.13/bin/s3qladm", line 25, in <module>
import s3ql.adm
File "/root/temp/s3ql-2.13/src/s3ql/adm.py", line 17, in <module>
from .metadata import restore_metadata, cycle_metadata, dump_metadata
File "/root/temp/s3ql-2.13/src/s3ql/metadata.py", line 11, in <module>
from .deltadump import INTEGER, BLOB, TIME, dump_table, load_table
ImportError: No module named 's3ql.deltadump'
>>>>>>
Instead, I needed to use './setup.py build_cython build_ext --inplace'
as indicated by Nikolaus in this ticket:
https://bitbucket.org/nikratio/s3ql/issues/118/no-module-named-s3qldeltadump-running
After this, 's3qladm upgrade' from 2.13 worked fine, and 2.14
(installed from portage) had no complaints.
--
-:-:- David K. Gasaway
-:-:- Email: [email protected]
--
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.
