Your message dated Mon, 18 Sep 2017 18:13:32 +0000
with message-id <[email protected]>
and subject line Bug#875225: fixed in virtualjaguar 2.1.3-1
has caused the Debian Bug report #875225,
regarding [virtualjaguar] 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.)
--
875225: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875225
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: virtualjaguar
Version: 2.1.2-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: virtualjaguar
Source-Version: 2.1.3-1
We believe that the bug you reported is fixed in the latest version of
virtualjaguar, 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.
John Paul Adrian Glaubitz <[email protected]> (supplier of updated
virtualjaguar 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, 18 Sep 2017 19:08:20 +0200
Source: virtualjaguar
Binary: virtualjaguar
Architecture: source
Version: 2.1.3-1
Distribution: sid
Urgency: medium
Maintainer: John Paul Adrian Glaubitz <[email protected]>
Changed-By: John Paul Adrian Glaubitz <[email protected]>
Description:
virtualjaguar - Cross-platform Atari Jaguar emulator
Closes: 875225
Changes:
virtualjaguar (2.1.3-1) unstable; urgency=medium
.
* New upstream release (Closes: #875225).
* Drop debian/patches/20-fix-sign-declarations.patch, fixed upstream.
* Drop debian/patches/10-add-version-file.patch, no longer needed.
* Add patch to fix version number in Makefile.
* Update Qt Build-Depends for Qt5 in debian/control.
* Add libcdio-dev to Build-Depends in debian/control.
* Update standards version to 4.0.1 in
debian/control, no changes required.
Checksums-Sha1:
4765bd88ca2cff46b1ec6d3d883f3a23884da864 2022 virtualjaguar_2.1.3-1.dsc
f61ba659d3ab59d06cbd9a7f12e2e9dc04764eb6 2921212
virtualjaguar_2.1.3.orig.tar.bz2
4ffb12f262ed47043763997ff61fceed02778899 4676
virtualjaguar_2.1.3-1.debian.tar.xz
bb32be337225fd6942ef925640f645981f80a539 11563
virtualjaguar_2.1.3-1_amd64.buildinfo
Checksums-Sha256:
d3d35469fb6b7664a709d8c1d938e4c02e6b3e200311af7da0cc01d2b3e16ab0 2022
virtualjaguar_2.1.3-1.dsc
5b2c8fced1df564624a37dd1d0209894770591d69763873cfeb7144359fe5f0e 2921212
virtualjaguar_2.1.3.orig.tar.bz2
196da246234ddc8e0181143b5d373e33a8f3a1721e20c9348b55dbf142b0362c 4676
virtualjaguar_2.1.3-1.debian.tar.xz
5c6caf9749fbbfcdd2e8ecf9d6983901fff556869444040b5c2b1c189635ee9c 11563
virtualjaguar_2.1.3-1_amd64.buildinfo
Files:
9646bf3271efcee3fffa714be0654afc 2022 otherosfs optional
virtualjaguar_2.1.3-1.dsc
0e3f30737c171c096ac2690a38f7029a 2921212 otherosfs optional
virtualjaguar_2.1.3.orig.tar.bz2
1a927f1f50befb69d9eff39861eeaf96 4676 otherosfs optional
virtualjaguar_2.1.3-1.debian.tar.xz
2991ab3ff29060b472c294094fd4f83c 11563 otherosfs optional
virtualjaguar_2.1.3-1_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEYv+KdYTgKVaVRgAGdCY7N/W1+RMFAlnAAEQACgkQdCY7N/W1
+RPyhg//URbmngIwsUUcsQsk74C0FI9qVKrCC+THQGOrFWMXIqt2jOU/Qy7YOkTC
fXQN4CL97rdkYDEy388fN5fr9zVz854BEnq9IWSrwDVzr+H5oa9NAOeSvXOI6G0v
wKDjEuul6MyyVBQi6i3PRoCDCYgJ8Xj3STgLbISLv1l2JxFUzlL/lk2qgoI66zRT
VsJ50avI2FBXnY0XsnpCfa4DlgfLPkeKZmAuLn9oe0oF/VXnDWG1BhAilg2HZ/4Q
HjHq2HgXSdX33ZDFKKVmNPNbScELYZnLSParnAabF6Hepc/iroIRQCCaLAxFC6Hh
hLavCremcyZfFd2u1clMYXygNAEzPfOt+48RzLiBdGcG7LLfu8xnGhLft9LgRrie
xf8873zAUEfbZzFwugx2CpX7rJJRxb8HvJl8dfHFGH5cRhMIl9xo/cGcMvZeHlV7
X5eiy8Tzm21lGKtcvt1Mpih/fFzGWxAzx1aEJpM1HhMDBBYlf6qLDbHff0I/L+uW
hkQ49ERmu3dxnVUYLBU4y0wRv2LJXKN0ImihE8OYUYd9EvRiSf2GE6cuDXfrt075
EwfkDfXOCBDOQXD9H7LyPJm4GjfAcQeSqm4UEFH5Z9whgvugoPr+wwrIKjemX845
QzjI7AoWMQlVDw5hAvfmPC9puz/BQdsrqCKvT6D1VSJowqnLDTc=
=DY4n
-----END PGP SIGNATURE-----
--- End Message ---
