Bug#875029: marked as done ([lightdm] Future Qt4 removal from Buster)
Your message dated Tue, 17 Sep 2019 21:04:17 +0000
with message-id <E1iAKe1-000FyX-C5@fasolo.debian.org>
and subject line Bug#875029: fixed in lightdm 1.26.0-6
has caused the Debian Bug report #875029,
regarding [lightdm] 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@example.com
Debian Bug Tracking System
Contact firstname.lastname@example.org with problems
--- Begin Message ---
- To: email@example.com
- Subject: [lightdm] Future Qt4 removal from Buster
- From: Lisandro Damián Nicanor Pérez Meyer <firstname.lastname@example.org>
- Date: Sat, 9 Sep 2017 22:10:37 +0200
- Message-id: <20170909201037.GA17596@pryan.ekaia.org>
Hi! As you might know we the Qt/KDE team are preparing to remove Qt4
as [announced] in:
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.
For any questions and issues, do not hesitate to contact the Debian Qt/KDE
team at email@example.com
The removal is being tracked in <https://wiki.debian.org/Qt4Removal>
on behalf of the Qt4 maintainers
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is fixed in the latest version of
lightdm, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to firstname.lastname@example.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
Yves-Alexis Perez <email@example.com> (supplier of updated lightdm 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 firstname.lastname@example.org)
-----BEGIN PGP SIGNED MESSAGE-----
Date: Tue, 17 Sep 2019 22:51:36 +0200
Maintainer: Debian Xfce Maintainers <email@example.com>
Changed-By: Yves-Alexis Perez <firstname.lastname@example.org>
lightdm (1.26.0-6) unstable; urgency=medium
* drop liblightdm-qt packages for Qt4 Debian removal.
Thanks Moritz Mühlenhoff for the patch (closes: #875029)
* d/control: update dh compat level to 11
* d/rules: explicitly enable gtk-doc.
It seems that default behavior changed at some point, making the package
FTBFS because dh_install can't find the gtk-doc folder.
* d/rules: override dh_installsystemd instead of dh_systemd_start
c763c60f0699313ad00d494c2deb0a7003921169 2274 lightdm_1.26.0-6.dsc
0a237c33c8fe424da58776a5d4f22a4deba03a2d 38288 lightdm_1.26.0-6.debian.tar.xz
b395a12c704a343e90fc8504e83f829b28bfedab 20034 lightdm_1.26.0-6_amd64.buildinfo
d5fbff34329d856906a61596330fbb25eefa6d764ddbc3aa4fb7ef4500b9aa84 2274 lightdm_1.26.0-6.dsc
270b5d6b871982a898608ab578b0d41e9c02dc19f55c26aa5c5cb7cc7bf56239 38288 lightdm_1.26.0-6.debian.tar.xz
740bd73ff95f9c033604e5ef387e8b877e68d6f97d3dccb62cf95a029604d71a 20034 lightdm_1.26.0-6_amd64.buildinfo
2af4c6b2f705505938b086e7441f0303 2274 x11 optional lightdm_1.26.0-6.dsc
ec0a35657e41b33ac90fecb40ae64545 38288 x11 optional lightdm_1.26.0-6.debian.tar.xz
b0485d9ff9a8c5d45f460dafe30cd56e 20034 x11 optional lightdm_1.26.0-6_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
--- End Message ---