@fidelio33b Here is the source of the knowledge It is kaputt 
ok, thanks…
arg…
/opt/seafile/seafile-server-7.1.4/seafile/bin/seaf-server-init: error while loading shared libraries: libmariadbclient.so.18: cannot open shared object file: No such file or directory
I’ve found seafile/lib/libmariadb.so.3 but not libmariadbclient.so.18 !
I run raspbian buster and libmariadbclient.so.18 seems to be for bionic !
Sorry…
Ok, last minute compilation for buster
If it works, I will let work the other containers later.
My error was exactly here, on --hard master
build_seafile()
{
echo
echo -e "\n\e[93m-> [6/$STEPS] Build seafile-server\e[39m\n"
cd $BUILDFOLDER
if [ -d "seafile-server" ]; then
cd seafile-server
(set -x; git reset --hard origin/master)
(set -x; git pull)
else
(set -x; git clone https://github.com/haiwen/seafile-server.git)
cd seafile-server
fi
(set -x; git reset --hard master) #it is harmless if != $VERSION_TAG
(set -x; ./autogen.sh)
(set -x; ./configure --with-mysql=$MYSQL_CONFIG_PATH)
(set -x; make dist)
cd $SCRIPTPATH
}
I used master branch for R7.1.3 since the master had some fixes that I want to include, but after the last commits, it is better to stick to $VERSION_TAG until the new tags are consolidated. SOOORRRRYYY
Your seafile server configuration has been finished successfully.
Many thanks to you, I will hold on
Not so bad but…
$ ./seafile.sh start … done
and
$ ./seahub.sh start
LC_ALL is not set in ENV, set to en_US.UTF-8
./seahub.sh: line 210: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8): No such file or directory
Starting seahub at port 8000 …
Traceback (most recent call last):
File “/opt/seafile/seafile-server-7.1.4/check_init_admin.py”, line 351, in
rpc = RPC()
File “/opt/seafile/seafile-server-7.1.4/check_init_admin.py”, line 284, in init
import ccnet
ModuleNotFoundError: No module named ‘ccnet’
To be continued… tomorrow !
It’s fixed in stretch, bionic, buster.
The problem appears for new installations, other like update had no issues.
Hi
Right, I remember I did it with my tries before downloading your last tarball !
I’ll take a look today.
Thanks !
Everything is almost correct…
I’ve downloaded the last tarball, removed everything (dir, databases…) and restarted install from scratch.
The install process was fine, everything done and seafile.sh started
but when starting seahub.sh :
…
Successfully created seafile admin
Error:Seahub failed to start.
Please try to run “./seahub.sh start” again
I’ve tried to look in logs but seahub.log is empty and ccnet.log/controller.log/seafile.log are correct.
Sorry… what did I missed ?
Read pls. the docu.
ok
found a dependency pb out of the scope of this f…g manual !
I’ll try to stop annoying you anymore and find by mylself…
Best regards
@jobenvil
It works !!! Many thanks for your help 
I will deploy it in production environment.
Just to be sure, it’s completely equivalent to do this ? Nothing is missing ?
sudo apt-get install python3 python3-setuptools python3-pip python3-ldap sqlite3 -y
sudo apt-get install libmemcached-dev zlib1g-dev libxml2-dev libxslt-dev
sudo apt-get install python3-lxml python3-jsmin python3-defusedxml python3-pam
pip install certifi idna
Regarding python3-pam, this package is not available. I replace it with what ?
About pip install certifi idna, I can replace it with what ?
Have a nice day.
Great news and congratulations!
I was wondering when a new release comes and finally here it is! I’m using Seafile from the very beginning, looking forward for 7.1.4 running on my RPI. Thus will start upgrading these days and hope to not encounter too many issues. 
These both you don’t need anymore since they are already shipped on the /seahub/thirdpart directory
My bad, here the correct name is python-pam which is for python 2/3. This is shipped in thirdpart directory /seahub/thirdpart too.
Conclusion: You don’t need to install the python-pam, certifi, idna, since they are already included in the seafile package .
The only you need are
Jinja2 : install by python3-jinja2sqlalchemy : install by python3-sqlalchemy
but if you have followed the documentation, they you have maybe already installed by pip. My recomendation was via apt
The rest look like good i.e. you use sqlite3
@Niclas I hope so, now you have 3 OS flavours to choose. That improves the stability and you get new and secure libraries if you use the Buster or Bionic.
@jobenvil
Yes, I made the choice to use SQLite. Regarding my use, it’s enough.
In my testing environment, I used pip. But I will install everything in my production environment without pip.
So, to sum up with Raspian Buster and Seafile/SQLite you only need :
sudo apt-get install python3 python3-setuptools python3-ldap sqlite3 -y
sudo apt-get install libmemcached-dev zlib1g-dev libxml2-dev libxslt-dev
sudo apt-get install python3-jinja2 python3-sqlalchemy
Many thanks for your help.
Have a nice day.
Thank you too. Yes, your summarize looks like good to me.
First of all - thank you for your great job bringing 7.1.4 to rpi!
And congratulations - the seafile team managed to get seafile for rpi working with seadrive in combination with shared libraries! This is indeed good news! 
After reading all the useful comments I was able to get WebDAV working at least.
Unfortunately seaf-fuse does make problems - it seems to start but it doesn’t work. The mounted folder is empty and it shows the following errors when I do ‘systemctl start seafile-server.service’.
Mai 25 19:32:53 hermes seaf-fuse[9180]: g_key_file_has_key_full: assertion 'key_file != NULL' failed
Mai 25 19:32:53 hermes seaf-fuse[9180]: g_propagate_error: assertion 'src != NULL' failed
Mai 25 19:32:53 hermes seaf-fuse[9180]: g_key_file_has_key_full: assertion 'key_file != NULL' failed
Mai 25 19:32:53 hermes seaf-fuse[9180]: g_propagate_error: assertion 'src != NULL' failed
Mai 25 19:32:53 hermes seaf-fuse[9180]: g_key_file_get_integer: assertion 'key_file != NULL' failed
Mai 25 19:32:53 hermes seaf-fuse[9180]: g_key_file_has_key_full: assertion 'key_file != NULL' failed
Mai 25 19:32:53 hermes seaf-fuse[9180]: g_propagate_error: assertion 'src != NULL' failed
Mai 25 19:32:55 hermes seafile-server[9035]: seaf-fuse started
Mai 25 19:32:55 hermes seafile-server[9035]: Done.
Similar thing when I try to start via script.
seafile-user@hermes:~/seafile-server-7.1.4$ ./seaf-fuse.sh start /media/seafile-fuse
Starting seaf-fuse, please wait ...
(process:3763): GLib-CRITICAL **: 17:56:09.562: g_key_file_has_key_full: assertion 'key_file != NULL' failed
(process:3763): GLib-CRITICAL **: 17:56:09.563: g_propagate_error: assertion 'src != NULL' failed
(process:3763): GLib-CRITICAL **: 17:56:09.563: g_key_file_has_key_full: assertion 'key_file != NULL' failed
(process:3763): GLib-CRITICAL **: 17:56:09.563: g_propagate_error: assertion 'src != NULL' failed
(process:3763): GLib-CRITICAL **: 17:56:09.563: g_key_file_get_integer: assertion 'key_file != NULL' failed
(process:3763): GLib-CRITICAL **: 17:56:09.563: g_key_file_has_key_full: assertion 'key_file != NULL' failed
(process:3763): GLib-CRITICAL **: 17:56:09.563: g_propagate_error: assertion 'src != NULL' failed
seaf-fuse started
Done.
Any hints for me?
@jobenvil
Your welcome !! But everything is possible thanks your great job.
I don’t understand, I run all the installation smoothly. Everything worked. And this night, I don’t know why seahub fall… I rebooted, deleted /tmp/seahub_cache/, opened /home/pi/SeaFile/conf/seahub_settings.py, etc. Nothing, except I can’t write in the file seahub_settings.py, even if my access rights are good ;
I don’t understand, what happens. Some ideas ?
Have a nice day.