rel-eng July 2019

rel-eng@lists.fedoraproject.org

9 participants
162 discussions

[pungi-fedora] PR #598: Fedora Minimal Compose for OpenQA testing
by Mohan Boddu 09 Mar '21

09 Mar '21

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

5 20

[pungi-fedora] PR #438: Add post-compose rsync script
by Kellin 08 Mar '21

08 Mar '21

kellin opened a new pull-request against the project: `pungi-fedora` that you are following: `` Add post-compose rsync script `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/438

3 2

[pungi-fedora] PR #502: WIP: Add fedora-atomic-ws config
by Colin Walters 08 Mar '21

08 Mar '21

walters opened a new pull-request against the project: `pungi-fedora` that you are following: `` WIP: Add fedora-atomic-ws config `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/502

6 20

[pungi-fedora] Issue #501: Mark compiler-rt as multilib
by Tom Stellard 26 Jan '21

26 Jan '21

tstellar reported a new issue against the project: `pungi-fedora` that you are following: `` The i686 packages for compiler-rt are no longer available in the x86_64 repositories starting with Fedora 27. Could you mark this package as multilb. See https://bugzilla.redhat.com/show_bug.cgi?id=1513286 `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/issue/501

2 3

[pungi-fedora] PR #731: cloud: remove s390x from image builds
by Dusty Mabe 06 Jan '21

06 Jan '21

dustymabe opened a new pull-request against the project: `pungi-fedora` that you are following: `` cloud: remove s390x from image builds `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/731

4 11

[pungi-fedora] Issue #738: Replace build_composeinfo with compose-create-legacy-composeinfo
by Martin Styk 21 May '20

21 May '20

martstyk reported a new issue against the project: `pungi-fedora` that you are following: `` I suggest replacing build_composeinfo with compose-create-legacy-composeinfo (compose-utils package). build_composeinfo is not providing enough information to distinguish between 2 composes. For example Beta & GOLD. F29 GOLD https://paste.fedoraproject.org/paste/kfRpr5QYWq64vrQZlp2Kqg F29 Beta https://paste.fedoraproject.org/paste/HjE6dcKJFWRKJf4iZ5XQEA This can lead to consider GOLD & Beta as same compose which is obviously wrong. On other hands .composeinfo generated by compose-create-legacy-composeinfo looks like this: F29 GOLD https://paste.fedoraproject.org/paste/pyJhX1qlWy-S2CWZDO-xKQ F29 Beta https://paste.fedoraproject.org/paste/7OcbcowriGvk7wKX3r8hQw `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/issue/738

6 7

[pungi-fedora] Issue #426: Convert file sync from one-liner to durable shell script
by Kellin 15 May '20

15 May '20

kellin reported a new issue against the project: `pungi-fedora` that you are following: `` The way we rsync composes today is a one-liner bash script that is not very durable and requires that a release engineer babysit it through the entire four hour rsync process. I am going to make this more durable, however, it will also slightly change our process behind the scenes. Today if a process works or is DOOMED after a full run it is assigned an RC release number. (EG: 1.1, 1.2, 1.3, etc). If the compose fails quickly from something such as a failure to have signed packages then it will not be assigned a release candidate. Per @mohanboddu there is not a durable way to identify the all of the different ways the special case DOOMed composes occur so they will be assigned an RC number after the automation is deployed. The only visible change will be extra gaps in the RC composes in /pub/alt/stage that represent these extra numbers being inserted to the sequence. @mohanboddu is fine with this change; does anyone else have objections? @ausil , @kevin , @puiterwijk please let me know. The initial script PR will be coming within the next two business days. `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/issue/426

4 7

[pungi-fedora] Issue #740: composeinfo file in Fedora Rawhid
by Mike Boswell 03 Dec '19

03 Dec '19

mboswell reported a new issue against the project: `pungi-fedora` that you are following: `` We started having Beaker import issues around July 17th. There seems to be a mismatch in the .composeinfo file and the compose. I was able to successfully import secondary Rawhide w/ the following edit: [variant-Everything] -arches = ppc64le,s390x +arches = ppc64le,i386,s390x id = Everything name = Everything type = variant Below was the error prior to manual edit of composeinfo. [root@fedmsg fedmsg]# beaker-import --dry-run --lab-controller=http://lab-02.rhts.eng.bos.redhat.com:8000 http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhide… ftp://download. eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhide-20190725.n.0 nfs://aoe-cluster.lab.bos.redhat.com:/ibm/exports/fedmsg/dumpdata/secondary/Fedora-Rawhide-20190725.n.0 2019-07-26 15:29:27,072 root INFO Dry Run only, no data will be sent to beaker 2019-07-26 15:29:27,205 root INFO Attempting to import: http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhide… 2019-07-26 15:29:27,226 root INFO Attempting to import: http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhide… 2019-07-26 15:29:27,273 root INFO Fedora-Rawhide-20190725.n.0 Everything ppc64le added to beaker. 2019-07-26 15:29:27,293 root INFO Attempting to import: http://download.eng.bos.redhat.com/fedmsg/dumpdata/secondary/Fedora-Rawhide… 2019-07-26 15:29:27,367 root CRITICAL No section: 'images-i386' `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/issue/740

3 7

[releng] Issue #8569: Side tag for llvm rebase in Rawhide
by Tom Stellard 13 Sep '19

13 Sep '19

tstellar reported a new issue against the project: `releng` that you are following: `` * Describe the issue We need a side tag (f31-llvm) for the upcoming llvm rebase in Fedora * When do you need this? (YYYY/MM/DD) 07/29/2019 * When is this no longer needed or useful? (YYYY/MM/DD) 08/29/2019 * If we cannot complete your request, what is the impact? Temporary breakage in rawhide when the LLVM rebase occurs. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8569

3 7

[releng] Issue #7793: Implement new Fedora Security policy for retiring packages with security bugs
by Huzaifa Sidhpurwala 13 Sep '19

13 Sep '19

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.fedorapr… "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=hi… 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=hi… 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

5 12

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2019