Search results

** Considering the new packages promise to be ABI-compatible with zlib, the packages depending on zlib won't be rebuilt. *** This may help to catch ABI-compatibility issues soon.

Release for MIPS Little Endian Multilib (N64 ABI preferred, O32 and N32) based on Fedora 21

= New 128-bit IEEE long double ABI for IBM 64-bit POWER LE<!-- The name of your change proposal --> = Transition IBM 64-bit POWER LE systems to the new 128-bit IEEE long double ABI.

...nary (interpreter) for the tools to be able to run, provides system-python(abi) * python3 still requires python3-libs and provides python(abi)

...mal. The smaller the core, the easier is to maintain and guarantee the API/ABI stability. Our intention is to move large and/or fast-moving components out ...to its short development & release cycles and the possible associated API/ABI breakage. We will therefore implement packaging changes that will allow us

The introduction of oneTBB marked a distinct change in the API And ABI of the library. In order to facilitate a transition from the traditional TB

...ibreoffice-core, without a specific n-v-r as extensions use the stable UNO abi which rarely changes, and then only to add extra apis. So unless you requir

...ezes ABI for release, so careful attention must be paid to any last minute ABI changes. ...t a mass rebuild uses the released version of glibc to fix any last minute ABI changes. The GNU C Library (glibc) does not require a mass rebuild for this

* A small module with easy to keep API/ABI promises * Maintaining the API/ABI promise is complicated

...ezes ABI for release, so careful attention must be paid to any last minute ABI changes. ...t a mass rebuild uses the released version of glibc to fix any last minute ABI changes. A mass rebuild is not required and this is communicated to release

...ezes ABI for release, so careful attention must be paid to any last minute ABI changes. ...t a mass rebuild uses the released version of glibc to fix any last minute ABI changes. A mass rebuild has been requested. <!-- REQUIRED FOR SYSTEM WIDE C

...penSSL 3.0 release is going to be a significantly new release with changed ABI however with minimal API changes. That means most of the dependent packages ...up to the final one should not be disruptive and they should not break API/ABI.

Requires: lua(abi) = %{lua_version}

...aim is to synchronize Fedora with the most recent Boost release. Because ABI stability is one of explicit Boost non-goals, this entails rebuilding of al ...For Fedora 20, the scope was: about 130 packages _must_ be rebuilt due to ABI breakage inherent in bumping Boost sonames. There were almost 250 client pa

* [[Architectures/MIPS|MIPS]]-64el (mips64r2, little endian, n64 ABI) * [[Architectures/MIPS|MIPS]]-el (mips32r2, little endian, o32 ABI)

...nt. (16-byte stack alignment was introduced with SSE2 support in the i386 ABI, but old binaries only provide 4-byte stack alignment.) ...For 64-bit x86 systems, SSE2 support is a required support of the baseline ABI and already extensively used by Fedora.

allows for keeping ABI stability in future upgrades. We will also add compat openssl102 package so ...atures we need to rebase to the 1.1.0 branch which brings long awaited API/ABI cleanup.

...tps://access.redhat.com/articles/rhel-abi-compatibility there is no API or ABI stability guarantee].

.... This change affects several multimedia players as there are both API and ABI changes. ...s using {{package|libva}} will be rebuilt to take into account the new API/ABI. Futhermore, the intel backend will be updated along (not provided by Fedor

..., notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these re * Avoid ABI/API changes where possible. If unavoidable, should coordinate a side tag to