Below are packages that get removed from host without python
Most notable are:
- policycoreutils-python (selinux tools)
|# Copyright: (c) 2018, Dusty Mabe <email@example.com>|
|# GNU General Public License v3.0+ (see COPYING or https://www.gnu.org/licenses/gpl-3.0.txt)|
|# Make coding more python3-ish|
|from __future__ import (absolute_import, division, print_function)|
|__metaclass__ = type|
|# -*- encoding: utf-8 -*-|
|# stub: vagrant-sshfs 1.3.0 ruby lib|
|Gem::Specification.new do |s||
|s.name = "vagrant-sshfs".freeze|
|s.version = "1.3.0"|
|s.required_rubygems_version = Gem::Requirement.new(">= 0".freeze) if s.respond_to? :required_rubygems_version=|
|s.require_paths = ["lib".freeze]|
|s.authors = ["Dusty Mabe".freeze]|
The Fedora Project has changed Fedora Atomic Host to be based on Fedora 25 packages with this general release. Fedora Atomic includes a base disk image suitable for booting virtual machines in local or cloud environments. Fedora Atomic Host allows for creating hosts that are immediately ready for container deployment and can upgraded and rolled back in an atomic manner. 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.
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.
Fedora Atomic will allow the typical Fedora user to easily provision cloud services. User contributions and experience reports are particularly welcome in preparing for future versions.
Fedora Atomic will replace Fedora Cloud as one of our three Fedora Editions. The Fedora Cloud Base im