rexwilliams1234: there's no such thing as a primary genre, but you can look at which tags are the most popular (sort by artist_tag.count). determining which tags are genres is simply a matter of joining tag.name with genre.name
<bitmap[m]> "rexwilliams1234: there's no such..." <- The primary genre is not a big deal. A count works great. Being a week into this after setting up the server I am most interested in just getting some basics, especially finding the table relationships around artist to genre. For the example of the Beatles ... the musicbrainz website has these genres listed: rock, pop, pop rock, psychedelic pop, merseybeat. Am wanting to
reproduce that. From your comments I figure that I can use the Beatles artist id in the artist_tag table and go to the tag table to identify genre names, using count in the artist_tag table to find the most popular genres. Will look into this and do more homework. Thanks.
minimal has quit
bitmap[m]
<rexwilliams1234[> "The primary genre is not a big..." <- [this query](https://github.com/metabrainz/musicbrainz-server/blob/7cfbd49/lib/MusicBrainz/Server/Data/EntityTag.pm#L59-L65) from the MB server code should help (just the highlighted part is relevant for genres). `$self->tag_table` would be `artist_tag` and `$self->type` would be `artist` in your case
yvanzo: i spent a chunk of this weekend porting the prep chunk of [jira-server-vm](https://github.com/metabrainz/jira-server-vm) to ansible, and the repo for that is over here in [ansible-jira](https://github.com/metabrainz/ansible-jira). i've got the prepare-installation part mostly working, but am running into a bit of trouble with replicating [the rsync
task](https://github.com/metabrainz/jira-server-vm/blob/master/script/mirror_old_jira.sh#L11-L17); if you wouldn't mind having a look at [the corresponding ansible](https://github.com/metabrainz/ansible-jira/blob/main/roles/jira-mirror/tasks/main.yml) and seeing if i might be missing something, i'd appreciate it
that means.... haha badly tagedd music is the work of the (devil/demon)
??
mayhem[m]
zas: did you see the mail from hetzner about the two server updates -- we now have a window given to us. is that workable?
zas[m]
Yes, see MeB Sec channel ;)
mayhem[m]
ha great minds.
zas[m]
We have more time than expected to prepare, but the time window is still large
downtime should be under one hour anyway
mayhem[m]
and we can do this without downtime?
reosarevok[m] joined the channel
reosarevok[m]
bitmap: I get the feeling that we are giving modbot reorder medium errors more often than would make sense when one medium is being added and the existing removed
I see relatively often people getting confused by the modbot note on the relevant edits
Wonder if we are causing these somehow when we shouldn't?
BrainzGit
[listenbrainz-server] 14MonkeyDo merged pull request #3220 (03bootstrap4…ansh/bootstrap4-explore-page): feat: Upgrade Entity, Explore and Modals to Bootstrap 4 https://github.com/metabrainz/listenbrainz-serv...
yvanzo[m] joined the channel
yvanzo[m]
julian45: Thank you for preparing it. These scripts have not been used for years. I will check your repository but I’m not fluent in Ansible. Did you look into these? https://community.atlassian.com/t5/Data-Center-...
krishnacosmic[m] joined the channel
krishnacosmic[m]
Hi @Jasjeet,
I have made some updates to my proposal based on your feedback. Kindly review the updated proposal file:///Users/krishna./Downloads/GSOC%202025%20Proposal%20(6).pdf and share your feedback.
* proposal file:///Users/krishna./Downloads/GSOC%202025%20Proposal%20(6) .pdf and
julian45[m]
<yvanzo[m]> "julian45: Thank you for preparin..." <- i wasn't aware of those, ngl. 🤦 i'll have a look later
<mayhem[m]> "I would prefer python since most..." <- The last part is false, there should be more people able to work on it in the future. Even you said that we should go with Rust repetitively at the summits. It isn’t going to happen if you discourage people from using it.
mayhem[m]
I do believe I qualified that -- I didn't say drop everything and start using rust for everything. My intention was that if we needed something that required speed, that we should consider using rust over go. but if python is a viable option as it is in this case, we should go with python.
so, no I dont want people to start randomly using rust for projects -- that should be a careful considering.
s/considering/consideration/
julian45[m]
<yvanzo[m]> "julian45: Thank you for preparin..." <- also, i guess it's news to me that these have not been used for years - since i saw commits pretty recently (e.g., at the last point update of jira, you updated `config.inc.sh` to change old vs new jira ver), i had assumed they were still used in some form
yvanzo[m]
julian45: I’m mainly updating the configuration files only.
julian45: The scripts were used to migrate from a server to another. This isn’t used for current updates.
Kladky has quit
mayhem: That’s good because nobody said “drop everything and start using rust for everything”. Also, speed isn’t the main benefit, so it shouldn’t be your only determining criterion either. Last, if we were waiting for critical projects, that would be a vicious circle and we would end up with never picking up a language we are never getting familiar with.
lucifer[m]
yeah but there also has to be enough tangible benefit to do a project in a different language be it rust or any other one.
else we'd end up with a bunch of projects in different languages making cross project knowledge transfer difficult.
Kladky joined the channel
yvanzo[m]
There are such tangible benefits, and we are not speaking about using all the programming languages on earth.
TOPIC: MetaBrainz Community and Development channel | MusicBrainz non-development: #musicbrainz | BookBrainz: #bookbrainz | Channel is logged and not empty as it is bridged to IRC; see https://musicbrainz.org/doc/ChatBrainz for details | Agenda: Reviews, ChatBrainz downtime
BobSwift[m] has quit
julian45[m]
<yvanzo[m]> "julian45: The scripts were..." <- i see. to some extent, that is still useful for me to reference.^ drilling down into your script a bit, i think you might be able to understand something i'm missing w/ the transfer of old files from a prev server; namely, it doesn't seem like the `jira` account on the "old" server (current prod) is meant to be SSHed to, as rsyncs time out. should i perhaps modify current state on the
prod server a bit to make those directories rsyncable? this could mean, e.g., adding an SSH key to the jira account, or seeing if i could wrangle agent forwarding so that i can SSH over to root on the "old" server from the "new" server
^ for ref, since the current prod server is on a very old ubuntu version with a JDK incompatible with later jira versions, i decided it was preferable to start "fresh" on a newer server
