Re: [atomic-announce] Final EOL Fedora Atomic Host Two Week Release Announcement: 29.20191126.0

[Sinny Kumari]

On Tue, Dec 3, 2019 at 12:03 AM Mike Nguyen  wrote:

> With Fedora 29 reaching End Of Life, this will be the final Fedora Atomic
> Host release (based on the Fedora 29 stream).  Fedora Atomic Host will no
> longer receive any updates.  More details can be found at
> https://www.projectatomic.io/blog/2019/11/fedora-atomic-host-nearing-eol/
>
> Thank you for using Fedora Atomic Host and your contributions to the
> project.  We would love it if you please give Fedora CoreOS preview a try
> and help us get it towards stable.  Documentation and download links can be
> found at https://getfedora.org/coreos/.
>
> Thank you,
> Fedora Release Engineering
>
>
>
> The final Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20191126.0
> Commit(x86_64):
> 563185fc932b93558a56dddb1f5688b941cc2d88dc8b400a3833766c68c2d2f1
> Commit(aarch64):
> de42987e180698a76934a75333ef438a2050b71704a33377bd85356e197efa06
> Commit(ppc64le):
> 4f30217814d71c3cef2a16ce8a9b834c1515466d54550ec65b7fc69625cd962a
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191126.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191126.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20191126.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191126.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191126.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20191126.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191126.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191126.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191126.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191126.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20191126.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191126.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20191126.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191126.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20191126.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191126.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191126.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20191126.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest

Fedora Atomic Host Two Week Release Announcement: 29.20191113.1

[Sinny Kumari]

A new Fedora Atomic Host update is available via an OSTree update:

Version: 29.20191113.1

Commit(x86_64): 2cb7f9eff5277633f3cf27add9b43789bcac908239d1d694374ac3fe3abae0bc

Commit(aarch64):
136d3d5270b5dc95b5ba87ef0ceaa0a9a356b5c7eae88ba42fc6a0455d273674

Commit(ppc64le):
8ddb6e0d8300025316d364c87c4320e4126f4ec78eb87fd38b66af3afe286802

We are releasing images from multiple architectures but please note

that x86_64 architecture is the only one that undergoes automated

testing at this time.

Existing systems can be upgraded in place via e.g. `atomic host upgrade`.

Corresponding image media for new installations can be downloaded from:

https://getfedora.org/en/atomic/download/

Alternatively, image artifacts can be found at the following links:

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191113.1.aarch64.qcow2

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191113.1.aarch64.raw.xz

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20191113.1.iso

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191113.1.ppc64le.qcow2

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191113.1.ppc64le.raw.xz

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20191113.1.iso

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191113.1.x86_64.qcow2

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191113.1.x86_64.raw.xz

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191113.1.x86_64.vagrant-libvirt.box

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191113.1.x86_64.vagrant-virtualbox.box

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20191113.1.iso

Respective signed CHECKSUM files can be found here:

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191113.1-aarch64-CHECKSUM

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20191113.1-aarch64-CHECKSUM

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191113.1-ppc64le-CHECKSUM

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20191113.1-ppc64le-CHECKSUM

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191113.1-x86_64-CHECKSUM

https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191113.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20191113.1-x86_64-CHECKSUM

For direct download, the "latest" targets are always available here:

x86_64:

https://getfedora.org/atomic_qcow2_x86_64_latest

https://getfedora.org/atomic_raw_x86_64_latest

https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest

https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest

https://getfedora.org/atomic_dvd_ostree_x86_64_latest

aarch64:

https://getfedora.org/atomic_qcow2_aarch64_latest

https://getfedora.org/atomic_raw_aarch64_latest

https://getfedora.org/atomic_dvd_ostree_aarch64_latest

ppc64le:

https://getfedora.org/atomic_qcow2_ppc64le_latest

https://getfedora.org/atomic_raw_ppc64le_latest

https://getfedora.org/atomic_dvd_ostree_ppc64le_latest

Filename fetching URLs are available here:

x86_64:

https://getfedora.org/atomic_qcow2_x86_64_latest_filename

https://getfedora.org/atomic_raw_x86_64_latest_filename

https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename

https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename

https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename

aarch64:

https://getfedora.org/atomic_qcow2_aarch64_latest_filename

https://getfedora.org/atomic_raw_aarch64_latest_filename

https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename

ppc64le:

https://getfedora.org/atomic_qcow2_ppc64le_latest_filename

https://getfedora.org/atomic_raw_ppc64le_latest_filename

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 29.20191013.0

[Sinny Kumari]

On Mon, Oct 14, 2019 at 11:00 PM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20191013.0
> Commit(x86_64):
> 1766b4526f1a738ba1e6e0a66264139f65340bcc28e7045f10cbe6d161eb1925
> Commit(aarch64):
> e2081395bb82ba1653da77e28e69448dd508613db1855ef52834087c67e67c05
> Commit(ppc64le):
> 06199fc2df5f3edbbcfbf2867662bdd7ce6eae6fbc31b9123ee6f57244b84be0
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191013.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191013.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20191013.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191013.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191013.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20191013.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191013.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191013.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191013.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20191013.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20191013.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20191013.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20191013.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20191013.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20191013.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20191013.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20191013.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20191013.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: Fedora Atomic Host Two Week Release Announcement: 29.20190903.0

[Sinny Kumari]

On Tue, Sep 3, 2019 at 6:31 PM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20190903.0
> Commit(x86_64):
> dd9fc5fd415d08b2f5aff025da85d3a4839fcae1f70b1a444c4a5ef31e3ee253
> Commit(aarch64):
> 3dd79159e79a4259ee97159ea34c318f12c856a83dd735a8e3a9a62e644fcc63
> Commit(ppc64le):
> becd5399c3138944eaba68f7c082ea192a264d0b333513c15da54f847e91abbb
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190903.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190903.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20190903.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190903.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190903.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190903.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190903.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190903.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190903.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190903.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20190903.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190903.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20190903.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190903.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20190903.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190903.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190903.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20190903.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename

Re: Fedora-29-updates-testing-20190819.0 compose check report

[Sinny Kumari]

>From the build logs [1] [2] , it looks like disk got full which could be
builder specific. We can dig in more if it happens again.

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=37134473
[2]
https://kojipkgs.fedoraproject.org//work/tasks/4473/37134473/screenshot.ppm

On Mon, Aug 19, 2019 at 8:33 AM Fedora compose checker <
rawh...@fedoraproject.org> wrote:

> Missing expected images:
>
> Atomichost raw-xz x86_64
> Atomichost qcow2 x86_64
>
> Passed openQA tests: 2/2 (x86_64)
> --
> Mail generated by check-compose:
> https://pagure.io/fedora-qa/check-compose
> ___
> Atomic Working Group mailing list -- ato...@lists.fedoraproject.org
> To unsubscribe send an email to atomic-le...@lists.fedoraproject.org
> Fedora Code of Conduct:
> https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/ato...@lists.fedoraproject.org
>


-- 
http://sinny.io/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 29.20190708.0

[Sinny Kumari]

On Tue, Jul 9, 2019 at 1:59 AM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20190708.0
> Commit(x86_64):
> e4c5affdeff6cbe5c494cbad48419d9746c017f17b46e97ae83639f6328989ce
> Commit(aarch64):
> 58d13ffe3fff2cba3736dfc6a1158991e5d8845fa16b8b501b6b03c7fead3af3
> Commit(ppc64le):
> ea961b706191a4fd6bab4e5b6dda2f5250497a0d1b7fc1831a11796b5af6f57e
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190708.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190708.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20190708.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190708.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190708.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190708.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190708.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190708.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190708.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190708.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20190708.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190708.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20190708.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190708.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20190708.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190708.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190708.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20190708.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 29.20190121.0

[Sinny Kumari]

On Tue, Jan 22, 2019 at 11:54 AM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20190121.0
> Commit(x86_64):
> cdcbea2ccac7804770be806befd30895457de080d1525ee6050a5bebdfeefeb7
> Commit(aarch64):
> 327fc6d2c7c8dc44733b6cfa5e8db3711ba15a46022862688427b162cd55d9cf
> Commit(ppc64le):
> 2169d9961bce21578367d145c86cb4765a2bda58411a7e5a4621d15731e9c2db
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190121.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190121.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20190121.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190121.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190121.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190121.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190121.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190121.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190121.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190121.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20190121.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190121.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20190121.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190121.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20190121.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190121.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190121.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20190121.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 29.20190107.0

[Sinny Kumari]

On Tue, Jan 8, 2019 at 12:52 PM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20190107.0
> Commit(x86_64):
> 822093aa47c985d24d5f3a40ad213d68f7734be3bff872c757d39315048691a4
> Commit(aarch64):
> 998b38c152b6808d7fa277eddadf87e5b2f73d923793328cff7985e67fa401bd
> Commit(ppc64le):
> 82d4e740198440c3f7fcab41aaea496add51fc2d54566d933e04b11deae35825
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190107.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190107.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20190107.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190107.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190107.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190107.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190107.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190107.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190107.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190107.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20190107.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190107.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20190107.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190107.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20190107.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190107.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190107.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20190107.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: Fedora Atomic Host Two Week Release Announcement: 29.20181210.0

[Sinny Kumari]

On Mon, Dec 10, 2018 at 10:07 PM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20181210.0
> Commit(x86_64):
> 0232d115fa5f1d4609dcf2eb90de228ccb08dbad1134b30a555d92ae676bb92d
> Commit(aarch64):
> 96281d24a61eaa25865dd7f79bea81886f5f24ef97c6610a5eb617d27c1bc432
> Commit(ppc64le):
> 361f682d18e53af9947d36d21fb04100ecedb6870e48933f06289d6c48fe0878
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20181210.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20181210.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20181210.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20181210.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20181210.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20181210.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20181210.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20181210.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20181210.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20181210.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20181210.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20181210.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20181210.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20181210.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20181210.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20181210.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181210.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20181210.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 29.20181113.0

[Sinny Kumari]

On Tue, Nov 13, 2018 at 10:14 PM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 29.20181113.0
> Commit(x86_64):
> 89bfa708d349a5856cc5cd3be441c07e1f96d0be2aa97e2b676f6004e7f6abed
> Commit(aarch64):
> d0e58aa379b37a39fd5e29b8d87d747b5a3a6aeaef91de751f7abd39fbbe2d51
> Commit(ppc64le):
> d8c4215c936a5e064dc4f1c9dbde5f08f77535995a7b3eddfed1fe2bad784a45
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20181113.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20181113.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20181113.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20181113.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20181113.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20181113.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20181113.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20181113.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20181113.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20181113.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20181113.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20181113.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20181113.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20181113.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20181113.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20181113.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20181113.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20181113.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: Fedora Atomic Host Two Week Release Announcement: 28.20181007.0

[Sinny Kumari]

On Mon, Oct 8, 2018 at 7:04 PM  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20181007.0
> Commit(x86_64):
> 8df48fa2e70ad1952153ae00edbba08ed18b53c3d4095a22985d1085f5203ac6
> Commit(aarch64):
> 6b8d55e59750cfe8e490dbfa63ab12ccdb0a231a4d58e1b074793dddb6c49648
> Commit(ppc64le):
> 4a95f167ee4063556daf59e13b85f7d84fb1073db4150c8f3dd6a4a36c80523f
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0.aarch64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0.aarch64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20181007.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0.ppc64le.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0.ppc64le.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20181007.0.iso
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0.x86_64.qcow2
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0.x86_64.raw.xz
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20181007.0.x86_64.vagrant-libvirt.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20181007.0.x86_64.vagrant-virtualbox.box
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20181007.0.iso
>
> Respective signed CHECKSUM files can be found here:
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20181007.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20181007.0-aarch64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20181007.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20181007.0-ppc64le-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20181007.0-x86_64-CHECKSUM
>
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20181007.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20181007.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 28.20180923.0

[Sinny Kumari]

On Wed, Sep 26, 2018 at 3:43 PM Sayan Chowdhury  wrote:

> On Tue, Sep 25, 2018 at 8:49 PM  wrote:
> >
> >
> > A new Fedora Atomic Host update is available via an OSTree update:
> >
> > Version: 28.20180923.0
> > Commit(x86_64):
> 8b82902a0ca203645e9e288b8a0bbf9fe525749ec67cd674e6715daa64e5b7dd
> > Commit(aarch64):
> 9303c782b619bfeccfc8b0fb86a16ebf40b48c7c65e08d16c999b1618fd8b417
> > Commit(ppc64le):
> d789fe23cb4bba0d5d24fd345358d122b8caef97ab2572ad23292025823888ff
> >
> >
> > We are releasing images from multiple architectures but please note
> > that x86_64 architecture is the only one that undergoes automated
> > testing at this time.
> >
> > Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
> >
> > Corresponding image media for new installations can be downloaded from:
> >
> > https://getfedora.org/en/atomic/download/
> >
> > Alternatively, image artifacts can be found at the following links:
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0.aarch64.qcow2
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0.aarch64.raw.xz
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-28-20180923.0.iso
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0.ppc64le.qcow2
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0.ppc64le.raw.xz
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-28-20180923.0.iso
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0.x86_64.qcow2
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0.x86_64.raw.xz
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180923.0.x86_64.vagrant-libvirt.box
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-28-20180923.0.x86_64.vagrant-virtualbox.box
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-28-20180923.0.iso
> >
> > Respective signed CHECKSUM files can be found here:
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/images/Fedora-AtomicHost-28-20180923.0-aarch64-CHECKSUM
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-28-20180923.0-aarch64-CHECKSUM
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-28-20180923.0-ppc64le-CHECKSUM
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-28-20180923.0-ppc64le-CHECKSUM
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/images/Fedora-AtomicHost-28-20180923.0-x86_64-CHECKSUM
> >
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-28-updates-20180923.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-28-20180923.0-x86_64-CHECKSUM
> >
> > For direct download, the "latest" targets are always available here:
> > x86_64:
> > https://getfedora.org/atomic_qcow2_x86_64_latest
> > https://getfedora.org/atomic_raw_x86_64_latest
> > https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> > https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> > https://getfedora.org/atomic_dvd_ostree_x86_64_latest
> >
> > aarch64:
> > https://getfedora.org/atomic_qcow2_aarch64_latest
> > https://getfedora.org/atomic_raw_aarch64_latest
> > https://getfedora.org/atomic_dvd_ostree_aarch64_latest
> >
> > ppc64le:
> > https://getfedora.org/atomic_qcow2_ppc64le_latest
> > https://getfedora.org/atomic_raw_ppc64le_latest
> > https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
> >
> > Filename fetching URLs are available here:
> > x86_64:
> > https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> > https://getfedora.org/atomic_raw_x86_64_latest_filename
> > https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> >
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> > https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
> >
> > aarch64:
> 

[Test-Announce] Re: Fedora 29 Candidate Beta-1.5 Available Now!

[Sinny Kumari]

Cloud Base and Atomic Host AMIs are available to test for various regions.

Cloud Base AMIs are here:
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-northeast-1
ami-0a24cb0b129391f91  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-northeast-2
ami-025a265da1a333635  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-south-1
ami-032f4d743f5c677bb  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-southeast-1
ami-0e014a47fd58202e1  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-southeast-2
ami-04f1eafc8d8cef238  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ca-central-1
ami-0423d7ead4d36fc13  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  eu-central-1
ami-0097aa31bfa6d957f  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  eu-west-1
ami-08779cabb5a70b267  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  eu-west-2
ami-0a2cafce4e146fa6f  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  sa-east-1
ami-07c85de0c364891f8  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  us-east-1
ami-0a5a4a027c594a3ee  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  us-west-1
ami-0db1697b106a42511  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  us-west-2
ami-0ae9bebb94df0dfb2  hvm  standard
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-northeast-1
ami-05cb9a208a11375a0  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-northeast-2
ami-03f32d94e35e8ee16  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-south-1
ami-08a95ab722459da46  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-southeast-1
ami-0b19c7c9c9f0e71b6  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ap-southeast-2
ami-03df355d88c07b195  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  ca-central-1
ami-02f4f27b3c8cda214  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  eu-central-1
ami-04077be43a1aa41cf  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  eu-west-1
ami-0fa29ca888e696593  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  eu-west-2
ami-09a9fa30546daec7b  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  sa-east-1
ami-0fe4b2f13a9c10b68  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  us-east-1
ami-0ef357b3f269575be  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  us-west-1
ami-0e24cc3e688d75512  hvm  gp2
Fedora-Cloud-Base-29_Beta-1.5.x86_64  us-west-2
ami-0e2412f7959332635  hvm  gp2

Atomic Host AMIs are here:
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-northeast-1
ami-0c8c3a243f8fa9389  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-northeast-2
ami-0f516fa511f7f5e73  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-south-1
ami-007c9eb1578a4688d  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-southeast-1
ami-0a0efd1bb6204159e  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-southeast-2
ami-04544eb8e7d88954e  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  ca-central-1
ami-0039a676512a0794e  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  eu-central-1
ami-0ba7d4f7df3adecd4  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  eu-west-1
ami-025df16716016af3a  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  eu-west-2
ami-0dd9376c148025bda  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  sa-east-1
ami-05851e0e3ba8fa569  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  us-east-1
ami-03630244e374b092b  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  us-west-1
ami-0455c73d39bb9d922  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  us-west-2
ami-08494e1090a21e688  hvm  standard
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-northeast-1
ami-0751c7e8531851ba0  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-northeast-2
ami-02d3a759042127f7a  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-south-1
ami-0ca9ba91af3aa6d22  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-southeast-1
ami-0ab9ca1d8d1e8353f  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  ap-southeast-2
ami-00383f891422b1ed2  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  ca-central-1
ami-075e5b73667dedb33  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  eu-central-1
ami-0716bdf9a47a23af4  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  eu-west-1
ami-0ed1063c442c97e39  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  eu-west-2
ami-0ab7b595091a81399  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  sa-east-1
ami-03952c6395be8a35d  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  us-east-1
ami-0be45426d63c7cf4a  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  us-west-1
ami-09f6c41ffc8c38a92  hvm  gp2
Fedora-AtomicHost-29_Beta-1.5.x86_64  us-west-2
ami-0e640910b38a99ad6  hvm  gp2


On Thu, Sep 20, 2018 at 11:57 AM  wrote:

> According to the schedule [1], Fedora 29 Candidate Beta-1.5 is now
> available for testing. Please help us complete all the validation
> testing! For more information on release validation testing, see:
> https://fedoraproject.org/wiki/QA:Release_validation_test_plan
>
> Test coverage information for the current release can be seen at:
> https://www.happyassassin.net/testcase_stats/29
>
> You can see all results, find 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 28.20180804.0

[Sinny Kumari]

On Wed, Aug 8, 2018 at 3:29 PM,  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180804.0
> Commit(x86_64): 5633f5b369b166d104720a4da31da1
> ac6b5e3c0de5c5bae70cb40a850dede502
> Commit(aarch64): 99267073f82f4d7161bb36c5229d4d
> cf0518503ea8eda161483278053a68df10
> Commit(ppc64le): 6b4f16f98c5609629bb1bac2f64e69
> c930d9e42a7bd13aca2fcae0d928c0a666
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/aarch64/images/Fedora-AtomicH
> ost-28-20180806.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/aarch64/images/Fedora-AtomicH
> ost-28-20180806.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/aarch64/iso/Fedora-AtomicHost
> -ostree-aarch64-28-20180806.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/ppc64le/images/Fedora-AtomicH
> ost-28-20180806.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/ppc64le/images/Fedora-AtomicH
> ost-28-20180806.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost
> -ostree-ppc64le-28-20180806.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-28-20180806.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-28-20180806.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-Vagrant-28-20180806.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-Vagrant-28-20180806.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-
> ostree-x86_64-28-20180806.0.iso
>
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/aarch64/images/Fedora-AtomicH
> ost-28-20180806.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/aarch64/iso/Fedora-AtomicHost
> -28-20180806.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/ppc64le/images/Fedora-AtomicH
> ost-28-20180806.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost
> -28-20180806.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-28-20180806.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180806.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-
> 28-20180806.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 28.20180722.0

[Sinny Kumari]

On Tue, Jul 24, 2018 at 9:42 PM,  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180722.0
> Commit(x86_64): 106a7095fd46741948ba60dbd05866
> 68ae7abe6336671444ec790d7541a88778
> Commit(aarch64): e4cb87910b0729293453004293c1aa
> c3d676b8683f4147a6fb3975092b53810f
> Commit(ppc64le): 8f316b541744eafb126c06128e1af6
> 14f6ab5dccd72a8b722db4b0e295194115
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/aarch64/images/Fedora-
> AtomicHost-28-20180723.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/aarch64/images/Fedora-
> AtomicHost-28-20180723.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/aarch64/iso/Fedora-AtomicHost
> -ostree-aarch64-28-20180723.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/ppc64le/images/Fedora-
> AtomicHost-28-20180723.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/ppc64le/images/Fedora-
> AtomicHost-28-20180723.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost
> -ostree-ppc64le-28-20180723.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/x86_64/images/Fedora-
> AtomicHost-28-20180723.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/x86_64/images/Fedora-
> AtomicHost-28-20180723.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/x86_64/images/Fedora-
> AtomicHost-Vagrant-28-20180723.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/x86_64/images/Fedora-
> AtomicHost-Vagrant-28-20180723.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-
> ostree-x86_64-28-20180723.0.iso
>
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/aarch64/images/Fedora-
> AtomicHost-28-20180723.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/aarch64/iso/Fedora-AtomicHost
> -28-20180723.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/ppc64le/images/Fedora-
> AtomicHost-28-20180723.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost
> -28-20180723.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/x86_64/images/Fedora-
> AtomicHost-28-20180723.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180723.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-
> 28-20180723.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 28.20180708.0

[Sinny Kumari]

On Tue, Jul 10, 2018 at 8:28 PM,  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180708.0
> Commit(x86_64): 5736e832b1fd59208465458265136f
> be2aa4ba89517d8bdcc91bc84724f40a8e
> Commit(aarch64): 4066f8e2f2f13709d0cf9a562a1f24
> cd2459bdc9f13e1ea1034a367586f79dac
> Commit(ppc64le): a197bd8bfb8cf039e8f2cccf7f743c
> bb92dde30fffa6ccb0729f8ad13e757b17
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/aarch64/images/
> Fedora-AtomicHost-28-20180709.0.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/aarch64/images/
> Fedora-AtomicHost-28-20180709.0.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/aarch64/iso/Fedora-
> AtomicHost-ostree-aarch64-28-20180709.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/ppc64le/images/
> Fedora-AtomicHost-28-20180709.0.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/ppc64le/images/
> Fedora-AtomicHost-28-20180709.0.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/ppc64le/iso/Fedora-
> AtomicHost-ostree-ppc64le-28-20180709.0.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/x86_64/images/
> Fedora-AtomicHost-28-20180709.0.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/x86_64/images/
> Fedora-AtomicHost-28-20180709.0.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/x86_64/images/
> Fedora-AtomicHost-Vagrant-28-20180709.0.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/x86_64/images/
> Fedora-AtomicHost-Vagrant-28-20180709.0.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/x86_64/iso/Fedora-
> AtomicHost-ostree-x86_64-28-20180709.0.iso
>
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/aarch64/images/
> Fedora-AtomicHost-28-20180709.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/aarch64/iso/Fedora-
> AtomicHost-28-20180709.0-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/ppc64le/images/
> Fedora-AtomicHost-28-20180709.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/ppc64le/iso/Fedora-
> AtomicHost-28-20180709.0-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/x86_64/images/
> Fedora-AtomicHost-28-20180709.0-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-28-20180709.0/AtomicHost/x86_64/iso/Fedora-
> AtomicHost-28-20180709.0-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest
> https://getfedora.org/atomic_raw_x86_64_latest
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest
> https://getfedora.org/atomic_raw_aarch64_latest
> https://getfedora.org/atomic_dvd_ostree_aarch64_latest
>
> ppc64le:
> https://getfedora.org/atomic_qcow2_ppc64le_latest
> https://getfedora.org/atomic_raw_ppc64le_latest
> https://getfedora.org/atomic_dvd_ostree_ppc64le_latest
>
> Filename fetching URLs are available here:
> x86_64:
> https://getfedora.org/atomic_qcow2_x86_64_latest_filename
> https://getfedora.org/atomic_raw_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
> https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename
>
> aarch64:
> https://getfedora.org/atomic_qcow2_aarch64_latest_filename
> https://getfedora.org/atomic_raw_aarch64_latest_filename
> 

Re: Fedora Atomic Host Two Week Release Announcement: 28.20180625.0

[Sinny Kumari]

On Tue, Jun 26, 2018 at 7:51 PM,  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 28.20180625.0
> Commit(x86_64): fbed0e26736fc189129f80e9547bfd
> 71497377ca49f0cfd421f173667f5ea825
> Commit(aarch64): b5067e5e11d6a5b178b782e91fef80
> 820cc8ce04b1d57dc076a3dfaa7d490a17
> Commit(ppc64le): 721a3c8fe5dedf496cd1c796dba125
> 991d764d3e08e5a77aa1e5f0ba26ef635f
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/aarch64/images/Fedora-AtomicH
> ost-28-20180625.1.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/aarch64/images/Fedora-AtomicH
> ost-28-20180625.1.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/aarch64/iso/Fedora-AtomicHost
> -ostree-aarch64-28-20180625.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/ppc64le/images/Fedora-AtomicH
> ost-28-20180625.1.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/ppc64le/images/Fedora-AtomicH
> ost-28-20180625.1.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost
> -ostree-ppc64le-28-20180625.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-28-20180625.1.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-28-20180625.1.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-Vagrant-28-20180625.1.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-Vagrant-28-20180625.1.x86_64.vagrant-virtualbox.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-
> ostree-x86_64-28-20180625.1.iso
>
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/aarch64/images/Fedora-AtomicH
> ost-28-20180625.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/aarch64/iso/Fedora-AtomicHost
> -28-20180625.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/ppc64le/images/Fedora-AtomicH
> ost-28-20180625.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/ppc64le/iso/Fedora-AtomicHost
> -28-20180625.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/x86_64/images/Fedora-AtomicHo
> st-28-20180625.1-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-A
> tomic-28-20180625.1/AtomicHost/x86_64/iso/Fedora-AtomicHost-
> 28-20180625.1-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
>
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
>
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
>
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_Image
> _Download_Links
>
> Do note that it can take some of the mirrors up to 12 hours to "check-in"
> at
> their own discretion.
>
> Thank you,
> Fedora Release Engineering
>

This release contains updated version of kernel, podman and cockpit.
Another noticeable change is that AMIs for all regions are now migrated
successfully to use longer resource IDs including eu-central-1 and
sa-east-1.
Adding to that https://getfedora.org/en/atomic/download/ now includes
download link 

Re: [atomic-devel] Fedora 28 Atoimic Host RC 1.1 available for testing

[Sinny Kumari]

On Thu, Apr 26, 2018 at 7:45 PM, Dusty Mabe <du...@dustymabe.com> wrote:

>
>
> On 04/26/2018 08:54 AM, Sinny Kumari wrote:
> >
> >
> > On Thu, Apr 26, 2018 at 2:05 AM, Dusty Mabe <du...@dustymabe.com
> <mailto:du...@dustymabe.com>> wrote:
> >
> > The Atomic Host compose based on RC 1.1 is available for testing now.
> >
> > The toplevel directory is: https://kojipkgs.fedoraproject.org/compose/
> twoweek/Fedora-Atomic-28-20180425.0 <https://kojipkgs.
> fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180425.0>
> >
> > The cloud images are under the compose/AtomicHost/$arch/images/
> directories.
> > The ISO images are under the compose/AtomicHost/$arch/iso/ directories.
> >
> >
> >> Tested Atomic Host RC 1.1:
> >> * Both ISO and cloud images look good  on all arches
> >> * AMIs are working as expected including openshift cluster set-up
> >> * Ran couple of podman commands and it worked as expected on all arches,
> >>   One thing I noticed that, since both docker and podman are available
> on host,
> >>   running "podman run -t fedora bash" didn't have network connectivity
> >>   inside container. So, I ran podman with option --net=host and network
> was fine
> >>   later on.
>
>
> Weird. I think I'm seeing the same thing. If I disable docker and reboot I
> get the
> expected behavior. For now we can just advise to disable docker if they
> want
> to use podman. It doesn't make a lot of sense to try to use both on the
> same system
> anyway.
>
> Sinny can you open an issue for this in atomic-wg and we'll ask brent for
> input.
>

Created atomic-wg issue - https://pagure.io/atomic-wg/issue/460


> Dusty
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [atomic-devel] Fedora 28 Atoimic Host RC 1.1 available for testing

[Sinny Kumari]

On Thu, Apr 26, 2018 at 7:45 PM, Dusty Mabe <du...@dustymabe.com> wrote:

>
>
> On 04/26/2018 08:54 AM, Sinny Kumari wrote:
> >
> >
> > On Thu, Apr 26, 2018 at 2:05 AM, Dusty Mabe <du...@dustymabe.com
> <mailto:du...@dustymabe.com>> wrote:
> >
> > The Atomic Host compose based on RC 1.1 is available for testing now.
> >
> > The toplevel directory is: https://kojipkgs.fedoraproject.org/compose/
> twoweek/Fedora-Atomic-28-20180425.0 <https://kojipkgs.
> fedoraproject.org/compose/twoweek/Fedora-Atomic-28-20180425.0>
> >
> > The cloud images are under the compose/AtomicHost/$arch/images/
> directories.
> > The ISO images are under the compose/AtomicHost/$arch/iso/ directories.
> >
> >
> >> Tested Atomic Host RC 1.1:
> >> * Both ISO and cloud images look good  on all arches
> >> * AMIs are working as expected including openshift cluster set-up
> >> * Ran couple of podman commands and it worked as expected on all arches,
> >>   One thing I noticed that, since both docker and podman are available
> on host,
> >>   running "podman run -t fedora bash" didn't have network connectivity
> >>   inside container. So, I ran podman with option --net=host and network
> was fine
> >>   later on.
>
>
> Weird. I think I'm seeing the same thing. If I disable docker and reboot I
> get the
> expected behavior. For now we can just advise to disable docker if they
> want
> to use podman. It doesn't make a lot of sense to try to use both on the
> same system
> anyway.
>

Agree with you. I also tried other way:
On a machine with F28 RC 1.1 installed, I first installed podman and
launched a container
using `podman run -t fedora bash` , network was fine. Next, I installed
docker and launched
container using docker, now no network inside docker container. Looks like
both conflict
each other.


>
> Sinny can you open an issue for this in atomic-wg and we'll ask brent for
> input.
>
> Dusty
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [atomic-devel] Fedora 28 Atoimic Host RC 1.1 available for testing

[Sinny Kumari]

On Thu, Apr 26, 2018 at 2:05 AM, Dusty Mabe  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The Atomic Host compose based on RC 1.1 is available for testing now.
>
> The toplevel directory is: https://kojipkgs.fedoraproject.org/compose/
> twoweek/Fedora-Atomic-28-20180425.0
>
> The cloud images are under the compose/AtomicHost/$arch/images/
> directories.
> The ISO images are under the compose/AtomicHost/$arch/iso/ directories.
>
>
Tested Atomic Host RC 1.1:
* Both ISO and cloud images look good  on all arches
* AMIs are working as expected including openshift cluster set-up
* Ran couple of podman commands and it worked as expected on all arches,
  One thing I noticed that, since both docker and podman are available on
host,
  running "podman run -t fedora bash" didn't have network connectivity
  inside container. So, I ran podman with option --net=host and network was
fine
  later on.


> We don't yet have AMIs. Will update you when those are available.
>
> - - Atomic WG
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlrg5qUACgkQMwLb1zlS
> 5nGKkhAAwOTjZGsnlYSpL6uGbMeNrLLkEfaRzzMpJX77PiR6yIAggm1JmtDtZyDo
> qtI8A2/2ibxGoapzBXWieWOvBus1MC2x4VSVpRqAxlCeUXH2wW4d7dBU5KQRWIev
> GDCfK7Lq6PML/dgrukgRP6RR8nQZPeVj22BEHG3Wp3YbXgR550R23jBBdqfTuP9z
> 8vph26jY/9d9MavFa9QfyUYt6jvAlprhZ4jFyEfLYlEHxeuqcJkb3HrF40XTzC8s
> +6W+qaPkcP2r7Ogz0wf0RQ4nVDwS+B/Z+LFG6ivhXiqNf/SIR9CnMiCN/Y/Qu+XP
> w+XrKNVSccj4gTLBFjib0n7BL8UegLf3FSuBKufQ7e9akSmBcOgPZmoyuYvbN3AI
> M/4dfdpelqm0gJr+fQipp3XH4jJPaBtXdDbjizg7ZH8oRJmITtPDY2C2V8p5oJUU
> 5xZL+ba7td+cn+iETIeKGMGGHoKzoFp5EfIjnwIxBB1WZhRbPhV1jaJO81XoGf3e
> SkAe/bO8n2/awTjsrsKJhN3QqO9s4O77tkGt5zgBsn0oSUvCZnAq867qMdMJrZcz
> lskj8FbRFn4mH7UBI/zyh1kWMz5f/7EICZJtckhIn1YrrEvPkY1QpaYd+hgrfPou
> ONlZ18jqDNaxiJle79SMLFW+tTXtMEJwkiDqUOaQNppbsKJC8fs=
> =ROaE
> -END PGP SIGNATURE-
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [atomic-devel] Fedora 28 Atoimic Host RC 1.1 available for testing

[Sinny Kumari]

Corresponding Atomic Host AMIs are available now for testing:

Fedora-AtomicHost-28-20180425.0.x86_64 us-west-2  ami-35c2aa4d hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 us-west-1  ami-d9a8b5b9 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 us-east-1  ami-1d279162 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 sa-east-1  ami-0eb4e762 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 eu-west-2  ami-3219fa55 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 eu-west-1  ami-09eac670 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 eu-central-1   ami-c2614729 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 ca-central-1   ami-51139235 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-2 ami-d864aeba hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-1 ami-32d8f74e hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 ap-south-1 ami-bd3110d2 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-2 ami-aefc55c0 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-1 ami-6f12f410 hvm gp2
Fedora-AtomicHost-28-20180425.0.x86_64 us-west-2  ami-f2cda58a hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 us-west-1  ami-85abb6e5 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 us-east-1  ami-393b8d46 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 sa-east-1  ami-eebdee82 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 eu-west-2  ami-f819fa9f hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 eu-west-1  ami-29e8c450 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 eu-central-1   ami-ea614701 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 ca-central-1   ami-d70e8fb3 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-2 ami-7b65af19 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-southeast-1 ami-4ddbf431 hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-south-1 ami-833110ec hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-2 ami-70fc551e hvm
standard
Fedora-AtomicHost-28-20180425.0.x86_64 ap-northeast-1 ami-cb17f1b4 hvm
standard

Thanks,
Sinny

On Thu, Apr 26, 2018 at 2:05 AM, Dusty Mabe  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The Atomic Host compose based on RC 1.1 is available for testing now.
>
> The toplevel directory is: https://kojipkgs.fedoraproject.org/compose/
> twoweek/Fedora-Atomic-28-20180425.0
>
> The cloud images are under the compose/AtomicHost/$arch/images/
> directories.
> The ISO images are under the compose/AtomicHost/$arch/iso/ directories.
>
> We don't yet have AMIs. Will update you when those are available.
>
> - - Atomic WG
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEPb6zG5c6sV89tRYPMwLb1zlS5nEFAlrg5qUACgkQMwLb1zlS
> 5nGKkhAAwOTjZGsnlYSpL6uGbMeNrLLkEfaRzzMpJX77PiR6yIAggm1JmtDtZyDo
> qtI8A2/2ibxGoapzBXWieWOvBus1MC2x4VSVpRqAxlCeUXH2wW4d7dBU5KQRWIev
> GDCfK7Lq6PML/dgrukgRP6RR8nQZPeVj22BEHG3Wp3YbXgR550R23jBBdqfTuP9z
> 8vph26jY/9d9MavFa9QfyUYt6jvAlprhZ4jFyEfLYlEHxeuqcJkb3HrF40XTzC8s
> +6W+qaPkcP2r7Ogz0wf0RQ4nVDwS+B/Z+LFG6ivhXiqNf/SIR9CnMiCN/Y/Qu+XP
> w+XrKNVSccj4gTLBFjib0n7BL8UegLf3FSuBKufQ7e9akSmBcOgPZmoyuYvbN3AI
> M/4dfdpelqm0gJr+fQipp3XH4jJPaBtXdDbjizg7ZH8oRJmITtPDY2C2V8p5oJUU
> 5xZL+ba7td+cn+iETIeKGMGGHoKzoFp5EfIjnwIxBB1WZhRbPhV1jaJO81XoGf3e
> SkAe/bO8n2/awTjsrsKJhN3QqO9s4O77tkGt5zgBsn0oSUvCZnAq867qMdMJrZcz
> lskj8FbRFn4mH7UBI/zyh1kWMz5f/7EICZJtckhIn1YrrEvPkY1QpaYd+hgrfPou
> ONlZ18jqDNaxiJle79SMLFW+tTXtMEJwkiDqUOaQNppbsKJC8fs=
> =ROaE
> -END PGP SIGNATURE-
>
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Delay in upcoming Two Week Atomic Release

[Sinny Kumari]

Hi all,

This email is to inform that there will be some delay in next Atomic Two
Week
Release. This is due to some issues with uploading Atomic AMIs. We are
working
on getting it fixed as soon as possible. Once we have AMIs back, we will do
next
Two week release.

Thanks,
Sinny
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Practical use of fedabipkgdiff

[Sinny Kumari]

On Tue, Apr 3, 2018 at 9:54 PM, Richard Shaw  wrote:

> I'm working on a new version of hamlib (3.1 -> 3.2) and instead of
> building manually or downloading packages and using abi-compliance-checker,
> I was going to try and use fedabipkgdiff from the libabigail package.
>
> How do I go about doing that (best practice) that should be less work than
> doing everything manually. Ideally I wouldn't have to build the packages
> locally but I'm fine with that if I have to. I would much rather just be
> able to compare what's in rawhide (--from fc29) to a scratch build I
> performed.
>
>
As far as I am aware, right now fedabipkgdiff tool doesn't support ABI
comparison against scratch build. I see this feature as a nice addition.

One option is to download scratch build rpms locally and use "fedabipkgdiff
--from fc29 path_to_local_rpm"  command. Since this command works only on
one
rpm at a time, you can run iteratively on all desired packages.

CC'ing Dodji and cqi in case they have more input.



> Thoughts?
>
> Thanks,
> Richard
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>


-- 
http://sinny.io/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [atomic-announce] Fedora Atomic Host Two Week Release Announcement: 27.105

[Sinny Kumari]

On Tue, Mar 27, 2018 at 11:43 PM,  wrote:

>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 27.105
> Commit(x86_64): c4015063c00515ddbbaa4c484573d3
> 8376db270b09adb22a4859faa0a39d5d93
> Commit(aarch64): 69bd8187bb519483f275dc1456434c
> c18eec961ab53d965fd50516865ded3c25
> Commit(ppc64le): ae9104933a70342d2b2b08c8ff9f07
> f2e883b6e18abf2b06c6a3e7be3685af66
>
>
> We are releasing images from multiple architectures but please note
> that x86_64 architecture is the only one that undergoes automated
> testing at this time.
>
> Existing systems can be upgraded in place via e.g. `atomic host upgrade`.
>
> Corresponding image media for new installations can be downloaded from:
>
> https://getfedora.org/en/atomic/download/
>
> Alternatively, image artifacts can be found at the following links:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/Atomic/aarch64/iso/Fedora-Atomic-
> ostree-aarch64-27-20180326.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/Atomic/ppc64le/iso/Fedora-Atomic-
> ostree-ppc64le-27-20180326.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/Atomic/x86_64/iso/Fedora-Atomic-
> ostree-x86_64-27-20180326.1.iso
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/aarch64/images/
> Fedora-Atomic-27-20180326.1.aarch64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/aarch64/images/
> Fedora-Atomic-27-20180326.1.aarch64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/ppc64le/images/
> Fedora-Atomic-27-20180326.1.ppc64le.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/ppc64le/images/
> Fedora-Atomic-27-20180326.1.ppc64le.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/x86_64/images/
> Fedora-Atomic-27-20180326.1.x86_64.qcow2
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/x86_64/images/
> Fedora-Atomic-27-20180326.1.x86_64.raw.xz
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-
> 20180326.1.x86_64.vagrant-libvirt.box
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/x86_64/images/Fedora-Atomic-Vagrant-27-
> 20180326.1.x86_64.vagrant-virtualbox.box
>
> Respective signed CHECKSUM files can be found here:
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/Atomic/aarch64/iso/Fedora-Atomic-27-
> 20180326.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/Atomic/ppc64le/iso/Fedora-Atomic-27-
> 20180326.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/Atomic/x86_64/iso/Fedora-Atomic-27-
> 20180326.1-x86_64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/aarch64/images/Fedora-CloudImages-27-
> 20180326.1-aarch64-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/ppc64le/images/Fedora-CloudImages-27-
> 20180326.1-ppc64le-CHECKSUM
> https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-
> Atomic-27-20180326.1/CloudImages/x86_64/images/Fedora-CloudImages-27-
> 20180326.1-x86_64-CHECKSUM
>
> For direct download, the "latest" targets are always available here:
> https://getfedora.org/atomic_iso_latest
> https://getfedora.org/atomic_qcow2_latest
> https://getfedora.org/atomic_raw_latest
> https://getfedora.org/atomic_vagrant_libvirt_latest
> https://getfedora.org/atomic_vagrant_virtualbox_latest
>
> Filename fetching URLs are available here:
> https://getfedora.org/atomic_iso_latest_filename
> https://getfedora.org/atomic_qcow2_latest_filename
> https://getfedora.org/atomic_raw_latest_filename
> https://getfedora.org/atomic_vagrant_libvirt_latest_filename
> https://getfedora.org/atomic_vagrant_virtualbox_latest_filename
>
> For more information about the latest targets, please reference the Fedora
> Atomic Wiki space.
>
> https://fedoraproject.org/wiki/Atomic_WG#Fedora_Atomic_
> Image_Download_Links
>
> Do note that it can take some of the mirrors up to 12 hours to "check-in"
> at
> their own discretion.
>
> Thank you,
> Fedora Release Engineering
>



In this week's release of Fedora Atomic Host we have a new release of
cockpit [1].

[1] https://github.com/cockpit-project/cockpit/releases/tag/164

An example of the diff between this and the previous released version
(for x86_64) is:

ostree diff commit old:
326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91
ostree diff commit 

Re: Fedora Atomic Host Two Week Release Announcement: 27.100

[Sinny Kumari]

  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

-- 
Sinny Kumari
http://sinny.io/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Atomic, Cloud and Docker images for s390x

[Sinny Kumari]

On Fri, Feb 2, 2018 at 8:25 PM, Daniel Walsh <dwa...@redhat.com> wrote:
> On 01/31/2018 06:26 PM, Josh Boyer wrote:
>>
>> On Tue, Jan 30, 2018 at 12:42 PM, Daniel Walsh <dwa...@redhat.com> wrote:
>>>
>>> On 01/30/2018 11:50 AM, Jan Kurik wrote:
>>>>
>>>> = Proposed Self Contained Change: Atomic, Cloud and Docker images for
>>>> s390x =
>>>>
>>>>
>>>> https://fedoraproject.org/wiki/Changes/Atomic_Cloud_and_Docker_images_for_s390x
>>>>
>>>> Change owner(s):
>>>> * Sinny Kumari 
>>>>
>>>>
>>>> This change is to bring s390x architecture closer to other Fedora
>>>> architectures by adding widely used Fedora variants. This includes
>>>> docker images, Atomic Host (iso, qcow2 and raw format) and regular
>>>> Cloud Images (qcow2 and raw format).
>>>>
>>>>
>>>> == Detailed Description ==
>>>> We already ship Atomic, Cloud and Docker images on other 64-bit Fedora
>>>> supported architectures- aarch64, x86_64 and ppc64le. With Fedora 27,
>>>> s390x is part of primary koji build system. Currently, we only ship
>>>> Server and Everything variants for s390x. So, our next steps should be
>>>> to have missing Fedora variants on s390x architecture which users will
>>>> find useful. This brings in shipping Atomic, Cloud and Docker images
>>>> in Fedora for s390x as well.
>>>>
>>>>
>>>> == Scope ==
>>>> * Proposal owners:
>>>> These are isolated changes which doesn't impact existing Fedora 28
>>>> release plan on s390x. To have these changes ready to ship in Fedora
>>>> 28, we mainly require s390x koji builders configured to run these
>>>> composes, changes in pungi configuration [
>>>> https://pagure.io/pungi-fedora/pull-request/496 ] to enable the
>>>> additional compose and fixing s390x specific issues encountered when
>>>> compose fails to run.
>>>>
>>>> * Other developers:
>>>> Changes in Fedora infrastructure configs/scripts will be required to
>>>> have s390x builders configured to run additional composes. Fedora
>>>> Infrastructure issue [
>>>> https://pagure.io/fedora-infrastructure/issue/6659 ] has been filed to
>>>> keep track of required changes to be done.
>>>>
>>>> * Release engineering:
>>>> #Releng 7286: https://pagure.io/releng/issue/7286
>>>>
>>>> * Policies and guidelines:
>>>> N/A (not a System Wide Change)
>>>>
>>>> * Trademark approval:
>>>> N/A (not needed for this Change)
>>>
>>>
>>> You mean OCI Images...
>>
>> Mostly likely, yes.
>>
>> Relatedly, has there been a change request to move the default
>> container runtime to cri-o or runc or rkt or anything other than
>> docker in Fedora Atomic?  If so, that will be neat and I'm sorry I
>> missed it.  If not, why not?
>
> Not yet.  We are working on packaging podman which would give users the same
> experience as Docker CLI without requiring a Daemon.  That would be the
> thing to replace
> Docker if we went that way.  CRI-O != Docker.  It does not have any of the
> CLI that users would expect.

Thanks Dan! Nice to know about podman.

> Rkt is dead in my opinion.  runc is on Atomic host now, I believe.

Indeed, runc is part of base Atomic Host.

>
>
>> josh
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org



-- 
http://sinny.io/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Atomic, Cloud and Docker images for s390x

[Sinny Kumari]

On Thu, Feb 1, 2018 at 9:14 PM, Josh Boyer <jwbo...@fedoraproject.org> wrote:
> On Thu, Feb 1, 2018 at 12:29 AM, Sinny Kumari <ksi...@gmail.com> wrote:
>> On Wed, Jan 31, 2018 at 11:56 PM, Josh Boyer <jwbo...@fedoraproject.org> 
>> wrote:
>>> On Tue, Jan 30, 2018 at 12:42 PM, Daniel Walsh <dwa...@redhat.com> wrote:
>>>> On 01/30/2018 11:50 AM, Jan Kurik wrote:
>>>>>
>>>>> = Proposed Self Contained Change: Atomic, Cloud and Docker images for
>>>>> s390x =
>>>>>
>>>>> https://fedoraproject.org/wiki/Changes/Atomic_Cloud_and_Docker_images_for_s390x
>>>>>
>>>>> Change owner(s):
>>>>> * Sinny Kumari 
>>>>>
>>>>>
>>>>> This change is to bring s390x architecture closer to other Fedora
>>>>> architectures by adding widely used Fedora variants. This includes
>>>>> docker images, Atomic Host (iso, qcow2 and raw format) and regular
>>>>> Cloud Images (qcow2 and raw format).
>>>>>
>>>>>
>>>>> == Detailed Description ==
>>>>> We already ship Atomic, Cloud and Docker images on other 64-bit Fedora
>>>>> supported architectures- aarch64, x86_64 and ppc64le. With Fedora 27,
>>>>> s390x is part of primary koji build system. Currently, we only ship
>>>>> Server and Everything variants for s390x. So, our next steps should be
>>>>> to have missing Fedora variants on s390x architecture which users will
>>>>> find useful. This brings in shipping Atomic, Cloud and Docker images
>>>>> in Fedora for s390x as well.
>>>>>
>>>>>
>>>>> == Scope ==
>>>>> * Proposal owners:
>>>>> These are isolated changes which doesn't impact existing Fedora 28
>>>>> release plan on s390x. To have these changes ready to ship in Fedora
>>>>> 28, we mainly require s390x koji builders configured to run these
>>>>> composes, changes in pungi configuration [
>>>>> https://pagure.io/pungi-fedora/pull-request/496 ] to enable the
>>>>> additional compose and fixing s390x specific issues encountered when
>>>>> compose fails to run.
>>>>>
>>>>> * Other developers:
>>>>> Changes in Fedora infrastructure configs/scripts will be required to
>>>>> have s390x builders configured to run additional composes. Fedora
>>>>> Infrastructure issue [
>>>>> https://pagure.io/fedora-infrastructure/issue/6659 ] has been filed to
>>>>> keep track of required changes to be done.
>>>>>
>>>>> * Release engineering:
>>>>> #Releng 7286: https://pagure.io/releng/issue/7286
>>>>>
>>>>> * Policies and guidelines:
>>>>> N/A (not a System Wide Change)
>>>>>
>>>>> * Trademark approval:
>>>>> N/A (not needed for this Change)
>>>>
>>>>
>>>> You mean OCI Images...
>>>
>>> Mostly likely, yes.
>>>
>>> Relatedly, has there been a change request to move the default
>>> container runtime to cri-o or runc or rkt or anything other than
>>> docker in Fedora Atomic?  If so, that will be neat and I'm sorry I
>>> missed it.  If not, why not?
>>
>> As per discussion outcome in atomic-wg ticket [1], Fedora 28 Atomic Host will
>> ship docker as default container runtime. Prior to this decision, a survey
>> happened about docker usage for Atomic Host [2] which shows that there are 
>> still
>> good number of people who want docker as default.
>>
>> Answer to the question on whether there will another default container 
>> runtime
>> like cri-o [2] is still undecided. For now reason is having both cri-o and
>> docker will increase size of base Atomic Host.
>
> Awesome information, Sinny!  Thanks for pulling this together in such
> a concise summary.  It helps others that don't follow Atomic closely
> understand the plans there.

Glad to hear that :)

> So Dan... OCI images for sure but in the context of Fedora users and
> other deliverables, Docker images isn't really wrong.  Plus, I just
> like giving you crap ;)
>
> josh
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org



-- 
http://sinny.io/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: F28 Self Contained Change: Atomic, Cloud and Docker images for s390x

[Sinny Kumari]

On Wed, Jan 31, 2018 at 11:56 PM, Josh Boyer <jwbo...@fedoraproject.org> wrote:
> On Tue, Jan 30, 2018 at 12:42 PM, Daniel Walsh <dwa...@redhat.com> wrote:
>> On 01/30/2018 11:50 AM, Jan Kurik wrote:
>>>
>>> = Proposed Self Contained Change: Atomic, Cloud and Docker images for
>>> s390x =
>>>
>>> https://fedoraproject.org/wiki/Changes/Atomic_Cloud_and_Docker_images_for_s390x
>>>
>>> Change owner(s):
>>> * Sinny Kumari 
>>>
>>>
>>> This change is to bring s390x architecture closer to other Fedora
>>> architectures by adding widely used Fedora variants. This includes
>>> docker images, Atomic Host (iso, qcow2 and raw format) and regular
>>> Cloud Images (qcow2 and raw format).
>>>
>>>
>>> == Detailed Description ==
>>> We already ship Atomic, Cloud and Docker images on other 64-bit Fedora
>>> supported architectures- aarch64, x86_64 and ppc64le. With Fedora 27,
>>> s390x is part of primary koji build system. Currently, we only ship
>>> Server and Everything variants for s390x. So, our next steps should be
>>> to have missing Fedora variants on s390x architecture which users will
>>> find useful. This brings in shipping Atomic, Cloud and Docker images
>>> in Fedora for s390x as well.
>>>
>>>
>>> == Scope ==
>>> * Proposal owners:
>>> These are isolated changes which doesn't impact existing Fedora 28
>>> release plan on s390x. To have these changes ready to ship in Fedora
>>> 28, we mainly require s390x koji builders configured to run these
>>> composes, changes in pungi configuration [
>>> https://pagure.io/pungi-fedora/pull-request/496 ] to enable the
>>> additional compose and fixing s390x specific issues encountered when
>>> compose fails to run.
>>>
>>> * Other developers:
>>> Changes in Fedora infrastructure configs/scripts will be required to
>>> have s390x builders configured to run additional composes. Fedora
>>> Infrastructure issue [
>>> https://pagure.io/fedora-infrastructure/issue/6659 ] has been filed to
>>> keep track of required changes to be done.
>>>
>>> * Release engineering:
>>> #Releng 7286: https://pagure.io/releng/issue/7286
>>>
>>> * Policies and guidelines:
>>> N/A (not a System Wide Change)
>>>
>>> * Trademark approval:
>>> N/A (not needed for this Change)
>>
>>
>> You mean OCI Images...
>
> Mostly likely, yes.
>
> Relatedly, has there been a change request to move the default
> container runtime to cri-o or runc or rkt or anything other than
> docker in Fedora Atomic?  If so, that will be neat and I'm sorry I
> missed it.  If not, why not?

As per discussion outcome in atomic-wg ticket [1], Fedora 28 Atomic Host will
ship docker as default container runtime. Prior to this decision, a survey
happened about docker usage for Atomic Host [2] which shows that there are still
good number of people who want docker as default.

Answer to the question on whether there will another default container runtime
like cri-o [2] is still undecided. For now reason is having both cri-o and
docker will increase size of base Atomic Host.

[1] https://pagure.io/atomic-wg/issue/360
[2] 
https://docs.google.com/document/d/1aC8uthOMrTLiYK3l5muUVKDnOO7Rich2JxJ0sd4LJ6o/edit#heading=h.4kdxqyoia6mn
[3] https://pagure.io/atomic-wg/issue/407

> josh
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org



-- 
http://sinny.io/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Unannounced soname bump (Rawhide and 26): ldns (libldns.so.1 -> libldns.so.2)

[Sinny Kumari]

On Tue, Mar 14, 2017 at 10:02 PM, Stephen Gallagher  wrote:
> On 03/14/2017 12:15 PM, Zbigniew Jędrzejewski-Szmek wrote:
>> On Tue, Mar 14, 2017 at 06:35:17AM -0400, Simo Sorce wrote:
>>> On Thu, 2017-03-09 at 15:10 -0800, Adam Williamson wrote:
 ldns was updated from 1.6.17 to 1.7.0 for Rawhide and Fedora 26 on
 2017-03-06. This update bumped the soname from libldns.so.1 to
 libldns.so.2 . This soname bump was not announced, as it is supposed
 to
 be, and dependent packages were not rebuilt.

 opendnssec depends on libldns and freeipa-server-dns requires
 opendnssec, so this resulted in FreeIPA server deployment - which is
 a
 core Fedora Server feature, and in the Alpha release requirements -
 breaking on both 26 and Rawhide.

 We will now need to go through the blocker process to have the
 opendnssec rebuild pulled into Fedora 26 composes, as this
 unannounced
 soname bump landed right before the Alpha freeze.

 Other packages that depend on libldns appear to be dnssec-trigger and
 netresolve. dnssec-trigger has been rebuilt (but will need to go
 through the blocker or FE process to make it into 26 Alpha),
 netresolve
 has not, yet. I will try to rebuild netresolve.

 Once again, folks, *please* announce your soname bumps, and co-
 ordinate
 rebuilds.
>>>
>>> Can we simply have a mechanism that blocks packages from going through
>>> if a soname bump id detected and an appropriate bugzilla with a
>>> specific keyword of SONAMEBUMP is not present, or something like that ?
>> There's also the old school technique of specifying the soname in %files:
>>
>> %global somajor 11
>> %global sominor 2.3
>> %files
>> %_libdir/lib%name.so.%soversion.%sominor
>> %_libdir/lib%name.so.%soversion
>> %files devel
>> %_libdir/lib%name.so
>>
>> And then one cannot do an announcement so-bump by mistake.
>>
>
> The libabigail approach would be more versatile, though. Mostly because
> upstreams don't always remember to bump soname when they break compatibility.

+1 for using libabigail tooling here. libabigail detects soname
changes along with other ABI changes.

For example, running libabigail's abipkgdiff tool locally between
ldns-1.6.17-20 and ldns-1.7.0-1, we see following results telling
soname of libldns has changed:
$ abipkgdiff --d1 ldns-debuginfo-1.6.17-20.fc25.x86_64.rpm --d2
ldns-debuginfo-1.7.0-1.fc27.x86_64.rpm --devel1
ldns-devel-1.6.17-20.fc25.x86_64.rpm --devel2
ldns-devel-1.7.0-1.fc27.x86_64.rpm ldns-1.6.17-20.fc25.x86_64.rpm
ldns-1.7.0-1.fc27.x86_64.rpm

Removed binaries:
  libldns.so.1.6.17, SONAME: libldns.so.1
Added binaries:
  libldns.so.2.0.0, SONAME: libldns.so.2

As Dan Horak mentioned, we already run abicheck taskotron task [1]
which uses libabigail
to detect any sort of ABI changes for a package update (currently runs
only for critpath packages).
With the help from taskotron devs, we have also extended abicheck run
from critpath
packages to all packages in dev instance [2]. Soon abicheck task will
run on all package
updates and result from abicheck will be visible in bodhi package
update interface too.

[1] 
https://taskotron.fedoraproject.org/resultsdb/results?testcases=dist.abicheck
[2] 
https://taskotron-dev.fedoraproject.org/resultsdb/results?testcases=dist.abicheck
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Getting error "Try #1 for call None (multiCall) failed: syntax error: line 1" while running locally abicheck task

[Sinny Kumari]

Hi Martin,

On Mon, Jan 2, 2017 at 7:10 PM, Martin Krizek <mkri...@redhat.com> wrote:
> - Original Message -
>> From: "Sinny Kumari" <ksi...@gmail.com>
>> To: "Fedora QA Development" <qa-devel@lists.fedoraproject.org>
>> Sent: Tuesday, December 20, 2016 1:15:43 PM
>> Subject: Getting error "Try #1 for call None (multiCall) failed: syntax 
>> error: line 1" while running locally abicheck
>> task
>>
>> Hi,
>>
>> Form few days, I am am not able to run task-abicheck [1] taskotron
>> task locally because of following error message:
>>
>> [koji] 11:58:43 INFOTry #1 for call None (multiCall) failed:
>> syntax error: line 1, column 0
>>
>> Detail log is available at [2]
>>
>> I am not sure if there is something to do with Flag day 2016 changes.
>> Although, I have made all related changes in my system. Also, I see
>> that task-abicheck on taskotron production instance [3] is running
>> fine.
>>
>> koji and libtaskotron version my system have are:
>> $ rpm -qa libtaskotron-* koji*
>>   libtaskotron-0.4.17-1.fc24.noarch
>>   koji-1.11.0-1.fc24.noarch
>>
>> Any help will be appreciated :)
>>
>
> Hi Sinny,
>
> I reproduced it on my machine as well. I managed to make it work with:
>
> 1. Use "https" when accessing koji, change these in 
> /etc/taskotron/taskotron.yml:
>
> ## URL of Koji instance used for querying about new builds
> koji_url: https://koji.fedoraproject.org/kojihub
> ## URL of repository of all the RPM packages built in Koji
> pkg_url: https://kojipkgs.fedoraproject.org/packages

Works for me as well with above suggested changes in taskotron.yml .
If urls has been
changed from http to https permanently, then we might need it get
fixed in next taskotron
release.
Thanks for the help!
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Getting error "Try #1 for call None (multiCall) failed: syntax error: line 1" while running locally abicheck task

[Sinny Kumari]

Hi,

Form few days, I am am not able to run task-abicheck [1] taskotron
task locally because of following error message:

[koji] 11:58:43 INFOTry #1 for call None (multiCall) failed:
syntax error: line 1, column 0

Detail log is available at [2]

I am not sure if there is something to do with Flag day 2016 changes.
Although, I have made all related changes in my system. Also, I see
that task-abicheck on taskotron production instance [3] is running
fine.

koji and libtaskotron version my system have are:
$ rpm -qa libtaskotron-* koji*
  libtaskotron-0.4.17-1.fc24.noarch
  koji-1.11.0-1.fc24.noarch

Any help will be appreciated :)

Thanks,
Sinny

[1] https://pagure.io/task-abicheck/
[2]https://paste.fedoraproject.org/510030/
[3] 
https://taskotron.fedoraproject.org/resultsdb/results?testcase_name=dist.abicheck
___
qa-devel mailing list -- qa-devel@lists.fedoraproject.org
To unsubscribe send an email to qa-devel-le...@lists.fedoraproject.org

Re: Please unpush FEDORA-2016-7776983633 on all releases or drop support for libjasper

[Sinny Kumari]

On Thu, Sep 15, 2016 at 4:20 PM, Josh Boyer  wrote:
> On Thu, Sep 15, 2016 at 3:42 AM, Dan Horák  wrote:
>> On Wed, 14 Sep 2016 20:50:49 +0100
>> Richard Hughes  wrote:
>>
>>> Can we get somebody to revert
>>> https://bodhi.fedoraproject.org/updates/FEDORA-2016-7776983633 please.
>>> The update was built to fix CVE-2015-5203 which fixes a double free
>>> when opening corrupt JPEG-2000 files but in doing-so breaks quite a
>>> few apps in the desktop spin causing them to exit with an assert deep
>>> in libjasper.
>>>
>>> In the update the function jas_stream_memopen has been changed:
>>>
>>> -jas_stream_t *jas_stream_memopen(char *buf, int bufsize);
>>> +jas_stream_t *jas_stream_memopen(char *buf, size_t bufsize);
>>>
>>> Unless I'm misunderstood things dramatically, size_t is basically
>>> *unsigned* long integer, but this function offers a feature where if
>>> the bufsize is -1 the buffer is realloc'd as needed. gdk-pixbuf2 uses
>>> this feature for JPEG-2000 files. However, as size_t represents only
>>> positive numbers, a conversion takes place to some very high number
>>> and the allocation fails.
>>
>> one more case for enabling libabigail tests in bodhi ...
>
> I agree.  This would have been caught by libabigail/abicheck as far as I know.

Yes, see my previous comment for more detail.

> Does anyone know what the blockers are for enabling it in production?

Right now abichecks already run in production on set of packages which are
listed in critpath[1] and can be viewed [2] or subscribed[3] to. For initial
phase, it has been kept as informational and no packages get blocked if
incompatible ABI changes found. There is already ticket [4] for
enabling abicheck
on all c/c++ package updates which I believe will be worked on soon.

[1] https://admin.fedoraproject.org/pkgdb/api/critpath
[2] 
https://taskotron.fedoraproject.org/resultsdb/results?testcase_name=dist.abicheck
[3] https://apps.fedoraproject.org/notifications/
[4] https://phab.qadevel.cloud.fedoraproject.org/T823
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Please unpush FEDORA-2016-7776983633 on all releases or drop support for libjasper

[Sinny Kumari]

On Thu, Sep 15, 2016 at 1:12 PM, Dan Horák  wrote:
> On Wed, 14 Sep 2016 20:50:49 +0100
> Richard Hughes  wrote:
>
>> Can we get somebody to revert
>> https://bodhi.fedoraproject.org/updates/FEDORA-2016-7776983633 please.
>> The update was built to fix CVE-2015-5203 which fixes a double free
>> when opening corrupt JPEG-2000 files but in doing-so breaks quite a
>> few apps in the desktop spin causing them to exit with an assert deep
>> in libjasper.
>>
>> In the update the function jas_stream_memopen has been changed:
>>
>> -jas_stream_t *jas_stream_memopen(char *buf, int bufsize);
>> +jas_stream_t *jas_stream_memopen(char *buf, size_t bufsize);
>>
>> Unless I'm misunderstood things dramatically, size_t is basically
>> *unsigned* long integer, but this function offers a feature where if
>> the bufsize is -1 the buffer is realloc'd as needed. gdk-pixbuf2 uses
>> this feature for JPEG-2000 files. However, as size_t represents only
>> positive numbers, a conversion takes place to some very high number
>> and the allocation fails.
>
> one more case for enabling libabigail tests in bodhi ...

Indeed, I can clearly see that there are incompatible ABI changes [1]
with this update
on running libabigail tool. Right now, abichecks run [2] only on
sub-set of packages
but testers and developers can use libabigail tools [3] locally to see
possible ABI changes
which may occur with the package update. After reviewing ABI changes, action can
be taken accordingly.


[1] https://paste.fedoraproject.org/428310/
[2] 
https://taskotron.fedoraproject.org/resultsdb/results?testcase_name=dist.abicheck
[3] https://sourceware.org/libabigail/manual/libabigail-tools.html#tools-manuals
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Renamed task-libabigail to task-abicheck and wiki page available

[Sinny Kumari]

On Thu, May 26, 2016 at 1:33 PM, Martin Krizek  wrote:

>
> Sorry for late reply, this has been done.

great, thanks!
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/qa-devel@lists.fedoraproject.org

Re: Automatic ABI checks for new package updates in bodhi using taskotron

[Sinny Kumari]

Hi Kamil,


On Thu, Apr 14, 2016 at 8:40 PM, Kamil Paral  wrote:

> Hi Sinny,
>
> I have created a review here:
> https://phab.qadevel.cloud.fedoraproject.org/D813
>
> I used our Phabricator, because it makes it easy to comment on particular
> lines. You can log in using your FAS email [1] and reply there, or here in
> the mailing list, it doesn't matter. I'm pleasantly surprised that despite
> our very lacking documentation, you managed to create a very good Taskotron
> task :-)
>

Thanks for the quick review. I have addressed review comments and added new
diff at https://phab.qadevel.cloud.fedoraproject.org/D817?id=2081 . I am
not sure if I  updated diff in right way but this is what I ended up by
following option "Update diff" available in right side :)


> One additional thing that I noticed today - when I ran the abipkgdiff
> comparison on lyx package, it used up to 6 GB RAM. That is really high and
> I believe our test clients don't have that many available. I don't know how
> abipkgdiff works and whether it is able to adjust its memory requirements
> based on the amount of available system memory (so that it would use less
> memory on a less equipped system and still work properly). Do you know if
> this is going to be a problem or not? And do you know what is the peak
> memory usage for very big packages (e.g. what about comparing two kernel
> packages)? Is there any solution that we could use to limit the memory
> consumption of abipkgdiff?
>

I had a talk about this with libabigail's maintainer (Dodji). If a binary
is taking more RAM then right now, we can't do anything about it. This is
because ELF information for binaries to be compared and corresponding
debuginfo gets loaded while performing ABI comparison.  Also, right now
libabigail doesn't support comparison of two kernel version.

I noticed that binary files available in lyx package are PIE (Position
Independent Executable) files which are basically executable files. As we
know, an application mainly consumes shared libraries from its dependent
packages. ABI change of shared libraries are what really matter in
packages. Therefore, I am now calling  abipkgdiff  with --dso-only  option.
This will avoid unnecessary comparison between executable files. This
reduces overall comparison time of a koji build update and hopefully
reduces memory consumption since most of shared libraries are smaller in
size (few MBs).

Right now there is a bug in libabigail that it doesn't distinguish between
PIE files and shared libraries since both are of type DSO(Dynamic Shared
object). So, right now abipkgdiff with --dso-only option does ABI
comparison for PIE files as well. Upstream bug has been reported to
distinguish between Shared libraries and PIE files
https://sourceware.org/bugzilla/show_bug.cgi?id=19961. This will be fixed
soon and will be available in next libabigail release.

Thanks,
Sinny
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/qa-devel@lists.fedoraproject.org

Automatic ABI checks for new package updates in bodhi using taskotron

[Sinny Kumari]

Hi Kamil,

Thank you for the reply.

On Wed, Apr 13, 2016 at 7:34 PM, Kamil Paral  wrote:

>
> Hello Sinny,
> thanks for your work and sorry for late response. I'll review your
> taskotron task and let you know if there's something that should be changed
> or not. Afterwards, we will start mirroring your git repo on our taskotron
> servers, and patch our taskotron-trigger to know about task-libabigail. We
> can then execute it on every new Koji build (or Bodhi update, your choice).
> Your task will probably be the first one that we will execute regularly
> while not being written and maintained directly by us, so if there are any
> rough edges in the process, I apologize in advance :-)
>

Okay, sounds good to me.


>
> You'll need to have two branches in your git:
> master - this will be used on our production server
> https://taskotron.fedoraproject.org/
> develop - this will be used on our dev and staging server
> http://taskotron-dev.fedoraproject.org/ and
> https://taskotron.stg.fedoraproject.org/


Okay, works for me.

You need to decide whether it is better to run libabigain against every new
> Koji build, or just against every new Bodhi update. From a quick look, I
> think it makes more sense to run libabigail on every new Koji build, so
> that people can see the results even before creating the update (that
> requires looking into ResultsDB manually at the moment). If we run it on
> every Koji build, the results will still show up in Bodhi - Bodhi should
> query ResultsDB and show the results for those particular builds present in
> the update. (We might need to teach Bodhi about libabigail existence, I'm
> not sure). Ultimately it's your choice, what makes more sense for your
> check.
>

I believe that when we say every new Koji build, we are talking about
non-scratch build which doesn't include scratch build done by anyone. If my
assumption is right, then yes running libabigail task on each koji build
will be good. It is possible to do that with current implementation since
libabigail task look for a koji build-id to download corresponding rpms.


> Please also create a wiki page at
> https://fedoraproject.org/wiki/Taskotron/Tasks/libabigail similar to these
> https://fedoraproject.org/wiki/Taskotron/Tasks/depcheck
> https://fedoraproject.org/wiki/Taskotron/Tasks/upgradepath
> linked from https://fedoraproject.org/wiki/Taskotron/Tasks .
>

Sure, I will create one.


> We try to have at least some basic documentation and FAQ for our checks in
> there. Currently it's not very discoverable (we should link to it at least
> from ResultsDB, which we currently don't) and the location can change, but
> at least it's a link we can give to people when asking basic questions
> about one of our tasks. Also, since you're going to maintain the task and
> not us, please include some "Contact" section where to post feedback or
> report bugs (e.g. github issues page). If people ask us about the task and
> we don't know the answer, we will point them to that wiki page.
>

Will add contact section in wiki page.
I wonder if it is better to have this included with other fedora qa tasks?


> Can we please continue this discussion in qa-devel [1] mailing list? We
> can discuss more implementation details in there, and I'll post my review
> findings in there as well.
>

done!


-- 
http://sinny.io/
___
qa-devel mailing list
qa-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/qa-devel@lists.fedoraproject.org

Automatic ABI checks for new package updates in bodhi using taskotron

[Sinny Kumari]

Hi all,

Last year, discussion happened around "Checking the ABI of packages
submitted to the updates-testing Fedora repository" on Fedora devel ML [1].

We felt that taskotron[2] will be the best place to run automatic ABI
checks for a new package update pushed in bodhi for testing against latest
stable package. If any ABI incompatibility is detected, we will provide
package maintainer feedback to review ABI changes, similar to how rpmlint
feedback is given.  This will help to ship stable ABI for Fedora packages,
reduced build failures which is seen later in packages depending on it.

I have created  a libabigail [3] taskotron task which can be integrated in
taskotron to perform automatic ABI checks for new bodhi updates. Right now,
this task downloads all rpms with debuginfo for specified package update
and corresponding latest stable package available for that release.
Further, it runs libabigail's abipkgdiff tool for ABI checks. It tells
PASSED if no ABI change occurred, otherwise FAILED and ABI changes log can
be reviewed to ensure changes are ok to go or not.

Source code of libabigail taskotron task can be accessed from github[4].
Some sample output of libabigail task run on my local machine:
  * http://fpaste.org/349740/
  * http://fpaste.org/349741/
  * http://fpaste.org/349761/

It will be great if someone can review libabigail task and provide
feedback. Also, I would love to know further steps required to integrate it
with taskotron?

Thanks,
Sinny

[1]
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/BBWQWPSYA66F2T4VVOLY3BGWW43W6K6C/#TDUMSBDHQDW6A4WBTRFYYH7WMQGNWLAZ
[2] http://libtaskotron.readthedocs.org/en/develop/
[3] https://sourceware.org/libabigail/
[4] https://github.com/sinnykumari/task-libabigail

-- 
http://sinny.io/
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Self Introduction and Review Request: Sinny Kumari

[Sinny Kumari]

Hi List,

I just pushed a package for review at
https://bugzilla.redhat.com/show_bug.cgi?id=1182261 and would like some
review on it.
I work at Red Hat India and contribute to KDE in my free time. I blog at
http://sinny.io/ and also give talks at local FOSS events (the last one was
on basic RPM packaging at Fedora 21 release party in Bangalore).

Please review my package and let me know if any changes are needed. I will
be more than happy to work on it.

Thanks
Sinny Kumari
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct