@i @PurpCat @lina @Lunarised @p @Cocoa @lunarised There's quite a few divergences, but less than in ackoma and nothing critical like password hash changes. Some new fields in users table might be troublesome, though.
$ diff -uar <(ls -1 rebased/priv/repo/migrations) <(ls -1 pleroma/priv/repo/migrations) --- /proc/self/fd/11 2024-07-04 17:10:27.018383357 +0300 +++ /proc/self/fd/12 2024-07-04 17:10:27.019383356 +0300 @@ -274,7 +274,6 @@ 20210401143153_user_notification_settings_fix.exs 20210416051708_remove_mastofe_settings_from_users.exs 20210420204354_delete_hashtags_objects_cascade.exs -20210612185407_add_email_list_field_to_users.exs 20210717000000_add_poll_to_notifications_enum.exs 20210818023112_add_user_id_to_apps.exs 20211121000000_create_user_notes.exs @@ -287,10 +286,8 @@ 20220125104429_add_birthday_month_day_index_to_users.exs 20220203224011_create_rules.exs 20220220135625_upload_filter_exiftool_to_exiftool_strip_location.exs -20220225164000_add_activity_assigned_account_index.exs 20220302013920_add_language_to_users.exs 20220308012601_create_announcements.exs -20220314220000_add_location_to_users.exs 20220319000000_add_status_to_notifications_enum.exs 20220506175506_add_index_hotspots.exs 20220509180452_change_thread_visibility_to_be_local_only_aware.exs @@ -298,21 +295,23 @@ 20220602052233_change_report_notes_content_to_text.exs 20220605185734_add_update_to_notifications_enum.exs 20220616163503_add_expires_at_to_user_relationships.exs -20220624104914_create_webhooks.exs 20220711182322_add_associated_object_id_function.exs 20220711192750_switch_to_associated_object_id_index.exs 20220807125023_data_migration_delete_context_objects.exs -20220819171321_add_pleroma_participation_accepted_to_notifications_enum.exs 20220821004840_change_thread_visibility_to_use_new_object_id_index.exs 20220905011454_generate_unset_user_keys.exs -20220927220033_add_last_move_at_to_users.exs -20221029171353_add_internal_to_webhooks.exs 20221103014611_create_oban_peers.exs 20221103014728_swap_primary_oban_indexes.exs 20221111164213_deprecate_quack.exs -20221207235104_add_events_index.exs 20221216052127_add_state_to_backups.exs 20230306112859_instances_add_metadata.exs 20230422154018_drop_unused_indexes.exs 20230504173400_remove_user_ap_enabled.exs 20231107200724_consolidate_email_queues.exs +20240207035927_create_rich_media_card.exs +20240223165000_create_bookmark_folders.exs +20240406000000_add_hint_to_rules.exs +20240527144418_oban_queues_refactor.exs +20240530011739_add_missing_foreign_keys.exs +20240608003957_upgrade_oban_jobs_to_v12.exs +20240619141319_deprecate_config_db_logger.exsConversation
Notices
-
(mint@ryona.agency)'s status on Thursday, 04-Jul-2024 23:14:41 JST -
Cocoa Hoto in real life (cocoa@nekosat.work)'s status on Friday, 05-Jul-2024 00:23:41 JST Cocoa Hoto in real life @mint @PurpCat @i @lina @Lunarised @p @lunarised I imagine reverting all Soapbox migrations and running the stock Pleroma migrations would fix that? I rarely mess with the database so I wouldn't know exactly how to do that, but I'm sure it's possible -
(mint@ryona.agency)'s status on Friday, 05-Jul-2024 00:23:41 JST @Cocoa @PurpCat @i @lina @Lunarised @p @lunarised It should, yes. I don't remember what exact commad one needs to run to revert a single migration, though.
-