rel-eng April 2019

rel-eng@lists.fedoraproject.org

9 participants
268 discussions

[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 #8275: Fedora 31 FTBFS and all Fails to install tracker bugzillas
by Miro Hrončok 31 Jul '19

31 Jul '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 #8180: mass rebuild status page broken
by Zbigniew Jędrzejewski-Szmek 30 Jul '19

30 Jul '19

zbyszek reported a new issue against the project: `releng` that you are following: `` * Describe the issue https://kojipkgs.fedoraproject.org/mass-rebuild/f30-failures.html says > 16 failed builds: Unless a minor miracle happened, this can't be real ;) * When do you need this? (YYYY/MM/DD) Soon. * When is this no longer needed or useful? (YYYY/MM/DD) After all rebuild failures are fixed. * If we cannot complete your request, what is the impact? We can expect people no to fix build failures. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8180

5 8

[releng] Issue #7718: The FTBFS cleanup policy is not happening
by Miro Hrončok 24 Jul '19

24 Jul '19

churchyard reported a new issue against the project: `releng` that you are following: `` The https://fedoraproject.org/wiki/Fails_to_build_from_source policy says: > If a FTBFS bug remains in NEW state, a weekly reminder will be sent. This never happened. (Opened also as https://pagure.io/fesco/issue/1973 - feel free to close the less appropriate one.) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7718

6 45

[releng] Issue #8204: Changes/HardenedCompiler
by Huzaifa Sidhpurwala 19 Jul '19

19 Jul '19

huzaifas reported a new issue against the project: `releng` that you are following: `` * Describe the issue Please review: https://fedoraproject.org/wiki/Changes/HardenedCompiler * When do you need this? (YYYY/MM/DD) As soon as you can please * When is this no longer needed or useful? (YYYY/MM/DD) F31 System-Wide changes deadline :/ * If we cannot complete your request, what is the impact? Not sure, but maybe we cant include this change unless you review it? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8204

3 7

[releng] Issue #7606: F29 system wide change: uEFI for ARMv7
by Peter Robinson 17 Jul '19

17 Jul '19

pbrobinson reported a new issue against the project: `releng` that you are following: `` https://fedoraproject.org/wiki/Changes/uEFIforARMv7 Change for uEFI on ARMv7. There will need to be a new version of oz deployed on aarch64 builder userd for building images to enable us to build ARMv7 images on those devices. I will co-ordinate with infra/rel-eng to deploy and test this on stage/prod infrastructure, and once deployed and tested will provide a PR with the pungi config changes (minor) to enable this in the nightly composes. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7606

3 5

[releng] Issue #8243: Consider enabling safe-failed-tree plugin
by Kevin Fenzi 17 Jul '19

17 Jul '19

kevin reported a new issue against the project: `releng` that you are following: `` https://docs.pagure.org/koji/plugins/#save-failed-tree-plugin We would need to make sure we set filters right and that this correctly errors after a buildroot has been cleaned up by kojid. Perhaps we could try it in staging for a bit. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8243

3 5

[releng] Issue #8221: Change impact: F31 Mass Python 2 Package Removal
by Miro Hrončok 17 Jul '19

17 Jul '19

churchyard reported a new issue against the project: `releng` that you are following: `` https://fedoraproject.org/wiki/Changes/F31_Mass_Python_2_Package_Removal There will be releng tickets to orphan or retire packages. I also offer that I can do those (or at least help with them) if I have ACLs to do so. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8221

4 9

[releng] Issue #7996: Taking over Hoard
by Emery D Berger 17 Jul '19

17 Jul '19

emeryberger reported a new issue against the project: `releng` that you are following: `` * Hoard has been orphaned; I am claiming it and taking it over. (I am the author and maintainer of Hoard.) `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7996

5 16

[releng] Issue #8143: 12 packages have no git directory on pkgs02, but are active in pdc.
by Kevin Fenzi 17 Jul '19

17 Jul '19

kevin reported a new issue against the project: `releng` that you are following: `` These packages do not have git repos on pkgs02, but are active in pdc: ``` ERROR: /srv/git/repositories/rpms/R-gnomeGUI.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/actdiag.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/compat-ImageMagick6.9.3.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/gnome-cpufreq-applet.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/kf5-textwidgets.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/nwdiag.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/python-elementtree.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/repsurgeon.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/seqdiag.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/tetex-beamer.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/tetex-pgf.git does not appear to be a directory ERROR: /srv/git/repositories/rpms/tetex-xcolor.git does not appear to be a directory ``` so, likely they should be marked eol in pdc and blocked in koji? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/8143

4 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng April 2019