[releng] Issue #8191: logs attached to FTBFS issues are too short to be
usable for anything
by Zbigniew Jędrzejewski-Szmek
zbyszek reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
Pretty much every FTBFS bugs has "file build.log too big, will only attach last 1024 bytes" and "file root.log too big, will only attach last 1024 bytes". 1024 *lines* would be somewhat useful, but 1024 characters is just the spew that mock outputs at the end of every build and contains no hint why the build failed whatsoever.
In addition, the message does not specify what kind of failure was encountered. koji knows this and says to look either in root.log (dependency issues) or build.log (build issues). It would be great if this could be included in the bug message.
* When do you need this? (YYYY/MM/DD)
For the next rebuild.
* When is this no longer needed or useful? (YYYY/MM/DD)
When packages stop failing to build.
* If we cannot complete your request, what is the impact?
Maintainers have harder time solving FTBFS bugs.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8191
4 years, 11 months
[releng] Issue #8237: Some f30 modules require platform:f29 (list included)
by Adam Samalik
asamalik reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
The following modules won't install on Fedora 30, failing on platform:f29 dependency. That's because they have been tagged during the f29 branch point from f29 to f30.
```
stratis:master
golang-ecosystem:2017.0
reviewboard:2.5
pki:10.6
docker:2017.0
mongodb:3.6
cri-o:2018.0
container-tools:2018.0
mariadb:10.1
testmodule:master
```
Some of them should be removed — for example mariadb:10.1 because it only lists platform:f28 as its dependency in dist git. Other should be untagged but rebuilt — for example golang-ecosystem:2017.0 which has platform:[] in dist-git.
You'll need to check dist-git to determine which are which.
I discussed this with @mohanboddu on IRC. Let me know if you have any questions.
* When do you need this? (YYYY/MM/DD)
Preferably before F30 Beta release. But no later than F30 final freeze.
* When is this no longer needed or useful? (YYYY/MM/DD)
* If we cannot complete your request, what is the impact?
Installing those modules will keep being an error.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8237
4 years, 11 months
[releng] Issue #8345: Unretire nodejs-safe-buffer
by Tom Hughes
tomh reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
nodejs-safe-buffer
* FAS username of the new maintainer?
tomh
* Branches that you need it to be unretired for?
master
* Package re-review BZ URL?
Retired for less than two weeks so no re-review required.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8345
4 years, 11 months
[releng] Issue #8332: Unretire gnome-shell-extension-openweather
by Artem Polishchuk
atim reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
gnome-shell-extension-openweather
* FAS username of the new maintainer?
atim
* Branches that you need it to be unretired for?
master
f30
f29
epel7
* Package re-review BZ URL?
Retired for less than two weeks so no re-review required.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8332
4 years, 11 months
[releng] Issue #8331: Unretire nodejs-clone
by Tom Hughes
tomh reported a new issue against the project: `releng` that you are following:
``
* Name of the package?
nodejs-clone
* FAS username of the new maintainer?
tomh
* Branches that you need it to be unretired for?
master
* Package re-review BZ URL?
Retired for less than two weeks so no re-review required.
* Any extra information?
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/8331
4 years, 11 months
[releng] Issue #7907: Fedora 30 Toolchain Rebase: glibc 2.29, gcc 9.0
by Carlos O'Donell
codonell reported a new issue against the project: `releng` that you are following:
``
* Describe the issue
All Fedora releases must be released using a released and supported version of the core toolchain involving glibc, gcc, and binutils.
The Fedora toolchain team is responsible for ensuring that Fedora Rawhide stabilizes static linking, code generation, and library ABI, before a Fedora release, or that after the branch that the Fedora release is rebased (a very small rebase) to the final released version. This is a requirement for Fedora to inherit the ABI and API guarantees provided by upstream. If a mass rebuild is required by binutils, gcc, glibc or other components, the Fedora toolcahin team will ensure coordination with release engineering such that a mass rebuild uses the released version of all components and fix any last minute ABI or code-generation changes.
* When do you need this? (2019/01/30)
We need a mass rebuild.
Change page for review: https://fedoraproject.org/wiki/Changes/GLIBC229
Owner: Carlos O'Donell carlos(a)redhat.com
glibc mass rebuild request: This request.
Change page for review: https://fedoraproject.org/wiki/Changes/PPC64LE_Float128_Transition
Owner: Carlos O'Donell carlos(a)redhat.com
glibc mass rebuild request: ppc64le transition to 128-bit IEEE long double.
GCC will file a system-wide change request for GCC 9 transition also in December.
Binutils will remain as 2.31.1 and will not change (Nick Clifton's notes).
* If we cannot complete your request, what is the impact?
I we cannot do a mass rebuild then we should not transition to glibc 2.29 or gcc 9, but we might still be able to transition via targeted mass rebuilds.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/7907
4 years, 11 months