Michael Orlitzky wrote:
> On 04/11/2018 06:27 AM, Dale wrote:
>> I think that is where they were talking about moving it from. At one
>> point, they were discussing putting it in /var somewhere. Maybe they
>> decided not to move it at all. I seem to recall there being a quite
>> active and lengt
On 04/11/2018 06:27 AM, Dale wrote:
>
> I think that is where they were talking about moving it from. At one
> point, they were discussing putting it in /var somewhere. Maybe they
> decided not to move it at all. I seem to recall there being a quite
> active and lengthy thread about it on -dev
Peter Humphrey wrote:
> On Wednesday, 11 April 2018 11:27:39 BST Dale wrote:
>> R0b0t1 wrote:
>>> On Tue, Apr 10, 2018 at 11:08 PM, Dale wrote:
J. Roeleveld wrote:
> Sounds like a bug.
> All fetch restriction packages I encounter want it in your distfiles
> folder. (Wherever you c
On Wednesday, 11 April 2018 11:27:39 BST Dale wrote:
> R0b0t1 wrote:
> > On Tue, Apr 10, 2018 at 11:08 PM, Dale wrote:
> >> J. Roeleveld wrote:
> >>> Sounds like a bug.
> >>> All fetch restriction packages I encounter want it in your distfiles
> >>> folder. (Wherever you configured it to be)
> >>>
R0b0t1 wrote:
> On Tue, Apr 10, 2018 at 11:08 PM, Dale wrote:
>> J. Roeleveld wrote:
>>> Sounds like a bug.
>>> All fetch restriction packages I encounter want it in your distfiles
>>> folder. (Wherever you configured it to be)
>>>
>>> I haven't really read the text on these myself lately, so not
On Tue, Apr 10, 2018 at 11:08 PM, Dale wrote:
> J. Roeleveld wrote:
>>
>> Sounds like a bug.
>> All fetch restriction packages I encounter want it in your distfiles folder.
>> (Wherever you configured it to be)
>>
>> I haven't really read the text on these myself lately, so not sure if other
>>
J. Roeleveld wrote:
>
> Sounds like a bug.
> All fetch restriction packages I encounter want it in your distfiles folder.
> (Wherever you configured it to be)
>
> I haven't really read the text on these myself lately, so not sure if other
> packages have the same, but I didn't notice any path oth
On April 10, 2018 8:23:46 PM UTC, Ian Zimmerman wrote:
>When I do emerge dev-java/oracle-jre-bin, portage quoth:
>
>!!! dev-java/oracle-jre-bin-1.8.0.162-r1 has fetch restriction turned
>on.
>!!! This probably means that this ebuild's files must be downloaded
>!!! manually. See the comments in th
On Tuesday, 10 April 2018 21:23:46 BST Ian Zimmerman wrote:
> When I do emerge dev-java/oracle-jre-bin, portage quoth:
>
> !!! dev-java/oracle-jre-bin-1.8.0.162-r1 has fetch restriction turned on.
> !!! This probably means that this ebuild's files must be downloaded
> !!! manually. See the commen
Ian Zimmerman wrote:
> When I do emerge dev-java/oracle-jre-bin, portage quoth:
>
> !!! dev-java/oracle-jre-bin-1.8.0.162-r1 has fetch restriction turned on.
> !!! This probably means that this ebuild's files must be downloaded
> !!! manually. See the comments in the ebuild for more information.
>
When I do emerge dev-java/oracle-jre-bin, portage quoth:
!!! dev-java/oracle-jre-bin-1.8.0.162-r1 has fetch restriction turned on.
!!! This probably means that this ebuild's files must be downloaded
!!! manually. See the comments in the ebuild for more information.
* Fetch failed for 'dev-java/
11 matches
Mail list logo
