Bug 2260332 - Picard 2.11 Upstream release
Summary: Picard 2.11 Upstream release
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: picard
Version: rawhide
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gerald Cox
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-01-25 12:21 UTC by Gerald Cox
Modified: 2024-02-07 01:50 UTC (History)
5 users (show)

Fixed In Version: picard-2.11.0-1.fc40 picard-2.11.0-1.fc38 picard-2.11.0-1.fc39
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-01-25 15:00:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Gerald Cox 2024-01-25 12:21:04 UTC
MusicBrainz Picard 2.11

Repository: metabrainz/picard · Tag: release-2.11 · Commit: 36b0c77

Bugfixes

PICARD-2819 - Track/release relationship settings not being respected as described 
PICARD-2602 - macOS: Spaces not visible between items after comma use
PICARD-2780 - Weighting search results does match non-video tracks incorrectly
PICARD-2781 - Weighting search results does apply extremely low matching if a release on MB has no release types at all
PICARD-2791 - Navigation tree in options dialog can be completely hidden
PICARD-2792 - Unlinked AcoustID results are preferred over results with metadata
PICARD-2805 - Metadata comparison for recordings raises exception if length is None
PICARD-2814 - Error loading files with invalid / unknown ID3 cover art type

Improvements

PICARD-2584 - Handle AcoustID missing metadata
PICARD-2777 - Options indicate that enabling track relationships automatically includes release relationships
PICARD-2795 - Display currently selected verbosity in log view verbosity selection
PICARD-2813 - AcoustID lookup on recoverable decoding errors

Reproducible: Always

Comment 1 Fedora Update System 2024-01-25 14:51:26 UTC
FEDORA-2024-ab24bd7607 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ab24bd7607

Comment 2 Fedora Update System 2024-01-25 14:52:15 UTC
FEDORA-2024-20bfda97ab has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-20bfda97ab

Comment 3 Fedora Update System 2024-01-25 14:53:34 UTC
FEDORA-2024-8af0899b96 has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-8af0899b96

Comment 4 Fedora Update System 2024-01-25 15:00:26 UTC
FEDORA-2024-8af0899b96 has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 5 Fedora Update System 2024-01-26 00:26:19 UTC
FEDORA-2024-20bfda97ab has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-20bfda97ab`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-20bfda97ab

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-01-26 01:06:05 UTC
FEDORA-2024-ab24bd7607 has been pushed to the Fedora 39 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ab24bd7607`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ab24bd7607

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2024-02-03 01:48:18 UTC
FEDORA-2024-20bfda97ab has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2024-02-07 01:50:25 UTC
FEDORA-2024-ab24bd7607 (picard-2.11.0-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.