Description of problem: When I do an upgrade install of a Mageia 6 64-bit Xfce guest in VirtualBox, using the M7 beta3 Round 3 Classical iso, near the end I encounter a script failure message for mtink-1.0.16-16.mga6.x86_64. I saw this with two separate upgrades. The original guest was created from the 6.1 Xfce LIVE iso, and fully updated before proceeding with the upgrade. I was able to complete the upgrade without further incident, and the result showed no ill effects. However, that is probably because mtink is a configuration tool for Epson printers, and I do not have one.
Assigning to all packagers collectively, since there is no registered maintainer for this package. Also CC'ing two committers.
Assignee: bugsquad => pkg-bugsCC: (none) => loginov_alex, marja11, smelror
Still in effect in the RC round 4 isos.
CC: (none) => marci_r
The bug is that the post-uninstall script for the mtink package attempts to restart the mtinkd service after the package has been updated. When using the classical installer ISO to upgrade, the target system is not running, so restarting the service fails. The fix is to ignore the error, as is already done in the post-install script. The mga6 package needs to be updated to fix this bug. There are no functional changes to the package. If the mtinkd service was running before the update, it should still be running afterwards, and vice-versa. As I don't own an Epsom inkjet printer, I can't test much else. Suggested Advisory ================== Updated mtink package prevents 'script failed' error when using the classical installer ISO to upgrade to Mageia 7. SRPMs ===== mtink-1.0.16-17.mga6.src.rpm i586 ==== mtink-1.0.16-17.mga6.i586.rpm x86_64 ====== mtink-1.0.16-17.mga6.x86_64.rpm
Assignee: pkg-bugs => qa-bugsSource RPM: (none) => mtink-1.0.16-16.mga6,mtink-1.0.16-18.mga7Status: NEW => ASSIGNEDCC: (none) => mageiaComponent: Installer => RPM PackagesWhiteboard: (none) => MGA6TOO
Martin, do you know if this package affects other Epson peripherals, like scanners? Or is it just printers? I have neither, so I can't test it. But, I can put out a call to QA. If scanners are affected too, it would widen the possibility of finding a tester.
Never mind. I should have checked with DuckDuckGo before asking. It just affects printers. According to one Debian site, it affects mostly Epsons, though some HP and Canon models are also supported. (They didn't say which ones.)
Confirmed that updating the Mga6 package results in eliminating the script error message. I saw that mtink was installed from the RC iso, and then updated later from online. At the end of the very smooth upgrade, mtink-1.0.16-18.mga7 had been installed. If no one steps forward in the next day or two to test the Epson functions, I will OK and verify on the basis of a clean install.
pushed in cauldron by akien on 01-06-2019
CC: (none) => tmbVersion: Cauldron => 6Whiteboard: MGA6TOO => (none)
Validating for MGA6. Advisory in Comment 3.
Keywords: (none) => validated_updateWhiteboard: (none) => MGA6-64-OKCC: (none) => sysadmin-bugs
Keywords: (none) => advisory
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2019-0041.html
Status: ASSIGNED => RESOLVEDResolution: (none) => FIXED