Bug #16943

Upgrade to Weblate 3.x

Added by intrigeri 2019-08-07 11:13:14 . Updated 2019-12-12 16:12:52 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Infrastructure
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Sysadmin
Blueprint:

Starter:
Affected tool:
Translation Platform
Deliverable for:
309

Description

Wrt. the dependencies and their status in Debian, see Feature #10038#note-30.

Subtasks

Related issues

Related to Tails - Bug #16994: Weblate database switch to PostgreSQL Resolved 2020-04-01 2020-04-01
Related to Tails - Bug #17050: Translation platform: design & implement long-term maintenance & support plan In Progress
Related to Tails - Bug #16183: Weblate cannot update some database schemes when upgrading Resolved 2018-12-03
Blocks Tails - Bug #16221: Stop using DocBook-style CSS classes In Progress 2018-12-13
Blocks Tails - Bug #16974: Improve Weblate UX for first-time visitors Confirmed
Blocks Tails - Feature #17358: Enable Markdown checks on Weblate Resolved

History

#1 Updated by sajolida 2019-08-09 14:13:43

  • blocks Bug #16221: Stop using DocBook-style CSS classes added

#2 Updated by intrigeri 2019-08-12 12:06:58

  • blocks Bug #16974: Improve Weblate UX for first-time visitors added

#3 Updated by intrigeri 2019-08-24 07:07:37

  • related to Bug #16994: Weblate database switch to PostgreSQL added

#4 Updated by Anonymous 2019-09-13 09:34:55

  • related to Bug #17050: Translation platform: design & implement long-term maintenance & support plan added

#5 Updated by intrigeri 2019-09-13 09:41:57

  • Deliverable for set to Sponsor_L

Only if there’s budget left once we’re done with the other SponsorL blockers.

#6 Updated by intrigeri 2019-09-13 10:08:53

  • related to Bug #16183: Weblate cannot update some database schemes when upgrading added

#7 Updated by intrigeri 2019-09-13 11:56:30

  • Description updated

#8 Updated by hefee 2019-12-12 16:12:52

  • Status changed from Confirmed to Resolved

for upgrading to 3.0.1

As root:

  • fill database with backup state
  • disable puppet, so puppet won’t override the next changes

Puppet:
* update templates/weblate/settings.py.erb (diff with upstream)
* upgrade manifests/weblate/python_modules.pp (those that are installed by pip)
* disable cronjobs in puppet code
* disable apache in puppet code
* Bump version number in puppet code
* Deploy puppet.

As weblate:

  • disable AUTH_USER_MODEL on settings.py
  • python3 ./manage.py migrate weblate_auth 0001
  • enable AUTH_USER_MODEL on settings.py again
  • python3 ./manage.py migrate # run rest of migration - takes a looong time ;D
  • (save a dump of the migrated db.)
  • python3 ./manage.py collectstatic —noinput #3. Collect updated static files
  • python3 ./manage.py setuplang #4. Update language definitions (this is not necessary, but heavily recommended):
  • python3 ./manage.py setupgroups #5. Optionally upgrade default set of privileges definitions — https://docs.weblate.org/en/latest/admin/management.html#django-admin-setupgroups (might cause trouble in current setup, let’s do later if needed.
  • enable puppet
  • Start apache
  • test a little bit the permissions on Weblate
  • fix permission
  • stop Apache
  • dump database

upgrade to 3.1

Puppet:
* update templates/weblate/settings.py.erb (diff with upstream)
* upgrade manifests/weblate/python_modules.pp (those that are installed by pip)

following the [Generic upgrade instructions](https://docs.weblate.org/en/weblate-3.9.1/admin/upgrade.html#generic-upgrade-instructions)
(step 2-4)
* step 1 is done via puppet
* do not execute step 5, as we don’t want to break our permission model
* don’t execute step 6, as we down install Weblate via git

upgrade to 3.2.2

  • same as upgrade to 3.1

upgrade to 3.5.1

  • same as upgrade to 3.1
  • give back users Reviewer status via view the SQL dump and creating an insert statement.

#9 Updated by sajolida 2019-12-16 16:06:39