package: s3ql severity: grave version: 2.11.1+dfsg-1 Justification: Renders filesystem unusable and data accessible
Hi.
I'm upgrading a system from wheezy to jessie.
Wheezy ships s3ql 1.11, jessie ships version 2.11.
I have a filesystem that I can easily mount and fsck in wheezy, but when
I try to run the jessie s3qladm upgrade command I get:
Getting file system parameters..
File system revision too old to upgrade!
You need to use an older S3QL version to upgrade to a more recent
revision before you can use this version to upgrade to the newest
revision.
Uncaught top-level exception:
Traceback (most recent call last):
File "/usr/bin/s3qladm", line 9, in <module>
load_entry_point('s3ql==2.11.1', 'console_scripts', 's3qladm')()
File "/usr/lib/s3ql/s3ql/adm.py", line 96, in main
options.cachedir))
File "/usr/lib/s3ql/s3ql/adm.py", line 316, in upgrade
print(get_old_rev_msg(param['revision'] + 1, 's3qladm'))
File "/usr/lib/s3ql/s3ql/adm.py", line 224, in
get_old_rev_msg
''' % { 'version': REV_VER_MAP[rev],
KeyError: 17
It's critical that there be a documented procedure that works for
upgrading from the version in wheezy to the version in jessie using
tools in jessie.
There was another upgrade at version 2.5, which is not in either wheezy
or jessie. However, it needs to be possible to upgrade from one Debian
release to the next using the software in Debian.
I believe this problem is important enough to fix in a Jessie point
release and would be happy to help with any process issues that come up
in making that happen.
pgpqzly9nonTg.pgp
Description: PGP signature
