We need to do essential maintainance on the main MusicBrainz database server today (specifically upgrading to Ubuntu 12.04 LTS). We’re aiming to get this work completed within an hour, and will require MusicBrainz to be in read-only mode for the duration of the upgrade. We’re going to go read-only from 2PM UTC (6AM PST, 9AM EST, 3PM CEST) to begin this work.
We’ve been informed that some people have noticed their MusicBrainz slave servers have stopped applying replication packets. We’ve tracked the problem down and now have a fix for this problem.
How Do I Tell If I’m Affected?
To determine if you are affected, connect to the MusicBrainz PostgreSQL database (we recommend using ./admin/psql from your musicbrainz-server checkout) and run the following:
SELECT now() - last_replication_date FROM replication_control;
If you see a date that is larger than a few days, there’s a good chance you are affected by this bug and should upgrade.
How Do I Fix This?
Fixing this is easy, you simply need to update your Git checkout. We suggest the following:
cd musicbrainz-server
git fetch --tags origin
git checkout v-2013-10-14-replication-fix-2
EDIT: formerly used a different (broken) tag and recommended a different method of fetching tags.
When replication next runs, the data that cannot be applied will be rewritten and replication will continue as normal.
With the schema change well past us, we’re finally back into normal development mode. This release contains more bug fixes to new features from the schema change, as well as an assortment of improvements and general bug fixes to the rest of the site. Many thanks to Nicolás Tamargo and the MusicBrainz team for their work on this release. Here’s what’s changed:
Bug
[MBS-5439] – ISE: Adding a release with a track of 0 length
[MBS-5658] – Various Artists used for track artists when adding release via disc ID lookup
[MBS-5926] – Collection names are shown for subscribed private collections
We’ve just finished rolling out the fall schema change release. Apart from the /place/create endpoint failing, the site is back up in full read-write mode now.
Read on for the changes in this release — our next blog post will give instructions on how to upgrade your instances of MusicBrainz.
Thanks to everyone who worked on this release!
Bug
[MBS-2301] – Attach TOC to new release – TOC/DiscId is lost when based on existing release/tracklist
With the MusicBrainz summit happening just this weekend, and most work continuing on the upcoming schema change release – this server update is a tad on the light side! However, we do at least have something to show. Thanks to nikki for the main change in this release:
Bug
[MBS-6735] – ProcessReplicationChanges breaks with update packages that cross the limit boundary
New Feature
[MBS-5789] – Make links for HTTPS enabled sites use schema independent links
Over the weekend, 17 MusicBrainz fanatics got together at WikiMedia’s German headquarters to discuss the immediate future of MusicBrainz. And in short – we had a blast! A tremendous amount of topics were covered, and we feel this was one of the most productive summits we’ve had so far. From genres to acoustic properties, to internationalization, to artist & label artwork, an incredible amount was discussed.
From left to right: ijabz, CatCat, ianmcorvidae, reosarevok, ruaok, navap, santiissopasse, Anders Arpteg (Spotify), LordSputnik, ocharles, warp, fractalizator, Freso, Mineo, kepstin, JonnyJD
A summary of all topics covered and points discussed can be found on the wiki, with thanks to diligent note taking by everyone who attended. As you’ll see, a lot of topics are now actionable, so hopefully work will begin to move forward with these. While it remains unclear what the solution is to some topics, the constructive conversations around them is helping us slowly move forward in the right direction.
Of course, it wouldn’t be a MusicBrainz summit if it was work work work – there was plenty of mayhem and play too! On Saturday we had our summit meal at Max & Moritz – complete with a police escort due to some unfortunately timed protests. A novel twist for a group meal… yet oddly consistent with the fresh and unpredictable nature of MusicBrainz.
ruaok takes a hard earned break… on Freso!
We also want to thank our sponsors who made the summit possible. Thank you to Spotify and Google’s Open Source Programs Office! Your support paid for some airfares, our lodging, summit meals and a large pile U-Bahn tickets. And of course, a big thanks also goes to Wikimedia Germany and in particular to Lydia Pintscher for baby-sitting us all weekend and also for making awesome introductions to other people to help with specific summit topics.
Thanks again to everyone who attended. Until next year!
Hello all. We’ve just pushed out another small little update to MusicBrainz. This release is small while we continue to focus on getting the upcoming schema change ready, so there are a handful of bug fixes and improvements. Thanks to Frederik “Freso” S. Olesen, Michael Wiencek and the rest of the MusicBrainz team for their work on this release. Here’s what’s changed:
Bug
[MBS-2521] – Setting fields via query parameters blanks all default values (including auto-editor checkbox)
[MBS-6163] – Following INSTALL does not result in a runnable server
We have a tiny release to kick off September, as we’ve been focusing quite heavily on tightening up the reliability and ease-of-maintenance of the servers themselves. However, we still have a few important bug fixes to release. Here’s what’s changed:
Bug
[MBS-4730] – Sort names for artist search hint aliases are displayed, but cannot be edited.
[MBS-6218] – When a Person with a gender is merged into a Group, ModBot ISEs.
[MBS-6561] – End column empty in search results for ended artists with no end date
[MBS-6635] – Several reports not updated since May 15
[MBS-6690] – JSON web service ISE with inc=aliases
[MBS-6698] – Wiki excerpts truncated by mid-sentence initials (eg, of names) that are mistaken for periods ending a sentence.
It’s a new month, which means it’s time for a a new release of MusicBrainz! This week we’re releasing a new version of the Cover Art Archive uploader, which now lets you upload multiple files at once, and also supports more file formats (including PNG and GIF):
Along with this, we’ve also solved a good selection of bugs, and have added a few little improvements along the way too. With help from Nicolás Tamargo and the rest of the MusicBrainz team, here’s what we’ve done in the last fortnight:
Bug
[MBS-4669] – Webservice returns an ASIN that was added in a voted down edit
[MBS-4981] – Cover art in sidebar links to CAA /front when no front is available
[MBS-5625] – Date display problem in edit listings
[MBS-6148] – Adding a disc ID automatically fills in durations without creating an edit
[MBS-6262] – Release events section of the release editor is all over the place
[MBS-6395] – medium_index not updating on medium inserts
We’ve just finished deploying the second update to musicbrainz.org for July. Continuing the trend, this release is primarily bug fixes with a few new improvements. Notably, people should be happy to hear that the Cover Art Archive now supports PNGs and GIFs, ISRC editing has become easier, and the release and relationship editors should be a little bit more stable. Many thanks to Nicolás Tamargo along with the MusicBrainz team for their continued work on MusicBrainz. Here’s what’s changed:
Bug
[MBS-3132] – Problems with track artist credits when seeding the release editor
[MBS-5310] – Artist aliases should not be shown for work relations when doing a release lookup
[MBS-5409] – Internal server error when artist begin year is 0
[MBS-5637] – Regression: Recording merges can result in duplicate relationships
[MBS-6058] – Artist Subscriptions overview page is contradicting itself
[MBS-6194] – regression : drums release relationships were invisible as long as there was at least one recording drums relationship
[MBS-6235] – Internal server error when using date of birth without century in profile
[MBS-6273] – Country names are no longer shown in the sidebar or in edits
[MBS-6275] – Diffs no longer work for release dates
[MBS-6276] – Release dates are badly aligned in edits
[MBS-6280] – Registering an account ignores DB_READ_ONLY
[MBS-6282] – Uploading cover art ignores DB_READ_ONLY