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: 86
Popularity: 2.02
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

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

Martchus commented on 2024-03-06 12:07 (UTC) (edited on 2024-03-07 17:54 (UTC) by Martchus)

KDE 6 is now in extra. That's why the latest version of syncthingtray no longer contains KDE integrations by default as those would only work on KDE 5. KDE integrations are now built by default in syncthingtray-qt6 to support KDE 6. So it makes most sense to switch to syncthingtray-qt6 now.


Note that Manjaro is still using KDE 5. So Manjaro users need to stick to the syncthingtray package for KDE integrations as long as this is the case. To still build them (despite no longer being built by default as explained before) you need to add the following to /etc/makepkg.conf:

SYNCTHING_TRAY_ENABLE_KIO_PLUGIN=1
SYNCTHING_TRAY_ENABLE_PLASMOID=1

Martchus commented on 2023-12-19 09:29 (UTC)

@Neurofibromin Please read the pinned comment. If you then still have a question, please state more closely what you've tried and what did not worked, e.g. commands you invoked and the output.

Neurofibromin commented on 2023-12-19 07:51 (UTC)

The required boost version does not seem to be available on any servers, so the package install fails

npreining commented on 2023-11-22 11:47 (UTC)

@Martchus indeed, thanks. I can confirm that after building c++utilities with --nocheck and install the package, I can build the syncthingtray package without changes.

Thanks for your work on all this!

Norbert

Martchus commented on 2023-11-22 11:41 (UTC)

@npreining Considering the sed command fixes this then this is the very same problem I've already fixed in the latest release of c++utilities. So please build dependencies in the right order. The tests of c++utilities currently fail for a different reason which I'm going to work on, see https://github.com/Martchus/cpp-utilities/issues/28.

npreining commented on 2023-11-22 11:28 (UTC)

I can confirm that on my uptodate system, the build fails in the same way as mentioned. The failed test:

    Start 4: syncthingtray_appstream_validation

4: Test command: /usr/bin/appstreamcli "validate" "/home/norbert/.cache/yay/syncthingtray/src/syncthingtray-1.4.9/tray/resources/syncthingtray.appdata.xml"
4: Working Directory: /home/norbert/.cache/yay/syncthingtray/src/syncthingtray-1.4.9/tray
4: Test timeout computed to be: 10000000
4: W: io.github.martchus.syncthingtray:38: developer-name-tag-deprecated
4: 
4: ✘ Validation failed: warnings: 1
4/6 Test #4: syncthingtray_appstream_validation .............***Failed    2.05 sec

I fixed it by removing the deprecated tag:

@@ -70,6 +70,9 @@ build() {
     $additional_args \
     .
   ninja
+
+  # fix incorrect appstream format, on check with appstreamcli validate it fails
+  sed -i '/developer_name/d' tray/resources/syncthingtray.appdata.xml
 }

 check() {

Martchus commented on 2023-11-22 10:00 (UTC)

Please share the full error log. Just this single line is not good enough to investigate the issue. I can just guess. Maybe you don't have the latest version of appstream installed? Please ensure that all dependencies are up-to-date before attempting the build as partial updates are not supported and neither is Manjaro.

danielsz commented on 2023-11-22 09:52 (UTC)

The following tests FAILED: 4 - syncthingtray_appstream_validation (Failed)

Martchus commented on 2023-11-08 11:47 (UTC)

Ok, so what does that even mean for people who don't know this tool?

PatoPan commented on 2023-11-08 06:41 (UTC)

running with paru --sudoloop causes test 3 to fail, just fyi