The Fedora Project is pleased to announce the immediate availability of the
Fedora 25 Alpha, an important milestone on the road to our Fedora 25 release
Download the prerelease from our Get Fedora site:
Or, check out one of our popular variants:
== Alternative Architectures ==
We are also simultaneously releasing the F25 Alpha for Power64 and 64-bit ARM
(AArch64). These are available from:
== What is the Alpha release? ==
The Alpha release contains all the features of Fedora 25'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 25 is expected in
November. 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.
== Issues and Details ==
Since this is an alpha release, 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 Freenode. As testing
progresses, common issues are tracked on the Common F25 Bugs page.
For tips on reporting a bug effectively, read "how to file a bug report".
== Release Schedule ==
The full release schedule is available on the Fedora wiki:
The current schedule calls for a beta release towards the middle of October,
and the final release in November. 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.
Fedora Release Engineering
(Dennis, Peter, Kevin, Mohan, Adam, Randy)
test-announce mailing list
This recent Microsoft's Patch
disable password change for Domain Controller NT4 Style.
IMHO, It may be time to enable support to AD-DC mode, or release
another renamed packages with AD-DC support enable.
The samba.src is ready for this:
I have try to download the samba.src rpm, modify the spec file like
> sed \
> -e 's/%global with_mitkrb5 1/%global with_mitkrb5 0/' \
> -e 's/%global with_dc 0/%global with_dc 1/' \
rebuild the package, install it on a test server and configure it in
It seems work fine.
My question is:
There is some hope that in the short this flags are enable by default?
Many thanks for your reply
(inviato dal mio Linux Fedora 24 Workstation)
I'm working on getting new luajit version for Rawhide. Affected packages:
$ sudo dnf -q repoquery --alldeps --whatrequires luajit --srpm
I will try to rebuild this packages. Looks like there were no serious
API changes (if there were any except adding new functions).
We have bug in InsightToolKit for > half year that it doesn't work
properly on ARM, but maintainer doesn't respond neither to bugzilla
nor to email. It's blocking me from importing 4 packages as all of
them failing on ARM due to ITK bug.
Probably it just needs update, probably some investigation. Would be
nice if we can reassign his packages to someone else.
He is maintainer of:
He is co-maintainer of:
I would be interested in taking care of: InsightToolkit, dcmtk, gdcm,
vxl, tinyxml2, vtk. As I have some number of packages depending on