Bug 27259 - Upgrading from PHP 7.3.19 to 7.3.21 is broken
Summary: Upgrading from PHP 7.3.19 to 7.3.21 is broken
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: Mageia 7
Assignee: Marc Krämer
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 26922 27239
Blocks:
  Show dependency treegraph
 
Reported: 2020-09-08 00:53 CEST by Frédéric "LpSolit" Buclin
Modified: 2020-10-19 11:30 CEST (History)
3 users (show)

See Also:
Source RPM: php-7.3.21
CVE:
Status comment:


Attachments

Description Frédéric "LpSolit" Buclin 2020-09-08 00:53:05 CEST
On my Mageia 7 machine I have PHP 7.3.19, but mgaapplet reports no new updates for PHP despite 7.3.21 is available for weeks in Core Updates. rpmdrake lists both 7.3.21 and 7.4.8 (despite the Core Backports media is not activated and so 7.4.8 should not be listed), but clicking on any 7.3.21 RPM reports one of the following errors (approximatively translated from french):

To update, the following packages must be uninstalled:
lib64php_common7-7.3.19-2.mga7.x86_64
 (because php == 3:7.3.19 is not satisfied)
php-ini-7.3.19-2.mga7.x86_64
 (because php == 3:7.3.19 is not satisfied)

or

To update, the following packages must be uninstalled:
php-curl-7.3.19-2.mga7.x86_64
 (because lib64php_common7 == 3:7.3.19 is not satisfied)
php-fileinfo-7.3.19-2.mga7.x86_64
 (car lib64php_common7 == 3:7.3.19 est non satisfait)
php-fpm-7.3.19-2.mga7.x86_64
 (car lib64php_common7 == 3:7.3.19 est non satisfait)
php-iconv-7.3.19-2.mga7.x86_64
 (car lib64php_common7 == 3:7.3.19 est non satisfait)
php-opcache-7.3.19-2.mga7.x86_64
 (car lib64php_common7 == 3:7.3.19 est non satisfait)
php-phar-7.3.19-2.mga7.x86_64
 (car lib64php_common7 == 3:7.3.19 est non satisfait)


I found no way to install PHP 7.3.21 (also found no way to make PHP 7.4.8 not be listed). Looks like bug 26922 broke it.
David Walser 2020-09-08 15:20:00 CEST

Depends on: (none) => 27239

David Walser 2020-09-08 15:20:24 CEST

Assignee: bugsquad => mageia

Comment 1 papoteur 2020-09-09 08:25:57 CEST
Hello,
I confirm to see 7.4.8 rpm listed in rpmdrake as update candidates, although I have added only updates testing enabled. In rpmdrake, they have a red icon on right (normally blue for updates)

CC: (none) => yves.brungard_mageia

Comment 2 Frédéric "LpSolit" Buclin 2020-09-09 12:54:04 CEST
Now I see that 7.4.10 is available, but now with a blue icon. What's the meaning of blue vs red icons?
Comment 3 Aurelien Oudelet 2020-10-16 19:55:07 CEST
Bugs 27239 has been closed fixed by publishing an update.

Can you manage to install it?

CC: (none) => ouaurelien

Comment 4 David Walser 2020-10-16 22:42:11 CEST
The blue 7.4.10 is a backport, just ignore that.
Comment 5 papoteur 2020-10-17 15:57:25 CEST
(In reply to David Walser from comment #4)
> The blue 7.4.10 is a backport, just ignore that.

It can't be ignored. If I select lib64php_common7 from 7.3.23, 7.4 dependencies are selected from backport (unselected).
There is no problem with urpmi.
Comment 6 Frédéric "LpSolit" Buclin 2020-10-18 22:56:40 CEST
(In reply to Aurelien Oudelet from comment #3)
> Bug 27239 has been closed fixed by publishing an update.
> 
> Can you manage to install it?

No. PHP 7.3.23 is still not listed by mgaapplet. And rpmdrake still reports 7.4.8 from backports despite I did not select this media.
Comment 7 Dave Hodgins 2020-10-19 03:53:20 CEST
https://mirror.math.princeton.edu/pub/mageia/distrib/7.1/x86_64/media/core/updates/php-bz2-7.3.23-1.mga7.x86_64.rpm

It should be on all of the mirrors by now.

What's the output of ...
urpmq --list-media active
urpmq --list-url|grep media/core

CC: (none) => davidwhodgins

Comment 8 Frédéric "LpSolit" Buclin 2020-10-19 11:30:16 CEST
(In reply to Dave Hodgins from comment #7)
> 
> It should be on all of the mirrors by now.


Yes, mgaapplet reported the new PHP right now, and it has been installed without any problem. Thanks!

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.