Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong install dependencies on a Debian build with QT6 (works with QT5) #1104

Closed
1 task done
oe4dns opened this issue Dec 3, 2024 · 3 comments · Fixed by #1109
Closed
1 task done

Wrong install dependencies on a Debian build with QT6 (works with QT5) #1104

oe4dns opened this issue Dec 3, 2024 · 3 comments · Fixed by #1109
Labels
bug Something isn't working Linux Linux-only issues packaging Every issue linked with providing and fixing packages for different distributions and systems

Comments

@oe4dns
Copy link

oe4dns commented Dec 3, 2024

Is there an existing issue for this?

  • I searched the existing issues and did not find anything similar.

Current Behavior

Building antimicrox on Debian works as expected when following the official build instructions.

Installing the .deb after building with QT6 fails. The reason is, apt wants to install "libqt6widgets6t64" as a dependency. This is a rather uncommon package and only available in Debian Unstable for the m68k architecture! Removing this dependency from the .deb results in an installable and working programm.

Building with QT5 works and installs as expected. It depends on libqt5widgets which is common and not unexpected at all.

My suspicion is, the libqt6widgets6t64 dependency should in fact be changed to libqt6widgets.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

Program Version 3.5.0

Raspberry Pi OS "bookworm" (Debian Stable) on a Raspberry Pi 4

Anything else?

No response


Upvote & Fund

  • If you find this issue important, mark it with 👍. It lets us see which fixes and features are demanded by the most users.
  • We're using Polar.sh so you can upvote and help fund this issue. It may incentivize some developers to contribute to this project and fix some bugs.
  • Funded developer receives the funding once the issue is completed & confirmed by you.
  • Thank you in advance for helping prioritize & fund our backlog.
Fund with Polar
@oe4dns oe4dns added the bug Something isn't working label Dec 3, 2024
@pktiuk
Copy link
Member

pktiuk commented Dec 8, 2024

My suspicion is, the libqt6widgets6t64 dependency should in fact be changed to libqt6widgets.

This may be a good idea. I will check it out

@pktiuk pktiuk added packaging Every issue linked with providing and fixing packages for different distributions and systems Linux Linux-only issues labels Dec 8, 2024
@pktiuk
Copy link
Member

pktiuk commented Dec 8, 2024

According to package registries in Ubuntu repos there is a package libqt6widgets6t64 which replaces package libqt6widgets6 which exists in Debian repos.

@qyot27
Copy link

qyot27 commented Dec 8, 2024

According to package registries in Ubuntu repos there is a package libqt6widgets6t64 which replaces package libqt6widgets6 which exists in Debian repos.

https://packages.ubuntu.com/search?keywords=libqt6widgets&searchon=names&suite=all&section=all

It only exists with that name in 24.04; presumably the ones in 24.10 and Plucky use 64-bit time but simply reverted back to the old package name.

The topic page on the Debian Wiki is here:
https://wiki.debian.org/ReleaseGoals/64bit-time

It remains to be seen how Debian is going to handle this (or did handle this, considering Ubuntu is branched off of sid, so the different naming in 24.04 could well have come from Debian temporarily altering the name of the package during the transition) when it comes to package naming in the next stable version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Linux Linux-only issues packaging Every issue linked with providing and fixing packages for different distributions and systems
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants