Bug 30853 - shadow-utils-4.12.3-1.mga9 breaks building rpm packages with iurt
Summary: shadow-utils-4.12.3-1.mga9 breaks building rpm packages with iurt
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-09-15 17:29 CEST by Aurelian R
Modified: 2022-09-16 00:01 CEST (History)
0 users

See Also:
Source RPM: shadow-utils-4.12.3-1.mga9.src.rpm
CVE:
Status comment:


Attachments

Description Aurelian R 2022-09-15 17:29:12 CEST
After updating to latest version(4.12.3) of shadow-utils, building rpms with iurt doesn't work anymore. It fails with error:
 
D: [iurt] [iurt] perl command
D: [iurt_root_command] Running iurt_root_command --cp /home/aurelian/MageiaFiles/rpmbuild/SRPMS//wine-7.17-1.20220914.1.mga9X.src.rpm...
D: [iurt_root_command] Copying files
F: [iurt_root_command] /home/aurelian/MageiaFiles/Iurt/chroot_tmp/aurelian/chroot_cauldron.i586.0.20220915143339/home/aurelian/rpmbuild/SRPMS/ forbidden
I: [iurt_root_command] ERROR: Copying files
D: [iurt] [iurt] Command exited with 256.
E: [iurt] [iurt] ERROR: call_ret=1 kill= err=256 ()
F: [iurt] [iurt] Command failed: perl

I: [iurt] [iurt] --------------- Command failed, full output follows ---------------
I: [iurt] [iurt] 
I: [iurt] [iurt] --------------- end of command output ---------------
D: [iurt] [iurt] clean chroot

The workaround for me was to revert to a previous version of shadow-utils(4.9) and that is very cumbersome for Cauldron as the old shadow-util rpms have to be in the repos that one uses. 
I see that on Mageia BS iurt started to run properly after a few hiccups, so
any other easier workaround or a specific reason why iurt started to fail would be appreciated.
Regards.
Comment 1 Aurelian R 2022-09-16 00:01:13 CEST
It looks like this bug is solved by the latest release, shadow-utils-4.12.3-2.mga9.
I will close it at it looks like normal issues nothing serious, :).
Cheers!

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


Note You need to log in before you can comment on or make changes to this bug.