Your message dated Wed, 27 Nov 2019 17:30:14 +0300 with message-id <20191127143014.GA12815@mitya57.me> and subject line Re: Bug#945554: Qt5: link against OpenSSL at compile-time has caused the Debian Bug report #945554, regarding Qt5: link against OpenSSL at compile-time 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 owner@bugs.debian.org immediately.) -- 945554: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945554 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: <submit@bugs.debian.org>
- Subject: Qt5: link against OpenSSL at compile-time
- From: Jan Nordholz <j.nordholz@tu-berlin.de>
- Date: Tue, 26 Nov 2019 21:19:21 +0100
- Message-id: <[🔎] 20191126201921.GB5803@inti>
Source: qtbase-opensource-src Severity: normal Version: 5.12.5+dfsg-2 Hi, is there a reason that Debian's distribution package is *not* using the build flag "-openssl-linked" to create a proper DT_NEEDED dependency at compile-time? (Couldn't find anything in the archived bugreports, sorry if this is reopening a can of worms.) The benefits of this flag seem to me: * minimal user surprise: the established mechanisms of library dependency lookup work for Qt as they do for everything else * less code duplication: Qt is effectively reimplementing a subset of ld.so's functionality (with a few provisions to cope with slightly different versions of OpenSSL, if my impression of that code is correct) * the dependency is automatically picked up by dh_* and thrown into ${shlibs:Depends}, no manual tracking necessary In the current state libqt5network5 already depends on libssl1.1 anyway, so we know what library will be "dynamically discovered" by Qt (i.e. we don't need the multi-version compatibility support Qt offers) - it's just harder to interpose the process if you want to, and it throws away the opportunity to use our existing tooling. See this Fedora report (esp. the last comments) for another community having gone through the same discussion[1]. Best regards Jan [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1328659
--- End Message ---
--- Begin Message ---
- To: 945554-close@bugs.debian.org
- Subject: Re: Bug#945554: Qt5: link against OpenSSL at compile-time
- From: Dmitry Shachnev <mitya57@debian.org>
- Date: Wed, 27 Nov 2019 17:30:14 +0300
- Message-id: <20191127143014.GA12815@mitya57.me>
- In-reply-to: <[🔎] 3136504.IFfzfPSMIy@dabney>
- References: <[🔎] 20191126201921.GB5803@inti> <[🔎] 20191126201921.GB5803@inti> <[🔎] 3136504.IFfzfPSMIy@dabney>
On Tue, Nov 26, 2019 at 09:33:20PM +0100, Sune Stolborg Vuorela wrote: > On Tuesday, November 26, 2019 9:19:21 PM CET Jan Nordholz wrote: > > is there a reason that Debian's distribution package is *not* using the > > build flag "-openssl-linked" to create a proper DT_NEEDED dependency at > > compile-time? (Couldn't find anything in the archived bugreports, sorry if > > this is reopening a can of worms.) > > Yes. the gpl versions are incompatible with openssl, so that would require all > users of the non-ssl using parts of qtnetwork to also have openssl exceptions. > > This way, only the applications actually requiring it requires the exception. So I am closing the bug. Thanks Sune for replying! -- Dmitry ShachnevAttachment: signature.asc
Description: PGP signature
--- End Message ---