Bug#874950: [keepassx] Future Qt4 removal from Buster

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#874950: [keepassx] Future Qt4 removal from Buster

Lisandro Damián Nicanor Pérez Meyer-4
Source: keepassx
Version: 2.0.3-1
Severity: wishlist
User: [hidden email]
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 [hidden email]

The removal is being tracked in <https://wiki.debian.org/Qt4Removal>

Lisandro,
on behalf of the Qt4 maintainers

Reply | Threaded
Open this post in threaded view
|

Bug#874950: src:keepassx: port to Qt 5

John Scott-3
Package: src:keepassx
Followup-For: Bug #874950
Control: tags -1 fixed-upstream

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Though I can't find a single statement upstream,
it seems that KeePassX moved a while ago [1]. No
new release has been made yet, but master builds
on my system and runs, though I didn't test it
more.

The wiki [2] seemed to imply that KeePassXC would
replace it after the Qt 4 removal. Upstream has
been active keeping it working with recent Qt [3],
so it's my intent to clarify that.

[1] https://dev.keepassx.org/issues/394
[2] https://github.com/keepassx/keepassx
[3] https://github.com/keepassx/keepassx/commit/1682ab90243ef93449a981eb7b8046b629720488

- -- System Information:
Debian Release: buster/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-2-amd64 (SMP w/2 CPU cores)
Kernel taint flags: TAINT_FIRMWARE_WORKAROUND
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEAXEkn09uX7g8Tv8W3qerYfa4vJcFAlx6tf4ACgkQ3qerYfa4
vJfuwQf/fqxGpQpDCTbJDo6Rx34fW79dnNawGr7GIh6bo3W5jKxhsSAhv52GSwFd
vrrGdwbi9OgTk+JILKuYQwGYILLdnAJsTUJo2+YrPtCA9lUMjxGHLLVuDXNpu/Um
vyOHhGSL+aQsgqIlrXvrUJ4/9GOiBX9bqwW1kG7X3VRozeBPvCNvJS3K4cs47fH3
iXfFLZ3+jB9Ko2YWP3919cZgWzMpRvR9ZwfowTEDvCeclodhyGHsKVx3NAUAEEvd
DH3MNK2RyFZzjh44lEoagf4pBPxjVo/8A4RI/mQMet0sRUUeCvt3bm/mIOnPWQwM
qJGnbAc74DLGiIs6QXwIuthxO9JnZA==
=XKkS
-----END PGP SIGNATURE-----