Your message dated Sun, 25 Aug 2019 13:25:06 +0000 with message-id <e1i1sw2-000gf7...@fasolo.debian.org> and subject line Bug#875242: fixed in yabause 0.9.14-4 has caused the Debian Bug report #875242, regarding [yabause] 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.) -- 875242: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875242 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Source: yabause Version: 0.9.14-2.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: yabause Source-Version: 0.9.14-4 We believe that the bug you reported is fixed in the latest version of yabause, 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. Reiner Herrmann <rei...@reiner-h.de> (supplier of updated yabause 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: Sun, 25 Aug 2019 14:49:38 +0200 Source: yabause Architecture: source Version: 0.9.14-4 Distribution: unstable Urgency: medium Maintainer: Debian Games Team <pkg-games-de...@lists.alioth.debian.org> Changed-By: Reiner Herrmann <rei...@reiner-h.de> Closes: 875242 Changes: yabause (0.9.14-4) unstable; urgency=medium . * Team upload. * Port to Qt5. (Closes: #875242) * Remove trailing whitespace in d/changelog. * Update watch file. * Update debhelper compat level to 12. * Update Standards-Version to 4.4.0: - declare that d/rules does not require root * Mark -common as Multi-Arch: foreign. * Use https for homepage. * Enable all hardening options. * Build against sdl2 instead of sdl1.2. * Use installed path for pixmaps so that dh_missing notices it. * Set 'set -e' in the script body of postinst/prerm. * Drop unused paragraphs from d/copyright. Checksums-Sha1: 2a0d6688467d812803e3799d36491b20c30d3d44 2508 yabause_0.9.14-4.dsc 777f83b1fca91ec69d6514e682a9b9ca06eedece 7176 yabause_0.9.14-4.debian.tar.xz f4481451ea45ec35f459abd43ee13faa7cfe0cac 17401 yabause_0.9.14-4_amd64.buildinfo Checksums-Sha256: b02fb6f9742da5fef7a49a6ac26ff229e73c11ee53c1f92db5af770f8c05e603 2508 yabause_0.9.14-4.dsc b07a8b7a286f7b210531ca7fbb6b7e9d93f7adcff027f6405dba55ba6c85bb50 7176 yabause_0.9.14-4.debian.tar.xz 5fe4a5f43be16f2699148c1509525efcef43e247876c15bdd1adf45e3d94cfa0 17401 yabause_0.9.14-4_amd64.buildinfo Files: 49b1c7f17a59daaffddd71a35364e1df 2508 otherosfs optional yabause_0.9.14-4.dsc b0eee61cedf16707f82dcfa204f71175 7176 otherosfs optional yabause_0.9.14-4.debian.tar.xz 01f8410f91dcac84e36de8cc244568bc 17401 otherosfs optional yabause_0.9.14-4_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQKjBAEBCgCNFiEErPPQiO8y7e9qGoNf2a0UuVE7UeQFAl1ihWJfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEFD RjNEMDg4RUYzMkVERUY2QTFBODM1RkQ5QUQxNEI5NTEzQjUxRTQPHGFwb0BkZWJp YW4ub3JnAAoJENmtFLlRO1Hkk48P/jnCBFfD8QZDsNc/AUcZVoFlAfKQaCyYg3yu hqvihhNDsHDd9VKXgV14EfoYhQjbflU8XnOHRNDvpgTkMblrRu8hkebqNsiUgESh JcOnobUjg83RcZx0YrFlZxYCZKHVbmi7dd7SHqTM4/RyxDUyicI7szbStkaAhrKG Wq8vxpjvEuiuE6EOie5yLndl4Cs9DvZ9iggK3SsTJ1NwYkytm3RXCjPiHU0gMCWU T8kZmy7RkUGdlQzUPIa/3V3dFc2XnTMy3V9q1gCLAsuDbZM96UeNyGCx7qrXQarn utejjeRaLPX1/HhTYn7ipcb2WCxXS8ioOmi9Jb5TY2utlvZU4JdhbPc+HHPHvSM5 ZyP8sHjA4FnE5Rj+U69Pu8ZdMg1gaqht0Vo6V1qLXNBoaZchfbS48d24hDymxwyi 4ABntPifllIMsHRB7WdhlD/tywltgyukcyiGI3U0WLna2w8QBI50SDiUk26MjsLv DCgW37tVB0D+VWD+GSBZttrU54Y5tMp93FnKO+G/rPWzsG2KAZrllU9xez4SHLMj GRe6m5Coytgg2EkckCo3E4/vcdQyOFW3ADzxzmsSz4yqc8zpxd1KDBn29kO90/lT xgJYhyDuuolTNp9W1RueLnDJpnUoQ0a7VlXVGikM0k8f2XL2/+V5VTp6DhCjEct+ Jp9IkaRw =gNHP -----END PGP SIGNATURE-----
--- End Message ---
