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: 1.68
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 .. 4 5 6 7 8 9 10 11 12 13 Next › Last »

Martchus commented on 2021-10-06 09:16 (UTC)

Should be fixed.

Varakh commented on 2021-10-06 09:01 (UTC)

==> Validating source files with sha256sums... qtforkawesome-0.0.1.tar.gz ... FAILED

Same for me on Arch

adwl commented on 2021-10-06 08:57 (UTC) (edited on 2021-10-06 09:54 (UTC) by adwl)

edit: Working Now

==> Validating source files with sha256sums... qtforkawesome-0.0.1.tar.gz ... FAILED

on Majaro. Disregard if this is not an issue for Arch

Martchus commented on 2021-10-06 08:33 (UTC)

The dependency should be there now. Sorry for the inconvenience. It is new so my scripts for pushing automatically to the AUR were lacking it.

Maxnet commented on 2021-10-06 07:37 (UTC)

fails to build due to missing dependency qtforkawesome. Can you have a look at it?

ChillFre4k commented on 2021-10-06 06:16 (UTC)

Hi,

there is no package for "qtforkawesome" at the moment. @Martchus

Martchus commented on 2021-07-19 13:33 (UTC)

see https://github.com/Martchus/syncthingtray/issues/98

reefland commented on 2021-07-19 13:01 (UTC) (edited on 2021-07-19 13:02 (UTC) by reefland) 

$ syncthingctl status
syncthingctl: error while loading shared libraries: libboost_filesystem.so.1.75.0: cannot open shared object file: No such file or directory

$ pacman -Q boost-libs
boost-libs 1.76.0-1

$ pacman -Q syncthingtray 
syncthingtray 1.1.8-1

Martchus commented on 2021-07-17 13:37 (UTC) (edited on 2021-07-17 13:39 (UTC) by Martchus)

I assume you've just ran the local -a command in some shell in some terminal. You could add the command within the PKGBUILD's check() function and also echo the environment variables. This way you would see whether it is setup as expected also in the build environment. (An AUR helper or makepkg might mess-up something here, e.g. makepkg generally sets environment variables from /etc/makepkg.conf.)

at the beginning

I've noticed that setting variables at the beginning of the file might not be reliable, at least that's my experience when using makechrootpkg (see https://github.com/hipersayanX/ArchPackages/commit/1e61856d067b5aeae6828e39e01d617661b1069e). Hence I recommend to set environment variables within the relevant functions.

tdallagn commented on 2021-07-16 17:12 (UTC)

I'm not sure what's wrong with my locales, it seems alright:

$ locale -a
C
en_GB.utf8
en_US.utf8
POSIX

But adding export LC_ALL=C; unset LANGUAGE at the beginning of the PKGBUILD worked, thanks!

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