So I see that the jdk-1.6 port has been marked as broken, unfortunately,
only after upgrading to the latest snapshot (i386).
Might anyone have any idea when this will be working again?
Many thanks in advance.
On Tue, Dec 31, 2013 at 12:14:26PM -0800, Scott Vanderbilt wrote:
> So I see that the jdk-1.6 port has been marked as broken,
> unfortunately, only after upgrading to the latest snapshot (i386).
>
> Might anyone have any idea when this will be working again?
No. It's actually been broken for a wh
On 1/1/2014 6:41 AM, Marc Espie wrote:
On Tue, Dec 31, 2013 at 12:14:26PM -0800, Scott Vanderbilt wrote:
So I see that the jdk-1.6 port has been marked as broken,
unfortunately, only after upgrading to the latest snapshot (i386).
Might anyone have any idea when this will be working again?
No
> While I have no doubt the port may have been broken for some time, it
> was working reliably in my particular use case as of the Dec. 7
> snapshot. (I'm running Apache Solr 4.6.) It was only after I updated to
> the Dec. 28 snapshot that the breakage manifested itself.
>
> Following up on you
On 1/1/2014 10:00 AM, Ian Darwin wrote:
Given that Java 6 has been EOL'd by Oracle for almost a year (Feb 2013,
as announced in Feb 2011), and it's on an operating system they
don't even know about, your bug report will most likely be ignored.
Sorry you wasted time there.
Given the situation wi
On 2014/01/01 10:11, Scott Vanderbilt wrote:
> On 1/1/2014 10:00 AM, Ian Darwin wrote:
>
> >Given that Java 6 has been EOL'd by Oracle for almost a year (Feb 2013,
> >as announced in Feb 2011), and it's on an operating system they
> >don't even know about, your bug report will most likely be ignor
On 1/1/2014 1:21 PM, Stuart Henderson wrote:
If anyone is able to help track down the timeframe this got broken
(or even pin it to a particular commit in base), that would be
extremely helpful...
I was previously running a snapshot from Dec. 7 that did not exhibit the
error. Sorry I can't be
I'm in the same boat as Scott (running jdk-1.7.0.21v0 on i386 that now
fails with thread error mentioned after upgrading to the Dec. 28
snapshots). I was previously running a snapshot from October so I doubt
that helps all that much, but I thought I'd toss it out there.
I'd sure like to get my Tom
On 1/1/2014 1:21 PM, Stuart Henderson wrote:
Your current options are:
- move to amd64.
- move back to code from a month or two ago.
If anyone is able to help track down the timeframe this got broken
(or even pin it to a particular commit in base), that would be
extremely helpful...
I hav
