Hello, I would like to suggest to run RPM scriptlets during build (and only during build) with bash 'set -xv' if possible. Reasoning: At the end of a package build, the binary RPMs get installed and thereby RPM scriptlets are executed. When a RPM scriptlet fails, the build fails but there is nothing in the build log that shows the scriptlet code. Because often in the spec file scriptlets are specified by RPM macros, the actual scriptlet code is also not in the spec file. In the end when a RPM scriptlet fails during build one has to do cumbersome reverse engineering to find out the actual scriptlet code for the particular repository and architecture where it had failed. Even with the actual scriptlet code it is not obvious what exactly had failed without knowing the exact command that had actually failed. If scriptlets would be run with bash 'set -xv' during build the build log would show the actual scriptlet code plus the commands and their arguments as they are executed. This should help a lot to find out the root cause why a scriptlet failed for a particular repository/architecture. Kind Regards Johannes Meixner -- SUSE LINUX GmbH - GF: Felix Imendoerffer, Jane Smithard, Dilip Upmanyu, Graham Norton - HRB 21284 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org