maybe I am not clear it with the working of search-server. But my final aim is to update the search-server with latest musicbrainz-db data. Please correct me if am wrong
2017-05-11 13104, 2017
_abhish
I tried official documentation for this but didn't found any updated solution for search-server update
2017-05-11 13110, 2017
_abhish
I tried official documentation for this but didn't found any updated solution for search-server index update
2017-05-11 13116, 2017
jwf joined the channel
2017-05-11 13143, 2017
arbenina has quit
2017-05-11 13118, 2017
github joined the channel
2017-05-11 13118, 2017
github
[picard] samj1912 opened pull request #727: Add new icons (master...new-icons) https://git.io/v9DQL
2017-05-11 13118, 2017
github has left the channel
2017-05-11 13128, 2017
samj1912
phew done :P
2017-05-11 13131, 2017
samj1912
made 50 new icons :D
2017-05-11 13105, 2017
agentsim joined the channel
2017-05-11 13109, 2017
Slurpee joined the channel
2017-05-11 13109, 2017
Slurpee has quit
2017-05-11 13109, 2017
Slurpee joined the channel
2017-05-11 13146, 2017
LordSputnik has quit
2017-05-11 13102, 2017
LordSputnik joined the channel
2017-05-11 13158, 2017
sampsyo has quit
2017-05-11 13157, 2017
zas
\o/
2017-05-11 13141, 2017
samj1912
zas: picard should look fabulous on high res displays after the merging of the latest 2 PRs :D
_abhish: we don't have freeDB as part of the search server anymore
2017-05-11 13135, 2017
reosarevok
So you can ignore that index
2017-05-11 13128, 2017
discopatrick has quit
2017-05-11 13143, 2017
discopatrick joined the channel
2017-05-11 13150, 2017
_abhish
<reosarevok> Thanks a lot, Please do me one more favour, I used metabrainz https://github.com/metabrainz/search-server to configure the search-server and in this, they have used freedb to setup the search server. Please let me how to setup the search-server?
2017-05-11 13105, 2017
reosarevok
I would expect you can just ignore the part about freedb, but I haven't tried this myself
2017-05-11 13136, 2017
github joined the channel
2017-05-11 13136, 2017
github
[picard] zas closed pull request #726: High-DPI support for Cover art pixmaps (master...high-dpi) https://git.io/v9Dsn
but it's unclear exactly what instructions you are following.
2017-05-11 13112, 2017
_abhish
Sorry
2017-05-11 13114, 2017
technexo_ has quit
2017-05-11 13119, 2017
alastairp
ruaok said
2017-05-11 13119, 2017
alastairp
2:47 PM <ruaok> that update indexes from replication stream code, never worked right. we abandoned it and it is not supported.
2017-05-11 13139, 2017
alastairp
in the output you just pasted, you run this command:
2017-05-11 13146, 2017
zas
samj1912: i'll merge the icons PR, so everyone can test in next builds with full hdpi support, we'll modify some prolly (i'm not fond of the cluster one for example).
zas, I always read "fix version" as the version that bug's going to be fixed in, so 2.0 seems fine
2017-05-11 13130, 2017
zas
ok, does it mean it makes no sense to have "unreleased versions" ?
2017-05-11 13145, 2017
Mineo
samj1912, I'm not sure if the license allows crediting a bunch of authors at once or requires explicitly mentioning which icon was made by whom
2017-05-11 13104, 2017
samj1912
I have the other list too
2017-05-11 13115, 2017
samj1912
but then that will be a lot of icons
2017-05-11 13123, 2017
samj1912
48 of them
2017-05-11 13148, 2017
Mineo
zas, I'm not sure why it would make no sense? "this bug will be fixed in the still unreleased version 2.0" makes sense to me
2017-05-11 13119, 2017
zas
i meant those *dev* versions
2017-05-11 13123, 2017
Mineo
ah
2017-05-11 13142, 2017
zas
because this is misleading imho
2017-05-11 13159, 2017
Mineo
well, this is not the first time I've asked about them, so it should be no surprise that I agree that they don't make much sense :)
2017-05-11 13132, 2017
zas
also Affects is always bothering me, a bug is supposed to affect one version, but not to be fixed in the same one
2017-05-11 13148, 2017
Mineo
samj1912, I only know that only having the names mentioned is probably not ok, everything else is legalese to me :)
2017-05-11 13110, 2017
samj1912
I will add the links to the authors
2017-05-11 13121, 2017
Mineo
zas, the obvious way out of that situation would be not introducing bugs during development :P
2017-05-11 13127, 2017
zas
ahah
2017-05-11 13131, 2017
zas
well, we do ;)
2017-05-11 13156, 2017
bitmap
samj1912: the icons looks very pixelated on my screen (probably a bug, they look great otherwise)
2017-05-11 13110, 2017
samj1912
bitmap: can I have a screenshot?
2017-05-11 13128, 2017
zas
example: 1.4 is released, we start to work on 1.4.1, introduce a bug, reported in jira as affecting 1.4 (wrong), 1.4.1 (wrong too), fixed before 1.4.1 release (so shouldn't appear in 1.4 to 1.4.1 release)... what is the correct way to handle that ?
