enterprisemediawiki / meza

Setup an enterprise MediaWiki server with simple commands
MIT License
41 stars 27 forks source link

"No package matching 'php72u' found available, installed or updated" #1290

Closed exodusprime1337 closed 2 years ago

exodusprime1337 commented 3 years ago

Environment

Issue details

Please provide any error messages you received and, if possible, steps to reproduce it. Consider reporting relevant data from /opt/data-meza/logs

TASK [apache-php : Ensure PHP IUS packages installed] ** Wednesday 05 May 2021 16:47:25 +0000 (0:00:00.481) 0:03:09.873 ***** [DEPRECATION WARNING]: Invoking "yum" only once while using a loop via squash_actions is deprecated. Instead of using a loop to supply multiple items and specifying name: "{{item}}", please use name: ['{{ php_ius_version }}', '{{ php_ius_version }}-cli', '{{ php_ius_version }}-common', '{{ php_ius_version }}-devel', '{{ php_ius_version }}-gd', '{{ php_ius_version }}-pspell', '{{ php_ius_version }}-snmp', '{{ php_ius_version }}-xml', '{{ php_ius_version }}-xmlrpc', '{{ php_ius_version }}-mysqlnd', '{{ php_ius_version }}-pdo', '{{ php_ius_version }}-odbc', '{{ php_ius_version }}-process', '{{ php_ius_version }}-bcmath', '{{ php_ius_version }}-intl', '{{ php_ius_version }}-opcache', '{{ php_ius_version }}-soap', '{{ php_ius_version }}-mbstring', '{{ php_ius_version }}-ldap', '{{ php_ius_version }}-pecl- memcached', 'pear1u'] and remove the loop. This feature will be removed in version 2.11. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg. failed: [localhost] (item=[u'php72u', u'php72u-cli', u'php72u-common', u'php72u-devel', u'php72u-gd', u'php72u-pspell', u'php72u-snmp', u'php72u-xml', u'php72u-xmlrpc', u'php72u-mysqlnd', u'php72u-pdo', u'php72u-odbc', u'php72u-process', u'php72u-bcmath', u'php72u-intl', u'php72u-opcache', u'php72u-soap', u'php72u-mbstring', u'php72u-ldap', u'php72u-pecl-memcached', u'pear1u']) => { "ansible_loop_var": "item", "changed": false, "item": [ "php72u", "php72u-cli", "php72u-common", "php72u-devel", "php72u-gd", "php72u-pspell", "php72u-snmp", "php72u-xml", "php72u-xmlrpc", "php72u-mysqlnd", "php72u-pdo", "php72u-odbc", "php72u-process", "php72u-bcmath", "php72u-intl", "php72u-opcache", "php72u-soap", "php72u-mbstring", "php72u-ldap", "php72u-pecl-memcached", "pear1u" ], "rc": 126, "results": [ "No package matching 'php72u' found available, installed or updated" ] }

MSG:

No package matching 'php72u' found available, installed or updated

RUNNING HANDLER [apache-php : restart apache] ** Wednesday 05 May 2021 16:47:29 +0000 (0:00:03.719) 0:03:13.592 *****

PLAY RECAP ***** localhost : ok=121 changed=67 unreachable=0 failed=1 skipped=27 rescued=0 ignored=0

jon-bailey-nstar commented 3 years ago

I'm currently (2021-05-27) trying Meza and ran into this. IUS removed php72u around 2021-02-11 because PHP 7.2 went EoL on 2020-11-30. It's still available in their archive repo.

Steps taken

  1. Installed CentOS-7-x86_64-Minimal-2009.iso on VMWare player 16.1.2
  2. Followed steps at https://www.mediawiki.org/wiki/Meza/Install_on_existing_server - meza commit 707e8fa
  3. The meza deploy monolith step failed with the php72u error in the issue title

Workaround

  1. Edited /etc/yum.repos.d/ius-archive.repo and changed ius-archive to enabled = 1
  2. Ran yum update
  3. Re-ran meza deploy monolith
l1fecoach commented 2 years ago

How do I edited the ius-archive to 1 in the "git-bash"? Running in the same issue with Vibrant on local VM

revansx commented 2 years ago

Not sure if this helps, but fwiw I just successfully upgraded php in my 34.x version of meza from 7.2 to 7.3 by making the following two changes in meza:

  1. in /opt/meza/src/roles/apache-php/tasks/php-redhat.yml i changed the package url from https://repo.ius.io/ius-release-el{{ ansible_distribution_major_version }}.rpm to http://rpms.remirepo.net/enterprise/remi-release-{{ ansible_distribution_major_version }}.rpm

  2. in /opt/meza/config/defaults.yml changed php_ius_version from "php72u" to "php"

Not sure if I had to, but I then manually deleted all the old packages that were php72u* and then ran a full deploy. Seems to have worked well. If this isn't directly helpful, maybe it will at least give you some clues on how to do what you are trying to do. Good luck!