| Summary: | Outdated version of colorgcc package (1.3.2, latest official is 1.4.4) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Maciej Sitarz <macieksitarz+redhatbugzilla> |
| Component: | colorgcc | Assignee: | Martin Cermak <mcermak> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 26 | CC: | hdegoede, mcermak |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | colorgcc-1.4.5-1.fc27 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-21 19:02:30 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The package is still in the old version on Fedora 26. Changing "Version" to "26". Maciej, would you mind checking if following scratch-build works for you? https://koji.fedoraproject.org/koji/taskinfo?taskID=23343217 https://mcermak.fedorapeople.org/colorgcc-1.4.5-1.fc28/ Martin, I'm in the middle of an upgrade to F27. If a test on F27 is fine I'll do it soon. Yup, please; you can also test this on top of F26. That still makes sense, since the F26 build would have different NVR, but identical content. Thanks. I did a simple test on F27 and it works. There are still no symlinks in the package which I mentioned in the bug's description. Is it intentional? ccache RPM package provides such symlinks. Maciej, the package already provides two sets of symlinks:
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/color-g++
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/color-cc
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/color-c++
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/color-ccache
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/colorgcc
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/colorg++
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/colorcc
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/colorc++
ln -s %{_bindir}/color-gcc $RPM_BUILD_ROOT/%{_bindir}/colorccache
Part of it is per bz1078180. I'm inclined to leave it as-is.
Thoughts?
I was rather thinking about symlinks named like compilers: gcc, g++, cc, c++. This way users can have that directory on the PATH and this way use colorgcc without modyfying Makefiles, special parameters etc. Just like using ccache. Hmm, you only ask for adding a few symlinks to the package. Nothing else. How does this help? How do you imagine the appropriate $PATH setting to be handled? Some /etc/profile.d/colorgcc* scripts? Or personal shell config file edited by hand? How about colorgcc co-existing with e.g. ccache? The user might want to install colorgcc only, or ccache only, or both, or both and then remove one, and that should still all work. Such setups might involve editing the colorgcc configuration file(!). Do you propose to automate such edits? Using rpm scriptlets? Or do you propose to let the user set that all up by hand? Thoughts? User will add the directory with symlinks to his PATH (in .bashrc or other config). The other approach reqires using colorgcc as a compiler name. colorgcc-1.4.5-1.fc27 has been submitted as an update to Fedora 27. https://bodhi.fedoraproject.org/updates/FEDORA-2017-ce5bdd2300 colorgcc-1.4.5-1.fc27 has been pushed to the Fedora 27 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-ce5bdd2300 colorgcc-1.4.5-1.fc27 has been pushed to the Fedora 27 stable repository. If problems still persist, please make note of it in this bug report. |
Description of problem: colorgcc package is out of date Version-Release number of selected component (if applicable): Version: 1.3.2 Release: 14%{?dist} Actual results: Current version for Fedora 24 is 1.3.2-14 Expected results: Epected version is 1.4.4 Additional info: Latest source code can be downloaded from: https://github.com/olibre/colorgcc/releases Example build script (Archlinux PKGBUILD): https://git.archlinux.org/svntogit/community.git/tree/trunk/PKGBUILD?h=packages/colorgcc There are some major fixes: - Tested with GCC-4.9 (Support GCC_COLOR) - Fixed bug when chained with ccache - Auto-detect compiler within the $PATH - System wide configuration support Also symlinks to gcc, cc, c++, g++ in the package would be useful: Example code: for i in cc c++ gcc g++ ; do ln -s /usr/bin/colorgcc "${pkgdir}/usr/lib/colorgcc/bin/${i}" done