| Summary: | x11-libs/libXext-1.0.5: "Generic Event Extension" incorrectly reported as missing when app doesn't ask for it. | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | John Bowler <jbowler> |
| Component: | [OLD] Library | Assignee: | Gentoo X packagers <x11> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | jbowler |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch to fix the bug in libXext 1.0.5 | ||
|
Description
John Bowler
2009-10-17 03:07:29 UTC
Created attachment 207377 [details, diff] Patch to fix the bug in libXext 1.0.5 I've reported the bug #24581 in bugs.freedesktop.org. The patch, verified against x11-libs/libXext/libXext-1.0.5.ebuild, is attached (it simply corrects the strcmp test) and has been verified against my own program. That (the strcmp change) is the wrong fix - the code really was meant to do that. There is an existing fix for libXext; commit 8a91fc6f72206362f399b5e29bf3d5f44f4eb822 - see #24581, here: http://bugs.freedesktop.org/show_bug.cgi?id=24581 Or see the commit itself: http://cgit.freedesktop.org/xorg/lib/libXext/commit/?id=8a91fc6f72206362f399b5e29bf3d5f44f4eb822 It's a two liner diff and the libXext 1.0.5 code seems unchanged so it can just be back ported into 1.0.5 Fixed in libxext-1.1, if I'm reading this right. X11: Wanna backport? Otherwise, just close this bug as FIXED It's just a warning and is clearly marked as such... We'll get to newer libXext at some point. I don't see the need to backport that "fix". Cheers |