September 2019 - rel-eng - Fedora Mailing-Lists

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

by Kevin Fenzi

kevin added a new comment to an issue you are following: `` This work has started happening. I am tracking it in https://pagure.io/fedora-infrastructure/issue/8065 We can keep this open to track it further here, or just close in favor of the other one, either is fine with me. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6805

4 years, 8 months

1
0
0 / 0

[releng] Issue #5967: Enable source repo generation

by Kevin Fenzi

kevin added a new comment to an issue you are following: `` Hey, we did this. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/5967

4 years, 8 months

1
0
0 / 0

[releng] Issue #5967: Enable source repo generation

by Kevin Fenzi

The status of the issue: `Enable source repo generation` of project: `releng` has been updated to: Closed as Fixed by kevin. https://pagure.io/releng/issue/5967

4 years, 8 months

1
0
0 / 0

[pungi-fedora] PR #763: drop publishing i686 trees ( https://fedoraproject.org/wiki/Releases/31/ChangeSet#No_i686_Repositories )

by Kevin Fenzi

kevin opened a new pull-request against the project: `pungi-fedora` that you are following: `` drop publishing i686 trees ( https://fedoraproject.org/wiki/Releases/31/ChangeSet#No_i686_Repositories ) `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/763

4 years, 8 months

2
2
0 / 0

Fedora 31 Beta Go/No-Go meeting

by Ben Cotton

Dear all, The Go/No-Go meeting for the Fedora 31 Beta release will be held on Thursday, 2019-09-12 at 17:00 UTC in #fedora-meeting-1. For more information, see: https://fedoraproject.org/wiki/Go_No_Go_Meeting View the meeting on Fedocal at: https://apps.fedoraproject.org/calendar/meeting/9613/ -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

4 years, 8 months

1
0
0 / 0

[releng] Issue #8421: allow coreos team to regen coreos distrepos

by Dusty Mabe

dustymabe reported a new issue against the project: `releng` that you are following: `` * Describe the issue Today we had an issue where the distrepo yum repos for our coreos tags went away. @mohanboddu regenerated them for us. We're not sure why they went away (this should probably also be investigated), but we'd like the ability to regen them on our own in case this happens again in the future (i.e. we'd like to be able to unblock ourselves in case it happens in a scenario where we need a build and time is critical) the commands were: - `koji dist-repo f29-coreos-continuous 429476B4 --allow-missing-signatures` - `koji dist-repo f30-coreos-continuous CFC659B9 --allow-missing-signatures` - `koji dist-repo coreos-pool 429476B4 CFC659B9` * When do you need this? (YYYY/MM/DD) would be nice to have it in the nxt week * When is this no longer needed or useful? (YYYY/MM/DD) never * If we cannot complete your request, what is the impact? we wait until releng can complete our request `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8421

4 years, 8 months

3
15
0 / 0

[releng] Issue #8743: Unorphan linkchecker

by Miro Hrončok

churchyard reported a new issue against the project: `releng` that you are following: `` * Name of the package? linkchecker * FAS username of the new maintainer? churchyard * Any extra information? no `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8743

4 years, 8 months

1
1
0 / 0

[releng] Issue #8742: Orphan packages

by Lumír Balhar

4 years, 8 months

2
4
0 / 0

[releng] Issue #8741: openzwave package did not get properly tagged into Rawhide

by Michael Cronenworth

mooninite reported a new issue against the project: `releng` that you are following: `` * Describe the issue I built a new update for the openzwave package a few days ago. https://koji.fedoraproject.org/koji/buildinfo?buildID=1368569 A bodhi update was never automatically created for it. It has never made it into the f32 tag. * When do you need this? (YYYY/MM/DD) ASAP * When is this no longer needed or useful? (YYYY/MM/DD) * If we cannot complete your request, what is the impact? The 'domoticz' package will fail to build. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8741

4 years, 8 months

2
2
0 / 0

[releng] Issue #8737: Please workaround koji bug 789

by Mat Booth

mbooth reported a new issue against the project: `releng` that you are following: `` * Describe the issue Since the upstream for my packages dropped 32bit support, I had to add "ExclusiveArch" to many of my noarch packages. And now this koji bug: https://pagure.io/koji/issue/789 is costing me hours and hours of lost time baby-sitting builds that hit builders for the wrong architecture. Since there is clearly no will to look at the problem on the koji side (6 months and no response!) can we work around the problem on the releng side? One possible workaround I heard about would be to split x86 builders into 2 groups, each group would only support one arch: either x86_64 or i386. Then I could guarantee my package would get a correct builder. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8737

4 years, 8 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng September 2019