Your message dated Wed, 04 Dec 2019 11:37:03 +0000
with message-id <e1icsxr-00026o...@fasolo.debian.org>
and subject line Bug#935352: fixed in trimage 1.0.6-1
has caused the Debian Bug report #935352,
regarding trimage: Qt4 removal from Bullseye
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.)


-- 
935352: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935352
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: trimage
Version: 1.0.5+git20130126.e47888e-1
Severity: important
User: debian-qt-...@lists.debian.org
Usertags: qt4-removal

Hi!

As you might know, we the Qt/KDE team are going to remove Qt 4 in Bullseye
cycle, as announced in [1].

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.

Your package still uses Qt 4, via the Python bindings (PyQt4).

Therefore, please take the time and:

- contact your upstream (if existing) and ask about the state of a Qt 5 /
  PyQt5 port of your application;
- if there are no activities regarding porting, investigate whether there are
  suitable alternatives for your users;
- if there is a Qt 5 port that is not yet packaged, consider packaging it;
- if both the Qt 4 and the Qt 5 versions already coexist in the Debian
  archives, consider removing the Qt 4 version.

Porting from Qt 4 to 5 is much easier than it was to port from Qt 3 to 4.
Please see [2] for the general porting instructions, and [3] for some
Python-specific differences.

The removal is being tracked in [4]. My intention is to bump the severity
of this bug to RC soon, like it is already the case with other Qt 4 removal
bugs.

[1]: https://lists.debian.org/debian-devel-announce/2017/08/msg00006.html
[2]: https://doc.qt.io/qt-5/sourcebreaks.html
[3]: https://www.riverbankcomputing.com/static/Docs/PyQt5/pyqt4_differences.html
[4]: https://wiki.debian.org/Qt4Removal

--
Dmitry Shachnev

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: trimage
Source-Version: 1.0.6-1

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

Debian distribution maintenance software
pp.
Andreas Tille <ti...@debian.org> (supplier of updated trimage 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: SHA256

Format: 1.8
Date: Wed, 04 Dec 2019 12:19:41 +0100
Source: trimage
Binary: trimage
Architecture: source
Version: 1.0.6-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PhotoTools Maintainers 
<pkg-phototools-de...@lists.alioth.debian.org>
Changed-By: Andreas Tille <ti...@debian.org>
Description:
 trimage    - GUI and command-line interface to optimize image files
Closes: 930279 935352 938720
Changes:
 trimage (1.0.6-1) unstable; urgency=medium
 .
   * Team upload.
   * New upstream version
     Closes: #930279
   * Point watch file to upstream release tags
   * Build using python3-pyqt5
     Closes: #935352, #938720
   * debhelper-compat 12
   * Standards-Version: 4.4.1
   * Trim trailing whitespace.
   * Use secure URI in Homepage field.
   * Set upstream metadata fields: Repository, Repository-Browse.
Checksums-Sha1:
 9a8e66a3c1da97c3b9541bebea9bbf9973f3d05a 1984 trimage_1.0.6-1.dsc
 73433417a40f93d1843b98844e93f765afea7faa 69246 trimage_1.0.6.orig.tar.gz
 ed9574e6155f8140a6cd6351052a8244b46e0098 5688 trimage_1.0.6-1.debian.tar.xz
Checksums-Sha256:
 9b9d7a788e935d3db50f91c08dab764882592f48b6b10252a6a98e3e2f167589 1984 
trimage_1.0.6-1.dsc
 60448b5a827691087a1bd016a68f84d8c457fc29179271f310fe5f9fa21415cf 69246 
trimage_1.0.6.orig.tar.gz
 fb713c122c7aa9c8ab27dd8523269738e751d0a62737e074ace99d7d27d8ce74 5688 
trimage_1.0.6-1.debian.tar.xz
Files:
 d98a2bd8e125e637a349cc0476c9e480 1984 graphics optional trimage_1.0.6-1.dsc
 0e69c56323692594b66ec5b2f6d0a206 69246 graphics optional 
trimage_1.0.6.orig.tar.gz
 258462e094d63e875a3d603e5ffef0b1 5688 graphics optional 
trimage_1.0.6-1.debian.tar.xz

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

iQJFBAEBCAAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAl3nly8RHHRpbGxlQGRl
Ymlhbi5vcmcACgkQV4oElNHGRtF1Pg/+JN0BFOuntiu7x9QTQFUwMlka56G2ltjK
Em8XsRMF0tqc2r2kQKsJiHiXWFFpszTOOd5vtgajggPw2ijg5LV6ZwteqknwREyl
KYM1KJuEVJoRnpIs3MjEyg4Kbc3FDN2qOxHLhMfPHL0/Zx4/F4FuH8qNTgq8bFZI
1Ymcgo+CLb+CG4TDVl78Oz7f3AWXhkZg4UZY+43g9sLVcsYkZ0kGSNsTwLMGdbwS
9QsOtbLps8XInDog19Ob4VN3ZSkNFJ8jFEt8zq3B9x5VKBJyXh9Mav/drmbBXnsL
0zZVL0bM9VO9gH9R3dhJrzQdveTtNcf/KWx52CKpUKDkbBAFJJoqscYekqW+Qra3
O5u8NkpU808j9Oh0GKMb12t7rQ5X0A6NIlg5/T5qtr2m8a/Anf7If9Hr83ItHA4t
vv7dV0Cz0nYQNzQsnnepJhBEHj6l3f1Vx2c26Jz7d7OPXWkuMnlK59DM5vwVAPWL
M1DzveKNad+XXsRTLwMrbCf3qB74RPvFgmozBvP9M/QgCmxrsqeDQbUZ/iOE5bdi
nzkmywSCQIO8nRr4ZAseP7DajSTsZrhJNdwcahDUDyfCHOZNF8MVE28neYCY7w93
I/GHQ+p5xPtAd2Y5zsnlqNe3vC1ocs08Rr+QCyxegbTzLthDetT/WK3VSq8XBjYO
QzZHzgq6kOA=
=j9Sa
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to