[releng] Issue #7525: unreasonable large build.log files for mingw-qt
by Till Maas
till reported a new issue against the project: `releng` that you are following:
``
```
du -hcs /mnt/koji/packages/mingw-qt/*/*/data/logs/*/build.log
[...]
253M /mnt/koji/packages/mingw-qt/4.8.7/1.fc25/data/logs/armv7hl/build.log
253M /mnt/koji/packages/mingw-qt/4.8.7/1.fc25/data/logs/i686/build.log
253M /mnt/koji/packages/mingw-qt/4.8.7/1.fc25/data/logs/x86_64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/2.fc26/data/logs/aarch64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/2.fc26/data/logs/armv7hl/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/2.fc26/data/logs/i686/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/2.fc26/data/logs/ppc64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/2.fc26/data/logs/ppc64le/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/2.fc26/data/logs/x86_64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc26/data/logs/aarch64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc26/data/logs/armv7hl/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc26/data/logs/i686/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc26/data/logs/ppc64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc26/data/logs/ppc64le/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc26/data/logs/x86_64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc27/data/logs/aarch64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc27/data/logs/armv7hl/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc27/data/logs/i686/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc27/data/logs/ppc64/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc27/data/logs/ppc64le/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc27/data/logs/s390x/build.log
2,7G /mnt/koji/packages/mingw-qt/4.8.7/3.fc27/data/logs/x86_64/build.log
69G
```
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7525
4 years, 11 months
[releng] Issue #7344: Please generate static deltas for FAW27
by Colin Walters
walters reported a new issue against the project: `releng` that you are following:
``
ostree has had static deltas for years now; it makes us look less than stellar if people aren't getting them. We do this as part of the FAH release process, but at the moment there is no such thing for FAW which just drops out of pungi. Simplest thing is probably to add it to Ansible for now, literally just `ostree --repo=/path/to/repo static-delta generate --if-not-exists fedora/27/x86_64/workstation`. (However, the benefits of deltas will be greatly maximized if we batch updates)
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7344
5 years
[releng] Issue #7455: Missing f28 dist-git branches
by Petr Pisar
ppisar reported a new issue against the project: `releng` that you are following:
``
Till now I found 4 packages that were missing f28 dist-git branches that should have been created at f28 branching time:
rpms/perl-Alien-Base-ModuleBuild
rpms/perl-Exporter-Easy
rpms/perl-Math-Utils
rpms/perl-Test-Exit
I worry there is some bug in the mass branching script and more packages are missing the f28 branch. Please recheck the repositories and create the branches where missing. (These four have already been fixed.)
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7455
5 years
[releng] Issue #7439: Bodhi can now manage containers
by Randy Barlow
bowlofeggs reported a new issue against the project: `releng` that you are following:
``
Greetings!
Today I deployed Bodhi 3.6.0 to production, which adds support for containers (except for buildroot overrides). To make use of it, we just need to add container releases to Bodhi with all the appropriate Koji tags and we're off to the races. Doing so may or may not require Freeze Break Requests, not sure, but wanted to let you know that the feature is ready for your use as you see fit.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7439
5 years
[releng] Issue #7405: [s390x] Latest cloud-base and (or) container images
are failing for F28 and rawhide composes
by Sinny Kumari
sinnykumari reported a new issue against the project: `releng` that you are following:
``
By looking into last few nightly composes for container and cloud on s390x, I observed that we never had all of the artifacts built successfully in a single compose.
For example:
* From Fedora-28-20180317.n.0 - cloud-base and container-minimal-base image built successfully. container-base image failed
* From Fedora-28-20180317.n.0 - cloud-base and container-base image built successfully. conatiner-minimal-base image failed.
Similar results from rest of the latest compose.
I did some local run of these images using imagefactory and each time following behavior has been seen:
* kernel.img and initrd files get downloaded, vm gets launched to start install process.
* vm boots and it reaches at
[ OK ] Reached target System Initialization.
[ OK ] Reached target Basic System.
[ 35.891858] dracut-initqueue[817]: RTNETLINK answers: File exists
[ 76.688981] random: crng init done
[ 427.634076] dracut-initqueue[817]: Warning: dracut-initqueue timeout - starting timeout scripts
---
[ 625.922797] dracut-initqueue[817]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 625.923855] dracut-initqueue[817]: Warning: Could not boot.
Starting Dracut Emergency Shell...
Warning: /dev/root does not exist
dracut:/#
and vm install stops here.
Not sure what is the reason of this behavior. Can it be something related to network between s390x machine and koji ?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7405
5 years