From Fedora Project Wiki
< Changes
m (Improve list readability some more) |
(Add trackers) |
||
| (4 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
= FontAwesome6 <!-- The name of your change proposal --> = | = FontAwesome6 <!-- The name of your change proposal --> = | ||
== Summary == | == Summary == | ||
| Line 59: | Line 57: | ||
== Current status == | == Current status == | ||
[[Category: | [[Category:ChangeAcceptedF39]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
| Line 77: | Line 75: | ||
ON_QA -> change is fully code complete | ON_QA -> change is fully code complete | ||
--> | --> | ||
* FESCo issue: | * [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/LCETWWN477NI26IHZ4NX4F3NWPM6GWER/ devel thread] | ||
* Tracker bug: | * FESCo issue: [https://pagure.io/fesco/issue/2968 #2968] | ||
* Release notes tracker: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=2181567 #2181567] | ||
* Release notes tracker: [https://pagure.io/fedora-docs/release-notes/issue/971 #971] | |||
== Detailed Description == | == Detailed Description == | ||
| Line 171: | Line 170: | ||
<!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | <!-- If your Change may require trademark approval (for example, if it is a new Spin), file a ticket ( https://pagure.io/Fedora-Council/tickets/issues ) requesting trademark approval from the Fedora Council. This approval will be done via the Council's consensus-based process. --> | ||
* Alignment with | * Alignment with Community Initiatives: | ||
<!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider --> | <!-- Does your proposal align with the current Fedora Objectives: https://docs.fedoraproject.org/en-US/project/objectives/ ? It's okay if it doesn't, but it's something to consider --> | ||
== Upgrade/compatibility impact == | == Upgrade/compatibility impact == | ||
<!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | <!-- What happens to systems that have had a previous versions of Fedora installed and are updated to the version containing this change? Will anything require manual configuration or data migration? Will any existing functionality be no longer supported? --> | ||
Users should not notice this change, except for having fewer bundled copies of the FontAwesome icons on disk. | Users should not notice this change, except for having fewer bundled copies of the FontAwesome icons on disk. | ||
== How To Test == | == How To Test == | ||
| Line 197: | Line 192: | ||
--> | --> | ||
Install packages from the [https://copr.fedorainfracloud.org/coprs/jjames/FontAwesome6 the FontAwesome6 COPR]. Launch each one and verify that it displays the expected icons. | Install packages from the [https://copr.fedorainfracloud.org/coprs/jjames/FontAwesome6 the FontAwesome6 COPR]. Launch each one and verify that it displays the expected icons. | ||
== User Experience == | == User Experience == | ||
| Line 217: | Line 209: | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
All dependencies are listed above and will be updated together. If maintainers do not respond to pull requests in a timely manner, then provenpackager privileges can be used to merge the pull requests and do the builds together. The definition of "timely manner" is up for debate. | All dependencies are listed above and will be updated together. If maintainers do not respond to pull requests in a timely manner, then provenpackager privileges can be used to merge the pull requests and do the builds together. The definition of "timely manner" is up for debate. | ||
== Contingency Plan == | == Contingency Plan == | ||
| Line 229: | Line 218: | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Blocks release? N/A (not a System Wide Change), Yes/No <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== Documentation == | == Documentation == | ||
Latest revision as of 14:58, 24 March 2023
FontAwesome6
Summary
Update the FontAwesome package in Fedora to version 6.x, with a compatibility package for packages still needing 4.x.
Owner
- Name: Jerry James
- Email: loganjerry@gmail.com
Affected maintainers
- Xavier Bachelot
- Lumír Balhar
- Nick Bebout
- Alexander Bokovoy
- Tom Callaway
- Rob Crittenden
- Endi Sukma Dewata
- Rex Dieter
- Radomir Dopieralski
- Claran Dorney
- Mohamed ElMorabity
- Marco Fargetta
- Kevin Fenzi
- Christina Fu
- Matthew Harmsen
- Jakub Hrozek
- ipa-maint
- Chris Kelley
- Martin Kosek
- Petr Lautrbach
- Ade Lee
- Fabio Allesandro Locati
- Jack Magne
- Christopher Meng
- Than Ngo
- Jindrich Novy
- Mukundan Ragavan
- Matthias Runge
- Alexander Scheel
- Simo Sorce
- Chedi Toueiti
- Patrick Uiterwijk
- Petr Vobornik
- Thomas Woerner
- Jonathan Wright
Current status
- Targeted release: Fedora Linux 39
- Last updated: 2023-03-24
- devel thread
- FESCo issue: #2968
- Tracker bug: #2181567
- Release notes tracker: #971
Detailed Description
The fontawesome-fonts package in Fedora is currently on version 4.7.0. Meanwhile, some packages now require version 5.x or 6.x of the fonts. Since most consumers still want version 4.7.0, the proposal is to introduce a fontawesome4-fonts compatibility package, and move the fontawesome-fonts package to the most recent release, currently version 6.3.0.
Feedback
Benefit to Fedora
Some user-facing applications will be able to display the latest versions of the FontAwesome icons, which have undergone a number of updates and cleanups to provide a more pleasing look. In addition, many new icons have been added in the 5.x and 6.x versions. For example, version 6.x contains a Fedora icon, while previous versions do not.
Scope
- Proposal owners:
- The fontawesome-fonts package will be updated to version 6.3.0.
- The python-pydata-sphinx-theme package will be updated to version 0.13.1, which requires FontAwesome 6.x.
- The python-QtAwesome package will be updated to version 1.2.2, which includes FontAwesome 6.x support, and changed to unbundle those fonts that can be unbundled.
- The python-sphinx_ansible_theme package will be updated to version 0.10.1, which permits some spec file simplifications, and updated to depend on fontawesome4-fonts.
- The python-XStatic-Font-Awesome package will be updated to version 6.2.1.1, which requires FontAwesome 6.x.
- The texlive package will be updated to remove an unnecessary dependency on fontawesome-fonts.
- Two new packages will be added to the distribution:
- fontawesome4-fonts, a nearly exact copy of the current fontawesome-fonts package
- python-accessible-pygments, to support upgrading the python-pydata-sphinx-theme package
- One package will be retired from the distribution:
- fontawesome5-fonts, which will be obsoleted by fontawesome-fonts, since version 6.x is backwards compatible with 5.x
- The following packages will be updated to depend on fontawesome4-fonts instead of fontawesome-fonts:
- freeipa
- ipsilon
- python-acme
- python-f5-sdk
- python-streamlink
- sympa
- The following packages will be updated to unbundle the FontAwesome CSS files and depend on fontawesome4-fonts:
- python-nbclassic
- The following packages will be updated to unbundle the FontAwesome 4.x fonts and depend on fontawesome4-fonts:
- dogtag-pki
- The following packages will be updated to unbundle the FontAwesome 6.x fonts:
- R-fontawesome
- The following packages will be updated to build documentation with the new version of python-pydata-sphinx-theme:
- python-networkx
- Finally, the cantata package will be updated to version 2.5.0, which is the final upstream version. Since upstream has declared itself dead, a patch to use FontAwesome 6.x will be added to the cantata package, so that we can someday retire fontawesome4-fonts.
- All of these changes are available for inspection at this COPR. Changes for an individual package can be seen in jjames's fork of that package.
- Several packages do not need any changes, because they already depend on
font(fontawesome), rather than on fontawesome-fonts, as suggested by the font guidelines.- coq
- libgpuarray
- libsemigroups
- python-BTrees
- python-primecountpy
- python-sphinx_rtd_theme
- Other developers:
Maintainers of the packages listed above will need to review the proposed changes and merge them if they are acceptable. Afterwards, I will build all packages in a side tag and merge to Rawhide once all builds are complete.
- 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 Community Initiatives:
Upgrade/compatibility impact
Users should not notice this change, except for having fewer bundled copies of the FontAwesome icons on disk.
How To Test
Install packages from the the FontAwesome6 COPR. Launch each one and verify that it displays the expected icons.
User Experience
Users should not see any changes, except for a disk space savings if they have more than one affected package installed.
Dependencies
All dependencies are listed above and will be updated together. If maintainers do not respond to pull requests in a timely manner, then provenpackager privileges can be used to merge the pull requests and do the builds together. The definition of "timely manner" is up for debate.
Contingency Plan
- 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), Yes/No
Documentation
N/A (not a System Wide Change)
Release Notes
The fontawesome-fonts package has been upgraded to version 6.3.0, and a compatibility fontawesome4-fonts package has been introduced for applications that still require FontAwesome 4.7.0. For packages that can use the FontAwesome 6.x icons, the changes described in the FontAwesome changelog are now available. Packages that use the FontAwesome 4.x icons do not have any user-visible changes.