Arch Linux User Repository

Hey yuyichao

Thanks for the patch.

I have updated it manually, as I installed it, as I have described a few posts below. Well, I am on 7.1.3 and only changed the file share_access_validation.html with your patch. repo.py did not work and ends in Internal Server Error. Without repo it works.
Thanks

@DanSman https://github.com/haiwen/seahub/pull/4442

See also https://github.com/archlinuxcn/repo/blob/3844a0e73eff940e25e5d138f4d379d43ffbdb0a/archlinuxcn/seahub/PKGBUILD for the updated 7.1.3 PKGBUILD including the patch.

Nah, that doesn't change anything on my end. Same problem. But thanks.

Edit:
Update to Seafile v7.1.2, same problem.

I briefly had the same issue, revoking the shared link and then generating it again was a workaround that solved this for me. That obviously only works if you can live with the changed link.

Hey

Does "shared folder + password protection" work for you?

I get an error:

Page unavailable

Sorry, but the requested page is unavailable due to a server hiccup.

Our engineers have been notified, so check back later.

But only with passwd protection.

Some notes in regarding to seafdav. Yesterday I've managed to build and run WebDAV backend for seafile 7.1.1. As it depends on Python3, two extra packages must be installed to satisfy dependensies (save the other deps): python-seafobj and python-wsgidav-seafile. To whom it may interest here is my repo with corresponding PKGBILD's: https://github.com/trap000d/aur/tree/master/seafile-server

P.S. I haven't submitted any packages to AUR yet so have no any experience with their maintenance. I'll be happy if someone could adopt the packages mentioned above.

TBH ... I don't understand the installation process of the wiki.

I'll leave here my own one. Maybe someone wants to create a new wiki or update the old one or we can figure out together?

I have to install also the package libselinux also from the AUR.

So, I installed seahub (to get all necessary pkgs) and libeslinux.

pikaur -S seahub libeslinux

sudo useradd -m -r -d /home/seafile -s /usr/bin/nologin seafile

sudo -u seafile -s /bin/sh

cd && mkdir installed && wget https://s3.eu-central-1.amazonaws.com/download.seadrive.org/seafile-server_7.1.1_x86-64.tar.gz && tar -xzf seafile-server_* && mv seafile-server_* installed && cd seafile-server-* && ./setup-seafile-mysql.sh

./seafile.sh start
./seahub.sh start 8000

sudo nano /etc/systemd/system/seafile.service

add:

[Unit]
Description=Seafile
# add mysql.service or postgresql.service depending on your database to the line below
After=network-online.target network.target NetworkManager-wait-online.service NetworkManager.service mariadb.service

[Service]
Type=oneshot
ExecStart=/home/seafile/seafile-server-latest/seafile.sh start
ExecStop=/home/seafile/seafile-server-latest/seafile.sh stop
RemainAfterExit=yes
User=seafile
Group=seafile

[Install]
WantedBy=multi-user.target

sudo nano /etc/systemd/system/seahub.service

add:

[Unit]
Description=Seahub
After=network-online.target network.target NetworkManager-wait-online.service NetworkManager.service seafile.service

[Service]
Type=oneshot
ExecStart=/home/seafile/seafile-server-latest/seahub.sh start
ExecStop=/home/seafile/seafile-server-latest/seahub.sh stop
RemainAfterExit=yes
User=seafile
Group=seafile

[Install]
WantedBy=multi-user.target

sudo systemctl enable seafile.service && sudo systemctl enable seahub.service

I know, it's without any description. Is just a quick "overview" actually. I just want to get this right. I prefer to use the official upgrades/installation.

Could you explain a little bit more about the installation process of Seahub?

Webdav isn't working right now, right? Because of the missing pkg python-wsgidav-seafile? Couldn't get this running.

Thank you very much
Dan

Edit:
Tree is the same:

/home/seafile/
├── ccnet
│   ├── ccnet-rpc.sock
│   └── misc
├── conf
│   ├── ccnet.conf
│   ├── gunicorn.conf.py
│   ├── __pycache__
│   ├── seafdav.conf
│   ├── seafile.conf
│   └── seahub_settings.py
├── installed
│   └── seafile-server_7.1.1_x86-64.tar.gz
├── logs
│   ├── ccnet.log
│   ├── controller.log
│   ├── seafile.log
│   └── seahub.log
├── pids
│   ├── ccnet.pid
│   ├── seaf-server.pid
│   └── seahub.pid
├── seafile-data
│   ├── httptemp
│   ├── library-template
│   ├── seafile.sock
│   ├── storage
│   └── tmpfiles
├── seafile-server-7.1.1
│   ├── check_init_admin.py
│   ├── reset-admin.sh
│   ├── runtime
│   ├── seaf-fsck.sh
│   ├── seaf-fuse.sh
│   ├── seaf-gc.sh
│   ├── seafile
│   ├── seafile.sh
│   ├── seahub
│   ├── seahub.sh
│   ├── setup-seafile-mysql.py
│   ├── setup-seafile-mysql.sh
│   ├── setup-seafile.sh
│   ├── sql
│   └── upgrade
├── seafile-server-latest -> seafile-server-7.1.1
└── seahub-data
    └── avatars

@Captain_Rage - seafile-admin is not supported for a long time and I don't think it will be updated in Python 3.

Now with the contribution of @yuyichao Seafile can practically be installed/upgraded as in the official manual.

https://download.seafile.com/published/seafile-manual/home.md

Your installation tree should look like this:

tree -L 2 /srv/seafile/seafile.tld
/srv/seafile/seafile.tld
├── ccnet
│   ├── ccnet-rpc.sock
│   └── misc
├── conf
│   ├── ccnet.conf
│   ├── gunicorn.conf.py
│   ├── __pycache__
│   ├── seafdav.conf
│   ├── seafile.conf
│   └── seahub_settings.py
├── logs
│   ├── ccnet.log
│   ├── controller.log
│   ├── seafile.log
│   └── seahub.log
├── pids
│   └── seahub.pid
├── seafile-data
│   ├── httptemp
│   ├── library-template
│   ├── pids
│   ├── seafile.sock
│   ├── storage
│   └── tmpfiles
├── seafile-server
│   ├── check_init_admin.py
│   ├── reset-admin.sh
│   ├── runtime
│   ├── seaf-fsck.sh
│   ├── seaf-fuse.sh
│   ├── seaf-gc.sh
│   ├── seafile
│   ├── seafile.sh
│   ├── seafobj_migrate.py
│   ├── seahub
│   ├── seahub.conf
│   ├── seahub.sh
│   ├── setup-seafile-mysql.py
│   ├── setup-seafile-mysql.sh
│   ├── setup-seafile.sh
│   ├── sql
│   ├── sqlite2mysql.py
│   ├── sqlite2mysql.sh
│   └── upgrade
├── seafile-server-latest -> seafile-server
└── seahub-data
    ├── avatars
    └── thumbnail

The content of the Systemd service has changed, but the result should be the same.

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?

@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.