Package Details: seahub 8.0.7-1

Git Clone URL: (read-only, click to copy)
Package Base: seahub
Description: The web frontend for seafile server
Upstream URL:
Licenses: Apache
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 6
Popularity: 0.000000
First Submitted: 2017-07-03 09:48
Last Updated: 2021-08-18 17:40

Latest Comments

1 2 3 4 5 6 ... Next › Last »

mqs commented on 2021-03-05 15:27

For all those wondering why seafile has to be installed as weirdly as it is (some directory with somthing.tld in /srv which has logs, configs, data and application files mixed, manual upgrades with helpers etc, I have two answers:

  1. This is (sadly) pretty much baked into the seafile-server code base. The multi-domain thing is something I do not understand as I know nobody who hosts multiple instances of seafile on a single machine. This does not make sense and no other package does this. But bundling everything together is hardcoded into seafile.
  2. I tried to fix this on my own by making some modifications to seahub and seafile-server. You can check it out here:

I'm using that package and I'm happy with it, but please be aware that I mostly glued the seafile-server and seahub packages together on my own assumptions and there is no defined upgrade path from the AUR packages to this one. I can only maintain this package because I can observe the changes made here and expect there to be bugs. I currently know of no bugs but I can't guarantee anything.

Joffrey commented on 2021-01-18 21:41

Hello @Artain, sorry I forgot to enable LDAP support.
It should be Ok with seafile-server-8.0.2-2.

Artain commented on 2021-01-18 16:23

@Joffrey can you please check something for me. I just upgraded and now the ldap integration is no longer working. This can be of course a problem with seafile it self and there is already a post in the seafile Forums But I noticed something. Since version 8 no longer has the ccnet component where does seafile get the ldap module from. If you look in the old ccnet package you can see a dependency to libldap but I can't find this or any similar dependency here or in the seafile-server package. Also in the Seafile forums announcement post someone also said that he needs the python lib "python3-ldap" Thank you. Artain

Joffrey commented on 2020-12-05 11:17

Thanks @kuzalj for your feedback, I have bumped "pkgrel" for all dependencies.
For those using ARM you can wait a bit before updating, Python 3.9 isn't on mirrors yet.

kuzalj commented on 2020-12-02 20:03

Just a reminder to everyone that might have some issues. Arch updated the Python packages in the repos to 3.9. This means any python packages you have installed need to be "recompiled" in order for any python depends to work, otherwise, you will get missing depends on errors.

IF you were running seafile with python 3.8 before, running this command will let you know what python packages haven't been recompiled yet and write it to a file.

sudo pacman -Qqo /usr/lib/python3.8/site-packages/* | sort -u > rebuild.txt

Then run this to reinstalll packages (clean the packages, make sure it does a clean rebuild)

yay -S - < rebuild.txt

I can confirm seafile is working with python 3.9. Enjoy!

Joffrey commented on 2020-10-03 09:49

Hello @all,

@kuzalj thanks for the analysis, I have pushed your modifications. For debug Seahub, in ~/domain.tld/conf/ you can change daemon = True by daemon = False and run manualy manualy ~/domain.tld/seafile-server/seahub start.
With this the Python Exception appears.


trap000d commented on 2020-10-01 05:27

@kuzalj, Well. Now it's clear why all stuff has working on my server without errors.

pacman -Ss python-django-rest-framework
community/python-django-rest-framework 3.12.1-1 [installed: 3.11.1-1]

I've not upgraded for the last few weeks so my one is still on 3.11.1

Thanks for information. I will know what to do after next upgrade :)

kuzalj commented on 2020-10-01 04:57


I FIXED IT. I went looking at the Github for seahub after noticing the error is related to django-rest-framework. There is a commit that somehow made it right after 7.1.5 requiring djangorestframework==3.11.1 instead of the undefined version before. I started researching, and 3.11.1 is the last version that supports django 1.xx. The version of django-rest-framework in the Arch repo is too new for Joffrey's bundled version of django, which is 1.11.29. Version 1.11.29 is required for Seahub however, as it relies on an old version. I believe I was reading in the commit history that they are updating to 2.xx the next release.

Either way, you need to bundle this older version of the rest-framework much like Jeoffrey did with django-picklefield. I edited the PKGBUILD to grab version 3.11.1 of django-rest-framework in the same way, and re-copied seafile-server, and everything is working again. @Joeffrey, since Arch updated the package, the package you depend on is too new and you will have to bundle rest-framework until the next seafile version updates with django 2.xx


# Maintainer: Joffrey <>
# Contributor: eolianoe <eolianoe [at] gmail [DoT] com>
# Contributor: Edvinas Valatka <>
# Contributor: Aaron Lindsay <>

pkgdesc='The web frontend for seafile server'
    'python-wsgidav-seafile: Webdav support'
    'python-django-pylibmc: Memcached support'
    'ffmpeg: For video thumbnails'
# Outdated Python modules, but required by Seahub

prepare() {
    cd "$srcdir/$pkgname-$pkgver-server"

    # Remove useless files and directories
    rm -rf \
        ./{CONTRIBUTORS,HACKING,Makefile} \
        ./{*test*,*dev*,*sh*,README*,pylintrc*,LICENSE*} \
        "$(find . -name \*.pyc)"

    sed -i -E "/SEAFILE_VERSION/s/[0-9.]+/$pkgver/" ./seahub/

build() {
    cd "$srcdir/$pkgname-$pkgver-server"

    for locale in ./locale/*/LC_MESSAGES/*.po; do
        echo "$locale"
        msgfmt -vo "${locale%.po}.mo" "$locale"

package() {
    cd "$srcdir/seahub-$pkgver-server/"

    install -dm755 "$pkgdir/usr/share/seafile-server/seahub"
    cp -r -p "./"* "$pkgdir/usr/share/seafile-server/seahub/"

    # Install third part
    for thirdpart in "${_thirdpart[@]}"; do
        cd "$srcdir/$thirdpart"
        python install \
            --root="$pkgdir/" \
            --install-lib="usr/share/seafile-server/$pkgname/thirdpart/" \
    rm -rf "$pkgdir"/usr/{bin,share/seafile-server/"$pkgname"/thirdpart/*.egg-info}

    install -Dm644 \
        "$srcdir/seahub@.service" \
    install -Dm644 \
        "$srcdir/nginx.example.conf" \

kuzalj commented on 2020-10-01 04:14


I believe i have python-django installed, because I use it for other packages. But Joffrey's package (look at the PKGBUILD) downloads django-1.11.29.tar.gz and sets it up to be used. So in effect, running seahub makes you use django 1.11.29. This was done on purpose i thought by Jeoffrey because we needed the older version?

trap000d commented on 2020-10-01 04:10

@kuzalj, Check your python-django (or python2-django) installation

ImportError: cannot import name 'ProhibitNullCharactersValidator' from 'django.core.validators'

'ProhibitNullCharactersValidator' was implemented in Django 2, so if you still have any instance of Django 1.x around, it might break all things.