Packaged commit, from May 2015: 012f65f74744ed62a80abac6e9a8c86e71c2b6fa (was not updated since May 2015, either - except for mass rebuilds) Required commit, from August 2015: b743d92d3215f11c9b5ce8830fafe1f16786adf4 (or newer. latest commit right now is from January 2018, so ...) syncthing 0.14.44 uses the "NoSync" option, which isn't present in older versions. Ideally I would like to have this in fedora 27 (and maybe 26), too - because syncthing 0.14.44 has some important bug fixes, and I don't want to mess with upstream's database settings.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
Ping, can somebody take a look at this please? A newer version of this package would be nice on f27+ ...
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
Ping from December 2018: syncthing 0.14.53 now uses the ReadOnly database mode, which the leveldb package in fedora doesn't support. it was introduced upstream in May 2015, only a few days after the current snapshot was taken (commit 315fcfb05d4d46d4354b313d146ef688dda272a9). This time, I can't trivially patch out the missing functionality from syncthing, so this ancient package is blocking syncthing updates. I need a newer version of this package on fedora 28+. Otherwise I'll have to switch back to building syncthing from bundled dependencies.
Two weeks later, another ping.
Two weeks later, I've switched syncthing builds back to use vendored dependencies. I will revisit this once dependencies aren't ancient anymore.
This bug appears to have been reported against 'rawhide' during the Fedora 30 development cycle. Changing version to '30.
Still no changes, still relevant to rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle. Changing version to 31.
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.