Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
** Changed in: webkit-open-source
Status: Unknown => Confirmed
** Changed in: webkit-open-source
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1757582
Title:
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
When I try to start System Tools / Printers it spins for a while and
goes away.
When I try it from the command line it crashes with a python error
$ system-config-printer
** (system-config-printer.py:2913): WARNING **: 21:05:20.121: Error retrieving
accessibility bus
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
Public bug reported:
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
201 - 300 of 1057 matches
Mail list logo
