Description of problem: mga7 1/52: removing lib64webkit2gtk-gir4.0-2.26.2-1.1.mga7.x86_64 ############################## /var/tmp/rpm-tmp.XfYrA9: line 1: conditional binary operator expected /var/tmp/rpm-tmp.XfYrA9: line 1: syntax error near `==0' /var/tmp/rpm-tmp.XfYrA9: line 1: `[[ $1 ==0 || $2 == 0 ]] && rm -f /usr/lib/cups/backend/smb' warning: %triggerun(samba-client-4.10.11-1.mga7.x86_64) scriptlet failed, exit status 2 ERROR: 'script' failed for samba-client-4.10.11-1.mga7.x86_64 2/52: removing samba-client-4.10.11-1.mga7.x86_64 ########################## Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: As root 1. urpmi_args="--wait-lock --replacefiles --auto-update --auto --download-all" 2. script -c "urpmi $dl_args $urpmi_args" install_updates.log 3. grep -E "conditional|error|warning" install_updates.log 3.
Thank you for reporting this. So the command you actually did was (or = to): # urpmi --wait-lock --replacefiles --auto-update --auto --download-all This looks like a failure removing the just superseded samba-client pkg from 4.10.11-1.mga7 to 4.10.12-1.mga7 which coincidentally I have just done from the normal 'update' Systray icon; *without* visible error; but that was GUI, not terminal. However, the syntax error is clear enough; $1 ==0 rather than $1 == 0 Assigning to rpm stack people. Unsure whether the exact SRPM version matters, the old or the new.
Assignee: bugsquad => rpmstack
(In reply to Lewis Smith from comment #1) > Thank you for reporting this. Problem was also in previous version, but I did not report it, thinking QA/DEV/Packager would catch it on next update/release. > This looks like a failure removing the just superseded samba-client pkg > from 4.10.11-1.mga7 > to 4.10.12-1.mga7 > which coincidentally I have just done from the normal 'update' Systray icon; > *without* visible error; but that was GUI, not terminal. I wondered how the bug sneaked through QA. Sounds like someone should open a bug report about the gui did not flag the problem. :) > However, the syntax error is clear enough; $1 ==0 rather than $1 == 0 > > Assigning to rpm stack people. > Unsure whether the exact SRPM version matters, the old or the new. Agree it appears to be just bad code in trigger.
(In reply to Lewis Smith from comment #1) > Assigning to rpm stack people. Why not to the samba maintainer? This is not something special to the rpm stack, it's just a typo in a %post scriptlet, which has already been removed from the cauldron package.
CC: (none) => doktor5000
Already reported and taken care of in another bug. Will be fixed in the next Samba update. *** This bug has been marked as a duplicate of bug 25903 ***
Status: NEW => RESOLVEDResolution: (none) => DUPLICATE
(In reply to Florian Hubold from comment #3) > > Assigning to rpm stack people. > Why not to the samba maintainer? This is not something special to the rpm > stack, it's just a typo in a %post scriptlet, which has already been removed > from the cauldron package. My mistake; a fair cop. Hope you told me privately (like I asked of devs in such situations). Just chance I re-visited this bug & saw this comment. (In reply to David Walser from comment #4) > Already reported and taken care of in another bug. Will be fixed in the > next Samba update. > *** This bug has been marked as a duplicate of bug 25903 *** Another mistake! I took it as applying just to the latest samba update. Also, BitTwister being one of our experienced helpers, I just believed it. I must tighten up my duplicate checking...
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=27414
See Also: https://bugs.mageia.org/show_bug.cgi?id=27414 => (none)