On 4 August 2015 at 15:43, Lubos Kardos <lkar...@redhat.com> wrote: > The problem is when you upgrade distro N to N+2 both triggers should > be run but only one was run, which was confusing so we disallowed > triggers fired by the same package with overlapping version intervals. > And initscripts <= 4.72 and initscripts <= 8.38-2 overlaps. > Have a look at bugs #585384, #702378 that initiate this change.
OK for that but there's a related issue with file triggers: I was testing converting our old filetriggers to new upstream filetriggers. However it looks like it's no more possible to have 2 different filetriggers (for %trans* ones) on the same directory: D: %triggerin(null-1:11-11.mga6.x86_64): waitpid(19591) rc 19591 status 0 rpm: backend/dbiset.c:62: dbiIndexSetUniq: Assertion `set->count > 0' failed. See the calls to rpmtsUniqTriggers() in lib/rpmtriggers.c (added in: http://rpm.org/gitweb?p=rpm.git;a=commitdiff;h=30a5603159083f2840bfae801ab27ba5f78c36e7) Why is that? For now, I've workarounded the case I've seen but there may be other cases... _______________________________________________ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
