Hi everyone! I’m CatQuest, the Endeavouring MusicBrainz Instrument Inserter. I’ve been meaning to write a post or two about this for a while, but now finally everything is in order!
As some of you may know, I have “officially” taken over instrument additions from reosarevok. I suggested this way back in June 2016 because a) reo was already overworked enough between doing Style, handling support, dealing with social media, and other things, and b) as a consequence of this, the Instrument Requests queue had grown unmanageably large.
Initially I started without grouping, components, or “fix versions”, but later I’ve been allowed to organise everything to my liking and so, I’ve gone back and retroactively added tickets for initial batches, modelled on freso’s ORG tickets.
So without further ado: Here is a list of the instrument tickets I solved from my initiate appointment in July 2016 to roughly October:
Very first batch:
It felt natural to separate this at Pipe and Tabor, so the next batch got a different “fix” version, from October to (taking a Christmas break) January 2017:
Stay tuned for part two!
We’re happy to announce the release of our May 2017 schema change today! Thanks to all who were patient during today’s downtime as we released everything to our production servers.
This is a fairly minor release as far as schema changes go, but please do report any issues that you come across.
Currently, the only visible change for editors is the ability to add multiple lyrics languages to works. We’ve also modified the schema to support dynamic attributes for entities other than works, but the UI for that won’t be complete for another release or two.
Now, on to the instructions.
Schema Change Upgrade Instructions
Note: Importing the latest data dump is always a valid alternative to running
./upgrade.sh on an existing database, if you’d prefer to also get new data in one go. Just follow the relevant instructions in INSTALL.md. The rest of the instructions here assume an in-place upgrade.
- Make sure
DB_SCHEMA_SEQUENCE is set to 23 in
- If you’re using the live data feed (your
REPLICATION_TYPE is set to
RT_SLAVE), ensure you’ve replicated up to the most recent replication packet available with the old schema. If you’re not sure, run
./admin/replication/LoadReplicationChanges and see what it tells you; if you’re ready to upgrade, it should say “This replication packet matches schema sequence #24, but the database is currently at #23.”
- Take down the web server running MusicBrainz, if you’re running a web server.
- Turn off cron jobs if you’re automatically updating the database via cron jobs.
- Switch to the new code with
git fetch origin followed by
git checkout v-2017-05-15-schema-change.
cpanm --installdeps --notest . (note the dot at the end) to ensure your perl-based dependencies are up to date.
- Downgrade DBD::Pg by running
cpanm TURNSTEP/DBD-Pg-3.5.3.tar.gz (version 3.6.0 breaks things currently).
./upgrade.sh (it may take a while to vacuum at the end).
DB_SCHEMA_SEQUENCE to 24 in
lib/DBDefs.pm as instructed by the output of
- Turn cron jobs back on, if applicable.
- Restart the MusicBrainz web server, if applicable. It’s also recommended you restart redis. If you’re accessing your MusicBrainz server in a web browser, run
npm install followed by
For those curious, here’s the list of resolved tickets (excluding MBS-8393):
- [MBS-9271] – Prevent usernames from being reused
- [MBS-9273] – Fix the a_ins_edit_note function in older setups to not populate edit_note_recipient for own notes
- [MBS-9274] – Fix the edit_note_idx_post_time_edit index in older setups to handle NULL post_time
- [MBS-5452] – Support multiple lyric language values for works
We’re going to start our schema change release process today at 17h UTC.
We anticipate having a short downtime of a few minutes as we”ll need to restart our database server. As usual, we’re not certain when we will start the downtime, but we’ll keep people posted about our progress in IRC and on Twitter.
Once we’re done with the release we will post instructions on this blog on how to upgrade any replicated instances of MusicBrainz you might be running.
Sambhav’s GSoC project is all about Picard 2.0, and among progress made the devel version is now installable via PyPi: https://pypi.python.org/pypi/picard_dev
To install the dev builds you need to have a Python 3.5 or greater. At the moment it is mainly a port of 1.4.x to Python 3 and Qt5, with support for HiDPI and new icons !
Please note that Picard Dev version uses a different config file than your stable Picard installation. As such the settings and plugins will be on their default configuration.
To use your stable config with the dev version, simple copy your “Picard.ini” file from your MusicBrainz user folder to “Picard Dev.ini” which can be found in the same folder.
Since testers may want to run a stable 1.4.x version along the 2.0 dev one, the executable is named “picard_dev”.
Of course, we encourage people to test this version on every platform they can, and report any issue.
Thanks to Sambhav
for the fantastic job he did on this ! And stay tuned, more to come !
Official MusicBrainz cross-platform music tagger Picard 1.4.2 is now out.
This is mainly a bugfix release, the only notable improvement is related to TOPE/TOAL tags.
Users can get Windows and MacOSx packages from Picard website downloads section.
- [PICARD-1053] – Picard does not stop analyzer while moving
- [PICARD-1055] – picard hangs with: RuntimeError: maximum recursion depth exceeded in cmp
- [PICARD-1070] – The “Convert Unicode punctuation characters to ASCII” function only works in certain tags
- [PICARD-1077] – ID3v2.4 text encoding settings are not saved correctly
- [PICARD-969] – Search dialog webservices get queued behind matched album requests
- [PICARD-1034] – Picard not seeing TOPE and TOAL
Oh boy, oh boy. It’s been a while. Again. Huh? Well, now we’re back! Really! And so, so much has happened in the last while that we’re in for quite a ride here. So strap in!
Continue reading “Community Recap Q1 2017”