Your message dated Mon, 15 Jan 2018 15:07:59 +0000
with message-id <[email protected]>
and subject line Bug#874909: fixed in i7z 0.27.2+git2013.10.12-g5023138-4
has caused the Debian Bug report #874909,
regarding [i7z] 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.)


-- 
874909: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874909
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: i7z
Version: 0.27.2+git2013.10.12-g5023138-3
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 ---
Source: i7z
Source-Version: 0.27.2+git2013.10.12-g5023138-4

We believe that the bug you reported is fixed in the latest version of
i7z, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Andreas Beckmann <[email protected]> (supplier of updated i7z 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 [email protected])


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

Format: 1.8
Date: Mon, 15 Jan 2018 15:01:52 +0100
Source: i7z
Binary: i7z
Architecture: source
Version: 0.27.2+git2013.10.12-g5023138-4
Distribution: unstable
Urgency: medium
Maintainer: Andreas Beckmann <[email protected]>
Changed-By: Andreas Beckmann <[email protected]>
Description:
 i7z        - reporting tool for i7, i5, i3 CPUs
Closes: 800323 856806 874909
Changes:
 i7z (0.27.2+git2013.10.12-g5023138-4) unstable; urgency=medium
 .
   * Stop building and shipping the Qt4 GUI.  (Closes: #874909, #800323)
   * nehalem.patch: Fix some nehalem detected as haswell, too.
     (Closes: #856806)
   * Set Priority to optional.
   * Bump Standards-Version to 4.1.3.
   * Use https:// URLs.
   * Switch to debhelper compat level 11.
Checksums-Sha1:
 35cf81d2269eceeeb50f9b66b2540ae4347ac2ad 2026 
i7z_0.27.2+git2013.10.12-g5023138-4.dsc
 4a40fe72843fc7e44262e158553348d515e44b49 6288 
i7z_0.27.2+git2013.10.12-g5023138-4.debian.tar.xz
 67ecf4808a332a3967ef388dacd0bb089b00ab0a 5769 
i7z_0.27.2+git2013.10.12-g5023138-4_source.buildinfo
Checksums-Sha256:
 7be52119214209187e29125f08ba97707b7a53812168c21b59affc1750f61698 2026 
i7z_0.27.2+git2013.10.12-g5023138-4.dsc
 a440c8a5c83063b0db7c2127d999525306c9f50bdb3113db34e81a0b8a0be2cb 6288 
i7z_0.27.2+git2013.10.12-g5023138-4.debian.tar.xz
 aa775cee63e280e1d072f9a21e764b6e3c5b2d53e897087fa2dfbbdc25720ab7 5769 
i7z_0.27.2+git2013.10.12-g5023138-4_source.buildinfo
Files:
 179288736bca3f583ae85815f94b31a5 2026 admin optional 
i7z_0.27.2+git2013.10.12-g5023138-4.dsc
 a1c27098bea5de97c23e5679c7e5c90d 6288 admin optional 
i7z_0.27.2+git2013.10.12-g5023138-4.debian.tar.xz
 85891e0e02306f7bf13ea2fdbba8147a 5769 admin optional 
i7z_0.27.2+git2013.10.12-g5023138-4_source.buildinfo

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

iQJEBAEBCAAuFiEE6/MKMKjZxjvaRMaUX7M/k1np7QgFAlpcuGAQHGFuYmVAZGVi
aWFuLm9yZwAKCRBfsz+TWentCEk1D/9abmuBRy4t4QzIY/QZ5GRl5GkEUcPv0+kj
0Zg5kgyad20eFlQOtXSQtS9jhAfQur+ab43cUbTeZmfgzMldJzFMHozDqH043dJR
qvrwTp6WxT7CQEd0PdgejeRfD/PPVkiBbPN9AtK/5x3swHGkuL5ln/iv/gfdEoes
E6QNaUqNjYI36/+fAuETDoV7JM2PHr0j9aDt7H5b5eqU6Xw3elm+rzOKH+OPRCLl
hh7QSUFrkvW3bdqHPbFOP/iYFZ6GgQLsxKz2BuFDFIQ1S0Hl2qfAvk458Ym6Ymae
RYZWFHjhq05pQZvV28CNVHVOuLKTq+Kat+MQP03jbGQs1PAisZsXaQSQVSrFnKHk
5FpZLKWln1Ine1sqr6xjs1236FnJJdeHXfOd8yMpDaG7bpC8vE1coo1ZNJ0iG5Nb
5eYLomg00iOv/pVul+xR19+aUkPudK2mAZC4gKaxbuzlpU5P6hL0OC1bYK8fhlY/
AFbZXUxFcZEuv5lT3CAZPwgX48VHQQK9XMxv+/occ4vnNXFdD232m/CbIDOdZ9j7
S5lC/QEJgbT51nAlHg+xPQ23Os9cwcCaZM58VqrunQLJoxE4JFDCmgdLffApH/Lw
mWY1VoRKyu8n3Hj8EK9EJuoLzkH6FVmEv9Da91DnP4wfsQ7vL/dQYavo0uOfMpzP
syL087dCzQ==
=I+tW
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to