| Summary: | x11-libs/libva-intel-driver-1.0.18-r1 fails to compile | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Karl Newman <SiliconFiend> |
| Component: | [OLD] Library | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Karl Newman
2012-08-20 20:46:03 UTC
... just why? See this: $ equery d libva * These packages depend on libva ... x11-libs/libva-intel-driver-1.0.18-r1 (>=x11-libs/libva-1.0.16) Sorry, I forgot to mention that because of some upstream funnyness 1.0.16 is actually newer than 1.1.0. Thanks, that fixed it. I emerged x11-libs/libva-1.0.16 and then x11-libs/libva-intel-driver-1.0.18-r1 emerged just fine. I normally try to avoid downgrading (which this appeared to be) and I figured the libva-1.1.0 ebuild would be replaced or upgraded shortly following its removal, but I didn't know about the upstream version sillyness. I also do that sometimes, but an additional 'equery c <package>' doesn't hurt to gather some info about the nature of a mask/removal. That's a completely awesome command. I've always hunted up the ChangeLog manually. I've been using Gentoo for 7 years and I'm still learning things... Thanks! |