May 2017 - rel-eng - Fedora Mailing-Lists

[releng] PR #6809: fix missing conversion from optparse to argument parser.

by Bill Peck

bpeck opened a new pull-request against the project: `releng` that you are following: `` fix missing conversion from optparse to argument parser. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/6809

6 years, 11 months

3
3
0 / 0

[releng] Issue #6792: Rename f26-modularity to module-bootstrap-f26

by Jan Kaluža

jkaluza reported a new issue against the project: `releng` that you are following: `` Hi, as I stated in https://pagure.io/releng/issue/6791, I would like to kindly ask rel-engs to rename `f26-modularity` tag to `module-bootstrap-f26` to make its name clearer. This tag has been always used to bootstrap the base-runtime module, which is later used as a base module for other modules. We originally did not have MBS in production and the "module-" prefix for modular tags has not been set in time when this tag has been created. All the current modules now have the tag prefixed with the "module-" prefix and it would be practical to have this prefix also for the current `f26-modularity` tag. In modularity tools, we always check that we are running all the operations with "module-" prefixed tag to not break the non-modular tags and because of this single `f26-modularity` tag, we have to allow strange exceptions to that rule, which complicates the code. Thanks in advance :) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6792

6 years, 11 months

2
2
0 / 0

[pungi-fedora] PR #238: Set release blocking deliverables

by Mohan Boddu

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Set release blocking deliverables `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/238

6 years, 12 months

2
1
0 / 0

[pungi-fedora] PR #237: set the release blocking deliverables and not being allowed to fail

by Dennis Gilmore

ausil opened a new pull-request against the project: `pungi-fedora` that you are following: `` set the release blocking deliverables and not being allowed to fail `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/237

6 years, 12 months

2
1
0 / 0

Fedora Atomic Host Two Week Release Announcement

by noreply＠fedoraproject.org

A new Fedora Atomic Host update is available via an OSTree commit: Commit: cdd359911de49f3a8199ffd41a9894019562001d6cf9be66e1894c31b6fa1c66 Version: 25.127 Existing systems can be upgraded in place via e.g. `atomic host upgrade` or `atomic host deploy`. Corresponding image media for new installations can be downloaded from: https://getfedora.org/en/atomic/download/ Respective signed CHECKSUM files can be found here: https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-Atomic-25-2017... 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 Cloud Wiki space. https://fedoraproject.org/wiki/Cloud#Quick_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

6 years, 12 months

2
1
0 / 0

[pungi-fedora] PR #226: cloud/docker: add Power64 arches to image creation

by Peter Robinson

pbrobinson opened a new pull-request against the project: `pungi-fedora` that you are following: `` cloud/docker: add Power64 arches to image creation `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/226

6 years, 12 months

3
3
0 / 0

[pungi-fedora] PR #235: Setup for Fedora 26 Beta

by Mohan Boddu

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Setup for Fedora 26 Beta `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/235

6 years, 12 months

2
1
0 / 0

[pungi-fedora] PR #233: atomic: update lorax passed vars

by Dusty Mabe

dustymabe opened a new pull-request against the project: `pungi-fedora` that you are following: `` atomic: update lorax passed vars `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/233

6 years, 12 months

2
1
0 / 0

Daily F26 images, do we need them in Freeze period?

by Parag Nemade

Hi, I tried asking on #fedora-releng below question but did not get any answer hence writing here. I see that Fedora Workstation Live image is still getting built daily and uploaded to mirrors. Is that expected considering we are in Beta Freeze? Also, I can't find any package added/removed in some of the f26 compose reports. So why are we using the koji resource to build the same set of packages again and again? Another thing why is it that there are no old Workstation Live iso images available? If I am not wrong then https://kojipkgs.fedoraproject.org/compose/branched/ is the correct location to check for old images. Regards, Parag

6 years, 12 months

1
0
0 / 0

[releng] Issue #6805: split fedora_koji and fedora_ftp storage volumes

by Kevin Fenzi

kevin reported a new issue against the project: `releng` that you are following: `` Later this year our storage provider is moving to newer appliances. These appliances will only have 2 grades of storage: sata disks or flash. The idea is that anything that doesn't require access very often or speed can be on the sata disks, and anything that is accessed/used a lot can be on the flash storage. Currently our fedora_koji volume is 45TB and growing. Currently our fedora_ftp master mirror volume is 12TB. In order to take advantage of the new flash storage we need to seperate out our data by usage. For fedora_ftp we should easily be able to split out the archive part. That ends up being about 6.5TB. Even if that data is accessed a fair bit having archive and non archive would help us better be able to fit into flash with it. For fedora_koji we can take advantage of koji's "volumes" support. Basically we make a new volume and mount it on /mnt/koji/koji_archive and then tell koji about that volume and then we script something that moves builds over to that volume. We could start with the oldest fc6 builds and move up from there. I am not sure how much space all the EOL releases will get us, we will just have to wait and see, but it should help reduce the massive size and make it more possible to get the active set into flash. So, actions here: * Run this by koji deveopers and see if it all makes sense and is implemented as we think. * Need to create volumes (I can do this) * need to tell koji about them (I can do this too) * Need a script to identify all non garbage collected builds for all EOL releases and run 'koji set build-volume' on each to move those builds to the new volume. We should be able to start on this after freeze... `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6805

6 years, 12 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng May 2017