> Diablo-1.5 does not work anymore (it is neither in the ports dir and if
installed
> manually it does not find /bin/libz.so.3 - the diable-jdk 1.5 is simply
> outdated):
>
> [hudson@lucene /]$ /usr/local/diablo-jdk1.5.0/bin/java
> /libexec/ld-elf.so.1: Shared object "libz.so.3" not found, require
That's because the moderators suck.
- Original Message
> From: Uwe Schindler
> To: builds@apache.org
> Sent: Tue, March 8, 2011 7:36:40 PM
> Subject: RE: Lucene slave [was: Re: Jenkins failure?]
>
> Hi again,
>
> > Your pmc was notified yesterday of the upgrade
>
> I am in the PMC,
Hi again,
> Your pmc was notified yesterday of the upgrade
I am in the PMC, but no mail was received on priv...@lucene.apache.org
yesterday.
Uwe
Hi,
Diablo-1.5 does not work anymore (it is neither in the ports dir and if
installed manually it does not find /bin/libz.so.3 - the diable-jdk 1.5 is
simply outdated):
[hudson@lucene /]$ /usr/local/diablo-jdk1.5.0/bin/java
/libexec/ld-elf.so.1: Shared object "libz.so.3" not found, required by
"j
Your pmc was notified yesterday of the upgrade. I have no idea why
you didn't just run
% pkg_add -r diablo-jdk15
% pkg_add -r diablo-jdk16
to pull in the missing ports, but I've gone ahead and done that now.
- Original Message
> From: Uwe Schindler
> To: builds@apache.org
> Sent: Tue
Hi Niklas,
since the upgrade the whole Lucene Build is broken (unfixable). We need JDK
1.5 to test our dependencies during compiling - this is gone after update
and is now uninstallable in FreeBSD latest version (neither Diablo nor any
other jdk can be installed anymore). I was able to install ope
On Tue, Mar 8, 2011 at 10:09 PM, Uwe Schindler wrote:
> Thanks, I will take care and place a link to the correct jdk in usr/local.
> Should it start automatically?
Ping me when you're done.
/niklas
Thanks, I will take care and place a link to the correct jdk in usr/local.
Should it start automatically?
--
Uwe Schindler
H.-H.-Meier-Allee 63, 28213 Bremen
http://www.thetaphi.de
Niklas Gustavsson schrieb:
On Tue, Mar 8, 2011 at 9:55 PM, Uwe Schindler wrote: > Could
you also restart the L
On Tue, Mar 8, 2011 at 9:55 PM, Uwe Schindler wrote:
> Could you also restart the Lucene slave? I cannot do this through
> webinterface (no admin rights). The machine is up and running; but the
> message in the webinterface is unclear, Hudson should be able to start the
> slave.
I'm guessing the
Hi Niklas,
Could you also restart the Lucene slave? I cannot do this through
webinterface (no admin rights). The machine is up and running; but the
message in the webinterface is unclear, Hudson should be able to start the
slave.
Uwe
-
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http:
On Tue, Mar 8, 2011 at 8:37 PM, Kristian Waagan
wrote:
> I got the error again right now (after you restarted the slave) for the
> Derby-trunk job, still on ubuntu1.
> Saw it twice; one SCM triggered build and one manually started.
Restarted again. No idea what causes this slave to behave like th
On 08.03.11 07:16, Niklas Gustavsson wrote:
On Mon, Mar 7, 2011 at 10:55 PM, Marshall Schor wrote:
The lines added look to be correct, but after this, we started getting this
failure report. I don't know what caused the user "SYSTEM" to add this. I
don't see any configuration for the rootModu
12 matches
Mail list logo
