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

Bug#874974: marked as done ([kmag] Future Qt4 removal from Buster)

Your message dated Sat, 09 Dec 2017 12:12:56 +0000
with message-id <E1eNe00-0006IL-CE@fasolo.debian.org>
and subject line Bug#874974: fixed in kmag 4:17.08.3-1
has caused the Debian Bug report #874974,
regarding [kmag] 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.)


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

We believe that the bug you reported is fixed in the latest version of
kmag, 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 874974@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 kmag 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:18:58 +0100
Source: kmag
Binary: kmag
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:
 kmag       - screen magnifier tool
Closes: 874974
Changes:
 kmag (4:17.08.3-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Maximiliano Curia ]
   * New upstream release (17.08.1):
     - switches to Qt5/KF5 (Closes: #874974)
   * Bump Standards-Version to 4.1.0.
   * Update upstream metadata
   * Update build-deps and deps with the info from cmake
   * Add breaks/replaces against the kde-l10n packages
 .
   [ Pino Toscano ]
   * New upstream release.
   * Bump Standards-Version to 4.1.2, no changes required.
   * Simplify watch file, and switch it to https.
   * Adjust l10npkgs_firstversion_ok to the version where kde-l10n will
     drop translations.
Checksums-Sha1:
 0f2ad1271ad778042c2bbda8beafefaa8187aed0 2468 kmag_17.08.3-1.dsc
 64e0bd85bd8a23eee911aa183b6b97a40adad0fc 587000 kmag_17.08.3.orig.tar.xz
 d5a88e06dbec4416ef8c60b496d842590e933f99 774 kmag_17.08.3.orig.tar.xz.asc
 eb91e7403bd08a9fbb0379258792687a21d6f760 9872 kmag_17.08.3-1.debian.tar.xz
 12157a7cb49f9c8823e9ba1a207ad1b6ffb8e082 18766 kmag_17.08.3-1_source.buildinfo
Checksums-Sha256:
 084eb702b8a3c4995b43eac8dee22107ebab65b7a992ac1f67322f7826adb3d9 2468 kmag_17.08.3-1.dsc
 2d81daa4e50a78ecff2527aae607f0020c5c2a1fe84c79d5f102a556f3ff4d35 587000 kmag_17.08.3.orig.tar.xz
 1e5d0c2e63c034764f4cdd8fe090a877a458f08c1f7a38f4cf06ea9fa1587967 774 kmag_17.08.3.orig.tar.xz.asc
 9057b6ecf2df8d8eefa23220ca5fa6e0fa3f2a1177b8da91e5d614604033a725 9872 kmag_17.08.3-1.debian.tar.xz
 e1843f294533bf27ac57db47d710105f31c086e75dd71bfcfc9efe3c87a6e057 18766 kmag_17.08.3-1_source.buildinfo
Files:
 8134728b66faa06a9e8eea0549a240b6 2468 kde optional kmag_17.08.3-1.dsc
 41a2db4f5927c1e13f3a382f89fe48bb 587000 kde optional kmag_17.08.3.orig.tar.xz
 0929eb48cba942e61639c006dd6421ed 774 kde optional kmag_17.08.3.orig.tar.xz.asc
 f9c8e5a61d1252d9f4305778c2226080 9872 kde optional kmag_17.08.3-1.debian.tar.xz
 20a0f40a741a787306b4f195268b6341 18766 kde optional kmag_17.08.3-1_source.buildinfo

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

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlornKAACgkQLRkciEOx
P00aZg//dghjNxByscQm9UkGWMIdx/ODAOKw6qf5v6zF/7u4YPct2hjsuwRQ2yrt
onQ928oYbqU2at04HScgeDCqoAB6OWAaou6/waMPc/aGIWL0FyLL3YPvu1lmCtvd
m/97lofsmdHmoK0eXCiDwa8K/7MHe5R8kNasdMk813nqDBSAArLzBPa4qpZVvG7W
lwA2bGqcqFtH0Dh3AIQVgqk+G28j68UgX6eX7NbrmTgFIF8yZaTsQMezB5EhaJyW
uuAWu3xiJYwtabeZtXiLIfNXhIGYSP/0+nXc0WGs/el7LtoTWt56WaoMagWqTros
NAHl+csKeTW9hQGEyDDaLJ8coNm+bTqwLkJxLV0npmBF7awnd6XHbiCA8LQ+xpJe
Xt61ICx7UaeYrX04PUUcSSPGinCLqmYKqJpT+2CIUJPf+ADhJG+CcOx+66tnnKh+
lbtwxFXDdx5z5chy4miHjl1IJXSZN0ezhtVKkCrWcO5MiqDDuQXVWucJnWcxwbdo
shbwZBL6ST9jke/2JIEfS+dHwD6rVl7qSYOFeGAtihQadhwAC/akNfGrxYQO/Ruq
whtFmUV70fqaKAdx3F44EYE2wGuG+Q9DoItS8gpn/UeDpBGTZM6u4ndF88R9wPR7
k9lSrjMnV6v5hZII+UZ1jzBcgHXVgxQkgTJem6BAUz5O/UTJxe8=
=PW6B
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: