Your message dated Sun, 28 Aug 2016 13:50:06 +0200
with message-id <[email protected]>
and subject line Re: Bug#828575: Acknowledgement (tomcat-native: FTBFS with
openssl 1.1.0)
has caused the Debian Bug report #828575,
regarding tomcat-native: FTBFS with openssl 1.1.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
828575: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828575
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: tomcat-native
Version: 1.2.7-1
Severity: important
Control: block 827061 by -1
Hi,
OpenSSL 1.1.0 is about to released. During a rebuild of all packages using
OpenSSL this package fail to build. A log of that build can be found at:
https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/tomcat-native_1.2.7-1_amd64-20160529-1545
On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the
reasons why it might fail. There are also updated man pages at
https://www.openssl.org/docs/manmaster/ that should contain useful information.
There is a libssl-dev package available in experimental that contains a recent
snapshot, I suggest you try building against that to see if everything works.
If you have problems making things work, feel free to contact us.
Kurt
--- End Message ---
--- Begin Message ---
Version: 1.2.8-1
This seems to have been fixed in the new upstream version:
https://breakpoint.cc/openssl-1.1-rebuild-2016-08-26/successful/tomcat-native_1.2.8-1_amd64-2016-08-26T19%3A53%3A54Z
Kurt
--- End Message ---
__
This is the maintainer address of Debian's Java team
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
[email protected] for discussions and questions.
