Bug 293435

Summary:	x11-misc/synergy-plus missing libXtst dependency
Product:	Gentoo Linux	Reporter:	Adam Nielsen <a.nielsen>
Component:	New packages	Assignee:	Doug Goldstein (RETIRED) <cardoe>
Status:	RESOLVED INVALID
Severity:	normal	CC:	desktop-misc, flameeyes
Priority:	High
Version:	2008.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Adam Nielsen 2009-11-16 22:53:35 UTC

I just emerged synergy-plus but it failed because it couldn't locate XTest.h.  This file has moved to x11-libs/libXtst, so I think libXtst should be added as a dependency of synergy-plus.

Apparently it used to be included in x11-proto/xextproto-7.0.5 (or thereabouts) but since x11-proto/xextproto-7.1.1 or so XTest.h is no longer included.  See bug 239653.

Comment 1 Doug Goldstein (RETIRED) gentoo-dev

2009-11-17 01:22:02 UTC

Bit confused here...

CDEPEND="x11-libs/libXtst
    x11-libs/libX11
    x11-libs/libXext
    x11-libs/libXinerama"
RDEPEND="${CDEPEND}
    !x11-misc/synergy"
DEPEND="${CDEPEND}
    x11-proto/xextproto
    x11-proto/xproto
    x11-proto/kbproto
    x11-proto/xineramaproto
    x11-libs/libXt"


Its already in RDEPEND and DEPEND so your issue is something else. Please attach the build.log and your emerge --info

Comment 2 Adam Nielsen 2009-11-17 02:36:09 UTC

That's odd, you're right.  If I uninstall libXtst then it gets pulled in with synergy-plus, yet 24 hours ago it wasn't being pulled in with synergy-plus and emerging libXtst reported it as a new package (not an upgrade or rebuild.)

Unfortunately with all the testing I've overwritten most of the build logs and I can no longer reproduce the issue.  The only build.log left behind from when things were broken is when I manually created an XTest.h to see if it would compile, which won't be an accurate indicator of what happened.

I can't see any logs in there that indicate why it decided libXtst was installed though.  Just that it was a dependency.  If you've got any suggestions where to look, let me know.

At any rate it seems the cause was a configuration issue at my end, so I'll mark the bug as invalid.  Thanks for the quick response.