aboutgitcodebugslistschat
path: root/contrib
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2025-03-19 16:14:23 +1100
committerStefano Brivio <sbrivio@redhat.com>2025-03-19 17:17:18 +0100
commitc250ffc5c11385d9618b3a8165e676d68d5cbfa2 (patch)
tree419db89512ffc2765154ef2a7466346ce56de385 /contrib
parentcfb3740568ab291d7be00e457658c45ce9367ed5 (diff)
downloadpasst-c250ffc5c11385d9618b3a8165e676d68d5cbfa2.tar
passt-c250ffc5c11385d9618b3a8165e676d68d5cbfa2.tar.gz
passt-c250ffc5c11385d9618b3a8165e676d68d5cbfa2.tar.bz2
passt-c250ffc5c11385d9618b3a8165e676d68d5cbfa2.tar.lz
passt-c250ffc5c11385d9618b3a8165e676d68d5cbfa2.tar.xz
passt-c250ffc5c11385d9618b3a8165e676d68d5cbfa2.tar.zst
passt-c250ffc5c11385d9618b3a8165e676d68d5cbfa2.zip
migrate: Bump migration version number
v1 of the migration stream format, had some flaws: it didn't properly handle endianness of the MSS field, and it didn't transfer the RFC7323 timestamp. We've now fixed those bugs, but it requires incompatible changes to the stream format. Because of the timestamps in particular, v1 is not really usable, so there is little point maintaining compatible support for it. However, v1 is in released packages, both upstream and downstream (RHEL at least). Just updating the stream format without bumping the version would lead to very cryptic errors if anyone did attempt to migrate between an old and new passt. So, bump the migration version to v2, so we'll get a clear error message if anyone attempts this. We don't attempt to maintain backwards compatibility with v1, however: we'll simply fail if given a v1 stream. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'contrib')
0 files changed, 0 insertions, 0 deletions