Package Details: seafile 9.0.5-1

Git Clone URL: https://aur.archlinux.org/seafile.git (read-only, click to copy)
Package Base: seafile
Description: An online file storage and collaboration tool
Upstream URL: https://github.com/haiwen/seafile
Licenses: GPL2
Conflicts: seafile-server
Provides: seafile-client-cli
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 111
Popularity: 0.000000
First Submitted: 2016-08-11 16:38 (UTC)
Last Updated: 2024-03-05 17:47 (UTC)

Pinned Comments

Latest Comments

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

ptr1337 commented on 2021-07-16 12:13 (UTC) (edited on 2021-07-16 12:14 (UTC) by ptr1337)

or just run:

      yay -G seafile seafile-client
      cd seafile 
      makepkg -si --skipinteg
      cd ..
     cd seafile-client
     makepkg -si --skipinteg

a-bostaurus commented on 2021-07-08 09:27 (UTC)

Perhaps this helps (I let translate it from German to US-English by deepl): Install pacman-contrib (sudo pacman -S pacman-contrib), update manually in the terminal (yaourt -Syyua) until the first error message appears and you are asked if you want to repeat the installation; leave this window as it is for later use, in a second window move to the folder /tmp/yaourt-tmp-username as normal user and execute the command updpkgsums as user, in the first window now answer in the affirmative to the question about the repetition

On the net I also found the following hint: do a sha256sum on the current archive file and paste it into the PKGBUILD

Translated with www.DeepL.com/Translator (free version)

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

I cannot install this package with the following error:

==> 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!

@dsnxt said that the checksum has changed. How do I fix my installation? Should I edit my PKGBUILD locally?

trap000d commented on 2021-07-02 11:17 (UTC)

Yep, they've fixed bug with windows names in 8.0.3 daemon without version change. As far as I understand from PR, they have now a key in config https://github.com/haiwen/seafile/pull/2471 ==

define KEY_HIDE_WINDOWS_INCOMPATIBLE_PATH_NOTIFICATION "hide_windows_incompatible_path_notification"

==

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

sha256 checksum for seafile-8.0.3.tar.gz changed to a83d5d301cf54819ab96ea0ab53824980efdf6727460b969ce3176b4c5109f6b

trap000d commented on 2021-07-01 07:49 (UTC)

To whom it might concern,

I've patched seafile 8.0.3 daemon sources - "it works for me" - here the patch: https://gist.github.com/trap000d/e5d9dfcc5c775a8579307534952121ab

trap000d commented on 2021-07-01 00:56 (UTC)

a-bostaurus, Seafile developers have introduced some controversial changes in client - see here https://github.com/haiwen/seafile/issues/2451

Keep on 8.0.1 until they find a working solution. I have some ideas how to "fix" the issue, though, however hope they will do it themself - I suppose they know their own code better then me.

Alternatively, find and rename all files with "invalid" names in all your Seafile libraries (unfortunately, it's not an option for me)

a-bostaurus commented on 2021-06-07 16:45 (UTC)

Since version 8.0.2-1 I get many information about problems, which are allways the same: The file path contains symbols that are not supported by the windows system. Whatever this means, it disturbes the workflow. My system: Linux blabla 5.12.2-1-MANJARO #1 SMP PREEMPT Fri May 7 17:53:15 UTC 2021 x86_64 GNU/Linux

tdallagn commented on 2021-06-05 11:28 (UTC)

Need to change sha256 of the first file (seafile-8.0.2.tar.gz) to d58f3cff33cf63dcfc1f9c889f365244e3939970e732ed70f39b36a55ed9e585

kepi commented on 2021-06-01 16:57 (UTC)

Wrong checksum for 8.0.2. Changing the first one for 8.0.2 seafile to bb5a3e8296d53d69b1b38b005619f327fc8e7980039bf424983165f7116dca43 helped.

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