F30 Self-Contained Change proposal: Pantheon Desktop
by Ben Cotton
https://fedoraproject.org/wiki/Changes/PantheonDesktop
= Pantheon Desktop =
== Summary ==
The Pantheon desktop environment is the DE that powers elementaryOS. It builds
on GNOME technologies, but utilizes components that were written from scratch
in vala, using the GTK+3 toolkit.
== Owner ==
* Name: [[User:Decathorpe | Fabio Valentini ]]
* Email: decathorpe AT fedoraproject DOT org
* Release notes owner:
== Current status ==
* Targeted release: [[Releases/30 | Fedora 30 ]]
* Last updated: {{REVISIONYEAR}}-{{REVISIONMONTH}}-{{REVISIONDAY2}}
* Tracker bug:
== Detailed Description ==
The Pantheon desktop will be another viable choice for users of fedora. In
particular, this is also interesting for users who like the Pantheon desktop,
but would prefer to use fedora instead of an ubuntu-based distribution.
Most of the components of the Pantheon desktop shell and the applications
developed by elementary have already been packaged for fedora.
== Benefit to Fedora ==
This change will make fedora the first linux distribution other than
elementaryOS to support the Pantheon Desktop environment and elementary
applications.
It gives users of fedora another choice for their desktop environment, and it
gives users of Pantheon and elementary applications the ability to choose a
different linux distribution for the first time.
== Scope ==
=== Proposal owners ===
* investigate improving missing switchboard plugs for fedora support,
and package them:
** Date and Time plug: behavioral differences between fedora / ubuntu
** Locale plug: implement dnf / PackageKit backend for langpack installation
** Power plug: remove dependency on ubuntu-specific patches to
gnome-settings-daemon
** Security and Privacy plug: implement FirewallD backend to replace ufw
* do testing for components not yet in official fedora repositories,
and package them:
** Parental Controls plug: does this actually work on fedora?
** Sharing plug: does this actually work on fedora?
** User Accounts plug: investigate behavioral differences between
fedora / ubuntu
* improve screensaver / lock screen support
** possibly patch Pantheon session components to use standard interfaces
** consider implementing shim for GDM / gnome-screensaver and LightDM
/ light-locker compatibility, or
** consider implementing adapter for translating different DBus calls for this
* create metapackages or comps groups:
** Pantheon Session (Desktop Environment without apps)
** Pantheon Desktop (Desktop Enviromnent with apps)
=== Other developers ===
This is not a system-wide change - however, some components require the latest
releases from the accounts-SSO / signon stack.
In particular, {{package|signon-glib}} needs an update to version 2.0 to allow
packaging the Online Accounts support for switchboard and some elementary
applications.
=== Release engineering ===
No impact
=== Trademark approval ===
N/A - not needed for this Change
This Change is about simply adding Desktop Environment to fedora.
If we decide to make this a spin in the future, that will be a separate Change.
== Upgrade/compatibility impact ==
Packages for the Pantheon DE and elementary applications have been available
since fedora 25 in some cases, and most components have been available since
fedora 27. Upgrading to the latest fedora release brings users the latest
versions of these packages.
However, due to upstream changes, some desktop applications might lose user
settings when upgrading from fedora 28 to 29, because upstream changed their
GSettings path between releases. For that reason, the updates containing these
breaking changes were not pushed to stable releases < 29.
== How To Test ==
* install the Pantheon Desktop Environment:
{{package|pantheon-session-settings}} (metapackages / comps groups not
yet available)
* choose Pantheon session at login
* use the system as usual
* try out elementary applications
* check if screensaver kicks in (possibly doesn't work yet)
== User Experience ==
* no impact for users who don't already have the Pantheon session or
elementary applications installed
* usability and stability improvements for users who already use it
== Dependencies ==
N/A
== Contingency Plan ==
* Contingency mechanism: N/A (not a System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change) - No
* Blocks product? N/A
== Documentation ==
The current status of the project and detailed instructions on how to install
the Pantheon session on fedora are available at
https://decathorpe.com/fedora-elementary-stable-status.html .
== Release Notes ==
The improved Pantheon Desktop Environment and elementary applications found in
the latest release of
[https://medium.com/elementaryos/elementary-os-5-juno-is-here-471dfdedc7b3
elementaryOS 5.0 "Juno"]
will officially be available on fedora 30 as well.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 1 month
Issues with Google Chrome, PyCharm, Steam and other third-party repos
in Fedora 29 prereleases
by Stephen Gallagher
It was discovered[1] a short while ago that, due to a packaging
mistake in the fedora-workstation-repos package, upgrades from Fedora
28->Fedora 29 would replace the /etc/yum.repos.d/*.repo files provided
from that package with their default configuration.
What this meant in practice is that anyone who was using those
repositories in Fedora 28 would find them silently disabled in Fedora
29. In particular, this would mean that they might not notice that
they were not receiving updates, particularly (in the case of Chrome)
security updates.
This has been fixed for F29 Final, but if you have upgraded from
F28->F29 prior to today (such as at the Beta release), you should
check and verify that your expected repos are correctly enabled.
You can verify which repositories on your system are enabled or
disabled by running the command:
`dnf repolist --all`
If you discover that any of your expected repos have been disabled,
they can be re-enabled with:
`dnf config-manager --set-enabled <repo_name>`
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1640626
5 years, 1 month
Fedora 29 Final Release Readiness meeting
by Ben Cotton
Dear all,
Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 29
Final Release Readiness meeting. This meeting will be held on Thursday,
2018-10-18 at 19:00 UTC.
We will meet to make sure we are coordinated and ready for the Final
release of Fedora 29. Please note that this meeting will be held even
if the release is delayed at the Go/No-Go meeting on the same day two
hours earlier.
You may receive this message several times in order to open this
meeting to the teams and to raise awareness, so hopefully more team
representatives will come to this meeting. This meeting works best
when we have representatives from all of the teams.
For more information, see
https://fedoraproject.org/wiki/Release_Readiness_Meetings.
View the meeting on Fedocal:
https://apps.fedoraproject.org/calendar/Fedora%20release/2018/10/18/#m9380
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 1 month
Fedora 30 System-Wide Change: Deprecating /etc/sysconfig/nfs
by Ben Cotton
https://fedoraproject.org/wiki/Changes/nfs.conf
== Summary ==
Deprecate /etc/sysconfig/nfs and only use /etc/nfs.conf to configure
NFS daemons.
== Owner ==
* Name: Steve Dickson
* Email: steved(a)redhat.com
== Detailed Description ==
Since the beginning /etc/sysconfig/nfs has been used to configure
the NFS server daemons by supply command line arguments
to the daemons or commands via SysVinit scripts.
Then systemd(1) came along and the idea of daemons
self-configuration was started. Meaning daemons and commands
would get their configurations from a file, not the command
line like with SysVinit scripts.
Back in late 2016, Neil Brown from SuSe, implemented this changed.
He built into each daemon the ability to read from
one central file, /etc/nfs.conf. See nfs.conf(5) for details.
After this work made it upstream, I a wrote patch that added
back the ability to use /etc/sysconfig/nfs to maintain
backwards compatibility which has lasted for the last few Fedora releases.
I think at this point, the timing is right to introduce this single
file configuration to Fedora 30.
== Benefit to Fedora ==
* Having a single file configuration will help IT automation systems
like Ansible configure NFS servers.
* This change also simplifies the systemd scrips.
* Having two ways of configuring NFS is not desirable. The only
reason there has been no problems is because nobody know about
/etc/nfs.conf
* There is a new command, nfsconf(8), that checks the correctness of
/etc/nfs.conf
== Scope ==
* Proposal owners: Steve Dickson <steved(a)redhat.com>
* Other developers: Justin Mitchell <jumitche(a)redhat.com>
* Release engineering: [https://pagure.io/releng/issue/7864 #7864 F30:
Deprecating /etc/sysconfig/nfs]
** List of deliverables: nfs-utils-2.3.3-1.fc30
* Policies and guidelines: The guidelines to use /etc/nfs.conf are
already being install with nfs.conf(5) and nfsconf(8) manpages
* Trademark approval: No trademarks are being changed so no approval is needed.
== Upgrade/compatibility impact ==
In [https://bugzilla.redhat.com/show_bug.cgi?id=1619270 BZ1619270] a
python script that will convert a sysconfig/nfs config into nfs.conf
config. There are a couple thoughts on how to use it.
On clean installs, when sysconfig/nfs does not exist, sysconfig/nfs
wil still be installed with directions to use nfs.conf to do the
configuration.
When sysconfig/nfs does exist, the configuration will '''not''' be
overwritten, but the systemd scripts will not use the file to
configure NFS.
The two thoughts on how to use python script:
# Have the upgrade run the script and maybe throw out a message that
the configuration has now been moved to nfs.conf
# Throw a message indicating the NFS configuration has changed and
then have the admin run the script
The first thought is probably the cleanest but changing configurations
behind admin's back is not very nice... I am very open on how to use
this script.
== How To Test ==
With the new nfsconf(8) command, the nfs.conf can be tested for
correctness, other than that, we should do the same testing as we do
today
== User Experience ==
After the initial shock, I think users will embrace the new
configuration. Being able to configure NFS via IT automation systems
(aka Ansible) is a step in the right direction. Having a command to
check the correctness of the configuration will be welcome.
== Dependencies ==
There are no dependencies that I know of.
== Contingency Plan ==
* Contingency mechanism: Revert the commit that removed support for
/etc/sysconfig/nfs.
* Contingency deadline: 2019-03-05 (Beta Freeze)
* Blocks release? No
* Blocks product? No
== Documentation ==
There are two man pages, nfs.conf(5) and nfsconf(8).
== Release Notes ==
The new way of configuring NFS should be release noted.
--
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
5 years, 1 month
Fedora Infrastructure Planned Outage 2018-10-03
by Stephen John Smoogen
l;dr: All Fedora Infrastructure systems will be updated and rebooted
over this week.
Systems that can be done outside of the planned outage.
2018-10-01 21:00 UTC Staging and downloads
2018-10-02 throughout the 'day' single proxies will be updated/rebooted.
2018-10-03 production systems including all build servers will be rebooted.
=== Planned Outage - Build/Production - 2018-10-03 21:00 UTC
There will be an outage starting at 2018-10-03 21:00 UTC,
which will last approximately 4 hours.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2018-10-03 21:00UTC'
Reason for outage:
Various kernel, library, and general security updates need to be
applied to all servers. Due to the kernel, glibc, and other updates..
all systems will be rebooted afterwords
Affected Services:
All build, production and related services will be affected.
Ticket Link:
https://pagure.io/fedora-infrastructure/issue/7272
Please join #fedora-admin or #fedora-noc on irc.freenode.net
or add comments to the ticket for this outage above.
--
Stephen J Smoogen.
5 years, 2 months
