I just did a quick test on Debian Stable (Buster), but Seahub didn’t come up:
django.core.exceptions.ImproperlyConfigured: mysqlclient 1.3.13 or newer is required; you have 1.3.10.
Django 2.2 requires python3-mysqldb => 1.3.13, but this package is 1.3.10 on stable.
There are Buster Backports for Django 2.2, so I guess, this can be fixed somehow.
We find open cloud mesh feature is not ready to test yet and the upgrade script is missing. Once obvious bugs are fixed, we will announce the new version.
Traceback (most recent call last):
File "seahub/manage.py", line 8, in <module>
from django.core.management import execute_from_command_line
File "/opt/seafile/seafile-server-8.0.0/seahub/thirdpart/django/__init__.py", line 1, in <module>
from django.utils.version import get_version
File "/opt/seafile/seafile-server-8.0.0/seahub/thirdpart/django/utils/version.py", line 71, in <module>
@functools.lru_cache()
AttributeError: 'module' object has no attribute 'lru_cache'
Done.
In upgrade SQL directory for 8.0.0. there are a “seafevents.sql” but i don’t have a table “seafevents” or similar. In upgrade directory for 6.3.0 are the same file. So is it needed or whats going on with this table? How can i setup this table?
What is the behavior of the libraries sharing between two seafile servers using the open cloud mesh protocol: Is the shared library synchronized to both servers?
That could be a good solution for EU-China collaboration.
Hello. As I understand you are the developer of this program. I have a question about making changes to the design of the project. I have often seen that you can make your own adjustments to the design for greater ease of use. How exactly can I do this?