Feature #15308

Cannot update database schemes in translate.lizard

Added by emmapeel 2018-02-13 11:54:38 . Updated 2019-06-27 17:16:31 .

Target version:
Start date:
Due date:
% Done:


Feature Branch:
Type of work:

Affected tool:
Deliverable for:


We need to allow the user weblate to write new migration fixtures to


In order to create such fixtures and allow the updating of the database.

This is needed before the SponsorL work starts.



#1 Updated by emmapeel 2018-03-06 18:13:03

  • Target version changed from Tails_3.6 to Tails_3.7

#2 Updated by Anonymous 2018-03-13 14:37:29

  • Assignee set to emmapeel
  • QA Check set to Info Needed
  • Deliverable for set to Sponsor_L

emmapeel, can you please confirm that this is needed only to update the current weblate version to a newer one? It’s not needed for pulling and adding components, correct?

#3 Updated by emmapeel 2018-04-03 09:26:05

  • Assignee changed from emmapeel to groente
  • QA Check changed from Info Needed to Dev Needed

This is needed even to finish the installation we have atm.

It will not prevent components to work but it generates problems with for example the glossary and the statistics.

#4 Updated by groente 2018-04-13 13:51:14

  • Assignee changed from groente to emmapeel
  • QA Check changed from Dev Needed to Info Needed

to what degree does it specifically need to be user weblate who has write permission here? i can chown the directory, but i’m a bit uncomfortable with giving a web-application write access to its own code. can you think of a solution to create these fixtures as a different user?

#5 Updated by emmapeel 2018-04-14 06:48:28

  • Assignee changed from emmapeel to groente
  • QA Check changed from Info Needed to Dev Needed

It will only be needed to update the database scheme because of changes on the code.

It can be taken out after finishing the update.

It will create some xml files and add/rm some columns on the database.

It would be good to do it first to finish current install, and then after we upgrade again.

The commands we need to run from /usr/local/share/weblate/ are:

- sudo -u weblate ./manage.py makemigrations /* this one creates the needed features

- sudo -u weblate ./manage.py migrate /* this one actually alters the database

Then we can remove the permission again.

#6 Updated by groente 2018-04-14 09:14:56

  • Assignee changed from groente to emmapeel

ok, the directory and its contents have been chown’ed, please let me know when the install/updates are done and i’ll revert this.

#7 Updated by emmapeel 2018-04-16 08:16:39

  • Assignee changed from emmapeel to groente

OK, I did one migration (the trans app), but now it wants to write to:


also (the accounts app, to: “- Alter field language on profile”)

#8 Updated by groente 2018-04-16 11:10:04

  • Assignee changed from groente to emmapeel

ok, that directory has also been chown’ed, let me know when you’re done with it!

#9 Updated by emmapeel 2018-04-16 13:28:04

  • Assignee changed from emmapeel to groente

Great! So, the migration for 2.10 is complete, we will need to do it again for 2.19. But you can remove the permissions for now.

#10 Updated by bertagaz 2018-05-10 11:09:04

  • Target version changed from Tails_3.7 to Tails_3.8

#11 Updated by intrigeri 2018-06-26 16:27:40

  • Target version changed from Tails_3.8 to Tails_3.9

#12 Updated by groente 2018-06-30 20:08:26

  • Status changed from Confirmed to Resolved
  • Assignee changed from groente to emmapeel

since the coming upgrade will be a project on its own anyway and these steps should then be handled by puppet, i’m going to close this ticket.

#13 Updated by intrigeri 2019-06-27 17:16:31

  • Assignee deleted (emmapeel)