Open martadinata666 opened 11 months ago
Is the interface actually different or is it just a naming issue? Perhaps libmatoya can just check for libjpeg.so.62.3.0
as well?
From my point of view, it is just about the naming issue, but on the backend I can't tell how the libjpeg is used by parsec.
I have the same issue, I installed libjpeg62, libjpeg89, libjpeg8-dev, all of the possible available libraries. Parsec does work, even if there's a message about the missing dependencies.
The problem however is that when I run upgrades, it wants to remove it. So I have to keep re-install it, remove dependencies check and reinstall it.
Also when there's a new parsec .deb version, I have to redo all of this.
The following packages have unmet dependencies:
parsec : Depends: libjpeg8 which is a virtual package and is not provided by any available package
The following actions will resolve these dependencies:
Remove the following packages:
1) parsec [150-91a (now)]
Accept this solution? [Y/n/q/?] n
libjpeg8
does not exist in debian bullseye bookworm, but exists on ubuntu. This application that use libtamoya like parsec throw missingMTY_SOLoad: libjpeg.so.8: cannot open shared object file: No such file or directory
There is hacky way of directly dirty linking
libjpeg.so.8
tolibjpeg.so.62.3.0
but not preferred.