rel-eng January 2019

rel-eng@lists.fedoraproject.org

10 participants
236 discussions

[releng] Issue #6746: Produce a slimmed-down compose whenever certain packages appear in an update
by Adam Williamson 26 Jan '19

26 Jan '19

adamwill added a new comment to an issue you are following: `` @mohanboddu said we can reopen this ticket now (the taiga is not the thing any more apparently), so I'm re-opening it... Current state: I have *less* of an urgent need for this now because I sorta gave up waiting and [did it myself](https://www.happyassassin.net/2019/01/23/new-openqa-tests-update-in…. openQA has a test now which creates an installer image containing the package from the update and then tests it - which is the thing I was trying to get done. This would still probably be nice to have for others to use and perhaps to get more images for testing, though. @mohanboddu says the thing that's missing now is a list of the packages which should act as 'triggers' for this process; we don't really have such a thing, so we'd have to either write one or somehow try and synthesize one out of comps and kickstart and fedora-pungi data or something. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6746

1 0

[releng] Issue #6746: Produce a slimmed-down compose whenever certain packages appear in an update
by Adam Williamson 26 Jan '19

26 Jan '19

The status of the issue: `Produce a slimmed-down compose whenever certain packages appear in an update` of project: `releng` has been updated to: Open by adamwill. https://pagure.io/releng/issue/6746

1 0

Ben Cotton Invoice # EP329947-932
by Ben Cotton 25 Jan '19

25 Jan '19

Sorry for the delay…. Please submit the new documents as soon as possible. Missing Documents: Invoice EP329947-932 (previous version is attached) Thank you for your business! Ben Cotton bcotton(a)redhat.com -

1 0

[releng] Issue #8065: please unlock and push this update to testing
by Mukundan Ragavan 24 Jan '19

24 Jan '19

nonamedotc reported a new issue against the project: `releng` that you are following: `` * Describe the issue I submitted an update of htop for Fedora 28. I ended up unpushing the update by mistake. Here is the update - https://bodhi.fedoraproject.org/updates/FEDORA-2019-a122c96bcf Please push this update to testing again. I am unable to edit the update since it is locked. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8065

2 3

[releng] Issue #8072: Please retire (and orphan) openmolar
by Ankur Sinha 24 Jan '19

24 Jan '19

ankursinha reported a new issue against the project: `releng` that you are following: `` * Describe the issue The openmolar src repository does not contain any files, and there are no builds for the package either. Could this package be retired please? I only have commit access so I cannot orphan the package, and the two maintainers seem to be inactive. * When do you need this? (YYYY/MM/DD) NA * When is this no longer needed or useful? (YYYY/MM/DD) NA * If we cannot complete your request, what is the impact? The empty package stays in SCM. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8072

1 1

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

23 Jan '19

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2019-01-24 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 #8068: Fedora 27 is still active in PDC
by Elliott Sales de Andrade 23 Jan '19

23 Jan '19

qulogic reported a new issue against the project: `releng` that you are following: `` * Describe the issue In PDC, Fedora 27 is still marked active: https://pdc.fedoraproject.org/release/?search=27 This causes `fedpkg request-branch --all-releases` to open requests for Fedora 27 which get closed as invalid, e.g., https://pagure.io/releng/fedora-scm-requests/issue/9492 * When do you need this? (YYYY/MM/DD) Two-ish months ago? * When is this no longer needed or useful? (YYYY/MM/DD) N/A * If we cannot complete your request, what is the impact? Extra branch request tickets for people using `fedpkg request-branch --all-releases` `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8068

2 2

Fedora Atomic Host Two Week Release Announcement: 29.20190121.0
by noreply＠fedoraproject.org 22 Jan '19

22 Jan '19

2 1

[releng] Issue #8067: 20190121: Release Fedora 29 Atomic Host
by Michael Nguyen 22 Jan '19

22 Jan '19

mnguyen reported a new issue against the project: `releng` that you are following: `` You should be able to do it with this command: `python push-two-week-atomic.py -k fedora-29 -r 29 --pungi-compose-id Fedora-29-updates-Fedora-29-updates-20190121.0` Note: We won't need to use options --compose-basedir and --first-release from this release onward. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8067

3 4

[releng] Issue #8066: Delete branch symlink-script in rpms/jmc
by Salman Siddiqui 22 Jan '19

22 Jan '19

sasiddiq reported a new issue against the project: `releng` that you are following: `` * Describe the issue I accidentally created a bugfix branch in dist-git * When do you need this? (YYYY/MM/DD) 2019/01/30 * When is this no longer needed or useful? (YYYY/MM/DD) 2019/01/21 * If we cannot complete your request, what is the impact? No real impact. This is just a cosmetic fix. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8066

2 2

← Newer
1
...
17
18
19
20
21
22
23
24
Older →

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