Please port your package away from Qt 4

Bug #1757595 reported by Simon Quigley
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
aseba (Debian)
Fix Released
Unknown
aseba (Ubuntu)
Fix Released
Undecided
Unassigned

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

Changed in aseba (Debian):
status: Unknown → New
Revision history for this message
Jeremy Bícha (jbicha) wrote :

This bug was fixed in the package aseba - 1.6.0-3

---------------
aseba (1.6.0-3) unstable; urgency=medium

  * debian/control: new build dependencies are qtbase5-dev, qt5-qmake,
    libqt5opengl5-dev, libqt5webkit5-dev, qtbase5-dev, qtbase5-dev-tools,
    qttools5-dev, libqwt-qt5-dev, libqt5svg5-dev
  * patched CMakeLists.txt, .cpp and .h files to use Qt5. Closes: #891021
  * skipped the auto_test taget in debian/rules

 -- Georges Khaznadar <email address hidden> Sat, 24 Feb 2018 14:45:29 +0100

Changed in aseba (Ubuntu):
status: New → Fix Released
Revision history for this message
Jeremy Bícha (jbicha) wrote :

Fails to build because of undefined references

https://launchpad.net/ubuntu/+source/aseba/1.6.0-3

Changed in aseba (Ubuntu):
status: Fix Released → Triaged
tags: added: ftbfs
Changed in aseba (Debian):
status: New → Fix Released
Revision history for this message
Simon Quigley (tsimonq2) wrote :

Migrated now.

Changed in aseba (Ubuntu):
status: Triaged → 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.