May 2017 - rel-eng - Fedora Mailing-Lists

[releng] Issue #6713 `create daily run of f26 atomic host `

by Dusty Mabe

dustymabe reported a new issue against the project: `releng` that you are following: `` We'd like to put out "pre-release" images for Fedora 26 atomic host. I was told by dennis that we should not use the images that are created by the nightly f26 branched "gloabal" compose because those get cleaned up quickly. Thus, we'd like to run a daily run of fedora 26 atomic host, just like we do for f25 (where we are using `fedora-atomic.conf` from the pungi-fedora repo and the results stored at https://kojipkgs.fedoraproject.org/compose/twoweek/ like the 25 results are so that we can allow people to test using them. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6713

6 years, 9 months

3
8
0 / 0

[releng] Issue #6689 `f26-kde koji build target`

by Rex Dieter

rdieter reported a new issue against the project: `releng` that you are following: `` To ease the building of batch updates of kde-related packages (of up to 70 packages at a time), please create a f26-kde koji build target (similar to how f25-kde works). Thanks. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6689

6 years, 9 months

4
8
0 / 0

[releng] Issue #6820: Please review the Making sudo pip safe Fedora 27 Change Proposal

by Tomas Orsava

torsava reported a new issue against the project: `releng` that you are following: `` The change proposal can be found here: https://fedoraproject.org/wiki/Changes/Making_sudo_pip_safe Thank you! `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6820

6 years, 9 months

2
2
0 / 0

[releng] Issue #6815: Please, review the Host and Platform Fedora 27 Change Proposal and provide feedback

by Petr Šabata

psabata reported a new issue against the project: `releng` that you are following: `` The incomplete change proposal can be found here: * https://fedoraproject.org/wiki/Host_and_Platform This change involves two specific Release Engineering tasks, as discussed during the Release Engineering meeting last week: * a new tag representing the new self-hosting buildroot module (`module-bootstrap-master`) set needs to be created; this is tracked in [#6791](https://pagure.io/releng/issue/6791) * assistance with tagging secure-boot group packages into this tag will be required See the [Host and Platform wiki page](https://fedoraproject.org/wiki/Host_and_Platform) for more information about the concept, how it differs from Base Runtime and what is the Bootstrap module used for. Thanks in advance. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6815

6 years, 9 months

2
6
0 / 0

[releng] Issue #6775: Please Review Arbitrary Branching Change Proposal and Provide Feedback

by Matt Prahl

mprahl reported a new issue against the project: `releng` that you are following: `` Hello, As you may have heard during DevConf 2017, the Modularity and Factory 2.0 teams are proposing a different package branching strategy for Fedora 27. If you missed the talk and are interested, please watch https://youtu.be/5gqccjyjwFk?t=26m27s Since this proposed change would largely affect Release Engineering and the Fedora community as a whole, we'd greatly appreciate your time in reviewing this Change Proposal and providing any feedback: https://fedoraproject.org/wiki/Changes/ArbitraryBranching If you have any questions, please feel free to reach out to me (mprahl(a)redhat.com) or Ralph Bean (rbean(a)redhat.com). Thank you for your time and help. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6775

6 years, 9 months

2
3
0 / 0

[releng] Issue #6803: Fedora Media Writer 4.1.0 released

by Martin Bříza

mbriza reported a new issue against the project: `releng` that you are following: `` Tagged in git. MinGW packages have been built in Koji and I'll push them to updates-testing. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6803

6 years, 9 months

3
9
0 / 0

[releng] Issue #6781: ARM/aarch64 rebuild of packages affected by the ABI change

by Marek Polacek

mpolacek reported a new issue against the project: `releng` that you are following: `` As explained here: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... we'll have to rebuild some of the aarch64/arm packages. I've been performing a mass rebuild and the list of packages to rebuild so far looks like: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o... So we'd like to ask RCM to please rebuild these packages, thanks. Note that this needs rebuilding both in F26 and F27. Also, aarch64 needs to have kernel rebuilt (inline asm miscompilation in there). `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6781

6 years, 9 months

4
7
0 / 0

[releng] Issue #6786: Kojira cannot handle number of targets it used to handle month ago.

by Jan Kaluža

jkaluza reported a new issue against the project: `releng` that you are following: `` Hi, let me first say something about the current situation and steps we have taken to mitigate it: 1) MBS used to create 2 targets per module build (one classic build target and one -repo target to have the repository with the final tag available in order to allow Copr or taskotron or local builds to get the built RPMs without the need to download all of them from koji directly). This has been done since the very first date of MBS deployment and over the time, the number of targets have grown to 670. In the same time, kojira started having problems generating the repositories and after discussion on #fedora-releng, we have been advised to stop generating so many tags. 2) On Thursday May 4th, we have removed 504 old targets (https://pagure.io/releng/issue/6774) in a hope things will get to normal and we will have a time to fix the MBS to not require any target when building module. I want to note here that we left just 170 targets in Koji - this is number of targets it used to normally handle in the previous months. We did not get to 670 targets over the night and there were whole month in which kojira worked just fine with more than 170 targets. Even with 170 targets left, kojira had the same issues regenerating the repositories. 3) On Thursday May 11, we have decided to remove all modular targets (not only the old ones) (https://pagure.io/releng/issue/6784). That day, we started with no modular target and it used to work well for some time, but after we hit around 40 modular targets, kojira started to be slow again and tasks time-outed on waitrepo. Note that this decision has broken modular builds in Copr and signing of modules in robosignatory which is another complication in Fedora 26 Modular release. 4) On Friday May 12, we have deployed new MBS which creates only single target per module build and which deletes the targets right after the module build finishes, we are now on 22 modular targets and this number will go down to more or less 10 targets in any time (because there are still old builds in progress which created 2 targets instead of 1). After an hour after the removal of targets to get to 22 modular targets, we still see 7 tasks waiting on waitrepo. Now the question. Why Kojira cannot handle the load it used to handle one month ago? Why it cannot handle even the much lower load currently? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6786

6 years, 9 months

5
7
0 / 0

[releng] Issue #6696 `Repo out of f26-modularity tag`

by Adam Samalik

asamalik reported a new issue against the project: `releng` that you are following: `` The modularity team needs to be able to build modules using local module-build-service (MBS). After some discussion on #fedora-modularity with @jkaluza and @psabata it appears I need `f26-modularity` to appear at [kojipkgs.fedoraproject.org/repos](https://kojipkgs.fedoraproject.org/repos/) so MBS can use it as a buildroot for modules. I probably want you to run `koji add-target f26-modularity-repo f26-modularity f26-modularity`. (@jkaluza promised it's the right command) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6696

6 years, 9 months

4
13
0 / 0

[releng] Issue #6700 `Please create a f26-gnome side tag`

by Kalev Lember

kalev reported a new issue against the project: `releng` that you are following: `` Hi, Please create a new f26-gnome side tag and build target. We'll use it for building GNOME megaupdates before submitting them to Bodhi. Thanks, Kalev `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/6700

6 years, 10 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng May 2017