Wiki: https://fedoraproject.org/wiki/Changes/TagLib2

Discussion Thread: https://discussion.fedoraproject.org/t/179198

**This is a proposed Change for Fedora Linux.**
This document represents a proposed Change. As part of the Changes process,
proposals are publicly announced in order to receive community feedback.
This proposal will only be implemented if approved by the Fedora
Engineering Steering Committee.

== Summary ==

Update the taglib package from 1.13 to 2.x (2.1.1 as of the time of
writing), which is an ABI and API break, and rebuild or port all dependents
to the new version.

== Owner ==

* Name: [[User:yselkowitz|Yaakov Selkowitz]]
* Email: [email protected]

== Detailed Description ==

taglib 2.0 was released upstream in January 2024, with subsequent releases
since, and currently stands at 2.1.1.  There have been no further 1.13
releases, so this is needed to be on a supported version.

While this change represents both an ABI and API break, sufficient time has
passed for dependent upstreams to adapt to the new API.

A [https://copr.fedorainfracloud.org/coprs/yselkowitz/taglib-2.1.1/ mass
prebuild] has been done to scope the work involved in this change, and
(aside from unrelated breakage from GCC 16 or other dependencies) only a
few dependents require more than a revbump and rebuild:
* ardour6: needs backport of taglib-2 support from latest upstream version
* ardour7: needs backport of taglib-2 support from latest upstream version
* easytag: patches available from Debian
* python-pytaglib: requires version bump to 3.x
* soundkonverter: patches available from a fork
* taglib-extras: is no longer required by any packages, can be retired

== Feedback ==



== Benefit to Fedora ==

Fedora will be on the latest supported version, and will benefit from
improvements in future minor releases with a simple update.

== Scope ==

* Proposal owners: bump and rebuild dependents, apply patches as necessary
* Other developers: fix unrelated build failures (e.g. from GCC 16 or other
Changes), help with backports or retire obsolete packages
* Release engineering: N/A (not needed for this Change)
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)
* Alignment with the Fedora Strategy:

== Upgrade/compatibility impact ==

Either all packages in Fedora will be simultaneously updated to the new
version, or a taglib1 compat package will be created.

== Early Testing (Optional) ==

https://copr.fedorainfracloud.org/coprs/yselkowitz/taglib-2.1.1

Do you require 'QA Blueprint' support? N

== How To Test ==



== User Experience ==



== Dependencies ==

48 packages as discovered by mass-prebuild.

== Contingency Plan ==

Provide a taglib1 compat package if all dependents cannot be fixed in time.
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a System
Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change)

== Documentation ==

[https://taglib.org/older.html Upstream release notes]

== Release Notes ==

The TagLib library has been updated to the latest version, with many new
features.
-- 
_______________________________________________
devel-announce mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue
-- 
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/[email protected]
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to