Please port your package away from Qt 4

Bug #1757860 reported by Simon Quigley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
scantailor (Debian)
Fix Released
Unknown
scantailor (Ubuntu)
Fix Released
Undecided
Colin Watson

Bug Description

Currently Qt 4 has been dead upstream and we are starting to have problems maintaining it, like for example in the OpenSSL 1.1 support case.

Following in the footsteps of Debian[1], all packages directly or indirectly depending on qt4-x11 (like this one) must either get ported to Qt 5 and uploaded to the development release or get removed (by means of demotion to -proposed or removal of the package) before the 19.04 release. If it is possible to port your package by the 18.10 release, please do so.

If you have any questions about porting or this transition, please ask in #ubuntu-qt (preferred) or directly ping me

[1] https://wiki.debian.org/Qt4Removal

Tags: qt4-removal
Changed in scantailor (Debian):
status: Unknown → Confirmed
Changed in scantailor (Debian):
status: Confirmed → Fix Released
Revision history for this message
Colin Watson (cjwatson) wrote :

Removing packages:
        scantailor 0.9.12.2-3 in eoan
                scantailor 0.9.12.2-3 in eoan amd64
                scantailor 0.9.12.2-3 in eoan arm64
                scantailor 0.9.12.2-3 in eoan armhf
                scantailor 0.9.12.2-3 in eoan i386
                scantailor 0.9.12.2-3 in eoan ppc64el
                scantailor 0.9.12.2-3 in eoan s390x
                scantailor-dbgsym 0.9.12.2-3 in eoan amd64
                scantailor-dbgsym 0.9.12.2-3 in eoan arm64
                scantailor-dbgsym 0.9.12.2-3 in eoan armhf
                scantailor-dbgsym 0.9.12.2-3 in eoan i386
                scantailor-dbgsym 0.9.12.2-3 in eoan ppc64el
                scantailor-dbgsym 0.9.12.2-3 in eoan s390x
Comment: (From Debian) RoQA; Depends on Qt4, dead upstream; Debian bug #941151
Remove [y|N]? y

Changed in scantailor (Ubuntu):
assignee: nobody → Colin Watson (cjwatson)
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.