Advice for building tomcat8 on jessie?

[tony mancill]

On Sun, Jul 22, 2018 at 11:09:06PM -0400, Roberto C. Sánchez wrote:
> On Thu, Jul 19, 2018 at 10:35:50PM -0700, tony mancill wrote:
> > Hi Roberto,
> > 
> > I was able to build your jessie branch in clean jessie chroot without
> > any problems.  I use sbuild on amd64.  It took about 50 minutes:
> > 
> 
> Hi Tony &co.,
> 
> I feel like after spending an unreasonable amount of time trying to
> determine the reason for the failure to build on my system that I cannot
> come up with a reasonable theory for the failure.  At this point,
> further investigation does not seem likely to be productive on my end it
> will only continue delaying the security update for users of tomcat8 in
> jessie.
> 
> As I am not comfortable uploading a package that does not build, could I
> trouble you to build the package and upload it for me?  The upload would
> need to go to security-master and once the ACCEPT comes back from the
> archive software I would release the security advisory (I have already
> prepared the text).  I have made the necessary commits and pushed them
> to my fork on salsa.  Since you are able to build on your system, you
> should only need to pull, build, sign, and upload.
> 
> Please let me know if you would be albe to assist with this.

Hello Roberto,

Yes, I can help with this.  As an additional step before the upload, it
is probably prudent to do some smoke-testing with the built package.  I
will get it built this evening and then share a link to the build.

Cheers,
tony
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-maintainers/attachments/20180724/ed4107ed/attachment-0001.sig>