rel-eng September 2016

rel-eng@lists.fedoraproject.org

11 participants
59 discussions

#6184: suitesparse can't be installed in ppc64 el6 buildroots
by Fedora Release Engineering 07 Nov '16

07 Nov '16

#6184: suitesparse can't be installed in ppc64 el6 buildroots -----------------------------+------------------------ Reporter: rmattes | Owner: rel-eng@… Type: defect | Status: new Milestone: Fedora 23 Final | Component: epel Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ I'm running into trouble building GeographicLib in epel6. GeographicLib requires octave, which in turn requires suitesparse. It looks like suitesparse was in epel for a while, but got absorbed into rhel at some point and blocked from the buildroots. Since centos doesn't provide ppc64 packages, the ppc64 octave package in epel now has missing dependencies on suitesparse libraries and can't be installed in koji. What's the best way forward for this issue? Is it to: - Unblock the epel6 suitesparse and make it exclusivearch ppc64? - Rebuild all of the dependencies of suitesparse to excludearch ppc64? - Make octave-GeographicLib excludearch ppc64 and ignore the issue entirely? Please advise. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6184> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 3

#6348: Missing suitesparse-3.4.0-9.el6 ppc64 package
by Fedora Release Engineering 07 Nov '16

07 Nov '16

#6348: Missing suitesparse-3.4.0-9.el6 ppc64 package --------------------+------------------------ Reporter: ellert | Owner: rel-eng@… Type: task | Status: new Milestone: | Component: epel Keywords: | Blocked By: Blocking: | --------------------+------------------------ The octave package is not installable in EPEL 6 ppc64: https://kojipkgs.fedoraproject.org//work/tasks/1598/12901598/root.log {{{ DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcolamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libumfpack.so.5()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcholmod.so.1()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libccolamd.so.2()(64bit) DEBUG util.py:399: Error: Package: 6:octave-3.4.3-1.el6.ppc64 (build) DEBUG util.py:399: Requires: libcxsparse.so.2()(64bit) }}} On x86_64 and i686 these are provided by suitesparse-3.4.0-9.el6. The suitesparse package is provided by RHEL, but it seems to be missing for ppc64. There is an older version suitesparse-3.4.0-2.el6 provided by EPEL, but since this has a lower NVR than the RHEL version it is not used in the koji build roots. This was the version that was used to build the octave package for EPEL 6 ppc64. It looks like when the suitesparse package started being provided by RHEL 6 and the EPEL 6 package was retired, the ppc64 version of the package got lost. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6348> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 5

#6479: secondary tag for llvm 3.9
by Fedora Release Engineering 01 Nov '16

01 Nov '16

#6479: secondary tag for llvm 3.9 -----------------------------+------------------------ Reporter: airlied | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 25 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Can I get f25-llvm tag created so I can start importing llvm 3.9 and seeing what fails. Thanks, Dave. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6479> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 6

#6470: Infrastructure tags
by Fedora Release Engineering 31 Oct '16

31 Oct '16

#6470: Infrastructure tags -----------------------------+------------------------ Reporter: puiterwijk | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 25 Alpha | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Can we get the Infrastructure side tags in koji for F23, F24, EL6 and EL7 created that were discussed during the Infra meeting at Flock?? -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6470> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 1

#6313: atomic host: reorienting ostree commits to match 2 week cadence
by Fedora Release Engineering 13 Oct '16

13 Oct '16

#6313: atomic host: reorienting ostree commits to match 2 week cadence -----------------------------+------------------------ Reporter: walters | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Current as I understand it, we have a "two week" process for images (cloud, ISO etc.), but the OSTree commits are made at the default Fedora at-most-once-a-day cadence. I would like to propose doing only one released OSTree commit matching the two week release. Meaning `atomic host upgrade` would exactly what the images give. The advantage of this is predictability. NOTE: we need an exception for critical async security errata. The /testing/ ref though would continue at its current rate - and ideally go even faster. I would be a lot happier if we skipped the manual once-a-day RPM signing and did direct Koji -> /testing/. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6313> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 17

#6195: Signed commits for ostree / Project Atomic
by Fedora Release Engineering 03 Oct '16

03 Oct '16

#6195: Signed commits for ostree / Project Atomic -----------------------------+------------------------ Reporter: mattdm | Owner: rel-eng@… Type: enhancement | Status: new Milestone: Fedora 23 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ As Atomic moves from experimental to something users will actually depend on, we need to get this right. It's my understanding that the current workflow doesn't make it easy (the signing needs to happen in a place different from what we're used to). I don't know the specifics, but as Dennis says, "we should figure something out. I just do not know what a good answer is". The same thing might let us also sign RPM repo metadata. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6195> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 2

#6267: sign ostree commits
by Fedora Release Engineering 03 Oct '16

03 Oct '16

#6267: sign ostree commits -----------------------------+------------------------ Reporter: walters | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 23 Final | Component: koji Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ This has been discussed several times. AIUI it is blocked on a Fedora policy of not doing detached signatures. As downstream Red Hat Enterprise Linux and its associated PST are OK with detached signatures, I think Fedora should as well. The GPG signature would have helped mitigate https://git.fedorahosted.org/cgit/spin- kickstarts.git/commit/?id=1e408e111008f539c89212a9ca9bb955e2c4f823 for example. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6267> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 11

Current Fedora 25 Atomic images are failing to boot
by Kushal Das 03 Oct '16

03 Oct '16

Hi all, The current F25 Atomic images are failing to boot[1], I never managed to reach dracut emergency shell in my local box. Can anyone else also please have a look? [1] https://apps.fedoraproject.org/autocloud/jobs/704/output Kushal -- Fedora Cloud Engineer CPython Core Developer https://kushaldas.in https://dgplug.org

4 4

#6350: integrate atomic (host and other) CI/CD into Fedora
by Fedora Release Engineering 02 Oct '16

02 Oct '16

#6350: integrate atomic (host and other) CI/CD into Fedora -----------------------------+------------------------ Reporter: walters | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 24 Alpha | Component: other Keywords: | Blocked By: Blocking: | -----------------------------+------------------------ Breaking out from: https://fedorahosted.org/rel-eng/ticket/6313 Let's define a system and process for CD (Continuous Delivery) that bypasses manual integration via Koji/Bodhi and ships as quickly as possible to a small audience on dl.fedoraproject.org. Specifically, use rpmdistro-gitoverlay to mirror upstream sources that we know have been peer reviewed already, and build/ship them automatically. Also generate a devel/ ostree ref based on this content, and potentially images. Integrate pull request testing into this too. Resources required: - OpenStack tenant resources - Ability to write to dl.fedoraproject.org somewhere -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6350> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 9

#6482: fix bodhi buildroot overrides with secure-boot packages
by Fedora Release Engineering 28 Sep '16

28 Sep '16

#6482: fix bodhi buildroot overrides with secure-boot packages -----------------------------+------------------------ Reporter: kevin | Owner: rel-eng@… Type: task | Status: new Milestone: Fedora 25 Alpha | Component: koji Keywords: meeting | Blocked By: Blocking: | -----------------------------+------------------------ Currently if you try and make a bodhi buildroot override with any of the packages in the 'secure-boot' koji permission it fails with a: "Override : Unable to save buildroot override: policy violation (tag)" This is because the bodhi user doesn't have 'secure-boot' perms in koji and the hub permissions require that to tag a package in that list. Options to fix: * Grant bodhi the 'secure-boot' permission. This should fix this issue, but is it granting it too many perms? * Adjust the koji hub permissions so that bodhi is allowed to add secure- boot packages only to *override tags. * Some other solution. Note that bodhi does have the 'admin' permission in koji currently, so it could also just --force the tag, but it's desired to actually remove this permission from bodhi so I didn't list that as a solution. -- Ticket URL: <https://fedorahosted.org/rel-eng/ticket/6482> Fedora Release Engineering <http://fedorahosted.org/rel-eng> Release Engineering for the Fedora Project

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng September 2016