rel-eng July 2019

rel-eng@lists.fedoraproject.org

9 participants
162 discussions

[releng] Issue #8469: Koji: Block or remove python-epel-rpm-macros and python3-rpm from f31
by Miro Hrončok 06 Aug '19

06 Aug '19

churchyard reported a new issue against the project: `releng` that you are following: `` * Describe the issue python-epel-rpm-macros and python3-rpm are epel only packages, please block them for f31 in Koji. * When do you need this? any time * When is this no longer needed or useful? N/A * If we cannot complete your request, what is the impact? unknown, possibly dangerous Actual result: ``` $ koji list-pkgs --show-blocked --tag f31 --package python3-rpm Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python3-rpm f31 releng $ koji list-pkgs --show-blocked --tag f31 --package python-epel-rpm-macros Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python-epel-rpm-macros f31 releng ``` Expected result: ``` $ koji list-pkgs --show-blocked --tag f31 --package python3-rpm (no matching packages) $ koji list-pkgs --show-blocked --tag f31 --package python-epel-rpm-macros (no matching packages) ``` Or: ``` $ koji list-pkgs --show-blocked --tag f31 --package python3-rpm Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python3-rpm f31 releng [BLOCKED] $ koji list-pkgs --show-blocked --tag f31 --package python-epel-rpm-macros Package Tag Extra Arches Owner ----------------------- ----------------------- ---------------- --------------- python-epel-rpm-macros f31 releng [BLOCKED] ``` `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8469

3 6

[releng] Issue #8275: Fedora 31 FTBFS and all Fails to install tracker bugzillas
by Miro Hrončok 01 Aug '19

01 Aug '19

churchyard reported a new issue against the project: `releng` that you are following: `` According to the [new policy about FTBFS and FTI (Fails to install) packages](https://pagure.io/fesco/issue/2109), please create the following new tracker bugzillas: * Fedora 31 Fails to build from source - F31FTBFS * Fedora 31 Fails to install - F31FailsToInstall * Fedora 30 Fails to install - F30FailsToInstall * Fedora 29 Fails to install - F29FailsToInstall * Fedora 28 Fails to install - F28FailsToInstall About the aliases: I suggested F31FTI, but @till [had a good point](https://pagure.io/fesco/issue/2109#comment-561765) that F30_fails_to_install (or similar) might be easier for others. I ultimately leave that decision to releng, but I guess we usually stick to CamelCase, so I went with F30FailsToInstall `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8275

2 6

[releng] Issue #8407: tracking issue: ppc64le network failures during f29AH composes
by Dusty Mabe 01 Aug '19

01 Aug '19

dustymabe reported a new issue against the project: `releng` that you are following: `` We are seeing network issues when pulling the ostree content during the image builds for f29AH (run during bodhi updates composes). This seems to be getting more consistent lately. I'm opening this bug to track the issue. Here are current cases where it has happened: - [Fedora-29-updates-testing-20190602.0](https://pagure.io/dusty/failed-composes/issue/1948) - [Fedora-29-updates-20190531.0](https://pagure.io/dusty/failed-composes/issue/1937#comment-573321) - [ Fedora-29-updates-20190601.0](https://pagure.io/dusty/failed-composes/issue/1941) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8407

6 22

Fedora Release Engineering Meeting Summary for 2019-07-31
by Mohan Boddu 01 Aug '19

01 Aug '19

====================================== #fedora-meeting-2: RELENG (2019-08-01) ====================================== Meeting started by mboddu at 15:59:02 UTC. The full logs are available athttps://meetbot.fedoraproject.org/fedora-meeting-2/2019-07-31/releng.2019… . Meeting summary --------------- * init process (mboddu, 15:59:02) * EPEL-8 (mboddu, 16:00:18) * We did a test compose of epel8-playground and it was successful in the first try (mboddu, 16:00:52) * ACTION: mboddu will update the comps file with only epel8 comps groups (mboddu, 16:21:36) * EPEL8 Bodhi Enablement (mboddu, 16:22:22) * ACTION: mboddu will try to enable bodhi for epel8 release today (mboddu, 16:24:46) * Mass Rebuild Status (mboddu, 16:37:43) * mass rebuild for rpms are done and all the builds are merged into main tag (mboddu, 16:42:50) * mboddu started filing ftbfs today (mboddu, 16:43:00) * Open Floor (mboddu, 16:46:55) * There wont be a meeting next week as most of the people might be traveling and I will be on PTO (mboddu, 16:47:42) * nirik will be moving/cleaning some storage stuff around, mboddu will be helping him in anyway possible (mboddu, 16:54:11) Meeting ended at 16:59:53 UTC. Action Items ------------ * mboddu will update the comps file with only epel8 comps groups * mboddu will try to enable bodhi for epel8 release today Action Items, by person ----------------------- * mboddu * mboddu will update the comps file with only epel8 comps groups * mboddu will try to enable bodhi for epel8 release today * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * mboddu (81) * nirik (62) * smooge (11) * zodbot (10) * ksinny (9) * jednorozec (0) * pbrobinson (0) * pingou (0) * sharkcz (0) Generated by `MeetBot`_ 0.1.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

[releng] Issue #8572: Unretire python2-numpy
by Gwyn Ciesla 01 Aug '19

01 Aug '19

limb reported a new issue against the project: `releng` that you are following: `` * Describe the issue Currently used only for EPEL, we need this for f31+ now. https://bugzilla.redhat.com/show_bug.cgi?id=1734445 * When do you need this? (YYYY/MM/DD) Soon-ish would be great. :) * When is this no longer needed or useful? (YYYY/MM/DD) * If we cannot complete your request, what is the impact? Unable to split python2-numpy and python3-numpy, preventing python3-numpy from upgrading to the current release. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8572

2 3

[releng] Issue #8565: Package lua-cyrussasl doesn't reach epel8-build repository
by Robert Scheck 01 Aug '19

01 Aug '19

robert reported a new issue against the project: `releng` that you are following: `` * Describe the issue When looking to https://kojipkgs.fedoraproject.org/repos/epel8-build/latest/x86_64/pkglist my package `lua-cyrussasl` is missing, even the build succeeded: https://koji.fedoraproject.org/koji/buildinfo?buildID=1323188 * When do you need this? (YYYY/MM/DD) ASAP :) * When is this no longer needed or useful? (YYYY/MM/DD) n/a * If we cannot complete your request, what is the impact? n/a `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8565

2 2

[releng] PR #8573: F31 ftbfs changes and changing shebangs to py3
by Mohan Boddu 01 Aug '19

01 Aug '19

mohanboddu opened a new pull-request against the project: `releng` that you are following: `` F31 ftbfs changes and changing shebangs to py3 `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/8573

1 1

[releng] Issue #8571: Orphan all packages of ricardo
by Miro Hrončok 31 Jul '19

31 Jul '19

churchyard reported a new issue against the project: `releng` that you are following: `` https://pagure.io/fesco/issue/2194 https://src.fedoraproject.org//api/0/projects?owner=ricardo&per_page=100&sh… `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8571

1 2

[releng] Issue #8570: Adopt package javaewah
by Mat Booth 31 Jul '19

31 Jul '19

mbooth reported a new issue against the project: `releng` that you are following: `` Please assign this package to me (mbooth). I am maintainer of jgit, so I am probably best-placed to maintain this dep. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8570

2 2

[releng] Issue #8563: unretire 389-console in epel7 branch
by Mark Reynolds 31 Jul '19

31 Jul '19

mreynolds reported a new issue against the project: `releng` that you are following: `` * Describe the issue Accidentally retired 389-console from epel7 branch. I was trying to retire it from master, but didn't realize I was on the wrong branch `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8563

2 4

← Newer
1
2
3
4
5
6
7
8
...
17
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2019