Fix migrations after deleting migration to bookworm

YunoHost · Nov 23, 2024 · 56c101f · 56c101f
1 parent becd8a9
commit 56c101f
Show file tree

Hide file tree

Showing 4 changed files with 0 additions and 320 deletions.
diff --git a/src/migrations/0028_delete_legacy_xmpp_permission.py b/src/migrations/0028_delete_legacy_xmpp_permission.py
diff --git a/src/migrations/0029_postgresql_13_to_15.py b/src/migrations/0029_postgresql_13_to_15.py
diff --git a/src/migrations/0030_rebuild_python_venv_in_bookworm.py b/src/migrations/0030_rebuild_python_venv_in_bookworm.py
diff --git a/src/tools.py b/src/tools.py
@@ -680,15 +680,6 @@ def get_matching_migration(target):
 
         raise YunohostValidationError("migrations_no_such_migration", id=target)
 
-    # Dirty hack to mark the bullseye->bookworm as done ...
-    # it may still be marked as 'pending' if for some reason the migration crashed,
-    # but the admins ran 'apt full-upgrade' to manually finish the migration
-    # ... in which case it won't be magically flagged as 'done' until here
-    migrate_to_bookworm = get_matching_migration("migrate_to_bookworm")
-    if migrate_to_bookworm.state == "pending":
-        migrate_to_bookworm.state = "done"
-        _write_migration_state(migrate_to_bookworm.id, "done")
-
     # auto, skip and force are exclusive options
     if auto + skip + force_rerun > 1:
         raise YunohostValidationError("migrations_exclusive_options")