Bug 30733

Summary:	php-pear-PHP_CodeCoverage cannot be installed due to unsatisfied php-pear-Text_Template
Product:	Mageia	Reporter:	Barry Jackson <zen25000>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	mageia
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	php-pear-PHP_CodeCoverage-1.2.17-7.mga8.src.rpm	CVE:
Status comment:

Description Barry Jackson 2022-08-11 01:14:21 CEST

Description of problem:
Install of zoneminder in cauldron fails with the following:

"adding a reason to already rejected package php-pear-PHP_CodeCoverage-1.2.17-7.mga8.noarch: unsatisfied php-pear-Text_Template[>= 1.1.1]"

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Barry Jackson 2022-08-12 01:10:47 CEST

CC: (none) => mageia

Comment 1 Barry Jackson 2022-08-12 01:12:04 CEST

Hi Marc,
Maybe you can help me here, any suggestions?

Comment 2 Marc Krämer 2022-08-12 02:23:20 CEST

yepp. In cauldron I've removed a lot of old pear modules that will not compile any more. Most of those projects are really old (see e.g. https://phpunit.de/announcements/end-of-life-for-pear-installation-method.html )

and don't get any support from their maintainers as well.
For you to get zoneminder running again: you can see CodeCoverage and many other dependancies are only needed for testcases they run at development level:
ZoneMinder-1.36.23/web/api/lib/Cake/TestSuite/CakeTestRunner.php

So I assume, you can remove the TestSuite and Test folder without harm and the package does not need so much (old) dependancies.

Comment 3 Marc Krämer 2022-08-12 02:26:14 CEST

I hope that solves it, if not, just write me again and I can have a closer look to it.

Comment 4 Barry Jackson 2022-08-13 17:20:42 CEST

Hi Marc,
Yes, thanks for your input!
I removed the whole Cake directory after the install to %{buildroot} and then re-organized the Requires: for php-8.2.
Turned out there was also an unrelated bug in 1.36.23 so it needed updating to 1.36.24 as well which now appears to be working fine :)

Closing as fixed

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