Tails

#2 Updated by Anonymous 2015-08-24 05:10:00

Weblate dependencies (from https://docs.weblate.org/en/latest/admin/install.html)

apt-get install python git python-django translate-toolkit python-whoosh python-pil python-libravatar python-babel mercurial python-social-auth pyuca

1. Web server option 1: nginx and uwsgi
   apt-get install nginx uwsgi uwsgi-plugin-python
2. Web server option 2: Apache with mod_wsgi
   apt-get install apache2 libapache2-mod-wsgi
3. Caching backend: memcached
   apt-get install memcached
4. Database option 1: mariadb
   apt-get install mariadb-server
5. Database option 2: mysql
   apt-get install mysql-server
6. Database option 3: postgresql
   apt-get install postgresql
7. SMTP server
   apt-get install exim4

dependencies which are not in Wheezy (installation via PIP only):
python-requests-oauthlib python-six python-openid python-django-crispy-forms

#6 Updated by Anonymous 2015-09-11 09:19:58

As noted by Martin Borgert: A small step is still a step: pyuca is now in NEW, packaged by Daniel Stender. pyuca is an optional package for weblate, but we can Depend on it, as soon as it is in unstable.

#7 Updated by Anonymous 2015-09-11 09:20:54

sajolida wrote:
> Why is this assigned to me? I probably created this ticket while wrapping up the notes from the summit but I have no personal interest in this.

sorry about the misunderstanding.

#11 Updated by emmapeel 2017-02-18 11:07:46

Yes, there are some new dependencies, because of changes on the
python-social-auth code, see:
https://github.com/omab/python-social-auth#deprecation-notice---2016-12-03

I have added 854895 and 854894 to the Debian BTS for them.

#16 Updated by drebs 2018-03-03 15:08:31

This is an up-to-date list of hard deps for Weblate 2.19 and their relation to Debian packages:

So, in summary, we’d need to create 4 new packages (and backport them) and also backport 4 other packages.

#17 Updated by drebs 2018-03-04 18:17:49

drebs wrote:
> This is an up-to-date list of hard deps for Weblate 2.19 and their relation to Debian packages:
> …
> So, in summary, we’d need to create 4 new packages (and backport them) and also backport 4 other packages.

Actually, there is one more packages to create because deps of deps are missing in the table above. social-auth-core has already been uploaded. These are the deps of deps for the direct deps of Weblate that are not yet packaged for Debian:

siphashc 1.0:

• No deps.

social-auth-app-django 2.1.0:

• six (1.10.0 is in stretch
• social-auth-core >= 1.2.0 (already uploaded

user-agents:

• ua-parser >= 0.4.1

ua-parser 0.7.3:

• pyyaml (required for setup, 3.12 is in stretch

So this amounts to a new total of 4 missing packages, not counting social-auth-core, as it’s been uploaded, and counting one new dep of dep. The missing packages are: siphashc, social-auth-app-django, user-agents and ua-parser

#18 Updated by drebs 2018-03-06 15:35:41

Here are ITPs on the Debian BTS for the missing packages:

• social-auth-core (already uploaded): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854894
• siphashc: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892182
• social-auth-app-django: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854895
• user-agents: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892190
• ua-parser: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890327

There’s some ongoing discussion about how to handle a cross-package dependency of ua-parser that might need packaging itself.

#19 Updated by drebs 2018-04-03 09:26:03

Update:

• social-auth-core 1.7.0 is now in Debian testing
• social-auth-app-django 2.1.0 has been packaged but the sponsor has not uploaded it yet.
• ua-parser 0.7.3 is now in Debian testing

Still missing: siphashc and user-agents.

There’s something else that is missing that the sponsor asked us to do, which is to go through the code of Weblate to find third party libraries or other dependencies that are not explicitelly listed as such (as for example this javascript file that is part of this third-party library. For these cases, we can either (ideally) file RFPs and then proceed with separating and packaging them or use embedded copies (if upstream needs an exact version and the Debian package is too new or too old).

#20 Updated by drebs 2018-06-10 14:09:47

Meanwhile, Weblate 3.0 was released, and this table compares dependencies previously mapped for 2.19 to current dependencies for 3.0:

It’s worth to mention here that the team is currently discussing what is the best option to upgrade and maintain Weblate in production for the longer term. The options are, currently, package everything to Debian, install python modules from Git and pin versions, or use Weblate’s upstream docker image. We are currently debating what’s the sanest option for short and long terms.

#30 Updated by intrigeri 2019-09-13 11:54:23

• In https://git.tails.boum.org/puppet-tails/tree/manifests/weblate/python_modules.pp every dependency we currently install via PIP is sorted between those that are in Stretch and those that are only in Buster. Apparently Buster has all the deps for Weblate 2.20.
• Some nice folks keep the RFP bug updated with blocking relationships to other RFPs for missing dependencies.

As of Weblate 3.8 what’s missing in Buster among requirements.txt:

• in testing/sid:
  • translate-toolkit 2.4.0 ** jellyfish >= 0.6.1 ** python3-diff-match-patch 20181111
• needed version is not in Debian at all
  • oauthlib >= 3.0.0 (sid has 2.1.0-1)
  • openpyxl >= 2.6.0 (sid has 2.4.9-1)
  • translation-finder >= 1.4 (sid has 1.0-1+b1)
• package not in Debian at all
  • celery-batches: https://bugs.debian.org/921335