Package Details: seahub 11.0.13-1

Git Clone URL: https://aur.archlinux.org/seahub.git (read-only, click to copy)
Package Base: seahub
Description: The web frontend for seafile server
Upstream URL: https://github.com/haiwen/seahub
Licenses: Apache
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 7
Popularity: 0.000000
First Submitted: 2017-07-03 09:48 (UTC)
Last Updated: 2024-11-14 17:03 (UTC)

Pinned Comments

Latest Comments

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

mqs commented on 2020-06-27 11:20 (UTC) (edited on 2020-06-28 12:41 (UTC) by mqs)

@Joffrey what do you mean when you write the following?

upgrade seafile-server directory with /usr/share/seafile-server in your instances, as a release change

Do you mean that we should copy the contents of /usr/share/seafile-server into /srv/<instance>/seafile-server? Does seafile-helper simplify this and if yes with which invocation? Also: are there files which should not be overwritten or can we completely remove all the contents of seafile-server and copy the new stuff in?

On another note, I have wondered this since I installed the package some years ago, but why is seafile/seahub laid out for multiple instances (I don't know any other package which does this) and why don't they simply all link to the same static seahub files and have a separate directory for state and configuration in /var/lib and /etc? Is this due to issues with seafile?

kuzalj commented on 2020-06-23 22:58 (UTC)

@Joffrey

Thank you so much for the minor upgrade. You were right about django-picklefield and this update essentially fixed the issue since you bundled it with the release.

Seafile is working for me once again, thank you :)

Joffrey commented on 2020-06-21 11:20 (UTC)

Hello @all,

For Seahub v7.1.4-2 you should to upgrade seafile-server directory with /usr/share/seafile-server in your instances, as a release change and execute minor-upgrade.sh after.

Best regards.

Joffrey commented on 2020-06-12 21:28 (UTC)

@kuzalj, It's Django-picklefield. The support of Django v1.11 was dropped, a downgrade to python-django-picklefield-2.1.1-1 temporarily fixes the problem. I'll look for a viable solution.

kuzalj commented on 2020-06-11 09:48 (UTC)

Not sure what I am doing wrong, but after running pacman and getting some python updates, I am getting an error on 7.1.4

TypeError at /
from_db_value() takes 4 positional arguments but 5 were given


Request Method: GET
Request URL:    https://x.com/
Django Version: 1.11.25
Exception Type: TypeError
Exception Value:    
from_db_value() takes 4 positional arguments but 5 were given
Exception Location: /srv/seafile/x.com/seafile-server/seahub/thirdpart/django/db/models/sql/compiler.py in apply_converters, line 832
Python Executable:  /usr/bin/python3
Python Version: 3.8.3
Python Path:    
['/usr/bin',
 '/srv/seafile/x.com/seafile-server/seafile/lib/python3.6/site-packages',
 '/srv/seafile/x.com/seafile-server/seafile/lib64/python3.6/site-packages',
 '/srv/seafile/x.com/seafile-server/seahub',
 '/srv/seafile/x.com/seafile-server/seahub/thirdpart',
 '/srv/seafile/x.com/seafile-server',
 '/usr/lib/python38.zip',
 '/usr/lib/python3.8',
 '/usr/lib/python3.8/lib-dynload',
 '/usr/lib/python3.8/site-packages',
 '/srv/seafile/x.com/seafile-server/seahub/seahub/api2/endpoints/../../../../../conf',
 '/srv/seafile/x.com/seafile-server/seahub/seahub/api2/endpoints/../../../../../conf']

yuyichao commented on 2020-03-29 12:35 (UTC)

Yes, either of the change should be enough to fix the issue.

Joffrey commented on 2020-03-29 10:55 (UTC)

@yuyichao, I have make a test and I think this patch is enough :

- <form action="{% url view_name token %}?p={{ path }}" method="post" id="share-passwd-form">
+ <form action="{% url view_name token %}?p=/{{ path }}" method="post" id="share-passwd-form">

Thanks for debugging.

yuyichao commented on 2020-03-29 01:41 (UTC)

Glad it works.

DanSman commented on 2020-03-29 01:11 (UTC)

..., you got the white space correct right?

Nah, you were right. That was wrong.

yuyichao commented on 2020-03-29 00:54 (UTC) (edited on 2020-03-29 00:54 (UTC) by yuyichao)

Oh, that repo.py. I thought you are talking about some code you use... Whatever....

Just to state the obvious (if you are a python users), if you applied the patch manually, you got the white space correct right?

The way I found the error last time was to just put something like a raise ValueError() in seahub/thirdpart/django/views/defaults.py at the beginning of server_error. That either cause the server to quite or otherwise cause a full backtrace to be printed. The message from there should tell you what kind of error you got. I don't really see how the new code, with the only addition beting basically a comparison to empty string, should cause and error in this case....

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