[packages/systemd] - add epoch to triggers (yes, both need it)

[Jan Rękorajski]

On Wed, 27 May 2015, Elan Ruusamäe wrote:

> On 26.05.2015 23:14, baggins wrote:
> > commit fd907fd52a09b244ccdce04f7acd1e244627fc35
> > Author: Jan Rękorajski <baggins at pld-linux.org>
> > Date:   Tue May 26 22:14:00 2015 +0200
> >
> >      - add epoch to triggers (yes, both need it)
> >
> >   systemd.spec | 4 ++--
> >   1 file changed, 2 insertions(+), 2 deletions(-)
> > ---
> > diff --git a/systemd.spec b/systemd.spec
> > index f6e9655..5a51496 100644
> > --- a/systemd.spec
> > +++ b/systemd.spec
> > @@ -910,11 +910,11 @@ if [ "$1" = "0" ]; then
> >   	%groupremove systemd-journal
> >   fi
> >   
> > -%triggerpostun -- systemd < 208-1
> > +%triggerpostun -- systemd < 1:208-1
> >   chgrp -R systemd-journal /var/log/journal
> >   chmod g+s /var/log/journal
> >   
> > -%triggerpostun -- systemd < 220-1
> > +%triggerpostun -- systemd < 1:220-1
> >   # https://bugs.freedesktop.org/show_bug.cgi?id=89202
> >   /bin/getfacl -p /var/log/journal/$(cat /etc/machine-id) | grep -v '^#' | sort -u | /bin/setfacl -R --set-file=- /var/log/journal/$(cat /etc/machine-id) || :
> >
> 
> what's the current state of multiple triggers per package combination? 
> are they both fired? in what order?
> 
> i recall, that in old times, it was just better to move triggers to one 
> trigger (one with biggest version combination) and write all trigger 
> bodies there, accounting that the trigger might have already been ran

AFAIK rpm5 does not have this problem and multiple triggers work.

-- 
Jan Rękorajski                    | PLD/Linux
SysAdm | baggins<at>pld-linux.org | http://www.pld-linux.org/