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

Dependency problems on Debian testing #1158

Closed
mariokamenjak opened this issue Jun 24, 2016 · 4 comments
Closed

Dependency problems on Debian testing #1158

mariokamenjak opened this issue Jun 24, 2016 · 4 comments

Comments

@mariokamenjak
Copy link

When I try to install otter browser witth gdebi it reports the following unsatisfied dependencies:
otter-browser depends on libhunspell-1.3-0 (>= 1.3.3); however:
Package libhunspell-1.3-0:amd64 is not installed.
otter-browser depends on qtbase-abi-5-3-2; however:
Package qtbase-abi-5-3-2 is not installed.

Funnily enough I have libhunspell-1.4.1-2 installed.

@Frenzie
Copy link
Member

Frenzie commented Jun 27, 2016

That seems to be a packaging problem with Stretch right now, not with Otter as such. qtbase-abi-5-3-2 is a virtual package provided by libqt5core5a, but only by the version in unstable, not in testing. I imagine that'll trickle down soon enough.

That being said, I think normal applications generally aren't supposed to depend on qtbase-abi but only on libqt5core5a, so I'm not entirely sure why shlibs:Depends expands to include it. Maybe it has something to do with the increasingly outdated Qt 5.3 in Jessie.

@mariokamenjak
Copy link
Author

On that matter... would it be a tough job for you guys to contact the guys at Debian and get otter into the Debian archive?
It would give a lot of coverage for otter, and Ubuntu and Mint also still take packages from the Debian archive.
https://www.debian.org/doc/manuals/distribute-deb/distribute-deb.html#adding-packages-to-debian
http://www.debian.org/devel/wnpp

@Emdek
Copy link
Member

Emdek commented Jun 27, 2016

@mariokamenjak, AFAIK hunspell 1.4 is ABI incompatible with 1.3, so package created for Debian stable could crash there.
It seems that the best solution for now would be to try to go for #1148, which would allow us to provide some package containing revived QtWebKit which will take some time to reach distributions.

@Emdek Emdek closed this as completed Jun 27, 2016
@mariokamenjak
Copy link
Author

Is it ok if I myself send the Debian guys a request trough wnpp? Maybe some of them are willing to help?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants