but I can't find that in the current version of the readme
2019-11-26 33012, 2019
bitmap
yvanzo: ^ is 1.21 still needed? if we can just fix the commands to use the correct names instead that'd be a lot less annoying for people using ubuntu 18.04 I think
2019-11-26 33040, 2019
nelgin
I can try 1.17.1 and see.
2019-11-26 33034, 2019
bitmap
if you run into an issue with the names maybe we can find a workaround
2019-11-26 33044, 2019
bitmap
not sure that's a good reason to require people to upgrade at least
2019-11-26 33018, 2019
nelgin
It's at the "setting up" stage
2019-11-26 33029, 2019
nelgin
Unescaped left brace in regex is deprecated, passed through in regex; marked by <-- HERE in m/(?<!\\)\${ <-- HERE ([^}]+)}/ at /usr/sbin/pam_getenv line 78.
2019-11-26 33043, 2019
nelgin
Got a bunch of those after Setting up postgresql
2019-11-26 33009, 2019
nelgin
invoke-rc.d: could not determine current runlevel
2019-11-26 33009, 2019
nelgin
invoke-rc.d: policy-rc.d denied execution of start.
2019-11-26 33012, 2019
nelgin
Some runlevel stuff
2019-11-26 33048, 2019
bitmap
does the whole process abort after those message, or does it keep going? (wondering if they're non-fatal warnings that can be ignored)
2019-11-26 33057, 2019
nelgin
Keep going
2019-11-26 33013, 2019
nelgin
It's building the perl modules now
2019-11-26 33036, 2019
bitmap
ok, maybe they're harmless then. I've seen the rc.d ones before and the regex one looks non-fatal
2019-11-26 33059, 2019
bitmap
(I haven't used musicbrainz-docker before, but I've seen them elsewhere)
2019-11-26 33052, 2019
nelgin
arning about asset size..
2019-11-26 33049, 2019
nelgin
yarn install v1.19.1
2019-11-26 33049, 2019
nelgin
[1/4] Resolving packages...
2019-11-26 33049, 2019
nelgin
[2/4] Fetching packages...
2019-11-26 33049, 2019
nelgin
info fsevents@1.2.7: The platform "linux" is incompatible with this module.
2019-11-26 33049, 2019
nelgin
info "fsevents@1.2.7" is an optional dependency and failed compatibility check. Excluding it from installation.
2019-11-26 33050, 2019
nelgin
info fsevents@1.2.4: The platform "linux" is incompatible with this module.
2019-11-26 33050, 2019
nelgin
info "fsevents@1.2.4" is an optional dependency and failed compatibility check. Excluding it from installation.
2019-11-26 33053, 2019
nelgin
A bit further up I got these
2019-11-26 33051, 2019
nelgin
Creating the database, guess I'll check in tomorrow lol
2019-11-26 33004, 2019
bitmap
heh, okay
2019-11-26 33007, 2019
bitmap
those you can ignore too
2019-11-26 33021, 2019
bitmap
alright, finished the mbs release now
2019-11-26 33027, 2019
nelgin
databas eimported. working on creating indexes
2019-11-26 33052, 2019
adiiiiiiiiiiiiii
sbvkrishna: Hey guys, i got my GitHub account back! It was a random flag done by the GitHub spam control system. Anyways my PR is still up https://github.com/bookbrainz/bookbrainz-site/pul…. Could anyone check into it?
2019-11-26 33035, 2019
adiiiiiiiiiiiiii
Also can i too contribute to the Google Code-In as a mentor ?
2019-11-26 33024, 2019
adiiiiiiiiiiiiii
I was a code-in participant for 2018 and 2017 and have done some task with Musicbrainz and bookbrainz.
2019-11-26 33043, 2019
chaban has quit
2019-11-26 33049, 2019
chaban joined the channel
2019-11-26 33032, 2019
pristine__
iliekcomputers: hi
2019-11-26 33038, 2019
nelgin
Ok, I'm at InitDB.pl succeeded. Let's see what's next.
2019-11-26 33056, 2019
nelgin
Docker is up. Let's see if I can build the search indexes. I'm running on a vm with 2 CPUs and 4GB of memory but I'm using a fixed rather than dynamic disk...so maybe take a day or two :)
2019-11-26 33022, 2019
nelgin
musicbrainz@musicbrainz:~/musicbrainz-docker$ sudo docker-compose exec indexer python -m sir reindex
As an alternative, you can either use COMPOSE_PROJECT_NAME=musicbrainz-docker (and rebuild every image so far) or replace musicbrainz-docker_ with musicbrainzdocker_ in this file.
reosarevok: it is already consistent, with 'any' :)
2019-11-26 33045, 2019
reosarevok
I mean, that to me is like saying "it's already consistent if we turn the rule off"
2019-11-26 33054, 2019
yvanzo
reosarevok: this rule is here to spot common mistakes, 'any' still detects such mistakes.
2019-11-26 33013, 2019
reosarevok
But why would we choose to have our code be less standardised if we can make it more standardised?
2019-11-26 33019, 2019
yvanzo
No, turning the rule off wouldn't detect such error.
2019-11-26 33045, 2019
reosarevok
It feels super weird to me to choose to have one thing that can be done in two ways done in different ways throughout the code
2019-11-26 33015, 2019
nelgin
This is way too complicated for someone who justs wants to get it up and running. I've been doing unix/linux admin for over 30 years and I'm still having problems following along.
2019-11-26 33008, 2019
yvanzo
nelgin: I agree, sorry, it is currently a bit of a mess, due to the ongoing search server migration, plus the schema change.
2019-11-26 33024, 2019
nelgin
So it'll really fail if I try and build/run it with docker-compose 1.17.1 even tho that's the latest that comes with Ubuntu?
2019-11-26 33032, 2019
yvanzo
Yes, not because of features, because it has a bug that is fixed in 1.21.0-rc1 only.
2019-11-26 33053, 2019
yvanzo
Note, it used to work with older versions of docker-compose before it broke stuff.
2019-11-26 33031, 2019
yvanzo
It still is probably less pain than handling dependencies, pg extensions, and all by hand.
2019-11-26 33040, 2019
nelgin
Oh well...
2019-11-26 33000, 2019
nelgin
At least I have the database, I'll just write some perl scripts to extract what I need rather than having the fun api.
2019-11-26 33019, 2019
Nyanko-sensei has quit
2019-11-26 33030, 2019
nelgin
Why not just write it in php and use the latest mysql and be done with it. Everyone has php & mysql
2019-11-26 33050, 2019
nelgin
or mariadb anyway, who the hell uses postgres any more ;)
2019-11-26 33055, 2019
D4RK-PH0ENiX joined the channel
2019-11-26 33007, 2019
reosarevok
Because then we'd have to write PHP
2019-11-26 33026, 2019
reosarevok
(I think that's the answer you'll get from all our devs, not just me :p )
2019-11-26 33029, 2019
reosarevok
And I mean, there's really not that much of a difference between mysql and postgres for just using the data anyway. I suspect it'd be as complicated in mysql/mariadb, it's just a complicated DB with a lot of things going on
2019-11-26 33015, 2019
ruaok
moin!
2019-11-26 33049, 2019
ruaok shudders at the thought of using PHP or even going back to the red hot mess that is mysql
2019-11-26 33015, 2019
bitmap
yvanzo: can't you explicitly set the project name to be without the hyphen though?
2019-11-26 33058, 2019
yvanzo
bitmap: yes but then you would have to set COMPOSE_PROJECT_NAME for recent versions...
2019-11-26 33010, 2019
bitmap
I mean the readme would have to include -p or whatever in all the commands so it'd work in either version
2019-11-26 33039, 2019
yvanzo
...which is probably more pain than installing latest version from dedicated apt repos.
2019-11-26 33054, 2019
bitmap
I don't see how making people to upgrade is less painful tbh, since they're copy/pasting the compose commands from the readme anyway
2019-11-26 33004, 2019
loujine joined the channel
2019-11-26 33000, 2019
bitmap
or we could provide scripts for that
2019-11-26 33045, 2019
yvanzo
Ultimately, there should be a global script indeed.
2019-11-26 33023, 2019
yvanzo
But if we change project name, that would break current users setup on git pull.
