Package Details: syncthingtray-qt6 1.7.2-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-or-later
Submitter: Martchus
Maintainer: Martchus
Last Packager: Martchus
Votes: 28
Popularity: 4.15
First Submitted: 2020-11-07 16:16 (UTC)
Last Updated: 2025-02-01 20:29 (UTC)

Dependencies (28)

Required by (0)

Sources (1)

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

1 2 3 4 5 6 7 Next › Last »

costor commented on 2025-01-12 23:58 (UTC)

@iyanmv @Martchus syncthingtray-git builds and work fine for me! I indeed had [kde-unstable] enabled, but I had forgotten that it was enabled...

iyanmv commented on 2025-01-12 22:30 (UTC)

Martchus: syncthingtray-git builds just fine also with Qt 6.9.0. Thanks!

Martchus commented on 2025-01-11 00:54 (UTC)

I pushed https://github.com/Martchus/syncthingtray/commit/db32c94c7212f7f890307d7cb045035040ff418d on GitHub. With that compilation against Qt 6 works for me. I haven't tested compilation against the latest KDE frameworks yet. You can test it using the syncthingtray-git package.

Martchus commented on 2025-01-10 23:25 (UTC) (edited on 2025-01-11 00:02 (UTC) by Martchus)

Ah, Qt 6.9 could be the problem, indeed. I haven't tested that yet. It often takes some adjustments to get things working (compilation and runtime behavior) with a newer minor release of Qt comes out. I will look into it at some point but for the time being this is simply not supported.

That you were using kde-unstable also explains the problem with qt6-tools and llvm.

Note that you should really mention if you have made customizations like enabling kde-unstable from the beginning.

iyanmv commented on 2025-01-10 19:52 (UTC)

I can replicate costor issue when using Qt 6.9 from [kde-unstable], both building locally and with makechrootpkg (using kde-unstable-x86_64-build)

Martchus commented on 2025-01-09 23:10 (UTC) (edited on 2025-01-09 23:11 (UTC) by Martchus)

Sounds like you have LLVM from the testing repo installed but qt6-tools from the regular repo. You need to install everything from the testing repo consistently. I have the testing repo enabled and lupdate from qt6-tools 6.8.1-2 (mind the -2 at the end) works just fine without clang18.

The original error has probably nothing to do with the testing repo. I'm using it as well for my development builds and didn't run into any errors. (The packages on my binary repo are built against regular repos so everyone can install them. So I haven't tested package builds against testing.)

And again, it would be good to know the command invocation that leads to the build failure you mentioned.

costor commented on 2025-01-09 22:53 (UTC) (edited on 2025-01-09 22:55 (UTC) by costor)

After the c++utilities update to 5.27.2-1, I couldn't build that due to a different error (/usr/lib/qt6/bin/lupdate: error while loading shared libraries: libclang-cpp.so.18.1: cannot open shared object file: No such file or directory). But I resolved that by installing clang18.

Now I'm back to the same build error on this as before.

I don't think I have any non-default (clang) build settings, and I've also tried completely clearing/deleting the cache/build directories of my AUR helper (pikaur).

So maybe it's somehow because I'm on [testing]?

Martchus commented on 2025-01-07 23:38 (UTC)

I didn't run into the build error when rebuilding the patched version. Not sure how to fix this as I cannot reproduce it myself and you provided very little information. It would be good to know at least the concrete command that failed.

The paths in your error message imply that some cache directory is used. You could try to clean that to build from scratch. (Just a shot in the dark; I don't know the AUR helper you're using.)

Are you building on Manjaro? Are you building with clang or any custom flags? I'm just asking because something must be different between our build environments and maybe it is that you're using a whole different distribution or otherwise changed the build environment.

costor commented on 2025-01-07 22:50 (UTC)

I have a completely updated system. To be sure, I manually reinstalled the following dependencies: qtutilities-qt6 qtforkawesome-qt6 c++utilities boost-libs qt6-svg openssl desktop-file-utils qt6-webengine qt6-declarative boost-libs cmake ninja qt6-tools qt6-declarative clang boost kio libplasma extra-cmake-modules cppunit syncthing iproute2.

But the build error failure remains the same.

Martchus commented on 2025-01-07 22:14 (UTC)

@costor I didn't run into this issue. I'm going to rebuild packages anyway to add an additional patch. Maybe I can reproduce the issue then. Note that you must always build against the latest version of c++utilities and other dependencies so update your system and other AUR dependencies first.

1 2 3 4 5 6 7 Next › Last »