Package Details: seafile 9.0.11-1

Git Clone URL: https://aur.archlinux.org/seafile.git (read-only, click to copy)
Package Base: seafile
Description: An online file storage and collaboration tool
Upstream URL: https://github.com/haiwen/seafile
Licenses: GPL2
Conflicts: seafile-server
Provides: seafile-client-cli
Submitter: eolianoe
Maintainer: Joffrey
Last Packager: Joffrey
Votes: 111
Popularity: 0.000000
First Submitted: 2016-08-11 16:38 (UTC)
Last Updated: 2024-11-14 17:06 (UTC)

Pinned Comments

Latest Comments

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 47 Next › Last »

<deleted-account> commented on 2015-03-04 14:17 (UTC)

@Varakh: In that case I am sorry the slightly harsh reply. Regarding the question: I do not know.

Varakh commented on 2015-03-04 11:14 (UTC)

@calrama: I didn't mean to be rude, sorry if it sounded like it. It is only a for each loop for every $language, isn't it?

<deleted-account> commented on 2015-03-04 10:04 (UTC)

@Varakh I never stated it as optional, please read again. I wrote "I don't use localisations [...]" and explained to you, that if you want this feature, you need to provide a patch, as it normal for a F(L)OSS environment. @derintendant This has been mentioned on the relevant ArchWiki page[1] since May 2014. [1] https://wiki.archlinux.org/index.php/Seafile

derintendant commented on 2015-03-04 09:37 (UTC)

Systemd no longer resolves the %h identifier in the Unit File as of Version 210 (https://bugs.archlinux.org/task/39258). Starting seafile-server via systemd thus fails. I have now hardcoded the path to seafile in the Unit file but I dont really like this "hack".

Varakh commented on 2015-03-04 09:35 (UTC)

@calrama I don't think that those things are "optional". Let me explain: editing seahub_settings.py and adding LANGUAGE='...' is optional, but generating the django.mo for each language should be default because languages are built in per default. They exist. We just don't "compile them with msgfmt". It's another thing to use them in settings.py. Do you know what I mean? :-) @BunBum Thanks, I added SEAFILE_VERSION='4.0.6' manually now. Although this is a bug. :-)

<deleted-account> commented on 2015-03-04 07:40 (UTC)

@Varakh I don't use localisations if it can be avoided, so if you want this functionality, you'd need to provide a tested patch to the PKGBUILD that does it.

BunBum commented on 2015-03-04 06:48 (UTC)

@Varakh regarding the version number: there was already a GitHub issue https://github.com/haiwen/seahub/issues/234

Varakh commented on 2015-03-03 17:47 (UTC)

Update worked, although I can think of some improvements: - step in https://github.com/haiwen/seafile/wiki/Seahub-Translation (msgfmt -o django.mo django.po) for my preferred language had to be done again. Is there a chance that this can be automated? - seahub interface is showing server version 3.0.0. Is this a bug? It is obviously not version 3.0.0. :-)

<deleted-account> commented on 2015-02-23 18:51 (UTC)

@TesterMcTest: Only after libevhtp has been updated for the newly required build options[1] [1] http://manual.seafile.com/build_seafile/server.html#libevhtp

TesterMcTest commented on 2015-02-16 19:10 (UTC)

@calrama: Hi. Could you update the PKGBUILD to the newly released version (4.0.6)?

« First ‹ Previous 1 .. 23 24 25 26 27 28 29 30 31 32 33 .. 47 Next › Last »