Bug 2403274
| Summary: | beets-2.5.0 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | beets | Assignee: | Gerald Cox <gbcox> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | gbcox, mh, michele | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | beets-2.5.0-1.fc44 beets-2.5.0-2.fc44 beets-2.5.0-3.fc44 beets-2.5.1-1.fc42 beets-2.5.1-1.fc43 | Doc Type: | --- | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2025-10-11 16:09:38 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Upstream Release Monitoring
2025-10-11 10:51:12 UTC
Scratch build failed. Details below:
BuilderException: Build failed:
There is a syntax error in updated specfile. See attached diff for the changes.
Traceback:
File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
result = self.builder.build(request.package, request.opts)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 205, in build
raise BuilderException(str(exc), value=output)
If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
Created attachment 2109340 [details]
Update to 2.5.0 (#2403274)
Release v2.5.0
Repository: beetbox/beets · Tag: v2.5.0 · Commit: 6faa4f3 · Released by: github-actions[bot]
New features
Convert Plugin: Add a config option to disable writing metadata to converted files.
Discogs Plugin Added support for featured artists. 🐛 (#6038)
Discogs Plugin New configuration option featured_string to change the default string used to join featured artists. The default string is Feat..
Discogs Plugin Support for artist_credit in Discogs tags. 🐛 (#3354)
Discogs Plugin Support for name variations and config options to specify where the variations are written. 🐛 (#3354)
Discogs Plugin: New config option strip_disambiguation to toggle stripping discogs numeric disambiguation on artist and label fields.
LastGenre Plugin: Add a --pretend option to preview genre changes without storing or writing them.
Bug fixes
Metadata source plugins: Fixed data source penalty calculation that was incorrectly applied during import matching. The source_weight configuration option has been renamed to data_source_mismatch_penalty to better reflect its purpose. 🐛 (#6066)
Chromaprint/Acoustid Plugin BPSync Plugin Fix plugin loading issue caused by an import of another beets.plugins.BeetsPlugin class. 🐛 (#6033)
Discogs Plugin Fixed inconsistency in stripping disambiguation from artists but not labels. 🐛 (#5366)
FromFilename Plugin: Fix 🐛 (#5218), improve the code (refactor regexps, allow for more cases, add some logging), add tests.
MusicBrainz Plugin Refresh flexible MusicBrainz metadata on reimport so format changes are applied. 🐛 (#6036)
Spotify Plugin Ensure spotifysync keeps popularity, ISRC, and related fields current even when audio features requests fail. 🐛 (#6061)
Spotify Plugin Fixed an issue where candidate lookup would not find matches due to query escaping (single vs double quotes).
Spotify Plugin Fixed an issue where track matching and lookups could return incorrect or misleading results when using the Spotify plugin. The problem occurred primarily when no album was provided or when the album field was an empty string. 🐛 (#5189)
Spotify Plugin Removed old and undocumented config options artist_field, album_field and track that were causing issues with track matching. 🐛 (#5189)
Other changes
Moved art.py utility module from beets into beetsplug namespace as it is not used in the core beets codebase. It can now be found in beetsplug._utils.
Moved vfs.py utility module from beets into beetsplug namespace as it is not used in the core beets codebase. It can now be found in beetsplug._utils.
When installing beets via git or locally the version string now reflects the current git branch and commit hash. 🐛 (#4448)
Autotagger Matching Options: match.distance_weights.source configuration has been renamed to match.distance_weights.data_source for consistency with the name of the field it refers to.
FAQ: Add check for musicbrainz plugin if auto-tagger can't find a match 🐛 (#6020)
Plugins: Clarify that musicbrainz must be mentioned if plugin list modified 🐛 (#6020)
Using the Auto-Tagger: Section on no matching release found, related to possibly disabled musicbrainz plugin 🐛 (#6020)
beets.metadata_plugin.MetadataSourcePlugin: Remove discogs specific disambiguation stripping.
For developers and plugin authors
Metadata source plugins are now registered globally when instantiated, which makes their handling slightly more efficient.
The track_distance() and album_distance() methods have been removed from MetadataSourcePlugin. Distance calculation for data source mismatches is now handled automatically by the core matching logic. This change simplifies the plugin architecture and fixes incorrect penalty calculations. 🐛 (#6066)
Typing improvements in beets/logging.py: getLogger now returns BeetsLogger when called with a name, or RootLogger when called without a name.
FEDORA-2025-a0cf058b1e (beets-2.5.0-1.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-a0cf058b1e FEDORA-2025-6034fcfe96 (beets-2.5.0-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6034fcfe96 FEDORA-2025-20c2b68269 (beets-2.5.0-1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-20c2b68269 FEDORA-2025-a0cf058b1e (beets-2.5.0-1.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-6034fcfe96 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6034fcfe96` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6034fcfe96 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-20c2b68269 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-20c2b68269` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-20c2b68269 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-0e43d32d8f (beets-2.5.0-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-0e43d32d8f FEDORA-2025-49dcdfc1f6 (beets-2.5.0-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-49dcdfc1f6 FEDORA-2025-7eaff9a490 (beets-2.5.0-2.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-7eaff9a490 FEDORA-2025-0e43d32d8f (beets-2.5.0-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-7eaff9a490 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7eaff9a490` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7eaff9a490 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-49dcdfc1f6 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-49dcdfc1f6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-49dcdfc1f6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-6597515bc4 (beets-2.5.0-3.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-6597515bc4 FEDORA-2025-f7e41d1527 (beets-2.5.0-3.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2025-f7e41d1527 FEDORA-2025-d6b067ea32 (beets-2.5.0-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-d6b067ea32 FEDORA-2025-f7e41d1527 (beets-2.5.0-3.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-d6b067ea32 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-d6b067ea32` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d6b067ea32 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-6597515bc4 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-6597515bc4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-6597515bc4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-17b7750c16 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-17b7750c16` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-17b7750c16 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-05fad2031e has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-05fad2031e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-05fad2031e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-05fad2031e (beets-2.5.1-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-17b7750c16 (beets-2.5.1-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. |