Summary: | media-libs/libquvi-0.4.1 with media-libs/libquvi-scripts-0.9.20131130 - configure: error: Package requirements (libquvi-scripts >= 0.4.0) were not met: No package 'libquvi-scripts' found | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Vladimir Miloserdov <milosvova> |
Component: | [OLD] Library | Assignee: | Gentoo Media-video project <media-video> |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | ao, bkohler, milosvova, staff, xmw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log
emerge -pqv output config.log |
Description
Vladimir Miloserdov
2014-02-05 03:14:10 UTC
Created attachment 369558 [details]
build.log
Created attachment 369560 [details]
emerge -pqv output
!!! Please attach the following file when seeking support: !!! /var/tmp/portage/media-libs/libquvi-0.4.1/work/libquvi-0.4.1_build/config.log Please do. Also, post your `emerge -vpq media-libs/libquvi-scripts' output in a comment. emerge -vpq media-libs/libquvi-scripts output: [ebuild R ] media-libs/libquvi-scripts-0.9.20131130 USE="-offensive" Created attachment 369624 [details]
config.log
ceres ~ 1 # emerge -vpq media-libs/libquvi-scripts [ebuild U ] media-libs/libquvi-scripts-0.9.20131130 [0.9.20131104] USE="-offensive" Downgrading (`emerge -av1 =media-libs/libquvi-scripts-0.9.20131104`) solves this, kinda. Why are you using stable libquvi with unstable libquvi-scripts? For unstable mplayer with quvi use flag enabled stable libquvi is required. My system is unstable so I've got libquvi-scripts installed. Yes, an unsuspecting full-unstable user can hit this easily. mplayer2 has this in RDEPEND: quvi? ( >=media-libs/libquvi-0.4.1 <media-libs/libquvi-0.9 ) It seems to me that media-libs/libquvi-0.4.1 should further restrict its libquvi-scripts dep, from just >=media-libs/libquvi-scripts-0.4.0 to >=media-libs/libquvi-scripts-0.4.0 <media-libs/libquvi-scripts-0.9 That should take care of the issue. Is there any reason that any of the libquvi-scripts-0.9* versions should be allowed with libquvi-0.4*? should be fixed in libquvi-0.4.1-r1 |