September 2019 - rel-eng - Fedora Mailing-Lists

[releng] Issue #8784: Please add tags, target, and Bodhi release for f31-flatpak

by Kalev Lember

kalev reported a new issue against the project: `releng` that you are following: `` See https://pagure.io/releng/issue/8238 for instructions on how to do that. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8784

4 years, 7 months

3
5
0 / 0

[releng] Issue #7793: Implement new Fedora Security policy for retiring packages with security bugs

by Huzaifa Sidhpurwala

huzaifas reported a new issue against the project: `releng` that you are following: `` We need to implement the new Fedora Security policy as per: https://lists.fedoraproject.org/archives/list/devel-announce@lists.fedora... "If a CRITICAL or IMPORTANT security issue is currently open against a package, or a security issue of lower severity has been open for at least 6 months, four weeks before the branch point a procedure similar to long-standing FTBFS will be triggered immediately, with 8 weeks of weekly notifications to maintainers and subsequent orphaning and then subsequent removal from distribution. This applies to all packages, not just leaf." So before 4 weeks before the branch point, we need to ensure that: 1. Packages which have any pending critical or important security flaws open ie: https://bugzilla.redhat.com/buglist.cgi?bug_severity=urgent&bug_severity=... are marked for FTBS and not built. 2. Packages which have any <important flaws open for atleast 6 months or more ie: https://bugzilla.redhat.com/buglist.cgi?bug_severity=urgent&bug_severity=... are marked for FTBS and not build. * When do you need this? 2019-01-01 - Much before the last branch point. * If we cannot complete your request, what is the impact? Fedora 30 will ship lot of insecure packages. Major issue for the release. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7793

4 years, 7 months

5
12
0 / 0

[releng] Issue #8624: Unretire mingw-libsoup

by Kalev Lember

kalev reported a new issue against the project: `releng` that you are following: `` mingw-libsoup got retired in the recent FTBFS cleanup. Please unretire it and unblock in f31. I'll take care of fixing the FTBFS. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8624

4 years, 7 months

3
7
0 / 0

[releng] Issue #8791: Enable tag2distrepo for active infra tags

by Mikolaj Izdebski

mizdebsk reported a new issue against the project: `releng` that you are following: `` Fedora infrastructure relies on tag2distrepo plugin to have dist repos generated for content of their Koji tags. However certain less-often used tags don't have tag2distrepo configured. Please enable tag2distrepo Koji plugin for the following Koji tags: - epel8-infra - epel8-infra-stg - f31-infra - f31-infra-stg - f32-infra - f32-infra-stg Koji admin can do this with the following commands: ``` koji edit-tag -x tag2distrepo.enabled=true -x tag2distrepo.keys=47dd8ef9 epel8-infra koji edit-tag -x tag2distrepo.enabled=true -x tag2distrepo.keys=47dd8ef9 epel8-infra-stg koji edit-tag -x tag2distrepo.enabled=true -x tag2distrepo.keys=47dd8ef9 f31-infra koji edit-tag -x tag2distrepo.enabled=true -x tag2distrepo.keys=47dd8ef9 f31-infra-stg koji edit-tag -x tag2distrepo.enabled=true -x tag2distrepo.keys=47dd8ef9 f32-infra koji edit-tag -x tag2distrepo.enabled=true -x tag2distrepo.keys=47dd8ef9 f32-infra-stg ``` `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8791

4 years, 7 months

2
3
0 / 0

[releng] PR #8792: Enable tag2distrepo for newly-created infra tags

by Mikolaj Izdebski

mizdebsk opened a new pull-request against the project: `releng` that you are following: `` Enable tag2distrepo for newly-created infra tags `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/8792

4 years, 7 months

2
1
0 / 0

[releng] Issue #8664: Module mass-rebuild for F32 Rawhide needed

by Stephen Gallagher

sgallagh reported a new issue against the project: `releng` that you are following: `` * Describe the issue At the Branch point, we need to perform a mass-rebuild of modular content so that they can be rebuilt against the new base module (in this case `platform:f32`). This does not seem to have happened during the F31 Branch from Rawhide, as https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-2019082... shows only those modules whose maintainers have done a manual rebuild since the Branch. * When do you need this? (YYYY/MM/DD) Immediately (2019-08-21) * When is this no longer needed or useful? (YYYY/MM/DD) When F32 goes EOL * If we cannot complete your request, what is the impact? Upgrade path on Rawhide will be broken for anyone with modules enabled. (That means pretty much everyone at this point). CC @kevin `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8664

4 years, 7 months

4
11
0 / 0

[releng] Issue #8702: F31 stable push requests

by Adam Williamson

adamwill reported a new issue against the project: `releng` that you are following: `` This ticket will be used for requesting pushes of tested blocker / freeze exception fixes during F31 release freezes. See https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process and https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process . Similar to candidate compose request tickets, this ticket can be closed by releng after each push and re-opened by QA each time a new push is needed. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8702

4 years, 7 months

3
35
0 / 0

[releng] Issue #8790: openvswitch needs to be unorphaned ASAP

by Flavio Leitner

fbl reported a new issue against the project: `releng` that you are following: `` * Describe the issue The 'openvswitch' package seem to be orphaned for no good reason as it is still maintained and important to the distribution. * When do you need this? (YYYY/MM/DD) ASAP because F31 is closing and 'openvswitch' is broken there, needs to be updated to 2.12.0. * If we cannot complete your request, what is the impact? F31 will be released with an old and broken 'openvswitch' which is used in OpenShift, OpenStack and other SDN environments. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8790

4 years, 7 months

3
6
0 / 0

[releng] Issue #8789: Errant Modules That Need To Be Retired

by Matt Prahl

mprahl reported a new issue against the project: `releng` that you are following: `` Due to a bug in MBS [1], the following modules were built and reused components from modules built against the wrong platform 6398 (perl:5.28:3020190912134325:eb1b2d95) 6397 (perl:5.28:2920190912134325:c8f01160) 6396 (perl:5.28:3120190912134325:a5d38390) 6390 (sway:rolling:3020190912072731:a5b0195c) 6389 (sway:rolling:3220190912072731:43bbeeef) 6388 (sway:rolling:3120190912072731:f636be4b) 6387 (sway:rolling:2920190912072731:6c81f848) 6386 (silver:rolling:2920190912064049:c5ebb199) 6385 (silver:rolling:3020190912064049:a23e773d) 6383 (silver:rolling:3120190912064049:22d7e2a5) Could I have permission to retire these modules using `mbs-manager retire <nsvc>` on the MBS backend? The following users are affected by this: @ignatenkobrain, @thofmann, and @ppisar. 1 - https://pagure.io/fm-orchestrator/issue/1409 `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8789

4 years, 7 months

4
13
0 / 0

Fedora 31 Beta is GO

by Ben Cotton

The Fedora 31 Beta RC1 compose[1] is GO and is will be shipped live on Tuesday, 17 September 2019. For more information please check the Go/No-Go meeting minutes [2] or log [3]. Thank you to everyone who has and still is working on this release! [1] https://dl.fedoraproject.org/pub/alt/stage/31_Beta-1.1/ [2] https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-12/f31-beta-go... [3] https://meetbot.fedoraproject.org/fedora-meeting-1/2019-09-12/f31-beta-go... -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

4 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng September 2019