Your message dated Sun, 24 Feb 2019 07:21:46 +0100
with message-id <[email protected]>
and subject line Re: Bug#875135: qgis: Qt5 version available
has caused the Debian Bug report #875135,
regarding [qgis] Future Qt4 removal from Buster
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 [email protected]
immediately.)
--
875135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875135
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: qgis
Version: 2.14.18+dfsg-1
Severity: wishlist
User: [email protected]
Usertags: qt4-removal
Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:
[announced]
<https://lists.debian.org/debian-devel-announce/2017/08/msg00006.html>
Currently Qt4 has been dead upstream and we are starting to have problems
maintaining it, like for example in the [OpenSSL 1.1 support] case.
[OpenSSL 1.1 support] <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=828522>
In order to make this move, all packages directly or indirectly depending on
the Qt4 libraries have to either get ported to Qt5 or eventually get
removed from the Debian repositories.
Therefore, please take the time and:
- contact your upstream (if existing) and ask about the state of a Qt5
port of your application
- if there are no activities regarding porting, investigate whether there are
suitable alternatives for your users
- if there is a Qt5 port that is not yet packaged, consider packaging it
- if both the Qt4 and the Qt5 versions already coexist in the Debian
archives, consider removing the Qt4 version
= Porting =
Some of us where involved in various Qt4 to Qt5 migrations [migration] and we
know for sure that porting stuff from Qt4 to Qt5 is much much easier and less
painful than it was from Qt3 to Qt4.
We also understand that there is still a lot of software still using Qt4.
Don't forget to take a look at the C++ API changes page [apichanges] whenever
you start porting your application.
[migration] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
[apichanges] http://doc.qt.io/qt-5/sourcebreaks.html
For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at [email protected]
The removal is being tracked in <https://wiki.debian.org/Qt4Removal>
Lisandro,
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
fixed 875135 qgis/3.4.5+dfsg-1~exp1
thanks
On 2/23/19 8:47 PM, Sebastiaan Couwenberg wrote:
> On 1/14/19 12:25 PM, Bas Couwenberg wrote:
>> On 2019-01-14 11:37, Scott Kitterman wrote:
>>> qgis is the last package that depends on the Qt4 version of
>>> QScintilla2. It
>>> would be nice to be able to drop that for Buster.
>>>
>>> I notice that qgis 3.4.3 is available as a Qt5 based LTS release. It
>>> would be
>>> great to see this in Buster.
>>
>> To quote myself in #913065:
>>
>> "
>> The qgis package in Debian tracks the LTR releases (in the upstream LTR
>> repo), which doesn't have 3.4 yet.
>>
>> See:
>> https://www.qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule
>>
>>
>> The 3.4.5 [release] is after the soft-freeze so we may not be able to
>> get it into
>> buster, it will find its way into buster-backports eventually.
>> "
>>
>> Since QGIS 3.4 switches to Qt5 and Python 3, this change is quite
>> invasive, we don't have Python 3 support in GRASS yet, so the
>> integration in QGIS will likely be broken.
>
> QGIS 3.4.5 has been uploaded to experimental, but will have to pass the
> NEW queue.
Thanks again for the quick review.
> I forgot to close this issue in the changelog, so I'll have to do that
> manually after it's accepted.
Doing that now.
> Once it is, I'll talk to the release team via an unblock to see if we
> can get it into buster before the release, assuming it's accepted in
> time for that.
Still TODO.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---