rel-eng January 2017

rel-eng@lists.fedoraproject.org

10 participants
43 discussions

Speed improvements in moving packages through bodhi
by Stewart Hardie 31 Jan '17

31 Jan '17

Hi there Apologies if this is not the right place to post. If not, forwarding to the appropriate people would be useful. As a Fedora end user, this is a suggestion about how package processing through bodhi could be improved. The time taken for a package to enter the testing or stable repos is sometimes days after it has been submitted to that repo. Presumably signing is part of that delay. It would be worthwhile to consider if this part of the bodhi process could be made faster, or capped in time by general policy. This would be primarily and more importantly done for security updates. Delays in packages entering repos after submission mean that feedback is missing on testing done by those who wait for the convenience and signing security of having the package being available in the testing repo. And it allows important updates to get into stable more rapidly, slicing off hours or days in the process. For security updates, this is only likely to be more important in the future. As an explanation.... When bodhi says: "This update has been submitted for testing by XXX." then the following bodhi message must appear within 1 hour: "This update has been pushed to testing." Naturally a package must then wait for appropriate feedback and karma......... But then, when bodhi says: "This update has been submitted for stable by bodhi." then the following bodhi message must appear within 1 hour: "This update has been pushed to stable." It may be that 1 hour is not currently feasible. If not, would 2, 6 or 12 hours be reasonable?? Ofcourse this only applies when the general process is running smoothly, not when servers and software are misbehaving. Regards Stewart

3 3

[releng] Issue #6577 `Fedora 26 mass rebuild`
by Pagure 31 Jan '17

31 Jan '17

sharkcz added a new comment to an issue you are following: `` we need feedback/help from the mainframe eng-ops guys it might be as simple as editing system.config file with different VLAN 00273 /* define vswitch */ 00274 define vswitch vsw1 rdev 0900 ETHERNET VLAN 1 00275 but I wouldn't dare to change it myself without being sure. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6577

1 0

[releng] Issue #6607 `unblock prelude-lml`
by Pagure 31 Jan '17

31 Jan '17

totol reported a new issue against the project: `releng` that you are following: `` review : https://bugzilla.redhat.com/show_bug.cgi?id=1417405 f25 and f26 are blocked `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6607

1 2

[releng] Issue #6577 `Fedora 26 mass rebuild`
by Pagure 31 Jan '17

31 Jan '17

ausil added a new comment to an issue you are following: `` as I have it the changes needed for the mass rebuild are as follows https://fedoraproject.org/wiki/Changes/GCC7 https://fedoraproject.org/wiki/Changes/ParallelInstallableDebuginfo https://fedoraproject.org/wiki/Changes/StaticLibraryDebuginfo https://fedoraproject.org/wiki/Changes/Fedora26CFlags https://fedoraproject.org/wiki/Changes/golang-buildmode-pie We need the boost side tag to be completed it is being tracked in #6605 a stretch goal is to get s390 merged into koji.fp.o before we build but we will not delay for it @kevin @sharkcz do we have any chance of the infra changes being done in time? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6577

1 0

[releng] Issue #6587 `PDC ownership in Fedora`
by Pagure 30 Jan '17

30 Jan '17

The issue: `PDC ownership in Fedora` of project: `releng` has been assigned to `mohanboddu` by ausil. https://pagure.io/releng/issue/6587

1 0

[Fedocal] Reminder meeting : Fedora Release Engineering
by Dennis Gilmore 30 Jan '17

30 Jan '17

Dear all, You are kindly invited to the meeting: Fedora Release Engineering on 2017-01-30 from 09:30:00 to 10:30:00 US/Central 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/4654/

2 1

[releng] Issue #6598 `Current Atomic Host commit is not signed`
by Pagure 30 Jan '17

30 Jan '17

walters added a new comment to an issue you are following: `` I'm seeing `2fb89decd2cb5c3bd73983f0a7b35c7437f23e3aaa91698fab952bb224e46af5` still not signed, and that appears to be the current tip. See also https://github.com/ostreedev/ostree/pull/663 ``` # cat /etc/ostree/remotes.d/fedora-atomic.conf [remote "fedora-atomic"] url=https://dl.fedoraproject.org/pub/fedora/linux/atomic/25/ gpg-verify=false gpgkeypath=/etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-25-primary ``` `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6598

1 0

[releng] Issue #6596 `fuse-encfs is blocked for tag dist-6E-epel-testing-candidate for koji build`
by Pagure 26 Jan '17

26 Jan '17

vascom added a new comment to an issue you are following: `` Thanks. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6596

1 0

[releng] Issue #6598 `Current Atomic Host commit is not signed`
by Pagure 26 Jan '17

26 Jan '17

puiterwijk added a new comment to an issue you are following: `` This was due to a configuration error. The current tree is signed again, and F25 will be signed from now on. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6598

1 0

[releng] Issue #6596 `fuse-encfs is blocked for tag dist-6E-epel-testing-candidate for koji build`
by Pagure 26 Jan '17

26 Jan '17

The status of the issue: `fuse-encfs is blocked for tag dist-6E-epel-testing-candidate for koji build` of project: `releng` has been updated to: Closed as Fixed by mohanboddu. https://pagure.io/releng/issue/6596

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng January 2017