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 .. 4 5 6 7 8 9 10 11 12 13 14 Next › Last »

Captain_Rage commented on 2020-02-25 14:57 (UTC) (edited on 2020-02-25 15:03 (UTC) by Captain_Rage)

I think I've successfully managed to upgrade seafile-server and seahub (7.0.5 → 7.1.1) but I have no idea how to initialize and run the server, since the systemd unit changed:

The former

ExecStart=/usr/bin/seafile-admin start

made some sense while the new

ExecStartPre=/srv/seafile/%i/seafile-server/seafile.sh start
ExecStart=/srv/seafile/%i/seafile-server/seahub.sh start

suggest that these scripts be run from a place they are not even present in (and copying them to that, or corresponding location, also fails to start seafile-server since it immediately complains about a missing "conf" folder, even though it is present).

It the easiest course of action simply to wait for the Python 3 version of seafile-admin and leave my current configuration as it is?

Joffrey commented on 2020-02-14 13:06 (UTC)

@yuyichao Many thanks for your contributions, your approach is interesting and it will decrease the number of patchs.

I also tested the 7.1.1 upgrade but with a Python virtualenv and Pypi packages.

I will try to test your modifications soon.

yuyichao commented on 2020-02-14 02:45 (UTC)

I've updated the archlinuxcn version of the package to 7.1.1 and python3 [1]. Please feel free to take any part you may find useful. It also seems that seafile-admin is out of date even for the 7.0 version and I've also changed the seafile-server[2] package and copied some update based on scripts/. It might be better to just switch to using scripts/ instead though that also need some patches....

So far the only issue I haven't fixed after the upgrade seems to be that shared link with password protection seems to be not working....

[1] https://github.com/archlinuxcn/repo/blob/f14bad28d1ab0ea9791e7d66fd1224cf2f14fd3b/archlinuxcn/seahub/PKGBUILD [2] https://github.com/archlinuxcn/repo/blob/f14bad28d1ab0ea9791e7d66fd1224cf2f14fd3b/archlinuxcn/seafile-server/PKGBUILD

DanSman commented on 2020-01-06 19:59 (UTC)

https://forum.seafile.com/t/seafile-server-7-1-0-is-ready-for-testing-migrate-to-python-3/10566/50

I think we have to wait until it is fully supported by Python 3. So many dependencies are no longer available. The biggest problem at the moment is probably the python2-django dependency.

DasGurke commented on 2019-11-12 17:11 (UTC)

I "fixed" my issue by changing two if not emailuser statements in seahub/base/accounts.py to if emailuser == None. One occurence was on line 98, the other on line 545. Judging from my very superficial Python knowledge this should mitigate the problem until I have time to figure this out properly.

DasGurke commented on 2019-11-12 16:27 (UTC)

After a reboot Seahub has stopped working, it keeps erroring out on every login with the following message:

AttributeError at /accounts/login/

type object '_SearpcObj' has no attribute '__bool__'


Request Method:     POST
Request URL:    http://--redacted--/accounts/login/?next=/
Django Version:     1.11.25
Exception Type:     AttributeError
Exception Value:    

type object '_SearpcObj' has no attribute '__bool__'

Exception Location:     /usr/lib/python2.7/site-packages/future/types/newobject.py in __nonzero__, line 70
Python Executable:  /usr/bin/python2
Python Version:     2.7.17
Python Path:    

['/srv/seafile/--redacted--/seafile-server/seahub',
 '/usr/bin',
 '/srv/seafile/--redacted--/seafile-server/seahub/thirdpart',
 '/usr/lib/python27.zip',
 '/usr/lib/python2.7',
 '/usr/lib/python2.7/plat-linux2',
 '/usr/lib/python2.7/lib-tk',
 '/usr/lib/python2.7/lib-old',
 '/usr/lib/python2.7/lib-dynload',
 '/usr/lib/python2.7/site-packages',
 '/usr/lib/python2.7/site-packages/gtk-2.0',
 '/srv/seafile/--redacted--/seafile-server/seahub/seahub/api2/endpoints/../../../../../conf',
 '/srv/seafile/--redacted--/seafile-server/seahub/seahub/api2/endpoints/../../../../../conf']

Server time:    Tue, 12 Nov 2019 16:17:22 +0000

I assumed this was some kind of problem with seafrpc so I rebuild the following packages: ccnet-server seahub libevhtp-seafile libsearpc. Sadly, this did not fix the issue.

Did anyone here stumble over the same problem?

zkrx commented on 2019-09-17 17:39 (UTC)

I don't understand the pinned comment. Does it mean that we shouldn't upgrade the package using pacman -U?

pvagner commented on 2019-08-14 07:05 (UTC)

Yes, setting daemon = false helped me to discover a typo in my config and now it's all working great for me again. BTW 7.0.4 is out.

DasGurke commented on 2019-08-13 18:15 (UTC)

For whatever reason the Seahub logfile wandered over to /tmp/seahub.log for me. If that doesn't work you can probably set daemon = False in gunicorn.conf.

pvagner commented on 2019-08-13 16:41 (UTC)

Can anyone run seahub after upgrading to 7.0.3? According to the seafile-admin start output it's started successfully, however seahub.log is empty and I can't figure out a way on how to peek at gunicorn's output.

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