I mean, I'm a DBA, I understand that there are many more relationships between things than things.
but it's still sad :/
nikki
adding a release is a lot of work for relatively few edits, adding the same conductor and orchestra to every track of a classical release is a whole bunch of edits in a minute
(well, "lot of work" depends of course, with a decent importer you can fill out a lot of stuff, but it still can't match the numbers you get from adding relationships)
(not that having nicer stats is a particularly good reason to implement that XD)
drsaunde joined the channel
royale1223 joined the channel
_5moufl joined the channel
xandora joined the channel
xandora
Got an album here that has 2 bonus tracks that are only on the CD if you bought it from Target. Should I label the tracks with (Target Exclusive)? Is there a common style guide for that?
simukis_ joined the channel
legoktm_ joined the channel
njh_ joined the channel
MissDee
xandora: that's what I;d do
erm, actually, a new release
Tyklol joined the channel
with a disambig comment
mb-chat-logger joined the channel
is it will be a different tracklist and disc id
xandora
Yea, I created a new release, added the extra tracks and added the disambig.
njh joined the channel
legoktm joined the channel
MissDee
woo :)
igndenok joined the channel
Draven__ joined the channel
Draven__
What's the best way to automatically update my musicbrainz-server files (not database, I have slave.sh running hourly) from git?
MJ joined the channel
I assume I should just make a cronjob to do a 'git pull' but I want to make sure I won't break anything
reosarevok joined the channel
ruaok joined the channel
drsaunde joined the channel
MJ joined the channel
Gues_____ joined the channel
xandora|mac joined the channel
xandora|mac
Is there a way to preview what your edits would look like before you commit them?
nikki
other than in the release editor, no
xandora|mac
So for things like release group merges, you just have to either know how it's going to turn out or find out after it happens?
nikki
yes :(
xandora|mac
…exciting!
nikki
for merging we really need something which gives us more control over what happens, but there's also a zillion other things we need >_<
you should get a release group with both releases in it credited to the artist with "as" lowercased (since it prefers the data on the target release group)
xandora|mac
Ahh, I didn't even see the 'As' or 'as'. No wonder they didn't end up in the same group. DERP.
nikki
they'll only end up in the same group if you actually tell it to use the same group
xandora|mac
Yea, I was wondering why it didn't tell me there was a duplicate release. Should've noticed something was up.
v6lur joined the channel
kepstin-laptop joined the channel
jcazevedo joined the channel
kepstin-laptop joined the channel
Draven__
What's the best way to automatically update my musicbrainz-server files (not database, I have slave.sh running hourly) from git? I assume I should just make a cronjob to do a 'git pull' but I want to make sure I won't break anything.
daveh
anything persistent won't change until you restart
nikki
making it automatically update is likely to break something at some point
what are you trying to achieve by updating the code automatically anyway?
daveh
nikki - like what?
kepstin-laptop
perl deps change and need reinstallation, the server needs restarting, dbdefs needs manual updating...
daveh
catalyst wil be fine, it's persistent. jsut restart at the end.
nikki
it always restarts when the files change for me, so I imagine the setup other people are using will do the same
(since I didn't go out of my way to make it do that)
daveh
oh, plackup -r
yeah
that's not really a production switch
kepstin-laptop
well, if you're autoupdating, it's obviously not a production setup ;)
What's the best way to update my musicbrainz-server files (not database, I have slave.sh on cron) from GitHub? Do I just make a cron to run 'git pull'?
daveh
you should have been here earlier today :)
reosarevok
Draven__: #musicbrainz-devel
kepstin-laptop
Draven__: the best way is to follow the blog, read the release notes for each new version, then manually check out the appropriate tag and follow any required upgrade instructions :)
reosarevok
Might be a better place
Draven__
I was. Got d/c'd.
reosarevok
Ok, I guess no need :)
Draven__
Alright. I do follow the blog, was hoping somebody knew an automated way. No problems. Thank you.
Jozo
http://pastebin.com/AHNmaNJP - What release countries we should use? (WordWide or should we list all countries?)
reosarevok
Heh
Technically, all countries. Although that looks terrible, so dunno. I'd just put one and say "fuck it" but if you feel like adding all of them that should be fine too I guess?
Jozo
I usually use just one or two... but many other uses 'WorldWide'
if a live version of a track is listed under a different name because it has a different arrangement, the recording is still just a "live" version of the work?