Description of problem: Doing an upgrade install of a VirtualBox mga8-64 Plasma guest, using the Beta2 Round 3 CI iso, with supplemental online media activated before the install, shows several "script errors" regarding various "php-pear" packages. This particular guest has been used as a test platform for mga8 for at least a year. It has had several packages installed for testing purposes, some of which have been removed, others that remain. The guest has two HP printers, some games, among others, making it a reasonably good simulation of a real-world user's system. It is my belief that the mga8 php-pear packages were installed during an attempted test of mediawiki a little over a year ago. For some reason, I never removed the mediawiki package, even though I never was successful in using it. It has been kept updated, but not yet to the package currently being tested by QA. The upgrade proceeded normally until the end, where it reported the script errors. Clicking on "OK" in that box continued the install to a normal-looking conclusion, and I rebooted into a working desktop.
Created attachment 13802 [details] report.bug.xz of the upgraded system Attaching the report.bug.xz from the updated guest. Searching for "php-pear" I see where there were problems having to do with conflicts, but understanding the causes of them is beyond my skills.
Severity: normal => majorPriority: Normal => High
Summary: Beta2 Round 3 upgrade in VirtualBox several php-pear script errors => Beta2 Round 3 upgrade in VirtualBox shows several php-pear script errors
Thanks for the report and all the evidence, TJ.
Assignee: bugsquad => php
@Thomas: can you share your insights? I don't really see anything in that big report file. The only conflicts I see is: * ERROR: selection failed: firefox-en_ZA-67.0.4-1.mga7.noarch (due to conflicts with firefox-78.5.0-1.mga7.x86_64) * ERROR: selection failed: firefox-en_ZA-67.0.4-1.mga7.noarch (due to conflicts with firefox-78.5.0-1.mga7.x86_64) * ERROR: selection failed: firefox-en_ZA-67.0.4-1.mga7.noarch (due to conflicts with firefox-78.5.0-1.mga7.x86_64) all pear stuff looks like this: * packageCallbackChoices: default choice ('php-pear-Crypt_GPG') from php-pear-Crypt_GPG,php-pear-Crypt_GPG for php-pear-Crypt_GPG
CC: (none) => mageia
Please understand that for the most part I don't have a clue here. That said... Looking at the file again and trying to comprehend, the "conflicts" I saw were probably just part of the process, as I see the same sort of messages regarding many other packages. There would be a message that "php-pear-whatever conflicts because of missing something" and then there'd be a reference to task-obsolete. Many, many messages of that type. But, searching the file for "error" I come up with this, about 2/3 of the way through the file: * urpmi error: ERROR: 'script' failed for php-pear-DbUnit-1.3.1-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHPUnit_Selenium-1.3.3-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHP_CodeCoverage-1.2.17-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHPUnit-3.7.34-5.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHPUnit_MockObject-1.2.3-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-Text_Template-1.2.0-6.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-File_Iterator-1.3.4-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHP_Invoker-1.1.3-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHP_Timer-1.0.5-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHPUnit_Story-1.0.2-7.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-Symfony2_Yaml-2.4.4-6.mga8.noarch * urpmi error: ERROR: 'script' failed for php-pear-PHP_TokenStream-1.2.2-6.mga8.noarch I hope that narrows it down a bit. If there is another install log that would help, let me know and I'll see if I can get it.
Wait... (In reply to Marc Krämer from comment #3) > @Thomas: can you share your insights? I don't really see anything in that > big report file. > The only conflicts I see is: > * ERROR: selection failed: firefox-en_ZA-67.0.4-1.mga7.noarch (due to > conflicts with firefox-78.5.0-1.mga7.x86_64) > * ERROR: selection failed: firefox-en_ZA-67.0.4-1.mga7.noarch (due to > conflicts with firefox-78.5.0-1.mga7.x86_64) > * ERROR: selection failed: firefox-en_ZA-67.0.4-1.mga7.noarch (due to > conflicts with firefox-78.5.0-1.mga7.x86_64) > > > all pear stuff looks like this: > * packageCallbackChoices: default choice ('php-pear-Crypt_GPG') from > php-pear-Crypt_GPG,php-pear-Crypt_GPG for php-pear-Crypt_GPG Those are mga7 references. Could I have uploaded the wrong file? I have two files here from /root/drakx. report.bug and report.bug.xz. I thought they were the same, except one is compressed, but... This guest might have originally been a mga7 guest that was updated, and there might be some old files left from that upgrade. Checking dates... Yep, that's an old report file. I messed up, big time. Will zip the correct file and upload in a few minutes.
Created attachment 13803 [details] correct report.bug
Attachment 13802 is obsolete: 0 => 1
Sorry about that. I feel like an idiot. Sigh.
As you can see, the files are all from mga8 and have all been removed. e.g. %postun(php-pear-PHPUnit_Selenium-1.3.3-7.mga8.noarch) scriptlet failed, exit status 255 I guess we can't do much about this scriptlet error.
Priority: High => LowSeverity: major => minor
New versions of those packages were not installed, and I was concerned for upgraders who use mediawiki not having the dependencies they needed to use it after the upgrade. I would have simply tried to run it myself, but as I stated in comment 0 I never did get it to work for me before. Doing some more research this morning, I see that the mga8 packages were indeed dependencies of mediawiki, but they are not required in mga9. So most likely all is OK after all. Sorry about the noise. I'm stumbling around in the dark here and bumped into a table, so I yelled about it. QA's working policy is "better to examine it now than find a problem after the release."
No, thank you for the repot. Better check it, before we have a severe problem.
Resolution: (none) => WONTFIXStatus: NEW => RESOLVED