showing the same error:
sudo apt-get install -y git build-essential python3-setuptools python3-dev libffi-dev libssl1.0-dev
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package libssl1.0-dev
E: Couldn’t find any package by glob ‘libssl1.0-dev’
E: Couldn’t find any package by regex ‘libssl1.0-dev’
sudo apt update && sudo apt install -y libssl1.0.0
showing below errors -
Hit:1 Index of /ubuntu xenial InRelease
Hit:2 Index of /ubuntu xenial-updates InRelease
Hit:3 Index of /ubuntu xenial-backports InRelease
Get:4 Index of /debian-security jessie/updates InRelease [44.9 kB]
Hit:5 Index of /ubuntu xenial-security InRelease
Err:4 Index of /debian-security jessie/updates InRelease
The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY AA8E81B4331F7F50
Reading package lists… Done
W: GPG error: Index of /debian-security jessie/updates InRelease: The following signatures couldn’t be verified because the public key is not available: NO_PUBKEY 9D6D8F6BC857C906 NO_PUBKEY AA8E81B4331F7F50
E: The repository ‘Index of /debian-security jessie/updates InRelease’ is not signed.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
Sorry guys - I specified the repos for debian instead of ubuntu. I don’t use ubuntu, but I’m sure it isn’t difficult to find repos that will work/match
I used to run into similar issues with dependencies being slightly mismatched versions when installing software from source and or a combo of source and packages back in the days before FreeBSD got a more sophisticated package management system. Seems like it happened a lot with PHP extensions, when the software was looking for an older library than was installed with the OS (or vice versa). The work around I used was to make a link to the newer library but name the link for what the software was asking for. It worked just fine and then I didn’t have to track the changes and do merges in the source code. I would keep track of those changes to the environment by putting them in a my system configuration script (these days I guess that’s called “devops”. But if you’re going to change the source maybe do a switch statement and make a pull request. Maybe the devs have a reason for that version of the library? Or maybe it’s just because that’s what is default on Ubuntu which moves faster than Debian.