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

[Stephen John Smoogen]

On Nov 3, 2015 07:30, "Steve Dickson" <SteveD at redhat.com> wrote:
>
>
>
> On 11/03/2015 06:59 AM, Michael Schwendt wrote:
> > 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 g
> What I don't understand is there the overlap? I have the following
triggers:
>
> %triggerun -- nfs-utils < 1:1.2.4-2
> %triggerun -- nfs-utils < 1:1.3.1-4.0
>
> where is the overlap?
>

Trigger two is true over any release less than 1.2.4 so it over laps. To
not overlap you need a > range

> steved.
> --
> devel mailing list
> devel at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20151103/59233916/attachment.html>