2.47 deb binary is not installable on Ubuntu 22.04.1

[curiousercreative]

trafficstars

Describe the bug Installation via deb binary fails due to a dependency on cronie. Confusingly, 2.46 is the latest stable release according to this repo, but the README on master (what everyone will see) is from the upcoming 2.47 release where we have new installation methods available. Perhaps the short term fix is to revert the README until 2.47 is released?

To Reproduce Steps to reproduce the behavior:

sudo wget -O /tmp/getssl.deb https://github.com/jeffmerkey/getssl/releases/download/v2.47/getssl_2.47-1_all.deb
sudo dpkg -i /tmp/getssl.deb

dpkg: warning: parsing file '/var/lib/dpkg/status' near line 2150 package 'getssl':
 missing 'Maintainer' field
dpkg: warning: parsing file '/var/lib/dpkg/tmp.ci/control' near line 10 package 'getssl':
 missing 'Maintainer' field
(Reading database ... 64815 files and directories currently installed.)
Preparing to unpack /tmp/getssl.deb ...
Unpacking getssl (2.47-1) over (2.47-1) ...
dpkg: dependency problems prevent configuration of getssl:
 getssl depends on cronie; however:
  Package cronie is not installed.

dpkg: error processing package getssl (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 getssl

Operating system (please complete the following information):

# uname -a
Linux ubuntu 5.15.0-56-generic #62-Ubuntu SMP Tue Nov 22 19:54:14 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

# cat /etc/os-release 
PRETTY_NAME="Ubuntu 22.04.1 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04.1 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

# bash --version
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)

[Pear-sudo]

same issue on Debian 5.10.149-2

[u2n]

Also, downloading cronie source, building and installing (which should eliminate the dependency error) has no effect.

This makes getssl unusable on the most popular linux distros.

If any fix, or even workaround, please post!

[githubRover]

As a workaround you could just do a manual install (I use just the single getssl.sh script) https://github.com/srvrco/getssl#manual-installation

[u2n]

@githubRover, TY but that didn't work for me (LM 20.3, k5.4.0-136).

[curiousercreative]

@u2n the workaround is to install v2.46: https://github.com/srvrco/getssl/tree/release2.46#installation. 2.47 doesn't appear to be released, our maintainer should probably have used a different branch for development, but we'll survive!

[timkimber]

@u2n @githubRover @curiousercreative thanks for following up on this - I have a version in my dev branch which auto-builds the deb package. I'll make sure that doesn't include the cronie dependency and installs on stock Debian and release. Hopefully tomorrow...

[u2n]

Thanks, @curiousercreative and @timkimber, will give those a try. TBH though, it may be awhile, since I went with acme.sh for now (shell access required). Two different approaches, glad to have both options, appreciate your work.

[morfien101]

Although this issue is now fixed, the README in the landing page for the repo still references 2.47 where the issue is present.

@timkimber Could you update those links so other poor souls like me don't end up falling foul of this error.

[timkimber]

Thanks @morfien101 - I've finally released 2.49 (which I'd forgotten to move out of draft) and updated the README to replace all occurances of 2.47 with 2.49