beetboxvm / beetbox

Pre-provisioned L*MP stack
http://beetbox.rtfd.org
92 stars 19 forks source link

"No package matching 'php7.3-mcrypt' is available" #481

Open klonos opened 5 years ago

klonos commented 5 years ago

Problem/Motivation

Provisioning fails with this message when php is set to 7.3

Expected behaviour

Provisioning should not fail.

Actual behaviour

    beetbox: TASK [geerlingguy.php : Ensure PHP packages are installed.] ********************
    beetbox: failed: [localhost] (item=[u'php7.3', u'php7.3-apcu', u'php7.3-cli', u'php7.3-common', u'php7.3-curl', u'php7.3-dev', u'php7.3-fpm', u'php7.3-gd', u'php7.3-imap', u'php7.3-json', u'php7.3-mbstring', u'php7.3-mcrypt', u'php7.3-opcache', u'php7.3-sqlite3', u'php7.3-xml', u'php7.3-yaml']) => {"changed": false, "item": ["php7.3", "php7.3-apcu", "php7.3-cli", "php7.3-common", "php7.3-curl", "php7.3-dev", "php7.3-fpm", "php7.3-gd", "php7.3-imap", "php7.3-json", "php7.3-mbstring", "php7.3-mcrypt", "php7.3-opcache", "php7.3-sqlite3", "php7.3-xml", "php7.3-yaml"], "msg": "No package matching 'php7.3-mcrypt' is available"}
    beetbox: 
    beetbox: PLAY RECAP *********************************************************************
    beetbox: localhost                  : ok=89   changed=7    unreachable=0    failed=1   
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Steps to reproduce

Change the php package to 7.3. Add this to your local.config.yml:

php_version: "7.3"

Proposed changes

This seems to be related: https://github.com/debops/debops/pull/149

In PHP 7.2 the MCrypt extension was moved out from core to PECL. A condition was added to only include the mcrypt package if the PHP version is lower than 7.2.

klonos commented 5 years ago

...also: https://github.com/geerlingguy/ansible-role-php-versions/issues/27

That's on Debian/Ubuntu builds with 7.3, since mcrypt has been deprecated (after being unmaintained for a decade or so). I'm thinking I can probably drop that dep in the default list at this point. I think most of the major CMSes don't have any particular mcrypt dependencies now. At least tested with Wordpress, Drupal 8, and Magento 2...

pich commented 5 years ago

+1