@calrama:
It's simple, you install a dependency somewhere on the system using a virtualenv and so it's not tracked by pacman. Either install everything in a virtualenv or provide a global package including its dependencies. Mixing things up just to fix problems never is a good idea and it does not actually follow KISS. [1]
But I will stop grumbling and will help with fixing this. :)
[1]: https://wiki.archlinux.org/index.php/The_Arch_Way
Search Criteria
Package Details: seafile 9.0.11-1
Package Actions
| 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) |
Dependencies (8)
- fuse (fuse2)
- libevent (libevent-gitAUR)
- libsearpcAUR
- libwebsockets
- python-future
- sqlite (sqlite-fossilAUR)
- intltool (make)
- vala (vala-gitAUR) (make)
Required by (2)
Sources (2)
rumpelsepp commented on 2014-06-25 10:10 (UTC)
kiven commented on 2014-06-25 09:53 (UTC)
@calrama : Yes, I did it each time I upgrade the package (I did it only for french, but i could be nice for each language).
<deleted-account> commented on 2014-06-25 09:46 (UTC)
@rumpelsepp: I don't really see what's "weird" about virtualenv, but I'm always happy to reduce the dependencies, should you get seafile-server to work without it, Otherwise, I got the email notifications regarding the other packages, I will reupload them later today (whyever could they not just run a script that adds dummy .AURINFO to all the AUR packages...)
rumpelsepp commented on 2014-06-25 09:20 (UTC)
@calrama
I have looked at the scripts:
- the virtualenv is only used to install django < 1.6 and djangorestframwork which could eventually be fixed with the instructions from google groups
- the configure script takes PYTHON=/usr/bin/python2, this should be fine
- with a shebang-patch we could get rid of these confusing sed calls which are in the wrong function (should be prepare).
- we have to patch these shebangs:
$ grep /usr/bin/env python -r .
./tools/seafile-admin:#!/usr/bin/env python
./tests/test-transfer.py:#!/usr/bin/env python
./tests/test-share.py:#!/usr/bin/env python
./setupwin.py:#!/usr/bin/env python
./scripts/upgrade/db_update_1.3_1.4.py:#!/usr/bin/env python
./scripts/sqlite2mysql.py:#!/usr/bin/env python
./scripts/build/gen-deb-src.py:#!/usr/bin/env python
./scripts/build/build-server.py:#!/usr/bin/env python
./scripts/build/build-server-src.py:#!/usr/bin/env python
./scripts/build/build-msi.py:#!/usr/bin/env python
./scripts/build/build-deb.py:#!/usr/bin/env python
./scripts/build/build-cli.py:#!/usr/bin/env python
./app/seaf-cli:#!/usr/bin/env python
So I think it should be possible to remove this weird virtualenv hack. I will have a deeper look and create a patch later. But I think we have to test it and play around a bit, so I suggest doing this on github or something similar. :)
Furthermore I have posted comments to some seafile-server dependencies which do not have .AURINFO files. And at last I have sent a message to aur-info [1] about django-pipeline which is outdated and maybe has the wrong package name. I will adopt it or create a new package instead; I will let you know when I get news.
[1]: https://mailman.archlinux.org/pipermail/aur-general/2014-June/028966.html
<deleted-account> commented on 2014-06-25 07:56 (UTC)
@rumpelsepp: Archlinux "python" is Python 3. Seafile explicitly gets the "python" binary (or at least, it did at the time the virtualenv was introduced, which was not done by me, by the way, but by the previous maintainer), expects it to be Python 2, and runs its scripts with it, so the only way to get it to work was to run it in an environment where "python" corresponds to Python 2 (which is what virtualenv does) and I see nothing in your link that addresses this issue (correct me if I'm wrong, of course).
If you want to create a patch for seafile-server to run without virtualenv you're welcome to do so; should it work well, I could include it, but personally I don't consider the little benefit of not using virtualenv worth the amount of code-delving necessary to get it to work.
rumpelsepp commented on 2014-06-25 06:10 (UTC)
What is the purpose of this virtualenv thing in seafile-server.install? You could create a patch, see here: https://groups.google.com/d/msg/seafile/bwbcBQ5ASfE/WmVErc_cjXsJ
<deleted-account> commented on 2014-06-19 10:28 (UTC)
@kiven: Is that something that has to be done after each seahub upgrade? If so, I could try to include it in the seahub-preupgrade script.
kiven commented on 2014-06-19 09:25 (UTC)
here is a tip to translate seahub. You need to go to your seahub instance directory, and go to locale/<LANGUAGE>/LC_MESSAGES and then msgfmt -o django.mo django.po
BunBum commented on 2014-06-18 13:05 (UTC)
@calrama thank you. Everything works fine!
<deleted-account> commented on 2014-06-18 11:32 (UTC)
@BunBum: Update pushed, should work, please test.
Pinned Comments