Schema update scripts out of date?

I’ve been going round in circles for over a day now. There is a very recent (2 days old) schema change and your instructions do not seem to work - I may be missing something though - there doesn’t seem to be a support forum set up for you so I’m asking here and thinking it’s a bug?

e.g.

# python mbslave-sync.py

Downloading https://metabrainz.org/api/musicbrainz/replication-122408.tar.bz2?token=w0pkN3I6xz62eftlOyVU7GtNl2lvxPvZ05luUFhh

Processing /tmp/tmpqd8R90.tar.bz2

Packet was produced at 2019-05-13 18:53:11.818061+00

Traceback (most recent call last):

File "mbslave-sync.py", line 193, in <module>

process_tar(tmp, db, config, ignored_schemas, ignored_tables, schema_seq, replication_seq, hook)

File "mbslave-sync.py", line 136, in process_tar

raise Exception("Mismatched schema sequence, %d (database) vs %d (replication packet)" % (expected_schema_seq, schema_seq))

Exception: Mismatched schema sequence, 24 (database) vs 25 (replication packet)

So I do as per instructions:

root@xyzserver:/opt/mbslave# python ./mbslave-remap-schema.py <sql/updates/schema-change/24.slave.sql | ./mbslave-psql.py

BEGIN

SET

?column?

20160602-mbs-8963.sql

(1 row)

CREATE FUNCTION

DELETE 0

?column?

20170507-mbs-8951.sql

(1 row)

DROP INDEX

CREATE INDEX

?column?

20170327-mbs-9271.sql

(1 row)

ERROR: relation "old_editor_name" already exists

I assume this is because 24.slave.sql needs to be something else (perhaps the 25 schema above which of course doesn’t exist yet)?

Have tried downloading and doing manually according to blogs instructions but that’s more for musicbrainz than mbslave and requires more tools to be installed etc. I can download the new schema tag using and will see where that leads, though I don’t think it’s leading anywhere at present.

git clone https://github.com/metabrainz/musicbrainz-server.git --branch=v-2019-05-13-schema-change

Can you advise? Thanks.

Comments (3)