rel-eng January 2019

rel-eng@lists.fedoraproject.org

10 participants
236 discussions

[releng] Issue #8062: Grant admin rights for koji
by Tomáš Hrčka 21 Jan '19

21 Jan '19

humaton reported a new issue against the project: `releng` that you are following: `` * Describe the issue I need permissions to do my releng related work * When do you need this? (YYYY/MM/DD) ASAP my FAS account: humaton `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8062

2 2

[releng] Issue #8047: source metatdata is empty
by Lubomír Sedlář 21 Jan '19

21 Jan '19

lsedlar reported a new issue against the project: `releng` that you are following: `` As discussed in this thread: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org… Originally filed as pungi#1111. The source repo is indeed empty and primary xml claims there are 0 packages. However I don't see how this could be an issue with Pungi, given that the updates compose looks different to that and is very much not empty. https://kojipkgs.fedoraproject.org/compose/updates/Fedora-29-updates-201901… The 20190109.2 is also correct. I don't know what exactly happens to the compose once it finishes and how it gets to mirrors. I think it's either a problem in Bodhi or some sync script that's causing the data to go missing. CC @nbecker `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8047

4 4

[releng] Issue #8031: Need +1: policy change re. module default stream changes & Fedora Changes
by Adam Samalik 21 Jan '19

21 Jan '19

asamalik reported a new issue against the project: `releng` that you are following: `` * Describe the issue The Modularity WG is changing the policy regarding module default stream changes & Fedora Changes. It is a minor policy change that doesn't require any changes in code. I'd like to get a formal +1 from RelEng and FESCo on the change before publishing it. The summary would be: "Instead of rigidly requiring a Fedora Change for all module default stream changes, we are relaxing the policy to 'submitting a Fedora Change based on packager's best judgement'. We are also restricting changes to major Fedora releases. This makes it more consistent with how we handle major changes in traditional packages." For more details, please see the current policy [1] (please note it's described quite "efficiently"), the new policy approved by the Modularity WG [2], and optionally a set of scenarios covering module default stream changes [3]. [1] https://docs.fedoraproject.org/en-US/modularity/making-modules/managing-def… [2] https://tree.taiga.io/project/modularity-wg/us/77 [3] https://pagure.io/modularity/working-documents/blob/master/f/lifecycles-upg… * When do you need this? (YYYY/MM/DD) No date. * When is this no longer needed or useful? (YYYY/MM/DD) No date. * If we cannot complete your request, what is the impact? Packagers would continue to be required to submit a Fedora change for every module default stream change, even in cases one wouldn't be submitted in a similar change introduced by traditional packages — making the workflows between the two delivery methods (trad packages & modules) inconsistent. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8031

2 4

[releng] Issue #8044: Set default stream and profiles for avocado in rawhide
by Merlin Mathesius 21 Jan '19

21 Jan '19

merlinm reported a new issue against the project: `releng` that you are following: `` Please set the default stream (`stable`) and profiles (`default`) for the `avocado` module in rawhide. PR: https://pagure.io/releng/fedora-module-defaults/pull-request/41 Note: This change will also allow retirement of the non-modular avocado packages. * Describe the issue The "avocado" module currently has no default stream or profiles set. * When do you need this? (YYYY/MM/DD) 2019/01/30 * When is this no longer needed or useful? (YYYY/MM/DD) N/A * If we cannot complete your request, what is the impact? * "avocado" modular packages cannot be installed unless the user first manually enables a module stream. * Users wishing to install the "avocado" module manually need to explicitly specify the "default" profile. * Non-modular "avocado" packages cannot be retired as requested by [BZ#1660921](https://bugzilla.redhat.com/show_bug.cgi?id=1660921) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8044

2 3

eInvoice Notification - 17 January 2019
by Ben Cotton 17 Jan '19

17 Jan '19

Dear Customer, Attached is the last invoice. Thanks in anticipation. Ben Cotton bcotton(a)redhat.com If you or your employer do not consent to Internet e-mail for messages of this kind, please advise the sender.

1 0

[Fedocal] Reminder meeting : Fedora Release Engineering
by mohanboddu＠fedoraproject.org 16 Jan '19

16 Jan '19

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2019-01-17 from 17:00:00 to 18:00:00 UTC At fedora-meeting-2(a)irc.freenode.net The meeting will be about: Fedora Release Engineering weekly meeting Source: https://apps.fedoraproject.org/calendar/meeting/9274/

1 0

[releng] Issue #8048: Add fedora-packages to f29-infra tag in Koji
by Mikolaj Izdebski 13 Jan '19

13 Jan '19

mizdebsk reported a new issue against the project: `releng` that you are following: `` Please add package `fedora-packages` to `f29-infra`. Package owner can be set to @cverna. This package is required to deploy [Fedora Packages](https://apps.fedoraproject.org/packages) application in Fedora Infrastructure. koji add-pkg --owner cverna f29-infra fedora-packages `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8048

2 2

RelEng schedule tasks
by Ben Cotton 11 Jan '19

11 Jan '19

I am beginning to prepare the schedule for Fedora 31. One thing I want to do is to make sure it still accurately reflects the work of different teams within Fedora. Please look at the tasks on your team's schedule [1] and discuss them in your team. Let me know if there are tasks that should be added, removed, or modified. You can email me directly or file an issue in Pagure[2]. I ask that you please provide feedback by Friday, 18 January, although I will be able to incorporate changes after that. [1] https://fedorapeople.org/groups/schedule/f-30/f-30-releng-tasks.html [2] https://pagure.io/fedora-project-schedule/issues -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

1 0

[releng] Issue #8045: Requesting ownership of python-tenacity
by Christopher Brown 10 Jan '19

10 Jan '19

snecker reported a new issue against the project: `releng` that you are following: `` * Describe the issue python-tenacity has been orphaned and I requested commit access in https://pagure.io/fesco/issue/2045 * When do you need this? (YYYY/MM/DD) No rush. * When is this no longer needed or useful? (YYYY/MM/DD) n/a * If we cannot complete your request, what is the impact? Cannot maintain package. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8045

2 2

[release] pungi 4.1.32
by Lubomír Sedlář 10 Jan '19

10 Jan '19

Hello everyone, a new version of Pungi is available! The 4.1.32 build is ready to be used. There are updates waiting in Bodhi to go to updates-testing. Ideally you should use the 4.1.32-3.fcX build. This is a minor bug-fix release. The old pungi command has been updated to use createrepo_c for creating repos and productmd for generating metadata. There have been a few tweaks and improvements to documentation. It is now possible to configure rootfs size for lorax for traditionall installer, not just the one based on ostree. Refer to the documentation [0] for details on what configuration options are available. [0] 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! Lubomír

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2019