| 1 |
On 7/15/19 1:39 PM, Marek Szuba wrote: |
| 2 |
|
| 3 |
> 2019-07-18-syncthing-update-incompatibility.en.txt |
| 4 |
> |
| 5 |
> Title: Syncthing 1.2.0 and newer do not interoperate with 0.14.45 and older |
| 6 |
> Author: Marek Szuba <marecki@g.o> |
| 7 |
> Posted: 2019-07-18 |
| 8 |
> Revision: 1 |
| 9 |
> News-Item-Format: 2.0 |
| 10 |
> Display-If-Installed: net-p2p/syncthing |
| 11 |
> |
| 12 |
> Starting with version 1.2.0, Syncthing always uses large, variable-sized, |
| 13 |
> blocks to index and transfer files larger than 256 MiB [1]. Syncthing |
| 14 |
> version 0.14.45 and older will initially appear to accept files scanned |
| 15 |
> with large blocks, but will later panic during some internal file |
| 16 |
> operations. Do NOT enable large blocks in clusters with devices still |
| 17 |
> on v0.14.45 or older, |
| 18 |
|
| 19 |
Should we be more specific as to how not to enable it here? is it a |
| 20 |
USE-flag? does it require a package mask for newer versions if it is |
| 21 |
always used for the newer ones? |
| 22 |
|
| 23 |
Also cluster immediately made me think of server<>client relationship |
| 24 |
and this only affecting server side, which probably doesn't fit well |
| 25 |
with syncthing, but admittedly I don't use it so not familiar with the |
| 26 |
nomenclature. |
| 27 |
|
| 28 |
> e.g. Debian Stretch servers using official packages. |
| 29 |
> |
| 30 |
> [1] https://docs.syncthing.net/advanced/folder-uselargeblocks.html |
| 31 |
|
| 32 |
|
| 33 |
-- |
| 34 |
Kristian Fiskerstrand |
| 35 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 36 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives