Bug 596806

Summary:	=www-client/vimb-2.11 USE=gtk3 depends on incorrect net-libs/webkit-gtk slot
Product:	Gentoo Linux	Reporter:	Virgil Dupras (RETIRED) <vdupras>
Component:	Current packages	Assignee:	No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed>
Status:	RESOLVED INVALID
Severity:	normal
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	vimb build log emerge --info vimb

Description Virgil Dupras (RETIRED) gentoo-dev

2016-10-11 00:26:00 UTC

www-client/vimb-2.11 specifies ">=net-libs/webkit-gtk-1.5.0:3" in the gtk3 branch of its dependencies. This causes webkit-gtk's 4th slot to be installed.

Then, when comes the time to build, vimb can't find the proper webkit-gtk library.

On my machine, changing the slot to "3/25" did the trick and vimb builds and installs properly.

Comment 1 Pacho Ramos gentoo-dev

2016-10-16 09:05:04 UTC

Please provide full build.log and emerge --info vimb

Comment 2 Virgil Dupras (RETIRED) gentoo-dev

2016-11-12 19:11:02 UTC

Created attachment 453152 [details]
vimb build log

Comment 3 Virgil Dupras (RETIRED) gentoo-dev

2016-11-12 19:11:37 UTC

Sorry for my response's delay. I forgot about it. Attached to this message are my build log and emerge --info.

The interesting bit in the log is at the end when it looks for "webkit-1.0" instead of "webkitgtk-3.0" (the library name set in GTK3LIBS at https://github.com/fanglingsu/vimb/blob/master/config.mk#L25 )

Comment 4 Virgil Dupras (RETIRED) gentoo-dev

2016-11-12 19:12:11 UTC

Created attachment 453154 [details]
emerge --info vimb

Comment 5 Virgil Dupras (RETIRED) gentoo-dev

2016-11-12 19:26:39 UTC

Upon further examination, it seems that my proposed slot change from "3" to "3/25" has no effect on the result of the build and that the "webkit-1.0" mention during the install phase is irrelevant becaue the final executable ends up being linked to libwebkitgtk-3.0.

I can't seem to be able to reproduce the issue I was initially having when I opened this issue. Coming back to Gentoo's version of vimb causes no problem on my machine.

Sorry about the noise.