Red Hat Bugzilla – Bug 1247140
Build failure due to bogus complaints about "Trigger fired by the same package is already defined in spec file"
Last modified: 2015-07-27 09:34:23 EDT
Description of problem:
If a package has more than one %triggerun on the same package but with different versions the build fails with the error
Trigger fired by the same package is already defined in spec file
E.g. the openssh-server package in the openssh specfile has two %triggerun as follows:
$ grep triggerun openssh.spec
%triggerun -n openssh-server -- openssh-server < 5.8p2-12
%triggerun -n openssh-server -- openssh-server < 5.9p1-22
A scratch build of this package in Fedora Rawhide is here:
The buildlog from the buildSRPMFromSCM task of this build:
says: "Trigger fired by the same package is already defined in spec file"
In the rpm git history the commit message for the following commit:
reads: "Allow multiple triggers fired by the some package of different versions"
(I assume there is a typo here s/some/same/)
So there seems to have been an attept to fix this problem, but it doesn't seem to have worked since it still trips on this check and fails.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. See above
The problem is that given version intervals overlap, so in some cases both version conditions are fulfilled (e.g for openssh-server-5.6p1-30) but rpm always sets off only one trigger that's why build of that package is refused. Previously rpm didn't refuse to build packages with overlapping version intervals but rpm always set off only one trigger. So probably triggers in your package didn't work as you expected also in previous version of rpm.
This is expected behavior, closing as not a bug.
See also: #585384 and #702378