Closed #209.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/209#event-2996950403___
Rpm-maint mailing list
As already pointed out this is indeed the expected behaviourand you can use
%triggerun instead. If you do not want to rely on the arguments to the trigger
script you can also check some files on disc if to determine the operation you
are in.
--
You are receiving this because you are
Case `%triggerin -- %{name} < 1.0-2.new`:
RPM triggers `%triggerin -- %{name} < 1.0-2.new`. It is according to the
description in the documentation [1] (_The %triggerin script is also run when
your package_ (`baz-1.0-2.new`) _is installed or upgraded, should the target
package_
I want to put a scriptlet into new package for package downgrading to unapply a
new feature in new package, but RPM triggers `%triggerin` scriptlet in wrong
situation.
RPM SPEC for `baz-1.0-1.old.noarch.rpm`:
```
Summary: Baz
Name: baz
Version: 1.0
Release: 1.old
Group: test group
License:
