Seafile Server 7.0.5 for Raspberry Pi is ready! 29.09.2019

You can get it from the Seafile download section.

We warmly recommend you first, before to proceed with the update, to take a view to the Seafile ChangeLog, because the requirements had changed considerably in the last releases :nerd_face:

:pushpin: Please remember:

  • Don’t forget to stop Seafile Server before the upgrade (i.e: service seafile-server stop or, another example: service seahub stop && service seafile stop)
  • Don’t forget to change the directory rights of Seafile after unpacking it (i.e: chown -R seafile:nogroup seafile-server-7.0.5 or, another example: sudo chown -R seafile:seafile seafile-server-7.0.5 )
  • Don’t forget to apply the upgrade script/s according your start release && with the properly user which in normal case should be seafile (i.e change to seafile user: su seafile -s /bin/bash or, another example: sudo su seafile)

During execution of the upgrade script (upgrade_6.3_7.0.sh) you will get some warnings. Check that these are the same like here. That’s for CE Version OK.

In case you don’t have the certifi and idna python packages installed. You will need to install it.

pip install certifi idna

Link to the official announcement in forum. Could be a help regarding known errors in x64 version.

Once again, thanks to the developers and Seafile Community, specially to @towa48 for his contributions on how to build seafile server by “doing for yourself”.

have fun :blush:

3 Likes

No problem with the upgrade. Thank you jobenvil.

I updated from 6.2.5. I executed both upgrade scripts. After that i started seafile.sh and then seahub.sh. It doesnt work, i dont know why. In Seahub.log is nothing new.

[2019-10-12 12:10:16 +0000] [1011] [INFO] Using worker: sync
[2019-10-12 12:10:16 +0000] [1019] [INFO] Booting worker with pid: 1019
[2019-10-12 12:10:16 +0000] [1020] [INFO] Booting worker with pid: 1020
[2019-10-12 12:10:16 +0000] [1021] [INFO] Booting worker with pid: 1021
[2019-10-12 12:10:16 +0000] [1022] [INFO] Booting worker with pid: 1022
[2019-10-12 12:10:17 +0000] [1023] [INFO] Booting worker with pid: 1023
[2019-10-12 12:15:49 +0000] [1011] [INFO] Handling signal: int
[2019-10-12 12:15:49 +0000] [1019] [INFO] Worker exiting (pid: 1019)
[2019-10-12 12:15:49 +0000] [1021] [INFO] Worker exiting (pid: 1021)
[2019-10-12 12:15:49 +0000] [1020] [INFO] Worker exiting (pid: 1020)
[2019-10-12 12:15:49 +0000] [1022] [INFO] Worker exiting (pid: 1022)
[2019-10-12 12:15:49 +0000] [1023] [INFO] Worker exiting (pid: 1023)
[INFO] Shutting down: Master
Error:Seahub failed to start.
Please try to run “./seahub.sh start” again

I also executed

./seahub.sh python-env seahub/manage.py migrate_file_comment

LC_ALL is not set in ENV, set to en_US.UTF-8

Warning: File comment has changed since version 6.3, while table base_filecomment is not migrated yet, please consider migrate it according to v6.3.0 release note, otherwise the file comment feature will not work correctly.

Start to update schema…
ALTER TABLE base_filecomment RENAME TO base_filecomment_backup_9e9984

CREATE TABLE base_filecomment (
id int(11) NOT NULL AUTO_INCREMENT,
author varchar(255) NOT NULL,
comment longtext NOT NULL,
created_at datetime NOT NULL,
updated_at datetime NOT NULL,
uuid_id char(32) NOT NULL,
PRIMARY KEY (id),
KEY base_filecomment_uuid_id_def2c8_fk_tags_fileuuidmap_uuid (uuid_id),
KEY base_filecomment_author_3c5aaf (author),
CONSTRAINT base_filecomment_uuid_id_63dfbb_fk_tags_fileuuidmap_uuid FOREIGN KEY (uuid_id) REFERENCES tags_fileuuidmap (uuid)
) ENGINE=InnoDB DEFAULT CHARSET=utf8

Start to migate comments data…
Done
Done.