we can try to upgrade docker on this machine, i had such issue on another machine a while ago, with this docker version
2018-12-04 33825, 2018
yvanzo
(only docker rm -f actually stopped the container)
2018-12-04 33801, 2018
zas
i'll proceed to an upgrade on it, it has to be done on all machines anyway, there is no critical container on this one.
2018-12-04 33821, 2018
yvanzo
Ok, I’m done with updating mb containers on every machine.
2018-12-04 33833, 2018
zas
i upgraded to version 18.06.1~ce~3-0~ubuntu (18.09 doesn't work, there are issues with systemd i need to look into, we already met this issue, so i stick version to 18.06)
2018-12-04 33825, 2018
zas
i'll reboot bootsy soon
2018-12-04 33826, 2018
zas
yvanzo: done with bootsy
2018-12-04 33830, 2018
yvanzo
thanks!
2018-12-04 33821, 2018
outsidecontext
zas: hi, what do you think about how to proceed with the picard beta release?
2018-12-04 33843, 2018
outsidecontext
I am unfortunately pretty loaded with work today and tomorrow :(
2018-12-04 33827, 2018
D4RK-PH0ENiX has quit
2018-12-04 33825, 2018
zas
We can tag beta, and I'll write a blog post about it to start with
2018-12-04 33821, 2018
zas
We need more people to test, and let some time for translators to work
2018-12-04 33840, 2018
D4RK-PH0ENiX joined the channel
2018-12-04 33803, 2018
yvanzo
george: you may need --force option to push updated commit message.
2018-12-04 33842, 2018
travis-ci joined the channel
2018-12-04 33843, 2018
travis-ci
metabrainz/picard#4143 (master - 1e8119f : Laurent Monin): The build passed.
Yes, I have been thinking about this as well. I was not sure if we should merge it now or only after final release, but probably it is good to have this online to point users to it
2018-12-04 33850, 2018
outsidecontext
The only thing missing there is that I wanted to have the new -P command line parameter documented, but we can do that later
2018-12-04 33851, 2018
ruaok
I love that you want to merge the thing that has the 'do not merge' label.
2018-12-04 33857, 2018
zas
yes, it doesn't make much difference, and users of 2.1.0dev2 will have the proper documentation
2018-12-04 33806, 2018
zas
ruaok: yes :)
2018-12-04 33832, 2018
outsidecontext
ruaok: :D I removed the label
2018-12-04 33837, 2018
zas
fixed ;)
2018-12-04 33843, 2018
ruaok
no fun.
2018-12-04 33800, 2018
outsidecontext
:p
2018-12-04 33820, 2018
zas
i'll merge, then we proceed to required updates (packages + -P option)
2018-12-04 33837, 2018
outsidecontext
ok
2018-12-04 33825, 2018
outsidecontext
zas: We currently don't have the command line options documented, but my thought was that it would be useful to be mentioned on the troubleshooting page
"MusicBrianz Server [Master] Pending — Can't define which status to set"
2018-12-04 33835, 2018
reosarevok
Also, MusicBrianz :D
2018-12-04 33854, 2018
yvanzo
Do you have something against him? ;)
2018-12-04 33817, 2018
yvanzo
Build sometimes fails because of Redis store, it's transient error only.
2018-12-04 33845, 2018
yvanzo
I just pushed a typo fix to master, next build should be fine.
2018-12-04 33826, 2018
reosarevok
Re: "releases which have cover art in the Cover Art Archive" commit message
2018-12-04 33854, 2018
reosarevok
I thought you told me commit messages should be fit in a small amount of characters, yvanzo? :D
2018-12-04 33838, 2018
reosarevok
(that's why I had "Add report for CAA releases with no CAA types", I though more would be too long)
2018-12-04 33816, 2018
reosarevok
Pushed the fix with a nicer commit message then
2018-12-04 33839, 2018
yvanzo
taht's not an excuse to write gibberish, is it? ;)
2018-12-04 33833, 2018
yvanzo
reosarevok: you can wrap it where you want and continue it in the message body
2018-12-04 33838, 2018
reosarevok
Well, sure, but anything that is understandable goes over the limit
2018-12-04 33847, 2018
reosarevok
Pushed it anyway
2018-12-04 33810, 2018
yvanzo
also, the example "releases which have cover art in the Cover Art Archive" is taken from report description, with your own words, it is not a suggestion for commit message :p
2018-12-04 33803, 2018
c1e0 has quit
2018-12-04 33807, 2018
c1e0 joined the channel
2018-12-04 33832, 2018
reosarevok
c1e0: hi! Just answered the task / left a few notes
2018-12-04 33841, 2018
reosarevok
Feel free to ask if you have any doubts! :)
2018-12-04 33819, 2018
c1e0
reosarevok: Thank you. :)
2018-12-04 33825, 2018
george
Does anyone know why syncing my fork with the GitHub MusicBrainz repo might take the Head back to " Adding the first batch of genre requests"?
c1e0: I would not keep that because that audio is a 2:32 sample and we don't have clear credits for it. Is it "Solo: Isao Nakamura"? Probably, but it's not clearly specified that the audio is from that performance
I don't really think that's a good idea tbh. If the system is broken then the system needs fixing, but we shouldn't have a ridiculously long string
2018-12-04 33806, 2018
yvanzo
george: make sure you fetch latest changes from metabrainz repo, then save your branch with git checkout release-label-master-v2 -b don-t-shoot; last try rebasing your branch onto master with git rebase release-label-master-v2 --onto metabrainz/master;
2018-12-04 33831, 2018
yvanzo
reosarevok: I agree, that's what gh:MBS#763 attempts to fix.
