Your message dated Fri, 23 Aug 2019 19:51:59 +0000
with message-id <e1i1fbl-000apt...@fasolo.debian.org>
and subject line Bug#875238: fixed in vmpk 0.7.1-1
has caused the Debian Bug report #875238,
regarding [vmpk] 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.)


-- 
875238: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875238
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vmpk
Version: 0.4.0-3
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: vmpk
Source-Version: 0.7.1-1

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

Debian distribution maintenance software
pp.
Sebastian Ramacher <sramac...@debian.org> (supplier of updated vmpk 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: Fri, 23 Aug 2019 21:34:23 +0200
Source: vmpk
Architecture: source
Version: 0.7.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multime...@lists.debian.org>
Changed-By: Sebastian Ramacher <sramac...@debian.org>
Closes: 758046 797535 870355 875238
Changes:
 vmpk (0.7.1-1) unstable; urgency=medium
 .
   * Team upload.
 .
   [ Ross Gammon ]
   * New upstream release
   * New maintainer (Closes: #797535)
   * Embedded copy of RiMidi no longer included (Closes: #758046)
   * Update to QT5 dependencies (Closes: #870355, #875238)
   * Unapply patches from source
   * Build depend on latest libdrumstick for new RT library
   * Add myself as uploaders
   * Use latest secure & canonical Vcs URIs
   * Drop old build options & add bindnow hardening option
   * Update copyrights & move to copyright format 1.0
   * Switch to Debian Multimedia Team maintenance
 .
   [ Sebastian Ramacher ]
   * debian/control:
     - Bump debhelper compat to 12.
     - Set Priority to optional.
     - Bump Standards-Version.
   * debian/rules: Force cmake build system.
Checksums-Sha1:
 6de7bb21b7b5c58ba1499ef660483f72c4ce840c 2061 vmpk_0.7.1-1.dsc
 1e4dcd3a6258351dcd6c0a25a9223c03278ae22e 623509 vmpk_0.7.1.orig.tar.gz
 6f35371a96ad9ad62c0c344c415568f463d27325 3556 vmpk_0.7.1-1.debian.tar.xz
Checksums-Sha256:
 2a6f7453c68778937e3558ff11e42cfafa633ba601ec2a161c14a33233c5d8e8 2061 
vmpk_0.7.1-1.dsc
 4afe1ad486c7463df95f5697dfb3551cfbbda22c8b89561832f37011101af2a6 623509 
vmpk_0.7.1.orig.tar.gz
 e1e7aee0dab3fceadb1b4cc1711a7727fdbd7452708c67142e697601c786a732 3556 
vmpk_0.7.1-1.debian.tar.xz
Files:
 521258bd33e127c063e88836b4a4d08a 2061 sound optional vmpk_0.7.1-1.dsc
 ed79a9495be4a6624f6bc88cfe19b786 623509 sound optional vmpk_0.7.1.orig.tar.gz
 732badfaf5eabeb19b139cd6c2be8bff 3556 sound optional vmpk_0.7.1-1.debian.tar.xz

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

iQIzBAEBCgAdFiEE94y6B4F7sUmhHTOQafL8UW6nGZMFAl1gQGIACgkQafL8UW6n
GZNCUQ/+LSTU4Ymt/x32q3H9TkvDYkQXBvOdxid2aNjwfNdIoHveng9y92qrZ2Vf
Wj+nlJQb7V1STZflGUfSrAA2ggXVxwxfn8z/b5A74Ac5fYYxr3ScGnJ9P9Z2FNGU
e2GtMKT9x7k0XerUDNUcwgtbSUT9wxOIqG6KADM3dshfJunFngCPEt2t4j79Anup
3V09JiVpVimM6v+pHcYhKe0UzmwkZrEmnZQOTSP0Qh+XwgN62UAeQ3CQXZdGaEoT
ZCseRWbOnjGLJBJ2KQNLAgK9bP117VG/ShfWgASrCxRnrDwwOh0Oakkox15JEkiL
Fx1UFLJSefwEfmiJY+CQ2NIO3X8GHbkg6vkEr+nUWXlWCMJwo7aV14lvKK3LrsKc
sSKZGPJ4+G63+fujLrZoGg6+N3pv5exwmCTsNg+dBEdzfnFJgfRvcFTGxhA6u5NO
f+7MzfU10+erwQR3wbPuZ4d+Idemt9bswsyVn5FWJU84bX2eCd0YaVZCwNUb3C3l
GR0e0prNpj1o4Zlk3AATvD4VhZMlIQMKEcaDlHm5ONOZQpwgGnFwpf/dri0CLpeW
2xZXuMWDg0/vA/iCKM2ItiGSWTudjbO68SWyLI+4yPkFQ4gi3bJrD4EpBO6UT57L
2x8nTis2/jVfIXrLuB8l6g9Kac7uq2QCH3pJgfcEeM814IwOJ7A=
=bVSK
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to