Bug 247860 - net/syncthing: Update to v1.7.0
Summary: net/syncthing: Update to v1.7.0
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Steve Wills
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-09 01:04 UTC by Adam Jimerson
Modified: 2020-07-13 15:27 UTC (History)
0 users

See Also:
bugzilla: maintainer-feedback? (swills)


Attachments
syncthing-v1.7.0.diff (918 bytes, patch)
2020-07-09 01:04 UTC, Adam Jimerson
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Jimerson 2020-07-09 01:04:53 UTC
Created attachment 216333 [details]
syncthing-v1.7.0.diff

This patch updates Syncthing to v1.7.0.

Changelog:

This release performs a database migration to optimize for clusters with
many devices.

Bugfixes:

#6552: panic: Stop called more than once on ... created by nat.Service
#6564: Closing an already removed connection causes GUI error message
#6646: Misleading error message when to be deleted dir contains receive-only changes
#6653: panic: nil pointer dereference in leveldb.(*DB).isClosed()
#6654: panic: runtime error: index out of range in processNeeded()
#6655: panic: nil pointer dereference in checkUpgrade()
#6679: QUIC listener is not added when default TCP port is unavailable
#6697: Malformed listen address causes hang on startup
#6706: Changing a folder in web UI removes introduced-by info
Enhancements:

#1830: "Folder path missing" when folder path is a junction
#4703: Suggest setting up auth on initial startup
#5910: Add Badger database backend for testing and consideration
#6372: Reduce database size by optimizing version list storage
Other issues:

#6608: Data race in Windows fs watcher tests
#6625: TestRequestRemoteRenameChanged is racy/flaky
Comment 1 Steve Wills freebsd_committer 2020-07-13 14:15:27 UTC
Sorry, missed this, was committed in ports r541833 (rP541833)
Comment 2 Adam Jimerson 2020-07-13 15:27:29 UTC
(In reply to Steve Wills from comment #1)

No worries, that commit happened not long after I opened this. Just glad to see that it got updated :).