July 2019 - rel-eng - Fedora Mailing-Lists

[releng] Issue #7490: container/waiverdb has no f28 branch?

by Ralph Bean

ralph reported a new issue against the project: `releng` that you are following: `` It has master and f27, but no f28. Did it get missed in mass-branching? As packagers, we're disallowed by dist-git to push the branch ourselves. /cc @gnaponie `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7490

4 years, 9 months

4
7
0 / 0

[releng] Issue #8166: Retire module stream "hub:prerelease"

by Stephen Gallagher

sgallagh reported a new issue against the project: `releng` that you are following: `` * Name of the module? hub * Stream name(s) and the new EOL date? prerelease New EOL date is EOL of Fedora 29. * Any extra information? This stream is not useful as it was originally addressing the lack of upstream releases for two years. However, upstream is now doing monthly releases and so it should go away. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8166

4 years, 9 months

3
6
0 / 0

[releng] Issue #8183: Changes/GatingRawhideSinglePackageUpdates

by Pierre-YvesChibon

pingou reported a new issue against the project: `releng` that you are following: `` * Describe the issue We would like to implement a system allowing to gate on test results rawhide packages before they land into the buildroot and affect other packages. This is aimed to be deployed in two phase, the first phase will concern the single package updates and the second phase will concern the multi-package updates. This ticket is to inform you about this change proposal, available in full at: https://fedoraproject.org/wiki/Changes/GatingRawhideSinglePackageUpdates Please let us know what you think of it :) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8183

4 years, 9 months

3
2
0 / 0

[releng] Issue #8148: Copying vmdk to output directory

by Dusty Mabe

dustymabe reported a new issue against the project: `releng` that you are following: `` * Describe the issue recently added vmdk to output cloud images but I don't see it getting copied to the output directories. For example for the [Fedora-Rawhide-20190217.n.0](https://kojipkgs.fedoraproject.org/compose/r... compose I see that the vmdk was built ([koji task](https://koji.fedoraproject.org/koji/taskinfo?taskID=32866399)) but I don't see it in the [output directory](https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawh.... * When do you need this? (YYYY/MM/DD) 2019/02/25 - next week * When is this no longer needed or useful? (YYYY/MM/DD) N/A * If we cannot complete your request, what is the impact? Lot's of extra bandwidth used when uploading to AWS. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8148

4 years, 9 months

4
8
0 / 0

[releng] Issue #8158: flatpak builds are failing with an aarch64 cluster error

by Kalev Lember

kalev reported a new issue against the project: `releng` that you are following: `` I'm getting the following when trying to build a flatpak for thunderbird: ``` $ fedpkg flatpak-build Created task: 32963187 Task info: https://koji.fedoraproject.org/koji/taskinfo?taskID=32963187 Watching tasks (this may be safely interrupted)... 32963187 buildContainer (noarch): free 32963187 buildContainer (noarch): free -> open (buildvm-12.phx2.fedoraproject.org) 32963187 buildContainer (noarch): open (buildvm-12.phx2.fedoraproject.org) -> FAILED: Fault: <Fault 2001: 'Image build failed. Error in plugin orchestrate_build: \'{"aarch64": {"general": "\\\\"AllClustersFailedException(\\\'Could not find appropriate cluster for worker build.\\\')\\\\""}}\'. OSBS build id: thunderbird-master-79998-3'> 0 free 0 open 0 done 1 failed 32963187 buildContainer (noarch) failed ``` I assume this is fallout from https://pagure.io/releng/issue/8133 that added the aarch64 architecture to container build tags in koji. @cverna @otaylor Any ideas? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8158

4 years, 9 months

4
5
0 / 0

[releng] Issue #8157: Publish new openh264 builds

by Kalev Lember

kalev reported a new issue against the project: `releng` that you are following: `` Hi, I just finished a new round of openh264 builds. Please sign and send the following to Cisco: openh264-1.8.0-3.fc29 openh264-1.8.0-3.fc30 openh264-1.8.0-3.fc31 Thanks, Kalev `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8157

4 years, 9 months

2
3
0 / 0

[releng] Issue #8145: Need some info about livemedia permission

by Ziqian SUN (Zamir)

zsun reported a new issue against the project: `releng` that you are following: `` * Describe the issue This is a general question. Given I am the LXQt spin maintainer, when I want to test my changes to kickstart files of generating livemedia, I need a way to try like the production. I saw there is a page about [Building Images in Koji](https://docs.pagure.org/koji/image_build/). So I tried like that ``` koji spin-livemedia fedora-lxqt 30 f30 x86_64 ./flat-live-lxqt.ks --scratch ``` But I got ``` 2019-02-20 11:20:15,915 [ERROR] koji: ActionNotAllowed: livemedia permission required ``` So my questions are * Is the livemedia permission granted only to Release Engineering people, or also spin maintainers * If this also grants to spin maintainers, can you grant me this permission? * If this only grants to Release Engineering, can you provide some guide for building a livemedia like it does in Koji? I saw [this wiki](https://fedoraproject.org/wiki/Livemedia-creator-_How_to_create_and... already but I always need to set `selinux --permissive` to make a working Fedora Rawhide(f30) livemedia. Thanks! * When do you need this? (YYYY/MM/DD) No ETA but as soon as possible * When is this no longer needed or useful? (YYYY/MM/DD) As long as I am still contributing to Fedora, this is still useful ;-) * If we cannot complete your request, what is the impact? Minimal. It just makes my work a little complex `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8145

4 years, 9 months

4
5
0 / 0

[releng] Issue #8092: Change impact: Python 3.8

by Miro Hrončok

churchyard reported a new issue against the project: `releng` that you are following: `` https://fedoraproject.org/wiki/Changes/Python3.8 * we'll need a side tag `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8092

4 years, 9 months

3
3
0 / 0

[releng] Issue #8540: Create f31-updates-stable-pending in staging koji

by Pierre-YvesChibon

pingou reported a new issue against the project: `releng` that you are following: `` * Describe the issue In order to test the Rawhide package gating workflow in staging, we need to have a ``f31-updates-stable-pending`` koji tag created since we push builds to this tag once their gate is lifted. * When do you need this? (YYYY/MM/DD) ASAP * When is this no longer needed or useful? (YYYY/MM/DD) When f31 is EOL in staging * If we cannot complete your request, what is the impact? We can't test gating properly in staging `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8540

4 years, 9 months

1
2
0 / 0

[releng] Issue #8536: Several builds sitting in f31-pending

by Petr Kubat

pkubat reported a new issue against the project: `releng` that you are following: `` * Describe the issue Seems like some builds (incl. libpq needed by me) are stuck in f31-pending: $ koji --quiet list-tagged --latest f31-pending cinnamon-session-4.2.1-1.fc31 f31-pending leigh123linux clamav-0.101.2-2.fc31 f31-pending sergiomb cross-gcc-9.1.1-2.fc31 f31-pending spot dbus-broker-21-5.fc31 f31-pending ngompa eureka-1.24-1.fc31 f31-pending limb highlight-3.52-2.fc31 f31-pending filiperosset ktimer-19.04.3-1.fc31 f31-pending rdieter ktoblzcheck-1.49-1.fc31 f31-pending notting libffi-3.1-22.fc31 f31-pending fweimer libpq-11.4-1.fc31 f31-pending pkubat php-netresearch-jsonmapper-1.5.0-1.fc31 f31-pending remi pidgin-2.13.0-14.fc31 f31-pending jskarvad * If we cannot complete your request, what is the impact? libpq-11.4-1.fc31 has been stuck for a week and is needed to rebuild postgresql in Rawhide + version 11 module. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8536

4 years, 9 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2019