FEDORA-2019-79c8f191ec created by gbcox 4 months ago for Fedora 30
stable

Upstream release #1753956


Upstream release #1752247

How to install

sudo dnf upgrade --advisory=FEDORA-2019-79c8f191ec

This update has been submitted for testing by gbcox.

4 months ago

This update's test gating status has been changed to 'waiting'.

4 months ago

This update has obsoleted picard-2.2.0-1.fc30, and has inherited its bugs and notes.

4 months ago

This update's test gating status has been changed to 'ignored'.

4 months ago

This update has been pushed to testing.

4 months ago

This update can be pushed to stable now if the maintainer wishes

4 months ago

This update has been submitted for stable by bodhi.

4 months ago
User Icon jflory7 commented & provided feedback 4 months ago
karma

The classical_extras plugin is broken upstream and causes crashes for anyone who uses this plugin:

https://community.metabrainz.org/t/picard-2-2-is-available/443479/22

Pushing this update could cause confusing breakage. Unfortunately the classical_extras plugin is shipped in default installations, versus an individual user decision to install and use the plugin. Upstream recommends holding off on 2.2 upgrades until an all-clear is given for classical_extras. Currently, they recommend manually replacing the ZIP file with a downloaded version from the MusicBrainz website. Perhaps a patch file could be written to fix this in Fedora, but I'm not sure if it is worth the work of a patch or to wait for a proper upstream fix.

BZ#1752247 picard-2.2 is available
BZ#1753956 picard-2.2.1 is available
User Icon gbcox commented & provided feedback 4 months ago

Thanks for the report... the actual ticket is here: https://tickets.metabrainz.org/projects/PICARD/issues/PICARD-1615?filter=allopenissues

Appears that the plugin was using an unsupported function. I double checked and this plugin must be manually activated, so we can't be sure how many people are actually using it - therefore, I'll open a bugzilla ticket with information to either deactivate the plugin or backout to the previous release until this is fixed.

User Icon jflory7 commented & provided feedback 4 months ago

Thanks for digging further. As I understand, classical users are a more narrow subset of the Picard user base. Do you think it makes sense to ship this, knowing that some advanced users may end up with a crash loop every time they open the "Options" menu? Curious what you think makes sense here.

User Icon gbcox commented & provided feedback 4 months ago

Well, it was pushed to stable before you commented on the issue. Since this plugin is not installed by default I don't think that justifies pulling the entire update, especially since we don't know how many people are really impacted. I personally don't use the classical_extras plugin and don't have it installed. If people know enough to install, I'm assuming they know how to uninstall it and search for issues regarding this on the internet. I've opened a bugzilla ticket with the links the report you referenced and the actual ticket. I believe that is sufficient.

This update has been pushed to stable.

4 months ago

Please login to add feedback.

Metadata
Type
bugfix
Karma
-1
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
3
Stable by Time
7 days
Dates
submitted
4 months ago
in testing
4 months ago
in stable
4 months ago
BZ#1752247 picard-2.2 is available
0
0
BZ#1753956 picard-2.2.1 is available
0
0

Automated Test Results