You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used chocolaty to install syncthing and update it regularly as well.
Here is a log of the last update:
syncthing v1.11.1 [Approved]
syncthing package files upgrade completed. Performing other installation steps.
Extracting 64-bit C:\ProgramData\chocolatey\lib\syncthing\tools\syncthing-windows-amd64-v1.11.1_x64.zip to C:\ProgramData\chocolatey\lib\syncthing\tools...
C:\ProgramData\chocolatey\lib\syncthing\tools
Environment Vars (like PATH) have changed. Close/reopen your shell to
see the changes (or in powershell/cmd.exe just type `refreshenv`).
ShimGen has successfully created a shim for syncthing.exe
ShimGen has successfully created a shim for syncthing.exe
ShimGen has successfully created a shim for syncthing.exe
ShimGen has successfully created a shim for syncthing.exe
ShimGen has successfully created a shim for syncthing.exe
ShimGen has successfully created a shim for syncthing.exe
The upgrade of syncthing was successful.
Software installed to 'C:\ProgramData\chocolatey\lib\syncthing\tools'As you see here the 1.11.1 version of syncthing was installed, and ShimGen reported that it successfully created shims. However starting syncthing via the shim starts an old version:
Based on some changes happening to the Chocolatey repositories, this issue has been moved from the chocolatey/shimgen repository to the chocolatey/home repository.
I used chocolaty to install syncthing and update it regularly as well.
Here is a log of the last update:
I would have expected that the most current version is started.
The reason is probably that the
syncthing
chocolatey packages installs multiple versions and shingen uses lexical order for creating the shims:IDK if this is a shimgen, a chocolatey or a syncthing packaging issue.
┆Issue is synchronized with this Gitlab issue by Unito
The text was updated successfully, but these errors were encountered: