Re: Advice for building tomcat8 on jessie?
- To: Emmanuel Bourg <ebourg@apache.org>, Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>, tony mancill <tmancill@debian.org>, Jakub Adam <jakub.adam@ktknet.cz>, debian-lts@lists.debian.org
- Subject: Re: Advice for building tomcat8 on jessie?
- From: Roberto C. Sánchez <roberto@debian.org>
- Date: Sun, 8 Jul 2018 16:18:31 -0400
- Message-id: <[🔎] 20180708201831.fbv36ztcsh3k2kf6@connexer.com>
- Mail-followup-to: Roberto C. Sánchez <roberto@debian.org>, Emmanuel Bourg <ebourg@apache.org>, Debian Java Maintainers <pkg-java-maintainers@lists.alioth.debian.org>, tony mancill <tmancill@debian.org>, Jakub Adam <jakub.adam@ktknet.cz>, debian-lts@lists.debian.org
- In-reply-to: <[🔎] 20180705134040.ubrbbuu47jqil4zz@connexer.com>
- References: <20180630180936.3ijoslv7gdjzofdn@connexer.com> <[🔎] 0121c995-6762-8378-2d8c-14dbd8b27d98@apache.org> <[🔎] 20180705134040.ubrbbuu47jqil4zz@connexer.com>
On Thu, Jul 05, 2018 at 09:40:40AM -0400, Roberto C. Sánchez wrote:
> On Tue, Jul 03, 2018 at 11:40:05PM +0200, Emmanuel Bourg wrote:
> > Le 30/06/2018 à 20:09, Roberto C. Sánchez a écrit :
> >
> > > I would very much appreciate your guidance on this so that I can get
> > > tomcat8 in jessie updated.
> >
> > Hi Roberto,
> >
> > Thank a lot for helping with the Tomcat maintenance. The error probably
> > comes from an expired test certificate or a change in OpenSSL. Try
> > building the package locally without pbuilder and inspect the test logs
> > generated in the output directory. You should get a good indication of
> > the cause of this error. Note that you can build the package and run
> > only one test by adding -Dtest.name=**/TestWebSocketFrameClientSSL*
> > after the "ant test" invocation in debian/rules. That should speed up
> > your investigations.
> >
> Hi Emmanuel,
>
> The SSL certificate expiration was exactly the problem. I have updated
> them from the latest available in the upstream sources and am presently
> running another build.
>
It turns out that build ended up failing. (I meant to ping back as soon
as it had completed, but I did not get around to it.) I tried a build
of the current version (8.0.14-1+deb8u11) with test SSL certificates
updated from upstream, and that build failed as well. A total of 12
unit tests failed.
This makes me wonder if I am missing something. I can understand the
SSL certificate expiry preventing a rebuild of the package. But I
cannot understand how the build would fail otherwise. I will dig into
the test failures tonight, but I would appreciate any thoughts on what
might be going wrong.
Regards,
-Roberto
--
Roberto C. Sánchez
Reply to: