Quote:
The unmet dependencies error can happen randomly on many different components or modules such as libsasl2, libssl, python-wxversion, zlib, libidn, libldap, libkrb, libgssapi, libstdc++, libstdc++-devel and etc, different by each system.
Although the system suggested resolution for the error is to try to reinstall the affected dependency modules by “apt-get -f install” command to attempt to fix and correct a system with broken dependencies in place, however, many users found that the error happens again, throwing up more unmet dependencies for “first level original” unmet dependencies, causing infinite loop of the error.
The cause of the issue of unmet dependencies, despite the fact that the modules and all dependencies have been properly installed, is probably due to corrupted package database, and/or some packages weren’t installed properly. Thus, to fix and resolve the problem, try to run one of the following commands:
sudo apt-get clean
or,
sudo apt-get autoclean
“apt-get clean” clears out the local repository of retrieved package files (i.e. the .deb files). It removes everything but the lock file from /var/cache/apt/archives/ and /var/cache/apt/archives/partial/. “apt-get autoclean” clears out the local repository of retrieved package files, but unlike “apt-get clean”, it only removes package files that can no longer be downloaded, and are largely useless.
After running “apt-get clean” or “apt-get autoclean”, re-run the “apt-get -f install” command in affected modules the show in the error message:
sudo apt-get -f install <module name>
Finally, try to install the package(s) again. It should be able to install properly now.
this is what fixed my problem a few more hours of searching payed off thank god thank you guys for your help WinSCP connects now :thumbup1: :ott1: