Hi all,
over the weekend we will be importing and enabling ppc64 and ppc64le builds in
koji.fedoraproject.org as part of https://fedoraproject.org/wiki/
Architectures/RedefiningSecondaryArchitectures The import and enablement of
ppc64 and ppc64le is for rawhide only, we expect to add s390x sometime after
f26 has branched
We will be making changes to the compose process early next week to enable
ppc64 and ppc64le in the rawhide compose, a reminder that i386 has been moved
from /pub/fedora/ to /pub/fedora-secondary/
A further announcement will come when building of ppc64 and ppc64le is enabled
Thanks
Dennis
= Proposed System Wide Change: Retire Synaptics Driver =
https://fedoraproject.org/wiki/Changes/RetireSynapticsDriver
Change owner(s):
* Peter Hutterer <peter DOT hutterer AT who-t DOT net>
Retire the xorg-x11-drv-synaptics driver and remove it from user's install.
== Detailed Description ==
xorg-x11-drv-synaptics has been the main X.Org touchpad driver for
over a decade. Since Fedora 22, it has been superseded by
xorg-x11-drv-libinput which aims to provide a better touchpad
experience.
The only way to assign X.Org drivers is via the xorg.conf.d
configuration system which is based on config file sort order. e.g.
evdev sorts as 10-evdev.conf, synaptics as 70-synaptics.conf, etc.
Whichever sorts last is assigned as driver for a device. Fedora 22 and
later shipped with libinput's config file sorting higher than all
other drivers to overwrite any previous matches.
Some users prefer the synaptics driver over libinput. This requires
the users to install the driver and then place a custom config snippet
or, more commonly, symlink to the synaptics config snippets with a
name that has a higher sort order than xorg-x11-drv-libinput.
The aim of this change is to ensure that the synaptics driver can
simply be installed when required without any further user
configuration. When installed, it should be assigned as the preferred
driver over xorg-x11-drv-libinput.
For historical reasons, a vast majority of users have the synaptics
driver installed, especially those updating from older releases.
We want to a) remove the xorg-x11-drv-synaptics driver from a user's
machine but b) make it possible to install where required.
== Scope ==
* Proposal owners:
- xorg-x11-drv-synaptics must be removed from comps (complete as of F25)
- xorg-x11-drivers must not include xorg-x11-drv-synaptics (complete as of F25)
- the X server needs to support a fallback input driver. This ensures
that when an xorg.conf snippet assigns the synaptics driver but that
driver is missing, the user still has a working touchpad. Complete as
of xorg-x11-server-1.18.4-5
- xorg-x11-drv-synaptics will get a subpackage
xorg-x11-drv-synaptics-legacy containing the actual driver
- xorg-x11-drv-libinput will obsolete/provide the current
xorg-x11-drv-synaptics version
* Other developers:
- packages that currently require xorg-x11-drv-synaptics need to
revisit and either require the new subpackage or drop the requirement
- Affected packages: mate-desktop, cinnamon-desktop
* Release engineering: Nothing required, the RE changes are complete as of F25
* Policies and guidelines: No update needed
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed Self Contained Change:Blivet-GUI in Anaconda =
https://fedoraproject.org/wiki/Changes/AnacondaBlivetGUI
Change owner(s):
* Martin Kolman <mkolman(a)redhat.com>
* Vojtěch Trefný <vtrefny(a)redhat.com>
Add blivet-gui as an alternative option for storage configuration in
Anaconda Installer.
== Detailed Description ==
Add blivet-gui as an alternative option for storage configuration in
Anaconda Installer.
Unlike the current custom partitioning screen in Anaconda, which works
in a top-down way (user specifies mountpoints and their properties),
blivet-gui works with the bottom-up principle (user has full control
to assemble the storage configuration from individual members). By
integrating blivet-gui into anaconda we will make the bottom-up
partitioning available to users during the installation. Blivet-gui is
built on top of the blivet library, which is used by Anaconda for
storage configuration, this makes the change very easy to implement
and doesn't bring new code and dependecies into the installer other
than a relatively small GUI package.
== Scope ==
* Proposal owners:
- blivet-gui devs: Prepare blivet-gui for integration into Anaconda --
change the UI to look consistently while running fullscreen inside an
Anaconda spoke, change look and feel of blivet-gui dialogs to match
Anaconda dialogs, add storage configuration sanity checking into
blivet-gui.
- anaconda devs: Add an option to use blivet-gui to the Storage spoke,
add blivet-gui package as a dependency of the anaconda package so that
it is pulled into the installation environment and also add an option
to not show blivet-gui in anaconda if requested (see
https://github.com/rhinstaller/anaconda/blob/master/docs/user-interaction-c…
for detailed explanation how hiding spokes works in Anaconda).
* Other developers: N/A (not a System Wide Change)
* Release engineering: N/A (not a System Wide Change)
* List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
The hardcoded upper limit of 16 jobs, passed to make via "-j" when you
use either %make_build or make %{?_smp_mflags} in the %build section of
your specfiles, is going away in rawhide. This may result in your jobs
being run with additional parallelization in some situations.
This change will appear in rawhide soon. It is not being made in F25 at
this time; that requires more discussion and will warrant a separate
announcement.
What you need to do:
Nothing. There is a small possibility that the additional parallelism
can tickle some kind of build failure, but the regular Fedora x86_64
builders won't assign more than 16 CPU threads to your jobs in any case
so issues may only appear on other architectures or when building your
packages outside of the Fedora buildsystem. Users with sufficient cores
to see any difference here can rejoice that their builds will use their
hardware.
What you need to do if this actually breaks your package:
For the quickest fix, you can add this at the top of your spec:
%global _smp_ncpus_max 16
This will put the limit back to where it was. There's a reasonable
chance that your package will occasionally still fail even at that level
of parallelism because most issues are going to be related to race
conditions which may depend on all sorts of conditions. Safer still may
be to use a lower value or even disable parallel builds entirely by not
calling make with %{?_smp_mflags}. But in this case you should instead
work with upstream to fix such issues at the source. After all, SMP
machines certainly aren't going away.
Background:
For many years, Fedora's default RPM configuration (via
/usr/lib/rpm/redhat/macros, from the redhat-rpm-macros package) has by
default set an upper limit of "16" for the job count passed to make via
"make -j". The reasons for this are related to build failures that
appeared when SPARC CPUs with large numbers of threads began to appear.
See https://bugzilla.redhat.com/show_bug.cgi?id=1384938 and
https://bugzilla.redhat.com/show_bug.cgi?id=669638 for some references.
There's not really any reason to keep the limit in place. It's
difficult to imagine that there is something SPARC-specific about the
original issues, and it's just not worth defaulting to such a low limit
when there is so much hardware which would go unused.
- J<
= Proposed System Wide Change: AARCH64 - 48-bit VA =
https://fedoraproject.org/wiki/Changes/aarch64-48bitVA
Change owner(s):
* Jeremy Linton < jeremy DOT linton AT arm DOT com >
Enable 48bit VA on AARCH64
== Detailed Description ==
The current aarch64 kernel is using a 42-bit process virtual address
(VA) space and due to the way aarch64 paging works this limits the max
physical address as well. This is fairly limiting for some
applications, but aarch64 processors also have support for 48-bit
VA's. This is actually 1-bit more than the "47-bit" VA's currently
used on x86_64. This change is a fairly minor kernel configuration but
it has caused problems with mozjs and luajit based projects because
they have stored tags in their pointers in the 48th address bit. The
upstream mozjs project has been fixed, and there are a set of changes
outstanding for luajit. Futher there, have been patches applied to
rawhide to support it (bug #1242326, bug #1375305. bug #1375547), but
the packages dependent on js185 require a rebuild due to an ABI
change.
== Scope ==
* Proposal owners:
The kernel config needs to be changed, and the core mozjs/luajit
tagging problems need to be resolved. This can either take the form of
patching the remaining mozjs packages that have not yet been patched
and rebuilding the affected js185 packages, or it can take the form of
moving dependent packages onto mozjs versions that have been patched.
Futher lua needs to either be updated to the latest mainline or the
critical patches need to be applied to the lua versions currently in
use.
* Release engineering:
Release engineering needs to assure the js185 packages are rebuilt.
Peter Robinson has volunteered to assist in this.
* Policies and guidelines: N/A
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
The Fedora Project is pleased to announce the immediate availability of
Fedora 25 Beta, the next big step on our journey to the exciting Fedora
25 release in November.
Fedora's journey is not simply about updating one operating system with
the latest and greatest packages. It's also about innovation for the
many different platforms represented in the Fedora Project:
Workstation, Server, Atomic, and the various Spins. Coordinating the
efforts across the many working groups is no small task, and serves as
a testament to the talent and professionalism found within the Fedora
community.
Download the prerelease from our Get Fedora site:
* Get Fedora 25 Beta Workstation
https://getfedora.org/en/workstation/prerelease/
* Get Fedora 25 Beta Server
https://getfedora.org/en/server/prerelease/
Looking for Cloud edition? Check out the section on Fedora Atomic
below. Or, check out one of our popular variants:
* Get Fedora 25 Beta Spins
https://spins.fedoraproject.org/prerelease
* Get Fedora 25 Beta Labs
https://labs.fedoraproject.org/prerelease
* Get Fedora 25 Beta ARM
https://arm.fedoraproject.org/prerelease
What's New?
===========
As we move into this Beta phase of the Fedora 25 release cycle, what
can users expect?
Fedora-Wide Changes
===================
Some of the changes that will be seen across all aspects of Fedora
include:
* Docker updated to version 1.12
* Support for weaker certificate authorities (i.e., 1024-bit) has
been removed
* Node.js updated to version 6.x, providing a new and better version of
the popular server-side JavaScript engine
* "Secondary architectures" now known as "alternate architectures"
* Rust: Fedora 25 brings the support for the Rust programming
language. Rust is a system programming language which runs
blazingly fast, and prevents almost all crashes, segfaults, and
data races.
* Python: Alongside the "standard" Python versions included in
Fedora 25 (3.5 and 2.7), Python programmers can now install Python
3.4, 3.3, and 2.6 from the repositories to help them run test
suites on multiple Python versions, as well as on PyPy, PyPy3, and
Jython, which were already there.
Fedora Workstation
==================
The Workstation edition of Fedora 25 Beta is going to show off its
stuff, too:
* GNOME 3.22: Fedora 25 includes GNOME 3.22 in its pre-release and in
the Final version, coming soon. Helpful new features include multiple
file renaming, a redesigned keyboard settings tool, and many other UI
improvements across the environment. For full details, refer to the
GNOME 3.22 release notes. https://help.gnome.org/misc/release-notes/3.22/
* New Fedora media writer: The new Fedora Media Writer is a tool that
downloads the latest stable Fedora for you. It then helps you write it
to media such as a USB stick, so you can take Fedora for a spin on your
system. If you like what you see, you can install to your system from
the live environment. The Fedora Media Writer is available for Windows,
Mac OS, and Linux.
* Wayland has been under development for several years. While like most
software it still has some bugs, we believe it's ready to serve as a
default that works for many users. Users can still select the old X11
system if necessary to avoid a problem that affects them.
* Improved Flatpak support in the Software tool: The Software tool
has the ability to install, update, and remove Flatpak software where a
Fedora system is configured to point to a repo that offers it.
* GNOME Shell extensions are no longer checked for compatibility with
the current version of the Shell. This was originally required because
the GNOME interfaces were changing rapidly during the early days of
GNOME 3. Now these interfaces have stabilized, and extensions can
generally be expected to work with new releases. Any problems with an
extension should be reported to the author through the homepage, as
listed on the Extensions site.
Fedora Server
=============
Fedora 25 Server is also going to see some interesting changes in this
cycle, particularly in the Cockpit tool:
* SELinux Troubleshooter module: Cockpit now has a SELinux
Troubleshooter module similar to Fedora Workstation.
If a system encounters an SELinux denial, it will display information
about the issue as well as suggestions for correcting the issue if it
was unexpected. Without the module, an administrator has to notice a
denial occurred, dig through log files for the denial, and search for
workarounds. The SELinux Troubleshooter presents information clearly
and to the point all from the convenience of Cockpit.
* Displays host SSH keys in the system dashboard: Easy to see and
understand what SSH keys are added to the system for connecting to the
machine.
* Includes support for network teaming, Docker volume, and storage
management, as well as the creation of systemd timer units
* Supports multi-step (including two-factor) authentication
FreeIPA identity management system has also been upgraded to 4.4
series:
* Topology management: FreeIPA web UI can now be used to visually
manage topology graph for large deployments
* DNS sites: DNS management in FreeIPA now supports location-specific
placement of services
* Subordinate Certificate Authorities: FreeIPA Certificate Authority
now is able to create subordinate CAs to issue certificates with a
specific scope
* Kerberos Authentication Indicators: Kerberos KDC now takes
Authentication Indicators into account when issuing service tickets.
This allows, for example, to require two-factor authenticated Kerberos
credentials prior to obtaining tickets to a VPN service (supported by
OpenConnect Server).
* Client certificate authentication in Web UI: FreeIPA Web UI and API
end-points now can be configured to log-in with client certificates and
smart cards.
* Active Directory integration improvements: a number of features
were added for enterprise environments
* FreeIPA now supports alternative user principal names and suffixes
from Active Directory and allows FreeIPA users to have Kerberos
aliases
* Active Directory users can now manage own details through the command
line interface (CLI), including public SSH keys and certificates
- In case of trusting multiple Active Directory forests, FreeIPA
is now capable to automatically solve DNS namespace routing conflicts
- FreeIPA framework gained support for external plugins
- Performance of FreeIPA has been optimized for large environments
Fedora Atomic
=============
Fedora Atomic includes a base image suitable for creating virtual
machines, the Fedora Atomic Host image for creating hosts for container
deployment, and a Docker image. This aspect of Fedora represents some
of the most exciting changes, as we build more cloud- and
container-ready tools into Fedora to create a fantastic developer
platform. While Fedora 25 Atomic Host will not be a part of this beta
release, the Fedora Project plans to change Fedora Atomic Host to be on
Fedora 25 base on when generally available.
Fedora Atomic images have new persistent download points:
https://getfedora.org/atomic_qcow2_latesthttps://getfedora.org/atomic_raw_latesthttps://getfedora.org/atomic_vagrant_libvirt_latesthttps://getfedora.org/atomic_vagrant_virtualbox_latest
"We chose to use Fedora Atomic as the base for our Navops Launch -
Kubernetes cluster provisioning solution because our customers trust
and already run Red Hat operating systems. We love the immutable aspect
of Fedora Atomic which is perfect for containerized environments."
Cameron Brunner, Chief Architect, Navops by Univa.
Fedora Atomic has a two-week refresh release cycle with major releases
every six months. It has an easy upgrade path to accommodate rapid
development for supporting the latest applications. It can also be run
as a desktop for those requiring a lightweight and highly
reconfigurable environment.
Still undergoing active development, once stable, Fedora Atomic should
allow the typical Fedora user to easily provision cloud services. User
contributions and experience reports are particularly welcome in
preparing the upcoming version.
Fedora Atomic will replace Fedora Cloud as one of our three Fedora
Editions. The Fedora Cloud Base image will continue to be available for
users wanting to build on a more traditional rpm-based foundation in a
cloud environment. https://getfedora.org/en/cloud/prerelease/
Spins and More
==============
These are not the only iterations of Fedora that are seeing changes in
the Beta release today. Our KDE spin features new and improved packages
for music, video, and personal information management. Xfce includes
imrpovements to the terminal, notifications, and power management.
Mate-Compiz features an update to Mate 1.16 and a complete switch to
the GTK+ 3 toolkit.
Issues and Details
==================
Since this is a beta 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. https://fedoraproject.org/wiki/Common_F25_bugs
For tips on reporting a bug effectively, read "how to file a bug report."
https://fedoraproject.org/wiki/How_to_file_a_bug_report
Release Schedule
================
The full release schedule is available on the Fedora wiki:
https://fedoraproject.org/wiki/Releases/25/Schedule
The current schedule calls for a 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.
Enjoy
Fedora Release Engineering
(Dennis, Peter, Kevin, Mohan, Adam, Randy)
= Proposed Self Contained Change: PHP 7.1 =
https://fedoraproject.org/wiki/Changes/php71
Change owner(s):
* Remi Collet <remi at fedoraproject dot org>
Update the PHP stack in Fedora to latest version 7.1.x
== Detailed Description ==
Update the PHP stack in Fedora to latest version 7.1.x.
* PHP 7.1.0RC3 was released Sep 29th
* PHP 7.1.0 is planed for end of year.
Compatibility for PHP code is very good. PHP 7.1 is the first
compatible version with OpenSSL 1.1.
== Scope ==
* Proposal owners: Check Koschei status. Test with latest version to
ensure compatibility. Work with upstream on bug fixing.
* Other developers: N/A (not a System Wide Change)
* Release engineering: needed mass rebuild (C extensions) done by change owner.
* List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed Self Contained Change: Odoo =
https://fedoraproject.org/wiki/Changes/Odoo
Change owner(s):
* Björn Esser < besser82 AT fedoraproject DOT org >
Odoo is the world's easiest all-in-one management software. It
includes hundreds of integrated business apps: CRM, Accounting,
Inventory, Marketing, eCommerce, Project Management, HR, MRP, etc.
== Detailed Description ==
Odoo is a complete ERP and CRM. The main features are accounting
(analytic and financial), stock management, sales and purchases
management, tasks automation, marketing campaigns, help desk, POS,
etc. Technical features include a distributed server, flexible
workflows, an object database, a dynamic GUI, customizable reports,
and XML-RPC interfaces.
== Scope ==
* Proposal owners: doing the packaging
* Other developers: doing the reviews
* Release engineering: N/A (not a System Wide Change)
* List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic
= Proposed Self Contained Change: Jekyll =
https://fedoraproject.org/wiki/Changes/Jekyll
Change owner(s):
* Björn Esser < besser82 AT fedoraproject DOT org >
Transform your plain text into static websites and blogs.
== Detailed Description ==
Jekyll is a simple, blog-aware, static site generator perfect for
personal, project, or organization sites. Think of it like a
file-based CMS, without all the complexity. Jekyll takes your content,
renders Markdown and Liquid templates, and spits out a complete,
static website ready to be served by Apache, Nginx or another web
server. Jekyll is the engine behind GitHub Pages, which you can use to
host sites right from your GitHub repositories.
Jekyll does what you tell it to do — no more, no less. It doesn't try
to outsmart users by making bold assumptions, nor does it burden them
with needless complexity and configuration. Put simply, Jekyll gets
out of your way and allows you to concentrate on what truly matters:
your content.
== Scope ==
* Proposal owners: doing the packaging
* Other developers: doing the reviews
* Release engineering: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)
--
Jan Kuřík
Platform & Fedora Program Manager
Red Hat Czech s.r.o., Purkynova 99/71, 612 45 Brno, Czech Republic