February 2018 - rel-eng - Fedora Mailing-Lists

[releng] Issue #7057: Tracking ticket for generating torrents for modular release

by Mohan Boddu

mohanboddu reported a new issue against the project: `releng` that you are following: `` For a traditional release we generate torrents for almost all the iso's in the compose. So, its safe to assume that a modular release also requires torrents generated for the iso's. There is not much work/code changes are needed here, but just an informational ticket for releng. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7057

5 years, 5 months

2
2
0 / 0

[releng] Issue #7017: Set up koji policy/channels for known archful noarch packages.

by Ralph Bean

ralph reported a new issue against the project: `releng` that you are following: `` Reported by @sgallagh in a discussion with @ralph and @mikeb. There are these funny things called 'archful noarch' packages. Packages which produce noarch binary rpms, but which can only be built on specific architectures (x86_64, specifically). In the traditional world, when you submit a build of one of these package to koji, your build is sent to a builder with a random architecture. Usually this is wrong, and your build fails. You then submit and submit again until it works. This is colloquially called "winning the builder lottery." It is annoying, but people put up with it. In the modular world, this poses a real problem. The MBS won't know *why* the build failed and we can't expect it to try over and over again until it wins the builder lottery. We need a better solution. The solution we came up with on a whiteboard (a few months ago) was that we can set up a *channel* in koji called `x86_64-builders` (or something like that). Then, start maintaining a list of all known "archful noarch" packages. This could start with one or two packages and then we grow it over time. We would then create a new koji hub policy that says something like: "Whenever a build is submitted of a package that matches any of the packages in the curated list, submit the build to the x86_64-builders channel." What do you think? Will it work? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7017

5 years, 5 months

5
9
0 / 0

[releng] Issue #7012: Tag hierarchy for modular updates.

by Ralph Bean

ralph reported a new issue against the project: `releng` that you are following: `` OK, the patch to bodhi that enables mashing modules is basically done. @mcurlej is wrapping up the test suite. Our target is to merge, release, and deploy it around Sept 20th, just after Beta freeze thaws. In order to use it, we're going to need to create some new tags for the tag hierarchy. The tag hierarchy for f27 currently looks like: ~❯ koji list-tag-inheritance --reverse f27 f27 (417) ├─f27-binutils-rebuild (1868) ├─f27-rebuild (1849) ├─f27-gcc-abi-rebuild (1274) ├─f27-atomic (433) ├─f27-openh264 (432) ├─f27-modularity (431) ├─f27-compose (419) └─f27-updates (418) ├─f27-pending (427) ├─f27-override (424) │ └─f27-build (425) │ ├─f27-gnome (2116) │ ├─f27-ocaml2 (1838) │ ├─f27-boost (1805) │ ├─f27-perl (1489) │ ├─f27-ocaml (1082) │ ├─f27-llvm4 (493) │ └─f27-infra (428) │ └─f27-infra-stg (429) │ └─f27-infra-candidate (430) ├─f27-updates-pending (423) ├─f27-updates-testing (421) │ └─f27-updates-testing-pending (422) │ └─f27-signing-pending (426) └─f27-updates-candidate (420) For f27 updates, we're going to need a tag structure something like this: ~❯ koji list-tag-inheritance --reverse f27-modular f27-modular └─f27-modular-updates ├─f27-modular-pending ├─f27-modular-updates-pending ├─f27-modular-updates-testing │ └─f27-modular-updates-testing-pending │ └─f27-modular-signing-pending └─f27-modular-updates-candidate Once that's done (and once the updated bodhi is deployed) we'll need to create a 'F27 Modular' "release" in bodhi's database that points to these tags. Lastly, the MBS will need to start tagging its built modules into `f27-modular-updates-candidate`. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7012

5 years, 6 months

3
9
0 / 0

[releng] Issue #7324: Review: Request for publishing Fedora Scientific Vagrant boxes

by Amit Saha

amitksaha reported a new issue against the project: `releng` that you are following: `` Hello, as proposed at https://fedoraproject.org/wiki/Changes/FedoraScientific_VagrantBox , I would like to request for a review of my request to publish Fedora Scientific vagrant boxes starting with Fedora 29. Thank you. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7324

5 years, 6 months

4
7
0 / 0

[releng] Issue #7346: Can't push to stable, dist.rpmdeplint false positive

by Remi Collet

remi reported a new issue against the project: `releng` that you are following: `` See https://bodhi.fedoraproject.org/updates/FEDORA-2018-7be3b16990 results: - arch: x86_64 item: php-pecl-couchbase2-2.4.4-1.fc27 outcome: FAILED scenario: x86_64 type: koji_build nothing provides php(api) = 20160303-32 needed by php-pecl-couchbase2-2.4.4-1.fc27.i686 But PHP is NOT a multilib package, no reason why this happen. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7346

5 years, 7 months

5
5
0 / 0

[releng] Issue #7251: Rebase binutils to 2.29.1 point release

by Nicholas Clifton

nickc reported a new issue against the project: `releng` that you are following: `` Rebase the binutils package from the 2.29 release to the 2.29.1 release of the FSF binutils project. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7251

5 years, 7 months

4
3
0 / 0

[releng] Issue #7178: Give ignatenkobrain rights to process fedora-scm-requests

by Igor Gnatenko

ignatenkobrain reported a new issue against the project: `releng` that you are following: `` It's [uncommon](https://lists.fedoraproject.org/archives/list/devel@lists.fedor... that people have to wait 2-3 days to get their SCM repo if they submit request on saturday morning (some of US times). It definitely applies for US holidays because @limb is located there. I would like to help myself in processing those tickets during weekends/holidays and whatever time you will tell me I should do. @kevin suggested to open releng ticket to track this, so here we go. As Patrick mentioned, there is no granular access so probably I would need to get more permissions just for this but I will use them only for this. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7178

5 years, 9 months

4
8
0 / 0

[releng] PR #7345: Update the mass-rebuild SOP

by Kellin

kellin opened a new pull-request against the project: `releng` that you are following: `` Update the mass-rebuild SOP `` To reply, visit the link below or just reply to this email https://pagure.io/releng/pull-request/7345

5 years, 9 months

2
9
0 / 0

[releng] Issue #7282: Rebase binutils to the new 2.30 release

by Nicholas Clifton

nickc reported a new issue against the project: `releng` that you are following: `` Update the rawhide binutils to the just release FSF binutils 2.30 sources. This new release brings in many big fixes and several new features including: * Support for location views in DWARF debug line information. * Support for parsing and following any type of separate debug information link. Plus other, more technical, enhancements. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7282

5 years, 9 months

7
14
0 / 0

[releng] Issue #7317: Changes/Remove GCC from BuildRoot

by Igor Gnatenko

ignatenkobrain reported a new issue against the project: `releng` that you are following: `` https://fedoraproject.org/wiki/Changes/Remove_GCC_from_BuildRoot It definitely has impact on releng and is asking you do to some work ;) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7317

5 years, 9 months

2
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng February 2018