Bug#856984: fis-gtm: please enable openssl support
Hi Sebastian, From: Sebastian Andrzej Siewior [mailto:sebast...@breakpoint.cc] Sent: Thursday, December 14, 2017 9:08 AM On 2017-12-13 08:33:02 [+0100], Andreas Tille wrote: >> On Wed, Mar 29, 2017 at 08:50:57PM +, Shah, Amul wrote: > somehow this email never reached me or I skipped it by accident. [amul] I blame the Outlook formatting! It would make anyone not want to read email! ;) >> > If I understood your question correctly, you are asking for the fis-gtm >> > package to either enable openssl OR drop the libssl-dev requirement. >> > >> > We dropped the openssl using encryption plugin libraries from the >> > distributed package because of the "openssl advertising clause". To work >> > around the advertising clause, we distribute our encryption plugin >> > libraries as source, letting the end users that desire encryption support >> > compile it for themselves. So we can't enable openssl. >> > >> > The fis-gtm package builds the encryption plugin sources as a >> > compatibility test build. That compatibility test build alerted us to the >> > upcoming changes in openssl 1.1. So we won't drop the libssl-dev >> > requirement. >> > >> > If the above makes sense, I would like to close this bug. If you have some >> > other option, let me know. > >That makes sense. I wanted to ensure that you don't depend on it for no reason >or that openssl support is disabled because the new openssl is not properly >detected (we had both cases it the past). If I remember correctly, then I >could not find a difference to build and without libssl-dev and the changelog >said that encryption was temporary disabled (or something like that). [amul] Understood and I agree with your stance. There is no need for dependencies that get in the way of moving forward. >If you are saying that as part of the build process you do use openssl and >that the build would fail if the openssl library would have changed/ became >incompatible for the source you distribute then this is fine. [amul] That is what I am saying. Can we close this bug? Thanks - Amul The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Bug#856984: fis-gtm: please enable openssl support
On 2017-12-13 08:33:02 [+0100], Andreas Tille wrote: > Hi Sebastian, Hi Andreas, > it would be nice if you could answer the question below. Otherwise > we would set the bug to wontfix for the moment. somehow this email never reached me or I skipped it by accident. > Thank you > > Andreas. > > On Wed, Mar 29, 2017 at 08:50:57PM +, Shah, Amul wrote: > > If I understood your question correctly, you are asking for the fis-gtm > > package to either enable openssl OR drop the libssl-dev requirement. > > > > We dropped the openssl using encryption plugin libraries from the > > distributed package because of the "openssl advertising clause". To work > > around the advertising clause, we distribute our encryption plugin > > libraries as source, letting the end users that desire encryption support > > compile it for themselves. So we can't enable openssl. > > > > The fis-gtm package builds the encryption plugin sources as a compatibility > > test build. That compatibility test build alerted us to the upcoming > > changes in openssl 1.1. So we won't drop the libssl-dev requirement. > > > > If the above makes sense, I would like to close this bug. If you have some > > other option, let me know. That makes sense. I wanted to ensure that you don't depend on it for no reason or that openssl support is disabled because the new openssl is not properly detected (we had both cases it the past). If I remember correctly, then I could not find a difference to build and without libssl-dev and the changelog said that encryption was temporary disabled (or something like that). If you are saying that as part of the build process you do use openssl and that the build would fail if the openssl library would have changed/ became incompatible for the source you distribute then this is fine. > > > > Thanks, > > Amul Sebastian
Bug#856984: fis-gtm: please enable openssl support
Hi Sebastian, it would be nice if you could answer the question below. Otherwise we would set the bug to wontfix for the moment. Thank you Andreas. On Wed, Mar 29, 2017 at 08:50:57PM +, Shah, Amul wrote: > If I understood your question correctly, you are asking for the fis-gtm > package to either enable openssl OR drop the libssl-dev requirement. > > We dropped the openssl using encryption plugin libraries from the distributed > package because of the "openssl advertising clause". To work around the > advertising clause, we distribute our encryption plugin libraries as source, > letting the end users that desire encryption support compile it for > themselves. So we can't enable openssl. > > The fis-gtm package builds the encryption plugin sources as a compatibility > test build. That compatibility test build alerted us to the upcoming changes > in openssl 1.1. So we won't drop the libssl-dev requirement. > > If the above makes sense, I would like to close this bug. If you have some > other option, let me know. > > Thanks, > Amul > > The information contained in this message is proprietary and/or confidential. > If you are not the intended recipient, please: (i) delete the message and all > copies; (ii) do not disclose, distribute or use the message in any manner; > and (iii) notify the sender immediately. In addition, please be aware that > any message addressed to our domain is subject to archiving and review by > persons other than the intended recipient. Thank you. > > ___ > Debian-med-packaging mailing list > debian-med-packag...@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-med-packaging > -- http://fam-tille.de
Bug#856984: fis-gtm: please enable openssl support
If I understood your question correctly, you are asking for the fis-gtm package to either enable openssl OR drop the libssl-dev requirement. We dropped the openssl using encryption plugin libraries from the distributed package because of the "openssl advertising clause". To work around the advertising clause, we distribute our encryption plugin libraries as source, letting the end users that desire encryption support compile it for themselves. So we can't enable openssl. The fis-gtm package builds the encryption plugin sources as a compatibility test build. That compatibility test build alerted us to the upcoming changes in openssl 1.1. So we won't drop the libssl-dev requirement. If the above makes sense, I would like to close this bug. If you have some other option, let me know. Thanks, Amul The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.
Bug#856984: fis-gtm: please enable openssl support
Package: fis-gtm Version: 6.3-000A-1 Severity: normal User: pkg-openssl-de...@lists.alioth.debian.org Usertags: openssl-1.1-trans I don't really have an idea what this package does and how important is the lack of openssl support. As far as I can tell 6.2 did not depend on libssl so it is probably no regression commpared to current stable. There is a patch "upstream_encryption_libs_openssl110_compatible" which looks like it would fix the openssl 1.1 issue which was added after the #828300 was closed which disabled ssl support. The release team said that no package should suffer from the openssl transition so I *think* it would be okay to get a new version with enabled openssl support in testing. If this is not important enough, then please close this bug post Stretch by either enabling openssl support or dropping the libssl-dev B-D. Little side note: The resulting deb file also contains source code + source.tar in /usr/lib/$ARCH/fis-gtm/V6.3-000A_x86_64/plugin/gtmcrypt/ of which I am not sure if this is on purpose or not. Sebastian
