starred/Lidarr

Fork 0

mirror of https://github.com/Lidarr/Lidarr.git synced 2026-03-02 22:56:57 -05:00

Anybody noticed that Musicbrainz changed its database layout #4288

New issue

Closed

opened 2026-02-20 03:03:23 -05:00 by deekerman · 5 comments

deekerman commented

2026-02-20 03:03:23 -05:00

Owner

Originally created by @synofan on GitHub (Jun 26, 2025).

Is there an existing issue for this?

I have searched the existing open and closed issues

Current Behavior

Unable to add new artists

Expected Behavior

To be able to add new artists and for Lidarr to communicate correctly with the new db layout.... please ;-)

Steps To Reproduce

No response

Environment

- OS: DSM 7.2
- Lidarr: 2.13.0.4664

What branch are you running?

Develop

Trace Logs?

Lidarr log.txt

Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided.

I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain trace - that are relevant and show this issue.

Originally created by @synofan on GitHub (Jun 26, 2025). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Current Behavior Unable to add new artists ### Expected Behavior To be able to add new artists and for Lidarr to communicate correctly with the new db layout.... please ;-) ### Steps To Reproduce _No response_ ### Environment ```markdown - OS: DSM 7.2 - Lidarr: 2.13.0.4664 ``` ### What branch are you running? Develop ### Trace Logs? [Lidarr log.txt](https://github.com/user-attachments/files/20928445/Lidarr.log.txt) ### Trace Logs have been provided as applicable. Reports may be closed if the required logs are not provided. - [x] I have read and followed the steps in the wiki link above and provided the required trace logs - the logs contain `trace` - that are relevant and show this issue.

deekerman

2026-02-20 03:03:23 -05:00

closed this issue
added the
Type: Support.
label

deekerman commented

2026-02-20 03:03:24 -05:00

Author

Owner

@alyraffauf commented on GitHub (Jun 26, 2025):

please check before posting, this is probably covered by #5498

@alyraffauf commented on GitHub (Jun 26, 2025): please check before posting, this is probably covered by #5498

deekerman commented

2026-02-20 03:03:24 -05:00

Author

Owner

@synofan commented on GitHub (Jun 26, 2025):

Maybe but the question is rather that Musicbrainz changed its database layout on may 19, so you are saying that that takes almost a month to fix. with all required respect! Maybe looking at wrong issue? I regretfully have not the capacity to fix this. Am greatfull for all the hardworking developers!

@synofan commented on GitHub (Jun 26, 2025): Maybe but the question is rather that Musicbrainz changed its database layout on may 19, so you are saying that that takes almost a month to fix. with all required respect! Maybe looking at wrong issue? I regretfully have not the capacity to fix this. Am greatfull for all the hardworking developers!

deekerman commented

2026-02-20 03:03:24 -05:00

Author

Owner

@synofan commented on GitHub (Jun 26, 2025):

Can anybody comment on the changed Musicbrainz DB, if it is an issue or not. Thank you in advance.

@synofan commented on GitHub (Jun 26, 2025): Can anybody comment on the changed Musicbrainz DB, if it is an issue or not. Thank you in advance.

deekerman commented

2026-02-20 03:03:24 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jun 26, 2025):

please search for existing metadata issues / looked at the pinned GHI or visit discord for support before opening yet another duplicate....

the bug report clearly states Report a new bug, if you are not 100% certain this is a bug please go to our Discord first I'm unsure why you choose to ignore this and open a bug that you were clearly unsure about.

@bakerboy448 commented on GitHub (Jun 26, 2025): please search for existing metadata issues / looked at the pinned GHI or visit discord for support before opening yet another duplicate.... the bug report clearly states `Report a new bug, if you are not 100% certain this is a bug please go to our Discord first` I'm unsure why you choose to ignore this and open a bug that you were clearly unsure about.

deekerman commented

2026-02-20 03:03:24 -05:00

Author

Owner

@bakerboy448 commented on GitHub (Jun 26, 2025):

For support and inquiries, please use our Discord channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.

@bakerboy448 commented on GitHub (Jun 26, 2025): For support and inquiries, please use our [Discord](http://lidarr.audio/discord) channel. GitHub is designated solely for bug reports and feature requests. It seems that this issue may fall under a support request, so we kindly ask you to visit our Discord for assistance. Thank you.