Re: [PATCH] Removing branched composes

As per Kevin's comment, just commenting the lines. And, here's the new diff: diff --git a/roles/releng/files/branched b/roles/releng/files/branched index 26fee6c..64192dd 100644 --- a/roles/releng/files/branched +++ b/roles/releng/files/branched @@ -1,4 +1,4 @@ # branched compose

Re: Freeze break: fix bodhi to poll armhfp instead of aarch64

Since its going to only check the first arch +1 from me. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Configure Bodhi to know how to find alternate arch syncs

LGTM +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR for f26 atomic two week nightly compose

New diff as per your comments, putting f26 first and both f26 and f25 atomic composes are one after the other: diff --git a/roles/releng/files/twoweek-updates b/roles/releng/files/twoweek-updates index 3b6df85..052a6e3 100644 --- a/roles/releng/files/twoweek-updates +++

FBR for f26 atomic two week nightly compose

We are planning to start composing f26 atomic two week nightly composes, could you verify the diff - https://paste.fedoraproject.org/paste/Ne6ctmNq0QyE4a5mmiSFXQ and do the necessary tasks. Thanks. Mohan Boddu. ___ infrastructure mailing list

Re: FBR for f26 atomic two week nightly compose

diff --git a/roles/releng/files/twoweek-updates b/roles/releng/files/twoweek-updates index 3b6df85..022c7ec 100644 --- a/roles/releng/files/twoweek-updates +++ b/roles/releng/files/twoweek-updates @@ -1,6 +1,6 @@ -# 2 week updates nightly compose +#Fedora 25 two-week updates nightly compose

Re: FBR - a timeout for the koji pkglist sync script

+1, default timeout cant be 12 hours. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

FBR for 0-day release actions

As per 0-day Release Actions under https://infrastructure.fedoraproject.org/infra/docs/docs/sysadmin-guide/sops/bodhi.rst SOP, I made the following changes: diff --git a/roles/bodhi2/backend/templates/atomic-config.py.j2 b/roles/bodhi2/backend/templates/atomic-config.py.j2 index

Re: FBR for disabling branched composes

Sorry, I just realized F27 modular is still in beta, so I am gonna leave it like that. New diff: diff --git a/roles/releng/files/branched b/roles/releng/files/branched index 270a6a1..30e3928 100644 --- a/roles/releng/files/branched +++ b/roles/releng/files/branched @@ -1,4 +1,4 @@ # branched

FBR for disabling branched composes

As we already have Gold RC compose, its time to disable nightlies. diff --git a/roles/releng/files/branched b/roles/releng/files/branched index 270a6a1..e8f3f58 100644 --- a/roles/releng/files/branched +++ b/roles/releng/files/branched @@ -1,4 +1,4 @@ # branched compose

Re: [PATCH] add syncing for f27-u-t ostree ref

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR for 0-day release actions

As per Dusty comment, new patch: diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2 index 1629e2d..5b22659 100644 --- a/roles/bodhi2/base/templates/production.ini.j2 +++ b/roles/bodhi2/base/templates/production.ini.j2 @@ -10,7 +10,7 @@

Re: FBR: Enable multi-arch ostree composes for F27+

LGTM +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

FBR: Update pungi on branched-composer.phx2.fedoraproject.org and compose-x86-02.phx2.fedoraproject.org

We need https://pagure.io/pungi/c/c89f0334579aee68286d07d4b57f4df67510166c?branch=master patch to create live images for arm in modularity, which is included in Pungi 4.1.20 release. So, I would like to update the branched composer and try it out. And if possible include it in F27 Beta Modular

Retroactive FBR for pungi update to pungi-4.1.19-3 on compose-x86-02.phx2.fedoraproject.org

We had a request to do a nightly F27 modular compose and when we tried to do the compose it failed due to comps not allowed in gather_source of type modules. So, we had to update pungi in compose-x86-02.phx2.fedoraproject.org. I totally forgot about the freeze and updated the box and hence

Re: FBR: Bodhi 3.0

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Freeze Break Request: update rpm on builders

+1 if its not going to affect on our f27 final or f27 modular server beta releases. Having rollback will help us getting back to the previous rpm version so I think its okay. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To

Re: Updates for AtomicHost artifacts in bodhi pungi runs

LGTM +1 But, can we add a branched release variable, so that we dont need to add the branch release version multiple times at different places? On Fri, Jun 1, 2018 at 4:06 PM Kevin Fenzi wrote: > On 06/01/2018 06:58 AM, Dusty Mabe wrote: > > [PATCH 1/5] bodhi-pungi: f29 will be new branched

FBR for Bodhi F28 release status update

Now that we got a gold compose, we would like to change bodhi configs to reflect F28 GA changes. There are some duplicates which doesn't make sense and hence removing them. diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2 index

Re: FBR : Disable F28 branched compose and enable two week atomic, cloud and container nightlies

On Thu, Apr 26, 2018 at 4:55 PM Dusty Mabe <du...@dustymabe.com> wrote: > > > On 04/26/2018 04:39 PM, Mohan Boddu wrote: > > Now that we got a F28 RC final compose, we dont need branched composes > anymore and also we should enable two week atomic, cloud and container

Re: FBR: Fix new-updates-sync typo

LGTM +1 On Thu, Apr 26, 2018 at 6:57 PM Patrick Uiterwijk wrote: > Hi, > > Can I get +1s for the following fix to my last version of the script? > > Patrick > > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync >

Re: Freeze Break Request: update new-updates-sync to sync f28 stable updates

LGTM +1 On Thu, Apr 26, 2018 at 8:35 PM Kevin Fenzi wrote: > We kinda need to sync f28 stable updates too: > > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync > > index 7cfe15e..21600c7 100755 > > ---

Re: FBR: Make new-updates-sync resync on re-stage without need for state deletion

LGTM +1 On Sun, Apr 29, 2018 at 9:44 AM Patrick マルタインアンドレアス Uiterwijk < puiterw...@redhat.com> wrote: > Hi, > > So, for now (until https://github.com/fedora-infra/bodhi/pull/1986 gets > finished and merged), it might happen that Bodhi stages a repo a second > time (if it crashed while waiting

Re: [PATCH] twoweek-nightly: Stop building F28 AH twoweek nightly composes

On Thu, Aug 16, 2018 at 9:11 AM Dusty Mabe wrote: > > > On 08/16/2018 01:59 AM, Sinny Kumari wrote: > > We are building Fedora 28 AH nightly artifacts during F28 bodhi-updates > run > > which produces same media name what we get during twoweek nightly [1] > compose > > run. > > > > This patch

FBR: Greenwave config update for F29

diff --git a/roles/openshift-apps/greenwave/templates/configmap.yml b/roles/openshift-apps/greenwave/templ index dd297c4..694ca3c 100644 --- a/roles/openshift-apps/greenwave/templates/configmap.yml +++ b/roles/openshift-apps/greenwave/templates/configmap.yml @@ -97,6 +97,7 @@ data: ---

Re: FBR: Greenwave config update for F29

ora-29 - fedora-28 - fedora-27 - fedora-26 On Tue, Aug 28, 2018 at 10:10 AM Ralph Bean wrote: > LGTM. Easy to roll back if it is incorrect. +1 > > On Tue, Aug 28, 2018 at 10:05:08AM -0400, Mohan Boddu wrote: > > diff --git a/roles/openshift-apps/greenwave/t

Re: FBR: Fix for new-updates-sync

('Release %s, repo %s, target %s', release, repo, target) RELEASES[release]['repos'][repo]['from'] = target return target On Tue, Aug 28, 2018 at 12:51 PM Mohan Boddu wrote: > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync &

Re: FBR: Fix for new-updates-sync

Aug 28, 2018 at 1:10 PM Dusty Mabe wrote: > LGTM - one comment below > > On 08/28/2018 12:59 PM, Mohan Boddu wrote: > > Better wording of the comment: > > > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sy

FBR: Fix for new-updates-sync

diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 3619e6c..5f00b29 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -367,10 +367,13 @@ def determine_last_link(release, repo):

FBR: Autosigning for post bodhi activation of F29

--- a/roles/robosignatory/files/robosignatory.production.py +++ b/roles/robosignatory/files/robosignatory.production.py @@ -132,28 +132,21 @@ config = { "keyid": "cfc659b9", "type": "modular" }, -{ -

Re: FBR: Set up docs.teamsilverblue.org

LGTM +1 On Tue, Aug 28, 2018 at 7:10 PM Mikolaj Izdebski wrote: > +1 > > On 08/29/2018 01:06 AM, Patrick Uiterwijk wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA512 > > > > Hi all, > > > > So, teamsilverblue pointed their DNS to us without informing us, can I > get +1s to add a

Re: [PATCH] rawhide ostree sync as part of new-updates-sync script

8/27/2018 04:07 PM, Mohan Boddu wrote: > > Dusty, how about this: > > > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync > > index 9ddc591..194e2bd 100755 > > --- a/roles/bodhi2/backend/files/new-updates-syn

Re: [PATCH] rawhide ostree sync as part of new-updates-sync script

, 2018 at 4:02 PM Dusty Mabe wrote: > mostly looks good a few nits inline > > On 08/27/2018 03:57 PM, Mohan Boddu wrote: > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync > > index 9ddc591..4537f0b 100755 > > --

[PATCH] rawhide ostree sync as part of new-updates-sync script

diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 3bcfbea..1cb22c2 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -20,7 +20,23 @@ FEDORAALTDEST =

Re: [PATCH] robosig: rename atomic workstation to silverblue

LGTM +1 On Sun, Aug 26, 2018 at 10:50 PM Dusty Mabe wrote: > --- > roles/robosignatory/files/robosignatory.production.py | 8 > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/roles/robosignatory/files/robosignatory.production.py >

FBR : To fix rawhide sync location

Fix for https://pagure.io/releng/issue/7731. This can be a temporary fix or permanent fix depends on which way we choose to proceed. If you think we should go back and revert the changes we made to this script and just sync them as part of nightly.sh, please -1 this. diff --git

Re: FBR: hotfix - Don't clean old mashes

LGTM +1 On Wed, Aug 29, 2018 at 12:27 PM Kevin Fenzi wrote: > +1 and we can think about this and revisit after freeze. > > kevin > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to >

Re: FBR : To fix rawhide sync location

o we can get our rawhide out of rawhide > > On Wed, 29 Aug 2018 at 10:09, Mohan Boddu wrote: > > > > > > Fix for https://pagure.io/releng/issue/7731. > > > > > > This can be a temporary fix or permanent fix > > > depends on which way we choose to

Re: Freeze Break: some more bodhi config for f29

LGTM +1 On Wed, Aug 29, 2018 at 3:24 PM Stephen John Smoogen wrote: > > +1 after review > > On Wed, 29 Aug 2018 at 14:07, Kevin Fenzi wrote: > >> > diff --git a/roles/bodhi2/base/templates/production.ini.j2 >> b/roles/bodhi2/base/templates/production.ini.j2 >> > index 37d8608..a44ffab 100644

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

Based on Randy's explanation +1 On Wed, Aug 29, 2018 at 3:37 PM Randy Barlow wrote: > On 08/29/2018 03:26 PM, Stephen John Smoogen wrote: > > Can you give me more information on what this will due, what could go > > wrong and how to recover? If not I don't think I can give an answer. > > Bodhi

Re: [PATCH] bodhi pungi ostree: point to different repos for f28

LGTM +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Update Bodhi tree filenames for atomic-workstation

LGTM +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

FBR: To update pungi on branched-composer.phx2.fedoraproject.org and rawhide-composer.phx2.fedoraproject.org to pungi-4.1.22-8.fc27

https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/PQUO2BPFYAOHT4DPICFSUMSSQEXO6UT3/ created an issue of skipping the noarch and multilib arches from Everything repo, this should be fixed in pungi-4.1.22-8.fc27 koji build:

Re: FBR: To update pungi on branched-composer.phx2.fedoraproject.org and rawhide-composer.phx2.fedoraproject.org to pungi-4.1.22-8.fc27

Correcting the statement: https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora... created an issue of skipping the noarch and multilib *builds* from Everything repo, this should be fixed in pungi-4.1.22-8.fc27 ___ infrastructure

FBR: To update pungi on branched-composer.phx2.fedoraproject.org and rawhide-composer.phx2.fedoraproject.org to pungi-4.1.22-7.fc27

We were having issues with modular rpms ending up in Everything repo and also missing Container variant, which should be fixed by pungi-4.1.22-7.fc27 update. koji build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1055890 Fixes: https://pagure.io/pungi/issue/862

FBR: To update pungi on branched-composer.phx2.fedoraproject.org and rawhide-composer.phx2.fedoraproject.org to pungi-4.1.22-9.fc27

This will fix the issue with empty module variant and also skipping buildinstall phase on variants. Koji build - https://koji.fedoraproject.org/koji/buildinfo?buildID=1058071 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To

Re: FBR $arch vs $basearch fixups for bodhi AH artifacts

LGTM +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR bodhi-pungi: Add AtomicHost variant

LGTM +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR fixes to bodhi-pungi configs for atomichost artifacts

I agree with Kevin, but also it seems that patch should be working So, +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: [FBR] fix the alternativearch git hook

LGTM +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Update fedmsg on compose-x86-01

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

FBR: To update pungi on compose-x86-01.phx2.fedoraproject.org to pungi-4.1.22-10.fc27

We updated pungi on branched and rawhide composer a lot during this freeze, here's the list of the FBR and why we updated pungi https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedoraproject.org/thread/TPAIGZ5WNTBLDNHBX47X5SH6S4Q4PB3O/

Re: Freeze Break Request: Change oz.cfg on power builders to just use 1 cpu for now

LGTM, +1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: To update pungi on compose-x86-01.phx2.fedoraproject.org to pungi-4.1.22-10.fc27

I didn't want to update it since pungi had so many issues with modular support. Hence I waited this long. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

FBR: To update pungi on branched-composer.phx2.fedoraproject.org and rawhide-composer.phx2.fedoraproject.org to pungi-4.1.22-10.fc27

pungi-4.1.22-10 should finally fix the issue with modular rpms getting into Everything repo Pungi Bug: https://pagure.io/pungi/issue/862 Fix: https://pagure.io/pungi/issue/862#comment-499692 Koji Build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1059055

Re: FBR: Make new-updates-sync print what it did and email to releng-cron

+1 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

FBR : Disable F28 branched compose and enable two week atomic, cloud and container nightlies

Now that we got a F28 RC final compose, we dont need branched composes anymore and also we should enable two week atomic, cloud and container nightlies diff --git a/roles/releng/files/branched b/roles/releng/files/branched index e303942..b560be1 100644 --- a/roles/releng/files/branched +++

Re: The trouble with torrents

On Wed, Sep 26, 2018 at 2:03 PM Kevin Fenzi wrote: > So, Fedora 29 Beta is out the door and mostly that went very smoothly as > always. With one exception: torrents. > > Right now we are (were) using the last opensource version of > 'bittorrent' python client to seed our torrents. However, I

Re: [Freeze Break Request: ] Also install the username/pass for pushing to the stg candidate registery.

+1 On Mon, Oct 15, 2018 at 2:06 PM wrote: > From: Kevin Fenzi > > Signed-off-by: Kevin Fenzi > --- > playbooks/groups/releng-compose.yml | 1 - > 1 file changed, 1 deletion(-) > > diff --git a/playbooks/groups/releng-compose.yml > b/playbooks/groups/releng-compose.yml > index

Re: Note on ansible release variables

On Fri, Oct 12, 2018 at 4:01 PM Kevin Fenzi wrote: > Greetings everyone. > > I thought I would send a short note on something I put in place before > the freeze. Basically it seems, even though we have SOPs and docs, we > spend a lot of time around release milestones changing files in ansible, >

Re: Freeze Break Request: fix up registry

LGTM +1 On Tue, Oct 16, 2018 at 3:12 PM Patrick マルタインアンドレアス Uiterwijk < puiterw...@redhat.com> wrote: > +1 > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to >

Re: Note on ansible release variables

On Thu, Oct 18, 2018 at 3:05 PM Kevin Fenzi wrote: > On 10/15/18 12:21 PM, Mohan Boddu wrote: > > > Then I think we should use another variable (probably RelengFreeze) > > to indicate releng freeze, as they dont actually end on the same day. > > Also, we are using it for

FBR: F29 is now GA and no need of special policy changes

commit 6bbd8c072381561a664290a7ded3871173e5eab2 Author: Mohan Boddu Date: Fri Oct 26 14:31:08 2018 + F29 is now GA and no need of any policy changes This change is to just disable roles/bodhi2/base/templates/production.ini.j2#n580 roles/bodhi2/base/templates

Re: [PATCH] new-updates-sync: no longer sync stable refs for ostrees

LGTM +1 On Mon, Oct 29, 2018 at 2:44 PM Kevin Fenzi wrote: > Sure. +1 > > kevin > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora

FBR: To enable 29 container and cloud composes

Please review the following patch to enable F29 container and cloud composes diff --git a/roles/releng/files/docker-updates b/roles/releng/files/docker-updates index f23ac64..c7b3f8d 100644 --- a/roles/releng/files/docker-updates +++ b/roles/releng/files/docker-updates @@ -1,4 +1,4 @@ -#Fedora 28

FBR: Disable F29 branched compose

This is to disable F29 branched composes since we got F29 GA gold compose diff --git a/roles/releng/files/branched b/roles/releng/files/branched index 561b8e0..cbcafff 100644 --- a/roles/releng/files/branched +++ b/roles/releng/files/branched @@ -1,3 +1,3 @@ # branched compose

Automating bodhi daily pushes

Please review this change: diff --git a/roles/bodhi2/backend/files/bodhi-automated-pushes.cron b/roles/bodhi2/backend/files/bodhi-au new file mode 100644 index 000..7e12cfd --- /dev/null +++ b/roles/bodhi2/backend/files/bodhi-automated-pushes.cron @@ -0,0 +1 @@ +59 23 * * * apache

Re: Automating bodhi daily pushes

Okay, fixed. And as Randy mentioned, we can use this without fixing @2579. diff --git a/roles/bodhi2/backend/files/bodhi-automated-pushes.py b/roles/bodhi2/backend/files/bodhi-auto new file mode 100644 index 000..aacc81c --- /dev/null +++

Re: [PATCH] Silverblue manifest is now fedora-silverblue.yaml

LGTM +1 On Mon, Nov 19, 2018 at 5:27 PM Dusty Mabe wrote: > --- > roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 > b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 >

Re: Proposal : Use OSBS to build the fedora container base image

+1 to the change proposal. Someone still need to submit updates in bodhi and rel-eng would be happy to own that task and it is much simpler than what we have today. On Mon, Dec 3, 2018 at 1:39 PM Clement Verna wrote: > Hi all, > > I would like to get feedbacks on the following proposal. Use

Re: FBR: Push a fix to clean_amis.py in fedimg box

LGTM +1 On Wed, Mar 27, 2019 at 1:26 PM Kevin Fenzi wrote: > On 3/27/19 2:57 AM, Sayan Chowdhury wrote: > > I need to push a fix to run the clean_amis script. The diff is as > follows: > > +1 here. > > kevin > > > ___ > infrastructure mailing list --

FBR: To add coreos-continuous permission to koji hub policy

Core OS folks wanted to have a separate koji tag to build and tag their Core OS continuous builds. This has been discussed in the releng ticket - https://pagure.io/releng/issue/8165. Also, we tested it staging koji and has been working fine. Here's the staging koji ansible commit:

Re: FBR: Apply MBS PR#1185 to fix Module Stream Expansion with new platform streams

LGTM +1 On Wed, Mar 27, 2019 at 1:29 PM Kevin Fenzi wrote: > +1 > > kevin > > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to > infrastructure-le...@lists.fedoraproject.org > Fedora Code

FBR: Unfreeze RelEng to push updates

Hello, I dont know if this FBR is needed or not, but now that we have a GOLD compose for F30 Beta and all the requested f30 builds pushed stable and I cloned f30-Beta tag from f30, now we can start pushing updates to F30 stable as well along with the others. +1's please diff --git

Re: FBR: clean up disk space on mirrors

On Mon, Mar 25, 2019 at 8:37 AM Stephen John Smoogen wrote: > 1. Remove F29beta from mirrors so mirrors can keep up > /pub/fedora/linux/releases/test/29_Beta/ > +1 > > 2. Move F27 to archives > a. Have mirrormanager point to /pub/archives/fedora/linux/27 > b. Remove /pub/fedora/linux/27 > +1 >

Re: Enable signing on f30-signing-pending tag

;: "f30-modular-updates-candidate", - "to": "f30-modular", +"to": "f30-modular-updates-testing-pending", "key": "fedora-30", "keyid": "c

Re: Enable signing on f30-signing-pending tag

Sorry, forgot to include Freeze Break Request for F30 Beta. On Wed, Mar 6, 2019 at 9:41 AM Mohan Boddu wrote: > This will enable signing on f30-signing-pending tag and once signed the > updates will be pushed to f30-updates-testing-pending tag > > diff --git a/roles/robosig

FBR to add fedora-30 key to bodhi pungi configs

Please review the FBR and +1 it, thanks. diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm. index b0742ec..8d9e9a3 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -27,6

[FBR] To update python-productmd on rawhide-composer.phx2.fp.o

We need python-productmd-1.20-1.fc29 to fix an issue with image types in sync with formats. This will enable us to generate vmdk format images for cloud. Patch: https://github.com/release-engineering/productmd/pull/108/files Also, I will be using f29-infra repos as this build is still in

Re: [FBR ] releng-compose: Just have compose-x86-01 get the default group values for mem and cpus

LGTM +1 On Tue, Mar 19, 2019 at 4:51 PM wrote: > From: Kevin Fenzi > > In recent months/years, pungi has started to use more and more memory when > gathering package sets. > So, give it enough memory to avoid the OOM killer killing composes. > > Signed-off-by: Kevin Fenzi > --- >

Re: "FBR: To update python3-productmd on compose-x86-01.phx2.fp.o"

Thanks guys :) On Wed, Mar 20, 2019 at 11:18 AM Rick Elrod wrote: > +1 > > -re > > On 3/20/19 8:15 AM, Mohan Boddu wrote: > > The recent RC compose failed due to: > > > > ValueError: Image: Field 'type' has invalid value: vmdk > > > > Support for vm

"FBR: To update python3-productmd on compose-x86-01.phx2.fp.o"

The recent RC compose failed due to: ValueError: Image: Field 'type' has invalid value: vmdk Support for vmdk was added in python3-productmd-1.21-1.fc29 version. Once updated, this issue should be fixed. Thanks. ___ infrastructure mailing list --

Re: "FBR: To update python3-productmd on compose-x86-01.phx2.fp.o"

Just to be clear, vmdk issue was fixed in python3-productmd-1.20-1.fc29 but that introduced another issue with a typo, which is fixed in python3-productmd-1.21-1.fc29. On Wed, Mar 20, 2019 at 8:15 AM Mohan Boddu wrote: > The recent RC compose failed due to: > > ValueError: Image: Fi

[FBR] Adding f30 key to bodhi modular pungi config

This patch will add fedora-30 key to bodhi modular pungi config. diff --git a/roles/bodhi2/backend/templates/pungi.module.conf.j2 b/roles/bodhi2/backend/templates/pungi.module.conf.j2 index bb021eb..43c6a7e 100644 --- a/roles/bodhi2/backend/templates/pungi.module.conf.j2 +++

Re: [FBR] Adding f30 key to bodhi modular pungi config

Thanks for +1's and its going into the doc. On Mon, Mar 11, 2019 at 1:26 PM Kevin Fenzi wrote: > +1 > > (and also update the branching docs to do this on branch next time. ;) > > kevin > > > ___ > infrastructure mailing list --

Re: pagure -> bugzilla sync script 'tiger team'

Count me in. I am happy to help as well. On Thu, Apr 11, 2019 at 8:40 PM Kevin Fenzi wrote: > On 4/10/19 12:45 AM, Pierre-Yves Chibon wrote: > > On Tue, Apr 09, 2019 at 07:37:56PM +0200, Clement Verna wrote: > >> On Sun, 7 Apr 2019 at 21:04, Kevin Fenzi wrote: > > >> I ll be happy to help

Re: [PATCH] tag2distrepo: also regen f*-coreos-continuous repos

I am +1 to this change. But I also would like @Kevin Fenzi to verify it as well. On Thu, Apr 11, 2019 at 3:05 PM Jonathan Lebon wrote: > We want to be able to get automatically regenerated yum repos whenever > we build into the continuous tags. This will be used by the Fedora > CoreOS team for

Compose Tracker Discussion

moving it to make it official. Please let me know if you have any questions. [1] https://pagure.io/releng/compose-tracker Thanks, Mohan Boddu. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email

Re: [[FBR] Freeze Break Request: ] dns: Actually drop the limit on the group we defined in the last commit.

+1 On Tue, Apr 30, 2019 at 4:46 PM Patrick マルタインアンドレアス Uiterwijk < puiterw...@redhat.com> wrote: > +1 > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to >

Re: [[FBR] Freeze Break Request: ] dns: add 2 rh nameservers that make a lot of legit queries against our dns.

+1 On Tue, Apr 30, 2019 at 4:46 PM Patrick マルタインアンドレアス Uiterwijk < puiterw...@redhat.com> wrote: > +1 > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to >

Re: PATCH: Setup for coreos-pool and coreos-release tags

FYI, I am using the coreos-continuous permission since its the same people who will be working on this as well. On Wed, May 1, 2019 at 1:24 PM Mohan Boddu wrote: > CoreOS needs coreos-pool and coreos-release tags to build backported > builds and tag the builds that go into the release. &g

PATCH: Setup for coreos-pool and coreos-release tags

CoreOS needs coreos-pool and coreos-release tags to build backported builds and tag the builds that go into the release. More info: https://pagure.io/releng/issue/8294 Please review the following patch and let me know if it needs any changes. diff --git a/roles/koji_hub/templates/hub.conf.j2

Re: old taiga instances

Just FYI, RelEng project has been totally moved to teams.fp.o, thanks for your help on that Kevin. On Mon, Apr 22, 2019 at 4:04 PM Kevin Fenzi wrote: > Greetings. > > We have 2 old taiga instances: taiga.fedorainfracloud.org and > taiga-stg.fedorainfracloud.org. > > Last week I disabled nginx

Re: Heads-up: Deleting bugyou role and config from ansible

+1 to delete. On Tue, Apr 23, 2019 at 6:29 AM Pierre-Yves Chibon wrote: > On Tue, Apr 23, 2019 at 12:22:30PM +0200, Clement Verna wrote: > > Hi all, > > > > I ll be deleting the bugyou role and config from our ansible > > repository since it is currently not used. > > > > See the patch file

Re: old taiga instances

Kevin and Jim, cant we just do the same thing as we did with the RelEng taiga instance, create a dump of the project and upload it to the new instance? On Tue, Apr 23, 2019 at 9:34 AM Adam Samalik wrote: > I had the Fedora Docs [1] board in there where I tracked development of > the build

Re: FBR: hotfix robosignatory to fix ostree signing issue

+1 to build the package and update the box with the newer rpm. On Thu, Aug 29, 2019 at 2:25 PM Dusty Mabe wrote: > We hit a bug every release where the directories haven't yet been > created for the refs we want to sign [1]. The bug has been fixed in > the latest code [2] but hasn't been

Re: [PATCH] robosignatory: add f31/f32 infra tags and f31-gnome side tag to be signed.

On Tue, Sep 3, 2019 at 1:23 PM Kevin Fenzi wrote: > Signed-off-by: Kevin Fenzi > --- > roles/robosignatory/files/robosignatory.production.py | 18 > ++ > 1 file changed, 18 insertions(+) > > diff --git a/roles/robosignatory/files/robosignatory.production.py >

Re: Please review: MBS platform definition for EPEL8

Hi, I created the tags as module-epel8-build and module-epel8-playground-build just to be consistent with the naming, so you need to change the config for koji_tag part. And may be also change the "stream" in the yaml file to epel8 and epel8-playground and change the name of the platform to

FBR: Update releases.json to make f31 active and no retirement

Hi, Another FBR to update releases.json to make sure retirement is not allowed diff --git a/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections.json b/roles/pkgdb-proxy/files/pkgdb-gnome-software-collections index aac977e..9e0cbf2 100644 ---

Re: Please review: MBS platform definition for EPEL8

Thanks for the info, I renamed the tags and updated the tickets. Why is naming so hard? On Thu, Oct 24, 2019 at 4:58 PM Merlin Mathesius wrote: > > > On Thu, Oct 24, 2019 at 3:32 PM Mohan Boddu wrote: > >> Hi, >> >> I created the tags as module-epel8-build and &g

  1   2   >