In 1.8.4 there was no dependency on the abi, and there wasn't also in June when Qt 5.4.2 was upgraded. The dependency can be checked (in addition to dpkg -s) by opening the DEBIAN/control of the binary deb https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-026/+build/7762777/+files/liboxideqt-qmlplugin_1.8.4-0ubuntu2_amd64.deb
In earlier times there was a dependency but it was dropped when oxideqmlscene was dropped.
At least the earlier usage was not flagged as being private symbol usage based on the Qt's symbol files, which meant Oxide did not need rebuilds when upgrading Qt. The new use in 1.9 however does bring both the qtbase and qtdeclarative abi dependencies in (https://launchpad.net/~ubuntu-mozilla-security/+archive/ubuntu/ppa/+build/7877092/+files/liboxideqt-qmlplugin_1.9.1-0ubuntu1_amd64.deb) so something new of both has been started to be used.
Thanks for reporting bugs upstream.
In 1.8.4 there was no dependency on the abi, and there wasn't also in June when Qt 5.4.2 was upgraded. The dependency can be checked (in addition to dpkg -s) by opening the DEBIAN/control of the binary deb https:/ /launchpad. net/~ci- train-ppa- service/ +archive/ ubuntu/ landing- 026/+build/ 7762777/ +files/ liboxideqt- qmlplugin_ 1.8.4-0ubuntu2_ amd64.deb
In earlier times there was a dependency but it was dropped when oxideqmlscene was dropped.
At least the earlier usage was not flagged as being private symbol usage based on the Qt's symbol files, which meant Oxide did not need rebuilds when upgrading Qt. The new use in 1.9 however does bring both the qtbase and qtdeclarative abi dependencies in (https:/ /launchpad. net/~ubuntu- mozilla- security/ +archive/ ubuntu/ ppa/+build/ 7877092/ +files/ liboxideqt- qmlplugin_ 1.9.1-0ubuntu1_ amd64.deb) so something new of both has been started to be used.
Thanks for reporting bugs upstream.