Bug 1204183 - Warn about multiple %triggers with intersecting conditions
Summary: Warn about multiple %triggers with intersecting conditions
Alias: None
Product: Fedora
Classification: Fedora
Component: rpmlint
Version: 20
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2015-03-20 14:36 UTC by Tomas Heinrich
Modified: 2016-09-20 04:52 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-06-30 00:16:18 UTC
Type: Bug

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 702378 0 unspecified CLOSED triggers with satisfied conditions don't get run 2021-02-22 00:41:40 UTC

Internal Links: 702378

Description Tomas Heinrich 2015-03-20 14:36:46 UTC
Description of problem:
When a specfile contains triggers such as:

%triggerin -- trgtst < 1.2
echo "foo1"
%triggerin -- trgtst < 1.3
echo "foo2"
%triggerin -- trgtst < 1.4
echo "foo3"

it would be intuitive to assume that the installation of a trgtst-1.1 package would trigger them all, but that is not how rpm behaves[0].

It would be great if rpmlint could warn about such constructs before they become bugs.
Some more information can be found here: rhbz 702378 - triggers with satisfied conditions don't get run

Version-Release number of selected component (if applicable):

Steps to Reproduce:
rpmlint foo.spec

[0] https://bugzilla.redhat.com/show_bug.cgi?id=702378#add_comment

Comment 1 Ville Skyttä 2015-03-23 10:07:12 UTC
There's some related info also in bug 585384; IMHO it's still rpm that needs a fix. BTW I guess with the latest related changes in upstream rpmbuild would prevent building a specfile with the triggers specified in the initial commit (it doesn't take the versions into account but just looks for and sees multiple triggers defined for the trgtst package _name_).

Comment 2 Fedora End Of Life 2015-05-29 13:45:28 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-30 00:16:18 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.