April 2022 - rel-eng - Fedora Mailing-Lists

by Ben Cotton

Due to outstanding blocker bugs[1], we F36 Final release candidate 3 was declared NO-GO. The next Fedora Linux 36 Final Go/No-Go meeting[2] will be held at 1700 UTC on Thursday 5 May in #fedora-meeting. We will aim for the "target date #3" milestone of 10 May. The release schedule[3] has been updated accordingly. Minutes[4] and logs[5] of the Go/No-Go meeting are available on Meetbot. [1] https://qa.fedoraproject.org/blockerbugs/milestone/36/final/buglist [2] https://calendar.fedoraproject.org/meeting/10242/ [3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html [4] https://meetbot.fedoraproject.org/fedora-meeting/2022-04-28/f36-final-go_... [5] https://meetbot.fedoraproject.org/fedora-meeting/2022-04-28/f36-final-go_... -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 year, 5 months

1
0
0 / 0

[pungi-fedora] PR #1087: Setup for F36 Final 1.2

by Mohan Boddu

mohanboddu opened a new pull-request against the project: `pungi-fedora` that you are following: `` Setup for F36 Final 1.2 `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/1087

1 year, 5 months

1
1
0 / 0

[Fedocal] Reminder meeting : Fedora Release Engineering

by mohanboddu＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2022-04-26 from 11:00:00 to 12:00:00 US/Eastern At fedora-meeting-3(a)irc.libera.chat The meeting will be about: Fedora Release Engineering weekly meeting Source: https://calendar.fedoraproject.org//meeting/9274/

1 year, 5 months

1
0
0 / 0

Agenda Item Request

by Jaime Magiera

Hi folks, The Fedora CoreOS Working Group is in the process planning future hosting and naming for our container images. To do so, we think it would be helpful to get a sense of what registry Fedora’s containers will be hosted in looking to the future. Could we get on your agenda for Tuesday’s meeting to ask a few questions and maybe do some shared brainstorming? Many thanks, Jaime

1 year, 5 months

2
1
0 / 0

[pungi-fedora] PR #1086: Setup for F36 final 1.1

by Tomáš Hrčka

humaton opened a new pull-request against the project: `pungi-fedora` that you are following: `` Setup for F36 final 1.1 `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/1086

1 year, 5 months

2
5
0 / 0

Fedora Linux 36 Final is NO-GO

by Ben Cotton

Due to outstanding blocker bugs[1], we do not have an F36 Final release candidate. As a result, F36 Final is NO-GO for target date #1 and tomorrow's Go/No-Go meeting is cancelled. The next Fedora Linux 36 Final Go/No-Go meeting[2] will be held at 1700 UTC on Thursday 28 April in #fedora-meeting. We will aim for the "target date #2" milestone of 3 May. The release schedule[3] has been updated accordingly. [1] https://qa.fedoraproject.org/blockerbugs/milestone/36/final/buglist [2] https://calendar.fedoraproject.org/meeting/10242/ [3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 year, 5 months

1
0
0 / 0

[release] Pungi 4.3.4

by Ondrej Nosek

The Pungi development team is pleased to announce the availability of Pungi 4.3.4. Releases are for Fedora 34-36 and will be in a stable repository in a moment. Here are the changes of 4.3.4: * Do not clone the same repository multiple times, re-use already cloned repository (ounsal) Clone the directory to the compose tmp directory. Update the test_scm in order to create real Compose object. Mock objects are not allowed to create/delete files for preventing multiple clones. * Variants file in config can contain path (onosek) rcm-metadata configs contain a definition of variants file. It can be in form of SCM or file path. Before the fix, only variants file's basename was considered. Now the path can be written. Example: variants_file = "comps/variants-rcmtools-2.0-rhel-8.xml" * 'nomacboot' option for livemedia koji tasks (cobrien) * kojiwrapper: Add retries to login call (lsedlar) The gssapi_login call is not retried automatically by Koji yet (see koji#3170). Let's try to work around that by retrying in the calling code. * doc: improve osbs_registries explanation (kdreyer) Explain the use-case for this setting, and use the active voice to explain what actions Pungi performs relative to other tools. * osbs: only handle archives of type "image" (kdreyer) Prior to this change, if a container image used Cachito with OSBS, then OSBS would store additional "remote-sources" files in the Koji archives for the build. Pungi cannot parse the metadata for these archive entries, so it would crash in add_metadata. Tell Koji to only return container image archives, and ignore these remote-source archives. * Fix the wrong working directory for the progress_notification script. (ounsal) The notification script inherits working directory from the parent process and it can be called from the same directory ``pungi-koji`` is called from. The working directory is listed at the start of main log. * Filter out environment groups unmatch given arch (hlin) Remove undefined groups or groups not matching given arch from environments. * profiler: Respect provided output stream (lsedlar) * modules: Correct a typo in loading obsoletes (ppisar) obsoletes --> obsolete * Update the default greedy_method value in doc (ounsal) Refer to the documentation [1] for details on what configuration options are available. [1] https://docs.pagure.org/pungi/index.html If you encounter problems or need general help, stop by #fedora-releng IRC channel or file issues in Pagure. Happy composing!

1 year, 5 months

1
0
0 / 0

[pungi-fedora] PR #1085: Sync changes from CentOS Stream 9

by Stephen Gallagher

sgallagh opened a new pull-request against the project: `pungi-fedora` that you are following: `` Sync changes from CentOS Stream 9 `` To reply, visit the link below or just reply to this email https://pagure.io/pungi-fedora/pull-request/1085

1 year, 5 months

2
2
0 / 0

[Fedocal] Reminder meeting : Fedora Release Engineering

by mohanboddu＠fedoraproject.org

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2022-04-19 from 11:00:00 to 12:00:00 US/Eastern At fedora-meeting-3(a)irc.libera.chat The meeting will be about: Fedora Release Engineering weekly meeting Source: https://calendar.fedoraproject.org//meeting/9274/

1 year, 5 months

2
1
0 / 0

Fedora Linux 36 Final is NO-GO

by Ben Cotton

Due to outstanding blocker bugs[1], we do not have an F36 Final release candidate. As a result, F36 Final is NO-GO for the early release target and tomorrow's Go/No-Go meeting is cancelled. The next Fedora Linux 36 Final Go/No-Go meeting[2] will be held at 1700 UTC on Thursday 21 April in #fedora-meeting. We will aim for the "target date #1" milestone of 26 April. The release schedule[3] has been updated accordingly. [1] https://qa.fedoraproject.org/blockerbugs/milestone/36/final/buglist [2] https://calendar.fedoraproject.org/meeting/10242/ [3] https://fedorapeople.org/groups/schedule/f-36/f-36-key-tasks.html -- Ben Cotton He / Him / His Fedora Program Manager Red Hat TZ=America/Indiana/Indianapolis

1 year, 5 months

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng April 2022