The issue was resolved with libqt5network5_5.11.1+dfsg-8_amd64.deb
Dear OpenSSL+Qt Sirs,
I'm posting to both mailing lists at once because I don't know where
to start. I have a Qt app (classified-ads) that uses QSslSocket that
internally uses OpenSSL for its work. This is a p2p-app where program
instances communicate with each others. I have an up-to-date
On Tue, Sep 11, 2018 at 10:43:26PM +0300, Antti Järvinen wrote:
> Dear OpenSSL+Qt Sirs,
Please try 5.11.1+dfsg-8.
Kurt
On 2018-09-11 22:43:26 [+0300], Antti Järvinen wrote:
> buster where this app was still working on Sunday 9th september. On
> 10th apt upgraded libqt5network5:amd64 from 5.11.1+dfsg-6 to 5.11.1+dfsg-7
does 5.11.1+dfsg-8 work for you?
…
> combination that should work? The nodes in the network
On 2018-09-11 16:11:02 [+0300], Adrian Bunk wrote:
> Dmitry already implemented my short-term workaround:
> https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/
>
> When this has been built on all release architectures openssl can bump
> the
Dear all,
On 09-09-18 22:04, Paul Gevers wrote:
> On 09/06/18 21:13, Paul Gevers wrote:
>> So it seems they are requested by something, and because the are not
>> available in testing, apt-get is not limited by our pinning to take them
>> from unstable. I believe it must be a "Provides" of some
On Tue, Sep 11, 2018 at 07:18:28PM +0200, Kurt Roeckx wrote:
> > > If this is for a call to SSL_CTX_set_max_proto_version(), you can
> > > use 0 instead of TLS_MAX_VERSION.
> >
> > Good point, thanks.
> >
> > However as the patch is temporary, I do not think it is worth
> > a new upload to change
On Tue, Sep 11, 2018 at 08:14:35PM +0300, Dmitry Shachnev wrote:
> Hi Kurt,
>
> On Tue, Sep 11, 2018 at 07:09:04PM +0200, Kurt Roeckx wrote:
> > If this is for a call to SSL_CTX_set_max_proto_version(), you can
> > use 0 instead of TLS_MAX_VERSION.
>
> Good point, thanks.
>
> However as the
Hi Kurt,
On Tue, Sep 11, 2018 at 07:09:04PM +0200, Kurt Roeckx wrote:
> If this is for a call to SSL_CTX_set_max_proto_version(), you can
> use 0 instead of TLS_MAX_VERSION.
Good point, thanks.
However as the patch is temporary, I do not think it is worth
a new upload to change that.
--
Dmitry
On Tue, Sep 11, 2018 at 04:11:02PM +0300, Adrian Bunk wrote:
>
> Dmitry already implemented my short-term workaround:
> https://tracker.debian.org/news/986618/accepted-qtbase-opensource-src-5111dfsg-8-source-into-unstable/
If this is for a call to SSL_CTX_set_max_proto_version(), you can
use 0
Source: qtbase-opensource-src
Version: 5.11.1+dfsg-8
In my today’s upload I added a patch named ssl_max_version.diff.
It is a temporary measure to support running against OpenSSL 1.1.0
(in testing) when building against OpenSSL 1.1.1 (in unstable).
When OpenSSL 1.1.1 migrates, we should drop
On Tue, 11 Sep 2018 at 09:00, Jan-Marek Glogowski wrote:
> Am 11.09.2018 um 11:57 schrieb Adrian Bunk:
>
>
> Qt5 is just the first breaking package - I have no idea, how many packages
> use TLS_MAX_VERSION in
> their code.
Only a handful according to
Package: kdelibs5-data
Version: 4:4.14.2-5+deb8u2
Severity: normal
Upon launching Akregator in the Kontact application, "HTTP Cache Cleaner"
starts up with the bouncing notifier cursor and a window entry in the taskbar.
Also plasma-desktop starts running more excitedly. This can be quite
On Tue, Sep 11, 2018 at 02:57:17PM +0200, Sebastian Andrzej Siewior wrote:
> On 2018-09-11 12:57:17 [+0300], Adrian Bunk wrote:
> > > I'm on buster and with the latest updates from yesterday came
> > > qtbase-opensource-src 5.11.1+dfsg-7
> > > and SSL started to fail in Qt5 programs. This was
On 2018-09-11 12:57:17 [+0300], Adrian Bunk wrote:
> > I'm on buster and with the latest updates from yesterday came
> > qtbase-opensource-src 5.11.1+dfsg-7
> > and SSL started to fail in Qt5 programs. This was reported in bug 907774 ~
> > 2 weeks ago.
> >
> > Basically libssl 1.1.1 (in
Am 11.09.2018 um 11:57 schrieb Adrian Bunk:
>> Basically libssl 1.1.1 (in whatever 1.1.1 version - my guess is
>> 1.1.1~~pre9-1 from the changelog)
>> changed the definition of TLS_MAX_VERSION from TLS1_2_VERSION to
>> TLS1_3_VERSION, which will start to
>> break all software in buster using
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Tue, 11 Sep 2018 13:29:28 +0300
Source: qtbase-opensource-src
Binary: libqt5core5a libqt5gui5 qt5-gtk-platformtheme qt5-flatpak-platformtheme
libqt5network5 libqt5opengl5 libqt5sql5 libqt5sql5-mysql libqt5sql5-odbc
qtbase-opensource-src_5.11.1+dfsg-8_source.changes uploaded successfully to
localhost
along with the files:
qtbase-opensource-src_5.11.1+dfsg-8.dsc
qtbase-opensource-src_5.11.1+dfsg-8.debian.tar.xz
qtbase-opensource-src_5.11.1+dfsg-8_source.buildinfo
Greetings,
Your Debian queue
Your message dated Tue, 11 Sep 2018 10:50:07 +
with message-id
and subject line Bug#908328: fixed in qtbase-opensource-src 5.11.1+dfsg-8
has caused the Debian Bug report #908328,
regarding qtbase5-doc-html: Class docs are missing in 5.11.1+dfsg-7
to be marked as done.
This means that you
Your message dated Tue, 11 Sep 2018 10:50:07 +
with message-id
and subject line Bug#907774: fixed in qtbase-opensource-src 5.11.1+dfsg-8
has caused the Debian Bug report #907774,
regarding Error while setting the maximum protocol version
to be marked as done.
This means that you claim that
Your message dated Tue, 11 Sep 2018 10:50:07 +
with message-id
and subject line Bug#907774: fixed in qtbase-opensource-src 5.11.1+dfsg-8
has caused the Debian Bug report #907774,
regarding [libqt5network5] Requires openssl >= 1.1.1
to be marked as done.
This means that you claim that the
Control: severity 908567 serious
Control: severity 907774 serious
Control: block 907774 by 908567
On Tue, Sep 11, 2018 at 11:00:00AM +0200, Jan-Marek Glogowski wrote:
> Package: libssl1.1
> Version: 1.1.1~~pre9-1
> Severity: important
>
> I'm on buster and with the latest updates from yesterday
Processing control commands:
> severity 908567 serious
Bug #908567 [libssl1.1] libssl 1.1.1 TLS_MAX_VERSION ABI breakage
Severity set to 'serious' from 'important'
> severity 907774 serious
Bug #907774 [libqt5network5] [libqt5network5] Requires openssl >= 1.1.1
Bug #908557 [libqt5network5] Error
Processing control commands:
> severity 908567 serious
Bug #908567 [libssl1.1] libssl 1.1.1 TLS_MAX_VERSION ABI breakage
Ignoring request to change severity of Bug 908567 to the same value.
> severity 907774 serious
Bug #907774 [libqt5network5] [libqt5network5] Requires openssl >= 1.1.1
Bug
Processing commands for cont...@bugs.debian.org:
> severity 908557 important
Bug #908557 [qtbase-opensource-src] Error while setting the maximum protocol
version
Severity set to 'important' from 'normal'
> reassign 908557 libqt5network5
Bug #908557 [qtbase-opensource-src] Error while setting the
Your message dated Tue, 11 Sep 2018 10:38:41 +0300
with message-id <20180911073841.ga2...@mitya57.me>
and subject line Re: Bug#908558: qttools5-dev-tools: Missing cmake files in
package
has caused the Debian Bug report #908558,
regarding qttools5-dev-tools: Missing cmake files in package
to be
Package: qttools5-dev-tools
Version: 5.11.1-5
Severity: important
Dear Maintainer,
https://packages.debian.org/buster/amd64/qttools5-dev-tools/filelist
says that there should be
/usr/lib/x86_64-linux-gnu/cmake/Qt5LinguistTools/*.cmake files.
But there are no such files:
$ dpkg -l
Package: qtbase-opensource-src
Version: 5.11.1+dfsg-7
Severity: normal
My Debian Buster installation of the Quassel client (version 0.12.5)
fails to connect with the message "Error while setting the maximum
protocol version". I verified with Wireshark that my Linux client is
actually
28 matches
Mail list logo
