On Sun, Jun 26, 2016 at 06:03:15PM +0200, Sebastiaan Couwenberg wrote: > Control: tags -1 unreproducible moreinfo > > Hi Kurt, > > Thanks for your work on OpenSSL. > > On 06/26/2016 12:23 PM, Kurt Roeckx wrote: > > 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/postgis_2.2.2+dfsg-2_amd64-20160529-1510 > > postgis has no direct dependency on libssl nor libcrypto. There is no > clear openssl related failure in the buildlog, but it does show that it > only installs the custom openssl dependencies and relies on unstable for > the rest of the packages. So none of postgis build dependencies have > been rebuilt with the new openssl packages. I suspect this issue is > caused by postgres still linking to the old openssl whereas the new > openssl is installed in the build environment. > > > 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. > > postgis is not among the reverse dependencies for openssl in the > auto-openssl transition tracker [0], so I guess postgis was only rebuilt > for your tests because it build depends on libssl-dev. > > I cannot reproduce the issue with the libssl-dev from experimental, so > I'm starting to suspect this issue is a false positive. > > Can you confirm that the openssl update to 1.1.0 only affects packaging > linking its libssl and/or libcrypto?
Only packages linking to libssl/libcrypto should be affected. I'm not sure why you build depend on libssl if you don't. Anyway, if you can't reproduce this, feel free to close it. Kurt