[releng] Issue #7388: predicting dependency failures in image builds
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
It would be nice if we could predict when dependency failures in image builds will happen. I have been using a rough set of commands to do this in the past few weeks but this could be polished up and put in place to forecast failures.
What I;ve been doing is:
`
dnf --releasever 29 --installroot /srv/installroot/ --disablerepo=* --enablerepo=today --enablerepo=koji install $(cat packages.txt | sed 's/^-/--exclude /' | tr '\n' ' ')
`
- where repo `today` is today's rawhide run
- where repo `koji` is the f29-build repo
- where packages.txt is the %packages list from a kickstart file
This is a pretty good indicator of failures.
This could be refined and put into a testing framework to run often. Steps: For each kickstart do:
- `ksflatten` kickstart file and get `%packages` list
- For groups use libcomps and fedora-comps repo to determine packages
- use koji `f29-build` repo and list of packages to determine if there are missing dependencies
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7388
5 years
[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
[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
[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, 1 month
[releng] Issue #7113: proposal to run bodhi updates pungi composes with
`--no-label`
by Dusty Mabe
dustymabe reported a new issue against the project: `releng` that you are following:
``
We have just started running bodhi updates via pungi (woo!!). One of the reasons the Atomic team has been helping drive this initiative is so that we can get better versioning of our ostrees output by fedora (via pungi).
When we started doing the runs we added a label to them of the form: `Update-20171025.1312`. Which translates into an ostree version of `27_Update.20171025.1312`. The atomic working group had previously got together and [decided](https://pagure.io/atomic-wg/issue/229) that a versioning scheme like `27.2017025.0` would be what we went with for better versioning for ostrees. This scheme was discussed with releng (including dennis) and also added as an RFE to pungi, which was implemented by @lsedlar in [PR](https://pagure.io/pungi/pull-request/592).
With the updates run we can get the desired version if we provide `--no-label` to pungi instead of actually giving it a label. This warrants the question: "what is the value of the label for an updates run?". Do we need it? What is it used for?
If we don't need it then I'd love to just use `--no-label`. If we do need it then we'll have to implement another smart versioning macro for ostrees in pungi.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7113
5 years, 4 months