Dax Mickelson's questions

In this specific situation I'm trying to install the latest version of SecureCRT (made by VanDyke). I get this type of issue every time I update to a new release of Ubuntu. That said, I've seen this issue with other programs.

Why is this file missing? Why do we remove the "old" version of the library and/or why do programmers hard code a specific version of shared library?

To date, I do not know how to get around this. I'd like to understand the deeper reasoning why this keeps happening and how I can fix it when it does happen (if it can even be fixed).

Am I just a curmudgeon when I find cloud-init annoying? I don't use "the cloud" for any of my projects yet the Ubuntu server ISO assumes that is my only path!

I wouldn't mind so much if cloud-init would figure out that it isn't "in the cloud" and disable itself. Instead, I have to figure out how to do some of the most simpliest of tasks (changing the hostname, as an example) via this convoluted process.

In short, how do I get a Ubuntu server installation that doesn't assume I'm going to integrate it with the cloud?

I've built 2 fresh VMs of Ubuntu server. One is from the 18.04.1 ISO and the other is from an older 18.04 ISO. The issue I'm having is that 'apt get install ansible' doesn't work on the 18.04.1 VM whereas it will work on the 18.04 VM. (I should note that even if I add the ppa:ansible/ansible to the 18.04.1 VM it still doesn't work because it needs the sshpass module which also doesn't appear accessible on 18.04.1.)

So, digging into the differences between the two VMs I noticed that the 18.04 VM has 10 or so repositories (not including deb-src lines) in its /etc/apt/source.list file whereas the 18.04.1 only has 4.

I didn't see any notes in the 18.04.1 readme to indicate that the sources.list file would be different. So, what am I doing wrong here?