I understand that builds of Ada packages have been failing on ppc64
since before the F23 release.
GPRbuild 2015 introduced some dependency loops that Koji can't handle.
This was worked around with some trickery, but apparently the secondary
architectures were left behind. We now have a better solution that
should allow future upgrades to go smoothly, and I'd like to see if we
can get GPRbuild back on track on ppc64.
I have no ppc64 hardware myself, and I'm not sure how to access the
build systems that secondary architectures use, but I hope we can work
together to restore GPRbuild and the packages that depend on it.
It should be possible to use the working GPRbuild in older releases to
re-bootstrap GPRbuild for Rawhide and F24. The following is how it
would be done on a primary architecture. The procedure may need to be
adapted if things work differently for secondary architectures.
1: Take a ppc64 host running F22 or F23 and install gprbuild and
gcc-gnat the usual way. You will get a dynamically linked GPRbuild 2014
that pulls in XMLada and libgnat.
2: Uninstall xmlada-devel if it is installed.
3: Copy the latest xmlada and gprbuild source packages from Rawhide or
F24 to the F22 or F23 host.
4: Build xmlada with RPMbuild.
5: Use rpm --install --excludedocs to install the resulting
xmlada-2015, xmlada-devel-2015 and xmlada-static-2015 packages. Do not
upgrade the base package, but keep xmlada-2013 installed alongside
xmlada-2015. (--excludedocs works around file conflicts.)
6: Build gprbuild with RPMbuild. This will produce a statically linked
7: Unpack the resulting gprbuild package and repackage the file tree in
a tarball. (/usr/share/doc can be omitted but all the rest of /usr is
8: Check out the master branch of gprbuild.
9: Add the tarball from step 7 as Source100 and set bootstrap_arch to
10: Build gprbuild in Koji. This step gets the statically linked
executables into Koji.
11: When the build from step 10 shows up in the buildroot, build xmlada
12: Remove Source100 and change bootstrap_arch back.
13: When the build from step 11 shows up in the buildroot, build
14: Repeat steps 8 to 13 for F24.
The Fedora 24 Alpha for POWER is here, right on schedule for our planned June
final release. Download the prerelease from our Get Fedora site:
- Get Fedora 24 Alpha Workstation https://getfedora.org/en/workstation/
- Get Fedora 24 Alpha Server https://getfedora.org/en/server/prerelease/
- Get Fedora 24 Alpha Cloud https://getfedora.org/en/cloud/prerelease/
- Get Fedora 24 Alpha Spins https://spins.fedoraproject.org/prerelease
- Get Fedora 24 Alpha Labs https://labs.fedoraproject.org/prerelease
- Get Fedora 24 Alpha ARM https://arm.fedoraproject.org/prerelease
What is the Alpha release?
The Alpha release contains all the features of Fedora 24's editions in
a form that anyone can help test. This testing, guided by the Fedora
QA team, helps us target and identify bugs. When these bugs are fixed,
we make a Beta release available. A Beta release is code-complete and
bears a very strong resemblance to the third and final release. The
final release of Fedora 24 is expected in June.
If you take the time to download and try out the Alpha, you can check
and make sure the things that are important to YOU are working. Every
bug you find and report doesn't just help you, it improves the
experience of millions of Fedora users worldwide!
Together, we can make Fedora rock-solid. We have a culture of
coordinating new features and pushing fixes upstream as much as we
can, and your feedback improves not only Fedora, but Linux and Free
software as a whole.
Under the hood, glibc has moved to 2.23. The update includes better
performance, many bugfixes and improvements to POSIX compliance, and
additional locales. The new library is backwards compatible with the
version of glibc that was shipped in Fedora 23, and includes a number
of security and bug fixes.
We've also updated the system compiler to GCC 6 and rebuilt all
packages with that, providing greater code optimization and catching
programming errors which had slipped past previous compilers.
In ppc64/ppc64le golang 1.6 brings all the same golang functionality that
other architectures have enjoyed enabling all the features and apps
that are avaialble there such as docker.
- FreeIPA 4.3 (Domain Controller role) is included in Fedora 24. This
version helps streamline installation of replicas by adding a
replica promotion method for new installs. A new topology plugin has
also been added that automatically manages new replication segment
creation. An effective replica topology visualization tool is also
available in the webUI.
- NodeJS 4 in now available for aarch64. Earlier versions of nodejs have
been available on primary architectures for some time. With nodejs4 we
now bring all the functionality to aarch64 too.
- More packages have been removed from the default Server edition to
make the footprint of the default installation smaller.
- For Fedora 24, we're working hard to make Fedora the best platform
for developing containers, from the base Fedora container images to
a full-featured PaaS to run and manage them.
- For both ppc64 and ppc64le we have qemu cloud images and add to it
docker base images to the release as well.
Issues and Details
This is an Alpha release. As such, we expect that you may encounter bugs
or missing features. To report issues encountered during testing,
contact the Fedora QA team via the mailing list or in #fedora-qa on
As testing progresses, common issues are tracked on the Common F24 Bugs
For tips on reporting a bug effectively, read "how to file a bug
The full release schedule is available on the Fedora wiki:
The current schedule calls for a beta release towards the beginning of May,
the final release in early June.
Be aware that these dates are development targets. Some projects release
on a set date regardless of feature completeness or bugs; others wait
until certain thresholds for functionality or testing are met. Fedora
uses a hybrid model, with milestones subject to adjustment. This allows
us to make releases with new features and newly-integrated and updated
upstream software while also retaining high quality.