rel-eng July 2019

rel-eng@lists.fedoraproject.org

9 participants
162 discussions

[releng] Issue #8529: F31 system wide change: stop composing and distributing i686 trees
by Kevin Fenzi 22 Aug '19

22 Aug '19

kevin reported a new issue against the project: `releng` that you are following: `` Please consider the release engineering impact of this change proposal targeting Fedora 31: https://fedoraproject.org/wiki/Changes/Noi686Repositories `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8529

5 7

[releng] Issue #8506: Fedora 32 side tag for Python 3.8
by Miro Hrončok 21 Aug '19

21 Aug '19

churchyard reported a new issue against the project: `releng` that you are following: `` * Describe the issue I'd kindly like to request a **Fedora 32** side tag in koji for Python 3.8 rebuilds. See https://pagure.io/releng/issue/8092 Preferred tag/target name: f32-python Parent: f32-build ``` $ koji add-tag f32-python --parent=f32-build --arches='armv7hl i686 x86_64 aarch64 ppc64 ppc64le s390x' $ koji add-target f32-python f32-python ``` * When do you need this? (2019/08/14) - right after branching * When is this no longer needed or useful? (2020/01/29) * If we cannot complete your request, what is the impact? We would not be able to rebuild Python 3.8 for Fedora 32. Thanks. Se also https://pagure.io/releng/issue/8320 `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8506

4 14

[releng] Issue #8439: Publish openh264 2.0.0 builds
by Kalev Lember 20 Aug '19

20 Aug '19

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-2.0.0-1.fc30 openh264-2.0.0-1.fc31 Thanks, Kalev `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8439

1 2

[releng] Issue #8555: Fedora 31 Mass Rebuild
by Mohan Boddu 19 Aug '19

19 Aug '19

mohanboddu reported a new issue against the project: `releng` that you are following: `` The fedora 31 schedule[1] has a mass rebuild scheduled for Jul 24 2019, We need to plan and coordinate all tasks in preparation for it. [1] https://fedoraproject.org/wiki/Releases/31/Schedule `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8555

7 20

[releng] Issue #8543: Adopt package "python2-django-1.11"
by Nicolas Chauvet 19 Aug '19

19 Aug '19

kwizart reported a new issue against the project: `releng` that you are following: `` Package name: python2-django-1.11 FAS username: kwizart Thx `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8543

2 4

[releng] Issue #8294: coreos-pool and coreos-release koji tags request for FCOS
by Sinny Kumari 14 Aug '19

14 Aug '19

sinnykumari reported a new issue against the project: `releng` that you are following: `` ** Describe the issue** Fedora CoreOS will have [various streams](https://github.com/coreos/fedora-coreos-tracker/blob/master/stream…. All streams will use packages which are built in Fedora koji. Mechanical streams will use packages available in Fedora repos from tags f$(release), f$(release)-updates, f$(release)-updates-testing. Development and production streams will get built from packages available under koji tag `coreos-pool`. Packages which make it to production will also get tagged to `coreos-release` tag. These tags will ensure that (1) packages are not automatically garbage collected (2) stream builds are reproducible (up to the GC retention policy we agree upon), and (3) packages are added to the pool (and thus into the production streams) in a controlled manner. To build FCOS for different streams we need: - coreos-pool and coreos-release koji tags created (include arches aarch64, ppc64le, x86_64) - Permission to add packages to requested tags (ACLs for bgilbert, dustymabe, jlebon and sinnykumari, until we have bot setup done) - Tag builds needs to be signed - Generate dist repo for requested tags with option `--non-latest` to koji dist-repo (to perform build with desired NVRA) **Question** As we have streams like next-devel and testing-devel, packages will be from multiple Fedora releases in coreos-pool and coreos-release tags. Since we will be using signed packages, does koji dist-repo allows to specify multiple keys for generating dist repos? This question is because, in [infra ansible tag2distrepo](https://infrastructure.fedoraproject.org/cgit/ansible.git/tre…, so far single key has been used. ** When do you need this? (YYYY/MM/DD) ** ASAP ** When is this no longer needed or useful? (YYYY/MM/DD) ** Always needed ** If we cannot complete your request, what is the impact? ** we won't be able to build FCOS for different streams `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8294

6 50

[releng] Issue #8549: ghc-8.6 Change for F31 will require a sidetag
by Jens Petersen 14 Aug '19

14 Aug '19

petersen reported a new issue against the project: `releng` that you are following: `` * Describe the issue The Haskell SIG is planning to update ghc and associated packages for F31. For this we will need f31-ghc sidetag in Koji to do the builds without disrupting Rawhide. https://fedoraproject.org/wiki/Changes/GHC_8.6 * When do you need this? 2019/07/26 * When is this no longer needed or useful? 2019/08/13 * If we cannot complete your request, what is the impact? We won't be able to complete the F31 Change `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8549

3 15

[releng] Issue #8435: Side tag for Golang new macros
by Robert-André Mauchin 12 Aug '19

12 Aug '19

eclipseo reported a new issue against the project: `releng` that you are following: `` I'd kindly like to request a Fedora 31 side tag in koji for Golang rebuilds. See https://fedoraproject.org/wiki/Changes/Adopt_new_Go_Packaging_Guidelines * For which release? F31 * Name of the side tag? (Generally fxx-pkg) Preferred tag/target name: f31-go or f31-golang Parent: f31-build $ koji add-tag f31-go --parent=f31-go --arches='armv7hl i686 x86_64 aarch64 ppc64 ppc64le s390x' $ koji add-target f31-go f31-go * Number of builds that are expected in the side tag? Around 1120. Exhaustive list: https://copr.fedorainfracloud.org/coprs/eclipseo/golang-ng/ * When do you need this? This week would be good. * How long do you need the side tag? Until 2019-07-24 * If we cannot complete your request, what is the impact? We would not be able to rebuild the Golang stack with the new macros. * Any extra information? I never used a side tag before so I'd also like some pointer or howto to properly make use of it. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8435

3 8

[releng] Issue #8500: Side tag needed for Boost 1.70 rebuilds in rawhide
by Jonathan Wakely 12 Aug '19

12 Aug '19

jwakely reported a new issue against the project: `releng` that you are following: `` * Describe the issue I need a sidetag, f31-boost, to do rebuilds of packages affected by https://fedoraproject.org/wiki/Changes/F31Boost170 * When do you need this? 2019/07/08 * When is this no longer needed or useful? 2019/08/24 * If we cannot complete your request, what is the impact? No boost update in F31 `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8500

3 8

[releng] Issue #8522: F30: Retire FTBFS packages on 2019-08-06
by Miro Hrončok 08 Aug '19

08 Aug '19

churchyard reported a new issue against the project: `releng` that you are following: `` ## Describe the issue According to [the FTBFS/FTI policy](https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_sour…: > A week before the mass branching, any packages which still have open FTBFS bugs from the previous release will be retired. This can be requested via a releng issue. A week before the mass branching, according to [the schedule](https://fedoraproject.org/wiki/Releases/31/Schedule), is at **2019-08-06**. There are currently [~800 open F30FTBFS bugzillas](https://bugzilla.redhat.com/showdependencytree.cgi?id=F30FTBFS&h…, 20-30 of them are ON_QA. Prior to the retiring, I suggest we close bugs for packages that built after the mass rebuild. (I've tried to run [mass-rebuild-close-bugs.py](https://pagure.io/releng/blob/master/f/scripts/mass-rebuild-close-bugs.py) but ti apparently sees no build, as it did nothing but skip all. Either I using it wrong or it is broken.) ## When do you need this? On 2019-08-06. ## When is this no longer needed or useful? Final F30 Freeze (2019-10-08) makes this not useful for F30, but stil useful for rawhide/F31. ## If we cannot complete your request, what is the impact? 8 hundred FTBFS packages that nobody fixes. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8522

3 14

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2019