Package Details: syncthingtray 1.5.2-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
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 87
Popularity: 2.32
First Submitted: 2016-09-14 20:13 (UTC)
Last Updated: 2024-04-09 14:19 (UTC)

Required by (0)

Sources (1)

Pinned Comments

Martchus commented on 2016-10-31 11:39 (UTC) (edited on 2024-03-06 16:44 (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
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.

Important remarks:

  • 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 usually also 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

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »

Martchus commented on 2022-01-11 16:34 (UTC)

When using my binary repo then Manjaro packages might be too old, indeed. Switching to the Git version doesn't help in this case at all, at least not using the version from my binary repo.

When building the package from sources one has to take care of rebuilding if a dependency changes its soname - regardless whether Manjaro or normal Arch is used. The only convenience Arch users have is that I usually bump pkgrel as needed (so e.g. their AUR helper does the rebuild as needed). Building packages from sources is also what my last comment was about.

Switching to the Git version likely helped in your case because that obviously means doing a new build so you've got the required rebuild. (But you could have just rebuilt the normal package as well.)

reefland commented on 2022-01-11 16:25 (UTC)

@Martchus - my understanding was that when using Manjaro, he has to wait until their packages catch up. If he wants it to work today, switch repos. My apologies if that is technically not accurate, but it worked as a solution for me, even if just luck.

Martchus commented on 2022-01-11 15:55 (UTC)

@reefland Whether using the Git or normal version makes not really a difference. You'll need to rebuild regardless which package you use. Of course rebuilding the package more frequently increases the chance of rebuilding it when it is required but that's just luck and I wouldn't sell it as solution.

reefland commented on 2022-01-11 15:33 (UTC)

@Oleg_Andreych - if using Manjaro switch to "syncthingtray-git" repo instead to resolve the message you see.

Martchus commented on 2022-01-11 11:29 (UTC)

@Oleg_Andreych Also read the pinned comment.

SanskritFritz commented on 2022-01-11 09:21 (UTC) (edited on 2022-01-11 09:22 (UTC) by SanskritFritz)

Oleg 1. don't run Manjaro :D but if you must, 2. rebuild the package after a system upgrade. And 3. read the pinned comment.

Oleg_Andreych commented on 2022-01-11 07:11 (UTC)

syncthingtray doesn't start with an error:

syncthingtray: error while loading shared libraries: libboost_filesystem.so.1.76.0: cannot open shared object file: No such file or directory

boost-libs package version is 1.78.0-1.

I'm running Manjaro.

Martchus commented on 2022-01-03 12:09 (UTC)

@Harvie It makes still sense to report test failures. But please include the actual error message and not just the last few lines.

Harvie commented on 2022-01-03 12:05 (UTC)

This worked for me to install it using yay: yay --mflags "--nocheck" -S syncthingtray

« First ‹ Previous 1 .. 3 4 5 6 7 8 9 10 11 12 13 Next › Last »