Summary
This point release fixes minor issue. This happens with as few code modifications as possible, due not risking the stability. The fixes are backported from the latest dev branch.
Backups have never been removed by the "Remove backups older than" rule. Additionally the Manage profiles dialog didn't stored the rule's time units properly and also corrupted the config file. The next problem was that the schedule mode "Repeatedly (anacron)" using "Hourly" time units behaved sligthly different from the other time units. The behavior is now consistent and the documentation and tooltip updated accordingly. In case of "local encrypted" profiles (using gocryptfs) the "General" tab now contain a warning text recommending not to use that mode for new profiles. See more details about that warning.
Changelog
Added
- Migration warning in "General" tab for local encrypted profiles (32c6e8a)
Changed
- Schedule mode "Repeatedly (anacron)": GUI re-phrased and extended with explanations (#2507)
- GUI State "Show hidden files" is On by default
Fixed
- Missing backup removal due to a miscalculation in the "Remove backups older than" rule, introduced in version 1.5.4 (#2588#issuecomment-5675126121)
- "Remove backups older than" value was stored only as years (#2460)
- Enum names in config file are replaced by their values (related to #2460)
- Prevent crash when a plugin fails (#2447)
- Crash after add known_host (57bbab5)
- Schedule mode "Repeatedly (anacron)" using "Hourly" units is now consistent with other time units (#2507)
- Clear up license and copyright situation of
qt/serviceHelper.py(#1986)
For the complete list of changes, see the changelog. Compare with the previous release: v1.6.1...v1.6.2
Feedback
Please report regressions or unexpected behavior in the Issues section. Feel free to use other contact channels.
Installation
This release contains the source code only and does not include distribution packages. To build from source, please follow the build & installation instructions.
Contributors
Thank you to @gzuaps for reporting a heavy issue (#2604) that postponed the major release (2.0.0) and made it urgent to release a point release instead.