From Fedora Project Wiki
- ...dering will be alphanumerical based on package name. There are no planned ABI/soname changes that would require logical build ordering. Further, all the ...4 KB (579 words) - 15:38, 27 January 2020
- ...rc3 that we force us to patch LLVM to maintain compatibility with the -rc2 ABI. This scenario would not require rebuilding LLVM library uses in Fedora, s ...17 KB (2,687 words) - 23:20, 28 September 2023
- ...dering will be alphanumerical based on package name. There are no planned ABI/soname changes that would require logical build ordering. Further, all the ...4 KB (616 words) - 13:40, 28 April 2018
- ...ARMv5tel (in the 'arm' directory) and ARMv7hl (in the 'armhfp' directory) ABI formats at the following location: ...4 KB (561 words) - 11:01, 6 June 2017
- ...dering will be alphanumerical based on package name. There are no planned ABI/soname changes that would require logical build ordering. Further, all the ...4 KB (617 words) - 03:14, 16 May 2017
- ...dering will be alphanumerical based on package name. There are no planned ABI/soname changes that would require logical build ordering. Further, all the ...4 KB (611 words) - 13:22, 3 August 2017
- ...e the actual release, so careful attention must be paid to any last minute ABI changes. ...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> ...15 KB (2,481 words) - 20:17, 11 December 2019
- ...e the actual release, so careful attention must be paid to any last minute ABI changes. ...ar, but to do so may require a mass rebuild to remove new symbols from the ABI/API. <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> ...16 KB (2,498 words) - 13:49, 7 July 2020
- ...dering will be alphanumerical based on package name. There are no planned ABI/soname changes that would require logical build ordering. Further, all the ...4 KB (602 words) - 13:41, 24 July 2019
- ...dering will be alphanumerical based on package name. There are no planned ABI/soname changes that would require logical build ordering. Further, all the ...4 KB (612 words) - 13:14, 26 July 2017
- ...dering will be alphanumerical based on package name. There are no planned ABI/soname changes that would require logical build ordering. Further, all the ...4 KB (650 words) - 10:15, 14 July 2018
- ...ase that we force us to patch LLVM to maintain compatibility with the -rc3 ABI. This scenario would not require rebuilding LLVM library users in Fedora, ...18 KB (2,882 words) - 00:50, 4 May 2024
- ...ing: No action from release engineering is needed for this change (libcurl ABI is kept). ...4 KB (586 words) - 12:21, 4 November 2017
- * If this is an update, the API packages don't break API/ABI and their file listings don't change. ...4 KB (643 words) - 18:06, 23 November 2016
- Requires: php(zend-abi) = %{php_zend_api} PECL extension '''MUST''' have ABI check (see previous) ...16 KB (2,243 words) - 19:14, 14 October 2016
- * When a proposed update contains an ABI or API change: notify '''a week in advance''' both fedora-devel and maintai * Avoid ABI/API changes where possible. If unavoidable, should coordinate a side tag to ...57 KB (4,247 words) - 07:56, 3 April 2019
- ...Regression/Issue: DNF 5.2 is not available in Fedora 38, 39, or 40 (it is ABI-incompatible with DNF 5.1), so testers will probably need to get the latest ...4 KB (587 words) - 05:20, 29 May 2024
- Known Regression/Issue: DNF 5.2 is not available in Fedora 39, or 40 (it is ABI-incompatible with DNF 5.1), so testers will probably need to get the latest ...4 KB (616 words) - 08:47, 7 June 2024
- ...that would force us to patch LLVM to maintain compatibility with the -rc3 ABI. This scenario would not require rebuilding LLVM library users in Fedora, ...19 KB (3,038 words) - 11:53, 21 June 2024
- ...Modules]] to let the user switch between them. If the library is not 100% ABI-compatible get one of the upstreams to rename. See [[Packaging:Conflicts#Ap ...12 KB (1,900 words) - 03:39, 20 December 2018