Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#42070 - [syncthing] Change build.sh arguments to properly tag noupdate
Attached to Project:
Community Packages
Opened by Alex W (awh) - Monday, 22 September 2014, 19:18 GMT
Last edited by Martin Wimpress (flexiondotorg) - Wednesday, 24 September 2014, 09:10 GMT
Opened by Alex W (awh) - Monday, 22 September 2014, 19:18 GMT
Last edited by Martin Wimpress (flexiondotorg) - Wednesday, 24 September 2014, 09:10 GMT
|
DetailsThe syncthing build system changed so doing './build.sh "" -tags noupgrade' won't properly add the tag and updates will still be enabled.
Instead, the argument was changed to './build.sh noupgrade' See https://github.com/syncthing/syncthing/issues/730 |
This task depends upon
Closed by Martin Wimpress (flexiondotorg)
Wednesday, 24 September 2014, 09:10 GMT
Reason for closing: Fixed
Wednesday, 24 September 2014, 09:10 GMT
Reason for closing: Fixed
Comment by Martin Wimpress (flexiondotorg) -
Tuesday, 23 September 2014, 16:23 GMT
If syncthing is built using './build.sh noupgrade' or 'go run build.go -no-upgrade build' it doesn't produce any executables in `bin/`. So, that sucks. I'll get in touch upstream.
Comment by Martin Wimpress (flexiondotorg) -
Wednesday, 24 September 2014, 09:10 GMT
syncthing-0.9.17-2 has been released and fixes this issue.