Package Details: seafile-client 8.0.7-1

Git Clone URL: https://aur.archlinux.org/seafile-client.git (read-only, click to copy)
Package Base: seafile-client
Description: GUI client for synchronizing your local files with seafile server
Upstream URL: https://github.com/haiwen/seafile-client
Licenses: Apache
Submitter: Localizator
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 168
Popularity: 0.023754
First Submitted: 2012-12-10 17:34 (UTC)
Last Updated: 2022-05-11 11:46 (UTC)

Pinned Comments

Joffrey commented on 2021-05-30 20:06 (UTC) (edited on 2021-05-30 20:11 (UTC) by Joffrey)

Please, when you have compilation or execution errors, recompile each component without using an AUR helper before reporting an issue.

Latest Comments

a-bostaurus commented on 2022-04-25 14:36 (UTC)

On more than 3 computers I get an Error-information: "Warnung: Konnte einige Dateien nicht übertragen Fehler: Der Vorgang konnte nicht durchgeführt werden (Konnte manche Dateien nicht übertragen) Fehler sind aufgetreten, keine Pakete wurden aktualisiert. ==> FEHLER: 'pacman' konnte fehlende Abhängigkeiten nicht installieren. ==> Fehlende Abhängigkeiten: -> qt6-webengine -> qt6-5compat ==> Prüfe Buildtime-Abhängigkeiten... ==> FEHLER: Konnte nicht alle Abhängigkeiten auflösen. :: Unable to build seafile-client - makepkg exited with code: 8" The wanted dependencies do not exist on servers (5.17.0-1-MANJARO)

jost5367 commented on 2022-03-09 07:26 (UTC)

Package build V8.0.6 succeeded only after I installed qt6-webengine manually. Please check, and add it to the build script as an additional dependency, thx.

fx333 commented on 2022-02-24 18:20 (UTC)

By the way, qt5-tools is not required to run the Seafile client. You can move it from depends to makedepends.

Logic commented on 2022-02-18 14:19 (UTC)

Hi,

maybe someone can help me with an error during compilation:

[ 88%] Linking CXX executable seafile-applet
/usr/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../lib/libgio-2.0.so: undefined reference to `g_module_open_full'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/seafile-applet.dir/build.make:4004: seafile-applet] Error 1
make[1]: *** [CMakeFiles/Makefile2:987: CMakeFiles/seafile-applet.dir/all] Error 2
make: *** [Makefile:146: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...

I build the package with "makepkg -fsri". When I check to see if the symbol is available, I find it:

readelf -Ws --dyn-syms /usr/lib/gcc/x86_64-pc-linux-gnu/11.2.0/../../../../lib/libgio-2.0.so | grep g_module_open_full
   417: 0000000000000000     0 FUNC    GLOBAL DEFAULT  UND g_module_open_full

Does anyone know how I can solve the problem?

JulianFP commented on 2022-02-16 16:38 (UTC) (edited on 2022-02-16 16:39 (UTC) by JulianFP)

When trying to login via SSO, seafile-applet crashes after entering the domain. In the cli the debug message "Aborted (core dumped)" appears and applet.log contains:

[16.02.2022 17:27:00]read id from id file
[16.02.2022 17:27:00]starting seaf-daemon:  ("-c", "/home/<user>/.ccnet",    "-d", "<path>/Seafile/.seafile-data", "-w", "<path>/Seafile/seafile/")
[16.02.2022 17:27:01][Rpc Client] connected to daemon
[16.02.2022 17:27:01][Rpc Client] connected to daemon
[16.02.2022 17:27:02]Starting the network status detector
[16.02.2022 17:27:02][AutoUpdateManager] cancel all download tasks
[16.02.2022 17:27:02][AutoUpdateManager] clean file caches db
[16.02.2022 17:27:02][AutoUpdateManager] clean file caches
[16.02.2022 17:27:02]starting applet rpc service
[16.02.2022 17:27:02]socket file exists, delete it anyway
[16.02.2022 17:27:02]applet rpc service started
[16.02.2022 17:27:05]WebEngineContext used before QtWebEngine::initialize() or OpenGL context creation failed.
[16.02.2022 17:27:05]QGLXContext: Failed to create dummy context
[16.02.2022 17:27:05]Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples 0, swapBehavior QSurfaceFormat::DefaultSwapBehavior, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile  QSurfaceFormat::NoProfile)

MrKyr commented on 2022-01-15 22:45 (UTC)

Hi, is it possible to make a package only for the cli client?

snack commented on 2021-11-03 07:40 (UTC)

The issue with the application crashing when the mouse is moved over the gear icon has vanished for me. I don't know what fixed it, maybe an update of a dependent package. The only manual intervention I recently did was to restore the compositing of my Plasma desktop after the upgrade to Plasma 5.23 removed the XRender backend and forced me to fix Plasma configuration in order to get the compositor back at work with the OpenGL backed. But to me this doesn't seem to have any clear relationship with the Seafile client issue, so it's probably irrelevant.

YamashitaRen commented on 2021-10-26 15:20 (UTC) (edited on 2021-10-26 15:21 (UTC) by YamashitaRen)

For the record, I have snack's issue too.

And now it looks like my preferences are ignored because the "undefined symbol" issue came back. Maybe you don't have the bug because you did not check it or something like that...

bionade24 commented on 2021-10-16 12:10 (UTC)

@snack No, it's full of AUR packages. Honestly, at this point just downgrade to 8.0.3 and stick with it. Maybe it's bc my server still runs 7.15. Someone has to take time to debug it correctly.

My checksums:
158237338f3476140a230ff5adff1f6b0e8831f3c2947317348d553deb99fca4 /usr/bin/seafile-applet
8fca5c846fd932d853915b207bbabe3eacffb74e990a24012141b69413913e06 /usr/bin/seaf-daemon
ab10cafcc2951a856a830b7a2686cf87efa62e55bd97ee10656aebd757234a31 /usr/lib/libsearpc.so
70fae0d24bd84ee00b5543f3c1ae676fed72773260081525bb43bf29f24af382 /usr/lib/libseafile.so

snack commented on 2021-10-16 12:02 (UTC)

@bionade24: thanks for the help and sorry for the off-topic question. The problem still persists on my machine, but I se that in your repo you have many other packages. Do you use these instead of the official Arch ones on the machines where Sefile works as expected? If yes then the breakage might come from a non-Seafile package whose version in Arch repos causes the breakage.

bionade24 commented on 2021-10-16 11:27 (UTC) (edited on 2021-10-16 11:28 (UTC) by bionade24)

This will go a bit off-topic (if requested I'll delete it).

@snack The key pacman complains about is a subkey of my key (Or the other way around idk). Answering the dialog will unfortunately not help. The right way is to edit the trust level of the key, which can be achieved faster by using pacman-key --lsign-key <fingerprint>.

snack commented on 2021-10-16 11:26 (UTC)

@bionade: I imported and trusted the key 289AD6AA32857A04ABA587417EAC11ACDBCFBCEB, then pacman -Syy then pacman -S seafile-client seafile libsearpc. Still the same issue.

snack commented on 2021-10-16 11:01 (UTC)

@bionade: I added your [oscloud] repo to my pacman.conf, but when I download its db pacman says:

error: oscloud: key "289AD6AA32857A04ABA587417EAC11ACDBCFBCEB" is unknown

This key is different from the one listed in archwiki:

Key-ID: CB222E7EBC11D682AAC8B317A4A0D73114FDE6FC

Should I trust it? (not a gpg expert here, so sorry if the question is a dumb one). Thanks

bionade24 commented on 2021-10-16 10:27 (UTC)

@snack I would say that should work, too. But you'll only be sure with PGP integrity.

Now upgraded my 2nd device, works fine too.

snack commented on 2021-10-14 08:13 (UTC)

@bionade24: I downloaded the packages from your site manually and the pacman -U.

snack commented on 2021-10-14 08:10 (UTC)

@bionade24: I downloaded the packages from your site manually and the pacman -U.

bionade24 commented on 2021-10-13 20:46 (UTC) (edited on 2021-10-16 10:27 (UTC) by bionade24)

@snack @wudu @ReneS I now updated my system and seafile to 8.0.4. As I've already guessed, it works fine for me and it seems to be a super tricky issue with dirty build environments. So either build in clean chroots or use my repo, but it's not the pkg's fault.

@Joffrey Maybe change the pinned comment to building in a clean chroot.

@snack: You sure youre cache didn't fuck that up? Try pacman -Rsc seafile-client seafile libsearpc && pacman -Scc && pacman -S seafile-client after you added my repo.

Edit: Now also updated my 2nd machine, everything works fine.

ReneS commented on 2021-10-13 15:22 (UTC)

Updated from v8.0.3 to v8.0.4 recently. Now it crashes, this is how you can reproduce the issue:

  1. Start Seafile
  2. In the Seafile window, hover the mouse over the settings button

Reproduced on 2 arch installations.

This is the stack trace: https://pastebin.com/AMmc9pTZ

snack commented on 2021-10-11 09:41 (UTC) (edited on 2021-10-11 09:41 (UTC) by snack)

@bionade24: I installed libsearpc, seafile and seafile-client from you repo, but the crash is still there. Am I still missing some package?

bionade24 commented on 2021-10-11 09:27 (UTC)

@snack: You have to reinstall every seafile related package, only reinstalling seafile-client obviously can't help if the libraries are broken.

snack commented on 2021-10-11 09:23 (UTC)

@bionade24: I built it with yay as always did. So I tried installing the packages from your repo but that didin't fix the problem.

bionade24 commented on 2021-10-11 09:18 (UTC)

@snack @wudu: Have you tried building every seafile related package in a clean chroot? Otherwise it's maybe caused by a broken build environment. https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot

If you don't want to do that yourself you can use the package from my CI/CD:
Build status: https://abs-cd.oscloud.info/cd_manager/seafile-client
https://wiki.archlinux.org/title/Unofficial_user_repositories#oscloud

snack commented on 2021-10-11 08:43 (UTC) (edited on 2021-10-11 08:43 (UTC) by snack)

@wudu It happens also to me. It didn't happen with 8.0.3 so I'd say it's a new bug.

wudu commented on 2021-10-11 08:38 (UTC) (edited on 2021-10-11 08:46 (UTC) by wudu)

I have installed the 8.0.4 version. On hovering (not clicking) the "gear" with the mouse to acces the options the program crashes. Didn't have an earlier version installed so I don't know if this problem existed before. Tried the same version in Ubuntu from the official repo without this problem in a VM.

When starting in a terminal I get: GLib-WARNING **: 10:28:05.114: (../glib/glib/gerror.c:761):g_error_new_valist: runtime check failed: (domain != 0)

Followed by: 'seafile-applet' terminated by signal SIGSEGV

enos commented on 2021-10-04 10:33 (UTC)

Because of the checksum error I updated the package to 8.0.4. Pls also see comments at https://aur.archlinux.org/packages/seafile/.

https://gitlab.com/enos-public/aur/-/snippets/2184294

bhartshorn commented on 2021-09-15 15:39 (UTC)

Can we get an optional dependency on qt5-wayland for those of us on Wayland?

Also, for those struggling with the validity check: updpkgsums from pacman-contrib makes short work of the problem, though don't get in the habit of using it blindly. It seems the seafile devs like to re-upload source packages.

Schroeffu commented on 2021-08-11 20:22 (UTC)

The sha256sum from depency seafile (v8.0.3.tar.gz) did also change, it is currently a83d5d301cf54819ab96ea0ab53824980efdf6727460b969ce3176b4c5109f6b

christian-heusel commented on 2021-07-24 10:06 (UTC) (edited on 2021-07-24 10:09 (UTC) by christian-heusel)

@urldog unfortunately this will be necessary:

  1. Clone packaging instructions: $ git clone https://aur.archlinux.org/seafile-client.git
  2. $ cd seafile-client
  3. Download the release from the official github page: $ wget -O seafile-client-8.0.3.tar.gz https://github.com/haiwen/seafile-client/archive/v8.0.3.tar.gz
  4. Create the checksums for it: $ sha256sum seafile-client-8.0.3.tar.gz
  5. Edit the PKGBUILD to match the shasum from Step 4 (line ~24)
  6. Install the package: $ makepkg -si

So here is your step by step explanation, note that "$" means "run as normal user".

The underlying problem arises because the seafile people seem to re-release sometimes so the shasums of the ".tar.gz"-file change after release.

As a further comment I would say that you have to realize that what I described does circumvent the download and obviously the checksumming mechanism of the package itself and could be done in other ways, but all those would probably be a bad habit for you in the future (like ignoring these checksums at all).

If you need further help or have questions just post again.

urldog commented on 2021-07-23 13:52 (UTC)

Could someone post the steps they did to get the client to work? Ideally each single step as I'm not ready to invest in how to edit/build packages in arch yet. Thanks a lot in advance.

enanone commented on 2021-07-08 09:19 (UTC)

@blackpoll until there is a new version of the PHGBUILD, you can edit it locally specifying the correct sha256sum for the file seafile-8.0.3.tar.gz, as explained by @dsnxt

blackpoll commented on 2021-07-02 15:26 (UTC)

==> Validating source files with sha256sums... seafile-8.0.3.tar.gz ... FAILED seaf-cli@.service ... Passed ==> ERROR: One or more files did not pass the validity check!

How to fix this?

dsnxt commented on 2021-07-02 10:12 (UTC) (edited on 2021-07-02 10:12 (UTC) by dsnxt)

sha256 checksum for seafile-client-8.0.3.tar.gz changed to 6c36c990992138cbc961d76689c6b1f60d5d2f52537169791e9e28b88d4850ad

kulak commented on 2021-06-03 15:24 (UTC)

I think it is worth pinning a note stating that package tracks current version of the official upstream. Upstream currently has an issue and it is recommended to take previous version of this git repository.

If the problem can be resolved that way. It seems like the least energy spent on everyone's part until upstream resolves issues.

YamashitaRen commented on 2021-06-03 14:05 (UTC)

Okay, I'll add the epoch myself if you don't want to do it.

And no, the package is not working as intended. Having a big list of warnings everytime you open your session is a confirmed bug. Upstream recommends a downgrade. There is absolutery no reason to not downgrade.

bionade24 commented on 2021-06-03 08:27 (UTC)

@doblerone: This isn't official upstream, it's their package maintainership work, which works like how Ubuntu handles that. Arch folllows the repository upstream. If they still have this release as latest, it's the version Arch ships, especially since it's not breaking the sync functionality. And when you look at how the seafile maintainers made it possible to downgrade: That's equal to self-cloning the repo on Arch, reverting latest version and makepkg -si

doblerone commented on 2021-06-03 08:01 (UTC) (edited on 2021-06-03 08:01 (UTC) by doblerone)

@bionade24: seafile-client has been officially downgraded to 8.0.1 due to the annoying synchronizing errors on non-windows machines.

https://github.com/haiwen/seafile/issues/2451#issuecomment-852018760

It would be nice to downgrade the package accordingly. Thanks for the effort of mantaining the package!

bionade24 commented on 2021-06-02 12:06 (UTC)

@ph2545: I'm against introducing an epoch(necessary to downgrade), that's just more confusing than this minor issue. It's also conflicts with Arch's philosophy and you'll be able to downgrade yourself easily.

ph2545 commented on 2021-06-02 12:01 (UTC)

Are you planning on downgrading the seafile-client package and its dependencies according to the discussion here ?

https://github.com/haiwen/seafile/issues/2451#issuecomment-851837162

Thank you for your work maintaining this package !!

RealOrRandom commented on 2021-05-31 08:21 (UTC)

Okay, I tracked down the problem.

The problem was that I had seafile 8.0.1-1 installed. I first needed to update seafile to 8.0.2-1. I think this package needs to have seafile version 8.0.2 as a depedency and not just seafile with any version.

bionade24 commented on 2021-05-31 08:14 (UTC)

@RealOrRandom: The package builds fine in my CI, so the failure is caused by your dirty environment. https://abs-cd.oscloud.info/cd_manager/seafile-client

@Joffrey: Without using an AUR helper doesn't make a difference, you should advise people to try building in a clean chroot instead. If it fails there, it's definately broken. E.g. aurutils has an option to build in clean chroots, so it does not always matter if an aur helper is used.

Joffrey commented on 2021-05-30 20:06 (UTC) (edited on 2021-05-30 20:11 (UTC) by Joffrey)

Please, when you have compilation or execution errors, recompile each component without using an AUR helper before reporting an issue.

RealOrRandom commented on 2021-05-30 13:01 (UTC) (edited on 2021-05-30 13:02 (UTC) by RealOrRandom)

This fails to be build for me:

/home/xxx/.cache/pikaur/build/seafile-client/src/seafile-client-8.0.2/src/utils/seafile-error.cpp: In function ‘QString translateSyncErrorCode(int)’:
/home/xxx/.cache/pikaur/build/seafile-client/src/seafile-client-8.0.2/src/utils/seafile-error.cpp:103:14: error: ‘SYNC_ERROR_ID_INVALID_PATH_ON_WINDOWS’ was not declared in this scope; did you mean ‘SYNC_ERROR_ID_INVALID_PATH’?
  103 |         case SYNC_ERROR_ID_INVALID_PATH_ON_WINDOWS:
      |              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      |              SYNC_ERROR_ID_INVALID_PATH
make[2]: *** [CMakeFiles/utils.dir/build.make:202: CMakeFiles/utils.dir/src/utils/seafile-error.cpp.o] Error 1

Joffrey commented on 2021-05-20 16:27 (UTC) (edited on 2021-05-20 19:47 (UTC) by Joffrey)

@GeneralFault I haven't tested on Manjaro, but on Arch Linux everything is fine.
Try to rebuild every components without AUR helper.

GeneralFault commented on 2021-05-19 14:31 (UTC)

Does build for me, but the following test fails, so the package won't install:

"test_file-utils" start time: May 19 16:28 CEST
Output:
----------------------------------------------------------
********* Start testing of FileUtils *********
Config: Using QtTest library 5.15.2, Qt 5.15.2 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 10.2.0), manjaro unknown
PASS   : FileUtils::initTestCase()
PASS   : FileUtils::getParentPath()
PASS   : FileUtils::getBaseName()
FAIL!  : FileUtils::expandUser() Compared values are not the same
   Actual   (expandUser("~"))       : "/"
   Expected (QDir::homePath() + "/"): "//"
   Loc: [/var/cache/private/pamac/seafile-client/src/seafile-client-8.0.1/tests/test_file-utils.cpp(36)]
PASS   : FileUtils::cleanupTestCase()
Totals: 4 passed, 1 failed, 0 skipped, 0 blacklisted, 0ms

Joffrey commented on 2021-03-25 19:17 (UTC)

Thanks @river_wunsch for your report, it's fixed.

river_wunsch commented on 2021-03-25 06:12 (UTC)

I'm using yay to build this package, but I got something like

/home/xxx/.cache/yay/seafile-client/src/seafile-client-7.0.10/src/rpc/rpc-client.cpp:1:1: note: ‘extern "C"’ linkage started here
    1 | extern "C" {
    | ^~~~~~~~~~
In file included from /usr/include/glib-2.0/glib/gatomic.h:31,
                from /usr/include/glib-2.0/glib/gthread.h:32,
                from /usr/include/glib-2.0/glib/gasyncqueue.h:32,
                from /usr/include/glib-2.0/glib.h:32,
                from /usr/include/searpc-client.h:10,
                from /home/xxx/.cache/yay/seafile-client/src/seafile-client-7.0.10/src/rpc/rpc-client.cpp:3:
/usr/include/c++/10.2.0/type_traits:2906:3: error: template with C linkage
2906 |   template<typename _Fn, typename _Tp>
    |   ^~~~~~~~

According to https://github.com/haiwen/seafile-client/pull/1346#issuecomment-788638328 , I added add_definitions(-DGLIB_VERSION_MIN_REQUIRED=GLIB_VERSION_2_26) to CMakeLists.txt , rebuild using cmake . and make. It seems good this time.

Can you guys build this package successfully?

FuelFlo commented on 2021-01-22 18:23 (UTC)

@dassystem well I have no idea how to reverse that. According to: https://manual.seafile.com/changelog/client-changelog/ the 8.0.x clients are still BETA, also the Mac and Windows clients released on the Seafile website are marked beta. So I'm quite confident they did not intend to release it as a stable version yet, even though there is a 8.0.1 release tag on Github.

dassystem commented on 2021-01-22 15:04 (UTC)

@FuelFlo at least it is flagged as out of date. Maybe we should then remove the flag if the newer version is beta?

FuelFlo commented on 2021-01-22 15:02 (UTC)

@dassystem well it's not really out of date is it?!

8.0.0 or 8.0.1 are only beta versions there is no stable Version after 7.0.10 afaik.

dassystem commented on 2021-01-22 14:26 (UTC)

This package is out of date. What can I do to help upgrading it to the new version?

bionade24 commented on 2020-11-02 08:39 (UTC)

This package is built by my CD and available in this repo:
https://wiki.archlinux.org/index.php/Unofficial_user_repositories#oscloud
CI status: https://abs-cd.oscloud.info/cd_manager/seafile-client

kulak commented on 2020-06-29 10:44 (UTC) (edited on 2020-06-29 10:45 (UTC) by kulak)

I couple issues with current version. I've got the same results on more than one machine.

sha256sum signature does not match for 7.0.8:

9c737acc7d6e92e36625156346b866c2e90fa5900828fc77a28ed4f622629bae  seafile-client-7.0.8.tar.gz

The following might be product problems, not package.

All clients result with window title area and profile area (one with refresh button) being transparent.

It might be related to message in applet log:

[06/29/2020 03:24:08 AM]libpng warning: iCCP: known incorrect sRGB profile

Last one: dragging window results in mouse moving at different speed than window and disconnect in locations of both.

Other than cosmetic issues above works as expected.

bionade24 commented on 2020-06-24 13:50 (UTC)

@jakeobsen: No, that's in base-devel which is needed for a working ABS enviroment. If makepkg works 100% correctly, patch is already installed.

jakeobsen commented on 2020-06-24 09:09 (UTC)

This package has a missing dependency 'patch'

MadMe commented on 2020-06-11 19:39 (UTC)

https://github.com/haiwen/seafile-client/archive/v7.0.8.tar.gz sha256sum changed again...

Joffrey commented on 2020-05-29 16:21 (UTC)

Hello @TheEbolaDoc,
This should fix it:

Patch

fix_QT5_v5.15_QPainterPath.diff

diff --git a/src/ui/events-list-view.cpp b/src/ui/events-list-view.cpp
index b1d04abb..09536b9e 100644
--- a/src/ui/events-list-view.cpp
+++ b/src/ui/events-list-view.cpp
@@ -1,4 +1,5 @@
 #include <QPainter>
+#include <QPainterPath>
 #include <QApplication>
 #include <QPixmap>
 #include <QToolTip>
diff --git a/src/ui/private-share-dialog.cpp b/src/ui/private-share-dialog.cpp
index 511d476b..284cc043 100644
--- a/src/ui/private-share-dialog.cpp
+++ b/src/ui/private-share-dialog.cpp
@@ -2,6 +2,7 @@
 #include <QCompleter>
 #include <QLineEdit>
 #include <QPainter>
+#include <QPainterPath>
 #include <QResizeEvent>
 #include <QStringList>
 #include <QStringListModel>
PKGBUILD
# Maintainer: Joffrey <j-off@live.fr>
# Contributor: eolianoe <eolianoe [at] gmail [DoT] com>
# Contributor: localizator <localizator@ukr.net>
# Contributor: Edvinas Valatka <edacval@gmail.com>

pkgname=seafile-client
pkgver=7.0.7
pkgrel=1
pkgdesc='GUI client for synchronizing your local files with seafile server'
arch=('i686' 'x86_64' 'armv7h' 'armv6h' 'aarch64')
url="https://github.com/haiwen/$pkgname"
license=('Apache')
depends=(
    'seafile'
    'qt5-base'
    'qt5-webengine'
    'qt5-webkit'
    'qt5-tools'
    'gtk-update-icon-cache'
)
makedepends=("cmake")
conflicts=('seafile-client-qt5')
provides=('seafile-client-qt5')
source=(
    "$pkgname-$pkgver.tar.gz::$url/archive/v$pkgver.tar.gz"
    'fix_QT5_v5.15_QPainterPath.diff'
)
sha256sums=(
    '49a97a1e7c55ff29237ff5b700cde8035b56a56c9176d7d7fc426357f4abab78'
    '300d77db22b8f0845faa4442afc557d46c21b758b7b3be75381e5a2dd58fef07'
)
prepare() {
    cd "$srcdir/$pkgname-$pkgver"
    patch -p1 -i "$srcdir/fix_QT5_v5.15_QPainterPath.diff"

    cd "$srcdir"
    rm -rf build
    mkdir -p build
}

build() {
    cd "$srcdir/build"
    cmake \
        -DBUILD_TESTING=ON \
        -DBUILD_SHIBBOLETH_SUPPORT=ON \
        -DCMAKE_BUILD_TYPE=Release \
        -DCMAKE_INSTALL_PREFIX='/usr' \
        "$srcdir/$pkgname-$pkgver"
    make
}

check() {
    cd "$srcdir/build"
    make test
}

package() {
    cd "$srcdir/build"
    make DESTDIR="$pkgdir" install
}

https://github.com/haiwen/seafile-client/pull/1297

christian-heusel commented on 2020-05-29 11:05 (UTC)

Hey, I just tried to install the seafile-client package and got the following error during compilation:

/home/chris/.cache/yay/seafile-client/src/seafile-client-7.0.7/src/ui/private-share-dialog.cpp:1036:22: error: aggregate ‘QPainterPath path’ has incomplete type and cannot be defined
 1036 |         QPainterPath path;
      |                      ^~~~

Please note that I may have a more recent QT Version than you due to being a testing user:

chris@pioneer ~ » pacman -Qi qt5-base
Name            : qt5-base
Version         : 5.15.0-1

So maybe it gets fixed until QT 5.15.0 is released into <extra>.

bionade24 commented on 2019-12-20 13:38 (UTC)

  1. Please fix the checksums of seafile-client and seafile.
  2. All packages can be built against python3, python2 is not necessary. Please fix this, too.
  3. Please Correct the Maintainer statement in the PKGBUILDs.

theangrywizard commented on 2019-12-17 15:41 (UTC) (edited on 2019-12-17 15:42 (UTC) by theangrywizard)

I think the sha256sum has changed again. I've downloaded the tar from the https://github.com/haiwen/seafile-client/archive/v7.0.4.tar.gz to verify and I'm getting:

638adba50cdd3727106178f972d144a0cec60911d72017fc6ccba7f423689b19

quantumriff commented on 2019-12-13 23:48 (UTC) (edited on 2019-12-13 23:50 (UTC) by quantumriff)

The sha256Sum has changed for the PKGBUILD. It should now be:

d33d6de57b9dc8083aecde78abbd00684f7cda6a36ec8fd00749c7c8236a2a8e  seafile-7.0.4.tar.gz

This is causing updates/builds to fail.

ugo commented on 2019-12-12 11:07 (UTC)

@Joffrey the pkg fails to build cause of wrong sha256 sum on seafile-7.0.4.tar.gz

plague-doctor commented on 2019-11-05 21:00 (UTC)

@Joffrey The seafile is defined as a dependency for your seafile-client package, so it should be installed and ready before seafile-client compilation. It is not. However when I installed seafile before hand, and then tried to build seafile-client again it was fine.

Joffrey commented on 2019-11-05 13:17 (UTC)

@plague-doctor this header is provided by Seafile. You must have Seafile installed and up to date before build Seafile-client.

plague-doctor commented on 2019-11-05 01:12 (UTC)

Build is failing during the compilation stage:

seafile-client-7.0.3/src/utils/seafile-error.cpp:2:10: fatal error: seafile/seafile-error.h: No such file or directory
2 | #include <seafile/seafile-error.h>

aacebedo commented on 2019-10-15 15:42 (UTC)

@vsilv I fixed the issue by injecting the correct value of the checksum in the first item of the array in the PKGBUILD

vsilv commented on 2019-10-15 15:21 (UTC)

Same problem as aacebedo for me.

aacebedo commented on 2019-10-13 17:17 (UTC)

Unable to use this package. I get a validity check error. Tried to clean the cache but nothing changed.

Elinvention commented on 2019-08-19 22:07 (UTC)

@FuelFlo I had the same problem with seafile-server. These commands finally fixed it for me:

rm .cache/yay/{ccnet-server/,seafile-server/,seafile/,libevhtp-seafile/,libsearpc/,python2-seafobj/,python2-wsgidav-seafile/,seahub/} -rf
sudo pacman -Rcs seafile-server ccnet-server seahub
yay -S seafile-server ccnet-server seahub

FuelFlo commented on 2019-08-19 21:56 (UTC)

But apparently linking libevent-2.1.so.7.0.0 to libevent-2.1.so.6 is not a good fix.

Somehow, no matter how often I rebuild seafile and seafile-client it links against libevent-2.1.so.6, but I have no libevent-2.1.so.6 in /usr/lib/ ....the only libevent-2.1.so.6 is in a tor-browser folder in my home directory.

So something is wrong with the build process. Any ideas @eolianoe?

FuelFlo commented on 2019-08-16 13:21 (UTC)

Linking the library fixed for me: ln -rs /usr/lib/libevent-2.1.so.7.0.0 /usr/lib/libevent-2.1.so.6 from: https://aur.archlinux.org/packages/seafile/#comment-704490

But that's just a workaround, seems like some dependency problem.

hopimet commented on 2019-08-16 08:06 (UTC)

@FuelFlo, I don't know. I told you what I have done to solve this issue. May be you could re-install libevent first. Then seafile and seafile-client.

FuelFlo commented on 2019-08-14 21:32 (UTC)

@hopimet mhm thx, i've tried that several times already, removing everything, Seafile dir, pamac buildcache...etc. but it still shows the same libevent error.

Something else i could try?

hopimet commented on 2019-08-13 20:38 (UTC)

@PocketSam and FuelFlo, same problem for me. Solved after rebuilt of seafile-client AND seafile. Both packages need to be recompiled to get rid of the libevent library error.

FuelFlo commented on 2019-08-13 07:33 (UTC)

@PocketSam, yeah I have the same problem. Strangely enough only on one device, on my other one no problems.

So i followed the advice from the pinned message and rebuild everything, but the problem still persists...even after rebuilding a second time.

Anyone, any ideas?

PocketSam commented on 2019-08-13 04:19 (UTC)

Am I the only one with this error: libevent-2.1.so.6 cannot open shared object file ?

Yrz0 commented on 2019-08-09 08:58 (UTC)

@tbleiker: Had the same problem. Delete your cache and download the file again.

tbleiker commented on 2019-08-02 19:00 (UTC)

For me, the sha256sum was not correct. Had to change it to 3e8749858f0276ed37a18fdcb96e343ce924fa5404ec4f877b9341427430c874.

ReneS commented on 2019-07-17 18:55 (UTC)

Thanks for updating the package!

h44z commented on 2019-07-12 22:54 (UTC)

@eolianoe: I have updated this package to version 7.0.1. Find the updated PKGBUILD and .SRCINFO here: https://drive.google.com/open?id=1Du4TcDStqG3Un_PQkQCbyzsacw71gbxx

I also updated the ccnet-server, seafile-server and seafile packages.

klemens commented on 2019-01-24 21:37 (UTC)

@Kicer: https://wiki.archlinux.org/index.php/Arch_User_Repository#Getting_started

Kicer commented on 2019-01-24 21:27 (UTC)

please add 'patch' 'automake' and 'autoconf' to build deps

Joffrey commented on 2018-12-24 09:58 (UTC)

@urldog If you rebuild ccnet-server, it should reslove the problem. I have pushed a new commit on ccnet-server, now ccnet-server provide ccnet.

urldog commented on 2018-12-23 22:03 (UTC)

Broken on my system,

: ccnet-server and ccnet are in conflict. Remove ccnet? [y/N] y error: failed to prepare transaction (could not satisfy dependencies) :: removing ccnet breaks dependency 'ccnet' required by seafile =>> Try again? [y/N]: :: Dependency not found: ccnet-server ==> Making package: seafile 6.2.9-1 (So 23 Dez 2018 23:01:17 CET) ==> Checking runtime dependencies... ==> Installing missing dependencies... error: target not found: ccnet-server ==> ERROR: 'pacman' failed to install missing dependencies. :: Unable to build seafile - makepkg exited with code: 8

eolianoe commented on 2018-11-02 18:58 (UTC)

@adequate: when there is an error, never use an AUR helper, only use plain makepkg to test. This is normal that the filename is the same as this the same version.

adequate commented on 2018-11-02 18:17 (UTC)

@j0hannes Had the same problem with the wrong checksum. The checksum is correct, I downloaded the file manually from the GitHub page and did the check.

I fixed it by removing the recent .tar.gz-files of the folder of my aur helper. For yay: ~.cache/yay/seafile-client Looks like there has been a conflict with the naming of the files since the version before had the same name and therefore it resulted in a wrong checksum.

eolianoe commented on 2018-10-31 18:25 (UTC)

@j0hannes: the 6.2.5-3 is in the sync with the right archive, check your download

j0hannes commented on 2018-10-31 11:25 (UTC)

6.2.5-3 fails the checksum test.

eolianoe commented on 2018-10-30 18:49 (UTC)

@SrTobi, @languitar: no trouble on my side with the 6.2.5-2 PKGBUILD are you sure that you have the latest PKGBUILD and tarball?

SrTobi commented on 2018-10-30 12:33 (UTC)

Checksum is still failing

languitar commented on 2018-10-30 09:34 (UTC)

Any chance to get an updated package with the checksum.

stevefan1999 commented on 2018-10-25 03:59 (UTC)

The validity check is not passed.

rori commented on 2018-10-02 12:04 (UTC)

Turns out it was a problem with libuuid. There were conflicts with the versions provided by anaconda. Once I removed those everything compiled just fine.

eolianoe commented on 2018-09-30 11:13 (UTC)

@rori: no trouble here, maybe it's specific to Manjaro

rori commented on 2018-09-29 10:10 (UTC) (edited on 2018-09-29 10:14 (UTC) by rori)

When I try to build on Manjaro I encounter the following error:

[100%] Linking CXX executable seafile-applet
/usr/bin/ld: /usr/lib/libblkid.so.1: undefined reference to `uuid_unparse@UUID_1.0'
collect2: error: ld returned 1 exit status
make[2]: *** [CMakeFiles/seafile-applet.dir/build.make:3744: seafile-applet] Error 1
make[1]: *** [CMakeFiles/Makefile2:298: CMakeFiles/seafile-applet.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
Error making: seafile-client

I tried rebuilding all components and also reinstalling libutil-linux which contains libblkid, but nothing works. Any suggestions?

ReneS commented on 2018-07-22 20:29 (UTC)

Seems to work again. Thanks!

ToK commented on 2018-07-15 10:40 (UTC) (edited on 2018-07-15 10:40 (UTC) by ToK)

Same here as Popkornium18 told: setting up seafile-client on a new machine, I need to enter my settings on every boot.
If I install seafile-6.1.8 and seafile-client-6.1.8 everything works. After upgrading to 6.2.0 everything still works. So i seems to be a problem only for new machines :(

Popkornium18 commented on 2018-07-12 18:41 (UTC) (edited on 2018-07-12 19:07 (UTC) by Popkornium18)

I recently set up a new machine, and setting up seafile is really weird with the current version. It asks me 4 times for a directory to set up Seafile every time I start it. Not just the first time. I have to click ok four times, then I have to cancel providing login information (which I already have) and then I get the normal seafile window.

Furthermore if I launch it from the console it respects the $QT_AUTO_SCREEN_SCALE_FACTOR sometimes. If I launch it by clicking the icon, it never does that and the scaling is all fucked up and not usable.

Since 6.2.0 is beta anyway, it would probably a good idea to revert this package back to the current stable version. It's not even the current beta version 6.2.1. Maybe it should be split up into seafile-client-stable and seafile-client-beta. But packaging an outdated beta version is not really a good idea.

FuelFlo commented on 2018-07-08 16:34 (UTC)

@Squigly --> that's the problem: https://github.com/haiwen/seafile-server/issues/27

seafile-client 6.2.0 for linux is still beta and the hash will change with every commit. We'll have to wait until they make it final and stop changing the file on github.

Squigly commented on 2018-07-08 06:51 (UTC)

It seems that the sha256sum listed in PKGBUILD is wrong (or the file getting pulled down is wrong):

sha256 of file downloaded: ~/.cache/aurman/seafile$ sha256sum seafile-6.2.0.tar.gz 50d117db2ebde2704cb1a327cf40a4bf6770637497d3bd4c4788a6db40f862cb seafile-6.2.0.tar.gz

sha256 from PKGBUILD: a456b8d80e2616f1d58f64448b527b204cadf626661d117ae6d1fdc9115c018e

Indecently, looks like the version was bumped to 6.2.1 couple of days ago.

runaz commented on 2018-07-06 18:56 (UTC)

sha256sum should be b79eb9b7ed93357ef3bf2e125cc1b6a0c5756bc09b5ce8cd3894ee04a992b8cf now

eolianoe commented on 2018-07-04 17:47 (UTC)

@SchorschD: I'm not able to reproduce your error, even in a clean chroot

SchorschD commented on 2018-07-04 07:37 (UTC) (edited on 2018-07-04 07:50 (UTC) by SchorschD)

Validity check fails for seafile. (seafile-client 6.2.0-3) sha256sum seafile-6.2.0.tar.gz 50d117db2ebde2704cb1a327cf40a4bf6770637497d3bd4c4788a6db40f862cb seafile-6.2.0.tar.gz

If corrected in PKGBUILD build fails with [code] libtool: link: gcc -DPKGDATADIR=\"/usr/share/seafile\" -DPACKAGE_DATA_DIR=\"/usr/share/seafile\" -DSEAFILE_CLIENT -I../include -I../lib -I../lib -I../common -I/usr/include/searpc -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -Wall -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -Wl,-z -Wl,relro -Wl,-z -Wl,now -o seaf-daemon seaf-daemon.o job-mgr.o timer.o cevent.o http-tx-mgr.o vc-utils.o sync-mgr.o seafile-session.o seafile-crypt.o diff-simple.o wt-monitor.o wt-monitor-linux.o wt-monitor-structs.o clone-mgr.o seafile-config.o branch-mgr.o fs-mgr.o repo-mgr.o commit-mgr.o log.o rpc-service.o vc-common.o obj-store.o obj-backend-fs.o block-mgr.o block-backend.o block-backend-fs.o mq-mgr.o curl-init.o sync-status-tree.o filelock-mgr.o set-perm.o change-set.o ../lib/.libs/libseafile_common.a -lssl -lcrypto ../common/cdc/.libs/libcdc.a ../common/index/.libs/libindex.a -luuid -lsqlite3 -levent -lsearpc -lgio-2.0 -lgobject-2.0 -lglib-2.0 -ljansson -lz -lcurl -pthread curl-init.o: In function seafile_curl_init': curl-init.c:(.text+0x3c): undefined reference toCRYPTO_num_locks' curl-init.c:(.text+0x7b): undefined reference to CRYPTO_num_locks' curl-init.c:(.text+0x8c): undefined reference toCRYPTO_set_id_callback' curl-init.c:(.text+0x9f): undefined reference to CRYPTO_set_locking_callback' curl-init.o: In functionseafile_curl_deinit': curl-init.c:(.text+0xbe): undefined reference to CRYPTO_set_id_callback' curl-init.c:(.text+0xc6): undefined reference toCRYPTO_set_locking_callback' curl-init.c:(.text+0xe9): undefined reference to `CRYPTO_num_locks' collect2: error: ld returned 1 exit status make[2]: *** [Makefile:536: seaf-daemon] Error 1 [/code]

hopimet commented on 2018-07-02 08:51 (UTC) (edited on 2018-07-02 08:52 (UTC) by hopimet)

For seafile-client, sha256sums should be: 5c0118031d0d2d06c76774d4973e7cf2ae60cc1ae51530dffd5ad9ccf2e9892e

In the PKGBUILD, just change: sha256sums=('3b5bbb16e30f70ecf2e4de50e1a1e1f26fb952115e25391e553a1212cf990ddc')

to

sha256sums=('5c0118031d0d2d06c76774d4973e7cf2ae60cc1ae51530dffd5ad9ccf2e9892e')

For seafile, sha256sums should be: a456b8d80e2616f1d58f64448b527b204cadf626661d117ae6d1fdc9115c018e

In the PKGBUILD, just change: sha256sums=('de0e8e1c48326d579fbd300fb2d5737f7bb1c42bd349fe5e53129987606bdfb8' 'a2d7f7cf0c59aba97650af62b3cefd0ceb71a1007c34d9369a88e5769c7f6076' 'c37510109c1de64c774896df39aece240c056b54414d2119fca01860211156ba')

to

sha256sums=('a456b8d80e2616f1d58f64448b527b204cadf626661d117ae6d1fdc9115c018e' 'a2d7f7cf0c59aba97650af62b3cefd0ceb71a1007c34d9369a88e5769c7f6076' 'c37510109c1de64c774896df39aece240c056b54414d2119fca01860211156ba')

Popkornium18 commented on 2018-07-01 17:15 (UTC)

Validity check still fails for seafile and seafile-client 6.2.0-2.

hopimet commented on 2018-06-30 17:55 (UTC) (edited on 2018-06-30 17:55 (UTC) by hopimet)

sha256sums has changed (as for seafile package) because source was modified one day ago. Need to be corrected in the PKGBUILD. Thank you

FuelFlo commented on 2018-06-29 16:00 (UTC)

It seems like the checksums of seafile (and seafile-client) 6.2.0 are broken again.

==> Validating source files with sha256sums... seafile-6.2.0.tar.gz ... FAILED libseafile.in.patch ... Passed seaf-cli@.service ... Passed ==> ERROR: One or more files did not pass the validity check!

FuelFlo commented on 2018-06-14 11:38 (UTC)

The patch #1099 has just been merged.

elmau commented on 2018-06-07 18:34 (UTC)

The patch https://github.com/haiwen/seafile-client/pull/1099 work fine, I hope soon they merge in master

eolianoe commented on 2018-06-05 19:55 (UTC)

@ignitedPotato: thanks for your patch :)

blubbblubb commented on 2018-06-04 14:06 (UTC) (edited on 2018-06-04 21:02 (UTC) by blubbblubb)

take a look at the previous posts, it's a problem with the seafile sourcecode

there is an open bug report as well as a pull request posted on their github page

https://github.com/haiwen/seafile-client/issues/1097 https://github.com/haiwen/seafile-client/pull/1099

For now you need to patch the source code yourself or downgrade to qt 5.9

sambadevi commented on 2018-06-03 10:00 (UTC) (edited on 2018-06-03 10:01 (UTC) by sambadevi)

I am encountering Unknown CMake command "QT5_USE_MODULES as well, on a complete new install of arch.

I tried installing the qt5 packages with pacman, manually installing with makepkg and also yaourt, however the error appears everytime.

ignitedPotato commented on 2018-05-30 14:21 (UTC)

Sounds to me like you're missing some build dependencies? Now it did compile on my machine with the added include in private-share-dialog.h And this diff for CMakeLists.txt:

802c802
< QT5_USE_MODULES(seafile-applet Core Gui Widgets Network)
---
> target_link_libraries(seafile-applet Qt5::Core Qt5::Gui Qt5::Widgets Qt5::Network)
804c804
< QT5_USE_MODULES(seafile-applet ${WEBKIT_NAME} ${WEBKIT_WIDGETS_NAME})
---
> target_link_libraries(seafile-applet Qt5::WebEngine Qt5::WebEngineWidgets)
809,812c809
<   TARGET_LINK_LIBRARIES(seafile-applet
<     ${QT_QTDBUS_LIBRARIES}
<   )
<   QT5_USE_MODULES(seafile-applet ${USE_QT_LIBRARIES})
---
>   target_link_libraries(seafile-applet Qt5::DBus)

blubbblubb commented on 2018-05-29 22:55 (UTC)

including QHeaderView in seafile-client-6.1.8/src/ui/private-share-dialog.h seems to resolve the forward declaration errors, but then it fails with

/usr/bin/ld: cannot find -lWebEngine
/usr/bin/ld: cannot find -lWebEngineWidgets
/usr/bin/ld: cannot find -lCore
/usr/bin/ld: cannot find -lGui
/usr/bin/ld: cannot find -lWidgets
/usr/bin/ld: cannot find -lLinguistTools
/usr/bin/ld: cannot find -lNetwork
/usr/bin/ld: cannot find -lWebEngineCore
/usr/bin/ld: cannot find -lWebEngine
/usr/bin/ld: cannot find -lWebEngineWidgets
/usr/bin/ld: cannot find -lDBus

which i guess are all the Qt Modules which now aren't included properly.

ignitedPotato commented on 2018-05-29 19:37 (UTC) (edited on 2018-05-29 19:52 (UTC) by ignitedPotato)

@blubbblubb As far as I know, support for qt5_use_modules has been dropped. We should use target_link_libraries instead.

Line 802 of CMakeLists.txt would look like this then:

target_link_libraries(seafile-applet Qt5::Core Qt5::Gui Qt5::Widgets Qt5::Network)

I'd love to tell you that this fixes all problems but I'm getting a whole lot of forward declarations for class QHeaderView when changing the lines 802, 804, 809 and 812.

Any more hints?

blubbblubb commented on 2018-05-27 17:11 (UTC) (edited on 2018-05-27 17:11 (UTC) by blubbblubb)

Im not able to update to the latest version, any hints?

CMake Error at CMakeLists.txt:802 (QT5_USE_MODULES):
  Unknown CMake command "QT5_USE_MODULES".

pelle commented on 2018-05-20 20:56 (UTC) (edited on 2018-05-20 20:59 (UTC) by pelle)

Hi @all,

as soon as I start seafile-applet, the CPU load goes to 100%. The icon is not displayed. There is no synchronization. Sorry for my bad formatting

Currently is installed:

  • seafile 6.1.8-1
  • seafile-client 6.1.8-2
  • ccnet 6.1.8-1

No log is created in the directory ~/.ccnet/logs/seafile.log

That's the result of ldd:

  • linux-vdso.so.1 (0x00007ffcd60d4000)
  • libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f682c8f8000)
  • libcrypto.so.1.1 => /usr/lib/libcrypto.so.1.1 (0x00007f682c47b000)
  • libevent-2.1.so.6 => /usr/lib/libevent-2.1.so.6 (0x00007f682c225000)
  • libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007f682bf10000)
  • libjansson.so.4 => /usr/lib/libjansson.so.4 (0x00007f682bd02000)
  • libsearpc.so.1 => /usr/lib/libsearpc.so.1 (0x00007f682baf8000)
  • libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x00007f682b8a4000)
  • libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x00007f682b58d000)
  • libccnet.so.0 => /usr/lib/libccnet.so.0 (0x00007f682b370000)
  • libseafile.so.0 => /usr/lib/libseafile.so.0 (0x00007f682b143000)
  • libz.so.1 => /usr/lib/libz.so.1 (0x00007f682af2c000)
  • libQt5WebEngineWidgets.so.5 => /usr/lib/libQt5WebEngineWidgets.so.5 (0x00007f682acea000)
  • libQt5DBus.so.5 => /usr/lib/libQt5DBus.so.5 (0x00007f682aa60000)
  • libQt5Network.so.5 => /usr/lib/libQt5Network.so.5 (0x00007f682a6d4000)
  • libQt5Widgets.so.5 => /usr/lib/libQt5Widgets.so.5 (0x00007f6829e7a000)
  • libQt5Gui.so.5 => /usr/lib/libQt5Gui.so.5 (0x00007f68296b9000)
    • libQt5Core.so.5 => /usr/lib/libQt5Core.so.5 (0x00007f6828fb1000)
  • libstdc++.so.6 => /usr/lib/libstdc++.so.6 (0x00007f6828c28000)
  • libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x00007f6828a10000)
  • libc.so.6 => /usr/lib/libc.so.6 (0x00007f6828654000)
  • /lib64/ld-linux-x86-64.so.2 => /usr/lib64/ld-linux-x86-64.so.2 (0x00007f682d0ff000)
  • libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f6828450000)
  • libm.so.6 => /usr/lib/libm.so.6 (0x00007f68280bb000)
  • libffi.so.6 => /usr/lib/libffi.so.6 (0x00007f6827eb2000)
  • libpcre.so.1 => /usr/lib/libpcre.so.1 (0x00007f6827c40000)
  • libuuid.so.1 => /usr/lib/libuuid.so.1 (0x00007f6827a39000)
  • libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0x00007f6827699000)
  • libQt5WebEngineCore.so.5 => /usr/lib/libQt5WebEngineCore.so.5 (0x00007f68214b9000)
  • libQt5Quick.so.5 => /usr/lib/libQt5Quick.so.5 (0x00007f6820e43000)
  • libQt5PrintSupport.so.5 => /usr/lib/libQt5PrintSupport.so.5 (0x00007f6820bd5000)
  • libQt5QuickWidgets.so.5 => /usr/lib/libQt5QuickWidgets.so.5 (0x00007f68209c3000)
  • libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0x00007f6820772000)
  • libssl.so.1.1 => /usr/lib/libssl.so.1.1 (0x00007f6820508000)
  • libGL.so.1 => /usr/lib/libGL.so.1 (0x00007f6820264000)
  • libpng16.so.16 => /usr/lib/libpng16.so.16 (0x00007f682002e000)
  • libharfbuzz.so.0 => /usr/lib/libharfbuzz.so.0 (0x00007f681fd7c000)
  • libsystemd.so.0 => /usr/lib/libsystemd.so.0 (0x00007f681faf5000)
  • libicui18n.so.61 => /usr/lib/libicui18n.so.61 (0x00007f681f64a000)
  • libicuuc.so.61 => /usr/lib/libicuuc.so.61 (0x00007f681f290000)
  • libpcre2-16.so.0 => /usr/lib/libpcre2-16.so.0 (0x00007f681f019000)
  • libdouble-conversion.so.1 => /usr/lib/libdouble-conversion.so.1 (0x00007f681ee09000)
  • libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x00007f681ec05000)
  • libresolv.so.2 => /usr/lib/libresolv.so.2 (0x00007f681e9ee000)
  • libmount.so.1 => /usr/lib/libmount.so.1 (0x00007f681e796000)
  • libQt5WebChannel.so.5 => /usr/lib/libQt5WebChannel.so.5 (0x00007f681e578000)
  • libQt5Positioning.so.5 => /usr/lib/libQt5Positioning.so.5 (0x00007f681e2f0000)
  • librt.so.1 => /usr/lib/librt.so.1 (0x00007f681e0e8000)
  • libsmime3.so => /usr/lib/libsmime3.so (0x00007f681dec1000)
  • libnss3.so => /usr/lib/libnss3.so (0x00007f681db96000)
  • libnssutil3.so => /usr/lib/libnssutil3.so (0x00007f681d966000)
  • libnspr4.so => /usr/lib/libnspr4.so (0x00007f681d728000)
  • libX11.so.6 => /usr/lib/libX11.so.6 (0x00007f681d3e9000)
  • libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00007f681d1e6000)
  • libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0x00007f681cfdc000)
  • libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x00007f681cdd9000)
  • libXext.so.6 => /usr/lib/libXext.so.6 (0x00007f681cbc7000)
  • libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00007f681c9c1000)
  • libXi.so.6 => /usr/lib/libXi.so.6 (0x00007f681c7b0000)
  • libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00007f681c5a5000)
  • libXtst.so.6 => /usr/lib/libXtst.so.6 (0x00007f681c39f000)
  • libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x00007f681c15c000)
  • libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x00007f681be93000)
  • libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0x00007f681bc2b000)
  • libwebpmux.so.3 => /usr/lib/libwebpmux.so.3 (0x00007f681ba21000)
  • libwebpdemux.so.2 => /usr/lib/libwebpdemux.so.2 (0x00007f681b81c000)
  • libwebp.so.7 => /usr/lib/libwebp.so.7 (0x00007f681b5ae000)
  • libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f681b37c000)
  • libXss.so.1 => /usr/lib/libXss.so.1 (0x00007f681b178000)
  • libre2.so.0 => /usr/lib/libre2.so.0 (0x00007f681af09000)
  • libavcodec.so.58 => /usr/lib/libavcodec.so.58 (0x00007f6819859000)
  • libavformat.so.58 => /usr/lib/libavformat.so.58 (0x00007f6819412000)
  • libavutil.so.56 => /usr/lib/libavutil.so.56 (0x00007f6819199000)
  • libopus.so.0 => /usr/lib/libopus.so.0 (0x00007f6818f45000)
  • libvpx.so.5 => /usr/lib/libvpx.so.5 (0x00007f68189bb000)
  • libasound.so.2 => /usr/lib/libasound.so.2 (0x00007f68186db000)
  • libsnappy.so.1 => /usr/lib/libsnappy.so.1 (0x00007f68184d3000)
  • libminizip.so.1 => /usr/lib/libminizip.so.1 (0x00007f68182c7000)
  • libxml2.so.2 => /usr/lib/libxml2.so.2 (0x00007f6817f61000)
  • libxslt.so.1 => /usr/lib/libxslt.so.1 (0x00007f6817d22000)
  • liblcms2.so.2 => /usr/lib/liblcms2.so.2 (0x00007f6817ac7000)
  • libQt5Qml.so.5 => /usr/lib/libQt5Qml.so.5 (0x00007f6817490000)
  • libGLX.so.0 => /usr/lib/libGLX.so.0 (0x00007f6817260000)
  • libGLdispatch.so.0 => /usr/lib/libGLdispatch.so.0 (0x00007f6816f92000)
  • libgraphite2.so.3 => /usr/lib/libgraphite2.so.3 (0x00007f6816d66000)
  • liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f6816b40000)
  • liblz4.so.1 => /usr/lib/liblz4.so.1 (0x00007f6816929000)
  • libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f681660d000)
  • libicudata.so.61 => /usr/lib/libicudata.so.61 (0x00007f6814a68000)
  • libblkid.so.1 => /usr/lib/libblkid.so.1 (0x00007f6814818000)
  • libplds4.so => /usr/lib/libplds4.so (0x00007f6814614000)
  • libplc4.so => /usr/lib/libplc4.so (0x00007f681440f000)
  • libxcb.so.1 => /usr/lib/libxcb.so.1 (0x00007f68141e6000)
  • libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f6813fd6000)
  • libswresample.so.3 => /usr/lib/libswresample.so.3 (0x00007f6813db9000)
  • libopencore-amrwb.so.0 => /usr/lib/libopencore-amrwb.so.0 (0x00007f6813ba5000)
  • libgsm.so.1 => /usr/lib/libgsm.so.1 (0x00007f6813999000)
  • libmp3lame.so.0 => /usr/lib/libmp3lame.so.0 (0x00007f6813721000)
  • libopencore-amrnb.so.0 => /usr/lib/libopencore-amrnb.so.0 (0x00007f68134f7000)
  • libopenjp2.so.7 => /usr/lib/libopenjp2.so.7 (0x00007f681329b000)
  • libspeex.so.1 => /usr/lib/libspeex.so.1 (0x00007f6813082000)
  • libtheoraenc.so.1 => /usr/lib/libtheoraenc.so.1 (0x00007f6812e43000)
  • libtheoradec.so.1 => /usr/lib/libtheoradec.so.1 (0x00007f6812c29000)
  • libvorbis.so.0 => /usr/lib/libvorbis.so.0 (0x00007f68129fd000)
  • libvorbisenc.so.2 => /usr/lib/libvorbisenc.so.2 (0x00007f6812754000)
  • libx264.so.152 => /usr/lib/libx264.so.152 (0x00007f68123d9000)
  • libx265.so.151 => /usr/lib/libx265.so.151 (0x00007f6811393000)
  • libxvidcore.so.4 => /usr/lib/libxvidcore.so.4 (0x00007f6811082000)
  • libva.so.2 => /usr/lib/libva.so.2 (0x00007f6810e60000)
  • libmodplug.so.1 => /usr/lib/libmodplug.so.1 (0x00007f6810ad5000)
  • libbluray.so.2 => /usr/lib/libbluray.so.2 (0x00007f6810884000)
  • libgmp.so.10 => /usr/lib/libgmp.so.10 (0x00007f68105f1000)
  • libgnutls.so.30 => /usr/lib/libgnutls.so.30 (0x00007f6810286000)
  • libssh.so.4 => /usr/lib/libssh.so.4 (0x00007f681000a000)
  • libva-drm.so.2 => /usr/lib/libva-drm.so.2 (0x00007f680fe07000)
  • libva-x11.so.2 => /usr/lib/libva-x11.so.2 (0x00007f680fc01000)
  • libvdpau.so.1 => /usr/lib/libvdpau.so.1 (0x00007f680f9fd000)
  • libdrm.so.2 => /usr/lib/libdrm.so.2 (0x00007f680f7eb000)
  • libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f680f5cb000)
  • libXau.so.6 => /usr/lib/libXau.so.6 (0x00007f680f3c7000)
  • libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00007f680f1c1000)
  • libsoxr.so.0 => /usr/lib/libsoxr.so.0 (0x00007f680ef4d000)
  • libogg.so.0 => /usr/lib/libogg.so.0 (0x00007f680ed46000)
  • libp11-kit.so.0 => /usr/lib/libp11-kit.so.0 (0x00007f680ea19000)
  • libunistring.so.2 => /usr/lib/libunistring.so.2 (0x00007f680e698000)
  • libtasn1.so.6 => /usr/lib/libtasn1.so.6 (0x00007f680e485000)
  • libnettle.so.6 => /usr/lib/libnettle.so.6 (0x00007f680e24e000)
  • libhogweed.so.4 => /usr/lib/libhogweed.so.4 (0x00007f680e018000)
  • libgomp.so.1 => /usr/lib/libgomp.so.1 (0x00007f680ddea000)

I have tried several times to reinstall the package seafile-client. Unfortunately, no success.

edacval commented on 2018-05-12 23:35 (UTC) (edited on 2018-05-12 23:36 (UTC) by edacval)

Line "export PKG_CONFIG_PATH=/usr/lib/openssl-1.0/pkgconfig" in PKGBUILD after https://github.com/haiwen/seafile-client/commit/6c946592e1870aaf16e398b4ac1b051c67ba243d is obsolete. Builds and works with openssl 1.1 perfectly.

lulingar commented on 2018-04-02 19:57 (UTC) (edited on 2018-04-02 20:24 (UTC) by lulingar)

Even after removing all seafile-related packages, I get the missing libevent-2.0.so.5 error. Furthermore, my installed libevent is v2.1.6, and after succesfully building and installing this AUR package, I get this:

$ ldd $(which seafile-applet) | grep event
        libevent-2.1.so.6 => /usr/lib/libevent-2.1.so.6 (0x00007f7b848e8000)
        libevent-2.0.so.5 => not found

So even if it found the new libevent, it insists on using the version of the error...

... but never mind: I needed to cleanup an old version of ccnet. After doing so, no more libevent-2.0.so.5 error.

eolianoe commented on 2018-03-03 17:25 (UTC)

@urldog: could you try to add -Dqmake_executable=/usr/bin/qmake to the cmake command? If it's not working you need to find someway to "hide" anaconda during the build (changing path, building in a clean chroot).

urldog commented on 2018-02-25 21:30 (UTC) (edited on 2018-02-25 21:31 (UTC) by urldog)

Looks like anaconda mucks up the install. It seems to be doing something to Qt5:

uild type: Release
qt5 version: 5.6.2
CMake Error at /opt/anaconda/lib/cmake/Qt5/Qt5Config.cmake:26 (find_package):
Could not find a package configuration file provided by "Qt5WebEngineCore"
with any of the following names:

    Qt5WebEngineCoreConfig.cmake
    qt5webenginecore-config.cmake

Add the installation prefix of "Qt5WebEngineCore" to CMAKE_PREFIX_PATH or
set "Qt5WebEngineCore_DIR" to a directory containing one of the above
files.  If "Qt5WebEngineCore" provides a separate development package or
SDK, be sure it has been installed.
Call Stack (most recent call first):
CMakeLists.txt:190 (FIND_PACKAGE)


-- Configuring incomplete, errors occurred!
See also "/tmp/trizen-quesada/seafile-client/src/build/CMakeFiles/CMakeOutput.log".
==> ERROR: A failure occurred in build().
    Aborting...
:: Unable to build seafile-client - makepkg exited with code: 2

Doesn't build on my machine.

klemens commented on 2018-02-24 14:19 (UTC)

@urldog: Just remove ccnet-server, ccnet no longer depends on it. See the ccnet package for further discussion.

urldog commented on 2018-02-24 09:35 (UTC)

ccnet and ccnet-server in conflict. It doesn't build. Can anyone replicate?

hypobool commented on 2018-01-11 17:06 (UTC)

Getting a segfault when trying to run 6.1.4-1 after rebuilding/installing all dependencies.

eolianoe commented on 2017-08-22 20:03 (UTC)

@SonOfANoMomGoat: building fine here, are you sure that everything is up to date?

commented on 2017-08-18 19:34 (UTC)

Starting from no previous install, building entire stack in a chroot clean environment, and I'm getting an error with the x265 library. The package is looking for libx265.so.116 and on August 15th the x265 library was at libx265.so=130-64. Not really good on library conflicts, is there something I can do to fix this, or does the source need to be updated?

fragfutter commented on 2017-07-18 14:25 (UTC)

and i forgot ccnet-server. all well after also rebuilding it. Complete list: ccnet, ccnet-server, seafile, seafile-client

fragfutter commented on 2017-07-18 14:10 (UTC)

for 6.0.7-3 seafile-applet: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory removed ccnet, seafile, seafile-applet. Pacman -Syu. reboot. rebuild and installed ccnet, verfied that it hat no dependency on libevent-2.0 rebuild and installed seafile, verfied that it hat no dependency on libevent-2.0 rebuild and installed seafile-client. seafile-applet is linked against libevent-2.0

eolianoe commented on 2017-07-17 20:54 (UTC)

@urldog: Try to remove all the seafile components, update your system and rebuild everything. You may also check if the error also occurs when building all the components in a clean chroot [a]. Do you have any special configurations that may break the build?

urldog commented on 2017-07-17 16:09 (UTC)

@eoliaone: sure, how can I help you providing more data? What should I run?

eolianoe commented on 2017-07-16 21:31 (UTC)

@urldog: This is not the same error. Could you provide more details?

urldog commented on 2017-07-16 19:15 (UTC)

@eoliaone: I rebuilt all libs, still get: “seafile-applet” terminated by signal SIGSEGV (Address boundary error)

eolianoe commented on 2017-07-14 09:37 (UTC)

@urldog: please read the pinned comment. You need to rebuild all the seafile packages to get everything link properly.

urldog commented on 2017-07-14 09:35 (UTC)

On manjaro I get: seafile-applet: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory It's current, and I reinstalled seafile-client from the AUR.

eolianoe commented on 2017-07-06 18:30 (UTC)

@cripcate: the problem is not python, the trouble is that anaconda ships an qmake executable and CMake picks it but there is no all qt stuff. Try to remove anacond from your path or add '-DCMAKE_PREFIX_PATH=/usr' to the cmake line in the PKGBUILD.

cripcate commented on 2017-07-06 10:06 (UTC)

@eolianoe Ah, so that's the problem. anaconda is in my pythoon path so i guess it is my default python distribution. how can i tell it to pick the system one? Sorry im a noob and dont know how to edit pkgbuilds etc

meister1337 commented on 2017-07-02 19:29 (UTC)

rebuilt seafile, seafile-client, ccnet and ccnet-server, fixed it.

Ondrej.it commented on 2017-07-02 09:31 (UTC) (edited on 2017-07-02 09:54 (UTC) by Ondrej.it)

@eolianoe not working for me... Only cp https://transfer.sh/C3hal/libevent-2.0.so.5.1.10 old version /usr/lib/libevent-2.0.so.5.1.10 works for me.

eolianoe commented on 2017-06-30 08:44 (UTC)

@cripcate: CMake picks the wrong Qt5 config file: it takes the one from anaconda instead of the system one.

eolianoe commented on 2017-06-30 08:43 (UTC)

@all: when you have some 'error while loading shared libraries', you need to rebuild every components.

cybertron commented on 2017-06-30 08:15 (UTC)

gna @revelation thanks ... too many packages for seafile -.- it works and sounds realy stupid that you need to have a "server" package installed for client ^^

Revelation60 commented on 2017-06-30 08:00 (UTC)

@cybertron: you also need to update ccnet-server.

cripcate commented on 2017-06-29 21:12 (UTC)

When I try to install i still get this error: -- Found PkgConfig: /usr/bin/pkg-config (found version "0.29.2") Build type: Release qt5 version: 5.6.2 CMake Error at /opt/anaconda/lib/cmake/Qt5/Qt5Config.cmake:26 (find_package): Could not find a package configuration file provided by "Qt5WebEngineCore" with any of the following names: Qt5WebEngineCoreConfig.cmake qt5webenginecore-config.cmake Add the installation prefix of "Qt5WebEngineCore" to CMAKE_PREFIX_PATH or set "Qt5WebEngineCore_DIR" to a directory containing one of the above files. If "Qt5WebEngineCore" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): CMakeLists.txt:190 (FIND_PACKAGE) -- Configuring incomplete, errors occurred! See also "/tmp/yaourt-tmp-nils/aur-seafile-client/src/build/CMakeFiles/CMakeOutput.log". qt5-webengine is installed and up to date. Reinstalling doesn't make a difference. All other dependencies are installed. I also can't build seafile-client from source (https://github.com/haiwen/seafile-client). So im all out of options. Any help?

cybertron commented on 2017-06-29 17:21 (UTC)

I rebuilt all components ... still the same problem

alexanderp commented on 2017-06-29 10:16 (UTC)

Ok, I've fixed it. seafile and ccnet also needed to be rebuilt because they also use libevent. I suggest you bump the PKGBUILD version on seafile, seafile-client, ccnet and ccnet-server to trigger a rebuild on -Syu

alexanderp commented on 2017-06-29 10:04 (UTC)

Hi. As of today I receive the following error: seafile-applet: error while loading shared libraries: libevent-2.0.so.5: cannot open shared object file: No such file or directory I've rebuilt both this and ccnet-server which depends on libevent but I still cannot the applet and GUI to launch.

eolianoe commented on 2017-06-01 08:42 (UTC)

@urldog: try to rebuild the package, but I cannot test with Manjaro.

Psynigmashi commented on 2017-05-28 04:23 (UTC)

Thank you @Dezponia. My seafile program wasn't launching for a few days now and after rebuilding it with yaourt, it's now working perfectly fine.

eolianoe commented on 2017-05-26 09:15 (UTC)

@Captain_Rage: openssl-1.0 is already resolved by the qt5 deps. @ndandanov & @noEntry: as @Dezponia said a rebuild resolves the new soname/symbols, no need of a downgrade, see the wiki [a]. [a] : https://wiki.archlinux.org/index.php/Frequently_asked_questions#What_if_I_run_a_full_system_upgrade_and_there_will_be_an_update_for_a_shared_library.2C_but_not_for_the_apps_that_depend_on_it.3F

ndandanov commented on 2017-05-26 07:55 (UTC) (edited on 2017-05-26 07:55 (UTC) by ndandanov)

Thank you, @Dezponia! After upgrading openssl-1.0 and qt5-base, it was a matter of just running: pacaur -S seafile-client --rebuild Now it works properly.

Dezponia commented on 2017-05-26 06:55 (UTC)

@ndandanov Try simply re-installing the seafile-client package. This is how I did it with the AUR-Helper "aurget". aurget -S seafile-client That launched a re-install and thus also a rebuild since its an AUR package. If it doesn't work that way with pacaur then I'll have to direct you to get help from the pacaur people. If nothing else you can just build it manually as per the Arch wiki (https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages)

ndandanov commented on 2017-05-26 06:47 (UTC) (edited on 2017-05-26 06:47 (UTC) by ndandanov)

@Dezponia, Sorry if this question is too basic, but could you please provide a simple example how one could rebuild the package? Perhaps use this information: https://wiki.archlinux.org/index.php/downgrading_packages#Rebuild_the_package? I am using pacaur if this has any importance. I'm relatively new to Arch, but have some experience with Debian-based distros. :) Thanks! Nikolay

Dezponia commented on 2017-05-25 21:53 (UTC)

Simply rebuilding seafile-client fixed this issue for me earlier today. Using the latest libraries here. Perhaps try that before downgrading.

ndandanov commented on 2017-05-25 21:50 (UTC)

After the latest updates of openssl-1.0: [2017-05-25 23:52] [ALPM] upgraded openssl-1.0 (1.0.2.k-3 -> 1.0.2.k-4) [2017-05-26 00:27] [ALPM] upgraded openssl-1.0 (1.0.2.k-4 -> 1.0.2.l-1) I cannot launch the Seafile client GUI: [nikolay@nikolay-t440p ~]$ seafile-applet seafile-applet: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.2d' not found (required by seafile-applet) I had to downgrade both openssl-1.0 and qt5-base: [nikolay@nikolay-t440p ~]$ sudo pacman -U /var/cache/pacman/pkg/openssl-1.0-1.0.2.k-3-x86_64.pkg.tar.xz [nikolay@nikolay-t440p ~]$ sudo pacman -U /var/cache/pacman/pkg/qt5-base-5.8.0-11-x86_64.pkg.tar.xz (Source: https://wiki.archlinux.org/index.php/downgrading_packages) Now the Seafile client seems to be running properly. :)

noEntry commented on 2017-05-25 21:43 (UTC)

Any way to fix this issue? Installing openssl-1.0 did not solves this issue. seafile-applet: /usr/lib/libcrypto.so.1.0.0: version `OPENSSL_1.0.2d' not found (required by seafile-applet)

Captain_Rage commented on 2017-05-25 19:05 (UTC)

Package openssl-1.0 should be marked as a dependency.

a-bostaurus commented on 2017-05-15 13:59 (UTC)

I have to apologize. It's not a problem of seafile, but a problem of my special configuration. The package is ok, Manjaro is okay, my system got some problems ...

gnacho commented on 2017-05-15 11:34 (UTC)

Confirmed that 6.06 fixed the errors with Manjaro and "Transport Error" with Antergos / Apricity :) Thanks a lot!!

Captain_Rage commented on 2017-05-15 08:31 (UTC)

6.0.6 fixed the 'Transport Error' issue. Thanks alot!

eolianoe commented on 2017-05-15 07:10 (UTC) (edited on 2017-05-15 07:12 (UTC) by eolianoe)

@a-bostaurus: it's compiling and running fine here, I'll try to test as much as I can the packages before releasing them. The packages are tested with Arch and not Manjaro, you may have a different version of some libraries and I cannot test. Maybe you can with pure makepkg in a clean-chroot [a] and be sure to have a fully up to date system before to build something. It seems that some program are not linked with the right libraries. [a] https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

a-bostaurus commented on 2017-05-15 06:30 (UTC)

This morning the update came in. That was great. Thank you very much. But there is still a problem: A mistake happened in build ... I interrupped ... MAKePkg could not create seafile-client This is a little bit horrible because I use it productive and professional ... The terminal says: /usr/bin/ld: warning: libwebpmux.so.2, needed by /usr/lib/libavcodec.so.57, not found (try using -rpath or -rpath-link) /usr/bin/ld: warning: libwebp.so.6, needed by /usr/lib/libavcodec.so.57, not found (try using -rpath or -rpath-link) /usr/lib/libavcodec.so.57: undefined reference to `WebPAnimEncoderDelete' /usr/lib/libavcodec.so.57: undefined reference to `WebPAnimEncoderNewInternal' /usr/lib/libavcodec.so.57: undefined reference to `WebPAnimEncoderOptionsInitInternal' /usr/lib/libavcodec.so.57: undefined reference to `WebPAnimEncoderAssemble' /usr/lib/libavcodec.so.57: undefined reference to `WebPAnimEncoderAdd' collect2: Fehler: ld gab 1 als Ende-Status zurück make[2]: *** [CMakeFiles/seafile-applet.dir/build.make:5389: seafile-applet] Fehler 1 make[1]: *** [CMakeFiles/Makefile2:997: CMakeFiles/seafile-applet.dir/all] Fehler 2 make: *** [Makefile:130: all] Fehler 2 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... ==> FEHLER:Makepkg konnte seafile-client nicht erstellen.

a-bostaurus commented on 2017-05-14 11:51 (UTC)

After the last Manjaro Update seafile does not work anymore. If I type in terminal yaourt -Ss seafile, it is said "out of date". I don't know, what the problem is.

Captain_Rage commented on 2017-05-09 10:38 (UTC)

@gnacho I tried typing seaf-daemon --daemon in a terminal. It doesn't fix the problem for me, but now the Seafile applet displays 'Failed to establish secure connection. Please check server SSL certificate' on top of 'Transport Error'. What is interesting though is that a folder called 'seafile' gets created upon running that command, even though the proper folder 'Seafile' exists in my home folder. Yes, it helps. Thank you for providing the information. I will keep on troubleshooting. :)

gnacho commented on 2017-05-08 11:23 (UTC)

@Captain_Rage @cybertron seaf-daemon --daemon fix the problems, but just until you restart the computer. I'm still trying to realize why I get this issue, I thought it has something to do with server side, but I'm not really sure now. It happens with different computers (i7, i5, m5, i3) all under ApricityOs x86_64. Hope that helps.

cybertron commented on 2017-05-06 16:59 (UTC)

@captain_rage killing my client configuration and new checkout helped me by the "transport error" don't know what the problem was, with the same client build on an another account on the same machine, all worked fine.

Captain_Rage commented on 2017-05-06 12:51 (UTC)

@gnacho: Having the same problem here. Which architecture did you compile Seafile client for? I'm using x86_64 for my Seafile client and it keeps showing 'Transport Error'.

gnacho commented on 2017-05-05 09:21 (UTC)

#eolianoe it did, many thanks. Now I just get this "Transport error" but it was there already before.

eolianoe commented on 2017-05-05 08:30 (UTC)

@gnacho: a rebuild should fix the issue.

gnacho commented on 2017-05-05 08:26 (UTC)

After last update I get the following message: seafile-applet: relocation error: seafile-applet: symbol _Znwm, version Qt_5 not defined in file libQt5WebEngineCore.so.5 with link time reference Under GNOME 3.24.

Psynigmashi commented on 2017-05-05 00:24 (UTC)

Is anyone else having problems with the seafile text? My text is showing up as a weird font that's unreadable. This only is happening in seafile and no other programs.

cripcate commented on 2017-05-02 21:22 (UTC)

@eolianoe: Guess I'll have to go some research then. Thank you nontheless, and sorry for being so nooby.

eolianoe commented on 2017-05-02 21:05 (UTC)

@cripcate: please read [a] in order to understand what you are doing. As a side note, I don't know much about Antergos and I cannot test the PKGBUILD with it. I don't fully understand your log, but it seems that you are using an old and specific Qt5 installation. You should upgrade your system and check your qt installation. [a] https://wiki.archlinux.org/index.php/Arch_User_Repository

cripcate commented on 2017-05-02 20:46 (UTC)

I did "yaourt -S seafile-client" without having any dependencies installed. Then i used "makepkg -L" which produced the following output: ==> ERROR: PKGBUILD does not exist. ==> ERROR: An unknown error has occurred. Exiting... i also did "yaourt -S seafile-client > seafile.log" afterwards (dependencies were installed now) which produced the following: https://gist.github.com/cripcate/d72c0a1d898aec586387e5ead10e09fb as the resulting log https://gist.github.com/cripcate/4e97c751db337f39c1bf0a111d90097a in the stdout

eolianoe commented on 2017-05-02 20:20 (UTC)

@cripcate: use 'makepkg -L' or redirect the standard output.

cripcate commented on 2017-05-02 19:51 (UTC) (edited on 2017-05-02 19:55 (UTC) by cripcate)

@eolianoe: Sorry, but where can i find makepkg logs? I'm using antergos (and only since two days) and am trying to install it via their gui tool for installing software. sudo yaourt -S seafile-client in terminal produced the same error tho.

eolianoe commented on 2017-05-02 18:30 (UTC) (edited on 2017-05-02 20:54 (UTC) by eolianoe)

@cripcate: could you paste the log of makepkg rather than the log of CMake, because there is no error in this log

cripcate commented on 2017-05-02 10:41 (UTC)

When installing seafile-client i get: -- Configuring incomplete, errors occurred! See also "/tmp/pamac-build-nils/seafile-client/src/build/CMakeFiles/CMakeOutput.log". ==> ERROR: A failure occurred in build(). Aborting... my logs are https://pastebin.com/anfgdfUh

snack commented on 2017-05-01 14:05 (UTC)

@Varakh: I had the same issue one moment ago after updating my parent's system. Again, rebuilding seafile-client (and just that) fixed the problem.

snack commented on 2017-05-01 12:44 (UTC)

@ciil: not needed here. I just did yaourt -S seafile-client to fix the error Varakh is experiencing. Other mileage may vary, though.

ciil commented on 2017-05-01 12:38 (UTC)

@Varakh @snack: You need to first uninstall all required (or at least the built packages), eg with yaourt -Rsn seafile-client. And then rebuild the full chain, including seafile and ccnet, again.

mitchlazzlo commented on 2017-05-01 11:46 (UTC)

Launching the seaf-daemon separatly in a terminal resolves the "Transport error" problem. However fixing this could be nice.

snack commented on 2017-05-01 08:37 (UTC)

@Varakh: rebuild seafile-client. It fixed that problem for me.

Varakh commented on 2017-05-01 08:34 (UTC) (edited on 2017-05-01 08:36 (UTC) by Varakh)

I am getting the following on startup: seafile-applet: relocation error: seafile-applet: symbol _Znwm, version Qt_5 not defined in file libQt5WebEngineCore.so.5 with link time reference Also, can you clean up your pkg build? There is no such pkg as seafile-client-qt5.

seidler2547 commented on 2017-05-01 07:59 (UTC)

Having the same problem. All libraries from all servers appear unsynced. Tried rebuilding but it didn't help.

Captain_Rage commented on 2017-04-28 19:48 (UTC)

When I drag and drop a file to the library icon in the Seafile applet the file gets uploaded. It still refuses to sync the files locally, though, and keeps showing the 'Transport Error' message. Very peculiar.

snack commented on 2017-04-28 17:24 (UTC)

@Captain_Rage: I noticed the presence of the server in the dropdown menu too. It sounds strange also to me. About the openssl packages in my system: lib32-openssl 1:1.1.0.e-1 lib32-openssl-1.0 1.0.2.k-1 openssl 1.1.0.e-1 openssl-1.0 1.0.2.k-3

Captain_Rage commented on 2017-04-28 17:10 (UTC)

@snack: I tried to delete only ~/.ccnet but that didn't help. When I delete both configuration directories and start up the Seafile applet, the configuration seems to be clean, except that the server address is still in the dropdown menu, which is a bit strange. Does the Seafile client keep any configuration files in other locations, besides ~/.ccnet and ~/Seafile/.seafile-data? @snack: Which packages of openssl do you have installed? Maybe my Seafile client got built against the wrong version, since I got openssl 1.1.0.e-1, openssl-1.0 1.0.2.k-3, lib32-openssl 1:1.1.0.e-1 and lib32-openssl-1.0 1.0.2.k-1 installed. Not sure how to troubleshoot this.

snack commented on 2017-04-28 15:52 (UTC)

@Captain_Rage: I had the same error messages in the log, which were solved by deleting ~/.ccnet. No idea why my solution doesn't work for you.

Captain_Rage commented on 2017-04-28 15:33 (UTC)

The Seafile applet starts fine but all the icons are yellow clouds (no sync) now and it keeps throwing a 'Transport Error' message. The problem appeared here as well after the last update. Deleting ~/.ccnet and ~/Seafile.seafile-data and setting everything up from a clean directory doesn't help. Rebuilding and reinstalling doesn't help either. The server got upgraded successfully and can be accessed from two Android devices, so the problem seems to lie with the desktop client. Looking into ~/.ccnet/logs/applet.log, this keeps appearing: '[2017-04-28 17:11:30][RPC] failed to start rpc server: 511 Unknown service. [2017-04-28 17:11:30][RPC] failed to start rpc server: 511 Unknown service. [2017-04-28 17:11:30]failed to get repo list: Transport Error' How did you resolve it?

blubbblubb commented on 2017-04-28 08:39 (UTC)

@llmecat thanks for the hint, reinstalling everything (again) fixed the qt5-webengine error.

ToK commented on 2017-04-27 15:57 (UTC)

I don't know why. Everything works fine now after a fresh new Install of arch :) Maybe because of setting not to check the https certificat (which I did before)...

ToK commented on 2017-04-27 14:44 (UTC)

Still not working. I tried installing on a new system (and removing ~/.ccnet and ~/seafile/.seafile). I tried starting seaf-daemon after starting the applet. I would think it should be my private server. But my Macbook syncs fine with seafile-client 6.0.4...

limecat commented on 2017-04-27 14:08 (UTC)

I also had this error: seafile-applet: relocation error: seafile-applet: symbol _Znwm, version Qt_5 not defined in file libQt5WebEngineCore.so.5 with link time reference Uninstalling everything (ccnet, seafile-client, all deps etc.) and reinstalling got the applet going again, but still gave me the Transport error on trying to sync with my existing libraries. Manually starting the seaf-daemon solves that as a workaround, and I can confirm that rm -rf on ~/.ccnet and ~/Seafile/.seafile-data makes everything work ok again.

eolianoe commented on 2017-04-27 13:52 (UTC)

@blubbblubb: everything is fine here, with the qt5-webengine-5.8.0-6. @polslinux: I made the PKGBUILD for seadrive [a], but I've no idea how to make it works... (if you have any idea please comment on the seadrive-gui page) [a] https://aur.archlinux.org/packages/seadrive-gui/

blubbblubb commented on 2017-04-27 11:52 (UTC) (edited on 2017-04-27 11:53 (UTC) by blubbblubb)

probably a qt5-webengine or seafile source problem but it cant hurt to mention it here as well, with the newest qt5-webengine (qt5-webengine-5.8.0-6) it is not possible to start the seafile-applet (all the newer qt5 packages, the ones in staging/beta also show problems) seafile-applet: relocation error: seafile-applet: symbol _Znwm, version Qt_5 not defined in file libQt5WebEngineCore.so.5 with link time reference I never submitted a bug for a package before so I will need to read up on the guidelines before doing so, if anyone feels like reporting this in the right place feel free to do so ;)

eolianoe commented on 2017-04-27 11:31 (UTC)

Nice that you find away to solve the problem. @polslinux: I'll look at this new client and see if it's easy to package it on linux

polslinux commented on 2017-04-26 18:53 (UTC)

@eolianoe: interested in packaging also the seadrive client? :) thanks!

blubbblubb commented on 2017-04-26 18:27 (UTC) (edited on 2017-04-26 18:27 (UTC) by blubbblubb)

Only removing ~/.ccnet did not work for me. I had to remove ~/.ccnet and ~/Seafile/.seafile-data All libraries are syncing now.

snack commented on 2017-04-26 17:04 (UTC)

Removing ~/.ccnet fixed the problem on my system: seaf-daemon no longer segfaults and sync works again. I had to re-configure the account and sync libraries: in doing so I overwrited the current version on my pc with the old version put on the server 4 hours ago. It was not a big issue for me but could be for others, so take care (I suggest to create a local backup of your libraries before syncing).

blubbblubb commented on 2017-04-26 16:12 (UTC) (edited on 2017-04-27 09:34 (UTC) by blubbblubb)

tl:dr Workaround: manually start seaf-daemon after launching the client/applet I got the same segfault with seaf-daemon, also did a full reinstall on my System and updated my Server to 6.0.9 Workaround for now: If i start the seaf-daemon from hand again with the client (applet) already running it seems to be running fine.

eolianoe commented on 2017-04-26 15:39 (UTC)

@ToK, @snack: just made a 'yaourt -Rncds libsearpc && yaourt -S seafile-client' and everything is going fine. No idea why there are failures on your systems :(

ToK commented on 2017-04-26 15:26 (UTC)

I just tried on a fresh Antergos system (before this I uses plain Arch) with the same result...

snack commented on 2017-04-26 15:24 (UTC)

@eolianoe: maybe not building in a clean chroot might be the problem? If so, it's strange since I always updated with yaourt with no problems up to now. Did you try building in a standard environment? I will try the chroot as soon as I have time.

eolianoe commented on 2017-04-26 15:00 (UTC)

@ToK, @snack: I've just rebuild the seafile packages in a clean and up-to-date chroot and I'm not seeing any segfault on two different computers. You may have some special configuration which may break something

ToK commented on 2017-04-26 14:09 (UTC)

I also got a segfault in seaf-daemon: Apr 26 15:56:39 clodsahamp kernel: pool[3981]: segfault at 100 ip 0000000000000100 sp 00007f74f25b3208 error 14 in seaf-daemon[400000+99000] Apr 26 15:56:39 clodsahamp systemd[1]: Started Process Core Dump (PID 3982/UID 0). Apr 26 15:56:39 clodsahamp systemd-coredump[3983]: Process 3978 (seaf-daemon) of user 1000 dumped core. Stack trace of thread 3981: #0 0x0000000000000100 n/a (n/a) And i got a segfault in seafile-applet: Apr 26 15:56:57 clodsahamp kernel: seafile-applet[3711]: segfault at 8 ip 00007f5ebb601b51 sp 00007fff1a3b8010 error 4 in libQt5Widgets.so.5.8.0[7f5ebb46b000+628000] Apr 26 15:56:57 clodsahamp systemd[1]: Started Process Core Dump (PID 4136/UID 0). Apr 26 15:56:57 clodsahamp systemd-coredump[4137]: Process 3711 (seafile-applet) of user 1000 dumped core. Stack trace of thread 3711: #0 0x00007f5ebb601b51 _ZNK7QWidget14ensurePolishedEv (libQt5Widgets.so.5) #1 0x00007f5ebb602ae9 _ZN7QWidget10showNormalEv (libQt5Widgets.so.5) #2 0x00000000004effd9 _ZN10MainWindow10showWindowEv (seafile-applet) #3 0x0000000000492139 _ZN13SeafileApplet10warningBoxERK7QStringP7QWidget (seafile-applet) #4 0x00000000004921c1 _ZN13SeafileApplet12errorAndExitERK7QString (seafile-applet) #5 0x00000000004a4c57 _ZN13DaemonManager20checkSeafDaemonReadyEv (seafile-applet) #6 0x00007f5eba907d79 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #7 0x00007f5eba914dc8 _ZN6QTimer10timerEventEP11QTimerEvent (libQt5Core.so.5) #8 0x00007f5eba908b93 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #9 0x00007f5ebb5be34c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #10 0x00007f5ebb5c5b61 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #11 0x00007f5eba8dc470 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #12 0x00007f5eba92fcee _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5) #13 0x00007f5eba930579 n/a (libQt5Core.so.5) #14 0x00007f5ec23c17b7 g_main_context_dispatch (libglib-2.0.so.0) #15 0x00007f5ec23c1a20 n/a (libglib-2.0.so.0) #16 0x00007f5ec23c1acc g_main_context_iteration (libglib-2.0.so.0) #17 0x00007f5eba93107f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #18 0x00007f5eba8da8ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #19 0x00007f5eba8e2e14 _ZN16QCoreApplication4execEv (libQt5Core.so.5) #20 0x000000000048e6ff main (seafile-applet) #21 0x00007f5eb9d31511 __libc_start_main (libc.so.6) #22 0x000000000048edca _start (seafile-applet) Stack trace of thread 3805: #0 0x00007f5eb9df367d poll (libc.so.6) #1 0x00007f5ec23c19b6 n/a (libglib-2.0.so.0) #2 0x00007f5ec23c1acc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f5eba93107f _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #4 0x00007f5eba8da8ca _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #5 0x00007f5eba6fca73 _ZN7QThread4execEv (libQt5Core.so.5) #6 0x00007f5ec1a79125 n/a (libQt5DBus.so.5) #7 0x00007f5eba7016d8 n/a (libQt5Core.so.5) #8 0x00007f5ec36cb2e7 start_thread (libpthread.so.0) #9 0x00007f5eb9dfd54f __clone (libc.so.6) Stack trace of thread 3756: #0 0x00007f5eb9df367d poll (libc.so.6) #1 0x00007f5eace5d8e0 n/a (libxcb.so.1) #2 0x00007f5eace5f679 xcb_wait_for_event (libxcb.so.1) #3 0x00007f5ea4d8a239 n/a (libQt5XcbQpa.so.5) #4 0x00007f5eba7016d8 n/a (libQt5Core.so.5) #5 0x00007f5ec36cb2e7 start_thread (libpthread.so.0) #6 0x00007f5eb9dfd54f __clone (libc.so.6) Stack trace of thread 3761: #0 0x00007f5eb9df367d poll (libc.so.6) #1 0x00007f5ec23c19b6 n/a (libglib-2.0.so.0) #2 0x00007f5ec23c1acc g_main_context_iteration (libglib-2.0.so.0) #3 0x00007f5ec23c1b11 n/a (libglib-2.0.so.0) #4 0x00007f5ec23e9295 n/a (libglib-2.0.so.0) #5 0x00007f5ec36cb2e7 start_thread (libpthread.so.0) #6 0x00007f5eb9dfd54f __clone (libc.so.6) Stack trace of thread 3762: #0 0x00007f5eb9df367d poll (libc.so.6) #1 0x00007f5ec23c19b6 n/a (libglib-2.0.so.0) #2 0x00007f5ec23c1d42 g_main_loop_run (libglib-2.0.so.0) #3 0x00007f5eb8eafff6 n/a (libgio-2.0.so.0) #4 0x00007f5ec23e9295 n/a (libglib-2.0.so.0) #5 0x00007f5ec36cb2e7 start_thread (libpthread.so.0) #6 0x00007f5eb9dfd54f __clone (libc.so.6) Stack trace of thread 3779: #0 0x00007f5ec36d1ca6 pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0) #1 0x00007f5e93d72e44 n/a (libGLX_nvidia.so.0) #2 0x00007f5e92a90394 n/a (libnvidia-glcore.so.378.13) #3 0x00007f5e93d7212c n/a (libGLX_nvidia.so.0) #4 0x00007f5ec36cb2e7 start_thread (libpthread.so.0) #5 0x00007f5eb9dfd54f __clone (libc.so.6) I removed every packet concerning seafile-applet like snack did. And I remove ~/.ccnet and ~/Seafile/.seafile I tried it in gnome and in plasma with a fresh user. Noting changed I could access the server by clicking in the "main window" of seafile applet. But syncing doesn't work. I also have a Mac with seafile-client 6.0.4 which works fine. So it could not be may Server, i think (running armbian on a cubietruck).

snack commented on 2017-04-26 13:42 (UTC)

@eolianoe: I just did a full rebuild of the stack: libsearpc ccnet-server ccnet seafile seafile-client in this order using yaourt, without touching any PKGBUILD. Nothing changed, seaf-daemon keeps crashing. @carlos @ToK: do you see the same segfault of seaf-daemon in journalctl?

eolianoe commented on 2017-04-26 12:31 (UTC)

@snack: I'm not seeing all theses errors... Could you try to rebuild all the seafile related packages in the proper order to get everything linked properly?

snack commented on 2017-04-26 12:17 (UTC) (edited on 2017-04-26 12:24 (UTC) by snack)

I noticed that when starting the client the seaf-daemon crashes. From journald: apr 26 14:09:59 elric kernel: pool[23823]: segfault at 100 ip 0000000000000100 sp 00007fdf8a3fe208 error 14 in seaf-daemon[400000+99000] apr 26 14:09:59 elric systemd[1]: Started Process Core Dump (PID 23826/UID 0). -- Subject: Unit systemd-coredump@9-23826-0.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-coredump@9-23826-0.service has finished starting up. -- -- The start-up result is done. apr 26 14:10:00 elric systemd-coredump[23827]: Process 23820 (seaf-daemon) of user 10085 dumped core. Stack trace of thread 23823: #0 0x0000000000000100 n/a (n/a) -- Subject: Process 23820 (seaf-daemon) dumped core -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- Documentation: man:core(5) -- -- Process 23820 (seaf-daemon) crashed and dumped core. -- -- This usually indicates a programming error in the crashing program and -- should be reported to its vendor as a bug. After manually restarting seaf-daemon from command line after the client I am able again to sync with remote. Unfortunately the crash happens again when the client is stopped and restarted. It seems that the client launches the daemon in a way that makes it crash, while launching it from the command line without any argument works.

snack commented on 2017-04-26 12:06 (UTC)

@eolianoe: the server is maintained by the IT department of my institute, it has not been updated in a while and it worked fine up to this morning. Is client 6.0.4 known to break compatibility with old servers? Or maybe the OpenSSL mayhem broke something? I see that seafile-applet still links libssl.so.1.0.0 so I guess that it should not be the root of the problem, but who knows...

eolianoe commented on 2017-04-26 11:32 (UTC)

@snack, @ToK: the seafile client is working fine on my setup (using a server maintained by a third-party). Maybe the problem is linked to your server rather than the client

carlos commented on 2017-04-26 11:31 (UTC)

Same problem here: ``` [26.04.2017 13:28:01][RPC] failed to start rpc server: 511 Unknown service. [26.04.2017 13:28:01][RPC] failed to start rpc server: 511 Unknown service. [26.04.2017 13:28:01]failed to get repo list: Transport Error ```

ToK commented on 2017-04-26 11:09 (UTC)

I have the same problem. Neither downgrading the package to 6.0.3 (bei changing the pkgver and sha5sums in pkgbuild) nor upgrading the server to 6.0.9 (the newest vor "pi") doesnt solve the problem.

snack commented on 2017-04-26 08:40 (UTC)

After today's upgrade to 6.0.4-2 it seems that the association between local and remote folders is gone. If I try to set the sync again I get this error: Failed to add download task: Transport Error I guess that it has something to do with the recent migration to OpenSSL 1.1 and all the relate compatibility work. Anyone with the same issue?

polslinux commented on 2017-04-25 15:44 (UTC)

@hhopimet cool! Back when I was trying it on a vm with testing enabled compiling the client wasn't possible. Still, there's a fundamental problem: the core is compiled against 1.0 while qt is compiled against 1.1. This could lead to some problem[1] [1] https://lists.debian.org/debian-devel/2016/11/msg00754.html

eolianoe commented on 2017-04-25 11:27 (UTC)

@Revelation60: openssl and openssl-1.0 are already resolved by the other dependencies

Revelation60 commented on 2017-04-25 11:12 (UTC)

Installing the extra/openssl-1.0 1.0.2.k-3 seems to do the trick. This should be one of the dependencies.

hopimet commented on 2017-04-25 06:27 (UTC)

I have core/openssl 1.1.0.e-1 and extra/openssl-1.0 1.0.2.k-3 installed and seafile-client builds fine.

eolianoe commented on 2017-04-24 20:53 (UTC)

@polslinux: I know, all the seafile packages need to be fixed to build against openssl-1.0. I'm trying to find a fix for each package, which will need some more time

polslinux commented on 2017-04-24 19:24 (UTC)

maybe the fix for cmake listed here? https://www.archlinux.org/todo/openssl-110-rebuild/

polslinux commented on 2017-04-24 19:24 (UTC)

cannot compile with openssl-1.1.0...

StraxKvar commented on 2017-02-12 17:20 (UTC)

The problem with seafile dependency checksum is now fixed and install works well.

StraxKvar commented on 2017-02-12 11:55 (UTC)

When building, this looks to use seafile-6.0.2.tar.gz, as in comments below with failed checksums. But the current version of that dependency is seafile-6.0.3.tar.gz. Also the checksum for 6.0.3 is currently broken: https://aur.archlinux.org/packages/seafile/

bsidb commented on 2017-02-12 02:01 (UTC)

==> Validating source files with sha256sums... seafile-6.0.2.tar.gz ... FAILED libseafile.in.patch ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build seafile. Meet the same problem here. Thanks!

StraxKvar commented on 2017-02-11 21:54 (UTC)

==> Validating source files with sha256sums... seafile-6.02.tar.gz ... FAILED libseafile.in.patch ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build seafile. --- Please sort this out. Thanks.

fedkey_yang commented on 2017-02-03 14:23 (UTC)

谢谢,seafile官方没有arch版本的,这里的软件解决了我的问题。

a-bostaurus commented on 2017-01-21 07:53 (UTC)

What helped were the following commads: "sudo pacman -S fontconfig freetype2" and then I agreed to delete fontconfig-infinality-ultimate and freetype2-infinality-ultimate. After that it was no problem to update seafile-client (and copyq). I apologize to eolianoe for making you busy, but it was me who was wrrong with to old packages.

a-bostaurus commented on 2017-01-19 09:54 (UTC)

In the meantime I am shure that my trouble is not a problem of seafile. I installed successful an alder version so now i can work. But after the last update I did not start virtualbox, but some minutes ago I tried but it did not work. The information about the problem is almost the same as trying the newest version of seafile: "virtualbox VirtualBox: supR3HardenedMainGetTrustedMain: dlopen("/usr/lib/virtualbox/VirtualBox.so",) failed: /usr/lib/libharfbuzz.so.0: undefined symbol: FT_Get_Var_Blend_Coordinates"

eolianoe commented on 2017-01-18 21:22 (UTC)

@a-bostaurus: you cannot rename libharfbuzz as seafile depends on it! Try to find the special configurations you made and if you cannot find it, build all seafile packages in a clean chroot [a]. As a side note, please post build logs in english in order to make the debug easier. ('export LANG=C' before the build should translate it) [a] https://wiki.archlinux.org/index.php/DeveloperWiki:Building_in_a_Clean_Chroot

a-bostaurus commented on 2017-01-18 20:00 (UTC)

Sorry, that did not help. So I renamed libharfbuzz... and that mistake did not appear again. But the problem with seafile-applet still exist: "/usr/lib/libQt5Gui.so.5.7.1: undefined reference to `hb_unicode_funcs_set_compose_func' /usr/lib/libQt5Gui.so.5.7.1: undefined reference to `hb_font_funcs_destroy' /usr/lib/libQt5WebEngineCore.so.5.7.1: undefined reference to `hb_ot_layout_has_positioning' /usr/lib/libQt5Gui.so.5.7.1: undefined reference to `hb_unicode_funcs_set_script_func' collect2: Fehler: ld gab 1 als Ende-Status zurück make[2]: *** [CMakeFiles/seafile-applet.dir/build.make:5385: seafile-applet] Fehler 1 make[1]: *** [CMakeFiles/Makefile2:997: CMakeFiles/seafile-applet.dir/all] Fehler 2 make: *** [Makefile:128: all] Fehler 2 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... ==> FEHLER:Makepkg konnte seafile-client nicht erstellen." Of course I rename the libharfbuzz...-file again.

eolianoe commented on 2017-01-18 14:28 (UTC)

@a-bostaurus: try to remove all seafile packages, then reinstall harfbuzz and all seafile packages. If it's working on your five others computers, there is a special configuration on the sixth which causes trouble.

a-bostaurus commented on 2017-01-18 09:57 (UTC) (edited on 2017-01-18 13:23 (UTC) by a-bostaurus)

There is harfbuzz on my computer, but no infinality ... "extra/harfbuzz 1.4.1-1 [installed] OpenType text shaping engine extra/harfbuzz-icu 1.4.1-1 [installed] OpenType text shaping engine (ICU integration) multilib/lib32-harfbuzz 1.4.1-1 [installed] OpenType text shaping engine (32-bit)" Should I deinstall harfbuzz? Some hours later: I had a look at the dependicies of harfbuzz. I fear deinstalling harfbuzz will mean to make my system unusabel. I.e. chromium needs it and so on. Because of i deinstalled seafile-client to get a clean new installation I just now cannot install seafile, although I need it strongly for my early work. Very annoying.

eolianoe commented on 2017-01-18 09:33 (UTC)

@snack: I think that they just regenerate the sources from the git tree without recreating a proper tag. It's a bit annoying and I think that I will use the commit hash to get the sources rather than the archive. @a-bostaurus: This may me linked to some harfbuzz and Infinality fonts bugs. DO you use them ?

Distorted commented on 2017-01-18 09:32 (UTC)

@a-bostaurus are you using infinality?

snack commented on 2017-01-18 09:26 (UTC)

I had similar problems with checksums this morning. When upgrading with yaourt I got this message: ==> Validating source files with sha256sums... seafile-6.0.2.tar.gz ... FAILED The cached version of seafile-6.0.2.tar.gz on my disk retrieved from previous updates did not pass the checksum of the current PKGBUILD, but evidently passed that of old PKGBUILD since I had no problems in previous updates. So I deleted the file and started the update again, to force a fresh download, and this time everything worked. So I'd say that seafile-6.0.2.tar.gz has changed upstream without changing the filename. Sounds a bit strange (to not say suspicious), but maybe there's an explanation for this?

a-bostaurus commented on 2017-01-18 09:23 (UTC)

I'm working with six arch computers. Everyone works with seafile. Whenever I try to update seafile-client there is some trouble. And never the same ... This time it is: "/usr/lib/libharfbuzz.so.0: undefined reference to `FT_Get_Var_Blend_Coordinates' collect2: Fehler: ld gab 1 als Ende-Status zurück make[2]: *** [CMakeFiles/seafile-applet.dir/build.make:5385: seafile-applet] Fehler 1 make[1]: *** [CMakeFiles/Makefile2:997: CMakeFiles/seafile-applet.dir/all] Fehler 2 make: *** [Makefile:128: all] Fehler 2 ==> FEHLER: Ein Fehler geschah in build(). Breche ab... ==> FEHLER:Makepkg konnte nicht erstellen." Deinstalling seafile-client with all its dependies and installing again did not help ...

MrKMG commented on 2017-01-17 15:52 (UTC)

SHA256SUM appears to be different: 8ac2eb3611e69b4fd85a9572714153566705c73e443cf2ae24da556c7cf12078 seafile-6.0.2.tar.gz

Captain_Rage commented on 2017-01-17 11:46 (UTC)

==> Validating source files with sha256sums... seafile-client-v6.0.2.tar.gz ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build seafile-client. The source doesn't get validated.

Distorted commented on 2017-01-11 08:25 (UTC)

@fifthecho My suspicions have been confirmed, and this is an issue with the infinality version of fontconfig that is outdated.

Distorted commented on 2017-01-10 16:54 (UTC)

@fifthecho I have the same issue, downgrading harfbuzz seems to fix it. But this issue is not related to the seafile client but to qt5 in general or a dependency of it.

fifthecho commented on 2017-01-10 15:48 (UTC)

I'm getting the following when (re-)installing seafile-client trying to update to the latest versions: [100%] Building CXX object CMakeFiles/seafile-applet.dir/qrc_QtAwesome.cpp.o [100%] Linking CXX executable seafile-applet /usr/lib/libharfbuzz.so.0: undefined reference to `FT_Get_Var_Blend_Coordinates' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/seafile-applet.dir/build.make:5303: seafile-applet] Error 1 make[1]: *** [CMakeFiles/Makefile2:997: CMakeFiles/seafile-applet.dir/all] Error 2 make: *** [Makefile:128: all] Error 2

a-bostaurus commented on 2017-01-08 19:57 (UTC)

Helpful was to deinstall ccnet ccnet-server seafile-client (and if existing other seafile-packages), then install seafile-client. The installation of ccnet and ccnet-server happens automatically. If you do not remove your seafile-directory in /home/user/, seafile is working immediatly after installing.

a-bostaurus commented on 2017-01-08 19:10 (UTC)

When trying to update I got a failure-message: "configure: error: Package requirements (libccnet >= 0.9.3) were not met: No package 'libccnet' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables CCNET_CFLAGS and CCNET_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ==> FEHLER: Ein Fehler geschah in build(). Breche ab... ==> FEHLER:Makepkg konnte seafile nicht erstellen." I updated ccnet some seconds before ... does the new ccnet not work together with seafile? (It is ccnet 6.0.2-1)

eolianoe commented on 2017-01-08 11:27 (UTC)

@Popkornium18: the seaf-cli binary is present in the seafile package

Popkornium18 commented on 2017-01-07 23:09 (UTC)

What happened to the 'seafile-client-cli' package? It doesn't exist anymore. Is the cli-client provided by another package?

eolianoe commented on 2017-01-07 18:54 (UTC)

@eduardosm: thanks I forgot this one

eduardosm commented on 2017-01-07 18:14 (UTC)

Please, add ccnet to dependencies, otherwise it won't run.

eolianoe commented on 2017-01-07 13:18 (UTC)

@micsnare: yes, you can try to reinstall Qt5

micsnare commented on 2017-01-07 12:51 (UTC)

@eolianoe: ok, how can i resolve this? because I run "sudo pacman -Syu" every day..... Do I need to uninstall Qt5 ?

eolianoe commented on 2016-12-28 12:24 (UTC)

@micsnare: It seems that your system is fully not up to date because CMake finds two different version of Qt5. I just checked in a clean chroot and there is no missing dependencies.

micsnare commented on 2016-12-26 20:39 (UTC)

I get this error: -- Found PkgConfig: /usr/sbin/pkg-config (found version "0.29.1") Build type: Release qt5 version: 5.7.0 CMake Error at /usr/lib64/cmake/Qt5WebEngineCore/Qt5WebEngineCoreConfig.cmake:97 (find_package): Could not find a configuration file for package "Qt5Quick" that is compatible with requested version "5.7.1". The following configuration files were considered but not accepted: /usr/lib64/cmake/Qt5Quick/Qt5QuickConfig.cmake, version: 5.7.0 Call Stack (most recent call first): /usr/lib64/cmake/Qt5/Qt5Config.cmake:26 (find_package) CMakeLists.txt:151 (FIND_PACKAGE) -- Configuring incomplete, errors occurred! See also "/tmp/yaourt-tmp-theresa/aur-seafile-client/src/build/CMakeFiles/CMakeOutput.log". Is there any dependency that I'm missing or any other reason why the seafile-client wouldn't install on my setup? :(

eolianoe commented on 2016-11-04 14:03 (UTC)

@oi_wtf: I cannot reproduce your error in a clean chroot. Could you send me the full compilation log?

oi_wtf commented on 2016-11-04 00:55 (UTC)

When building this in a headless environment, it complains about missing GL/gl.h include. So mesa should probably be a makedepend. FTR, error is: CMake Error at /usr/lib64/cmake/Qt5Gui/Qt5GuiConfigExtras.cmake:9 (message): Failed to find "GL/gl.h" in "/usr/include/libdrm". Call Stack (most recent call first): /usr/lib64/cmake/Qt5Gui/Qt5GuiConfig.cmake:158 (include) /usr/lib64/cmake/Qt5/Qt5Config.cmake:26 (find_package) CMakeLists.txt:151 (FIND_PACKAGE) -- Configuring incomplete, errors occurred!

alxndr13 commented on 2016-10-18 11:31 (UTC)

@MadMe: had the same issue. removing protobuf3 and installing protobuf2.6.1 resolved the issue.

MadMe commented on 2016-10-14 08:02 (UTC)

@eolianoe i tried but it didn't work... the output if i try to rebuild: [100%] Linking CXX executable seafile-applet /usr/bin/ld: warning: libprotobuf.so.9, needed by /usr/lib/libQt5WebEngineCore.so.5.7.0, not found (try using -rpath or -rpath-link) /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::LogMessage::operator<<(char const*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageLite::SerializeAsString[abi:cxx11]() const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormat::SerializeUnknownFields(google::protobuf::UnknownFieldSet const&, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageLite::ParseFromArray(void const*, int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteInt64(int, long, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageLite::SerializeToString(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::UnknownFieldSet::AddVarint(int, unsigned long)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteBytes(int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteBool(int, bool, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `vtable for google::protobuf::internal::FunctionClosure0' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormat::SkipField(google::protobuf::io::CodedInputStream*, unsigned int, google::protobuf::UnknownFieldSet*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageFactory::InternalRegisterGeneratedMessage(google::protobuf::Descriptor const*, google::protobuf::Message const*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::Message::CheckTypeAndMergeFrom(google::protobuf::MessageLite const&)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::VarintSize32Fallback(unsigned int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageLite::SerializeToArray(void*, int) const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::ReadString(google::protobuf::io::CodedInputStream*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::Skip(int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::LogMessage::LogMessage(google::protobuf::LogLevel, char const*, int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::ReadVarint64Fallback(unsigned long*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteUInt64(int, unsigned long, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteStringMaybeAliased(int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::StringTypeHandlerBase::New[abi:cxx11]()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::Message::GetTypeName[abi:cxx11]() const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::ReadTagFallback()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::Message::DiscardUnknownFields()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::VarintSize64(unsigned long)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::UnknownFieldSet::ClearFallback()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::LogMessage::~LogMessage()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::Message::InitializationErrorString[abi:cxx11]() const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::WriteStringWithSizeToArray(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned char*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::empty_string_[abi:cxx11]' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::Message::SpaceUsed() const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteInt32(int, int, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteSInt32(int, int, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::ReadVarint32Fallback(unsigned int*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormat::SerializeUnknownFieldsToArray(google::protobuf::UnknownFieldSet const&, unsigned char*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::UnknownFieldSet::MergeFrom(google::protobuf::UnknownFieldSet const&)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteFloat(int, float, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::RepeatedPtrFieldBase::Reserve(int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::PushLimit(int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteBytesMaybeAliased(int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::VerifyVersion(int, int, char const*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteDouble(int, double, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteUInt32(int, unsigned int, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::DescriptorPool::FindFileByName(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::StringTypeHandlerBase::Delete(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::GeneratedMessageReflection::GeneratedMessageReflection(google::protobuf::Descriptor const*, google::protobuf::Message const*, int const*, int, int, int, google::protobuf::DescriptorPool const*, google::protobuf::MessageFactory*, int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::FunctionClosure0::~FunctionClosure0()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::InitEmptyString()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageFactory::generated_factory()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::DescriptorPool::generated_pool()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::ReadLittleEndian64Fallback(unsigned long*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteMessageMaybeToArray(int, google::protobuf::MessageLite const&, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageFactory::InternalRegisterGeneratedFile(char const*, void (*)(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&))' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::BytesUntilLimit() const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::empty_string_once_init_' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::WriteVarint32(unsigned int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::ReflectionOps::Merge(google::protobuf::Message const&, google::protobuf::Message*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::UnknownFieldSet::UnknownFieldSet()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::Message::~Message()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteEnum(int, int, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::MessageLite::ParseFromString(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::LogFinisher::operator=(google::protobuf::internal::LogMessage&)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::WriteLittleEndian32(unsigned int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::OnShutdown(void (*)())' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::ReadBytes(google::protobuf::io::CodedInputStream*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::GoogleOnceInitImpl(long*, google::protobuf::Closure*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::DescriptorPool::InternalAddGeneratedFile(void const*, int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormat::ComputeUnknownFieldsSize(google::protobuf::UnknownFieldSet const&)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::WriteVarint64ToArray(unsigned long, unsigned char*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::PopLimit(int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::UnknownFieldSet::~UnknownFieldSet()' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::ReadRaw(void*, int)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::BytesUntilTotalBytesLimit() const' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedInputStream::ReadLittleEndian32Fallback(unsigned int*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::WriteVarint32FallbackToArray(unsigned int, unsigned char*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::internal::WireFormatLite::WriteString(int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, google::protobuf::io::CodedOutputStream*)' /usr/lib/libQt5WebEngineCore.so.5.7.0: undefined reference to `google::protobuf::io::CodedOutputStream::WriteVarint64(unsigned long)' collect2: Fehler: ld gab 1 als Ende-Status zurück make[2]: *** [CMakeFiles/seafile-applet.dir/build.make:5247: seafile-applet] Fehler 1 make[1]: *** [CMakeFiles/Makefile2:997: CMakeFiles/seafile-applet.dir/all] Fehler 2 make: *** [Makefile:128: all] Fehler 2 now i think the problem is not seafile-client itself I think qt5-WebEngine is the "bad Guy" But at the moment i dont have time for debugging... when i have more time then i will look in this problem...

eolianoe commented on 2016-10-10 07:49 (UTC)

@MadMe: You should rebuild the package in case of such problem

MadMe commented on 2016-10-08 19:42 (UTC)

After an update i just had a problem, the seafile client didn't start... in the console: seafile-applet: error while loading shared libraries: libprotobuf.so.9: cannot open shared object file: No such file or directory i didn' had much time so i just copied libprotobuf.so.9 libprotobuf.so.9.0.1 libprotobuf-lite.so.9 libprotobuf-lite.so.9.0.1 libprotoc.so.9 and libprotoc.so.9.0.1 to /usr/lib/ i don't think thats it is a good idea... but it works... be aware that this quick and dirty solution may have some disadvantages... The Problem seems to be somewhere around protobuf3, protobuf2.6 and qt5-webengine...

gnacho commented on 2016-09-20 20:55 (UTC)

@eolianoe Thanks for the help, I did already but same results. Weird thing is I got one of the laptops updated, not sure how. I know Apricity is not real Archlinux, but it's really easy to install and using the same repositories, shouldn't make a big difference. For non IT people like me is the only chance to use Arch :)

eolianoe commented on 2016-09-20 11:53 (UTC)

@gnacho: Try to reinstall everything but this may be linked to the fact that you are using Apricity and not a real Archlinux.

gnacho commented on 2016-09-19 21:39 (UTC)

@eolianoe They ARE installed, that's the funny thing. And working ok with 5.1.3. It happens with two laptop and 2 desktop computers. All of them HP and running Apricity OS... :(

eolianoe commented on 2016-09-16 07:43 (UTC)

@gnacho: I do not understand your problem, qt5-webengine and seafile-shared are needed to use this package, so you must install them.

gnacho commented on 2016-09-15 20:58 (UTC)

Version 5.1.4 gives me an error updating saying that needs qtwebengine dependencie and seafile. 5.1.3 works fine tho.

Dezponia commented on 2016-08-27 18:53 (UTC) (edited on 2016-08-30 19:29 (UTC) by Dezponia)

@Loris1123: I also have this problem on my GNOME3 laptop but not on my KDE desktop. Seems its because of this bug: https://github.com/haiwen/seafile-client/issues/809

Loris1123 commented on 2016-08-26 10:16 (UTC)

The size of my client is scaled twice the size. Everything looks very big and I cannot resize the window. Does anybody has the same problem? I'm using gnome as my desktop.

eolianoe commented on 2016-06-20 18:32 (UTC)

@Mechanix: Nice to hear that you fixed your errors, but please make your comments on the right package page.

Mechanix commented on 2016-06-20 18:20 (UTC)

Managed to fix this by removing libmysqlclient and installing libmariadbclient

Mechanix commented on 2016-06-20 17:18 (UTC) (edited on 2016-06-20 17:26 (UTC) by Mechanix)

Hi, I cannot build ccnet, it throws following error: . . . /usr/bin/ld: warning: libmysqlclient.so.18, needed by /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so, not found (try using -rpath or -rpath-link) /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_stmt_execute@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_stmt_bind_result@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_close@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_stmt_error@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_stmt_reset@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_stmt_param_count@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_stmt_close@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_query@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_free_result@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_stmt_bind_param@libmysqlclient_18' /usr/lib/gcc/x86_64-pc-linux-gnu/6.1.1/../../../../lib/libzdb.so: undefined reference to `mysql_fetch_field_direct@libmysqlclient_18' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:533: ccnet-server] Error 1 Any hints to get this working? Thank you

agrajag commented on 2016-06-17 09:06 (UTC) (edited on 2016-06-17 09:51 (UTC) by agrajag)

SOLVED: This was related to me setting XDG_CURRENT_DESKTOP=kde. This was intended to fix missing icons in Dolphin! I am getting a seg fault from the seafile-applet since the last update. Any ideas on how to debug it? I've already recompiled the whole package. GDB Output (gdb) run Starting program: /usr/bin/seafile-applet [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1". [New Thread 0x7fffe05e6700 (LWP 12142)] [New Thread 0x7fffd1605700 (LWP 12143)] [New Thread 0x7fffcb9e3700 (LWP 12159)] [New Thread 0x7fffcab54700 (LWP 12160)] [New Thread 0x7fffca353700 (LWP 12161)] [Thread 0x7fffca353700 (LWP 12161) exited] Thread 1 "seafile-applet" received signal SIGSEGV, Segmentation fault. 0x00007fffefc63d14 in QString::multiArg(int, QString const**) const () from /usr/lib/libQt5Core.so.5

muon commented on 2016-06-14 15:00 (UTC)

@eolianoe: Thanks for the suggestions. Rebooting didn't help, but a recompile/kill/restart of the package seems to have fixed it.

eolianoe commented on 2016-06-14 08:52 (UTC)

@muon: I can right-click on the icon and inside the interface. Did you try to recompile and restart (and even reboot)?

muon commented on 2016-06-14 03:06 (UTC)

I'm not sure exactly when this changed, but I can no longer right-click to get a context menu within the interface (e.g. to check info about a library). Just me? I didn't find an upstream issue, but if others see the same behavior and we don't think it's specific to this build, I can file one.

eolianoe commented on 2016-05-08 20:24 (UTC) (edited on 2016-05-08 20:25 (UTC) by eolianoe)

@PsiTrax: please read carefully the dependency list. This package only depends on 'seafile-shared' which is part of the split package 'seafile-server'. This split package builds 'seafile-shared', 'seafile-client-cli' and 'seafile-server' but you have to install only 'seafile-shared' to get 'seafile-client' working.

PsiTrax commented on 2016-05-08 20:17 (UTC)

Still pulling the server ??? ;(

lins05 commented on 2016-04-05 09:08 (UTC) (edited on 2016-04-05 09:08 (UTC) by lins05)

Hi, I'm Shuai Lin from the seafile team. I'm here to notify the maintainer of this AUR that we're going to remove Qt 4 support in seafile-client soon (most likely before we release seafile client 5.1.0) since it has become a maintenance burden of the code base.

tuxayo commented on 2016-03-19 15:03 (UTC)

Is there something that prevents updating the client to 5.0.6?

muon commented on 2016-02-09 19:47 (UTC)

For what it's worth, the upgrade worked fine for me by simply * removing older versions of seafile-client and seafile-shared * building/upgrading ccnet (to 5.0.5-1) * building/upgrading seafile-shared from the split package (to 5.0.5-1) * building/upgrading this package (to 5.0.4-1). Now, all seems to be running fine.

a-bostaurus commented on 2016-02-06 14:29 (UTC)

I got four arch-computer with seafile, and in the meantime no one is working relating to seafile. What I get are informations that there is an error ... It is more than annoying ...

rami commented on 2016-01-31 12:58 (UTC)

To me, it worked after I installed current seafile-shared manually. The dependency statement seafile-shared>=4.3.0 seems to be wrong.

nicolauz commented on 2016-01-15 12:25 (UTC)

The whole aur package is broken/annoying! Not that I can't fix the issue .. it's that there is an issue. A simple yaour -Suya should update all my aur packages .. it does, except seafile because either the dep on ccnet is "=" (instead of >=), or because seafile-[shared|server]'s pkg-split is broken

Popkornium18 commented on 2016-01-14 12:15 (UTC)

How can I upgrade the seafile-client package without reinstalling it. When I try to upgrade it it fails, because seafile-shared needs ccnet-5.0.3.

mjianr commented on 2016-01-07 20:25 (UTC)

Seems like there's a big misunderstood here about "seafile-shared" package. As it's made with split-pkgbuild, it outputs client-cli, server and shared packages (so that you won't compile all, 2 hours each on raspberry pi). AUR helpers like yaourt may try to install all of them, so, if someone struggling, make seafile-shared first and install needed packages with pacman -U manually or either use appropriate arguments (NOT --noconfirm!). I hope I made this clearer.

Popkornium18 commented on 2016-01-07 19:35 (UTC) (edited on 2016-01-07 19:37 (UTC) by Popkornium18)

The installation process of the Seafile client STILL pulls the Seafile server and the Seafile CLI client as a dependency... Why? This is so pointless... Could you PLEASE tell us if this is intentional, and if so, why it is necessery? If it is not intended please fix it. It's kind of annoying.

snack commented on 2015-12-21 11:44 (UTC)

It seems that the sync issue with new libraries can be bypassed by moving all the files in a temporary folder and then moving them back to the original folder. Seafile detects new files in the library folder and the synchronizes them correctly.

snack commented on 2015-12-15 15:36 (UTC)

Is anyone using the client with an old server (the one at my institute is 2.1.4) and experiencing no sync for new libraries? If I create a new library to sync a local folder already containing some files then no sync is performed: no file is uploaded to the server. The seafile.log file shows: [12/15/15 16:35:22] sync-mgr.c(660): Repo 'Documents' sync state transition from 'synchronized' to 'committing'. [12/15/15 16:35:23] sync-mgr.c(660): Repo 'Documents' sync state transition from 'committing' to 'initializing'. But if I add a new file to the local folder or touch one of the existing ones then that file is synced and uploaded.

snack commented on 2015-12-14 08:56 (UTC)

Compiling with Qt5 support as suggested by edacval partially fixes the problem. xembedsniproxy does not crash anymore and the Saefile icon is not displayed in the system tray but rather in the Status & Notifications panel, which is fine for me. The only problem is that the application window cannot be restored by clicking on the Seafile icon, and also the right click does nothing.

edacval commented on 2015-12-13 13:30 (UTC)

You can try to rebuild with QT5: change PKGBUILD 19 line to "cmake -DUSE_QT5=on -DBUILD_SHIBBOLETH_SUPPORT=ON -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr ."

eolianoe commented on 2015-12-13 12:54 (UTC)

Does a switch to Qt5 may change something to the problem? By the way the change to Qt5 can be a good thing as Qt4 will reach its end of life

xarinatan commented on 2015-12-13 00:35 (UTC)

Seeing the same issue as @Snack on a completely fresh setup (KDE 5.5), not sure what to do to resolve the issue though.

snack commented on 2015-12-11 11:01 (UTC)

Since the update to Plasma 5.5 the tray icon is disappeared. I have been able to track down the issue being seafile-applet making xembedsniproxy crash, as reported here: https://bbs.archlinux.org/viewtopic.php?pid=1585237#p1585237 Is anyone having a similar issue?

fsf commented on 2015-12-08 14:54 (UTC)

Thank you very much!

edacval commented on 2015-11-10 13:27 (UTC)

Done.

fsf commented on 2015-11-06 12:01 (UTC) (edited on 2015-11-06 12:03 (UTC) by fsf)

Please Add -DBUILD_SHIBBOLETH_SUPPORT=ON to the build options and change md5sum to SHA256sum, thx

hopimet commented on 2015-11-04 21:41 (UTC)

Thank you for updating this package. It works fine.

simontunnat commented on 2015-10-29 16:23 (UTC)

Could someone please take over the seafile packages as maintainer. I just can't find the time to maintain them.

Dezponia commented on 2015-10-01 16:11 (UTC)

Thanks for updating the package and taking on the maintainer role. So far the new client seems to work fine on my systems, syncing up and down without issues. In the case you don't want to maintain the client and its dependencies I'm willing to take it on. Client 4.4.0 is clearly marked as Beta on https://www.seafile.com/en/download/ Server 4.4.1 is also clearly marked as Beta. A good test here to see which is the latest stable is that the Seafile client will not show the "New stable version x.x.x is out" window unless its a new stable. That's why 4.3.4 is not asking to upgrade to 4.4.0 right now, 4.4.0 not considered stable by upstream. More info about how Seafile handles stable versions can be found here: https://seacloud.cc/group/3/wiki/client-changelog/ Specifically: "For desktop clients, we maintain two versions, one stable version and one master version. Master version will come with major modifications that may cause syncing issues." Master is not recommended for regular users but should be considered testing. And since Seafile handles peoples data I think its better to be careful (the 4.3.0-4.3.3 sync disaster shows this). Lastly I would also like to chime in and support the switch to use SHA256 over MD5.

fsf commented on 2015-10-01 15:20 (UTC)

4.4 is out on all clients as stable, server still beta: Seafile Client for Linux Runs on Ubuntu 12.04 or above 4.3.4 64bit 4.3.4 32bit 4.4.0 64bit 4.4.0 32bit And please use sha256sum and NOT md5, thx

cybertron commented on 2015-10-01 13:15 (UTC)

still not work for me, so can't download anything

simontunnat commented on 2015-10-01 12:26 (UTC)

If someone else wanted to take care of the packages im happily willing to give up my ownership. I just saw that there was no maintainer at the time.

simontunnat commented on 2015-10-01 12:24 (UTC)

Version 4.3.4 seems to be the last stable version. On the official homepage there is no 4.4 client and the server version 4.4 is marked as "beta". (https://www.seafile.com/en/download/)

fsf commented on 2015-10-01 09:50 (UTC)

i wanted to commit 4.4 but, now theres just apeared another maintainer... So, @simontunnat - would you mind to bump the version to 4.4 ?

commented on 2015-09-29 12:49 (UTC)

I am unwilling to wait any longer, so the package is now orphaned. I advise anyone willing to pick this up to pick up the whole seafile dependency tree, as it would otherwise become tedious to maintain.

Dezponia commented on 2015-09-26 22:47 (UTC)

Status update on new maintainer?

nebulon commented on 2015-09-16 08:30 (UTC)

Any updates on the ownership change? Thanks.

cybertron commented on 2015-09-05 20:19 (UTC)

Thanks a lot!

commented on 2015-09-05 15:38 (UTC)

This is the last upstream-based package update from me. Since I have received mail from one from person interested in maintaining, I will not orphan the packages just yet, but in the next couple of days.

cybertron commented on 2015-09-04 06:34 (UTC)

it's gettin older and older :/

Xaap commented on 2015-08-21 17:43 (UTC)

My synchronisation issue was related to SSL cert and seafile silently falling back to its own protocol on previous server versions. All works for me now.

taggaara commented on 2015-08-19 13:26 (UTC)

@a-bostaurus Please check my commet @ 2015-08-11 06:00, you can search it in this page.

a-bostaurus commented on 2015-08-19 11:06 (UTC)

After the last update to version 4.3.1-1 there are some problems with syncing. If you have worked with a file and saved it the seafile client says: Uploading is not possible or did not work. (Hochladen der Datei fehlgeschlagen). I tested it on 4 Computers with Arch Linux und found everywhere the same problem. Downgrading could help but I am not able to do this.

Dezponia commented on 2015-08-19 10:42 (UTC)

@maxi_jac 4.3.2 just got released which fixes even more syncing issues with the 4.3.x branch. Perhaps you've run into one of these issues?

taggaara commented on 2015-08-15 04:17 (UTC)

@calrama You have maintained this pkg for more than 2years. Really Thanks! I've never heard Funtoo before because I moved my working environment from Windows to Archlinux only 1 year ago. There are lots of things I need to learn in Linux. Since I don't have enough knowledge to maintain this package, I fell so sorry.

Xaap commented on 2015-08-14 16:18 (UTC)

Thanks calrama. At least, now the window/systray works. But I still have problems with synchronisation. I'll investigate.

commented on 2015-08-13 13:18 (UTC)

@Dezponia Cool, unfortunately my last Archlinux box is headless, so the maximum testing for this I can still do is build verification. @taggaara Should work with the update to 4.3.1 and the downgrade to QT4. Also, since I may not have stressed this enough, I WILL drop all my AUR packages sometime after 2015-08-31, maybe as early as 2015-09-01. <OT> I have been moving away from Archlinux to Funtoo for quite a while now and except for one box used to keep maintaining here, I no longer have any Archlinux boxes. I am glad that Archlinux existed when I moved away from Ubuntu in '09, as it allowed me to sharpen my Linux-fu so to speak, but I do not agree with several of the decisions regarding Archlinux' future made by its core developers - including, but not limited to the adoption of systemd - and it was/is time for me to move to something that satisfies my requirements and I simply do not have the time (and quite frankly the motivation) to keep maintaining something that I have no use for (which I btw have been doing for about half a year now as thanks for what Archlinux has enabled me to do in the past).</OT>

commented on 2015-08-13 13:16 (UTC)

@Dezponia Cool, unfortunately my last Archlinux box is headless, so the maximum testing for this I can still do is build verification. @taggaara Should work with the update to 4.3.1 and the downgrade to QT4. Also, since I may not have stressed this enough, I WILL drop all my AUR packages sometime after 2015-08-31, maybe as early as 2015-09-01. <OT> I have been moving away from Archlinux to Funtoo for quite a while now and except for one box used to keep maintaining here, I no longer have any Archlinux boxes. I am glad that Archlinux existed when I moved away from Ubuntu in '09, as it allowed me to sharpen my Linux-fu so to speak, but I do not agree with several of the decisions regarding Archlinux' future made by its core developers - including, but not limited to the adoption of systemd - and it was/is time for me to move to something that satisfies my requirements and I simply do not have the time quite frankly the motivation to keep maintaining something that I have no use for (which I btw have been doing for about half a year now as thanks for what Archlinux has enabled me to do in the past).</OT>

Dezponia commented on 2015-08-13 13:02 (UTC)

Thanks for the update to version 4.3.1. I can confirm the system menu tray now works as intended again on Qt4. As I have not experienced any sync bugs myself (I did not trigger the "empty folder" bug) someone else will have to verify that part is solved.

Dezponia commented on 2015-08-12 08:37 (UTC)

The sync bug is probably related to version 4.3.0, it was fixed in 4.3.1 that just got released. The system tray menu bug is likely a problem with the Qt5 branch from what I've found. If the maintainer could do two set of builds, one with Qt4 and one with Qt5 and test that would be nice. For the moment most users probably want a fully working Qt4 client over a sort-of working Qt5 one.

Xaap commented on 2015-08-11 15:42 (UTC)

@taggaara Thx, we need now to know if this is KDE/Plasma related or not. Does someone have it working and with what DE if you do ? And/or need to know if it is a packaging issue. Not much time to investigate this right now :/

taggaara commented on 2015-08-11 06:07 (UTC)

And if @calrama give up maintain of this package, maybe I will stay v4.1.6 for long time...

taggaara commented on 2015-08-11 06:00 (UTC)

Hei~ maxi_jac, I updated to 4.3.0-1 either, and my plasma systray cann't show right click menu, when I re-run the seafile-applet the seafile client GUI show but it cannot sync anything. I downgrade all pkg to 4.2.4 with AUR pkg: "seafile-client seafile-shared seafile-client-cli ccnet", but still the same thing. In the end I have to downgrade, back to 4.1.6 which version I used with no problem . I have to get PKGBUILD file from AUR GIT History Mirror: http://pkgbuild.com/git/aur-mirror.git/ http://pkgbuild.com/git/aur-mirror.git/log/seafile-client http://pkgbuild.com/git/aur-mirror.git/log/seafile-client-cli http://pkgbuild.com/git/aur-mirror.git/log/seafile-shared http://pkgbuild.com/git/aur-mirror.git/log/ccnet # I download this whole commit history file(122MB), because I cannot find the indepence package with every seafile pkg. http://pkgbuild.com/git/aur-mirror.git/snapshot/aur-mirror-087de4535ed8d4fd3e08deac214b3ffb6b7d0607.tar.xz

Xaap commented on 2015-08-08 12:19 (UTC)

Do you guys still have a working systray icon ? Using KDE/Plasma I used to have it working but now, I can see it registered in my plasma systray when developing it, but I cannot interact with it, no left/right click does a thing. In console output it does not give any error and says it successfully registered to KStatusNotifierWatcher. I do have sni-qt. Any idea ?

commented on 2015-08-07 19:02 (UTC)

Since I no longer intend to use distributions with systemd for personal use, I will abandon this package no earlier than 2015-09-01. Should someone be interested in maintaining this package afterwards, he or she can contact me in the interim to become co-maintainer and then sole maintainer once I leave, to ensure a smooth transition. If possible, I would like to hand over the following packages over to a single maintainer, since they comprise a dependency graph: libevhtp-seafile, libsearpc, ccnet, seafile-shared, seafile-client, seafile-client-cli, seafile-server

tes5884 commented on 2015-08-05 21:25 (UTC)

Version 4.3 was released

commented on 2015-06-12 09:34 (UTC)

Initial AUR4 import at seafile version 4.2.4.

cirk2 commented on 2015-06-05 10:21 (UTC)

@guiguid: you also need qt5-tools, else the cmake fails to find Qt5LinguistTools

guiguid commented on 2015-05-27 19:46 (UTC)

for build with QT5 : -depends=('seafile-shared>=4.1.6' 'qt4' 'qtwebkit') +depends=('seafile-shared>=4.1.6' 'qt5-base' 'qt5-webkit') -cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr . +cmake -DUSE_QT5=on -DCMAKE_BUILD_TYPE=Release -DCMAKE_INSTALL_PREFIX=/usr .

jcelerier commented on 2015-04-12 14:21 (UTC)

Would it be possible to switch from Qt4 to Qt5 ?

timsn commented on 2015-03-27 07:22 (UTC)

4.1.3 was released 4.1.3 (2015/03/23) [fix] Fix unable to sync bug (permission denial) if the Windows system user name contains space like "test 123" introduced in v4.1.2 [win] Update version of OpenSSL to 1.0.2a 4.1.2 (2015/03/19) (deprecated) Add logout/login support (need server 4.1.0+) fix proxy password disappearance after restarting issue mask proxy password in the setting dialog [Fix] fix unexpected disconnection with proxy servers [Fix] fix a conflicting case when we have read-only sharing repository to a group update translations support darkmode (OS X) and other minor fixes

chilledheart commented on 2015-03-04 16:31 (UTC)

Hi all, From version 4.1.0, it seems seafile-client have add support for qt5. I think you can enable this by pass -DUSE_QT5=on to cmake. And if you have a hidpi screen (or more than one), you can try something like setting environment variable QT_DEVICE_PIXEL_RATIO=auto (or 2) before starting seafile-client. Feel free to email me if you have any issues with it.

arnieswap commented on 2015-01-22 22:24 (UTC)

==> Building and installing package ==> ERROR: options array contains unknown option '' ==> ERROR: Makepkg was unable to build libsearpc. ==> Restart building libsearpc ? [y/N]

Chocobozzz commented on 2015-01-22 12:27 (UTC)

Seafile-client 4.0.7 released :)

commented on 2014-12-26 19:50 (UTC)

@blubbblubb: 1) The package had already been flagged out-of-date 2) The checksums are generated semi-automatically by invoking updpkgsums (which downloads all necessary sources and updates the relevant checksum lines in the PKGBUILD, provided they are at the end of the file), which belongs to pacman and can thus be assumed to be always installed.

blubbblubb commented on 2014-12-26 18:54 (UTC)

4.0.5 released change package version to 4.0.5 and use this sha sum: b2ab5251450b33a3a425d9a8a4fa17a17e7cad33691339784f0861416bd48186

commented on 2014-12-03 12:54 (UTC)

@monochromec: See my reply at the URL you linked from 2014-12-03 12:48.

monochromec commented on 2014-12-03 07:43 (UTC)

Noticed an SIGILL issue on an armv7h on both the server and client side. Comment on the server page contains a workaround (https://aur.archlinux.org/packages/seafile-server).

Rook commented on 2014-12-01 16:14 (UTC)

4.0.2 has been released (2014/11/29) : [fix] Fix bugs in syncing with HTTP protocol

issue commented on 2014-11-18 17:26 (UTC)

4.0.1 was just released, fixes the previous segfault aswell

shimi commented on 2014-11-18 15:40 (UTC)

@Perry3D that works, thanks.

Perry3D commented on 2014-11-18 14:11 (UTC)

@shimi: I got the same error. After recompiling seafile-shared and seafile-client it works.

shimi commented on 2014-11-17 17:28 (UTC)

I'm getting this error when trying to run the applet, any ideas? (seafile-applet:9929): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed fish: Job 1, “seafile-applet ” terminated by signal SIGSEGV (Address boundary error)

commented on 2014-11-12 16:13 (UTC)

@gnumdk: It was properly released as stable: https://github.com/haiwen/seafile-client/tags By the upstream developers' own convention, stable released have no additional suffix and beta released have the "-testing" suffix. While one upstream developer did afterwards say that 4.0 is still in beta, they have not yet removed the stable tag for it, so upstream (as a whole) has two contradictory statements (if it truly is purely a beta release, they should have renamed the stable tag after noticing the wrong naming - even if this introduces a temporary hassle for people who already pulled the changes). The statement I chose to follow is the release of a properly versioned, stable tarball by their own convention.

commented on 2014-11-12 16:12 (UTC)

@gnumdk: It was properly released as stable: https://github.com/haiwen/seafile-client/tags By the upstream developer's own convention, stable released have no additional suffix and beta released have the "-testing" suffix. While one upstream developer did afterwards say that 4.0 is still in beta, they have not yet removed the stable tag for it, so upstream (as a whole) has two contradictory statements (if it truly is purely a beta release, they should have renamed the stable tag after noticing the wrong naming - even if this introduces a temporary hassle for people who already pulled the changes). The statement I chose to follow is the release of a properly versioned, stable tarball by their own convention.

gnumdk commented on 2014-11-12 14:51 (UTC)

Seafile 4 is a beta version!

commented on 2014-10-31 00:09 (UTC)

@alinmear: If the package has been flagged out of date, then I have been notified of it. If the package remains flagged (that is, I don't unflag it because of an invalid flagging) I will update it when I have the necessary time to test it. Please wait with reminders about it until the end of the following weekend, since it is quite possible that I cannot make the necessary time on the weekdays. I have now - as an exception - updated the packages without testing them to accomodate you this time.

alinmear commented on 2014-10-30 12:23 (UTC)

@calrama. Please update the pkgver=3.1.8! we also need to update the seafile-shared! i uploaded the updated PKGBUILDs as GIST: https://gist.github.com/anonymous/50a36bbdfec30cc83c13

commented on 2014-10-04 10:07 (UTC)

@jpambrun: The perspective to be used here is a source-based (not binary based !) non-beta build script for a FLOSS (or at least a seemingly so) development project (seafile client), in which stable releases have been marked by providing source archive files for long enough for that to have become the de facto standard (both in FLOSS generally and in seafile specifically). Marking this package as out-of-date - if there is no stable release archive newer than the currently used one - is incorrect, since it cannot be updated without such an archive without becomimg broken. With that being said, the devs from seafile "forget" to do this on a regular basis - on average every third release or so (estimation based on memory) - and when reminded it can appear anywhere between a couple of minutes to a couple of weeks later, but with no shown intention of fixing their imho problematic release procedure. You might want to create a github issue there about the missing tag if you wish, or alternatively create a seafile-client-beta package and use their testing tags (which are pretty much always there the way you expect). For references to my claims you can look hat this packages comment history. It will support the pattern.

jpambrun commented on 2014-10-04 01:26 (UTC)

@calrama: "incorrectly" is a question of perspective; the release was announced on their twitter account on sept 27 and binaries are available for all platforms on their web site since then. They obviously just forgot to create another git tag.

commented on 2014-10-03 21:24 (UTC)

@jpambrun: There is no issue that I know of with the "Flag as out-of-date" action, you flagged it out of date incorrectly, so I unflagged it. As of my writing this, the latest stable tag is v3.1.6: https://github.com/haiwen/seafile-client/tags

jpambrun commented on 2014-10-03 14:26 (UTC)

There seems to be an issue with the "Flag as out-of-date" action so I'm writing this comment. I have sync issue and I hope this update will fix my problems. 3.1.7 (2014/09/28) - [fix] Fix another not sync problem when adding a big file (>100M) and several other files.

Chocobozzz commented on 2014-08-18 12:46 (UTC)

Oh, sorry the same than jbgi. But I don't undestand why they don't precise it's testing here http://www.seafile.com/en/download/ Anyway, thanks for your work and your rapidity calrama.

jbgi commented on 2014-08-14 11:54 (UTC)

sorry false "out-of-date" flagging. only "v3.1.5-testing" was really released.

simontunnat commented on 2014-08-11 15:15 (UTC)

I agree with malachay. Had the same problem and it worked after I added "qtwebkit" to the dependencies.

malachay commented on 2014-08-07 19:58 (UTC)

Hi calrama, I have a fresh arch install on my laptop with nearly nothing installed. While installing seafile-client I got this error: CMake Error at /usr/share/cmake-3.0/Modules/FindPackageHandleStandardArgs.cmake:136 (message): Could NOT find Qt4 (missing: QT_QTWEBKIT_INCLUDE_DIR QT_QTWEBKIT_LIBRARY) (found version "4.8.6") After installing qtwebkit, the client was built. You shoul add qtwebkit to the dependencies :) Regards, malachay

commented on 2014-07-16 10:04 (UTC)

Dear Ondřej, thank you for informing me about this issue. As you said, in the AUR we are technically only distributing "Descriptions on how to build Seafile", not Seafile itself, so as far as I understand the GPL, we're fine. Should someone, however, contact me about merging any of these packages into the main repositories (which would imply distribution of automatically built binaries), I shall point them to this problem (should it not be fixed by then). One question, though, as I'm not really clear on that point: The GPL violations seem to be in the seafile repository, do they also automatically propagate to anything that includes them (like the seafile-client repository)? I ask because you posted this here and not at one of the other seafile-* packages. Cheers, Moritz

oerdnj commented on 2014-07-14 08:34 (UTC)

Dear maintainer, the seafile is violation GPL[1] and the resulting work cannot be legally distributed. I am not sure if that also applies to ArchLinux since you are not distributing binary packages, but you should be at least aware of the issue. Cheers, Ondrej 1. https://github.com/haiwen/seafile/issues/666

cedricziel commented on 2014-04-27 08:37 (UTC)

The sha256 sum differs from the archive.

allspark commented on 2014-03-15 01:26 (UTC)

yes, tested it with -j 9

commented on 2014-03-14 23:34 (UTC)

Have you explicitly tested it with more jobs, otherwise that could simply be because makepkg.conf has one job by default?

allspark commented on 2014-03-14 22:13 (UTC)

please remove the '-j1'. it builds fine without

commented on 2014-01-20 23:16 (UTC)

pacman -Qo /usr/share/applications/seafile.desktop /usr/share/applications/seafile.desktop is owned by seafile-shared 2.1.1-4 The .desktop file resides in the "seafile" repo, not in the "seafile-client" repo, so it goes into seafile-shared ATM, but it is there (since seafile-client depends on seafile-shared).

haagch commented on 2014-01-20 22:51 (UTC)

Works fine, but a .desktop file in /usr/share/apps would be helpful for having it in the menus.

commented on 2014-01-14 12:27 (UTC)

Before unflagging this, please wait for a response to this: https://github.com/haiwen/seafile/issues/406#issuecomment-32260305

commented on 2013-11-09 09:58 (UTC)

Because of a serious bug in the client, I was asked not to provide version 2.0.7 here[1]. For the time being I'll thus use 2.0.6 here. [1] https://github.com/haiwen/seafile/issues/406#issuecomment-28117454

commented on 2013-11-05 21:31 (UTC)

The cli client resides in the "seafile" repository and is not part of the new client, which is why it doesn't belong here anymore. There's now a seperate package for it called "seafile-client-cli"; give it a try and please report any problems you find (don't have enough time right now to do an in-depth test).

commented on 2013-11-05 20:56 (UTC)

The cli client resides in the "seafile" repository and is not part of the new client. I'll upload a seperate package for it in a bit.

monksy commented on 2013-11-05 20:22 (UTC)

What happened to the seaf-cli client? All I see is the seafile-daemon and the applet. I can't use the applet with a headless box.

kevincox commented on 2013-11-04 21:34 (UTC)

Sorry, I don't know how I managed it but the order in which I built them allowed the new seafile-client to build but couldn't link. Rebuilding seafile-shared then seafile-client fixed it. Cheers.

kevincox commented on 2013-11-04 21:26 (UTC)

That's good to have the new Qt applet (the web one kinda sucked TBH) however I get the following error when starting seafile-applet. $ seafile-applet seafile-applet: error while loading shared libraries: libseafile.so.0: cannot open shared object file: No such file or directory

commented on 2013-10-30 20:38 (UTC)

This package has now been changed to use the new Qt-based seafile-client, as the old one is going to be dropped soon (see the discussion on this issue: https://github.com/haiwen/seafile/issues/406). However, the new client in the seafile-client repository depends on some of the shared core components of seafile, which were previously part of this package; these have been moved out to the seafile-shared package, as they aren't really part of the actual client.

commented on 2013-08-20 09:31 (UTC)

Thanks for the info, you might simply want to flag out-of-date next time (I've done it this time), though, as that produces less comments (which people have to look through if for some reason the package doesn't work for them). Once ccnet is updated to use 1.8.0 I'll update this.

commented on 2013-08-20 09:30 (UTC)

Thanks for the info, you might simply want to flag out-of-date next time, though, as that produces less comments (which people have to look through if for some reason the package doesn't work for them). Once ccnet is updated to use 1.8.0 I'll update this.

commented on 2013-08-20 04:39 (UTC)

Version 1.8.0 is out. I've updated the PKGBUILD here: http://pastebin.com/7x67pFQj I stripped out the sha sums out of pure laziness, sorry about that.

commented on 2013-08-04 12:06 (UTC)

> Why don't you use the source-releases from https://github.com/haiwen/seafile/releases > They provide a "zip" Download-Link for each tagged release. (1) Because the ccnet package doesn't do it and seafile-client depends on it (2) Because haiwen's tagging is arbitrary and not done in the usual clear way (i.e. only the version number, no extras). > The current package builds, but the web-interface of seafile has a python-error when you click any link in it: I cannot reproduce that error on any of my machines (x86_64 VirtualBox VM, x86_64 Native, i686 Native). The package builds on all of them and I can use all settings / click all links in the web-interface of seafile-client, as well as download / synchronize my libraries with my private server running the seafile server (from the AUR package seafile). Sorry, but I don't know how to help you here.

commented on 2013-08-04 10:01 (UTC)

(sorry for the many edits, i thought it would work now, but it doesn't) The current package builds, but the web-interface of seafile has a python-error when you click any link in it: Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/web/wsgiserver/__init__.py", line 1245, in communicate req.respond() [...] File "/usr/lib/python2.7/site-packages/web/httpserver.py", line 319, in log print >> outfile, utils.safestr(msg) IOError: [Errno 5] Input/output error

commented on 2013-08-04 09:53 (UTC)

Why don't you use the source-releases from https://github.com/haiwen/seafile/releases They provide a "zip" Download-Link for each tagged release.

commented on 2013-07-08 12:42 (UTC)

Until now, I've written emails, but I'll write it here once for reference: 1) Seafile gets (at the moment) released here: https://code.google.com/p/seafile/downloads/list 2) Binaries for Seafile are currently released before source tarballs 3) There's no point in flagging seafile-client out-of-date *until* these source tarballs become available, even if new binaries have been released because without the source tarballs, this package cannot be built. Example: At the moment of me writing this comment the latest released source tarball is version 1.7.1 (as is this package), while the latest released binaries are 1.7.3 (they were released two days prior). I cannot update seafile-client to 1.7.3 until i) the source tarball for 1.7.3 gets released (which usually takes a couple of days) ii) the ccnet package gets updated, as usually both get changes that make compiling the client without the exact proper ccnet version not possible. It is sensbile to flag seafile-client out of date as soon as you notice i) and I'll push the new PKGBUILD when notice ii) (and have the time)

commented on 2013-06-24 12:24 (UTC)

Thanks for flagging out of date, but please don't flag out of date AND comment about it unless the comment has important info, as it sends two mails about the same issue with the same amount of information in them.

commented on 2013-06-24 12:17 (UTC)

Thanks for flagging out of date, but please don't flag out of date AND comment about it unless the comment has important info, as it sends two mails about the same issue with the same amount of information in them.

oliver_aur commented on 2013-06-22 12:58 (UTC)

thanks. Looks good now

commented on 2013-06-21 22:32 (UTC)

Technically, that shouldn't happen, because the python binary gets explicitly set to python2 when configuring (see the ./configure line in the PKGBUILD), so I'd say that this is a bug in upstream; I've included a patch to take care of that for now.

oliver_aur commented on 2013-06-21 22:14 (UTC)

The first line of /usr/bin/seaf-cli needs to be updated in order to successfully run The generic installed version (#!/usr/bin/env python) gives me the following: $ seaf-cli status File "/sbin/seaf-cli", line 105 print "%s not found in PATH. Have you installed seafile?" % prog ^ SyntaxError: invalid syntax If I modify it to be #!/usr/bin/env python2 it works $ seaf-cli status # Name Status Progress # Name Status conf_files synchronized Is there some fancy way I'm missing that enables the correct version of python to be selected without modifying the packaged file?

commented on 2013-03-07 11:33 (UTC)

I will (as in can only when) update this when ccnet has been updated.

commented on 2013-02-27 16:38 (UTC)

Hm, you're right, though I don't know why I had intltool installed (and thus not notice this). I never installed it explicitly and there was no package installed that depends on it... Anyway, it's in the dependencies now, thank you.

xeross commented on 2013-02-27 14:15 (UTC)

./configure: line 13399: intltool-update: command not found checking for intltool >= 0.35.0... found configure: error: Your intltool is too old. You need intltool 0.35.0 or later. ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build . Needs a builddep on extra/intltool?

commented on 2013-02-26 13:34 (UTC)

Sorry about that, it was in the dependencies before, I must've accidentally deleted it when adopting it to build from source. It's done now.

mbunkus commented on 2013-02-26 13:30 (UTC)

Another issue occurs when I want to start seafile-applet: Load config from /home/mosu/.ccnet Traceback (most recent call last): File "main.py", line 75, in <module> default_filters=['decode.utf8']) File "/usr/lib/python2.7/site-packages/web/contrib/template.py", line 107, in __init__ from mako.lookup import TemplateLookup ImportError: No module named mako.lookup Installing "python2-mako" helps, so please add it to the dependencies.

commented on 2013-02-26 12:36 (UTC)

No problem. Anyway, I'd suggest putting this flag into your /etc/makepkg.conf (https://www.archlinux.org/pacman/makepkg.conf.5.html). This way it will get used by makepkg automatically *unless* the make call in the PKGBUILD specifically states -j1, to which I've now just updated this packages PKGBUILD. In essence: (1) Move -j3 to /etc/makepkg.conf into the line "#MAKEFLAGS=" and uncomment it. (2) Try building with the package release I just uploaded

mbunkus commented on 2013-02-26 12:26 (UTC)

Yes, I do. I have "export MAKEFLAGS="-j 3"" in my shell startup files. I've temporarily removed it and re-built seafile-client. It works now. Thanks for the fast response.

commented on 2013-02-26 12:24 (UTC)

The same error occurs on ccnet when building with more than one job, so do you use more than one job? If so, try changing make to make -j1 in the PKGBUILD.

commented on 2013-02-26 12:23 (UTC)

The same error occurs on ccnet when building with more than one job, so do you use more than one job?

commented on 2013-02-26 12:22 (UTC)

The same error occurs on ccnet when building with more than one job, so do you use more than one job?

mbunkus commented on 2013-02-26 12:21 (UTC)

And sorry for flagging out of date, I confused client with server version numbers. Still, the error does happen.

mbunkus commented on 2013-02-26 12:18 (UTC)

This package does currently not build due to an error during compilation: In file included from ../common/rpc-service.c:39:0: ../../lib/searpc-marshal.h:1027:13: error: redefinition of ‘register_marshals’ ../../lib/searpc-marshal.h:816:13: note: previous definition of ‘register_marshals’ was here ../../lib/searpc-marshal.h:816:13: warning: ‘register_marshals’ defined but not used [-Wunused-function]

commented on 2013-02-23 17:07 (UTC)

Adopted this package, it will now be build from source to avoid python2/python3 problems.

commented on 2013-02-23 15:58 (UTC)

Please make this compile from source, because the precompiled binaries expect python to be python2 instead of python3, which means this will not work with python3 installed, as the connection between applet and server is a python script that won't start, breaking the entire client. To change this the PYTHON variable needs to be set to /usr/bin/python2 at ./configure time. I have a working PKGBUILD that also builds upon the already available ccnet and libsearpc packages: http://pastebin.com/raw.php?i=UkMiPZYw

commented on 2013-02-23 15:55 (UTC)

Please make this compile from source, because the precompiled binaries expect python to be python2 instead of python3, which means this will not work with python3 installed, as the connection between applet and server is a python script that won't start, breaking the entire client. To change this the PYTHON variable needs to be set to /usr/bin/python2 at ./configure time. I have a working PKGBUILD that also builds upon the already available ccnet and libsearpc packages: http://pastebin.com/raw.php?i=LLYYShCs

commented on 2013-02-23 15:55 (UTC)

Please make this compile from source, because the precompiled binaries expect python to be python3 instead of python2, which means this will not work with python3 installed, as the connection between applet and server is a python script that won't start, breaking the entire client. To change this the PYTHON variable needs to be set to /usr/bin/python2 at ./configure time. I have a working PKGBUILD that also builds upon the already available ccnet and libsearpc packages: http://pastebin.com/raw.php?i=LLYYShCs

mbunkus commented on 2012-12-29 19:47 (UTC)

If Python 3 is installed in addition to Python 2.7 then the ccnet-web.sh will start the wrong Python executable. /usr/bin/ccnet-web.sh simply calls "python ..." which is a symlink in /usr/bin to the actual Python version. For me this was /usr/bin/python3, resulting in various syntax errors and, after having manually fixed those, in "module XYZ not found". So please fix ccnet-web.sh to call "python2.7 ..." instead of simply "python ...".