August 2017 - rel-eng - Fedora Mailing-Lists

[releng] Issue #6975: pdc: map our releases to product versions

by Ralph Bean

ralph reported a new issue against the project: `releng` that you are following: `` All of our product-versions say they are inactive. According to [upstream](https://github.com/product-definition-center/product-definition..., this is because they are not mapped to any active releases. We *do* have lots of active releases.. but they are not mapped to the product-versions. See the API response here: https://pdc.fedoraproject.org/rest_api/v1/releases/ the `product_version` is `null` for all of them. If we set those to the appropriate product-version, the 'active' field on the products should flip. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6975

5 years, 9 months

1
1
0 / 0

[releng] PR #6949: Some scripts for orphan/ownership management.

by Ralph Bean

ralph opened a new pull-request against the project: `releng` that you are following: `` Some scripts for orphan/ownership management. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/6949

5 years, 9 months

4
9
0 / 0

[releng] PR #6973: check the f27-binutils-rebuild tag

by Dennis Gilmore

ausil opened a new pull-request against the project: `releng` that you are following: `` check the f27-binutils-rebuild tag `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/6973

5 years, 9 months

2
1
0 / 0

[pungi-fedora] PR #305: rename the Docker Variant and images to Container

by Dennis Gilmore

ausil opened a new pull-request against the project: `pungi-fedora` that you are following: `` rename the Docker Variant and images to Container `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/305

5 years, 9 months

3
3
0 / 0

[pungi-fedora] PR #332: Fix up the f27 modular config.

by Ralph Bean

ralph opened a new pull-request against the project: `pungi-fedora` that you are following: `` Fix up the f27 modular config. `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/332

5 years, 9 months

2
3
0 / 0

[pungi-fedora] PR #333: F27 images should use f27 kickstarts.

by Ralph Bean

ralph opened a new pull-request against the project: `pungi-fedora` that you are following: `` F27 images should use f27 kickstarts. `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/333

5 years, 9 months

2
1
0 / 0

[releng] Issue #6971: pungi->bodhi - where should pungi configs be stored?

by Dusty Mabe

dustymabe reported a new issue against the project: `releng` that you are following: `` I had assumed that we would just do a git clone of the pungi-fedora git repo, but @bowlofeggs pointed out that this has implications on other users of bodhi outside of Fedora. I'll try to point out some of the options and some of the arguments for or against those options: Options: #### Store the pungi configs in pungi-fedora git repo and git clone them from within bodhi - postive: all configs files live in the same repo. Easy to make changes to nightly pungi config files and bodhi pungi config files. - positive: we don't have to copy around the pungi configs or the variants.xml file - positive: as soon as you commit a change to the git repo it will take effect - negative: bodhi needs to learn about another place where config is stored and git clone a repo to grab the config - negative: possible bad experience for sysadmins managing bodhi machines #### Store pungi config for bodhi in infra ansible - place them on bodhi backend machines using ansible - positive: more configuration for bodhi lives in the ansible git repo - positive: maybe sys-admins will like this better? - negative: we manage pungi configs in separate places (pungi-fedora and infra ansible repo) - negative: we have to make a copy of the variants file from pungi-fedora in infra ansible repo #### Store pungi config in pungi-fedora repo - place them on bodhi backend machines using ansible - positive: other users of bodhi (not Fedora) can still place their pungi configs manually on the machine using whatever mechanism they like. They are not forced to have a git repo for the configs. - negative: config still doesn't live in ansible (sys-admins might not like this) - negative: when you commit to the pungi-fedora git repo you also need to get someone to run an ansible playbook to apply the change `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6971

5 years, 9 months

2
1
0 / 0

pungi->bodhi - where should pungi configs be stored?

by Dusty Mabe

I just created an issue in the releng pagure about $SUBJECT. Please read and weigh in on that topic. https://pagure.io/releng/issue/6971 Dusty

5 years, 9 months

1
0
0 / 0

[pungi-fedora] PR #331: Adding missing 'f' to the comps file name

by Mohan Boddu

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Adding missing 'f' to the comps file name `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/331

5 years, 9 months

2
2
0 / 0

[pungi-fedora] PR #324: f27: container merge recent changes from rawhide back into f27

by Dusty Mabe

dustymabe opened a new pull-request against the project: `pungi-fedora` that you are following: `` f27: container merge recent changes from rawhide back into f27 `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/324

5 years, 9 months

2
5
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng August 2017