Tails

#1 Updated by emmapeel 2018-12-03 10:24:40

• Assignee set to groente

#2 Updated by emmapeel 2018-12-03 10:25:35

• Description updated

#3 Updated by groente 2018-12-03 12:32:55

• Assignee changed from groente to emmapeel

well, i don’t see any failures, even when running migrate with -v3 —traceback.

what i do see is that the migate command adds an entry to the django_migrations table.

running the thing in strace, i don’t even see it trying to make any changes to the database structure. All that is sent to the mysql server is the INSERT into the django_migrations table and a whole lot of SELECT’s, but no ALTER or UPDATE or anything else I’d expect from an attempt to make the needed adjustments you mentioned.

i’m afraid i can’t help you any further on this one, i’m inclined to think there’s something wrong with the internal logic of manage.py.

#4 Updated by intrigeri 2019-08-01 15:50:01

• Status changed from Confirmed to Rejected

We’ve seen no such problem last time we upgraded Weblate (late June). Let’s reopen this (currently not actionable) ticket if we see this problem again!

#5 Updated by hefee 2019-08-22 12:41:56

• Status changed from Rejected to Confirmed
• Assignee deleted (emmapeel)

The migration is about available checks. I expect, that some typo or anything in that list, that is not correct, but somehow the migration checks this incorrectly.

<code class="python">
class Migration(migrations.Migration):

    dependencies = [
        ('trans', '0162_auto_20190627_1801'),
    ]

    operations = [
        migrations.AlterField(
            model_name='check',
            name='check',
            field=models.CharField(choices=[('begin_space', 'Starting spaces'), ('ellipsis', 'Ellipsis'), ('end_newline', 'Trailing newline'), ('end_ellipsis', 'Trailing ellipsis'), ('zero-width-space', 'Zero-width space'), ('perl_format', 'Perl format'), ('javascript_format', 'Javascript format'), ('end_space', 'Trailing space'), ('begin_newline', 'Starting newline'), ('xml-invalid', 'Invalid XML markup'), ('multiple_failures', 'Multiple failing checks'), ('escaped_newline', 'Mismatched \\n'), ('end_exclamation', 'Trailing exclamation'), ('php_format', 'PHP format'), ('translated', 'Has been translated'), ('end_semicolon', 'Trailing semicolon'), ('end_colon', 'Trailing colon'), ('bbcode', 'Mismatched BBcode'), ('optional_plural', 'Optional plural'), ('end_question', 'Trailing question'), ('max-length', 'Maximum length of translation'), ('python_brace_format', 'Python brace format'), ('c_format', 'C format'), ('same-plurals', 'Same plurals'), ('plurals', 'Missing plurals'), ('end_stop', 'Trailing stop'), ('xml-tags', 'XML tags mismatch'), ('python_format', 'Python format'), ('inconsistent', 'Inconsistent')], max_length=50),
        ),
    ]

</code>

#7 Updated by intrigeri 2019-09-13 10:08:54

• related to Bug #16943: Upgrade to Weblate 3.x added

#8 Updated by Anonymous 2019-09-13 10:09:02

• Subject changed from weblate cannot update the database schemas to Weblate cannot update some database schemes when upgrading

#10 Updated by hefee 2019-12-12 16:25:08

• Status changed from Confirmed to Resolved

We had issues when we upgrade to 3.0.1 (Bug #16943), because a lot of created migrations scripts were added under `weblate/*/migration/*py`, that made the update to 3.0.1 impossible. That’s why we deleted the non committed files.

This also is in line with what we found, how to do a upgrade. On an upgrade you should not need to run `python3 ./manage.py makemigrations`. Maybe it was needed in earlier Weblate versions, but at least for the 3.X ones, you don’t need to run them anymore.

And we also see no failing migration anymore.