March 2018 - Atomic Working Group - Fedora mailing-lists

[atomic-wg] Issue #276: Set architecture label in the base container image
by Clement Verna 14 Mar '18

14 Mar '18

cverna added a new comment to an issue you are following: `` I believe this is done now. ``` { "Name": "candidate-registry.fedoraproject.org/f27/greenwave", "Digest": "sha256:abda79af6349e8ff09fb35500477d71c01f4607e90721d60b8d010fe51097aab", "RepoTags": [ "rawhide-container-candidate-49347-20180212083824", "f27-91008-20180218082622", "f27-container-candidate-75796-20180314172356" ], "Created": "2018-03-14T17:27:32.444383Z", "DockerVersion": "1.13.1", "Labels": { "architecture": "x86_64", ``` `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/276

1 0

[atomic-wg] Issue #206: Move nginx container image from Fedora-Dockerfiles GitHub into DistGit
by Clement Verna 14 Mar '18

14 Mar '18

cverna added a new comment to an issue you are following: `` This is now in the registry, so we can close this ticket `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/206

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Dusty Mabe 14 Mar '18

14 Mar '18

The status of the issue: `FLIBS: bogus 'authorative-source-url' in layered images` of project: `atomic-wg` has been updated to: Closed as Fixed by dustymabe. https://pagure.io/atomic-wg/issue/272

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Dusty Mabe 14 Mar '18

14 Mar '18

The issue: `FLIBS: bogus 'authorative-source-url' in layered images` of project: `atomic-wg` has been assigned to `cverna` by dustymabe. https://pagure.io/atomic-wg/issue/272

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Dusty Mabe 14 Mar '18

14 Mar '18

dustymabe added a new comment to an issue you are following: `` thanks! `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/272

1 0

[atomic-wg] Issue #272: FLIBS: bogus 'authorative-source-url' in layered images
by Clement Verna 14 Mar '18

14 Mar '18

cverna added a new comment to an issue you are following: `` This is now fixed. ``` { "Name": "candidate-registry.fedoraproject.org/f27/greenwave", "Digest": "sha256:abda79af6349e8ff09fb35500477d71c01f4607e90721d60b8d010fe51097aab", "RepoTags": [ "rawhide-container-candidate-49347-20180212083824", "f27-91008-20180218082622", "f27-container-candidate-75796-20180314172356" ], "Created": "2018-03-14T17:27:32.444383Z", "DockerVersion": "1.13.1", "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.fedoraproject.org", "build-date": "2018-03-14T17:24:02.218777", ``` we can close this issue `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/272

1 0

Fedora Atomic WG Meeting Minutes 2018-03-14
by Sinny Kumari 14 Mar '18

14 Mar '18

summary: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-14/fedora_atomic… full log: https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-14/fedora_atomic… =================================== #fedora-meeting-1: fedora_atomic_wg =================================== Meeting started by ksinny at 16:30:10 UTC. The full logs are available at https://meetbot.fedoraproject.org/fedora-meeting-1/2018-03-14/fedora_atomic… . Meeting summary --------------- * Roll Call (ksinny, 16:30:25) * Action items from last meeting (ksinny, 16:34:26) * davdunc is working with the Marketplace team at AWS to walk them through it (ksinny, 16:40:22) * davdunc will do further update about AWS scan results of Fedora Atomic Host on atomic-wg ticket (ksinny, 16:43:52) * LINK: https://pagure.io/atomic-wg/issue/339 (ksinny, 16:44:03) * ACTION: jlebon to write blog post for recent rpm-ostree/ostree releases features (ksinny, 16:44:38) * Asian/Australian timezone IRC meeting for community and parts of WG (ksinny, 16:45:13) * LINK: https://pagure.io/atomic-wg/issue/433 (ksinny, 16:45:21) * atomic-wg meeting for Asian/Australian timezone has been scheduled biweekly on Tuesday at 5:00 UTC on #fedora-meeting1 (ksinny, 16:56:01) * LINK: https://pagure.io/atomic-wg/issue/429 (sanja_, 16:59:13) * Atomic VFAD outcome from last week (ksinny, 17:00:44) * LINK: https://pagure.io/atomic-wg/issue/429 (ksinny, 17:00:55) * LINK: VFAD vluejeans recording - https://dustymabe.fedorapeople.org/2018-03-09_Fedora-Atomic-WG-vFAD.mp4 (ksinny, 17:07:44) * LINK: VFAD summary - https://public.etherpad-mozilla.org/p/2018-03-09_Fedora-Atomic-WG-vFAD (ksinny, 17:08:00) * Open Floor (ksinny, 17:08:06) * cverna will be introducing some CI to fedora container which will incldude checks like Dockerfile linter (ksinny, 17:12:30) Meeting ended at 17:23:14 UTC. Action Items ------------ * jlebon to write blog post for recent rpm-ostree/ostree releases features Action Items, by person ----------------------- * jlebon * jlebon to write blog post for recent rpm-ostree/ostree releases features * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * ksinny (74) * sanja_ (69) * zodbot (34) * miabbott (22) * dustymabe (21) * cverna (17) * jlebon (11) * davdunc (7) * roshi (6) * ttomecek (6) * misc (5) * maxamillion (5) * jsmith (4) * jbrooks (3) * kushal (2) * lorbus (2) * strigazi (1) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[atomic-wg] Issue #433: Asian/Australian timezone IRC meeting for community and parts of WG
by Sanja Bonic 14 Mar '18

14 Mar '18

sanja reported a new issue against the project: `atomic-wg` that you are following: `` Several times we've had to say "sorry, no can do" to community members for the Asian/Australian time zone and it would be good to be able to accommodate that timezone with a meeting as well. ## GOAL * including people in the Asian and Australian timezone into the discussions they often cannot be part of live due to time set * gain new voices ## ACTIONS These actions are needed in order to implement such a meeting. * show the meeting char the zodbot commands and explain how to chair an IRC meeting (contact me by replying to the mailing list or via private mail if you're interested but need more information) * go through the atomic-wg meeting items and see if there are some actions your meeting participants can/want to take over * introduce new discussions that are relevant to members which will then be discussed in atomic-wg's Wednesday meeting if relevant, otherwise pagure issues will be created --- This was posted to the mailing list - @sinnykumari has stated she can chair the meetings for that timezone. This ticket is about finding a suitable time. Suggestions in the ticket please - updates to the description can be made then. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/433

3 4

[atomic-wg] PR #436: Update meeting-people.txt
by Jared Smith 14 Mar '18

14 Mar '18

jsmith opened a new pull-request against the project: `atomic-wg` that you are following: `` Update meeting-people.txt `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/pull-request/436

2 1

2wk atomic release candidate:20180314
by Sinny Kumari 14 Mar '18

14 Mar '18

Hi all, We couldn't send Release Candidate for testing earlier due to some issue with AMIs upload. Good news is that issue has been resolved and latest AMIs are available now! Tomorrow we will attempt to release the 20180314 images. These images contain the following ostree version/commits from the Fedora-27-updates-20180313.0 updates run: Version: 27.100 Commit(x86_64): 326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91 Commit(aarch64): ba2aa19d99466c53e614651f014c8b97ae1940f87885b7c7dfed1fb62ae91567 Commit(ppc64le): ca0ea3a6e15b6270aefe3c7b55ffbee3c8bd27707fd6d979cc66b39fc18fa5f4 The atomic host VM images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018031… The ISO images are in the sub-directories under: https://kojipkgs.fedoraproject.org/compose/twoweek/Fedora-Atomic-27-2018031… The AMIs are here: Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-2) ami-a468f8dc hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-1) ami-c20612a2 hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-east-1) ami-a112d1dc hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (sa-east-1) ami-8d5401e1 hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-west-1) ami-e3a8e19a hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-central-1) ami-452e452a hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-2) ami-c022e1a2 hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-1) ami-432d7d3f hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-northeast-1) ami-0a5e146c hvm standard Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-2) ami-916afae9 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-west-1) ami-30071350 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (us-east-1) ami-3e16d543 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (sa-east-1) ami-d75702bb hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-west-1) ami-31a8e148 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (eu-central-1) ami-bd2f44d2 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-2) ami-c623e0a4 hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-southeast-1) ami-f32f7f8f hvm gp2 Fedora-Atomic-27-20180314.0.x86_64 EC2 (ap-northeast-1) ami-c85d17ae hvm gp2 An example of the diff between this and the previous released version (for x86_64) is: ostree diff commit old: da0bd968610aa1e29c5bb37065649407fbbfffa53e63831afdadbd34a3b05327 ostree diff commit new: 326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91 Upgraded: atomic 1.21.1-1.fc27 -> 1.22.1-1.fc27 atomic-registries 1.21.1-1.fc27 -> 1.22.1-1.fc27 audit 2.8.2-1.fc27 -> 2.8.3-1.fc27 audit-libs 2.8.2-1.fc27 -> 2.8.3-1.fc27 audit-libs-python 2.8.2-1.fc27 -> 2.8.3-1.fc27 audit-libs-python3 2.8.2-1.fc27 -> 2.8.3-1.fc27 bridge-utils 1.5-16.fc27 -> 1.6-1.fc27 ceph-common 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 cockpit-bridge 161-1.fc27 -> 163-1.fc27 cockpit-docker 161-1.fc27 -> 163-1.fc27 cockpit-networkmanager 161-1.fc27 -> 163-1.fc27 dhcp-client 12:4.3.6-8.fc27 -> 12:4.3.6-9.fc27 dhcp-common 12:4.3.6-8.fc27 -> 12:4.3.6-9.fc27 dhcp-libs 12:4.3.6-8.fc27 -> 12:4.3.6-9.fc27 dnsmasq 2.78-2.fc27 -> 2.78-6.fc27 fedora-gpg-keys 27-1 -> 27-2 fedora-repos 27-1 -> 27-2 glibc 2.26-24.fc27 -> 2.26-27.fc27 glibc-all-langpacks 2.26-24.fc27 -> 2.26-27.fc27 glibc-common 2.26-24.fc27 -> 2.26-27.fc27 gnupg2 2.2.4-1.fc27 -> 2.2.5-1.fc27 gnupg2-smime 2.2.4-1.fc27 -> 2.2.5-1.fc27 ima-evm-utils 1.0-3.fc27 -> 1.1-2.fc27 kernel 4.15.4-300.fc27 -> 4.15.8-300.fc27 kernel-core 4.15.4-300.fc27 -> 4.15.8-300.fc27 kernel-modules 4.15.4-300.fc27 -> 4.15.8-300.fc27 libblkid 2.30.2-1.fc27 -> 2.30.2-2.fc27 libcephfs2 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libcrypt-nss 2.26-24.fc27 -> 2.26-27.fc27 libfdisk 2.30.2-1.fc27 -> 2.30.2-2.fc27 libgcc 7.3.1-2.fc27 -> 7.3.1-5.fc27 libgomp 7.3.1-2.fc27 -> 7.3.1-5.fc27 libidn2 2.0.4-1.fc27 -> 2.0.4-3.fc27 libmount 2.30.2-1.fc27 -> 2.30.2-2.fc27 librados2 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libradosstriper1 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 librbd1 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libreport-filesystem 2.9.3-1.fc27 -> 2.9.3-2.fc27 librgw2 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 libsmartcols 2.30.2-1.fc27 -> 2.30.2-2.fc27 libsolv 0.6.31-1.fc27 -> 0.6.33-1.fc27 libsss_idmap 1.16.0-6.fc27 -> 1.16.0-8.fc27 libsss_nss_idmap 1.16.0-6.fc27 -> 1.16.0-8.fc27 libsss_sudo 1.16.0-6.fc27 -> 1.16.0-8.fc27 libstdc++ 7.3.1-2.fc27 -> 7.3.1-5.fc27 libunistring 0.9.7-3.fc27 -> 0.9.9-1.fc27 libuuid 2.30.2-1.fc27 -> 2.30.2-2.fc27 mpfr 3.1.5-5.fc27 -> 3.1.6-1.fc27 nspr 4.17.0-1.fc27 -> 4.18.0-1.fc27 nss 3.34.0-1.0.fc27 -> 3.35.0-1.1.fc27 nss-softokn 3.34.0-1.0.fc27 -> 3.35.0-1.0.fc27 nss-softokn-freebl 3.34.0-1.0.fc27 -> 3.35.0-1.0.fc27 nss-sysinit 3.34.0-1.0.fc27 -> 3.35.0-1.1.fc27 nss-tools 3.34.0-1.0.fc27 -> 3.35.0-1.1.fc27 nss-util 3.34.0-1.0.fc27 -> 3.35.0-1.0.fc27 p11-kit 0.23.9-2.fc27 -> 0.23.10-1.fc27 p11-kit-trust 0.23.9-2.fc27 -> 0.23.10-1.fc27 pcre 8.41-5.fc27 -> 8.41-6.fc27 pcre2 10.30-6.fc27 -> 10.31-1.fc27 policycoreutils 2.7-4.fc27 -> 2.7-5.fc27 policycoreutils-python 2.7-4.fc27 -> 2.7-5.fc27 policycoreutils-python-utils 2.7-4.fc27 -> 2.7-5.fc27 policycoreutils-python3 2.7-4.fc27 -> 2.7-5.fc27 publicsuffix-list-dafsa 20171228-1.fc27 -> 20180223-1.fc27 python-cephfs 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python-rados 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python-rbd 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python-rgw 1:12.2.2-1.fc27 -> 1:12.2.3-1.fc27 python2 2.7.14-7.fc27 -> 2.7.14-8.fc27 python2-libs 2.7.14-7.fc27 -> 2.7.14-8.fc27 python3-sssdconfig 1.16.0-6.fc27 -> 1.16.0-8.fc27 runc 2:1.0.0-17.rc4.git9f9c962.fc27 -> 2:1.0.0-19.rc5.git4bb1fe4.fc27 selinux-policy 3.13.1-283.24.fc27 -> 3.13.1-283.26.fc27 selinux-policy-targeted 3.13.1-283.24.fc27 -> 3.13.1-283.26.fc27 sssd-client 1.16.0-6.fc27 -> 1.16.0-8.fc27 subscription-manager-rhsm-certificates 1.21.1-1.fc27 -> 1.21.2-3.fc27 systemd 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-container 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-libs 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-pam 234-9.fc27 -> 234-10.git5f8984e.fc27 systemd-udev 234-9.fc27 -> 234-10.git5f8984e.fc27 util-linux 2.30.2-1.fc27 -> 2.30.2-2.fc27 vim-minimal 2:8.0.1527-1.fc27 -> 2:8.0.1573-1.fc27 xfsprogs 4.12.0-4.fc27 -> 4.15.1-1.fc27 Removed: cockpit-system-161-1.fc27.noarch Added: cockpit-ostree-163-1.fc27.noarch Please test it to ensure that latest Atomic Host is working for you as expected! Thanks, Sinny Kumari

1 0

2024

2023

2022

2021

2020

2019

2018

2017

Atomic Working Group March 2018