July 2018 - rel-eng - Fedora Mailing-Lists

[releng] Issue #7379: Cannot install the python2-markdown RPM on Rawhide because the module gets pulled in for some reason

by Randy Barlow

bowlofeggs reported a new issue against the project: `releng` that you are following: `` Bodhi CI is failing to run on Rawhide because it cannot install python2-markdown. Instead of the RPM being present in the repository, the module for it is present instead and is signed with the wrong key: ``` $ sudo docker run --rm -it registry.fedoraproject.org/fedora:rawhide dnf install -y python2-markdown Fedora - Rawhide - Developmental packages for the next Fedora release 3.0 MB/s | 60 MB 00:19 Last metadata expiration check: 0:00:21 ago on Wed Mar 7 17:12:37 2018. Dependencies resolved. =================================================================================================================================================================================================================== Package Arch Version Repository Size =================================================================================================================================================================================================================== Installing: python2-markdown noarch 2.4.1-11.module_0b083f9b rawhide 189 k Installing dependencies: python2 x86_64 2.7.14-13.fc29 rawhide 101 k python2-libs x86_64 2.7.14-13.fc29 rawhide 6.3 M python2-pip noarch 9.0.1-16.fc29 rawhide 1.8 M python2-setuptools noarch 38.4.0-3.fc28 rawhide 622 k Transaction Summary =================================================================================================================================================================================================================== Install 5 Packages Total download size: 9.0 M Installed size: 36 M Downloading Packages: (1/5): python2-markdown-2.4.1-11.module_0b083f9b.noarch.rpm 513 kB/s | 189 kB 00:00 (2/5): python2-2.7.14-13.fc29.x86_64.rpm 274 kB/s | 101 kB 00:00 (3/5): python2-setuptools-38.4.0-3.fc28.noarch.rpm 743 kB/s | 622 kB 00:00 (4/5): python2-pip-9.0.1-16.fc29.noarch.rpm 942 kB/s | 1.8 MB 00:01 (5/5): python2-libs-2.7.14-13.fc29.x86_64.rpm 1.1 MB/s | 6.3 MB 00:05 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Total 1.4 MB/s | 9.0 MB 00:06 warning: /var/cache/dnf/rawhide-2d95c80a1fa0a67d/packages/python2-markdown-2.4.1-11.module_0b083f9b.noarch.rpm: Header V3 RSA/SHA256 Signature, key ID a3cc4e62: NOKEY Importing GPG key 0x429476B4: Userid : "Fedora 29 (29) <fedora-29(a)fedoraproject.org>" Fingerprint: 5A03 B4DD 8254 ECA0 2FDA 1637 A20A A56B 4294 76B4 From : /etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-x86_64 Key imported successfully Import of key(s) didn't help, wrong key(s)? Public key for python2-markdown-2.4.1-11.module_0b083f9b.noarch.rpm is not installed. Failing package is: python2-markdown-2.4.1-11.module_0b083f9b.noarch GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-fedora-29-x86_64 The downloaded packages were saved in cache until the next successful transaction. You can remove cached packages by executing 'dnf clean packages'. Error: GPG check FAILED ``` `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7379

5 years, 2 months

3
3
0 / 0

[releng] Issue #7354: apitrace-libs.i686 version mismatches apitrace-libs.x86_64 on F27

by Sandro Mani

smani reported a new issue against the project: `releng` that you are following: `` On F27 the current version of apitrace is apitrace-7.1-7.fc27. On F27 x86_64 however, # dnf install --refresh apitrace-libs.i686 currently gives you apitrace-libs-7.1-7.fc27.i686 (note: -7 instead of -9). On the other hand, # dnf install --refresh apitrace-libs gives you apitrace-libs-7.1-9.fc27.x86_64 as expected. apitrace-libs is multilib whitelisted, but appears to be out of sync. See also #1541099. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7354

5 years, 2 months

2
2
0 / 0

[releng] Issue #7316: variants-modular.xml & fedora-release*

by Langdon White

langdon reported a new issue against the project: `releng` that you are following: `` Once [#7227](https://pagure.io/releng/issue/7227) is complete, I wanted to confirm that: * We should continue to make PRs against [variants-modular.xml](https://pagure.io/pungi-fedora/blob/master/f/variants-modular.xml) and file tickets here to get new modules added to the compose. * Should we file tickets here or use some other method to get changes to fedora-release* rpms? Specifically, we will need to include a system profile ([for example](https://github.com/sgallagher/semimodular_poc/blob/master/semimo...) and modify it as modules are added. /cc @sgallagh @psabata `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7316

5 years, 2 months

2
2
0 / 0

[releng] Issue #7031: Should f27 and f27-build have different architectures?

by Kellin

kellin reported a new issue against the project: `releng` that you are following: `` $ koji taginfo f27 Tag: f27 [417] Arches: armv7hl i686 x86_64 ppc64 ppc64le aarch64 ^PGroups: appliance-build, build, livecd-build, livemedia-build, srpm-build Required permission: 'admin' Tag options: mock.package_manager : 'dnf' Inheritance: $ koji taginfo f27-build Tag: f27-build [425] Arches: aarch64 armv7hl i686 ppc64 ppc64le s390x x86_64 Groups: appliance-build, build, livecd-build, livemedia-build, srpm-build Required permission: 'admin' Tag options: This tag is a buildroot for one or more targets Current repo: repo#785431: 2017-09-14 21:09:29.969602 Targets that build from this tag: f27-candidate f27-rebuild f27-binutils-rebuild f27 Inheritance: 0 .... f27-override [424] `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7031

5 years, 2 months

4
6
0 / 0

[releng] Issue #7664: Delete rawhide-repo-holder build target

by Mikolaj Izdebski

mizdebsk reported a new issue against the project: `releng` that you are following: `` * Describe the issue Presence of [rawhide-repo-holder](https://koji.fedoraproject.org/koji/buildtargetinfo?... build target in Koji makes kojira generate repos for [rawhide](https://koji.fedoraproject.org/koji/taginfo?tagID=197) tag, which according to @puiterwijk is not used any longer. * When do you need this? (YYYY/MM/DD) earliest convenience * When is this no longer needed or useful? (YYYY/MM/DD) * If we cannot complete your request, what is the impact? Koji resources are wasted generating unneeded repos. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7664

5 years, 2 months

3
5
0 / 0

[releng] Issue #7604: F29 System-Wide Change: Remove Excessive Linking

by Igor Gnatenko

ignatenkobrain reported a new issue against the project: `releng` that you are following: `` Please review https://fedoraproject.org/wiki/Changes/RemoveExcessiveLinking change. P.S. I don't think that any actions from rel-eng are needed. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7604

5 years, 3 months

5
10
0 / 0

[releng] Issue #7110: libtomcrypt missing from Koji f27 buildroot?

by Randy Barlow

bowlofeggs reported a new issue against the project: `releng` that you are following: `` Greetings! I've discovered that [Bodhi doesn't build in F27](https://koji.fedoraproject.org/koji/taskinfo?taskID=22659036) as of recently, as libtomcrypt doesn't seem to be available in the buildroot: ``` - nothing provides libtomcrypt.so.0()(64bit) needed by python2-crypto-2.6.1-17.fc27.s390x ``` I [reported this](https://bugzilla.redhat.com/show_bug.cgi?id=1505641) to the libtomcrypt maintainer, who pointed out that it seems to be tagged correctly. I then realized that I was able to install it in an f27 container as well: ``` $ sudo docker run --rm registry.fedoraproject.org/fedora:27 dnf install python2-crypto -y ``` Is there maybe something wrong with the f27 buildroot that causes this issue? `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7110

5 years, 3 months

3
5
0 / 0

[releng] Issue #7173: Orphan all of jcapik's packages

by Randy Barlow

bowlofeggs reported a new issue against the project: `releng` that you are following: `` FESCo has voted to orphan all of @jcapik's packages: https://pagure.io/fesco/issue/1786 `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7173

5 years, 4 months

14
24
0 / 0

[releng] Issue #7612: moving fedora-release entirely to src.fp.o

by Zbigniew Jędrzejewski-Szmek

zbyszek reported a new issue against the project: `releng` that you are following: `` * Describe the issue This is a continuation of the proposal made on fedora-devel late last year and repeated recently [https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.o...]. The dicussion there didn't result in any decision, and @ausil recommended that it talk with releng directly. I'd asking for the following: - retirement of the seperate "upstream" for fedora-release, i.e. simply merge https://pagure.io/fedora-release/pull-request/119. This has to be done by one of the owners of that repo. - the ability to build fedora-release. I probably can write to dist-git directly as proven packager, but I'm not sure if I can successfully build the package in koji. Either way, I'd prefer to be added as co-maintainer to make this official, and for any other changes that need to be made to be made. - review of https://src.fedoraproject.org/fork/zbyszek/rpms/fedora-release/branch/dro.... I can't submit that as PR now, because PRs are disabled. Stuff that I can do myself, once the above is done: - enable PRs on src.fp.o/rpms/fedora-release - resubmit the drop-upstream-split as PR, merge it once it's reviewed, and build - resubmit other requests against fedora-release as PRs, e.g. https://pagure.io/fedora-release/pull-request/139 and others. * When do you need this? A few days or a week would be great. Doing this will allow preset requests to be processed more quickly, making other things happen faster too. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7612

5 years, 4 months

3
14
0 / 0

[releng] Issue #7030: please create f27-kde koji sidetarget

by Rex Dieter

rdieter reported a new issue against the project: `releng` that you are following: `` Please create a f27-kde koji sidetarget, have a few large batched updates to do (already). No rest for the wicked. `` To reply, visit the link below or just reply to this email https://pagure.io/releng/issue/7030

5 years, 5 months

6
13
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

rel-eng July 2018