Package Details: syncthingtray 1.7.7-1

Git Clone URL: https://aur.archlinux.org/syncthingtray.git (read-only, click to copy)
Package Base: syncthingtray
Description: Tray application for Syncthing
Upstream URL: https://github.com/Martchus/syncthingtray
Licenses: GPL-2.0-or-later
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 93
Popularity: 0.69
First Submitted: 2016-09-14 20:13 (UTC)
Last Updated: 2025-05-06 12:23 (UTC)

Pinned Comments

Martchus commented on 2016-10-31 11:39 (UTC) (edited on 2025-05-03 08:48 (UTC) by Martchus)

All my packages are managed at GitHub where you can also contribute directly: https://github.com/Martchus/PKGBUILDs
There also exist a binary repository: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#ownstuff

Important remarks:

  • Switch to the Qt 6 based version. There is probably no good reason to still use the Qt 5 based version under GNU/Linux.
  • The packages within the binary repository are built against the latest packages from Arch Linux and hence might not be compatible with Manjaro. This can be the cause when the Plasmoid doesn't work.
  • Like with any other package a rebuild is required when the soname of a dependency like boost changes (see e.g. https://github.com/Martchus/syncthingtray/issues/98). The package in my binary repository should be rebuilt in a timely manner. I'm also sometimes updating pkgrel of the AUR package when a rebuild is required (only in accordance with Arch Linux of course, not in accordance with Manjaro).
    • The "dirty" way is forcing the installation/update (leaving syncthingtray broken until it has been rebuilt) or to uninstall syncthingtray temporarily before the update. After the update syncthingtray can be rebuilt and reinstalled again.
    • The correct solution is to use makechrootpkg which is also how official developers build their packages (and how packages in my binary repository are built).
  • It is required to build dependencies (that are not provided by Arch Linux itself) before building this package. So you need to build c++utilities, qtutilities, qtforkawesome and syncthingtray in that order.
  • The KDE integrations have been ported to KDE 6 but building them for KDE 5 should still work. This package does not build any KDE integrations by default because KDE 6 is now in the main repositories. To build KDE integrations for KDE 6 you need to install syncthingtray-qt6 instead of this package.
  • Note that the tests of this package might fail despite there's nothing wrong (e. g. because Syncthing is just too slow and the test runs in a timeout). To ignore those false-positives, build the package with makepkg --nocheck or makechrootpkg -- --nocheck. It makes still sense to report failures. But please include the actual error message and not just the last few lines.

Latest Comments

1 2 3 4 5 6 .. 14 Next › Last »

Martchus commented on 2025-05-07 09:13 (UTC)

@Sabu Because Syncthing Tray depends on Boost which breaks its ABI on every release. That's generally a good thing as it allows for a better evolution of that library and users don't need to care about it - only developers/distributors. As an AUR "user" you are unfortunately put into the role of a distributor by having to build packages yourself. Even if using my binary repo this is problematic because there will always be a small delay between official repos and me catching up with them.

I could mitigate this by linking statically against Boost but this would go against the usual packaging practices.

Sabu commented on 2025-05-07 00:36 (UTC) (edited on 2025-05-07 00:38 (UTC) by Sabu)

During the upgrade today I got the error unable to satisfy dependency libboost_filesystem.so=1.87.0-64 required by syncthingtray-qt6 but boost-libs 1.88.0-2 is installed which provides libboost_filesystem.so=1.88.0-64.

A more generic question, why I get more often these annoying dependency errors with syncthing in comparison to the other thousands of installed packages?

Martchus commented on 2025-05-03 08:45 (UTC)

And you probably want to take this opportunity to finally switch to the Qt 6 based version at this point.

jestarray commented on 2025-05-03 05:09 (UTC)

If you get boost breaking, uninstall syncthingtray, update boost, and then run: paru -S syncthingtray --rebuild

Martchus commented on 2024-09-03 08:24 (UTC)

Please read the comments and do not flag the package. Simply rebuild the package against the latest version of boost.

Martchus commented on 2024-09-03 07:45 (UTC)

There's nothing to fix, see the pinned comment and the other comment on the Qt 6 based version.

mmtech2012 commented on 2024-09-03 05:56 (UTC)

Hi thank you for your amazing package. please fix the problem with resolving dependencies... warning: cannot resolve "libboost_filesystem.so=1.83.0-64", a dependency of "syncthingtray" as you know the name of the boost library changed. :: installing boost-libs (1.86.0-1) breaks dependency 'libboost_filesystem.so=1.83

Martchus commented on 2024-06-03 12:30 (UTC)

I can look into it later. Note that at this point you probably want to use syncthingtray-qt6.

tietze commented on 2024-06-03 12:16 (UTC) (edited on 2024-06-03 12:20 (UTC) by tietze)

Thanks for your work! Hope this can help. Passing --nocheck to makepkg makes it build. Otherwise it fails at the WizardTests:. Part of log below, full test log here: https://file.io/Bkf8rExdgR1Z

********* Start testing of WizardTests *********
Config: Using QtTest library 5.15.14, Qt 5.15.14 (x86_64-little_endian-l
p64 shared (dynamic) release build; by GCC 14.1.1 20240522), arch unknow
n
QDEBUG : WizardTests::initTestCase() "HOME dir: /tmp/syncthingwidgets_wizard_tests-ACNtCz"
PASS   : WizardTests::initTestCase()
PASS   : WizardTests::testShowingSettings()
QWARN  : WizardTests::testConfiguringLauncher() This plugin does not support propagateSizeHints()
QWARN  : WizardTests::testConfiguringLauncher() This plugin does not support propagateSizeHints()

=== Received signal at function time: 300000ms, total time: 300087ms, dumping stack ===
=== End of stack trace ===
QFATAL : WizardTests::testConfiguringLauncher() Test function timed out
FAIL!  : WizardTests::testConfiguringLauncher() Received a fatal error.
   Loc: [Unknown file(0)]
Totals: 2 passed, 1 failed, 0 skipped, 0 blacklisted, 300090ms
********* Finished testing of WizardTests *********
<end of output>
Test time = 300.52 sec
----------------------------------------------------------
Test Failed.
"syncthingwidgets_run_wizard_tests" end time: Jun 03 14:01 CEST
"syncthingwidgets_run_wizard_tests" time elapsed: 00:05:00
----------------------------------------------------------

End testing: Jun 03 14:01 CEST