Bug#609886: libapache2-mod-jk: After upgrade from 1.2.26 to 1.2.30 mod_jk no longer connects to tomcats

Vamegh Hedayati vamegh at gmail.com
Sun Feb 6 03:49:23 UTC 2011


Hi,

I did the same test as Nelson above, but I built on my laptop which
runs kubuntu 10.10, obviously not Debian.. The packages I built didn't
work, my server is running Debian though. I did notice the following
build dependency:

apt-file search /usr/bin/apxs2
apache2-prefork-dev: /usr/bin/apxs2
apache2-threaded-dev: /usr/bin/apxs2

I tried using them each for build-dependency made no difference didn't
work, something to do with the Ubuntu build process for me possibly ?
Either way it was a bad test and I couldnt be bothered setting up a
debian vm to test it further.

Miguel I have set you up a test domu, which is practically identical
to my actual server, you can use it for testing. I will email you the
details now.

All the best,

Vamegh


On 4 February 2011 22:57, Vamegh Hedayati <vamegh at gmail.com> wrote:
> Hi,
>
> I was also just testing it, all combinations I tried didn't work with
> the built package you provided.  Miguel do you want access into my
> server, just so you can verify ? I should also note my server is a xen
> domu, but that should make absolutely no difference.
>
> I will also try compiling it / building my own package and will let
> you know if that works for me also.
>
> All the best,
>
>
> Vamegh
>
> On 4 February 2011 22:49, Nelson Lago <nelson.lago at gmail.com> wrote:
>> On Fri, Feb 4, 2011 at 7:39 PM, Miguel Landaeta <miguel at miguel.cc> wrote:
>>> I prepared a new package for 1.2.31.
>>> Would you please test it?
>>
>> Your binary package itself did not work, BUT I took your sources and
>> created a debian package myself, and it works!
>>
>> I downloaded the files:
>>
>> libapache-mod-jk_1.2.31-0miguel1.dsc
>> libapache-mod-jk_1.2.31-0miguel1.debian.tar.gz
>> libapache-mod-jk_1.2.31.orig.tar.gz
>>
>> Then
>>
>> dpkg-source -x libapache-mod-jk_1.2.31-0miguel1.dsc
>>
>> then debian/rules binary
>>
>> I really do not understand why this happens, though. If the only
>> important difference here was the OpenVZ kernel, how would this
>> influence the compilation?
>>
>> If you also do not know what is going on, maybe this should be brought
>> to the attention of the mainstream authors.
>>
>





More information about the pkg-java-maintainers mailing list