2wk atomic release candidate: 20170807
by Dusty Mabe
Tomorrow we will attempt to release the 20170807 images.
These images contain the following ostree version/commit:
26.101
f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6
The atomic host VM images are here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170...
The ISO image is here:
https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-26-20170...
The AMIs are here:
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-northeast-1) ami-3623c850 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-1) ami-df0c95bc hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-2) ami-1f2e377c hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-central-1) ami-df822cb0 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-west-1) ami-fd3fc984 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (sa-east-1) ami-0d97e161 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-east-1) ami-d82f00a3 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-1) ami-e8341f88 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-2) ami-20d43558 hvm gp2
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-northeast-1) ami-9a2ec5fc hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-1) ami-3c0c955f hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (ap-southeast-2) ami-6a2f3609 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-central-1) ami-ea802e85 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (eu-west-1) ami-823ccafb hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (sa-east-1) ami-0e97e162 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-east-1) ami-5f2f0024 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-1) ami-d1311ab1 hvm standard
Fedora-Atomic-26-20170807.0.x86_64 EC2 (us-west-2) ami-13d7366b hvm standard
The diff between this and the previous released version is:
ostree diff commit old: 0715ce81064c30d34ed52ef811a3ad5e5d6a34da980bf35b19312489b32d9b83
ostree diff commit new: f6331bcd14577e0ee43db3ba5a44e0f63f74a86e3955604c20542df0b7ad8ad6
Upgraded:
GeoIP-GeoLite-data 2017.06-1.fc26.noarch -> 2017.07-1.fc26.noarch
cockpit-bridge 143-1.fc26.x86_64 -> 147-1.fc26.x86_64
cockpit-docker 143-1.fc26.x86_64 -> 147-1.fc26.x86_64
cockpit-networkmanager 143-1.fc26.noarch -> 147-1.fc26.noarch
cockpit-ostree 143-1.fc26.x86_64 -> 147-1.fc26.x86_64
cockpit-system 143-1.fc26.noarch -> 147-1.fc26.noarch
container-selinux 2:2.20-2.fc26.noarch -> 2:2.21-1.fc26.noarch
criu 3.2.1-2.fc26.x86_64 -> 3.3-2.fc26.x86_64
curl 7.53.1-8.fc26.x86_64 -> 7.53.1-9.fc26.x86_64
dbus 1:1.11.14-1.fc26.x86_64 -> 1:1.11.16-1.fc26.x86_64
dbus-libs 1:1.11.14-1.fc26.x86_64 -> 1:1.11.16-1.fc26.x86_64
dhcp-client 12:4.3.5-7.fc26.x86_64 -> 12:4.3.5-9.fc26.x86_64
dhcp-common 12:4.3.5-7.fc26.noarch -> 12:4.3.5-9.fc26.noarch
dhcp-libs 12:4.3.5-7.fc26.x86_64 -> 12:4.3.5-9.fc26.x86_64
file 5.30-6.fc26.x86_64 -> 5.30-8.fc26.x86_64
file-libs 5.30-6.fc26.x86_64 -> 5.30-8.fc26.x86_64
glusterfs 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
glusterfs-client-xlators 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
glusterfs-fuse 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
glusterfs-libs 3.10.4-1.fc26.x86_64 -> 3.10.4-2.fc26.x86_64
gnupg 1.4.21-2.fc26.x86_64 -> 1.4.22-1.fc26.x86_64
gomtree 0.3.1-1.fc26.x86_64 -> 0.4.0-1.fc26.x86_64
iputils 20161105-2.fc26.x86_64 -> 20161105-5.fc26.x86_64
krb5-libs 1.15.1-15.fc26.x86_64 -> 1.15.1-17.fc26.x86_64
libcurl 7.53.1-8.fc26.x86_64 -> 7.53.1-9.fc26.x86_64
libidn2 2.0.2-1.fc26.x86_64 -> 2.0.3-1.fc26.x86_64
libselinux 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libselinux-python 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libselinux-python3 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libselinux-utils 2.6-6.fc26.x86_64 -> 2.6-7.fc26.x86_64
libsepol 2.6-1.fc26.x86_64 -> 2.6-2.fc26.x86_64
libsolv 0.6.28-1.fc26.x86_64 -> 0.6.28-5.fc26.x86_64
libsss_idmap 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
libsss_nss_idmap 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
libsss_sudo 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
nfs-utils 1:2.1.1-5.rc4.fc26.x86_64 -> 1:2.1.1-5.rc5.fc26.x86_64
nmap-ncat 2:7.40-5.fc26.x86_64 -> 2:7.40-7.fc26.x86_64
nspr 4.14.0-2.fc26.x86_64 -> 4.15.0-1.fc26.x86_64
nss 3.30.2-1.1.fc26.x86_64 -> 3.31.0-1.1.fc26.x86_64
nss-softokn 3.30.2-1.0.fc26.x86_64 -> 3.31.0-1.0.fc26.x86_64
nss-softokn-freebl 3.30.2-1.0.fc26.x86_64 -> 3.31.0-1.0.fc26.x86_64
nss-sysinit 3.30.2-1.1.fc26.x86_64 -> 3.31.0-1.1.fc26.x86_64
nss-tools 3.30.2-1.1.fc26.x86_64 -> 3.31.0-1.1.fc26.x86_64
nss-util 3.30.2-1.0.fc26.x86_64 -> 3.31.0-1.0.fc26.x86_64
oci-register-machine 0-3.8.gitbf6b0f2.fc26.x86_64 -> 0-3.10.gitcbf1b8f.fc26.x86_64
ostree 2017.8-3.fc26.x86_64 -> 2017.9-2.fc26.x86_64
ostree-grub2 2017.8-3.fc26.x86_64 -> 2017.9-2.fc26.x86_64
ostree-libs 2017.8-3.fc26.x86_64 -> 2017.9-2.fc26.x86_64
pcre2 10.23-8.fc26.x86_64 -> 10.23-9.fc26.x86_64
policycoreutils 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
policycoreutils-python 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
policycoreutils-python-utils 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
policycoreutils-python3 2.6-5.fc26.x86_64 -> 2.6-6.fc26.x86_64
python3-sssdconfig 1.15.2-5.fc26.noarch -> 1.15.3-1.fc26.noarch
rpm-ostree 2017.6-3.fc26.x86_64 -> 2017.7-1.fc26.x86_64
runc 1:1.0.0-9.git6394544.fc26.x86_64 -> 1:1.0.1-1.gitc5ec254.fc26.x86_64
selinux-policy 3.13.1-260.1.fc26.noarch -> 3.13.1-260.3.fc26.noarch
selinux-policy-targeted 3.13.1-260.1.fc26.noarch -> 3.13.1-260.3.fc26.noarch
skopeo 0.1.22-1.git5d24b67.fc26.x86_64 -> 0.1.23-2.git1bbd87f.fc26.x86_64
skopeo-containers 0.1.22-1.git5d24b67.fc26.x86_64 -> 0.1.23-2.git1bbd87f.fc26.x86_64
sssd-client 1.15.2-5.fc26.x86_64 -> 1.15.3-1.fc26.x86_64
tmux 2.3-2.fc26.x86_64 -> 2.5-1.fc26.x86_64
vim-minimal 2:8.0.728-1.fc26.x86_64 -> 2:8.0.823-1.fc26.x86_64
There are a lot of updates in this release, including ostree, rpm-ostree,
cockpit and selinux.
Dusty
6 years, 8 months
[atomic-wg] Issue #311: RFE: availability of rawhide containers within the
fedora container registry
by Dusty Mabe
dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
You can build a rawhide rpm and users will get it in an update in a short amount of time (if they are following rawhide). This allows people to use things and give feedback early without having to build things themselves in order to test things out. It would be great if we can get rawhide container images delivered to the registry in much the same way.
I've been told that this will be much easier to do once @maxamillion has everything automated more. It is understood that this ask is really on enabled by that automation. It is not a request for @maxamillion to do more manual work.
``
To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/311
6 years, 8 months