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

Bug#874957: marked as done ([kmousetool] Future Qt4 removal from Buster)



Your message dated Sat, 09 Dec 2017 12:13:03 +0000
with message-id <E1eNe07-0006JW-2v@fasolo.debian.org>
and subject line Bug#874957: fixed in kmousetool 4:17.08.3-1
has caused the Debian Bug report #874957,
regarding [kmousetool] 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.)


-- 
874957: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874957
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: kmousetool
Version: 4:16.08.0-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: kmousetool
Source-Version: 4:17.08.3-1

We believe that the bug you reported is fixed in the latest version of
kmousetool, 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 874957@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Pino Toscano <pino@debian.org> (supplier of updated kmousetool 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: SHA512

Format: 1.8
Date: Sat, 09 Dec 2017 09:22:50 +0100
Source: kmousetool
Binary: kmousetool
Architecture: source
Version: 4:17.08.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>
Changed-By: Pino Toscano <pino@debian.org>
Description:
 kmousetool - mouse manipulation tool for the disabled
Closes: 874957
Changes:
 kmousetool (4:17.08.3-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream release:
     - switches to Qt5/KF5 (Closes: #874957)
   * Bump Standards-Version to 4.1.2, no changes required.
   * Simplify watch file, and switch it to https.
   * Update the build dependencies following the port to Frameworks:
     - remove kde-sc-dev-latest, and kdelibs5-dev
     - add extra-cmake-modules, libkf5dbusaddons-dev, libkf5doctools-dev,
       libkf5i18n-dev, libkf5iconthemes-dev, libkf5notifications-dev,
       libkf5xmlgui-dev, libphonon4qt5-dev, libphonon4qt5experimental-dev, and
       qtbase5-dev
   * Use the right dhmk helper.
   * Add kde-l10n breaks/replaces.
Checksums-Sha1:
 daec5739354c1be6b0ea2b0fe9dea15274428d10 2395 kmousetool_17.08.3-1.dsc
 f9d4ba37ecd2f81433cf80485a2af5b3345c46ef 110844 kmousetool_17.08.3.orig.tar.xz
 08357c07143af177e61ef1a01869d68af109a919 4840 kmousetool_17.08.3-1.debian.tar.xz
 7882c354cab088634e2c31abe0c01e9676a0b8d9 18025 kmousetool_17.08.3-1_source.buildinfo
Checksums-Sha256:
 c8674216df621ccfce685574bead45dff7c0e6b391607c9983c871fe45321451 2395 kmousetool_17.08.3-1.dsc
 3ba4d8a4dc93a25eeb0dfc154a5adf0fa74d71fe7e868b06f9970b42f4565f78 110844 kmousetool_17.08.3.orig.tar.xz
 68f5af84312656a12d01ca5189e79682f68a6cf0c0550978787b056961d55dd9 4840 kmousetool_17.08.3-1.debian.tar.xz
 47659c10ec24d4bfb1147ca4b6538e92c5e147010a03af28bc73d7f70b66c1b7 18025 kmousetool_17.08.3-1_source.buildinfo
Files:
 491b06d23ac8166fba7691dbfbc72f62 2395 kde optional kmousetool_17.08.3-1.dsc
 339247030683cafba498e5665b4f3ec8 110844 kde optional kmousetool_17.08.3.orig.tar.xz
 960cc43590d1310c77e76eeb907454bc 4840 kde optional kmousetool_17.08.3-1.debian.tar.xz
 5d625f9f1d83fda7980cc80239f6c4e9 18025 kde optional kmousetool_17.08.3-1_source.buildinfo

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

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlornYMACgkQLRkciEOx
P02eLxAAlkdkcDW0aG4d07qwWKVEKw2UcxdevgAX2+de+C3lFRd2dJmJyLYBNbE5
7fNz6G5QjX3bXyzXbFCmThUB8oVpABLgojS0FEfnowZDov4psV727skY1VbQnCZO
6GmzVMR7URf//UpN3ZDGRH4/9S9iG05AYfgAGxI8APyu2FUzDJ08KCl+0SO0l+8u
vIxjFJMZ5DZUk+W3uOyKZ9beNOCZ/XDszBvdnuV7548Uoo4P2A6HwO9c6oDDP2UC
7QUQ94llxGZmrad/y83hcPyhpGaPRlFB+cHBr7gN1Kp3fuM5/+713KW/j131i9mU
Zk6/O7D5rFUwEz5LqLlNDHVr0vmx1ZYk63T0lYaSRzvHZpAtt4T4qcFRmLJLZKMI
0b7t43Go01fM2slrFhm24q+3qb/OrH32Qv1Sa9Lh29YCw1t6F7rpRktJLRP1WU9H
vn/aE4OtcNmytlGZgcxl7QEkWyaiq+WN8JBoZHbEFZ2oy+VADiO+37kZpGZyWfYq
Meq/c4gRg9Mr4Poj8TWLaitsdz9TEd45Wp97WrD0fglCOqg0Tp5bSoPZhgCxkmmd
x7YyicezD4VOcmPPM3Rbls0+GvRkGvbnhAXb04bwJVUs8eAMSwJ9on397uShmMtI
9R1nJQPb9TP3eTurjbiEUkeOrqQW0VF4bklvMlw5+jyJ+d931Gs=
=xiAx
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: