Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Sylvestre Ledru]

Hello,

There is no need to dump the abi as we are back where we were before.

Sylvestre


Le dim. 13 janv. 2019 à 09:31, Roman Lebedev  a
écrit :

> On Thu, Dec 27, 2018 at 12:52 AM Sylvestre Ledru  wrote:
> >
> >
> > Le 26/12/2018 à 21:30, Lisandro Damián Nicanor Pérez Meyer a écrit :
> > >
> > > Sylvestre: if I understand correctly (please correct me if I am wrong)
> > > you broke ABI without a transition. That's simply not good, you should
> > > now rebuild all rdeps. After the Qt transition is over, of course.
> >
> > This was a bug of clang. Fixed since then.
> >
> > I guess qtcreator was built with the incorrect version of the
> > llvm-toolchain-7.
> Presently, with qtcreator 4.8.0-1, this issue is gone,
> although i guess the LLVM packages still needs to bump the ABI?
>
> > S
> Roman.
>

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Roman Lebedev]

On Thu, Dec 27, 2018 at 12:52 AM Sylvestre Ledru  wrote:
>
>
> Le 26/12/2018 à 21:30, Lisandro Damián Nicanor Pérez Meyer a écrit :
> >
> > Sylvestre: if I understand correctly (please correct me if I am wrong)
> > you broke ABI without a transition. That's simply not good, you should
> > now rebuild all rdeps. After the Qt transition is over, of course.
>
> This was a bug of clang. Fixed since then.
>
> I guess qtcreator was built with the incorrect version of the
> llvm-toolchain-7.
Presently, with qtcreator 4.8.0-1, this issue is gone,
although i guess the LLVM packages still needs to bump the ABI?

> S
Roman.

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Sylvestre Ledru]

Le 26/12/2018 à 21:30, Lisandro Damián Nicanor Pérez Meyer a écrit :


Sylvestre: if I understand correctly (please correct me if I am wrong)
you broke ABI without a transition. That's simply not good, you should
now rebuild all rdeps. After the Qt transition is over, of course.


This was a bug of clang. Fixed since then.

I guess qtcreator was built with the incorrect version of the 
llvm-toolchain-7.


S

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Lisandro Damián Nicanor Pérez Meyer]

Hi Roman!

On Wed, 26 Dec 2018 at 17:26, Roman Lebedev  wrote:
[snip]
> BUT there are good news too.
> After installing apt-build, and rebuilding qtcreator, it now works!

Thanks for checking.

> So the package needs to be re-uploaded/rebuilt for this to be fixed.
> While there, maybe upload the 4.8 that is already in
> https://salsa.debian.org/qt-kde-team/qt/qtcreator/commits/master :)

Qt transition has just started, so it will either get uploaded or binNMUed.

Sylvestre: if I understand correctly (please correct me if I am wrong)
you broke ABI without a transition. That's simply not good, you should
now rebuild all rdeps. After the Qt transition is over, of course.

Cheers, Lisandro.

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Roman Lebedev]

On Wed, Dec 26, 2018 at 8:36 PM Roman Lebedev  wrote:
>
> On Wed, Dec 26, 2018 at 8:09 PM Sylvestre Ledru  wrote:
> >
> > Hello,
> Hi.
>
> > Le 18/11/2018 à 20:06, Lisandro Damián Nicanor Pérez Meyer a écrit :
> > > clone 914002 -1
> > > reassign -1 src:llvm-toolchain-7 1:7.0.1~+rc2-4
> > > affects -1 qtcreator
> > > thanks
> > >
> > > El domingo, 18 de noviembre de 2018 10:18:03 -03 Adam Majer escribió:
> > >> On 2018-11-18 12:30 p.m., Roman Lebedev wrote:
> > >>> If kit is clang (tried with both the clang 7, and llvm trunk),
> > >>> the parsing appears to fail, pretty much all the C++ std:: symbols
> > >>> are underscored, and marked as not found.
> > >>>
> > >>> ii  libclang1-71:7.0.1~+rc2-4
> > >> The problem is clang. Clang in Testing works just fine. When I upgraded 
> > >> Qt
> > >> Creator, all is fine. But as soon as clang was updated, it breaks.
> > >> Downgrading to clang 1:7-6 fixes the problem.
> > >>
> > >> Looks like regression caused by clang 1:7.0.1~+rc2-4 and related.
> > > Cloning the bug so. Hope I've got the right bts invocations.
> > >
> > >
> > Could you please have a look with 7.0.1-2 ?
> $ dpkg -l | grep "llvm-7\|qtcreator"
> ii  llvm-71:7.0.1-2
>   amd64Modular compiler and
> toolchain technologies
> ii  llvm-7-dev1:7.0.1-2
>   amd64Modular compiler and
> toolchain technologies, libraries and headers
> ii  llvm-7-runtime1:7.0.1-2
>   amd64Modular compiler and
> toolchain technologies, IR interpreter
> ii  llvm-7-tools  1:7.0.1-2
>   amd64Modular compiler and
> toolchain technologies, tools
> ii  qtcreator 4.7.2-2
>   amd64integrated development
> environment (IDE) for Qt
> ii  qtcreator-data4.7.2-2
>   all  application data for Qt
> Creator IDE
>
> > it should work now.
> Still an issue.
BUT there are good news too.
After installing apt-build, and rebuilding qtcreator, it now works!

So the package needs to be re-uploaded/rebuilt for this to be fixed.
While there, maybe upload the 4.8 that is already in
https://salsa.debian.org/qt-kde-team/qt/qtcreator/commits/master :)

> > Thanks
> >
> > S
Roman.

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Roman Lebedev]

On Wed, Dec 26, 2018 at 8:09 PM Sylvestre Ledru  wrote:
>
> Hello,
Hi.

> Le 18/11/2018 à 20:06, Lisandro Damián Nicanor Pérez Meyer a écrit :
> > clone 914002 -1
> > reassign -1 src:llvm-toolchain-7 1:7.0.1~+rc2-4
> > affects -1 qtcreator
> > thanks
> >
> > El domingo, 18 de noviembre de 2018 10:18:03 -03 Adam Majer escribió:
> >> On 2018-11-18 12:30 p.m., Roman Lebedev wrote:
> >>> If kit is clang (tried with both the clang 7, and llvm trunk),
> >>> the parsing appears to fail, pretty much all the C++ std:: symbols
> >>> are underscored, and marked as not found.
> >>>
> >>> ii  libclang1-71:7.0.1~+rc2-4
> >> The problem is clang. Clang in Testing works just fine. When I upgraded Qt
> >> Creator, all is fine. But as soon as clang was updated, it breaks.
> >> Downgrading to clang 1:7-6 fixes the problem.
> >>
> >> Looks like regression caused by clang 1:7.0.1~+rc2-4 and related.
> > Cloning the bug so. Hope I've got the right bts invocations.
> >
> >
> Could you please have a look with 7.0.1-2 ?
$ dpkg -l | grep "llvm-7\|qtcreator"
ii  llvm-71:7.0.1-2
  amd64Modular compiler and
toolchain technologies
ii  llvm-7-dev1:7.0.1-2
  amd64Modular compiler and
toolchain technologies, libraries and headers
ii  llvm-7-runtime1:7.0.1-2
  amd64Modular compiler and
toolchain technologies, IR interpreter
ii  llvm-7-tools  1:7.0.1-2
  amd64Modular compiler and
toolchain technologies, tools
ii  qtcreator 4.7.2-2
  amd64integrated development
environment (IDE) for Qt
ii  qtcreator-data4.7.2-2
  all  application data for Qt
Creator IDE

> it should work now.
Still an issue.

> Thanks
>
> S
Roman.

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Sylvestre Ledru]

Hello,

Le 18/11/2018 à 20:06, Lisandro Damián Nicanor Pérez Meyer a écrit :

clone 914002 -1
reassign -1 src:llvm-toolchain-7 1:7.0.1~+rc2-4
affects -1 qtcreator
thanks

El domingo, 18 de noviembre de 2018 10:18:03 -03 Adam Majer escribió:

On 2018-11-18 12:30 p.m., Roman Lebedev wrote:

If kit is clang (tried with both the clang 7, and llvm trunk),
the parsing appears to fail, pretty much all the C++ std:: symbols
are underscored, and marked as not found.

ii  libclang1-71:7.0.1~+rc2-4

The problem is clang. Clang in Testing works just fine. When I upgraded Qt
Creator, all is fine. But as soon as clang was updated, it breaks.
Downgrading to clang 1:7-6 fixes the problem.

Looks like regression caused by clang 1:7.0.1~+rc2-4 and related.

Cloning the bug so. Hope I've got the right bts invocations.



Could you please have a look with 7.0.1-2 ?

it should work now.

Thanks

S

Re: Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Lisandro Damián Nicanor Pérez Meyer]

El domingo, 18 de noviembre de 2018 16:45:57 -03 Sylvestre Ledru escribió:
> Le 18/11/2018 à 20:06, Lisandro Damián Nicanor Pérez Meyer a écrit :
> > clone 914002 -1
> > reassign -1 src:llvm-toolchain-7 1:7.0.1~+rc2-4
> > affects -1 qtcreator
> > thanks
> > 
> > El domingo, 18 de noviembre de 2018 10:18:03 -03 Adam Majer escribió:
> >> On 2018-11-18 12:30 p.m., Roman Lebedev wrote:
> >>> If kit is clang (tried with both the clang 7, and llvm trunk),
> >>> the parsing appears to fail, pretty much all the C++ std:: symbols
> >>> are underscored, and marked as not found.
> >>> 
> >>> ii  libclang1-71:7.0.1~+rc2-4
> >> 
> >> The problem is clang. Clang in Testing works just fine. When I upgraded
> >> Qt
> >> Creator, all is fine. But as soon as clang was updated, it breaks.
> >> Downgrading to clang 1:7-6 fixes the problem.
> >> 
> >> Looks like regression caused by clang 1:7.0.1~+rc2-4 and related.
> > 
> > Cloning the bug so. Hope I've got the right bts invocations.
> 
> Can you try if rebuilding qtcreator against this version of clang fixes the
> issue or not?

I personally can't promise it.

I was pointed at:



Is that in the archive already? It might be the cause of this bug.

-- 
A proprietary undocumented text format as the de facto standard -- and that's
what .doc is -- is a shame for all parties involved. It's like using a special
patented ink that can only be read with special patented sun glasses. Who
would want to use that for all their scientific, private and business
documents? Probably nobody. Why they do so with computers is beyond me.
  Matthias Ettrich, founder of the KDE project.
  https://lwn.net/Articles/273715/rss

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Sylvestre Ledru]

Le 18/11/2018 à 20:06, Lisandro Damián Nicanor Pérez Meyer a écrit :
> clone 914002 -1
> reassign -1 src:llvm-toolchain-7 1:7.0.1~+rc2-4
> affects -1 qtcreator
> thanks
> 
> El domingo, 18 de noviembre de 2018 10:18:03 -03 Adam Majer escribió:
>> On 2018-11-18 12:30 p.m., Roman Lebedev wrote:
>>> If kit is clang (tried with both the clang 7, and llvm trunk),
>>> the parsing appears to fail, pretty much all the C++ std:: symbols
>>> are underscored, and marked as not found.
>>>
>>> ii  libclang1-71:7.0.1~+rc2-4
>>
>> The problem is clang. Clang in Testing works just fine. When I upgraded Qt
>> Creator, all is fine. But as soon as clang was updated, it breaks.
>> Downgrading to clang 1:7-6 fixes the problem.
>>
>> Looks like regression caused by clang 1:7.0.1~+rc2-4 and related.
> 
> Cloning the bug so. Hope I've got the right bts invocations.
Can you try if rebuilding qtcreator against this version of clang fixes the 
issue or not?

Thanks
S




signature.asc
Description: OpenPGP digital signature

Processed: Re: Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> clone 914002 -1
Bug #914002 [qtcreator] qtcreator's clang code model appears to be broken with 
kit = clang
Bug 914002 cloned as bug 914042
> reassign -1 src:llvm-toolchain-7 1:7.0.1~+rc2-4
Bug #914042 [qtcreator] qtcreator's clang code model appears to be broken with 
kit = clang
Bug reassigned from package 'qtcreator' to 'src:llvm-toolchain-7'.
No longer marked as found in versions qtcreator/4.7.2-2.
Ignoring request to alter fixed versions of bug #914042 to the same values 
previously set
Bug #914042 [src:llvm-toolchain-7] qtcreator's clang code model appears to be 
broken with kit = clang
Marked as found in versions llvm-toolchain-7/1:7.0.1~+rc2-4.
> affects -1 qtcreator
Bug #914042 [src:llvm-toolchain-7] qtcreator's clang code model appears to be 
broken with kit = clang
Added indication that 914042 affects qtcreator
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
914002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914002
914042: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Lisandro Damián Nicanor Pérez Meyer]

clone 914002 -1
reassign -1 src:llvm-toolchain-7 1:7.0.1~+rc2-4
affects -1 qtcreator
thanks

El domingo, 18 de noviembre de 2018 10:18:03 -03 Adam Majer escribió:
> On 2018-11-18 12:30 p.m., Roman Lebedev wrote:
> > If kit is clang (tried with both the clang 7, and llvm trunk),
> > the parsing appears to fail, pretty much all the C++ std:: symbols
> > are underscored, and marked as not found.
> > 
> > ii  libclang1-71:7.0.1~+rc2-4
> 
> The problem is clang. Clang in Testing works just fine. When I upgraded Qt
> Creator, all is fine. But as soon as clang was updated, it breaks.
> Downgrading to clang 1:7-6 fixes the problem.
> 
> Looks like regression caused by clang 1:7.0.1~+rc2-4 and related.

Cloning the bug so. Hope I've got the right bts invocations.


-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Processed: Re: Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Debian Bug Tracking System]

Processing control commands:

> tag -1 - moreinfo
Bug #914002 [qtcreator] qtcreator's clang code model appears to be broken with 
kit = clang
Removed tag(s) moreinfo.

-- 
914002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 - moreinfo

El domingo, 18 de noviembre de 2018 10:09:59 -03 Roman Lebedev escribió:
[snip]
> > > I can't tell.
> > > I don't remember when it was working for *certain*,
> > > but i think it was working a week ago, and broke before yesterday.
> > 
> > Well, that's an interesting datapoint. I switched qtcreator to use
> > LLVM/clang 7 on 4.7.2-2. Please try installing qtcreator 4.7.2-1 from
> > snapshots.debian.org and see what happens:
> > 
> > 
> > 
> 
> Very interesting. That helped.
> I guess i have mixed up the timeframe, *or* there is something else going
> on.

Sylvestre: this can be either a bug in llvm/clang or qt creator. Of course 
I'll try to see if the bug belongs or not to Qt creator, but if we keep llvm/
clang 6 in the archive I'll probably switch back to if if we can't find a fix.

Cheers, Lisandro.

-- 
¿De qué vive un superamigo? De las regalías de su merchandising, que sólo
puede ser adquirido por burgueses. Como a los burgueses no les agradan las
clases bajas, los superamigos sólo salvan burgueses.
  José Hipólito Moyano - http://bit.ly/fYgbLJ

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Adam Majer]

On 2018-11-18 12:30 p.m., Roman Lebedev wrote:
> If kit is clang (tried with both the clang 7, and llvm trunk),
> the parsing appears to fail, pretty much all the C++ std:: symbols
> are underscored, and marked as not found.

> ii  libclang1-71:7.0.1~+rc2-4


The problem is clang. Clang in Testing works just fine. When I upgraded Qt 
Creator, all is fine. But
as soon as clang was updated, it breaks. Downgrading to clang 1:7-6 fixes the 
problem.

Looks like regression caused by clang 1:7.0.1~+rc2-4 and related.

- Adam

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Roman Lebedev]

On Sun, Nov 18, 2018 at 3:18 PM Lisandro Damián Nicanor Pérez Meyer
 wrote:
>
> Control: tag -1 moreinfo
>
> El domingo, 18 de noviembre de 2018 09:04:27 -03 Roman Lebedev escribió:
> [snip]
> > > clang is now built with clang itself (stage2 build) since 7-5
> > >
> > > Maybe this is the reason!
> >
> > I can't tell.
> > I don't remember when it was working for *certain*,
> > but i think it was working a week ago, and broke before yesterday.
>
> Well, that's an interesting datapoint. I switched qtcreator to use LLVM/clang
> 7 on 4.7.2-2. Please try installing qtcreator 4.7.2-1 from
> snapshots.debian.org and see what happens:
>
>
> 
Very interesting. That helped.
I guess i have mixed up the timeframe, *or* there is something else going on.

> --
> Programming today is a race between software engineers striving to build
> bigger and better idiot-proof programs, and the Universe trying to produce
> bigger and better idiots. So far, the Universe is winning.
>   Anonymous
>
> Lisandro Damián Nicanor Pérez Meyer
Roman.

> http://perezmeyer.com.ar/
> http://perezmeyer.blogspot.com/

Processed: Re: Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Debian Bug Tracking System]

Processing control commands:

> tag -1 moreinfo
Bug #914002 [qtcreator] qtcreator's clang code model appears to be broken with 
kit = clang
Added tag(s) moreinfo.

-- 
914002: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914002
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Lisandro Damián Nicanor Pérez Meyer]

Control: tag -1 moreinfo

El domingo, 18 de noviembre de 2018 09:04:27 -03 Roman Lebedev escribió:
[snip]
> > clang is now built with clang itself (stage2 build) since 7-5
> > 
> > Maybe this is the reason!
> 
> I can't tell.
> I don't remember when it was working for *certain*,
> but i think it was working a week ago, and broke before yesterday.

Well, that's an interesting datapoint. I switched qtcreator to use LLVM/clang 
7 on 4.7.2-2. Please try installing qtcreator 4.7.2-1 from 
snapshots.debian.org and see what happens:




-- 
Programming today is a race between software engineers striving to build
bigger and better idiot-proof programs, and the Universe trying to produce
bigger and better idiots. So far, the Universe is winning.
  Anonymous

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Roman Lebedev]

On Sun, Nov 18, 2018 at 2:57 PM Sylvestre Ledru  wrote:
>
> Hello
>
> Le 18/11/2018 à 12:30, Roman Lebedev a écrit :
> > Package: qtcreator
> > Version: 4.7.2-2
> > Severity: important
> >
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > If kit is gcc, the project (any fresh one i open) is parsed normally.
> > All the symbols are resolved, and i can go to the definition.
> >
> > If kit is clang (tried with both the clang 7, and llvm trunk),
> > the parsing appears to fail, pretty much all the C++ std:: symbols
> > are underscored, and marked as not found.
>
> clang is now built with clang itself (stage2 build) since 7-5
>
> Maybe this is the reason!
I can't tell.
I don't remember when it was working for *certain*,
but i think it was working a week ago, and broke before yesterday.

> Cheers,
> Sylvestre
Roman.

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Sylvestre Ledru]

Hello

Le 18/11/2018 à 12:30, Roman Lebedev a écrit :

Package: qtcreator
Version: 4.7.2-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

If kit is gcc, the project (any fresh one i open) is parsed normally.
All the symbols are resolved, and i can go to the definition.

If kit is clang (tried with both the clang 7, and llvm trunk),
the parsing appears to fail, pretty much all the C++ std:: symbols
are underscored, and marked as not found.


clang is now built with clang itself (stage2 build) since 7-5

Maybe this is the reason!

Cheers,
Sylvestre

Bug#914002: qtcreator's clang code model appears to be broken with kit = clang

[Roman Lebedev]

Package: qtcreator
Version: 4.7.2-2
Severity: important

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

If kit is gcc, the project (any fresh one i open) is parsed normally.
All the symbols are resolved, and i can go to the definition.

If kit is clang (tried with both the clang 7, and llvm trunk),
the parsing appears to fail, pretty much all the C++ std:: symbols
are underscored, and marked as not found.

But building works with any of these kits.
So this should be somehow a qtcreator clangcodemodel issue?

It might be as simple as rebuilding llvm and/or qtcreator,
which would imply that it is yet again yet another manifestation
of the "update of gcc breaks clang-based tools"..

Roman.

- -- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'unstable-debug'), (1, 
'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.18.0-2-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages qtcreator depends on:
ii  libbotan-2-5   2.6.0-3
ii  libc6  2.27-8
ii  libclang1-71:7.0.1~+rc2-4
ii  libgcc11:8.2.0-9
ii  libgl1 1.1.0-1
ii  libqbscore1.12 1.12.1+dfsg-2
ii  libqbsqtprofilesetup1.12   1.12.1+dfsg-2
ii  libqt5concurrent5  5.11.2+dfsg-5+b1
ii  libqt5core5a [qtbase-abi-5-11-2]   5.11.2+dfsg-5+b1
ii  libqt5designer55.11.2-5
ii  libqt5designercomponents5  5.11.2-5
ii  libqt5gui5 5.11.2+dfsg-5+b1
ii  libqt5help55.11.2-5
ii  libqt5network5 5.11.2+dfsg-5+b1
ii  libqt5printsupport55.11.2+dfsg-5+b1
ii  libqt5qml5 [qtdeclarative-abi-5-11-2]  5.11.2-3
ii  libqt5quick5   5.11.2-3
ii  libqt5quickwidgets55.11.2-3
ii  libqt5script5  5.11.2+dfsg-2
ii  libqt5sql5 5.11.2+dfsg-5+b1
ii  libqt5sql5-sqlite  5.11.2+dfsg-5+b1
ii  libqt5widgets5 5.11.2+dfsg-5+b1
ii  libqt5xml5 5.11.2+dfsg-5+b1
ii  libstdc++6 8.2.0-9
ii  qml-module-qtqml-models2   5.11.2-3
ii  qml-module-qtquick-controls5.11.2-2
ii  qml-module-qtquick25.11.2-3
ii  qtchooser  64-ga1b6736-5
ii  qtcreator-data 4.7.2-2

Versions of packages qtcreator recommends:
pn  clang  
ii  gdb8.1-4+b1
ii  konsole [x-terminal-emulator]  4:18.04.0-1
ii  make   4.2.1-1.2
ii  qmlscene   5.11.2-3
ii  qt5-doc5.11.2-1
ii  qt5-qmltooling-plugins 5.11.2-3
ii  qtbase5-dev-tools  5.11.2+dfsg-5+b1
pn  qtcreator-doc  
ii  qtdeclarative5-dev-tools   5.11.2-3
ii  qttools5-dev-tools 5.11.2-5
ii  qttranslations5-l10n   5.11.2-2
ii  qtxmlpatterns5-dev-tools   5.11.2-2
ii  xterm [x-terminal-emulator]337-1

Versions of packages qtcreator suggests:
ii  cmake   3.12.3-3
ii  g++ 4:8.2.0-2
ii  git 1:2.19.1-1
ii  kate-data   4:4.14.3-5
ii  subversion  1.10.3-1+b1
ii  valgrind1:3.14.0-2

- -- no debconf information

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEjkF6151RK40WXe2HCDw+u0oWieAFAlvxTWAACgkQCDw+u0oW
ieB8QhAAqJB3t4K+FeZo81tLQg7ErKb+EC3VnTy3RE04mo0o84h3w4C57VpuiRog
FCoJ6VT0kiummDD4OIPj3oz3Bf92Xq4CfTE23yvsNdhJbH6Ycp+4hywaBPUyeMtg
3cQ0zIiwZLOyXKIA6RjSodPd2G1thwmIaP0am9pD9CrXZ+tqA2Pc6m/g+74NGstY
8Mxds9jwunjdg7yGmB1E8MZKfpBTNDVRuH7/DFIf4ztnobblK5lq818eK3sdfALw
O4AKEu6PqAlyKI76MWlRP025vNfPvD/l0tkng4gTIknX+rLwBeY+hMR/KUqZ2qcX
wadhifLPR1+pYdpyFb8fOV37dHkuZPjfg/v4K9mwgGUfHt6qEVfeHVongfkozMk2
EobkufZw+Kex/T5J+4wU5EywhzAhQjlWdunb+iO9qzet00b183qc/XMW1MGUp/cc
OqSDq/zlzeb0lSsVgzDiWC+xtwj8A1taiqsc9POI4KgdEIInp68h8Nl7BOcIHb1p
3TmcZsXr4d1CXkeXx250nZOGAhNLroXsiEsx099Sf+CG28qHQi/Ehl7s+lI8Iy4+
CxJD5RER20+5CgQHX7mUExv3fT0LMJjP0CkgE89agnBoQoUo1m6DtBTQdUz/Ux7G
fX1z74lK/KCHCLWhKdBuyBmkdknut8o/vC6UpyI4dFjFmKO5zWY=
=LrR/
-END PGP SIGNATURE-