1 |
On Sat, 19 July 2014, at 2:26 am, meino.cramer@×××.de wrote: |
2 |
> ... |
3 |
> dev-java/java-sdk-docs-1.7.0.60 cannot be emerged. |
4 |
> |
5 |
> !!! dev-java/java-sdk-docs-1.7.0.60 has fetch restriction turned on. |
6 |
> ... |
7 |
> |
8 |
> I downloaded that file manually. It turns out, that Orcale offers |
9 |
> version dev-java/java-sdk-docs-1.7.0.65 in the meanwhile. |
10 |
> |
11 |
> An according bug was filed. |
12 |
> |
13 |
> When will the ebuild it be updated? |
14 |
|
15 |
|
16 |
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. |
17 |
|
18 |
This probably means something like |
19 |
|
20 |
# mkdir -p /usr/local/portage/dev-java/java-sdk-docs/ |
21 |
# 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 |
22 |
# ebuild /usr/local/portage/dev-java/java-sdk-docs/java-sdk-docs-1.7.0.65.ebuild manifest |
23 |
# emerge -1 =java-sdk-docs/java-sdk-docs-1.7.0.65 |
24 |
|
25 |
You can't rely on when the devs might update the tree - there's no way to know when they'll do so/ |
26 |
|
27 |
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. |
28 |
|
29 |
Stroller. |