[releng] Issue #7553: Arch-Specific Runtime Dependencies in sub-packages
by Miro Hrončok
churchyard reported a new issue against the project: `releng` that you are following:
``
Please first read trough https://pagure.io/packaging-committee/issue/691
We have been approached by this question:
1. I have an noarch package `foo`
2. it has (implicitly noarch) subpackage `foo-extra`, it has a runtime dependency on `extra` package (that is not available on `xyz` arch)
How do I proceed to exclude the `foo-extra` subpackage from being build/available on the `xyz` arch?
Do I need to switch both the main package and the subpackage to be arched?
In FPC, we have some _ideas_ about how it _should_ work, however, we don't know how it actually is implemented.
Thanks
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7553
5 years, 1 month
[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
5 years, 1 month
[releng] Issue #8232: EPEL 6 buildroot broken in koji for x86_64
by Mattias Ellert
ellert reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Build fails in EPEL 6 with the following error:
```
DEBUG util.py:554: BUILDSTDERR: Error:
DEBUG util.py:554: BUILDSTDERR: Problem: conflicting requests
DEBUG util.py:554: BUILDSTDERR: - nothing provides texinfo-tex needed by R-core-devel-3.5.2-2.el6.x86_64
DEBUG util.py:556: (try to add '--skip-broken' to skip uninstallable packages)
DEBUG util.py:698: Child return code was: 1
```
The error only happens on x86_64. For the other architectures
texinfo-tex.ppc64 4.13a-8.el6
texinfo-tex-4.13a-8.el6.i686
are installed
See: https://koji.fedoraproject.org/koji/taskinfo?taskID=33758893
(I tried three times with the same result)
* When do you need this? (YYYY/MM/DD)
As soon as possible
* When is this no longer needed or useful? (YYYY/MM/DD)
When EPEL 6 is EOL
* If we cannot complete your request, what is the impact?
Some packages in EPEL 6 can not be built.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8232
5 years, 1 month
[releng] Issue #8230: Taking over the pl package
by Jerry James
jjames reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
I would like ownership of the pl package, which is currently orphaned.
* When do you need this? (YYYY/MM/DD)
ASAP
* When is this no longer needed or useful? (YYYY/MM/DD)
N/A
* If we cannot complete your request, what is the impact?
A bunch of my packages get retired next week.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8230
5 years, 1 month