Okay, I immediately downloaded the deb version so I had it now.
Then I used Gdebi to try the install. It had a problem. I also tried QApt, but that did not work either. I used these because they are supposed to be able to satisfy dependencies.
At least I was able to verify the problem. I have 6.4.2 installed and you wanted 6.6.2. I wondered what was going on because I had both QT5 and QT6 installed. I will bet that stepping down to 6.4 would solve a lot of install problems. Of course I cannot be sure without getting past that first dependency issue.
I see you’re using Debian Bookworm. In addition to backporting QPrompt to work with Qt 6.4, the issue preventing us from supporting that version of Debian is that it only supplies Qt 5 versions of the KDE Frameworks that we depend on (those currently being: extra-cmake-modules, kcoreaddons, kirigami; and previously also ki18n). We’d have to create packages for those KDE libraries in addition to the package for QPrompt, for its dependencies to be satisfied. That is a time consuming process and it would have to be done on both ARM64 and x86_64 architectures. I don’t think it’s worth the time considering Debian Trixie is right around the corner.
You appear to have failed to address the issue. It is not about QT5, but about QT6, which as you can see appears installed in my system. That is on Debian 12 Bookworm. So if I have QT6, why is there a problem with 6.4? It’s still QT6 isn’t it?
You have Qt 6.4, it is a bit older than 6.7, which is the one that QPrompt currently requires, but it’s not too difficult to change QPrompt’s CMake code in order to make it work. That’s not the issue. The issue is Debian Bookworm doesn’t ship Qt 6 versions of the KDE Framework libraries that QPrompt depends on. Because QPrompt, in addition to depending on Qt, also has dependencies that depend on Qt. Debian Bookworm only ships Qt 5 versions of those dependencies. To work around that I’d have to create packages not only for QPrompt but for Qt 6.4 compatible versions of those dependencies as well, and that is far more work than just backporting to QPrompt to work with Qt 6.4.
Out of curiosity, I looked up which versions of KDE Frameworks 6 are compatible with Qt 6.4 and it appears that none of them are. KDE Frameworks 6.1 was the oldest version I could find that indicated which version of Qt 6 it requires. The minimum required version for KDE Frameworks 6.1 is Qt 6.5.
I might be wrong, but I highly doubt that KDE Frameworks 6.0 is compatible with anything lower than Qt 6.5. Even if I’m wrong, I don’t feel comfortable backporting to use such an early version of KDE Frameworks 6.
What I don’t understand is how I have anything in the QT6 range in the first place if Debian doesn’t come with anything higher than QT5. I guess I still cannot understand what’s going on.
From https://www.qt.io/blog/qt-6.6-released we read:
“We have continued our work with the Debian project, and established a new Qt 6 maintainer group. Thanks to this collaboration we now have Qt 6 packages available for Debian 11 and Debian 12 from the regular distribution repositories. Commercial Qt 6.6 packages are available from a Debian repository hosted by The Qt Company. Thanks to this work, both Commercial and Open Source users on Debian-based Linux systems can maintain their Qt installation using regular apt-get workflows. This includes embedded boards that are natively using Debian or Ubuntu distributions, such as the Raspberry Pi 4.”
Well, you’re going to have to explain this. If I understand, and trying to keep it simple, your software requires some particular libraries. Are they partly QT6.X and partly KDE Frameworks?
I don’t have to explain anything. I answer these questions because I care about the people using the software. Frankly, you’re taking my free time away, time which could be going into the project or to interactions that are less draining than our conversations,@KitchM.
As mentioned above, QPrompt’s KDE dependencies are:
extra-cmake-modules
KCoreAddons
Kirigami
To install QPrompt 2.0 you need a version of those libraries that is compatible with Qt 6.5.0 or later. Debian Bookworm only ships versions of KDE Frameworks that are compatible Qt 5.15. Packages for KDE Frameworks compatible with Qt 5 start with the prefix kf5- while packages for KDE Frameworks compatible with Qt 6 start with the prefix kf6-. Those are already present in Debian Trixie, which is now up for testing and will likely release this year. Let’s just wait for it to come out and continue working on universal packaging formats while we get there.
Whoa there, Good Buddy. Sorry. No insult or demand intended. I perhaps could have rephrased it better. In fact, there is no need for you to take any time to explain anything at all. I’m just thinking out loud.
All I was trying to get to is that there appears much more than simple dependencies required in this testing scenario. If I am to take my time to help you in your project, I am showing that I’m willing to step back in and engage if there is anything I can do, even after stopping a number of times.
At one point in time, it appeared that I could do no more because of my OS. I did some research and found a possible way to force the dependency installs. Sadly, it looked like that failed.
That just led me to wonder why my QT6 wasn’t good enough. Then I learn that there is yet another software package involved; KDE Frameworks. Have no idea whatsoever regarding the relationship between the two.
Obviously, I like the program and want it to mature and work on all platforms and am willing to help as I can. Sadly, I cannot do that from a position of ignorance.
I may upgrade Debian to testing or unstable, or move to another OS with more up-to-date libraries. I just haven’t decided right now.
