https://bugzilla.redhat.com/show_bug.cgi?id=1649552
--- Comment #20 from Severin Gehwolf <[email protected]> --- Installing : jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64 1/1 Running scriptlet: jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64 1/1 bash: /builddir/build/SOURCES/symlink_libs.sh: No such file or directory warning: %triggerin(jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64) scriptlet failed, exit status 127 Non-fatal <unknown> scriptlet failure in rpm package jmc Non-fatal <unknown> scriptlet failure in rpm package jmc bash: /builddir/build/SOURCES/symlink_libs.sh: No such file or directory warning: %triggerin(jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64) scriptlet failed, exit status 127 Non-fatal <unknown> scriptlet failure in rpm package jmc Non-fatal <unknown> scriptlet failure in rpm package jmc bash: /builddir/build/SOURCES/symlink_libs.sh: No such file or directory warning: %triggerin(jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64) scriptlet failed, exit status 127 Non-fatal <unknown> scriptlet failure in rpm package jmc Non-fatal <unknown> scriptlet failure in rpm package jmc bash: /builddir/build/SOURCES/symlink_libs.sh: No such file or directory warning: %triggerin(jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64) scriptlet failed, exit status 127 Non-fatal <unknown> scriptlet failure in rpm package jmc Non-fatal <unknown> scriptlet failure in rpm package jmc bash: /builddir/build/SOURCES/symlink_libs.sh: No such file or directory warning: %triggerin(jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64) scriptlet failed, exit status 127 Non-fatal <unknown> scriptlet failure in rpm package jmc Non-fatal <unknown> scriptlet failure in rpm package jmc Verifying : jmc-7.0.0-0.20181130hg1ddf3baa4e26.fc28.x86_64 This failure comes from this in the spec: # set triggers to update symlinks when Eclipse JARs are updated %triggerin -- eclipse-ecf-core bash %{SOURCE3} %{buildroot}%{_jmcdir}/plugins You need to actually install the symlinking script, e.g. into %{_jmcdir}/tools/symlink_libs.sh, and then call it with %{_jmcdir}/plugins (no %buildroot). The man page still contains the wrong path. I suggest to pre-process the man page in prep, substituting %{_jmcdir} via sed or so and then install the processed man page rather than the verbatim SOURCE2. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
