v-2022-08-25

Update instructions

Please ignore this release and the rest of these instructions if:

• you’re not running a mirror server;
• or you don’t make use of genre or tag data;
• or you’ve already done a full re-import of your database after the schema change release;
• or you've already run the script 20220720-mbs-12508.sh earlier.

This release brings only one patch to the script 20220720-mbs-12508.sh which can be used to fix missing genre and tag data on MusicBrainz mirror server. Indeed, a bug (MBS-12508) in the upgrade script of MusicBrainz Server’s latest schema-change release caused aggregate genre and tag data (if you had imported any) to be deleted.

To restore the genre and tag data, follow these steps:

1. Ensure you’ve replicated up to the most recent replication packet available. If you’re not sure, run:

   sudo bash -c 'docker-compose exec musicbrainz replication.sh &' && \
   sudo docker-compose exec musicbrainz /usr/bin/tail -f mirror.log

   and see what it tells you; if you’re up-to-date, it should say “Replication packet … is not available.”

2. Turn off cron jobs and update your musicbrainz-docker setup (assuming your checked out version of musicbrainz-docker is v-2022-05-17-mbdb27 or later):

   admin/configure rm replication-cron
   git fetch --tags origin && \
   git checkout v-2022-08-25 && \
   sudo docker-compose up --build -d

3. Run:

   sudo docker-compose exec musicbrainz ./admin/sql/updates/20220720-mbs-12508.sh

4. Turn cron jobs back on:

   admin/configure add replication-cron
   sudo docker-compose up -d musicbrainz

You can verify that this process worked by checking that the number of tags in the database is over 200,000:

sudo docker-compose exec musicbrainz bash -c "echo 'SELECT count(*) FROM tag' | ./admin/psql READWRITE"

Only change

• Upgrade MusicBrainz Server to v-2022-08-25-hotfixes (which fixes MBS-12548 only)