When you install php-channel-phpunit-1.3-7.mbs2.noarch.rpm you are in fact installing pear.symfony-project.com, which makes install/registering pear packages fail. Somehow the php-channel-phpunit-1.3-7.mga2.src.rpm and php-channel-phpunit-1.3-7.mbs2.noarch.rpm differs. The source rpm is correct but the binary rpm is wrong: [root@localhost /]# cat /usr/share/pear/packages/pear.phpunit.de.xml <?xml version="1.0" encoding="UTF-8" ?> <channel version="1.0" xmlns="http://pear.php.net/channel-1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://pear.php.net/channel-1.0 http://pear.php.net/dtd/channel-1.0.xsd"> <name>pear.symfony-project.com</name> <summary>The symfony project PEAR channel</summary> <suggestedalias>symfony</suggestedalias> <servers> <primary> <rest> <baseurl type="REST1.0">http://pear.symfony-project.com/rest/</baseurl> <baseurl type="REST1.1">http://pear.symfony-project.com/rest/</baseurl> <baseurl type="REST1.2">http://pear.symfony-project.com/rest/</baseurl> <baseurl type="REST1.3">http://pear.symfony-project.com/rest/</baseurl> </rest> </primary> </servers> After further investigation php-pear-channel-horde-1.0-15.mbs2 and php-pear-channel-components-1.0.0-2.mbs2.noarch.rpm are also affected. I suspect the mageia build system / file storage is to blame for this as the affected source rpm packages shares the "channel.xml" file name for Source0:. This makes me quite worried what else may be affected in mga2 (and later?), and no one else noticed?
CC: (none) => johnny
Sorry, my bad. I'm confusing MBS packages with MGA2 ones.
Status: NEW => RESOLVEDResolution: (none) => INVALID
mbs issue
CC: (none) => nicolas.lecureuil