Your message dated Tue, 20 Feb 2018 21:13:08 +0000
with message-id <e1eofdo-000g2s...@fasolo.debian.org>
and subject line Bug#874975: fixed in kmix 4:17.12.2-1
has caused the Debian Bug report #874975,
regarding [kmix] 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 ow...@bugs.debian.org
immediately.)


-- 
874975: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874975
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: kmix
Version: 4:16.08.0-1
Severity: wishlist
User: debian-qt-...@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-...@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: kmix
Source-Version: 4:17.12.2-1

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

Debian distribution maintenance software
pp.
Pino Toscano <p...@debian.org> (supplier of updated kmix 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Tue, 20 Feb 2018 21:22:11 +0100
Source: kmix
Binary: kmix
Architecture: source
Version: 4:17.12.2-1
Distribution: unstable
Urgency: medium
Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-...@lists.debian.org>
Changed-By: Pino Toscano <p...@debian.org>
Description:
 kmix       - volume control and mixer
Closes: 874975
Changes:
 kmix (4:17.12.2-1) unstable; urgency=medium
 .
   * New upstream release:
     - switches to Qt5/KF5 (Closes: #874975)
   * Update the build dependencies following the port to Frameworks:
     - remove kde-sc-dev-latest, and kdelibs5-dev
     - add extra-cmake-modules, qtbase5-dev, libkf5completion-dev,
       libkf5config-dev, libkf5configwidgets-dev, libkf5crash-dev,
       libkf5dbusaddons-dev, libkf5doctools-dev, libkf5globalaccel-dev,
       libkf5i18n-dev, libkf5iconthemes-dev, kinit-dev, libkf5notifications-dev,
       libkf5plasma-dev, libkf5solid-dev, libkf5widgetsaddons-dev,
       libkf5windowsystem-dev, and libkf5xmlgui-dev
   * Use the right makefile class:
     - use debian-qt-kde.mk v3
     - bump the pkg-kde-tools build dependency to >= 0.15.16
   * Stop passing -DKMIX_KF5_BUILD=0 to cmake, as kmix is now only Qt5/KF5.
   * Break/replace against kde-l10n that ships translations.
   * Update the patches:
     - kmix_showeverywhere.diff: refresh
   * Remove symlinking of the desktop autostart, since they are now installed
     in the correct location.
   * Use https for Format in copyright.
   * Update lintian overrides.
Checksums-Sha1:
 2b94d610698e3258bad1497af2e407f2df6b5694 2656 kmix_17.12.2-1.dsc
 38a4532620cf0154b3204b9e7d6b517c30128408 1282236 kmix_17.12.2.orig.tar.xz
 f98d3c6e6b9edef8840d0b008aaa144335d14ca7 6904 kmix_17.12.2-1.debian.tar.xz
 0b84eaf6399926a5f8a6cb7bfd33d1120a4f3463 20643 kmix_17.12.2-1_source.buildinfo
Checksums-Sha256:
 0f9692f5c34507864c70b49cbb84d1dcdf5bd0d9f85652de688df73a30c58535 2656 
kmix_17.12.2-1.dsc
 b22def92dd17696e0c10a84b96c2aaeed52c37a87a1c52f797ecc1c67d5dcd24 1282236 
kmix_17.12.2.orig.tar.xz
 fae24bf0b04e64597a066afbf9e944f775d7cc7820efec96da7c1315685e8dc7 6904 
kmix_17.12.2-1.debian.tar.xz
 40815888d373d710f93260ffa4a47f4c36d72506d5c0d1632cec31be2c45e288 20643 
kmix_17.12.2-1_source.buildinfo
Files:
 175aff1fe471d62fd6a734e8eec16a3a 2656 kde optional kmix_17.12.2-1.dsc
 7ccf16c998dc565cd3f8b4777826a1bb 1282236 kde optional kmix_17.12.2.orig.tar.xz
 b888cb795e17e38a20c61389fc263637 6904 kde optional kmix_17.12.2-1.debian.tar.xz
 d5b66d28851fcf2576ba636d29268ac1 20643 kde optional 
kmix_17.12.2-1_source.buildinfo

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

iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAlqMg5EACgkQLRkciEOx
P02DyA//cZxUxYukIBSkIAVHWDh2wtJRRvLiUloPxGQnK90c1AhomYDmDKK9xg8v
sPSeMiC1n+JTddlpZGqeg3dqP4RePnkVhyibquvCo/WPsc4Hp2Td1Ko4XEPRbC1q
CihtADQlyoDSlbsxemt2Krk3+4WnmnuQCpPkAg7cxxyE8lJTuH8HeF6oAg33vI2w
uD71qqwQTayIzputeZi/+ayRv7JsqOnvYedNPiUTAmWx7GoJA1nBC2eFweB9JeCV
PL5FvYBUlGvakJhcG7RaztsC2kcE1Ov/dGxBmAXM8nHaoEDRTmVMQlG79S7X5KJ+
FF5BG1We4X1NJ/c0H3ujKcIoWd1cL+BXis/i7mLgPxOm0T6FifZXMoeRsMkaYxtF
c+g1Fpcu5X4qsv1DC9Kw+S3o81qsbiVL5UJHXGH+dKKz6lLipKFyCtTJHMDeO+fL
a/WtcTiU+lxEWPbjGTMG7bVxIYqR/vUXYAjPlPs4VGFqjphKP+ppKu76ZcbosHlO
iaHgGTcrQTdf+bJd7PYfahiR91Bu3BmDETlS83d3X4Ves5Hycz0g2Nfdf9gAJuWO
oFoMOM1oVv49+2rp8BcJV2i5wNVhpZ35WBjIRdq6aiRSqC3nUbcY11Dp1pHj+5+4
FKLPNEsiMvx0ZXYN+yibsqXgJUVKNkMnkIc3vsFIwPsY59T1zvE=
=2JVi
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to