Build Error: Trigger fired by the same package is already fired???

[Michael Schwendt]

On Tue, 3 Nov 2015 04:32:47 -0500, Steve Dickson wrote:

> > %triggerun -- nfs-utils < 1:1.3.1-4.0
> > # reset configuration files and running daemons
> > if [ $1 -eq 2 ] ; then
> >     /bin/systemctl enable nfs-client.target >/dev/null 2>&1 || :
> >     /bin/systemctl restart nfs-config  >/dev/null 2>&1 || :
> >     /bin/systemctl restart nfs-client.target  >/dev/null 2>&1 || :
> > fi
> So the answer is... I have to remove the above trigger to get
> the build to work... 
> 
> What policy has changed that we now have to remove triggers
> got get builds to work??? That is not a good direction... IMHO!

AFAIK, overlapping triggers have never worked before, because RPM would
only fire a single trigger. It's good that triggers with overlapping version
ranges cause a build failure instead.