[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#875021: marked as done ([libdbusmenu-qt] Future Qt4 removal from Buster)

Your message dated Sun, 25 Aug 2019 16:36:45 +0000
with message-id <E1i1vVV-0008N8-1T@fasolo.debian.org>
and subject line Bug#875021: fixed in libdbusmenu-qt 0.9.3+16.04.20160218-2
has caused the Debian Bug report #875021,
regarding [libdbusmenu-qt] 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 owner@bugs.debian.org
immediately.)


-- 
875021: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875021
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: libdbusmenu-qt
Version: 0.9.3+16.04.20160218-1
Severity: wishlist
User: debian-qt-kde@lists.debian.org
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 debian-qt-kde@lists.debian.org

The removal is being tracked in <https://wiki.debian.org/Qt4Removal>

Lisandro,
on behalf of the Qt4 maintainers

--- End Message ---
--- Begin Message --- 
Source: libdbusmenu-qt
Source-Version: 0.9.3+16.04.20160218-2

We believe that the bug you reported is fixed in the latest version of
libdbusmenu-qt, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 875021@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Scott Kitterman <scott@kitterman.com> (supplier of updated libdbusmenu-qt package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 25 Aug 2019 12:07:44 -0400
Source: libdbusmenu-qt
Architecture: source
Version: 0.9.3+16.04.20160218-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Krap Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Scott Kitterman <scott@kitterman.com>
Closes: 875021
Changes:
 libdbusmenu-qt (0.9.3+16.04.20160218-2) unstable; urgency=medium
 .
   * Team upload.
   * Drop Qt4 support (Closes: #875021)
   * Update Vcs-* to point to salsa
   * Update symbols files
Checksums-Sha1:
 d0b7622b158873892a71ba9c3875841d05612098 2359 libdbusmenu-qt_0.9.3+16.04.20160218-2.dsc
 c93c2fc1271edb46377b287ea59e7cb9f114946b 5268 libdbusmenu-qt_0.9.3+16.04.20160218-2.debian.tar.xz
 71a2641d19220192b465067cb29f4b0c1af075c3 10026 libdbusmenu-qt_0.9.3+16.04.20160218-2_source.buildinfo
Checksums-Sha256:
 485ab4c4c624955571d8de5151ac2486edefcdeba7062f05546bff0b18cf43a7 2359 libdbusmenu-qt_0.9.3+16.04.20160218-2.dsc
 a7bc4f85ab574005b277b56dd24a1ec9720ca98446adb185f8dd3c2ae064b9f5 5268 libdbusmenu-qt_0.9.3+16.04.20160218-2.debian.tar.xz
 0407758c8d4251f24587cbc2ec50c8cfda2cde47d62efd34dbd1494ea32be9b2 10026 libdbusmenu-qt_0.9.3+16.04.20160218-2_source.buildinfo
Files:
 85a0b65ab5786716816aabe554ed1d19 2359 libs optional libdbusmenu-qt_0.9.3+16.04.20160218-2.dsc
 4ecf4427202e276a63251e294254c5ac 5268 libs optional libdbusmenu-qt_0.9.3+16.04.20160218-2.debian.tar.xz
 81a9ff55afbd9b563c8cc662d3e9071c 10026 libs optional libdbusmenu-qt_0.9.3+16.04.20160218-2_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE53Kb/76FQA/u7iOxeNfe+5rVmvEFAl1isnUACgkQeNfe+5rV
mvHhTw//bsgKYfCYWpAXldqj+LsRm6VfMG9JJC5nizHSDEWVqMMGClCWiK1s5QlM
KhMhrN53vO3mk4tBAe7shRw4Xw7koY3gK2JoRMuFSLlXFeEpzSusFYW9RiGZSMIi
lEAq0hmCssqVBVnhvZRU/jIR3cE+BypiN+fD5t7gNHa6QX2u1UIJG5OrnT5tAR0Z
s49ppym0iOlSUxFlJigviuoZPGxqKh/11A5TaQOYSrsMnPmNzIKj4sN/WVvD3BMo
A7bNBSgkHA6WwQYlMek6HSv3CU1SCcpro1GXwOWNRGNgL10Ipi6n1FV5SCARLCHw
WkALzwj4hrJDhdSm3OGNPHGct0XDdtBrQ7qkaOfVWDjGKId+wdKXZJ0bejWo6xvk
RaV3PQj/hqsHnKTDzXN0yI5upgS6MPUZclzUN7YjM+CS9RSIoSJonJVuJEQDa0K1
j5Fhc5ZPcz+oIegxvmvjebikoEPaFTOs88stM8gKkduF/a3xwyf0vzwMMS7qcIBw
//SXqd0+liz39X+hMwpYrqA0hk/KB0IfuP0x7XyPzKo/+dtKhDiuJ3igKPrrxOXi
IQbdvKYGARcX5zCMiaF2lGVnT3kGdTVKrE5Au3diuiFpskxMyrTBreM8kGiq8r/1
oMebzT90EF009sGS0xQEOfu5KeGYoyFW+dhtvKjvIOwO9guinzA=
=L6AP
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: