Hi,

I'm using this PPA to get the latest Skrooge - https://launchpad.net/~s-mankowski/+archive/ubuntu/beta-kf5

I have an issue with Ubuntu 18.04 as it depends on:

• "qtbase-abi-5-9-4" (which was a virtual package in 17.10, but no longer provided), and instead I believe it could use "libqt5core5a".
• "libqca2-plugin-ossl" (which was a transitional package in 17.10), and instead I believe it should use "libqca2-plugins").

I manually modified the .deb and installed however the QT version mismatches on the minor.

Cannot mix incompatible Qt library (version 0x50904) with this library (version 0x50905)

Would you be able to rebuild with updated dependencies?

Thanks,
Chris

I am not able to test it.
What should I change in packaging?
Could you help me by giving me more details?

I think it's just a case of changing these 2 dependencies

qtbase-abi-5-9-4 -> libqt5core5a
libqca2-plugin-ossl -> libqca2-plugins

Basically I think it just needs building on Ubuntu 18.04.

Hi,
Thank you for the information but this is may be not so simple.
Indeed, yesterday, I pushed a new beta version on launchpad without changing the dependencies in the packaging.
As you can see here, the build is correct:
https://launchpad.net/~s-mankowski/+arc ... u/beta-kf5

Moreover, I don't have qtbase-abi-5-9-4 in the "control" packaging file.

Ok, I see what you're saying.

For #1, in your new beta build overnight the "qtbase-abi-5-9-4" has suddenly jumped to "qtbase-abi-5-9-5" (visible in the build log). While this is good, I suspect this is due to the build host changing randomly? Perhaps modify the debain/control file entry "qtbase5-dev (>= 5.5)," needs to be "(>= 5.9.5)"? Making this change might break older Ubuntu versions, I'm not sure...

For #2, the transitional package issue, I think also in the debian/control file there needs a simple change from "libqca2-plugin-ossl" to "libqca2-plugins". This is backward compatible to 16.04 it seems.

Thanks,
Chris

Just an FYI, I manually downloaded the new "~beta3" deb files, and manually changed the dependency from "libqca2-plugin-ossl" to "libqca2-plugins" locally and installed it.

Everything seems OK so far....

I published a new version 2.12.2 with the packaging correction.
Could you tell me if this works well?

Works!

Thank you.