| Summary: | x11-libs/cairo-1.12.16-r4 stabilization request | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Arfrever Frehtes Taifersar Arahesis <arfrever.fta> |
| Component: | [OLD] Keywording and Stabilization | Assignee: | Alexandre Rostovtsev (RETIRED) <tetromino> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | alpha, ia64, junghans, multilib+disabled, pacho, ppc64, ppc, sparc, x11, x86, yngwin |
| Priority: | Normal | Keywords: | STABLEREQ |
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | 510782 | ||
| Bug Blocks: | |||
|
Description
Arfrever Frehtes Taifersar Arahesis
2014-10-13 15:58:56 UTC
X11 team is going to make a big stabilization bug for all packages in the herd again. If the other maintainers wish to proceed earlier, please go ahead. Please continue in the x11 stabilization bug. If the other maintainers wish to proceed with stabilization before the x11 stabilization bug is ready, re-open this bug and CC: arches. *** This bug has been marked as a duplicate of bug 530652 *** I want to fix build failure with recent gcc before stabilizing (bug #510782) (In reply to Alexandre Rostovtsev from comment #3) > I want to fix build failure with recent gcc before stabilizing (bug #510782) Looks like it fail with gcc-4.9, not 4.8 (the latest stable one) :/ Depending on how long we wait, we might want to jump straight to 1.12.18. People, you are slacking and emul-linux-x86 are eating puppies! (In reply to Alexandre Rostovtsev from comment #3) > I want to fix build failure with recent gcc before stabilizing (bug #510782) Is there any fix undergoing? If not, I'd rather see cairo stabilized and USE=lto p.u.masked. Adding lto semi-implicitly to random packages in the tree is a bad idea anyway. (In reply to Michał Górny from comment #7) > (In reply to Alexandre Rostovtsev from comment #3) > > I want to fix build failure with recent gcc before stabilizing (bug #510782) > > Is there any fix undergoing? If not, I'd rather see cairo stabilized and > USE=lto p.u.masked. Adding lto semi-implicitly to random packages in the > tree is a bad idea anyway. Ok, I see that upstream reverted LTO support. Disabled it in 1.2.16-r[34] as well. *cairo-1.12.16-r4 (29 Nov 2014) 29 Nov 2014; Michał Górny <mgorny@gentoo.org> +cairo-1.12.16-r4.ebuild: Stop wrapping cairo-features.h. Now that we pass consistent configure options, it should be the same on all ABIs. Fixes compatibility with dev-haskell/cairo hackery, bug #531120. Maybe -r4 would be a better stable candidate, and it shouldn't add any delay as we are near a month since it was added to the tree arm stable Stable for HPPA. amd64 stable Superseded by bug #540676 - please stabilize 1.12.18 now, it fixes lots of bugs. *** This bug has been marked as a duplicate of bug 540676 *** |
