On Sat, 19 July 2014, at 2:26 am, [email protected] wrote: > ... > dev-java/java-sdk-docs-1.7.0.60 cannot be emerged. > > !!! dev-java/java-sdk-docs-1.7.0.60 has fetch restriction turned on. > ... > > I downloaded that file manually. It turns out, that Orcale offers > version dev-java/java-sdk-docs-1.7.0.65 in the meanwhile. > > An according bug was filed. > > When will the ebuild it be updated?
Doesn't matter, bump /usr/portage/dev-java/java-sdk-docs/java-sdk-docs-1.7.0.60.ebuild to java-sdk-docs-1.7.0.65 in your local overlay. This probably means something like # mkdir -p /usr/local/portage/dev-java/java-sdk-docs/ # cp /usr/portage/dev-java/java-sdk-docs/java-sdk-docs-1.7.0.60.ebuild /usr/local/portage/dev-java/java-sdk-docs/java-sdk-docs-1.7.0.65.ebuild # ebuild /usr/local/portage/dev-java/java-sdk-docs/java-sdk-docs-1.7.0.65.ebuild manifest # emerge -1 =java-sdk-docs/java-sdk-docs-1.7.0.65 You can't rely on when the devs might update the tree - there's no way to know when they'll do so/ Hopefully the devs will bump mainline quickly, as the fetch restriction will surely break this package for everyone, but there's no point in waiting on them. Stroller.
