Package Details: syncthingtray-qt6 1.7.7-1

Git Clone URL: https://aur.archlinux.org/syncthingtray-qt6.git (read-only, click to copy)
Package Base: syncthingtray-qt6
Description: Tray application for Syncthing (using Qt 6)
Upstream URL: https://github.com/Martchus/syncthingtray
Licenses: GPL-2.0-or-later
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 32
Popularity: 2.02
First Submitted: 2020-11-07 16:16 (UTC)
Last Updated: 2025-05-06 12:23 (UTC)

Pinned Comments

Martchus commented on 2023-11-21 23:20 (UTC) (edited on 2024-10-21 15:10 (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:

  • 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-qt6 broken until it has been rebuilt) or to uninstall syncthingtray-qt6 temporarily before the update. After the update syncthingtray-qt6 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-qt6, qtforkawesome-qt6 and syncthingtray-qt6 in that order.
  • The KDE integrations have been ported to KDE 6. This package builds KDE integrations for KDE 6 by default as KDE 6 is now in the main repositories.
  • 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 2 3 4 5 6 7 .. 9 Next › Last »

OzzyHelix commented on 2025-02-09 02:48 (UTC)

whoever is maintaining the chaotic aur package for this needs to update their package it is causing dependacies issues

:: installing boost-libs (1.87.0-2) breaks dependency 'libboost_filesystem.so=1.86.0-64' required by syncthingtray-qt6

FreePenguin commented on 2025-02-08 12:12 (UTC)

Ok, thanks for explanation, maybe I should read pinned comments before suggesting something next time.

mEDI_S commented on 2025-02-08 11:40 (UTC) (edited on 2025-02-08 11:42 (UTC) by mEDI_S)

This work for me to fix the depends

sys upgrade with -d

-d, --nodeps Skips dependency version checks

rebuild all depends

rebuild syncthingtray-qt6

$ upgrade and reinstall

sudo pacman -Suyd

yay -S --answerclean All --rebuildall c++utilities qtutilities-qt6 qtforkawesome-qt6

yay -S --answerclean All --rebuildall syncthingtray-qt6

gl

ps: -d is dangerous and have u to many packages to update is the better way to remove, upgrade and reinstall syncthingtray-qt6

Martchus commented on 2025-02-07 19:25 (UTC)

Like I said, you just have to rebuild this package against the new version of boost.

derivativeoflog7 commented on 2025-02-07 17:24 (UTC)

@FreePenguin I tried forcibly updating boost-libs and it broke syncthingtray-qt6; I've temporarily switched to using the Flatpak release since keeping the older version of the libraries was keeping too many updates from working

Martchus commented on 2025-02-07 17:21 (UTC) (edited on 2025-02-07 17:23 (UTC) by Martchus)

@FreePenguin That the system update is prevented in this case means it works as intended. The system update would otherwise break syncthingtray-qt6. This is the correct way of packaging following best practices that official packages use as well. To resolve this, you have to rebuild syncthingtray-qt6 against the new version of boost, see the pinned comment.

FreePenguin commented on 2025-02-07 16:32 (UTC)

I suggest weakening requirements for this package since after compiling they're becoming very strict like "libboost_filesystem.so=1.2.34" which might prevent system upgrading from regular repos.

diff --git a/PKGBUILD b/PKGBUILD
index b936050..b4f5932 100644
--- a/PKGBUILD
+++ b/PKGBUILD
@@ -93,8 +93,6 @@ check() {
 }

 package() {
-  depends+=('libqtutilities-qt6.so' 'libqtforkawesome-qt6.so' 'libc++utilities.so' 'libboost_filesystem.so')
-
   cd "$srcdir/${PROJECT_DIR_NAME:-$_reponame-$pkgver}"
   DESTDIR="${pkgdir}" ninja install
 }

Martchus commented on 2025-02-06 21:43 (UTC)

If it is caused by how KDE handles adjacent Plasmoids then there is indeed nothing I can do about it. However, I think this shouldn't be a problem when showing the Plasmoid as part of the system tray Plasmoid. The README contains more information about the different ways the Plasmoid can be configured, see https://github.com/Martchus/syncthingtray?tab=readme-ov-file#configuring-plasmoid.

derivativeoflog7 commented on 2025-02-06 21:41 (UTC)

@matchus I mean, it could be caused by how KDE handles adjacent plasmoids, or by how I have my panel configured for all I know

« First ‹ Previous 1 2 3 4 5 6 7 .. 9 Next › Last »