Arch Linux User Repository

AT THIS POINT YOU ALMOST CERTAINLY WANT TO USE https://aur.archlinux.org/packages/syncthingtray-qt6 INSTEAD.

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.

I cannot update my system the normal way (with yay) because something breaks with syncthingtray.

The quick way (via yay) to do it is to update your system with the -d or --nodeps flag, which ignores the version and lets your system upgrade. Then you're left with a broken syncthingtray. To fix it, reinstall it with yay -S syncthingtray.

You need to rebuild this package against the new version of boost. I've already mentioned this in a previous comment:

The "dirty" way is forcing the installation (I suppose there's some pacman flag) or to uninstall the old version of syncthingtray temporarily. 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).

EDIT: I have also updated the pinned comment with these instructions.

I cannot update my system the normal way (with yay) because something breaks with syncthingtray. When I run yay, it bails out with:

error: failed to prepare transaction (could not satisfy dependencies) :: installing boost-libs (1.81.0-2) breaks dependency 'libboost_filesystem.so=1.80.0-64' required by syncthingtray

How to proceed?

No, just rebuild the package against the new version of boost.

A "normal" update from 1.2.4 to 1.3.0 without helpers and only using makepkg --nocheck will fail because of how dependencies are checked.

Not if one uninstalls the old version of syncthingtray before. Having to do that is not a big loss considering it would be broken in the meantime anyways (which is also the reason pacman complains). It is nice that Arch Linux lowers the entrance barrier for building packages by allowing one to invoke makepkg without chroot. When building leaf packages or other packages that do not require rebuilding further packages that is good enough. However, this simple approach has its limitations. That's also why official developers always use makechrootpkg. I cannot solve this limitation (and also not the maintainer of other AUR packages like ffmpeg-libfdk_aac). One can only point out workarounds or to use makechrootpkg. I personally don't use AUR helpers (just my own scripts / build service) but I believe there are AUR helpers out there that can help with using makechrootpkg (to make its use easier).

Martchus: Regarding frazar0 comment, I still think that not supporting AUR helpers (which is okay) and only being able to build/install it successfully using makechrootpkg or extra-x86_64-build are different things. A "normal" update from 1.2.4 to 1.3.0 without helpers and only using makepkg --nocheck will fail because of how dependencies are checked.

Once I've got feedback on https://github.com/Martchus/syncthingtray/issues/161 I'll add patches to this package. Until then, please use --nocheck or stop anything using port 8384 on your system before attempting the build.

@jackdinn I cannot give you support for AUR helpers. I don't use those myself. Somehow you need to find a way to pass flags to makepkg as mentioned in the pinned comment.

@Sintan I mentioned in my previous comments two other "dirty" ways that are likely even better and one clean way.

@frazar0 Using AUR helpers is definitely not what I'd call "normal". Maybe those helpers cannot handle so-dependencies very well. Note that this way of specifying dependencies is the preferred way now and many official packages use it as well. Those dependencies have the advantage that pacman will refuse breaking your system in case a soname changes. Note that other AUR packages with similar dependencies (like ffmpeg-libfdk_aac) aren't different.

I am surprised as to why the "normal" installation fails. I have tried with different AUR helpers, but only achieved failures:

$ yay -S syncthingtray
 -> Could not find all required packages:
    libc++utilities.so (Wanted by: syncthingtray)
    libqtutilities.so (Wanted by: syncthingtray)
    libqtforkawesome.so (Wanted by: syncthingtray)

$ paru -S syncthingtray
:: Resolving dependencies...
error: could not find all required packages:
    libqtutilities.so (wanted by: syncthingtray)
    libqtforkawesome.so (wanted by: syncthingtray)
    libc++utilities.so (wanted by: syncthingtray)

I often install AUR packages, and I was wondering: why does only the syncthingtray package present this issue?

Thank you for your work.