Apt considers 'unmet dependencies' to be a critical and usually fatal error: The software lacks files that the packager felt it needs for minimal function. The error cannot be bypassed, muted, or ignored.
It is not related to apt's marking (hold) feature.
In MOST cases (but not this case!) a 'missing dependency' error is caused by a user's mistake with an unwise source or unfortunate package version, and is most easily corrected by simply undoing the mistake or by agreeing to apt's package-based solution. If you found this solution by searching, this probably applies to you.
Dependencies are often between packages that come from entirely different upstreams, and there is room for disagreement. If you disagree with the packager's decision and can recommend an alternative that enhances the package's usefulness, please feel free to raise a bug or contact them directly to discuss how the packaging and requirements can be refined. Most deb packagers are volunteers.
If you have the skills, you can avoid the problem entirely by installing the software using a non-deb method. This method is more complex than using packages, and is NOT recommended for beginners.
